Examples
Worked examples
- Is an instance
The ERIC Thesaurus, used to index education research literature in the ERIC database, is a controlled vocabulary built following Z39.19-style conventions: each descriptor has a scope note, and non-preferred synonyms point (USE) to the preferred descriptor, which in turn carries BT/NT/RT cross-references to related descriptors.
- Is an instance
An institutional repository maintaining a subject-tagging vocabulary for deposited datasets applies Z39.19's term-form rules (e.g., preferring 'Climate change' over an ambiguous or overly narrow variant) and its equivalence relationships, so that a search for a common synonym still retrieves records tagged with the preferred term.
- Is an instance
A government agency thesaurus for classifying technical reports (a common domain-specific use case Z39.19 was designed for) assigns each preferred term a unique identifier, a scope note defining its intended use, and explicit BT/NT links up and down a subject hierarchy.
Counter-examples
Looks similar, but isn't
- Not an instance
A folksonomy or free-tagging system, where users apply any text string they like with no approved term list and no cross-references between synonymous or related tags, is not a Z39.19-conformant controlled vocabulary -- it has no equivalence, hierarchical, or associative relationship structure at all, which is the entire mechanism Z39.19 exists to standardize.
- Not an instance
A flat, unstructured pick-list of category names with no BT/NT/RT relationships and no documented scope notes is a controlled vocabulary in the loosest sense (a fixed term list) but does not meet Z39.19's guidelines for a properly constructed and managed vocabulary, since it provides no way to navigate between related or hierarchically nested concepts.
Editorial commentary
ANSI/NISO Z39.19 — formally “Guidelines for the Construction, Format, and Management of Monolingual Controlled Vocabularies,” designated Z39.19-2005 and reaffirmed in 2010 as Z39.19-2005 (R2010) — is the American National Standard governing how to build, format, test, and maintain controlled vocabularies and thesauri used for information storage and retrieval. It was developed and is maintained by NISO (the National Information Standards Organization), an ANSI-accredited standards developer. The standard’s core purpose is stated plainly in its scope: vocabulary control exists to achieve consistency in how content is described, so that a search using any one of several possible terms for a concept still retrieves everything relevant that has been indexed under it.
What the standard covers
Z39.19 addresses controlled vocabularies across a spectrum of structural complexity, from simple to most elaborate: authority lists (a single approved term for each concept, no relationships), synonym rings (sets of interchangeable terms with no preferred form), taxonomies (hierarchically arranged terms), and full thesauri (hierarchical arrangement plus explicit equivalence and associative relationships). For each, it specifies rules covering term selection and form (for example, preferring noun phrases, consistent singular/plural conventions, and using a parenthetical qualifier to disambiguate a homograph), how terms should be displayed, how a vocabulary should be tested before release, and how it should be governed and updated over time as usage and the underlying subject domain change.
The three relationship types
The best-known part of Z39.19, and the part most other thesaurus/vocabulary tooling has standardized around, is its definition of three relationship types between terms:
- Equivalence (USE / UF — “Used For”): links a non-preferred synonym or near-synonym to the single preferred term that should be used for indexing. A search or browse on the non-preferred term redirects the user to the preferred one.
- Hierarchical (BT / NT — Broader Term / Narrower Term): expresses genus-species, whole-part, or instance relationships, letting a user navigate from a general concept down to more specific ones (or back up).
- Associative (RT — Related Term): connects terms that are conceptually related in a way a searcher would find useful, but that are neither synonymous nor in a hierarchical relationship with each other.
These three relationship types, and the USE/UF, BT/NT, RT abbreviations themselves, are the vocabulary most thesaurus-management software and library/information-science curricula use as the default framework for describing how any controlled vocabulary’s terms relate to one another — Z39.19 is the standard those conventions trace back to.
Where Z39.19 fits among metadata and vocabulary standards
Z39.19 is a metadata schema-adjacent standard in a specific sense: it does not define a set of descriptive fields the way a schema like Dublin Core does, but it governs the controlled-term values that fill a schema’s subject or keyword fields. It sits alongside other NISO information-organization and data-documentation standards covered elsewhere in this dictionary, including domain-specific documentation formats such as DDI Codebook (survey and social-science dataset documentation) and PREMIS (digital preservation metadata), and web-native data-catalog description via the W3C’s DCAT (Data Catalog Vocabulary) — each solves a different part of describing and organizing data, while Z39.19 specifically governs the subject-indexing vocabulary layer. Internationally, the closely related ISO 25964 (Thesauri and interoperability with other vocabularies, parts 1-2) covers similar ground with some structural differences; content produced to one is not automatically interchangeable with the other without mapping.
Why it matters for research data management
Controlled vocabularies built to Z39.19 (or an equivalent framework) underpin subject indexing in library catalogs, institutional and disciplinary repositories, and government and scientific databases. For research data management specifically, a well-governed controlled vocabulary for subject tagging or keyword assignment — rather than free-text, uncontrolled tags — is part of what makes a dataset genuinely findable: search and retrieval work reliably only when the same concept is consistently represented by the same controlled term, with documented relationships to its synonyms and related concepts, rather than left to whatever free-text keyword each depositor happens to choose.
CASRAI and the NISO standards ecosystem
CASRAI is not a steward of Z39.19 itself. It is worth noting, for context, that CASRAI does have a direct working relationship with NISO elsewhere in the standards landscape: CASRAI has stewarded the CRediT (Contributor Roles Taxonomy) taxonomy since 2014, and CRediT was formalized as the full ANSI/NISO Z39.104-2022 standard, with NISO now holding primary stewardship and CASRAI operating as a federation partner. That relationship illustrates the kind of cross-organizational standards work NISO coordinates across the research-information landscape — Z39.19 is a separate, earlier NISO standard with no CASRAI stewardship role, included here because it is the foundational reference for how the controlled vocabularies referenced throughout this dictionary and elsewhere in research data management are properly constructed.
References
- NISO, ‘ANSI/NISO Z39.19-2005 (R2010): Guidelines for the Construction, Format, and Management of Monolingual Controlled Vocabularies’ (niso.org/publications/ansiniso-z3919-2005-r2010).
Frequently Asked Questions
What do BT, NT, RT, USE, and UF mean in a Z39.19 thesaurus?
These abbreviations identify the three relationship types Z39.19 defines between vocabulary terms. USE and UF (“Used For”) mark equivalence, linking a non-preferred synonym to the single preferred term; BT and NT (Broader Term / Narrower Term) mark hierarchical relationships such as genus-species or whole-part; and RT (Related Term) marks an associative link between concepts that are neither synonyms nor hierarchically related. Most thesaurus-management software and library/information-science curricula use this same USE/UF, BT/NT, RT framework, tracing back to Z39.19.
What’s the difference between a controlled vocabulary, a taxonomy, and a thesaurus?
Z39.19 treats these as points along a spectrum of increasing structural complexity. An authority list is the simplest form: a single approved term per concept with no relationships defined. A synonym ring adds interchangeable terms with no preferred form. A taxonomy arranges terms hierarchically, and a full thesaurus is the most elaborate, combining hierarchical arrangement with explicit equivalence and associative relationships.
Is ANSI/NISO Z39.19 the same as ISO 25964?
No. ISO 25964 (Thesauri and interoperability with other vocabularies) covers similar ground internationally but has structural differences from Z39.19. Content built to one standard is not automatically interchangeable with the other without mapping between them.
Who maintains the Z39.19 standard?
NISO (the National Information Standards Organization), an ANSI-accredited standards developer, developed and maintains Z39.19. The current version, Z39.19-2005, was reaffirmed in 2010 and is formally cited as Z39.19-2005 (R2010).
Does CASRAI maintain or steward the Z39.19 standard?
No. CASRAI has no stewardship role in Z39.19, which is a separate, earlier NISO standard. CASRAI’s own working relationship with NISO is elsewhere: CASRAI has stewarded the CRediT (Contributor Roles Taxonomy) since 2014, and CRediT was later formalized as ANSI/NISO Z39.104-2022, with NISO now holding primary stewardship and CASRAI operating as a federation partner.
Why does a controlled vocabulary matter for research data management?
A dataset is genuinely findable only when the same concept is consistently described using the same term across records, rather than left to whatever free-text keyword each depositor happens to choose. A controlled vocabulary built to Z39.19 or an equivalent framework, complete with documented relationships to synonyms and related concepts, is what makes subject tagging and search retrieval reliable in library catalogs, repositories, and scientific databases.
Machine-readable encodings
Use in your systems
<role vocab="credit"
vocab-identifier="https://casrai.org/dictionary/"
vocab-term="ANSI/NISO Z39.19 (Controlled Vocabularies and Thesauri)"
vocab-term-identifier="https://casrai.org/dictionary/term/ansi-niso-z39-19-controlled-vocabularies-thesauri" />{
"@context": "https://schema.org",
"@type": "DefinedTerm",
"@id": "https://casrai.org/dictionary/term/ansi-niso-z39-19-controlled-vocabularies-thesauri",
"name": "ANSI/NISO Z39.19 (Controlled Vocabularies and Thesauri)",
"identifier": "https://casrai.org/dictionary/term/ansi-niso-z39-19-controlled-vocabularies-thesauri",
"description": "A controlled vocabulary or thesaurus is constructed to ANSI/NISO Z39.19-2005 (R2010), \"Guidelines for the Construction, Format, and Management of Monolingual Controlled Vocabularies,\" when it follows the standard's rules for term selection and form (preferring noun phrases, singular/plural conventions, avoiding ambiguous homographs without a qualifier), and when it displays the three relationship types Z39.19 defines between terms: equivalence relationships (USE/UF, linking a non-preferred synonym to its preferred term), hierarchical relationships (BT/NT, Broader Term/Narrower Term, for genus-species, whole-part, or instance relationships), and associative relationships (RT, Related Term, for terms that are conceptually related but not synonymous or hierarchical). The standard covers several vocabulary types along a spectrum of structural complexity -- authority lists, synonym rings, taxonomies, and full thesauri -- and specifies how each should be tested, formatted, and maintained over time (adding, deprecating, and merging terms as usage and the underlying domain evolve).",
"inDefinedTermSet": "https://casrai.org/dictionary/domain/data-infrastructure#set",
"url": "https://casrai.org/dictionary/term/ansi-niso-z39-19-controlled-vocabularies-thesauri",
"sameAs": [],
"license": "https://creativecommons.org/licenses/by/4.0/",
"publisher": {
"@id": "https://casrai.org/#organization"
},
"dateModified": "2026-08-15T04:42:00",
"inLanguage": "en"
}






