← Back to catalogue
Published

Taxonomy / Classification Scheme

vr.wm-knw-018 · wm-knw-018-taxonomy-classification-scheme

Represent one governed versioned knowledge-organization scheme containing concept definitions, labels, notations, semantic relations, mappings and release governance.

World Models Information and virtual systems INF.KNW.TAX

Bundle → Layer → Finding → Questions Filled

6 bundles · 12 layers · 24 findings · 72 questions

Scheme identity, profile, scope and release Groups the governed Resource Consumption concern for scheme identity, profile, scope and release.

Identity, namespace, version and distribution

Groups Resource Consumption context for identity, namespace, version and distribution without importing neighboring master lifecycles.

Scheme identifier, canonical URI, namespace, prefix and local-ID policy

Records scheme identifier, canonical uri, namespace, prefix and local-id policy as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.

  1. Which scheme and concept identities, profile, scope, language, relation semantics and release establish scheme identifier, canonical uri, namespace, prefix and local-id policy? identity
  2. Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses scheme identifier, canonical uri, namespace, prefix and local-id policy, and under which authority? ownership
  3. Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify scheme identifier, canonical uri, namespace, prefix and local-id policy? validation

Version, edition, release status, date, predecessor, successor and distribution

Records version, edition, release status, date, predecessor, successor and distribution as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.

  1. Which scheme and concept identities, profile, scope, language, relation semantics and release establish version, edition, release status, date, predecessor, successor and distribution? lifecycle
  2. Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses version, edition, release status, date, predecessor, successor and distribution, and under which authority? authority
  3. Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify version, edition, release status, date, predecessor, successor and distribution? security

Scheme kind, purpose, scope, audience, language and authority

Groups Resource Consumption context for scheme kind, purpose, scope, audience, language and authority without importing neighboring master lifecycles.

Taxonomy, thesaurus, classification, list, synonym-ring, ontology and hybrid profile

Records taxonomy, thesaurus, classification, list, synonym-ring, ontology and hybrid profile as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.

  1. Which scheme and concept identities, profile, scope, language, relation semantics and release establish taxonomy, thesaurus, classification, list, synonym-ring, ontology and hybrid profile? classification
  2. Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses taxonomy, thesaurus, classification, list, synonym-ring, ontology and hybrid profile, and under which authority? requirement
  3. Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify taxonomy, thesaurus, classification, list, synonym-ring, ontology and hybrid profile? privacy

Purpose, subject, scope, audience, language, jurisdiction, owner, publisher and steward

Records purpose, subject, scope, audience, language, jurisdiction, owner, publisher and steward as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.

  1. Which scheme and concept identities, profile, scope, language, relation semantics and release establish purpose, subject, scope, audience, language, jurisdiction, owner, publisher and steward? authority
  2. Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses purpose, subject, scope, audience, language, jurisdiction, owner, publisher and steward, and under which authority? constraint
  3. Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify purpose, subject, scope, audience, language, jurisdiction, owner, publisher and steward? retention
Concepts, labels, definitions, notations and notes Groups the governed Resource Consumption concern for concepts, labels, definitions, notations and notes.

Concept identity, membership, type and referent boundary

Groups Resource Consumption context for concept identity, membership, type and referent boundary without importing neighboring master lifecycles.

Concept URI, local identifier, in-scheme, top concept and concept type

Records concept uri, local identifier, in-scheme, top concept and concept type as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.

  1. Which scheme and concept identities, profile, scope, language, relation semantics and release establish concept uri, local identifier, in-scheme, top concept and concept type? identity
  2. Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses concept uri, local identifier, in-scheme, top concept and concept type, and under which authority? process
  3. Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify concept uri, local identifier, in-scheme, top concept and concept type? access

Concept characteristics, extension, intension, referent, authority and RWO distinction

