Every taxonomy release is a governance event
IPTC ships NewsCodes updates quarterly. One recent rework of the economy and business branch added 9 concepts, retired 60, modified 120, and moved 79 in the hierarchy. If your local tags map to Media Topics, every one of those changes is a reconciliation job. TopQuadrant governs your vocabularies and the mappings between them, so a release is a reviewed diff.
Trusted to govern the data behind the world's most regulated decisions.
Five vocabularies per asset, and nothing reconciling them
A single video may need IPTC Media Topics for subject, NewsCodes for genre and provider, EBUCore or PBCore for technical and rights metadata, schema.org for search surfacing, and your own editorial taxonomy on top. Each is maintained by a different body on a different cycle. The reconciliation between them is the actual asset, and it is usually the one thing nobody owns.
IPTC NewsCodes releases a year, each retiring, relabelling, and moving concepts your local tags map to.
Prebuilt vocabularies and ontologies available to adopt, including the standards this sector publishes against.
One governed concept scheme per domain, with every external mapping held alongside it.
SKOS-native vocabularies
Model the vocabulary the way the standards do
Concept schemes, preferred and alternate labels, broader and narrower relationships, and multilingual labels are native here, because SKOS is the W3C standard IPTC’s own vocabularies are published in. You work in the same model your standards bodies do.
- Concepts, not strings. Each term is a governed concept with a definition, an owner, and a history.
- Polyhierarchy supported. A concept can sit under more than one parent without duplication.
- Multilingual by design. Labels per language, governed together and released together.
External standard mappings
Map to IPTC and schema.org, and keep the mapping current
Mappings from your editorial taxonomy to Media Topics, NewsCodes, schema.org, EBUCore, PBCore, Dublin Core, or BIBFRAME are governed assets with versions and provenance. When a standard releases, you see which of your mappings now point at retired concepts.
- Version-stamped mappings. Each correspondence records the standard release it was asserted against.
- Release diffs. New, retired, relabelled, and moved concepts in each external update.
- Break reports. Your mappings and tagged content affected by an external change, listed.
Change management across content
Retire a concept without orphaning the archive
Renaming or retiring a term has to carry the content with it. Concepts deprecate with successor relationships, so historical tagging still resolves and search continues to find the material under its new label.
- Deprecation with successors. Retired concepts stay resolvable and point to what replaced them.
- Impact before change. Every tagged asset and downstream system affected by an edit.
- Bulk retagging. Migrate affected content automatically where the mapping is unambiguous.
Governing machine tagging
Auto-tagging still needs a taxonomy to be right about
Automated tagging is how the volume gets handled, which shifts the taxonomy team’s job from tagging to designing, validating, and auditing what the model produced. Suggestions are constrained to governed concepts, scored, and queued for review by rules you set.
- Vocabulary-bounded suggestions. The model can only propose governed concepts.
- Threshold-driven review. Confidence rules decide what publishes and what waits for a human.
- Provenance on every tag. Human or machine, which model, which version, which reviewer, when.