Records concept characteristics, extension, intension, referent, authority and rwo distinction as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.

  1. Which scheme and concept identities, profile, scope, language, relation semantics and release establish concept characteristics, extension, intension, referent, authority and rwo distinction? definition
  2. Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses concept characteristics, extension, intension, referent, authority and rwo distinction, and under which authority? event
  3. Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify concept characteristics, extension, intension, referent, authority and rwo distinction? exception

Lexical label, definition, note, example and notation

Groups Resource Consumption context for lexical label, definition, note, example and notation without importing neighboring master lifecycles.

Preferred, alternative and hidden label, language, script, direction and uniqueness

Records preferred, alternative and hidden label, language, script, direction and uniqueness as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.

  1. Which scheme and concept identities, profile, scope, language, relation semantics and release establish preferred, alternative and hidden label, language, script, direction and uniqueness? classification
  2. Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses preferred, alternative and hidden label, language, script, direction and uniqueness, and under which authority? measurement
  3. Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify preferred, alternative and hidden label, language, script, direction and uniqueness? interoperability

Definition, scope note, example, history, change, editorial note, notation and code

Records definition, scope note, example, history, change, editorial note, notation and code as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.

  1. Which scheme and concept identities, profile, scope, language, relation semantics and release establish definition, scope note, example, history, change, editorial note, notation and code? definition
  2. Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses definition, scope note, example, history, change, editorial note, notation and code, and under which authority? evidence
  3. Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify definition, scope note, example, history, change, editorial note, notation and code? decision
Hierarchy, association, facets, collections and integrity Groups the governed Resource Consumption concern for hierarchy, association, facets, collections and integrity.

Broader, narrower, association, polyhierarchy and topology

Groups Resource Consumption context for broader, narrower, association, polyhierarchy and topology without importing neighboring master lifecycles.

Broader, narrower, generic, instance, partitive, top-concept and transitive closure

Records broader, narrower, generic, instance, partitive, top-concept and transitive closure as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.

  1. Which scheme and concept identities, profile, scope, language, relation semantics and release establish broader, narrower, generic, instance, partitive, top-concept and transitive closure? relationship
  2. Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses broader, narrower, generic, instance, partitive, top-concept and transitive closure, and under which authority? quality
  3. Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify broader, narrower, generic, instance, partitive, top-concept and transitive closure? identity

Related, see-also, direction, role, symmetry, polyhierarchy, cycle and orphan

Records related, see-also, direction, role, symmetry, polyhierarchy, cycle and orphan as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.

  1. Which scheme and concept identities, profile, scope, language, relation semantics and release establish related, see-also, direction, role, symmetry, polyhierarchy, cycle and orphan? relationship
  2. Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses related, see-also, direction, role, symmetry, polyhierarchy, cycle and orphan, and under which authority? validation
  3. Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify related, see-also, direction, role, symmetry, polyhierarchy, cycle and orphan? classification

Facets, arrays, collections, compounds and structural rules

Groups Resource Consumption context for facets, arrays, collections, compounds and structural rules without importing neighboring master lifecycles.

Facet, facet value, array, node label, guide term and systematic display

Records facet, facet value, array, node label, guide term and systematic display as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.

  1. Which scheme and concept identities, profile, scope, language, relation semantics and release establish facet, facet value, array, node label, guide term and systematic display? composition
  2. Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses facet, facet value, array, node label, guide term and systematic display, and under which authority? security
  3. Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify facet, facet value, array, node label, guide term and systematic display? composition

Collection, ordered collection, member list, compound concept and precoordination

Records collection, ordered collection, member list, compound concept and precoordination as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.

  1. Which scheme and concept identities, profile, scope, language, relation semantics and release establish collection, ordered collection, member list, compound concept and precoordination? composition
  2. Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses collection, ordered collection, member list, compound concept and precoordination, and under which authority? privacy
  3. Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify collection, ordered collection, member list, compound concept and precoordination? relationship
Mapping, alignment, method, confidence and dispute Groups the governed Resource Consumption concern for mapping, alignment, method, confidence and dispute.

Mapping relation, source, target, version and direction

Groups Resource Consumption context for mapping relation, source, target, version and direction without importing neighboring master lifecycles.

Exact, close, broad, narrow, related, equivalent, subclass and same-as distinction

Records exact, close, broad, narrow, related, equivalent, subclass and same-as distinction as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.

  1. Which scheme and concept identities, profile, scope, language, relation semantics and release establish exact, close, broad, narrow, related, equivalent, subclass and same-as distinction? interoperability
  2. Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses exact, close, broad, narrow, related, equivalent, subclass and same-as distinction, and under which authority? retention
  3. Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify exact, close, broad, narrow, related, equivalent, subclass and same-as distinction? state

Source concept, target concept, scheme version, direction, symmetry and transitivity

Records source concept, target concept, scheme version, direction, symmetry and transitivity as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.

  1. Which scheme and concept identities, profile, scope, language, relation semantics and release establish source concept, target concept, scheme version, direction, symmetry and transitivity? relationship
  2. Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses source concept, target concept, scheme version, direction, symmetry and transitivity, and under which authority? access
  3. Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify source concept, target concept, scheme version, direction, symmetry and transitivity? lifecycle

Mapping method, evidence, confidence, review and conflict

Groups Resource Consumption context for mapping method, evidence, confidence, review and conflict without importing neighboring master lifecycles.

Mapping method, actor, tool, date, rationale, evidence, confidence and quality

Records mapping method, actor, tool, date, rationale, evidence, confidence and quality as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.

  1. Which scheme and concept identities, profile, scope, language, relation semantics and release establish mapping method, actor, tool, date, rationale, evidence, confidence and quality? provenance
  2. Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses mapping method, actor, tool, date, rationale, evidence, confidence and quality, and under which authority? exception
  3. Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify mapping method, actor, tool, date, rationale, evidence, confidence and quality? temporal

Candidate, accepted, rejected, contested, superseded, conflict and resolution

Records candidate, accepted, rejected, contested, superseded, conflict and resolution as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.

  1. Which scheme and concept identities, profile, scope, language, relation semantics and release establish candidate, accepted, rejected, contested, superseded, conflict and resolution? state
  2. Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses candidate, accepted, rejected, contested, superseded, conflict and resolution, and under which authority? interoperability
  3. Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify candidate, accepted, rejected, contested, superseded, conflict and resolution? spatial
Governance, change, lifecycle, quality and validation Groups the governed Resource Consumption concern for governance, change, lifecycle, quality and validation.

Proposal, review, approval, change and retirement

Groups Resource Consumption context for proposal, review, approval, change and retirement without importing neighboring master lifecycles.

Draft, proposed, reviewed, approved, published, deprecated, superseded and retired state

Records draft, proposed, reviewed, approved, published, deprecated, superseded and retired state as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.

  1. Which scheme and concept identities, profile, scope, language, relation semantics and release establish draft, proposed, reviewed, approved, published, deprecated, superseded and retired state? lifecycle
  2. Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses draft, proposed, reviewed, approved, published, deprecated, superseded and retired state, and under which authority? decision
  3. Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify draft, proposed, reviewed, approved, published, deprecated, superseded and retired state? provenance

Change set, add, update, move, split, merge, replace, delete, rationale and impact

Records change set, add, update, move, split, merge, replace, delete, rationale and impact as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.

  1. Which scheme and concept identities, profile, scope, language, relation semantics and release establish change set, add, update, move, split, merge, replace, delete, rationale and impact? event
  2. Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses change set, add, update, move, split, merge, replace, delete, rationale and impact, and under which authority? identity
  3. Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify change set, add, update, move, split, merge, replace, delete, rationale and impact? ownership

Validation, quality, completeness, consistency and release gate

Groups Resource Consumption context for validation, quality, completeness, consistency and release gate without importing neighboring master lifecycles.

Identity, label, language, notation, domain, range, hierarchy, cycle and mapping check

Records identity, label, language, notation, domain, range, hierarchy, cycle and mapping check as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.

  1. Which scheme and concept identities, profile, scope, language, relation semantics and release establish identity, label, language, notation, domain, range, hierarchy, cycle and mapping check? validation
  2. Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses identity, label, language, notation, domain, range, hierarchy, cycle and mapping check, and under which authority? classification
  3. Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify identity, label, language, notation, domain, range, hierarchy, cycle and mapping check? authority

Coverage, completeness, freshness, consistency, accuracy, usability and release assurance

Records coverage, completeness, freshness, consistency, accuracy, usability and release assurance as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.

  1. Which scheme and concept identities, profile, scope, language, relation semantics and release establish coverage, completeness, freshness, consistency, accuracy, usability and release assurance? quality
  2. Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses coverage, completeness, freshness, consistency, accuracy, usability and release assurance, and under which authority? composition
  3. Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify coverage, completeness, freshness, consistency, accuracy, usability and release assurance? requirement
Access, license, retention, publication and interoperability Groups the governed Resource Consumption concern for access, license, retention, publication and interoperability.

Rights, access, sensitivity, retention and audit

Groups Resource Consumption context for rights, access, sensitivity, retention and audit without importing neighboring master lifecycles.

License, rights holder, attribution, purpose, role, sensitivity and minimum disclosure

Records license, rights holder, attribution, purpose, role, sensitivity and minimum disclosure as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.

  1. Which scheme and concept identities, profile, scope, language, relation semantics and release establish license, rights holder, attribution, purpose, role, sensitivity and minimum disclosure? access
  2. Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses license, rights holder, attribution, purpose, role, sensitivity and minimum disclosure, and under which authority? relationship
  3. Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify license, rights holder, attribution, purpose, role, sensitivity and minimum disclosure? constraint

Retention, legal hold, tombstone, withdrawal, audit and resolution continuity

Records retention, legal hold, tombstone, withdrawal, audit and resolution continuity as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.

  1. Which scheme and concept identities, profile, scope, language, relation semantics and release establish retention, legal hold, tombstone, withdrawal, audit and resolution continuity? retention
  2. Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses retention, legal hold, tombstone, withdrawal, audit and resolution continuity, and under which authority? state
  3. Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify retention, legal hold, tombstone, withdrawal, audit and resolution continuity? process

Serialization, profile, import, export and loss

Groups Resource Consumption context for serialization, profile, import, export and loss without importing neighboring master lifecycles.

SKOS, RDF, RDFS, OWL, JSON-LD, MADS, DCMI, DCAT, DataCite and RO-Crate projection

Records skos, rdf, rdfs, owl, json-ld, mads, dcmi, dcat, datacite and ro-crate projection as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.

  1. Which scheme and concept identities, profile, scope, language, relation semantics and release establish skos, rdf, rdfs, owl, json-ld, mads, dcmi, dcat, datacite and ro-crate projection? interoperability
  2. Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses skos, rdf, rdfs, owl, json-ld, mads, dcmi, dcat, datacite and ro-crate projection, and under which authority? lifecycle
  3. Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify skos, rdf, rdfs, owl, json-ld, mads, dcmi, dcat, datacite and ro-crate projection? event

Profile, version, context, shape, conformance, round trip, migration and semantic loss

Records profile, version, context, shape, conformance, round trip, migration and semantic loss as a source-qualified Taxonomy / Classification Scheme assertion while classified objects, classification bindings, source evidence, policies, datasets and indexes retain external mastership.

  1. Which scheme and concept identities, profile, scope, language, relation semantics and release establish profile, version, context, shape, conformance, round trip, migration and semantic loss? validation
  2. Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses profile, version, context, shape, conformance, round trip, migration and semantic loss, and under which authority? temporal
  3. Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify profile, version, context, shape, conformance, round trip, migration and semantic loss? measurement

Classifiers Filled

Family
World Models
Category
Information and virtual systems
Entry kind
aggregate
Navigation path
NAV.INF.KNW.TAX
Domain
INF.KNW.TAX
Industry
Cross-industry
Tags
taxonomyclassificationschemeinf.knw.tax

What it is Filled

Owns scheme identity, namespace, canonical URI, profile, purpose, scope, subject, audience, language, jurisdiction, owner, publisher and steward; immutable releases and change sets; concept identity, scheme membership and top concepts; labels, definitions, notes, examples and notations; broader, narrower and related relations; hierarchy profiles, polyhierarchy, facets, arrays, collections and ordered membership; cross-scheme mappings with versions, method, confidence and provenance; proposal, approval, publication, deprecation, replacement, split, merge and retirement; validation, quality, access, licensing, retention and loss-aware projections. Classified real-world objects, classification bindings, source evidence, policies, workflows, datasets and search indexes remain external.

In scope

  • Scheme identity, namespace, profile, scope, authority, release and concept membership
  • Labels, definitions, notations, hierarchy, association, facets, collections, mappings, lifecycle and validation
  • Provenance, governance, access, licensing, retention and interoperability

Out of scope

  • Owning classified objects, classification bindings, evidence, organization, policy, workflow, dataset or search-index lifecycles
  • Equating labels with identity, concepts with referents, broader with part-of, closeMatch with exactMatch, or mapping with proved equivalence
  • Executing release approval, object reassignment, protected disclosure, external system mutation or irreversible deletion without authority

Why it exists Filled

Represent one governed versioned knowledge-organization scheme containing concept definitions, labels, notations, semantic relations, mappings and release governance.

Distinguishing features Filled

  • Holds the scheme and its concepts, not the assignment of concepts to objects, which is the classification binding model.
  • A concept has a stable identifier; labels and codes are names for it and may change or repeat.
  • Broader and narrower express generality, not part-of; close match is weaker than exact match.
  • Differs from an ontology, which defines formal axioms, and from a schema, which defines data structure.

What robots and AI may and may not do Filled

Must not

  • Treat a label or code as the identity of a concept.
  • Publish or approve a scheme release.
  • Delete or redefine a concept that objects are still classified under.
  • Assert an exact match where only a close match is supported.
  • Reassign classified objects after a scheme change.

Only with a human decision

  • Approving a release or a namespace.
  • Splitting, merging or deprecating concepts in use.

May

  • Propose new concepts, labels and definitions for review.
  • Propose candidate mappings to other schemes with a match type.
  • Validate a scheme for cycles, orphan concepts and duplicate labels.
  • Publish read-only views of an approved release.

Moral aspects Filled

  • Categories describing people, such as ethnicity, disability or gender, can stigmatise and need careful wording.
  • Classifications decide access to services, statistics and funding, so errors affect real people.
  • Offering labels in only one language excludes communities that use others.

Who is affected

  • People and groups that the categories describe
  • Users and systems that classify with the scheme
  • Language communities
  • Scheme maintainers

Owners Filled

Steward

Declare the Dimension owner, scheme owner, publisher, vocabulary steward, concept editors, mapping reviewers, release approvers and access roles.

Roles

Dimension owner
Own namespace, mastership, delegation, access, retention and federation rules.
Scheme owner or publisher
Own purpose, scope, authority, releases, license and public commitments.
Vocabulary steward
Own scheme profile, concept model, relation semantics, lifecycle and editorial policy.
Concept editor or terminologist
Propose identifiers, definitions, labels, notations, notes and internal relations.
Mapping curator
Own mapping methods, evidence, confidence, review and conflict handling.
Release approver
Own change-set acceptance, validation gate, effective time and publication decision.
Consumer or classifier
Use pinned releases and keep external classification bindings in their owning model.
Reviewer or auditor
Review authority, quality, mappings, changes, access and retention without rewriting originals.

Links to other meta-models Filled

references

  • WM-XCT-020 Classification Binding - Resolve assignments of external objects to concepts while the registry parent direction remains under review.
  • Classified object, evidence, policy, dataset, distribution and search-index masters - Resolve external referents, sources, governance and delivery context without importing their lifecycles.

aligned

  • W3C SKOS Reference and Primer - Project concepts, schemes, labels, notations, notes, semantic relations, collections, mappings and integrity conditions.
  • RDF Schema 1.1, OWL 2 and JSON-LD 1.1 - Project linked-data classes, properties, axioms, annotations, contexts, language maps and graph serialization.
  • SHACL, PROV-O and DQV - Project validation, attribution, revision, invalidation and quality measurement semantics.
  • DCAT 3, DataCite 4.7 and RO-Crate 1.3 - Project catalog, distribution, persistent metadata and portable release packaging views.
  • ISO 25964 parts 1 and 2 - Project multilingual thesaurus construction, maintenance, exchange and cross-vocabulary mapping profiles.
  • ISO 704:2022, ISO 1087:2019 and NISO Z39.19 - Project terminology, concept, designation, definition and controlled-vocabulary management profiles.
  • DCMI Metadata Terms and Library of Congress MADS/RDF - Project vocabulary metadata, authority data, variants, schemes, collections and RWO separation.
  • BCP 47 language tags and matching - Project language-tag identity, validation, filtering and lookup for labels and notes.
  • ODRL 2.2, RFC 3339 and RFC 8785 - Project rights constraints, unambiguous clocks and deterministic JSON serialization.
  • ISO/IEC 11179-3:2023 - Project registry-item identification, designation, definition, registration, classification and mapping facilities.

neighbor

  • WM-XCT-020 Classification Binding - A classification binding assigns an external object to a concept in a pinned scheme release. The scheme defines that concept; the registry parent direction appears reversed or navigational and remains held for review.
  • Concept and real-world referent - A concept is a unit of thought or authority entry with its own URI. The person, place, product or other referent remains a separate mastered object.
  • Ontology and schema - OWL and RDFS can express formal class axioms while SHACL validates graphs. A taxonomy may project to them but does not inherit formal semantics unless the profile declares them.
  • Metadata registry - ISO/IEC 11179 defines generic registration, identification, designation, definition, classification and mapping facilities. This model specializes them for a knowledge-organization scheme.
  • Vocabulary distribution and dataset - DCAT, DataCite and RO-Crate distributions package or describe a release. They do not replace canonical scheme, concept or mapping identity.
  • Search index - An index may tokenize labels and materialize hierarchy for retrieval. Ranking, cache, deployment and query-log lifecycles remain external.
  • Mapping assessment - The scheme owns mapping assertions and their status, while evidence and reviewer decisions remain attributable external records. Mapping never silently merges concept identity.

parent

  • WM-XCT-020

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Authoritative master-system identifier for the scheme, concept, mapping, release or change assertion.
  • Governed globally resolvable scheme or concept IRI.
  • Adopting-Dimension UUID or ULID when no authoritative external identifier exists.

Direct properties not applicable Not applicable

Not applicable

Institutional or informational subject: no invented physical properties.

Recognition optional Filled

  • A scheme has a namespace, a set of concepts with identifiers, labels, definitions, hierarchical relations and versioned releases.
  • Often confused with an ontology, a code list, a glossary and a classification binding.

Capabilities and actions required Filled

  • Register scheme: Create stable scheme identity, namespace, profile, purpose, scope, owner and initial release.
  • Define concept: Create or revise one concept with stable identity, definition, characteristics and scheme membership.
  • Manage labels and notations: Append language-tagged preferred, alternative or hidden labels, notes and typed notations.
  • Relate concepts: Append typed broader, narrower, related or custom semantic relations with explicit hierarchy profile.
  • Manage facets and collections: Create facets, arrays, collections, ordered membership and compound structures without changing concept identity.
  • Map schemes: Append source-qualified cross-scheme mappings with exact semantics, versions, method and confidence.
  • Validate scheme: Run identity, lexical, structural, mapping, quality and profile checks against a pinned release.
  • Review and publish change: Review a proposal, append approval or rejection and issue an immutable release and change set.
  • Deprecate, split, merge or replace: Append deprecation and successor relations while retaining old identifiers and affected-binding impact.
  • Project scheme view: Produce an authorized version-pinned standards projection with declared loss and round-trip limits.

Hazards and failure modes required Filled

  • Breaking changes that orphan classified records.
  • Wrong mappings that merge distinct concepts.
  • Offensive or outdated terms remaining in use.
  • Identifiers reused for different meanings.

Standards and interfaces required Filled

  • W3C SKOS and SKOS-XL.
  • ISO 25964 thesauri and interoperability.
  • ANSI/NISO Z39.19 controlled vocabularies.
  • ISO 1087 terminology work.
  • W3C PROV-O for change provenance.

Context of use required Filled

  • ISO and NISO vocabulary standards, W3C linked-data vocabularies and Library of Congress authority data are complementary profiles rather than universal law.
  • Labels, definitions, preferred terms, mapping judgments and publication authority depend on language, community, discipline and jurisdiction.
  • ISO 25964 parts are under revision and licensed details require exact release pins before production conformance claims.

Sources Filled

  1. SKOS Simple Knowledge Organization System Reference - World Wide Web Consortium
  2. SKOS Simple Knowledge Organization System Primer - World Wide Web Consortium
  3. RDF Schema 1.1 - World Wide Web Consortium
  4. OWL 2 Web Ontology Language Structural Specification - World Wide Web Consortium
  5. JSON-LD 1.1 - World Wide Web Consortium
  6. Shapes Constraint Language - World Wide Web Consortium
  7. PROV-O: The PROV Ontology - World Wide Web Consortium
  8. Data Quality Vocabulary - World Wide Web Consortium
  9. Data Catalog Vocabulary Version 3 - World Wide Web Consortium
  10. Thesauri for information retrieval - International Organization for Standardization
  11. Interoperability with other vocabularies - International Organization for Standardization
  12. Terminology work principles and methods - International Organization for Standardization
  13. Terminology work and terminology science vocabulary - International Organization for Standardization
  14. Guidelines for Controlled Vocabularies - National Information Standards Organization
  15. DCMI Metadata Terms - Dublin Core Metadata Initiative
  16. MADS/RDF Documentation - Library of Congress
  17. Tags for Identifying Languages - Internet Engineering Task Force
  18. Matching of Language Tags - Internet Engineering Task Force
  19. DataCite Metadata Schema - DataCite
  20. RO-Crate Specification - RO-Crate Community
  21. ODRL Information Model 2.2 - World Wide Web Consortium
  22. Date and Time on the Internet - Internet Engineering Task Force
  23. JSON Canonicalization Scheme - Internet Engineering Task Force
  24. Metadata registries common facilities - International Organization for Standardization

Open questions

  • Resolve whether the WM-XCT-020 Classification Binding parent signal is navigational, reversed or should be replaced by an outbound reference from the binding to the scheme.
  • Develop domain-specific taxonomy, thesaurus, classification, ontology, multilingual, hierarchy, facet and mapping profiles.
  • Pin ISO 25964 replacements and every production crosswalk to exact releases and run bidirectional conformance, inference and semantic-loss tests.
  • Obtain independent terminology, library science, ontology, domain, accessibility, legal, privacy, security and records review.
  • Domain, language, jurisdiction, legal, safety, privacy, licensing, reasoning and retention profiles require expert review.
  • Classified objects, classification bindings, evidence, policies, datasets, search indexes and operational workflows remain neighboring masters.
  • Automatic concept induction, universal mapping, ontology theorem proving and silent reassignment after taxonomy change remain future work.

Machine files

Provenance

world-models research · reviewable-draft

Built from: models/wm-knw-018-taxonomy-classification-scheme/spec.yaml, ver-cy/world-models/card-supplements/wm-knw-018-taxonomy-classification-scheme.json