# Vercy AI instruction - YAML 1.2 (JSON-compatible) { "vercy": "1.0-draft", "publication": { "status": "published", "adjudicationStatus": "reviewable-draft", "publishableCanonical": false, "generatedAt": "2026-09-07T09:22:01Z", "synthesisSha256": "416e453789412773cfb3b0f2a163aea354d36473928dd6231b844f6f84a36433", "providerMode": "single-provider-waiver", "providers": [ "Codex" ], "waivedProviders": [ "Claude", "Grok" ] }, "metaModel": { "id": "WM-KNW-018", "registryId": "vr.wm-knw-018", "name": "Taxonomy / Classification Scheme", "version": "0.3.0-research.1", "previousVersions": [], "entryKind": "aggregate", "family": "World Models", "category": "Information and virtual systems", "industry": [ "Cross-industry" ], "domain": [ "INF.KNW.TAX" ], "tags": [ "taxonomy", "classification", "scheme", "inf.knw.tax" ], "status": "published" }, "canonicalUrl": "https://ver.cy/models/wm-knw-018-taxonomy-classification-scheme/", "sourceUrl": "https://github.com/ver-cy/world-models/tree/feat/mega-model-registry/research/runs/wm-knw-018", "model": { "registry_id": "vr.wm-knw-018", "model_id": "WM-KNW-018", "name": "Taxonomy / Classification Scheme", "entry_kind": "aggregate", "purpose": "Represent one governed versioned knowledge-organization scheme containing concept definitions, labels, notations, semantic relations, mappings and release governance.", "scope_statement": "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" ], "boundary_notes": [ { "neighbor": "WM-XCT-020 Classification Binding", "distinction": "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.", "source_refs": [ "SRC-001", "SRC-011", "SRC-015", "SRC-024" ] }, { "neighbor": "Concept and real-world referent", "distinction": "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.", "source_refs": [ "SRC-001", "SRC-012", "SRC-013", "SRC-016" ] }, { "neighbor": "Ontology and schema", "distinction": "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.", "source_refs": [ "SRC-003", "SRC-004", "SRC-006" ] }, { "neighbor": "Metadata registry", "distinction": "ISO/IEC 11179 defines generic registration, identification, designation, definition, classification and mapping facilities. This model specializes them for a knowledge-organization scheme.", "source_refs": [ "SRC-024" ] }, { "neighbor": "Vocabulary distribution and dataset", "distinction": "DCAT, DataCite and RO-Crate distributions package or describe a release. They do not replace canonical scheme, concept or mapping identity.", "source_refs": [ "SRC-009", "SRC-019", "SRC-020" ] }, { "neighbor": "Search index", "distinction": "An index may tokenize labels and materialize hierarchy for retrieval. Ranking, cache, deployment and query-log lifecycles remain external.", "source_refs": [ "SRC-010", "SRC-014" ] }, { "neighbor": "Mapping assessment", "distinction": "The scheme owns mapping assertions and their status, while evidence and reviewer decisions remain attributable external records. Mapping never silently merges concept identity.", "source_refs": [ "SRC-001", "SRC-002", "SRC-007", "SRC-008", "SRC-011" ] } ] }, "sources": [ { "id": "SRC-001", "title": "SKOS Simple Knowledge Organization System Reference", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/skos-reference/", "version_or_date": "W3C Recommendation, 18 August 2009", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:29:00Z", "relevance": "Defines concepts, schemes, labels, notations, notes, semantic relations, collections, mappings and integrity conditions." }, { "id": "SRC-002", "title": "SKOS Simple Knowledge Organization System Primer", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/skos-primer/", "version_or_date": "W3C Working Group Note, 18 August 2009", "source_type": "first-party-doc", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:29:00Z", "relevance": "Explains scheme construction, multilingual labels, hierarchy, collections and mapping behavior." }, { "id": "SRC-003", "title": "RDF Schema 1.1", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/rdf-schema/", "version_or_date": "W3C Recommendation, 25 February 2014", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:29:00Z", "relevance": "Defines classes, properties, subclass, subproperty, domain, range, labels and comments." }, { "id": "SRC-004", "title": "OWL 2 Web Ontology Language Structural Specification", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/owl2-syntax/", "version_or_date": "W3C Recommendation, 11 December 2012", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:29:00Z", "relevance": "Defines ontology identity, imports, version IRIs, classes, axioms, annotations and formal equivalence." }, { "id": "SRC-005", "title": "JSON-LD 1.1", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/json-ld11/", "version_or_date": "W3C Recommendation, 16 July 2020", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:29:00Z", "relevance": "Defines JSON serialization of linked data, contexts, IRIs, typed values, language maps and containers." }, { "id": "SRC-006", "title": "Shapes Constraint Language", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/shacl/", "version_or_date": "W3C Recommendation, 20 July 2017", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:29:00Z", "relevance": "Defines graph constraints, targets, severity, validation results and reports." }, { "id": "SRC-007", "title": "PROV-O: The PROV Ontology", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/prov-o/", "version_or_date": "W3C Recommendation, 30 April 2013", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:29:00Z", "relevance": "Defines entities, activities, agents, attribution, derivation, revision and invalidation." }, { "id": "SRC-008", "title": "Data Quality Vocabulary", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/vocab-dqv/", "version_or_date": "W3C Working Group Note, 15 December 2016", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:29:00Z", "relevance": "Defines quality measurements, annotations, policies, standards and provenance." }, { "id": "SRC-009", "title": "Data Catalog Vocabulary Version 3", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/vocab-dcat-3/", "version_or_date": "W3C Recommendation, 22 August 2024", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:29:00Z", "relevance": "Defines catalog resources, datasets, distributions, versioning, relations, access and rights metadata." }, { "id": "SRC-010", "title": "Thesauri for information retrieval", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/53657.html", "version_or_date": "ISO 25964-1:2011, confirmed 2022; replacement pending", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:29:00Z", "relevance": "Defines monolingual and multilingual thesaurus development, maintenance, data model and exchange." }, { "id": "SRC-011", "title": "Interoperability with other vocabularies", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/53658.html", "version_or_date": "ISO 25964-2:2013, confirmed 2023; revision initiated 2026", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:29:00Z", "relevance": "Compares vocabulary types and governs mappings among thesauri and other vocabularies." }, { "id": "SRC-012", "title": "Terminology work principles and methods", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/79077.html", "version_or_date": "ISO 704:2022", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:29:00Z", "relevance": "Defines relations among objects, concepts, characteristics, definitions and designations." }, { "id": "SRC-013", "title": "Terminology work and terminology science vocabulary", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/62330.html", "version_or_date": "ISO 1087:2019, confirmed 2025", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:29:00Z", "relevance": "Defines core terminology-work and terminology-science concepts." }, { "id": "SRC-014", "title": "Guidelines for Controlled Vocabularies", "organization": "National Information Standards Organization", "url": "https://www.niso.org/publications/ansiniso-z3919-2005-r2010", "version_or_date": "ANSI/NISO Z39.19-2005 R2010", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:29:00Z", "relevance": "Defines construction, format, testing, maintenance and management of lists, synonym rings, taxonomies and thesauri." }, { "id": "SRC-015", "title": "DCMI Metadata Terms", "organization": "Dublin Core Metadata Initiative", "url": "https://www.dublincore.org/specifications/dublin-core/dcmi-terms/", "version_or_date": "DCMI Recommendation, issued 20 January 2020", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:29:00Z", "relevance": "Defines identifiers, titles, language, rights, versions, relations and vocabulary encoding schemes." }, { "id": "SRC-016", "title": "MADS/RDF Documentation", "organization": "Library of Congress", "url": "https://www.loc.gov/standards/mads/rdf/", "version_or_date": "Published update, 28 October 2015", "source_type": "ontology", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:29:00Z", "relevance": "Defines authority data, variants, schemes, collections, hierarchy, mappings and separation from real-world objects." }, { "id": "SRC-017", "title": "Tags for Identifying Languages", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc5646.html", "version_or_date": "RFC 5646 and BCP 47, September 2009", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:29:00Z", "relevance": "Defines language tags and the maintained IANA language-subtag registry." }, { "id": "SRC-018", "title": "Matching of Language Tags", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc4647.html", "version_or_date": "RFC 4647 and BCP 47, September 2006", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:29:00Z", "relevance": "Defines basic and extended filtering plus language-tag lookup semantics." }, { "id": "SRC-019", "title": "DataCite Metadata Schema", "organization": "DataCite", "url": "https://schema.datacite.org/", "version_or_date": "DataCite Metadata Schema 4.7, 3 March 2026", "source_type": "schema", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:29:00Z", "relevance": "Defines persistent resource metadata, versions, relations, subjects, rights and controlled values." }, { "id": "SRC-020", "title": "RO-Crate Specification", "organization": "RO-Crate Community", "url": "https://www.researchobject.org/ro-crate/specification.html", "version_or_date": "RO-Crate 1.3, current long-term release", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:29:00Z", "relevance": "Defines portable aggregation, contextual entities, actions, provenance and profiles." }, { "id": "SRC-021", "title": "ODRL Information Model 2.2", "organization": "World Wide Web Consortium", "url": "https://www.w3.org/TR/odrl-model/", "version_or_date": "W3C Recommendation, 15 February 2018", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:29:00Z", "relevance": "Defines permissions, prohibitions, duties, constraints and policy parties for governed use." }, { "id": "SRC-022", "title": "Date and Time on the Internet", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc3339.html", "version_or_date": "RFC 3339, July 2002", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:29:00Z", "relevance": "Defines timestamps with seconds and explicit numeric offsets or Z." }, { "id": "SRC-023", "title": "JSON Canonicalization Scheme", "organization": "Internet Engineering Task Force", "url": "https://www.rfc-editor.org/rfc/rfc8785.html", "version_or_date": "RFC 8785, June 2020", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:29:00Z", "relevance": "Defines deterministic JSON canonicalization for hashing and signing." }, { "id": "SRC-024", "title": "Metadata registries common facilities", "organization": "International Organization for Standardization", "url": "https://www.iso.org/standard/78915.html", "version_or_date": "ISO/IEC 11179-3:2023", "source_type": "standard", "primary_source": true, "authority_tier": 1, "accessed_at": "2026-09-07T09:29:00Z", "relevance": "Defines registry items, identification, designation, definition, registration, classification and mapping metamodels." } ], "structure": { "bundles": [ { "id": "scheme-identity-profile-scope-and-release", "name": "Scheme identity, profile, scope and release", "description": "Groups the governed Resource Consumption concern for scheme identity, profile, scope and release.", "rationale": "Establish one authoritative scheme and the boundary of each immutable release.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-009", "SRC-015", "SRC-019", "SRC-020", "SRC-022", "SRC-023", "SRC-024", "SRC-002", "SRC-010", "SRC-011", "SRC-014", "SRC-017", "SRC-018" ], "layers": [ { "id": "identity-namespace-version-and-distribution", "name": "Identity, namespace, version and distribution", "description": "Groups Resource Consumption context for identity, namespace, version and distribution without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-009", "SRC-015", "SRC-019", "SRC-020", "SRC-022", "SRC-023", "SRC-024" ], "findings": [ { "id": "scheme-identifier-canonical-uri-namespace-prefix-and-local-id-policy", "name": "Scheme identifier, canonical URI, namespace, prefix and local-ID policy", "description": "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.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-009", "SRC-015", "SRC-019", "SRC-020", "SRC-022", "SRC-023", "SRC-024" ], "questions": [ { "id": "scheme-identifier-canonical-uri-namespace-prefix-and-local-id-policy-q01", "text": "Which scheme and concept identities, profile, scope, language, relation semantics and release establish scheme identifier, canonical uri, namespace, prefix and local-id policy?", "kind": "identity", "answer_data": [ "scheme identifier, namespace, profile, version, release and status", "concept URI, local identifier, labels, definition, notation, membership and relation type", "subject scope, audience, language, jurisdiction, effective period and exclusions" ] }, { "id": "scheme-identifier-canonical-uri-namespace-prefix-and-local-id-policy-q02", "text": "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?", "kind": "ownership", "answer_data": [ "owner, publisher, scheme steward, concept editor, mapper, reviewer and approver roles", "mandate, source, editorial policy, proposal, review, approval, dispute and change authority", "source system, license, purpose, access, retention and audit basis" ] }, { "id": "scheme-identifier-canonical-uri-namespace-prefix-and-local-id-policy-q03", "text": "Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify scheme identifier, canonical uri, namespace, prefix and local-id policy?", "kind": "validation", "answer_data": [ "definition, note, broader, narrower, related, collection, facet and topology", "mapping source and target versions, method, confidence, evidence, reviewer and conflict", "validation result, change set, predecessor, successor, projection profile and semantic-loss declaration" ] } ], "data_elements": [ { "id": "scheme-identifier-canonical-uri-namespace-prefix-and-local-id-policy-data", "name": "Scheme identifier, canonical URI, namespace, prefix and local-ID policy data", "description": "Typed scheme-scoped values and references required to answer the governed questions for scheme identifier, canonical uri, namespace, prefix and local-id policy.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-009", "SRC-015", "SRC-019", "SRC-020", "SRC-022", "SRC-023", "SRC-024" ] } ], "artifacts": [ { "id": "scheme-identifier-canonical-uri-namespace-prefix-and-local-id-policy-artifact", "name": "Scheme identifier, canonical URI, namespace, prefix and local-ID policy evidence manifest", "description": "Digest-addressed manifest of concepts, labels, definitions, relations, mappings, validation, changes and provenance supporting scheme identifier, canonical uri, namespace, prefix and local-id policy.", "media_or_form": [ "application/ld+json", "text/turtle", "application/rdf+xml", "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative vocabulary or registry identifier first, otherwise governed concept-scheme IRI, then Dimension UUID or ULID; include immutable release or assertion revision and digest.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-009", "SRC-015", "SRC-019", "SRC-020", "SRC-022", "SRC-023", "SRC-024" ] } ], "inline_only_rationale": null }, { "id": "version-edition-release-status-date-predecessor-successor-and-distribution", "name": "Version, edition, release status, date, predecessor, successor and distribution", "description": "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.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-009", "SRC-015", "SRC-019", "SRC-020", "SRC-022", "SRC-023", "SRC-024" ], "questions": [ { "id": "version-edition-release-status-date-predecessor-successor-and-distribution-q01", "text": "Which scheme and concept identities, profile, scope, language, relation semantics and release establish version, edition, release status, date, predecessor, successor and distribution?", "kind": "lifecycle", "answer_data": [ "scheme identifier, namespace, profile, version, release and status", "concept URI, local identifier, labels, definition, notation, membership and relation type", "subject scope, audience, language, jurisdiction, effective period and exclusions" ] }, { "id": "version-edition-release-status-date-predecessor-successor-and-distribution-q02", "text": "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?", "kind": "authority", "answer_data": [ "owner, publisher, scheme steward, concept editor, mapper, reviewer and approver roles", "mandate, source, editorial policy, proposal, review, approval, dispute and change authority", "source system, license, purpose, access, retention and audit basis" ] }, { "id": "version-edition-release-status-date-predecessor-successor-and-distribution-q03", "text": "Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify version, edition, release status, date, predecessor, successor and distribution?", "kind": "security", "answer_data": [ "definition, note, broader, narrower, related, collection, facet and topology", "mapping source and target versions, method, confidence, evidence, reviewer and conflict", "validation result, change set, predecessor, successor, projection profile and semantic-loss declaration" ] } ], "data_elements": [ { "id": "version-edition-release-status-date-predecessor-successor-and-distribution-data", "name": "Version, edition, release status, date, predecessor, successor and distribution data", "description": "Typed scheme-scoped values and references required to answer the governed questions for version, edition, release status, date, predecessor, successor and distribution.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-009", "SRC-015", "SRC-019", "SRC-020", "SRC-022", "SRC-023", "SRC-024" ] } ], "artifacts": [ { "id": "version-edition-release-status-date-predecessor-successor-and-distribution-artifact", "name": "Version, edition, release status, date, predecessor, successor and distribution evidence manifest", "description": "Digest-addressed manifest of concepts, labels, definitions, relations, mappings, validation, changes and provenance supporting version, edition, release status, date, predecessor, successor and distribution.", "media_or_form": [ "application/ld+json", "text/turtle", "application/rdf+xml", "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative vocabulary or registry identifier first, otherwise governed concept-scheme IRI, then Dimension UUID or ULID; include immutable release or assertion revision and digest.", "source_refs": [ "SRC-001", "SRC-004", "SRC-005", "SRC-009", "SRC-015", "SRC-019", "SRC-020", "SRC-022", "SRC-023", "SRC-024" ] } ], "inline_only_rationale": null } ] }, { "id": "scheme-kind-purpose-scope-audience-language-and-authority", "name": "Scheme kind, purpose, scope, audience, language and authority", "description": "Groups Resource Consumption context for scheme kind, purpose, scope, audience, language and authority without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-009", "SRC-010", "SRC-011", "SRC-014", "SRC-015", "SRC-017", "SRC-018", "SRC-024" ], "findings": [ { "id": "taxonomy-thesaurus-classification-list-synonym-ring-ontology-and-hybrid-profile", "name": "Taxonomy, thesaurus, classification, list, synonym-ring, ontology and hybrid profile", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-009", "SRC-010", "SRC-011", "SRC-014", "SRC-015", "SRC-017", "SRC-018", "SRC-024" ], "questions": [ { "id": "taxonomy-thesaurus-classification-list-synonym-ring-ontology-and-hybrid-profile-q01", "text": "Which scheme and concept identities, profile, scope, language, relation semantics and release establish taxonomy, thesaurus, classification, list, synonym-ring, ontology and hybrid profile?", "kind": "classification", "answer_data": [ "scheme identifier, namespace, profile, version, release and status", "concept URI, local identifier, labels, definition, notation, membership and relation type", "subject scope, audience, language, jurisdiction, effective period and exclusions" ] }, { "id": "taxonomy-thesaurus-classification-list-synonym-ring-ontology-and-hybrid-profile-q02", "text": "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?", "kind": "requirement", "answer_data": [ "owner, publisher, scheme steward, concept editor, mapper, reviewer and approver roles", "mandate, source, editorial policy, proposal, review, approval, dispute and change authority", "source system, license, purpose, access, retention and audit basis" ] }, { "id": "taxonomy-thesaurus-classification-list-synonym-ring-ontology-and-hybrid-profile-q03", "text": "Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify taxonomy, thesaurus, classification, list, synonym-ring, ontology and hybrid profile?", "kind": "privacy", "answer_data": [ "definition, note, broader, narrower, related, collection, facet and topology", "mapping source and target versions, method, confidence, evidence, reviewer and conflict", "validation result, change set, predecessor, successor, projection profile and semantic-loss declaration" ] } ], "data_elements": [ { "id": "taxonomy-thesaurus-classification-list-synonym-ring-ontology-and-hybrid-profile-data", "name": "Taxonomy, thesaurus, classification, list, synonym-ring, ontology and hybrid profile data", "description": "Typed scheme-scoped values and references required to answer the governed questions for taxonomy, thesaurus, classification, list, synonym-ring, ontology and hybrid profile.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-009", "SRC-010", "SRC-011", "SRC-014", "SRC-015", "SRC-017", "SRC-018", "SRC-024" ] } ], "artifacts": [ { "id": "taxonomy-thesaurus-classification-list-synonym-ring-ontology-and-hybrid-profile-artifact", "name": "Taxonomy, thesaurus, classification, list, synonym-ring, ontology and hybrid profile evidence manifest", "description": "Digest-addressed manifest of concepts, labels, definitions, relations, mappings, validation, changes and provenance supporting taxonomy, thesaurus, classification, list, synonym-ring, ontology and hybrid profile.", "media_or_form": [ "application/ld+json", "text/turtle", "application/rdf+xml", "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative vocabulary or registry identifier first, otherwise governed concept-scheme IRI, then Dimension UUID or ULID; include immutable release or assertion revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-009", "SRC-010", "SRC-011", "SRC-014", "SRC-015", "SRC-017", "SRC-018", "SRC-024" ] } ], "inline_only_rationale": null }, { "id": "purpose-subject-scope-audience-language-jurisdiction-owner-publisher-and-steward", "name": "Purpose, subject, scope, audience, language, jurisdiction, owner, publisher and steward", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-009", "SRC-010", "SRC-011", "SRC-014", "SRC-015", "SRC-017", "SRC-018", "SRC-024" ], "questions": [ { "id": "purpose-subject-scope-audience-language-jurisdiction-owner-publisher-and-steward-q01", "text": "Which scheme and concept identities, profile, scope, language, relation semantics and release establish purpose, subject, scope, audience, language, jurisdiction, owner, publisher and steward?", "kind": "authority", "answer_data": [ "scheme identifier, namespace, profile, version, release and status", "concept URI, local identifier, labels, definition, notation, membership and relation type", "subject scope, audience, language, jurisdiction, effective period and exclusions" ] }, { "id": "purpose-subject-scope-audience-language-jurisdiction-owner-publisher-and-steward-q02", "text": "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?", "kind": "constraint", "answer_data": [ "owner, publisher, scheme steward, concept editor, mapper, reviewer and approver roles", "mandate, source, editorial policy, proposal, review, approval, dispute and change authority", "source system, license, purpose, access, retention and audit basis" ] }, { "id": "purpose-subject-scope-audience-language-jurisdiction-owner-publisher-and-steward-q03", "text": "Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify purpose, subject, scope, audience, language, jurisdiction, owner, publisher and steward?", "kind": "retention", "answer_data": [ "definition, note, broader, narrower, related, collection, facet and topology", "mapping source and target versions, method, confidence, evidence, reviewer and conflict", "validation result, change set, predecessor, successor, projection profile and semantic-loss declaration" ] } ], "data_elements": [ { "id": "purpose-subject-scope-audience-language-jurisdiction-owner-publisher-and-steward-data", "name": "Purpose, subject, scope, audience, language, jurisdiction, owner, publisher and steward data", "description": "Typed scheme-scoped values and references required to answer the governed questions for purpose, subject, scope, audience, language, jurisdiction, owner, publisher and steward.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-009", "SRC-010", "SRC-011", "SRC-014", "SRC-015", "SRC-017", "SRC-018", "SRC-024" ] } ], "artifacts": [ { "id": "purpose-subject-scope-audience-language-jurisdiction-owner-publisher-and-steward-artifact", "name": "Purpose, subject, scope, audience, language, jurisdiction, owner, publisher and steward evidence manifest", "description": "Digest-addressed manifest of concepts, labels, definitions, relations, mappings, validation, changes and provenance supporting purpose, subject, scope, audience, language, jurisdiction, owner, publisher and steward.", "media_or_form": [ "application/ld+json", "text/turtle", "application/rdf+xml", "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative vocabulary or registry identifier first, otherwise governed concept-scheme IRI, then Dimension UUID or ULID; include immutable release or assertion revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-009", "SRC-010", "SRC-011", "SRC-014", "SRC-015", "SRC-017", "SRC-018", "SRC-024" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "concepts-labels-definitions-notations-and-notes", "name": "Concepts, labels, definitions, notations and notes", "description": "Groups the governed Resource Consumption concern for concepts, labels, definitions, notations and notes.", "rationale": "Represent concept meaning independently from labels, codes and real-world referents.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-012", "SRC-013", "SRC-015", "SRC-016", "SRC-024", "SRC-002", "SRC-005", "SRC-010", "SRC-014", "SRC-017", "SRC-018" ], "layers": [ { "id": "concept-identity-membership-type-and-referent-boundary", "name": "Concept identity, membership, type and referent boundary", "description": "Groups Resource Consumption context for concept identity, membership, type and referent boundary without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-012", "SRC-013", "SRC-015", "SRC-016", "SRC-024" ], "findings": [ { "id": "concept-uri-local-identifier-in-scheme-top-concept-and-concept-type", "name": "Concept URI, local identifier, in-scheme, top concept and concept type", "description": "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.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-012", "SRC-013", "SRC-015", "SRC-016", "SRC-024" ], "questions": [ { "id": "concept-uri-local-identifier-in-scheme-top-concept-and-concept-type-q01", "text": "Which scheme and concept identities, profile, scope, language, relation semantics and release establish concept uri, local identifier, in-scheme, top concept and concept type?", "kind": "identity", "answer_data": [ "scheme identifier, namespace, profile, version, release and status", "concept URI, local identifier, labels, definition, notation, membership and relation type", "subject scope, audience, language, jurisdiction, effective period and exclusions" ] }, { "id": "concept-uri-local-identifier-in-scheme-top-concept-and-concept-type-q02", "text": "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?", "kind": "process", "answer_data": [ "owner, publisher, scheme steward, concept editor, mapper, reviewer and approver roles", "mandate, source, editorial policy, proposal, review, approval, dispute and change authority", "source system, license, purpose, access, retention and audit basis" ] }, { "id": "concept-uri-local-identifier-in-scheme-top-concept-and-concept-type-q03", "text": "Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify concept uri, local identifier, in-scheme, top concept and concept type?", "kind": "access", "answer_data": [ "definition, note, broader, narrower, related, collection, facet and topology", "mapping source and target versions, method, confidence, evidence, reviewer and conflict", "validation result, change set, predecessor, successor, projection profile and semantic-loss declaration" ] } ], "data_elements": [ { "id": "concept-uri-local-identifier-in-scheme-top-concept-and-concept-type-data", "name": "Concept URI, local identifier, in-scheme, top concept and concept type data", "description": "Typed scheme-scoped values and references required to answer the governed questions for concept uri, local identifier, in-scheme, top concept and concept type.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-012", "SRC-013", "SRC-015", "SRC-016", "SRC-024" ] } ], "artifacts": [ { "id": "concept-uri-local-identifier-in-scheme-top-concept-and-concept-type-artifact", "name": "Concept URI, local identifier, in-scheme, top concept and concept type evidence manifest", "description": "Digest-addressed manifest of concepts, labels, definitions, relations, mappings, validation, changes and provenance supporting concept uri, local identifier, in-scheme, top concept and concept type.", "media_or_form": [ "application/ld+json", "text/turtle", "application/rdf+xml", "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative vocabulary or registry identifier first, otherwise governed concept-scheme IRI, then Dimension UUID or ULID; include immutable release or assertion revision and digest.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-012", "SRC-013", "SRC-015", "SRC-016", "SRC-024" ] } ], "inline_only_rationale": null }, { "id": "concept-characteristics-extension-intension-referent-authority-and-rwo-distinction", "name": "Concept characteristics, extension, intension, referent, authority and RWO distinction", "description": "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.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-012", "SRC-013", "SRC-015", "SRC-016", "SRC-024" ], "questions": [ { "id": "concept-characteristics-extension-intension-referent-authority-and-rwo-distinction-q01", "text": "Which scheme and concept identities, profile, scope, language, relation semantics and release establish concept characteristics, extension, intension, referent, authority and rwo distinction?", "kind": "definition", "answer_data": [ "scheme identifier, namespace, profile, version, release and status", "concept URI, local identifier, labels, definition, notation, membership and relation type", "subject scope, audience, language, jurisdiction, effective period and exclusions" ] }, { "id": "concept-characteristics-extension-intension-referent-authority-and-rwo-distinction-q02", "text": "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?", "kind": "event", "answer_data": [ "owner, publisher, scheme steward, concept editor, mapper, reviewer and approver roles", "mandate, source, editorial policy, proposal, review, approval, dispute and change authority", "source system, license, purpose, access, retention and audit basis" ] }, { "id": "concept-characteristics-extension-intension-referent-authority-and-rwo-distinction-q03", "text": "Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify concept characteristics, extension, intension, referent, authority and rwo distinction?", "kind": "exception", "answer_data": [ "definition, note, broader, narrower, related, collection, facet and topology", "mapping source and target versions, method, confidence, evidence, reviewer and conflict", "validation result, change set, predecessor, successor, projection profile and semantic-loss declaration" ] } ], "data_elements": [ { "id": "concept-characteristics-extension-intension-referent-authority-and-rwo-distinction-data", "name": "Concept characteristics, extension, intension, referent, authority and RWO distinction data", "description": "Typed scheme-scoped values and references required to answer the governed questions for concept characteristics, extension, intension, referent, authority and rwo distinction.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-012", "SRC-013", "SRC-015", "SRC-016", "SRC-024" ] } ], "artifacts": [ { "id": "concept-characteristics-extension-intension-referent-authority-and-rwo-distinction-artifact", "name": "Concept characteristics, extension, intension, referent, authority and RWO distinction evidence manifest", "description": "Digest-addressed manifest of concepts, labels, definitions, relations, mappings, validation, changes and provenance supporting concept characteristics, extension, intension, referent, authority and rwo distinction.", "media_or_form": [ "application/ld+json", "text/turtle", "application/rdf+xml", "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative vocabulary or registry identifier first, otherwise governed concept-scheme IRI, then Dimension UUID or ULID; include immutable release or assertion revision and digest.", "source_refs": [ "SRC-001", "SRC-003", "SRC-004", "SRC-012", "SRC-013", "SRC-015", "SRC-016", "SRC-024" ] } ], "inline_only_rationale": null } ] }, { "id": "lexical-label-definition-note-example-and-notation", "name": "Lexical label, definition, note, example and notation", "description": "Groups Resource Consumption context for lexical label, definition, note, example and notation without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-010", "SRC-012", "SRC-013", "SRC-014", "SRC-016", "SRC-017", "SRC-018" ], "findings": [ { "id": "preferred-alternative-hidden-label-language-script-direction-and-uniqueness", "name": "Preferred, alternative and hidden label, language, script, direction and uniqueness", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-010", "SRC-012", "SRC-013", "SRC-014", "SRC-016", "SRC-017", "SRC-018" ], "questions": [ { "id": "preferred-alternative-hidden-label-language-script-direction-and-uniqueness-q01", "text": "Which scheme and concept identities, profile, scope, language, relation semantics and release establish preferred, alternative and hidden label, language, script, direction and uniqueness?", "kind": "classification", "answer_data": [ "scheme identifier, namespace, profile, version, release and status", "concept URI, local identifier, labels, definition, notation, membership and relation type", "subject scope, audience, language, jurisdiction, effective period and exclusions" ] }, { "id": "preferred-alternative-hidden-label-language-script-direction-and-uniqueness-q02", "text": "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?", "kind": "measurement", "answer_data": [ "owner, publisher, scheme steward, concept editor, mapper, reviewer and approver roles", "mandate, source, editorial policy, proposal, review, approval, dispute and change authority", "source system, license, purpose, access, retention and audit basis" ] }, { "id": "preferred-alternative-hidden-label-language-script-direction-and-uniqueness-q03", "text": "Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify preferred, alternative and hidden label, language, script, direction and uniqueness?", "kind": "interoperability", "answer_data": [ "definition, note, broader, narrower, related, collection, facet and topology", "mapping source and target versions, method, confidence, evidence, reviewer and conflict", "validation result, change set, predecessor, successor, projection profile and semantic-loss declaration" ] } ], "data_elements": [ { "id": "preferred-alternative-hidden-label-language-script-direction-and-uniqueness-data", "name": "Preferred, alternative and hidden label, language, script, direction and uniqueness data", "description": "Typed scheme-scoped values and references required to answer the governed questions for preferred, alternative and hidden label, language, script, direction and uniqueness.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-010", "SRC-012", "SRC-013", "SRC-014", "SRC-016", "SRC-017", "SRC-018" ] } ], "artifacts": [ { "id": "preferred-alternative-hidden-label-language-script-direction-and-uniqueness-artifact", "name": "Preferred, alternative and hidden label, language, script, direction and uniqueness evidence manifest", "description": "Digest-addressed manifest of concepts, labels, definitions, relations, mappings, validation, changes and provenance supporting preferred, alternative and hidden label, language, script, direction and uniqueness.", "media_or_form": [ "application/ld+json", "text/turtle", "application/rdf+xml", "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative vocabulary or registry identifier first, otherwise governed concept-scheme IRI, then Dimension UUID or ULID; include immutable release or assertion revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-010", "SRC-012", "SRC-013", "SRC-014", "SRC-016", "SRC-017", "SRC-018" ] } ], "inline_only_rationale": null }, { "id": "definition-scope-note-example-history-change-editorial-note-notation-and-code", "name": "Definition, scope note, example, history, change, editorial note, notation and code", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-010", "SRC-012", "SRC-013", "SRC-014", "SRC-016", "SRC-017", "SRC-018" ], "questions": [ { "id": "definition-scope-note-example-history-change-editorial-note-notation-and-code-q01", "text": "Which scheme and concept identities, profile, scope, language, relation semantics and release establish definition, scope note, example, history, change, editorial note, notation and code?", "kind": "definition", "answer_data": [ "scheme identifier, namespace, profile, version, release and status", "concept URI, local identifier, labels, definition, notation, membership and relation type", "subject scope, audience, language, jurisdiction, effective period and exclusions" ] }, { "id": "definition-scope-note-example-history-change-editorial-note-notation-and-code-q02", "text": "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?", "kind": "evidence", "answer_data": [ "owner, publisher, scheme steward, concept editor, mapper, reviewer and approver roles", "mandate, source, editorial policy, proposal, review, approval, dispute and change authority", "source system, license, purpose, access, retention and audit basis" ] }, { "id": "definition-scope-note-example-history-change-editorial-note-notation-and-code-q03", "text": "Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify definition, scope note, example, history, change, editorial note, notation and code?", "kind": "decision", "answer_data": [ "definition, note, broader, narrower, related, collection, facet and topology", "mapping source and target versions, method, confidence, evidence, reviewer and conflict", "validation result, change set, predecessor, successor, projection profile and semantic-loss declaration" ] } ], "data_elements": [ { "id": "definition-scope-note-example-history-change-editorial-note-notation-and-code-data", "name": "Definition, scope note, example, history, change, editorial note, notation and code data", "description": "Typed scheme-scoped values and references required to answer the governed questions for definition, scope note, example, history, change, editorial note, notation and code.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-010", "SRC-012", "SRC-013", "SRC-014", "SRC-016", "SRC-017", "SRC-018" ] } ], "artifacts": [ { "id": "definition-scope-note-example-history-change-editorial-note-notation-and-code-artifact", "name": "Definition, scope note, example, history, change, editorial note, notation and code evidence manifest", "description": "Digest-addressed manifest of concepts, labels, definitions, relations, mappings, validation, changes and provenance supporting definition, scope note, example, history, change, editorial note, notation and code.", "media_or_form": [ "application/ld+json", "text/turtle", "application/rdf+xml", "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative vocabulary or registry identifier first, otherwise governed concept-scheme IRI, then Dimension UUID or ULID; include immutable release or assertion revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-005", "SRC-010", "SRC-012", "SRC-013", "SRC-014", "SRC-016", "SRC-017", "SRC-018" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "hierarchy-association-facets-collections-and-integrity", "name": "Hierarchy, association, facets, collections and integrity", "description": "Groups the governed Resource Consumption concern for hierarchy, association, facets, collections and integrity.", "rationale": "Preserve exact relation semantics and validate the intended graph profile.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-016", "SRC-024" ], "layers": [ { "id": "broader-narrower-association-polyhierarchy-and-topology", "name": "Broader, narrower, association, polyhierarchy and topology", "description": "Groups Resource Consumption context for broader, narrower, association, polyhierarchy and topology without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-016" ], "findings": [ { "id": "broader-narrower-generic-instance-partitive-top-concept-and-transitive-closure", "name": "Broader, narrower, generic, instance, partitive, top-concept and transitive closure", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-016" ], "questions": [ { "id": "broader-narrower-generic-instance-partitive-top-concept-and-transitive-closure-q01", "text": "Which scheme and concept identities, profile, scope, language, relation semantics and release establish broader, narrower, generic, instance, partitive, top-concept and transitive closure?", "kind": "relationship", "answer_data": [ "scheme identifier, namespace, profile, version, release and status", "concept URI, local identifier, labels, definition, notation, membership and relation type", "subject scope, audience, language, jurisdiction, effective period and exclusions" ] }, { "id": "broader-narrower-generic-instance-partitive-top-concept-and-transitive-closure-q02", "text": "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?", "kind": "quality", "answer_data": [ "owner, publisher, scheme steward, concept editor, mapper, reviewer and approver roles", "mandate, source, editorial policy, proposal, review, approval, dispute and change authority", "source system, license, purpose, access, retention and audit basis" ] }, { "id": "broader-narrower-generic-instance-partitive-top-concept-and-transitive-closure-q03", "text": "Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify broader, narrower, generic, instance, partitive, top-concept and transitive closure?", "kind": "identity", "answer_data": [ "definition, note, broader, narrower, related, collection, facet and topology", "mapping source and target versions, method, confidence, evidence, reviewer and conflict", "validation result, change set, predecessor, successor, projection profile and semantic-loss declaration" ] } ], "data_elements": [ { "id": "broader-narrower-generic-instance-partitive-top-concept-and-transitive-closure-data", "name": "Broader, narrower, generic, instance, partitive, top-concept and transitive closure data", "description": "Typed scheme-scoped values and references required to answer the governed questions for broader, narrower, generic, instance, partitive, top-concept and transitive closure.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-016" ] } ], "artifacts": [ { "id": "broader-narrower-generic-instance-partitive-top-concept-and-transitive-closure-artifact", "name": "Broader, narrower, generic, instance, partitive, top-concept and transitive closure evidence manifest", "description": "Digest-addressed manifest of concepts, labels, definitions, relations, mappings, validation, changes and provenance supporting broader, narrower, generic, instance, partitive, top-concept and transitive closure.", "media_or_form": [ "application/ld+json", "text/turtle", "application/rdf+xml", "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative vocabulary or registry identifier first, otherwise governed concept-scheme IRI, then Dimension UUID or ULID; include immutable release or assertion revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-016" ] } ], "inline_only_rationale": null }, { "id": "related-see-also-direction-role-symmetry-polyhierarchy-cycle-and-orphan", "name": "Related, see-also, direction, role, symmetry, polyhierarchy, cycle and orphan", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-016" ], "questions": [ { "id": "related-see-also-direction-role-symmetry-polyhierarchy-cycle-and-orphan-q01", "text": "Which scheme and concept identities, profile, scope, language, relation semantics and release establish related, see-also, direction, role, symmetry, polyhierarchy, cycle and orphan?", "kind": "relationship", "answer_data": [ "scheme identifier, namespace, profile, version, release and status", "concept URI, local identifier, labels, definition, notation, membership and relation type", "subject scope, audience, language, jurisdiction, effective period and exclusions" ] }, { "id": "related-see-also-direction-role-symmetry-polyhierarchy-cycle-and-orphan-q02", "text": "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?", "kind": "validation", "answer_data": [ "owner, publisher, scheme steward, concept editor, mapper, reviewer and approver roles", "mandate, source, editorial policy, proposal, review, approval, dispute and change authority", "source system, license, purpose, access, retention and audit basis" ] }, { "id": "related-see-also-direction-role-symmetry-polyhierarchy-cycle-and-orphan-q03", "text": "Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify related, see-also, direction, role, symmetry, polyhierarchy, cycle and orphan?", "kind": "classification", "answer_data": [ "definition, note, broader, narrower, related, collection, facet and topology", "mapping source and target versions, method, confidence, evidence, reviewer and conflict", "validation result, change set, predecessor, successor, projection profile and semantic-loss declaration" ] } ], "data_elements": [ { "id": "related-see-also-direction-role-symmetry-polyhierarchy-cycle-and-orphan-data", "name": "Related, see-also, direction, role, symmetry, polyhierarchy, cycle and orphan data", "description": "Typed scheme-scoped values and references required to answer the governed questions for related, see-also, direction, role, symmetry, polyhierarchy, cycle and orphan.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-016" ] } ], "artifacts": [ { "id": "related-see-also-direction-role-symmetry-polyhierarchy-cycle-and-orphan-artifact", "name": "Related, see-also, direction, role, symmetry, polyhierarchy, cycle and orphan evidence manifest", "description": "Digest-addressed manifest of concepts, labels, definitions, relations, mappings, validation, changes and provenance supporting related, see-also, direction, role, symmetry, polyhierarchy, cycle and orphan.", "media_or_form": [ "application/ld+json", "text/turtle", "application/rdf+xml", "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative vocabulary or registry identifier first, otherwise governed concept-scheme IRI, then Dimension UUID or ULID; include immutable release or assertion revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-011", "SRC-012", "SRC-014", "SRC-016" ] } ], "inline_only_rationale": null } ] }, { "id": "facets-arrays-collections-compounds-and-structural-rules", "name": "Facets, arrays, collections, compounds and structural rules", "description": "Groups Resource Consumption context for facets, arrays, collections, compounds and structural rules without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-010", "SRC-011", "SRC-014", "SRC-016", "SRC-024" ], "findings": [ { "id": "facet-facet-value-array-node-guide-term-and-systematic-display", "name": "Facet, facet value, array, node label, guide term and systematic display", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-010", "SRC-011", "SRC-014", "SRC-016", "SRC-024" ], "questions": [ { "id": "facet-facet-value-array-node-guide-term-and-systematic-display-q01", "text": "Which scheme and concept identities, profile, scope, language, relation semantics and release establish facet, facet value, array, node label, guide term and systematic display?", "kind": "composition", "answer_data": [ "scheme identifier, namespace, profile, version, release and status", "concept URI, local identifier, labels, definition, notation, membership and relation type", "subject scope, audience, language, jurisdiction, effective period and exclusions" ] }, { "id": "facet-facet-value-array-node-guide-term-and-systematic-display-q02", "text": "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?", "kind": "security", "answer_data": [ "owner, publisher, scheme steward, concept editor, mapper, reviewer and approver roles", "mandate, source, editorial policy, proposal, review, approval, dispute and change authority", "source system, license, purpose, access, retention and audit basis" ] }, { "id": "facet-facet-value-array-node-guide-term-and-systematic-display-q03", "text": "Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify facet, facet value, array, node label, guide term and systematic display?", "kind": "composition", "answer_data": [ "definition, note, broader, narrower, related, collection, facet and topology", "mapping source and target versions, method, confidence, evidence, reviewer and conflict", "validation result, change set, predecessor, successor, projection profile and semantic-loss declaration" ] } ], "data_elements": [ { "id": "facet-facet-value-array-node-guide-term-and-systematic-display-data", "name": "Facet, facet value, array, node label, guide term and systematic display data", "description": "Typed scheme-scoped values and references required to answer the governed questions for facet, facet value, array, node label, guide term and systematic display.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-010", "SRC-011", "SRC-014", "SRC-016", "SRC-024" ] } ], "artifacts": [ { "id": "facet-facet-value-array-node-guide-term-and-systematic-display-artifact", "name": "Facet, facet value, array, node label, guide term and systematic display evidence manifest", "description": "Digest-addressed manifest of concepts, labels, definitions, relations, mappings, validation, changes and provenance supporting facet, facet value, array, node label, guide term and systematic display.", "media_or_form": [ "application/ld+json", "text/turtle", "application/rdf+xml", "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative vocabulary or registry identifier first, otherwise governed concept-scheme IRI, then Dimension UUID or ULID; include immutable release or assertion revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-010", "SRC-011", "SRC-014", "SRC-016", "SRC-024" ] } ], "inline_only_rationale": null }, { "id": "collection-ordered-collection-member-list-compound-concept-and-precoordination", "name": "Collection, ordered collection, member list, compound concept and precoordination", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-010", "SRC-011", "SRC-014", "SRC-016", "SRC-024" ], "questions": [ { "id": "collection-ordered-collection-member-list-compound-concept-and-precoordination-q01", "text": "Which scheme and concept identities, profile, scope, language, relation semantics and release establish collection, ordered collection, member list, compound concept and precoordination?", "kind": "composition", "answer_data": [ "scheme identifier, namespace, profile, version, release and status", "concept URI, local identifier, labels, definition, notation, membership and relation type", "subject scope, audience, language, jurisdiction, effective period and exclusions" ] }, { "id": "collection-ordered-collection-member-list-compound-concept-and-precoordination-q02", "text": "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?", "kind": "privacy", "answer_data": [ "owner, publisher, scheme steward, concept editor, mapper, reviewer and approver roles", "mandate, source, editorial policy, proposal, review, approval, dispute and change authority", "source system, license, purpose, access, retention and audit basis" ] }, { "id": "collection-ordered-collection-member-list-compound-concept-and-precoordination-q03", "text": "Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify collection, ordered collection, member list, compound concept and precoordination?", "kind": "relationship", "answer_data": [ "definition, note, broader, narrower, related, collection, facet and topology", "mapping source and target versions, method, confidence, evidence, reviewer and conflict", "validation result, change set, predecessor, successor, projection profile and semantic-loss declaration" ] } ], "data_elements": [ { "id": "collection-ordered-collection-member-list-compound-concept-and-precoordination-data", "name": "Collection, ordered collection, member list, compound concept and precoordination data", "description": "Typed scheme-scoped values and references required to answer the governed questions for collection, ordered collection, member list, compound concept and precoordination.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-010", "SRC-011", "SRC-014", "SRC-016", "SRC-024" ] } ], "artifacts": [ { "id": "collection-ordered-collection-member-list-compound-concept-and-precoordination-artifact", "name": "Collection, ordered collection, member list, compound concept and precoordination evidence manifest", "description": "Digest-addressed manifest of concepts, labels, definitions, relations, mappings, validation, changes and provenance supporting collection, ordered collection, member list, compound concept and precoordination.", "media_or_form": [ "application/ld+json", "text/turtle", "application/rdf+xml", "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative vocabulary or registry identifier first, otherwise governed concept-scheme IRI, then Dimension UUID or ULID; include immutable release or assertion revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-010", "SRC-011", "SRC-014", "SRC-016", "SRC-024" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "mapping-alignment-method-confidence-and-dispute", "name": "Mapping, alignment, method, confidence and dispute", "description": "Groups the governed Resource Consumption concern for mapping, alignment, method, confidence and dispute.", "rationale": "Map schemes without silently merging identities or propagating weak equivalence.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-011", "SRC-016", "SRC-024", "SRC-007", "SRC-008", "SRC-012", "SRC-013", "SRC-014", "SRC-019" ], "layers": [ { "id": "mapping-relation-source-target-version-and-direction", "name": "Mapping relation, source, target, version and direction", "description": "Groups Resource Consumption context for mapping relation, source, target, version and direction without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-011", "SRC-016", "SRC-024" ], "findings": [ { "id": "exact-close-broad-narrow-related-equivalent-subclass-and-same-as-distinction", "name": "Exact, close, broad, narrow, related, equivalent, subclass and same-as distinction", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-011", "SRC-016", "SRC-024" ], "questions": [ { "id": "exact-close-broad-narrow-related-equivalent-subclass-and-same-as-distinction-q01", "text": "Which scheme and concept identities, profile, scope, language, relation semantics and release establish exact, close, broad, narrow, related, equivalent, subclass and same-as distinction?", "kind": "interoperability", "answer_data": [ "scheme identifier, namespace, profile, version, release and status", "concept URI, local identifier, labels, definition, notation, membership and relation type", "subject scope, audience, language, jurisdiction, effective period and exclusions" ] }, { "id": "exact-close-broad-narrow-related-equivalent-subclass-and-same-as-distinction-q02", "text": "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?", "kind": "retention", "answer_data": [ "owner, publisher, scheme steward, concept editor, mapper, reviewer and approver roles", "mandate, source, editorial policy, proposal, review, approval, dispute and change authority", "source system, license, purpose, access, retention and audit basis" ] }, { "id": "exact-close-broad-narrow-related-equivalent-subclass-and-same-as-distinction-q03", "text": "Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify exact, close, broad, narrow, related, equivalent, subclass and same-as distinction?", "kind": "state", "answer_data": [ "definition, note, broader, narrower, related, collection, facet and topology", "mapping source and target versions, method, confidence, evidence, reviewer and conflict", "validation result, change set, predecessor, successor, projection profile and semantic-loss declaration" ] } ], "data_elements": [ { "id": "exact-close-broad-narrow-related-equivalent-subclass-and-same-as-distinction-data", "name": "Exact, close, broad, narrow, related, equivalent, subclass and same-as distinction data", "description": "Typed scheme-scoped values and references required to answer the governed questions for exact, close, broad, narrow, related, equivalent, subclass and same-as distinction.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-011", "SRC-016", "SRC-024" ] } ], "artifacts": [ { "id": "exact-close-broad-narrow-related-equivalent-subclass-and-same-as-distinction-artifact", "name": "Exact, close, broad, narrow, related, equivalent, subclass and same-as distinction evidence manifest", "description": "Digest-addressed manifest of concepts, labels, definitions, relations, mappings, validation, changes and provenance supporting exact, close, broad, narrow, related, equivalent, subclass and same-as distinction.", "media_or_form": [ "application/ld+json", "text/turtle", "application/rdf+xml", "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative vocabulary or registry identifier first, otherwise governed concept-scheme IRI, then Dimension UUID or ULID; include immutable release or assertion revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-011", "SRC-016", "SRC-024" ] } ], "inline_only_rationale": null }, { "id": "source-concept-target-concept-scheme-version-direction-symmetry-and-transitivity", "name": "Source concept, target concept, scheme version, direction, symmetry and transitivity", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-011", "SRC-016", "SRC-024" ], "questions": [ { "id": "source-concept-target-concept-scheme-version-direction-symmetry-and-transitivity-q01", "text": "Which scheme and concept identities, profile, scope, language, relation semantics and release establish source concept, target concept, scheme version, direction, symmetry and transitivity?", "kind": "relationship", "answer_data": [ "scheme identifier, namespace, profile, version, release and status", "concept URI, local identifier, labels, definition, notation, membership and relation type", "subject scope, audience, language, jurisdiction, effective period and exclusions" ] }, { "id": "source-concept-target-concept-scheme-version-direction-symmetry-and-transitivity-q02", "text": "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?", "kind": "access", "answer_data": [ "owner, publisher, scheme steward, concept editor, mapper, reviewer and approver roles", "mandate, source, editorial policy, proposal, review, approval, dispute and change authority", "source system, license, purpose, access, retention and audit basis" ] }, { "id": "source-concept-target-concept-scheme-version-direction-symmetry-and-transitivity-q03", "text": "Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify source concept, target concept, scheme version, direction, symmetry and transitivity?", "kind": "lifecycle", "answer_data": [ "definition, note, broader, narrower, related, collection, facet and topology", "mapping source and target versions, method, confidence, evidence, reviewer and conflict", "validation result, change set, predecessor, successor, projection profile and semantic-loss declaration" ] } ], "data_elements": [ { "id": "source-concept-target-concept-scheme-version-direction-symmetry-and-transitivity-data", "name": "Source concept, target concept, scheme version, direction, symmetry and transitivity data", "description": "Typed scheme-scoped values and references required to answer the governed questions for source concept, target concept, scheme version, direction, symmetry and transitivity.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-011", "SRC-016", "SRC-024" ] } ], "artifacts": [ { "id": "source-concept-target-concept-scheme-version-direction-symmetry-and-transitivity-artifact", "name": "Source concept, target concept, scheme version, direction, symmetry and transitivity evidence manifest", "description": "Digest-addressed manifest of concepts, labels, definitions, relations, mappings, validation, changes and provenance supporting source concept, target concept, scheme version, direction, symmetry and transitivity.", "media_or_form": [ "application/ld+json", "text/turtle", "application/rdf+xml", "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative vocabulary or registry identifier first, otherwise governed concept-scheme IRI, then Dimension UUID or ULID; include immutable release or assertion revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-011", "SRC-016", "SRC-024" ] } ], "inline_only_rationale": null } ] }, { "id": "mapping-method-evidence-confidence-review-and-conflict", "name": "Mapping method, evidence, confidence, review and conflict", "description": "Groups Resource Consumption context for mapping method, evidence, confidence, review and conflict without importing neighboring master lifecycles.", "source_refs": [ "SRC-007", "SRC-008", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-019", "SRC-024" ], "findings": [ { "id": "mapping-method-actor-tool-date-rationale-evidence-confidence-and-quality", "name": "Mapping method, actor, tool, date, rationale, evidence, confidence and quality", "description": "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.", "source_refs": [ "SRC-007", "SRC-008", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-019", "SRC-024" ], "questions": [ { "id": "mapping-method-actor-tool-date-rationale-evidence-confidence-and-quality-q01", "text": "Which scheme and concept identities, profile, scope, language, relation semantics and release establish mapping method, actor, tool, date, rationale, evidence, confidence and quality?", "kind": "provenance", "answer_data": [ "scheme identifier, namespace, profile, version, release and status", "concept URI, local identifier, labels, definition, notation, membership and relation type", "subject scope, audience, language, jurisdiction, effective period and exclusions" ] }, { "id": "mapping-method-actor-tool-date-rationale-evidence-confidence-and-quality-q02", "text": "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?", "kind": "exception", "answer_data": [ "owner, publisher, scheme steward, concept editor, mapper, reviewer and approver roles", "mandate, source, editorial policy, proposal, review, approval, dispute and change authority", "source system, license, purpose, access, retention and audit basis" ] }, { "id": "mapping-method-actor-tool-date-rationale-evidence-confidence-and-quality-q03", "text": "Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify mapping method, actor, tool, date, rationale, evidence, confidence and quality?", "kind": "temporal", "answer_data": [ "definition, note, broader, narrower, related, collection, facet and topology", "mapping source and target versions, method, confidence, evidence, reviewer and conflict", "validation result, change set, predecessor, successor, projection profile and semantic-loss declaration" ] } ], "data_elements": [ { "id": "mapping-method-actor-tool-date-rationale-evidence-confidence-and-quality-data", "name": "Mapping method, actor, tool, date, rationale, evidence, confidence and quality data", "description": "Typed scheme-scoped values and references required to answer the governed questions for mapping method, actor, tool, date, rationale, evidence, confidence and quality.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-007", "SRC-008", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-019", "SRC-024" ] } ], "artifacts": [ { "id": "mapping-method-actor-tool-date-rationale-evidence-confidence-and-quality-artifact", "name": "Mapping method, actor, tool, date, rationale, evidence, confidence and quality evidence manifest", "description": "Digest-addressed manifest of concepts, labels, definitions, relations, mappings, validation, changes and provenance supporting mapping method, actor, tool, date, rationale, evidence, confidence and quality.", "media_or_form": [ "application/ld+json", "text/turtle", "application/rdf+xml", "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative vocabulary or registry identifier first, otherwise governed concept-scheme IRI, then Dimension UUID or ULID; include immutable release or assertion revision and digest.", "source_refs": [ "SRC-007", "SRC-008", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-019", "SRC-024" ] } ], "inline_only_rationale": null }, { "id": "candidate-accepted-rejected-contested-superseded-conflict-and-resolution", "name": "Candidate, accepted, rejected, contested, superseded, conflict and resolution", "description": "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.", "source_refs": [ "SRC-007", "SRC-008", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-019", "SRC-024" ], "questions": [ { "id": "candidate-accepted-rejected-contested-superseded-conflict-and-resolution-q01", "text": "Which scheme and concept identities, profile, scope, language, relation semantics and release establish candidate, accepted, rejected, contested, superseded, conflict and resolution?", "kind": "state", "answer_data": [ "scheme identifier, namespace, profile, version, release and status", "concept URI, local identifier, labels, definition, notation, membership and relation type", "subject scope, audience, language, jurisdiction, effective period and exclusions" ] }, { "id": "candidate-accepted-rejected-contested-superseded-conflict-and-resolution-q02", "text": "Who creates, owns, stewards, proposes, reviews, approves, maps, publishes, revises or discloses candidate, accepted, rejected, contested, superseded, conflict and resolution, and under which authority?", "kind": "interoperability", "answer_data": [ "owner, publisher, scheme steward, concept editor, mapper, reviewer and approver roles", "mandate, source, editorial policy, proposal, review, approval, dispute and change authority", "source system, license, purpose, access, retention and audit basis" ] }, { "id": "candidate-accepted-rejected-contested-superseded-conflict-and-resolution-q03", "text": "Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify candidate, accepted, rejected, contested, superseded, conflict and resolution?", "kind": "spatial", "answer_data": [ "definition, note, broader, narrower, related, collection, facet and topology", "mapping source and target versions, method, confidence, evidence, reviewer and conflict", "validation result, change set, predecessor, successor, projection profile and semantic-loss declaration" ] } ], "data_elements": [ { "id": "candidate-accepted-rejected-contested-superseded-conflict-and-resolution-data", "name": "Candidate, accepted, rejected, contested, superseded, conflict and resolution data", "description": "Typed scheme-scoped values and references required to answer the governed questions for candidate, accepted, rejected, contested, superseded, conflict and resolution.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-007", "SRC-008", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-019", "SRC-024" ] } ], "artifacts": [ { "id": "candidate-accepted-rejected-contested-superseded-conflict-and-resolution-artifact", "name": "Candidate, accepted, rejected, contested, superseded, conflict and resolution evidence manifest", "description": "Digest-addressed manifest of concepts, labels, definitions, relations, mappings, validation, changes and provenance supporting candidate, accepted, rejected, contested, superseded, conflict and resolution.", "media_or_form": [ "application/ld+json", "text/turtle", "application/rdf+xml", "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative vocabulary or registry identifier first, otherwise governed concept-scheme IRI, then Dimension UUID or ULID; include immutable release or assertion revision and digest.", "source_refs": [ "SRC-007", "SRC-008", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-019", "SRC-024" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "governance-change-lifecycle-quality-and-validation", "name": "Governance, change, lifecycle, quality and validation", "description": "Groups the governed Resource Consumption concern for governance, change, lifecycle, quality and validation.", "rationale": "Manage proposals and releases without erasing prior concept meaning or assignments.", "source_refs": [ "SRC-001", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-014", "SRC-015", "SRC-016", "SRC-019", "SRC-024", "SRC-002", "SRC-006", "SRC-008", "SRC-013" ], "layers": [ { "id": "proposal-review-approval-change-and-retirement", "name": "Proposal, review, approval, change and retirement", "description": "Groups Resource Consumption context for proposal, review, approval, change and retirement without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-014", "SRC-015", "SRC-016", "SRC-019", "SRC-024" ], "findings": [ { "id": "draft-proposed-reviewed-approved-published-deprecated-superseded-and-retired-state", "name": "Draft, proposed, reviewed, approved, published, deprecated, superseded and retired state", "description": "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.", "source_refs": [ "SRC-001", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-014", "SRC-015", "SRC-016", "SRC-019", "SRC-024" ], "questions": [ { "id": "draft-proposed-reviewed-approved-published-deprecated-superseded-and-retired-state-q01", "text": "Which scheme and concept identities, profile, scope, language, relation semantics and release establish draft, proposed, reviewed, approved, published, deprecated, superseded and retired state?", "kind": "lifecycle", "answer_data": [ "scheme identifier, namespace, profile, version, release and status", "concept URI, local identifier, labels, definition, notation, membership and relation type", "subject scope, audience, language, jurisdiction, effective period and exclusions" ] }, { "id": "draft-proposed-reviewed-approved-published-deprecated-superseded-and-retired-state-q02", "text": "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?", "kind": "decision", "answer_data": [ "owner, publisher, scheme steward, concept editor, mapper, reviewer and approver roles", "mandate, source, editorial policy, proposal, review, approval, dispute and change authority", "source system, license, purpose, access, retention and audit basis" ] }, { "id": "draft-proposed-reviewed-approved-published-deprecated-superseded-and-retired-state-q03", "text": "Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify draft, proposed, reviewed, approved, published, deprecated, superseded and retired state?", "kind": "provenance", "answer_data": [ "definition, note, broader, narrower, related, collection, facet and topology", "mapping source and target versions, method, confidence, evidence, reviewer and conflict", "validation result, change set, predecessor, successor, projection profile and semantic-loss declaration" ] } ], "data_elements": [ { "id": "draft-proposed-reviewed-approved-published-deprecated-superseded-and-retired-state-data", "name": "Draft, proposed, reviewed, approved, published, deprecated, superseded and retired state data", "description": "Typed scheme-scoped values and references required to answer the governed questions for draft, proposed, reviewed, approved, published, deprecated, superseded and retired state.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-014", "SRC-015", "SRC-016", "SRC-019", "SRC-024" ] } ], "artifacts": [ { "id": "draft-proposed-reviewed-approved-published-deprecated-superseded-and-retired-state-artifact", "name": "Draft, proposed, reviewed, approved, published, deprecated, superseded and retired state evidence manifest", "description": "Digest-addressed manifest of concepts, labels, definitions, relations, mappings, validation, changes and provenance supporting draft, proposed, reviewed, approved, published, deprecated, superseded and retired state.", "media_or_form": [ "application/ld+json", "text/turtle", "application/rdf+xml", "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative vocabulary or registry identifier first, otherwise governed concept-scheme IRI, then Dimension UUID or ULID; include immutable release or assertion revision and digest.", "source_refs": [ "SRC-001", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-014", "SRC-015", "SRC-016", "SRC-019", "SRC-024" ] } ], "inline_only_rationale": null }, { "id": "change-set-add-update-move-split-merge-replace-delete-rationale-and-impact", "name": "Change set, add, update, move, split, merge, replace, delete, rationale and impact", "description": "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.", "source_refs": [ "SRC-001", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-014", "SRC-015", "SRC-016", "SRC-019", "SRC-024" ], "questions": [ { "id": "change-set-add-update-move-split-merge-replace-delete-rationale-and-impact-q01", "text": "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?", "kind": "event", "answer_data": [ "scheme identifier, namespace, profile, version, release and status", "concept URI, local identifier, labels, definition, notation, membership and relation type", "subject scope, audience, language, jurisdiction, effective period and exclusions" ] }, { "id": "change-set-add-update-move-split-merge-replace-delete-rationale-and-impact-q02", "text": "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?", "kind": "identity", "answer_data": [ "owner, publisher, scheme steward, concept editor, mapper, reviewer and approver roles", "mandate, source, editorial policy, proposal, review, approval, dispute and change authority", "source system, license, purpose, access, retention and audit basis" ] }, { "id": "change-set-add-update-move-split-merge-replace-delete-rationale-and-impact-q03", "text": "Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify change set, add, update, move, split, merge, replace, delete, rationale and impact?", "kind": "ownership", "answer_data": [ "definition, note, broader, narrower, related, collection, facet and topology", "mapping source and target versions, method, confidence, evidence, reviewer and conflict", "validation result, change set, predecessor, successor, projection profile and semantic-loss declaration" ] } ], "data_elements": [ { "id": "change-set-add-update-move-split-merge-replace-delete-rationale-and-impact-data", "name": "Change set, add, update, move, split, merge, replace, delete, rationale and impact data", "description": "Typed scheme-scoped values and references required to answer the governed questions for change set, add, update, move, split, merge, replace, delete, rationale and impact.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-014", "SRC-015", "SRC-016", "SRC-019", "SRC-024" ] } ], "artifacts": [ { "id": "change-set-add-update-move-split-merge-replace-delete-rationale-and-impact-artifact", "name": "Change set, add, update, move, split, merge, replace, delete, rationale and impact evidence manifest", "description": "Digest-addressed manifest of concepts, labels, definitions, relations, mappings, validation, changes and provenance supporting change set, add, update, move, split, merge, replace, delete, rationale and impact.", "media_or_form": [ "application/ld+json", "text/turtle", "application/rdf+xml", "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative vocabulary or registry identifier first, otherwise governed concept-scheme IRI, then Dimension UUID or ULID; include immutable release or assertion revision and digest.", "source_refs": [ "SRC-001", "SRC-007", "SRC-009", "SRC-010", "SRC-011", "SRC-014", "SRC-015", "SRC-016", "SRC-019", "SRC-024" ] } ], "inline_only_rationale": null } ] }, { "id": "validation-quality-completeness-consistency-and-release-gate", "name": "Validation, quality, completeness, consistency and release gate", "description": "Groups Resource Consumption context for validation, quality, completeness, consistency and release gate without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-011", "SRC-013", "SRC-014", "SRC-024" ], "findings": [ { "id": "identity-label-language-notation-domain-range-hierarchy-cycle-and-mapping-check", "name": "Identity, label, language, notation, domain, range, hierarchy, cycle and mapping check", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-011", "SRC-013", "SRC-014", "SRC-024" ], "questions": [ { "id": "identity-label-language-notation-domain-range-hierarchy-cycle-and-mapping-check-q01", "text": "Which scheme and concept identities, profile, scope, language, relation semantics and release establish identity, label, language, notation, domain, range, hierarchy, cycle and mapping check?", "kind": "validation", "answer_data": [ "scheme identifier, namespace, profile, version, release and status", "concept URI, local identifier, labels, definition, notation, membership and relation type", "subject scope, audience, language, jurisdiction, effective period and exclusions" ] }, { "id": "identity-label-language-notation-domain-range-hierarchy-cycle-and-mapping-check-q02", "text": "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?", "kind": "classification", "answer_data": [ "owner, publisher, scheme steward, concept editor, mapper, reviewer and approver roles", "mandate, source, editorial policy, proposal, review, approval, dispute and change authority", "source system, license, purpose, access, retention and audit basis" ] }, { "id": "identity-label-language-notation-domain-range-hierarchy-cycle-and-mapping-check-q03", "text": "Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify identity, label, language, notation, domain, range, hierarchy, cycle and mapping check?", "kind": "authority", "answer_data": [ "definition, note, broader, narrower, related, collection, facet and topology", "mapping source and target versions, method, confidence, evidence, reviewer and conflict", "validation result, change set, predecessor, successor, projection profile and semantic-loss declaration" ] } ], "data_elements": [ { "id": "identity-label-language-notation-domain-range-hierarchy-cycle-and-mapping-check-data", "name": "Identity, label, language, notation, domain, range, hierarchy, cycle and mapping check data", "description": "Typed scheme-scoped values and references required to answer the governed questions for identity, label, language, notation, domain, range, hierarchy, cycle and mapping check.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-011", "SRC-013", "SRC-014", "SRC-024" ] } ], "artifacts": [ { "id": "identity-label-language-notation-domain-range-hierarchy-cycle-and-mapping-check-artifact", "name": "Identity, label, language, notation, domain, range, hierarchy, cycle and mapping check evidence manifest", "description": "Digest-addressed manifest of concepts, labels, definitions, relations, mappings, validation, changes and provenance supporting identity, label, language, notation, domain, range, hierarchy, cycle and mapping check.", "media_or_form": [ "application/ld+json", "text/turtle", "application/rdf+xml", "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative vocabulary or registry identifier first, otherwise governed concept-scheme IRI, then Dimension UUID or ULID; include immutable release or assertion revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-011", "SRC-013", "SRC-014", "SRC-024" ] } ], "inline_only_rationale": null }, { "id": "coverage-completeness-freshness-consistency-accuracy-usability-and-release-assurance", "name": "Coverage, completeness, freshness, consistency, accuracy, usability and release assurance", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-011", "SRC-013", "SRC-014", "SRC-024" ], "questions": [ { "id": "coverage-completeness-freshness-consistency-accuracy-usability-and-release-assurance-q01", "text": "Which scheme and concept identities, profile, scope, language, relation semantics and release establish coverage, completeness, freshness, consistency, accuracy, usability and release assurance?", "kind": "quality", "answer_data": [ "scheme identifier, namespace, profile, version, release and status", "concept URI, local identifier, labels, definition, notation, membership and relation type", "subject scope, audience, language, jurisdiction, effective period and exclusions" ] }, { "id": "coverage-completeness-freshness-consistency-accuracy-usability-and-release-assurance-q02", "text": "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?", "kind": "composition", "answer_data": [ "owner, publisher, scheme steward, concept editor, mapper, reviewer and approver roles", "mandate, source, editorial policy, proposal, review, approval, dispute and change authority", "source system, license, purpose, access, retention and audit basis" ] }, { "id": "coverage-completeness-freshness-consistency-accuracy-usability-and-release-assurance-q03", "text": "Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify coverage, completeness, freshness, consistency, accuracy, usability and release assurance?", "kind": "requirement", "answer_data": [ "definition, note, broader, narrower, related, collection, facet and topology", "mapping source and target versions, method, confidence, evidence, reviewer and conflict", "validation result, change set, predecessor, successor, projection profile and semantic-loss declaration" ] } ], "data_elements": [ { "id": "coverage-completeness-freshness-consistency-accuracy-usability-and-release-assurance-data", "name": "Coverage, completeness, freshness, consistency, accuracy, usability and release assurance data", "description": "Typed scheme-scoped values and references required to answer the governed questions for coverage, completeness, freshness, consistency, accuracy, usability and release assurance.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-011", "SRC-013", "SRC-014", "SRC-024" ] } ], "artifacts": [ { "id": "coverage-completeness-freshness-consistency-accuracy-usability-and-release-assurance-artifact", "name": "Coverage, completeness, freshness, consistency, accuracy, usability and release assurance evidence manifest", "description": "Digest-addressed manifest of concepts, labels, definitions, relations, mappings, validation, changes and provenance supporting coverage, completeness, freshness, consistency, accuracy, usability and release assurance.", "media_or_form": [ "application/ld+json", "text/turtle", "application/rdf+xml", "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative vocabulary or registry identifier first, otherwise governed concept-scheme IRI, then Dimension UUID or ULID; include immutable release or assertion revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-006", "SRC-007", "SRC-008", "SRC-010", "SRC-011", "SRC-013", "SRC-014", "SRC-024" ] } ], "inline_only_rationale": null } ] } ] }, { "id": "access-license-retention-publication-and-interoperability", "name": "Access, license, retention, publication and interoperability", "description": "Groups the governed Resource Consumption concern for access, license, retention, publication and interoperability.", "rationale": "Expose governed projections while preserving source identity, versions and semantic loss.", "source_refs": [ "SRC-007", "SRC-009", "SRC-015", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024", "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-008", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-016", "SRC-017", "SRC-018" ], "layers": [ { "id": "rights-access-sensitivity-retention-and-audit", "name": "Rights, access, sensitivity, retention and audit", "description": "Groups Resource Consumption context for rights, access, sensitivity, retention and audit without importing neighboring master lifecycles.", "source_refs": [ "SRC-007", "SRC-009", "SRC-015", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ], "findings": [ { "id": "license-rights-holder-attribution-purpose-role-sensitivity-and-minimum-disclosure", "name": "License, rights holder, attribution, purpose, role, sensitivity and minimum disclosure", "description": "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.", "source_refs": [ "SRC-007", "SRC-009", "SRC-015", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ], "questions": [ { "id": "license-rights-holder-attribution-purpose-role-sensitivity-and-minimum-disclosure-q01", "text": "Which scheme and concept identities, profile, scope, language, relation semantics and release establish license, rights holder, attribution, purpose, role, sensitivity and minimum disclosure?", "kind": "access", "answer_data": [ "scheme identifier, namespace, profile, version, release and status", "concept URI, local identifier, labels, definition, notation, membership and relation type", "subject scope, audience, language, jurisdiction, effective period and exclusions" ] }, { "id": "license-rights-holder-attribution-purpose-role-sensitivity-and-minimum-disclosure-q02", "text": "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?", "kind": "relationship", "answer_data": [ "owner, publisher, scheme steward, concept editor, mapper, reviewer and approver roles", "mandate, source, editorial policy, proposal, review, approval, dispute and change authority", "source system, license, purpose, access, retention and audit basis" ] }, { "id": "license-rights-holder-attribution-purpose-role-sensitivity-and-minimum-disclosure-q03", "text": "Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify license, rights holder, attribution, purpose, role, sensitivity and minimum disclosure?", "kind": "constraint", "answer_data": [ "definition, note, broader, narrower, related, collection, facet and topology", "mapping source and target versions, method, confidence, evidence, reviewer and conflict", "validation result, change set, predecessor, successor, projection profile and semantic-loss declaration" ] } ], "data_elements": [ { "id": "license-rights-holder-attribution-purpose-role-sensitivity-and-minimum-disclosure-data", "name": "License, rights holder, attribution, purpose, role, sensitivity and minimum disclosure data", "description": "Typed scheme-scoped values and references required to answer the governed questions for license, rights holder, attribution, purpose, role, sensitivity and minimum disclosure.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-007", "SRC-009", "SRC-015", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "artifacts": [ { "id": "license-rights-holder-attribution-purpose-role-sensitivity-and-minimum-disclosure-artifact", "name": "License, rights holder, attribution, purpose, role, sensitivity and minimum disclosure evidence manifest", "description": "Digest-addressed manifest of concepts, labels, definitions, relations, mappings, validation, changes and provenance supporting license, rights holder, attribution, purpose, role, sensitivity and minimum disclosure.", "media_or_form": [ "application/ld+json", "text/turtle", "application/rdf+xml", "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative vocabulary or registry identifier first, otherwise governed concept-scheme IRI, then Dimension UUID or ULID; include immutable release or assertion revision and digest.", "source_refs": [ "SRC-007", "SRC-009", "SRC-015", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "inline_only_rationale": null }, { "id": "retention-legal-hold-tombstone-withdrawal-audit-and-resolution-continuity", "name": "Retention, legal hold, tombstone, withdrawal, audit and resolution continuity", "description": "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.", "source_refs": [ "SRC-007", "SRC-009", "SRC-015", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ], "questions": [ { "id": "retention-legal-hold-tombstone-withdrawal-audit-and-resolution-continuity-q01", "text": "Which scheme and concept identities, profile, scope, language, relation semantics and release establish retention, legal hold, tombstone, withdrawal, audit and resolution continuity?", "kind": "retention", "answer_data": [ "scheme identifier, namespace, profile, version, release and status", "concept URI, local identifier, labels, definition, notation, membership and relation type", "subject scope, audience, language, jurisdiction, effective period and exclusions" ] }, { "id": "retention-legal-hold-tombstone-withdrawal-audit-and-resolution-continuity-q02", "text": "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?", "kind": "state", "answer_data": [ "owner, publisher, scheme steward, concept editor, mapper, reviewer and approver roles", "mandate, source, editorial policy, proposal, review, approval, dispute and change authority", "source system, license, purpose, access, retention and audit basis" ] }, { "id": "retention-legal-hold-tombstone-withdrawal-audit-and-resolution-continuity-q03", "text": "Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify retention, legal hold, tombstone, withdrawal, audit and resolution continuity?", "kind": "process", "answer_data": [ "definition, note, broader, narrower, related, collection, facet and topology", "mapping source and target versions, method, confidence, evidence, reviewer and conflict", "validation result, change set, predecessor, successor, projection profile and semantic-loss declaration" ] } ], "data_elements": [ { "id": "retention-legal-hold-tombstone-withdrawal-audit-and-resolution-continuity-data", "name": "Retention, legal hold, tombstone, withdrawal, audit and resolution continuity data", "description": "Typed scheme-scoped values and references required to answer the governed questions for retention, legal hold, tombstone, withdrawal, audit and resolution continuity.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-007", "SRC-009", "SRC-015", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "artifacts": [ { "id": "retention-legal-hold-tombstone-withdrawal-audit-and-resolution-continuity-artifact", "name": "Retention, legal hold, tombstone, withdrawal, audit and resolution continuity evidence manifest", "description": "Digest-addressed manifest of concepts, labels, definitions, relations, mappings, validation, changes and provenance supporting retention, legal hold, tombstone, withdrawal, audit and resolution continuity.", "media_or_form": [ "application/ld+json", "text/turtle", "application/rdf+xml", "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative vocabulary or registry identifier first, otherwise governed concept-scheme IRI, then Dimension UUID or ULID; include immutable release or assertion revision and digest.", "source_refs": [ "SRC-007", "SRC-009", "SRC-015", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "inline_only_rationale": null } ] }, { "id": "serialization-profile-import-export-and-loss", "name": "Serialization, profile, import, export and loss", "description": "Groups Resource Consumption context for serialization, profile, import, export and loss without importing neighboring master lifecycles.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ], "findings": [ { "id": "skos-rdf-rdfs-owl-jsonld-mads-dcmi-dcat-datacite-and-rocrate-projection", "name": "SKOS, RDF, RDFS, OWL, JSON-LD, MADS, DCMI, DCAT, DataCite and RO-Crate projection", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ], "questions": [ { "id": "skos-rdf-rdfs-owl-jsonld-mads-dcmi-dcat-datacite-and-rocrate-projection-q01", "text": "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?", "kind": "interoperability", "answer_data": [ "scheme identifier, namespace, profile, version, release and status", "concept URI, local identifier, labels, definition, notation, membership and relation type", "subject scope, audience, language, jurisdiction, effective period and exclusions" ] }, { "id": "skos-rdf-rdfs-owl-jsonld-mads-dcmi-dcat-datacite-and-rocrate-projection-q02", "text": "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?", "kind": "lifecycle", "answer_data": [ "owner, publisher, scheme steward, concept editor, mapper, reviewer and approver roles", "mandate, source, editorial policy, proposal, review, approval, dispute and change authority", "source system, license, purpose, access, retention and audit basis" ] }, { "id": "skos-rdf-rdfs-owl-jsonld-mads-dcmi-dcat-datacite-and-rocrate-projection-q03", "text": "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?", "kind": "event", "answer_data": [ "definition, note, broader, narrower, related, collection, facet and topology", "mapping source and target versions, method, confidence, evidence, reviewer and conflict", "validation result, change set, predecessor, successor, projection profile and semantic-loss declaration" ] } ], "data_elements": [ { "id": "skos-rdf-rdfs-owl-jsonld-mads-dcmi-dcat-datacite-and-rocrate-projection-data", "name": "SKOS, RDF, RDFS, OWL, JSON-LD, MADS, DCMI, DCAT, DataCite and RO-Crate projection data", "description": "Typed scheme-scoped values and references required to answer the governed questions for skos, rdf, rdfs, owl, json-ld, mads, dcmi, dcat, datacite and ro-crate projection.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "artifacts": [ { "id": "skos-rdf-rdfs-owl-jsonld-mads-dcmi-dcat-datacite-and-rocrate-projection-artifact", "name": "SKOS, RDF, RDFS, OWL, JSON-LD, MADS, DCMI, DCAT, DataCite and RO-Crate projection evidence manifest", "description": "Digest-addressed manifest of concepts, labels, definitions, relations, mappings, validation, changes and provenance supporting skos, rdf, rdfs, owl, json-ld, mads, dcmi, dcat, datacite and ro-crate projection.", "media_or_form": [ "application/ld+json", "text/turtle", "application/rdf+xml", "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative vocabulary or registry identifier first, otherwise governed concept-scheme IRI, then Dimension UUID or ULID; include immutable release or assertion revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "inline_only_rationale": null }, { "id": "profile-version-context-shape-conformance-round-trip-migration-and-semantic-loss", "name": "Profile, version, context, shape, conformance, round trip, migration and semantic loss", "description": "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.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ], "questions": [ { "id": "profile-version-context-shape-conformance-round-trip-migration-and-semantic-loss-q01", "text": "Which scheme and concept identities, profile, scope, language, relation semantics and release establish profile, version, context, shape, conformance, round trip, migration and semantic loss?", "kind": "validation", "answer_data": [ "scheme identifier, namespace, profile, version, release and status", "concept URI, local identifier, labels, definition, notation, membership and relation type", "subject scope, audience, language, jurisdiction, effective period and exclusions" ] }, { "id": "profile-version-context-shape-conformance-round-trip-migration-and-semantic-loss-q02", "text": "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?", "kind": "temporal", "answer_data": [ "owner, publisher, scheme steward, concept editor, mapper, reviewer and approver roles", "mandate, source, editorial policy, proposal, review, approval, dispute and change authority", "source system, license, purpose, access, retention and audit basis" ] }, { "id": "profile-version-context-shape-conformance-round-trip-migration-and-semantic-loss-q03", "text": "Which definitions, hierarchy, mappings, quality checks, change lineage and interoperability limits qualify profile, version, context, shape, conformance, round trip, migration and semantic loss?", "kind": "measurement", "answer_data": [ "definition, note, broader, narrower, related, collection, facet and topology", "mapping source and target versions, method, confidence, evidence, reviewer and conflict", "validation result, change set, predecessor, successor, projection profile and semantic-loss declaration" ] } ], "data_elements": [ { "id": "profile-version-context-shape-conformance-round-trip-migration-and-semantic-loss-data", "name": "Profile, version, context, shape, conformance, round trip, migration and semantic loss data", "description": "Typed scheme-scoped values and references required to answer the governed questions for profile, version, context, shape, conformance, round trip, migration and semantic loss.", "value_kind": "object", "cardinality": "1", "required": true, "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "artifacts": [ { "id": "profile-version-context-shape-conformance-round-trip-migration-and-semantic-loss-artifact", "name": "Profile, version, context, shape, conformance, round trip, migration and semantic loss evidence manifest", "description": "Digest-addressed manifest of concepts, labels, definitions, relations, mappings, validation, changes and provenance supporting profile, version, context, shape, conformance, round trip, migration and semantic loss.", "media_or_form": [ "application/ld+json", "text/turtle", "application/rdf+xml", "application/json", "application/yaml", "text/markdown", "external reference" ], "serial": true, "identity_strategy": "Authoritative vocabulary or registry identifier first, otherwise governed concept-scheme IRI, then Dimension UUID or ULID; include immutable release or assertion revision and digest.", "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "inline_only_rationale": null } ] } ] } ] }, "functions": [ { "id": "register-scheme", "name": "Register scheme", "description": "Create stable scheme identity, namespace, profile, purpose, scope, owner and initial release.", "inputs": [ "scheme proposal", "namespace", "owner" ], "outputs": [ "scheme identifier", "initial release" ], "preconditions": [ "active Dimension", "namespace authority" ], "effects": [ "identity and explicit unknowns are appended" ], "source_refs": [ "SRC-001", "SRC-004", "SRC-009", "SRC-015", "SRC-019", "SRC-024" ] }, { "id": "define-concept", "name": "Define concept", "description": "Create or revise one concept with stable identity, definition, characteristics and scheme membership.", "inputs": [ "scheme release", "concept proposal", "definition" ], "outputs": [ "concept revision" ], "preconditions": [ "editor authority", "referent boundary declared" ], "effects": [ "concept identity remains distinct from labels and classified objects" ], "source_refs": [ "SRC-001", "SRC-012", "SRC-013", "SRC-016", "SRC-024" ] }, { "id": "manage-labels-notations", "name": "Manage labels and notations", "description": "Append language-tagged preferred, alternative or hidden labels, notes and typed notations.", "inputs": [ "concept revision", "lexical form", "language or notation profile" ], "outputs": [ "lexical assertion" ], "preconditions": [ "language and uniqueness rules pass" ], "effects": [ "prior labels and reasons remain resolvable" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-005", "SRC-010", "SRC-014", "SRC-017", "SRC-018" ] }, { "id": "relate-concepts", "name": "Relate concepts", "description": "Append typed broader, narrower, related or custom semantic relations with explicit hierarchy profile.", "inputs": [ "concepts", "relation type", "authority" ], "outputs": [ "relation assertion" ], "preconditions": [ "endpoints and profile resolvable" ], "effects": [ "inverse, cycle and transitive effects are validated" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-010", "SRC-014" ] }, { "id": "manage-facets-collections", "name": "Manage facets and collections", "description": "Create facets, arrays, collections, ordered membership and compound structures without changing concept identity.", "inputs": [ "scheme release", "members", "structure kind" ], "outputs": [ "grouping structure" ], "preconditions": [ "membership and ordering valid" ], "effects": [ "grouping remains distinct from semantic hierarchy" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-010", "SRC-014" ] }, { "id": "map-schemes", "name": "Map schemes", "description": "Append source-qualified cross-scheme mappings with exact semantics, versions, method and confidence.", "inputs": [ "source concept", "target concept", "mapping profile" ], "outputs": [ "mapping assertion" ], "preconditions": [ "scheme versions pinned" ], "effects": [ "identity is not merged and weak mappings do not gain stronger inference" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-011", "SRC-024" ] }, { "id": "validate-scheme", "name": "Validate scheme", "description": "Run identity, lexical, structural, mapping, quality and profile checks against a pinned release.", "inputs": [ "scheme release", "shape profile", "quality rules" ], "outputs": [ "validation report", "quality measurements" ], "preconditions": [ "validator and profile pinned" ], "effects": [ "results remain distinct from editorial approval" ], "source_refs": [ "SRC-001", "SRC-006", "SRC-008", "SRC-010", "SRC-014", "SRC-024" ] }, { "id": "review-publish-change", "name": "Review and publish change", "description": "Review a proposal, append approval or rejection and issue an immutable release and change set.", "inputs": [ "change proposal", "review evidence", "approver" ], "outputs": [ "decision reference", "release", "change set" ], "preconditions": [ "separation of duties", "release gate passes" ], "effects": [ "prior release remains resolvable" ], "source_refs": [ "SRC-007", "SRC-009", "SRC-010", "SRC-014", "SRC-015", "SRC-019" ] }, { "id": "deprecate-replace", "name": "Deprecate, split, merge or replace", "description": "Append deprecation and successor relations while retaining old identifiers and affected-binding impact.", "inputs": [ "concept or scheme revision", "reason", "successors" ], "outputs": [ "lifecycle assertion", "migration map" ], "preconditions": [ "change authority", "impact assessed" ], "effects": [ "old URIs resolve and assignments are not silently rewritten" ], "source_refs": [ "SRC-001", "SRC-007", "SRC-009", "SRC-015", "SRC-016", "SRC-019", "SRC-024" ] }, { "id": "project-scheme", "name": "Project scheme view", "description": "Produce an authorized version-pinned standards projection with declared loss and round-trip limits.", "inputs": [ "scheme release", "target profile", "purpose" ], "outputs": [ "projection", "conformance report", "semantic-loss declaration" ], "preconditions": [ "authorized recipient", "target pinned" ], "effects": [ "projection is logged and canonical identities are preserved" ], "source_refs": [ "SRC-001", "SRC-002", "SRC-003", "SRC-004", "SRC-005", "SRC-006", "SRC-007", "SRC-008", "SRC-009", "SRC-010", "SRC-011", "SRC-012", "SRC-013", "SRC-014", "SRC-015", "SRC-016", "SRC-017", "SRC-018", "SRC-019", "SRC-020", "SRC-021", "SRC-022", "SRC-023", "SRC-024" ] } ], "composition": [ { "target": "WM-XCT-020 Classification Binding", "relation": "REFERENCE", "purpose": "Resolve assignments of external objects to concepts while the registry parent direction remains under review.", "required": false, "source_refs": [ "SRC-001", "SRC-011", "SRC-015", "SRC-024" ] }, { "target": "Classified object, evidence, policy, dataset, distribution and search-index masters", "relation": "REFERENCE", "purpose": "Resolve external referents, sources, governance and delivery context without importing their lifecycles.", "required": false, "source_refs": [ "SRC-007", "SRC-009", "SRC-015", "SRC-016", "SRC-019", "SRC-020" ] }, { "target": "W3C SKOS Reference and Primer", "relation": "ALIGN", "purpose": "Project concepts, schemes, labels, notations, notes, semantic relations, collections, mappings and integrity conditions.", "required": false, "source_refs": [ "SRC-001", "SRC-002" ] }, { "target": "RDF Schema 1.1, OWL 2 and JSON-LD 1.1", "relation": "ALIGN", "purpose": "Project linked-data classes, properties, axioms, annotations, contexts, language maps and graph serialization.", "required": false, "source_refs": [ "SRC-003", "SRC-004", "SRC-005" ] }, { "target": "SHACL, PROV-O and DQV", "relation": "ALIGN", "purpose": "Project validation, attribution, revision, invalidation and quality measurement semantics.", "required": false, "source_refs": [ "SRC-006", "SRC-007", "SRC-008" ] }, { "target": "DCAT 3, DataCite 4.7 and RO-Crate 1.3", "relation": "ALIGN", "purpose": "Project catalog, distribution, persistent metadata and portable release packaging views.", "required": false, "source_refs": [ "SRC-009", "SRC-019", "SRC-020" ] }, { "target": "ISO 25964 parts 1 and 2", "relation": "ALIGN", "purpose": "Project multilingual thesaurus construction, maintenance, exchange and cross-vocabulary mapping profiles.", "required": false, "source_refs": [ "SRC-010", "SRC-011" ] }, { "target": "ISO 704:2022, ISO 1087:2019 and NISO Z39.19", "relation": "ALIGN", "purpose": "Project terminology, concept, designation, definition and controlled-vocabulary management profiles.", "required": false, "source_refs": [ "SRC-012", "SRC-013", "SRC-014" ] }, { "target": "DCMI Metadata Terms and Library of Congress MADS/RDF", "relation": "ALIGN", "purpose": "Project vocabulary metadata, authority data, variants, schemes, collections and RWO separation.", "required": false, "source_refs": [ "SRC-015", "SRC-016" ] }, { "target": "BCP 47 language tags and matching", "relation": "ALIGN", "purpose": "Project language-tag identity, validation, filtering and lookup for labels and notes.", "required": false, "source_refs": [ "SRC-017", "SRC-018" ] }, { "target": "ODRL 2.2, RFC 3339 and RFC 8785", "relation": "ALIGN", "purpose": "Project rights constraints, unambiguous clocks and deterministic JSON serialization.", "required": false, "source_refs": [ "SRC-021", "SRC-022", "SRC-023" ] }, { "target": "ISO/IEC 11179-3:2023", "relation": "ALIGN", "purpose": "Project registry-item identification, designation, definition, registration, classification and mapping facilities.", "required": false, "source_refs": [ "SRC-024" ] } ], "serviceLayers": { "dimension": { "owner_package_requirements": [ "Declare the Dimension owner, scheme owner, publisher, vocabulary steward, concept editors, mapping reviewers, release approvers and access roles.", "Register authoritative scheme, concept, label, notation, relation, mapping, status, language, license, validation and projection profiles.", "Register classified-object and classification-binding masters separately from scheme content.", "Pin subject, language, jurisdiction, reasoning, validation, serialization and exchange profiles." ], "namespace_guidance": "Mint scheme, release, concept, label assertion, relation, collection, mapping, proposal, validation and projection identifiers only in the adopting Dimension namespace; preserve classified-object, binding, evidence, policy, dataset and index identities as typed external references.", "registry_links": [ "https://ver.cy/models/", "https://ver.cy/model-agent-protocol.md", "Dimension-local scheme, namespace, language, relation, mapping, status, license, access, retention and provenance registries" ] }, "canon_and_patch": { "canonicalization_rules": [ "Canonicalize by registry ID, model version, authoritative scheme identifier and namespace, immutable release, concept URI, assertion identity, owner and source; never use a label, notation, path, filename or hash alone as identity.", "Keep scheme, concept, label, notation, semantic relation, collection, mapping, classified object and classification binding distinct." ], "patch_rules": [ "Additive extensions use a Dimension-owned namespace and declare target node, relation semantics, language, authority, source, rationale, access, time and interoperability impact.", "Breaking changes require a new release, immutable change set, migration and mapping files, compatibility declaration and continued resolution of prior URIs and assignments." ], "compatibility_rules": [ "Consumers may ignore unknown additive fields only when scheme and concept identity, labels, definitions, relation semantics, mapping, lifecycle and access meaning remain intact.", "SKOS, RDF, RDFS, OWL, JSON-LD, MADS, DCMI, DCAT, DataCite and RO-Crate mappings pin source and target versions and declare transformed, omitted, inferred or non-round-trippable values." ] }, "artifact_rules": { "identity_priority": [ "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." ], "timestamp_rule": "Record event timestamps in RFC 3339 with seconds and an explicit UTC offset or Z; keep proposal, review, approval, issue, effective, publication, deprecation, correction and ingestion times distinct.", "serial_naming_rule": "Name serial artifacts as {scheme-id}--{artifact-kind}--{release-or-assertion-id}; never use a date, title, label, notation, filename or hash alone as identity.", "integrity_rule": "Store digest, media type, byte length, issuer, namespace, source and vocabulary versions, language, scope, clocks, provenance, assurance, license and access marking for each retained serial artifact." }, "policies": [ "The adopting Dimension declares who may register namespaces, define concepts, manage labels, assert relations, create mappings, validate, approve releases, deprecate, disclose, retain and tombstone scheme records.", "Every published release requires stable scheme and concept identities, namespace, profile, purpose, scope, owner, labels, definitions, relation semantics, change set, validation and provenance as applicable.", "Agents never infer concept identity from a label or code, part-of from broader, equivalence from close mapping, or universal authority from publication.", "Classified objects, classification bindings, source evidence, policies, datasets and indexes remain external masters.", "Automated agents may append low-risk candidate mappings, lexical checks and projections under delegation, but namespace creation, release approval, destructive change and protected disclosure require accountable authority." ], "crud": { "read": [ "Resolve active Dimension, purpose, role, scheme and release, language, hierarchy and mapping inference profile, assurance, license and access policy; return the minimum permitted projection." ], "create": [ "Create stable scheme and concept identities, namespace, profile, scope, owner, language and explicit unknowns before adding labels, relations or mappings." ], "update": [ "Append an immutable label, definition, relation, mapping, lifecycle or correction assertion with actor, authority, reason, source, RFC 3339 effective time and predecessor." ], "delete": [ "Apply policy, licensing, dispute, assignment-impact, audit, retention and legal-hold rules; tombstone eligible scheme-owned assertions while preserving URI resolution, material provenance and non-cascading external bindings." ] }, "roles": [ { "name": "Dimension owner", "responsibilities": [ "Own namespace, mastership, delegation, access, retention and federation rules." ] }, { "name": "Scheme owner or publisher", "responsibilities": [ "Own purpose, scope, authority, releases, license and public commitments." ] }, { "name": "Vocabulary steward", "responsibilities": [ "Own scheme profile, concept model, relation semantics, lifecycle and editorial policy." ] }, { "name": "Concept editor or terminologist", "responsibilities": [ "Propose identifiers, definitions, labels, notations, notes and internal relations." ] }, { "name": "Mapping curator", "responsibilities": [ "Own mapping methods, evidence, confidence, review and conflict handling." ] }, { "name": "Release approver", "responsibilities": [ "Own change-set acceptance, validation gate, effective time and publication decision." ] }, { "name": "Consumer or classifier", "responsibilities": [ "Use pinned releases and keep external classification bindings in their owning model." ] }, { "name": "Reviewer or auditor", "responsibilities": [ "Review authority, quality, mappings, changes, access and retention without rewriting originals." ] } ], "access": { "default_rule": "Deny mutation and sensitive disclosure unless active Dimension, role, purpose, scheme sensitivity, jurisdiction, license and field policy grant the action; expose the minimum necessary projection.", "scopes": [ "bundle", "layer", "finding", "artifact" ], "exceptions": [ "Emergency or legally compelled access must be grounded, time-limited, purpose-bound, attributable, independently reviewed and unable to erase immutable scheme, release, mapping, dispute or legal-hold evidence." ], "audit_requirements": [ "Log actor, role, purpose, scheme and release identity, action, decision, policy and vocabulary versions, RFC 3339 timestamp with offset, affected concepts or mappings, source evidence and outcome for privileged mutation or disclosure." ] }, "agents_bootstrap": { "filename": "AGENTS.md", "required_fields": [ "Name", "Type", "Specification URL", "Storage type URL", "Interface URL", "Processes URL" ], "read_order": [ "Read the nearest Dimension-owner AGENTS.md, active scheme, release, language, hierarchy and mapping profile, authorities, license, access and retention rules.", "Read this model AGENTS.md, pinned spec.yaml and required classification-binding, evidence, policy, dataset and index instructions before mutation." ] } }, "coverage": { "claim": "WM-KNW-018 covers a governed versioned Taxonomy / Classification Scheme with scheme and concept identity, namespace, profile, scope, labels, definitions, notations, hierarchy, associations, facets, collections, mappings, lifecycle, change sets, governance, validation, quality, rights, retention and loss-aware interoperability. Domain, language, licensing, reasoning and independent-review questions remain deferred.", "confidence": "medium", "checklist": [ { "dimension": "identity", "status": "covered", "notes": "Scheme, release, concept, label assertion, relation, mapping, proposal, validation and successor identities remain distinct." }, { "dimension": "classification and definition", "status": "covered", "notes": "Taxonomy, thesaurus, classification, controlled list, synonym ring, ontology and hybrid profiles are explicit." }, { "dimension": "direct properties", "status": "covered", "notes": "Namespace, purpose, scope, language, labels, definitions, notations, relations, mappings, status and license are covered." }, { "dimension": "recognition and observation", "status": "covered", "notes": "Agents distinguish concepts through stable URIs, definitions, characteristics, scheme membership and profile rules rather than labels alone." }, { "dimension": "lifecycle", "status": "covered", "notes": "Draft, approved, published, deprecated, superseded and retired scheme and concept states preserve releases and change sets." }, { "dimension": "relationships", "status": "covered", "notes": "Hierarchy, association, collections, mappings, successors and external classification bindings use typed relations." }, { "dimension": "temporal", "status": "covered", "notes": "Proposal, approval, issue, effective, publication, deprecation, correction and ingestion clocks remain distinct." }, { "dimension": "spatial", "status": "covered", "notes": "Geographic scope and jurisdiction are represented when a vocabulary is location-bound; geometry remains external." }, { "dimension": "provenance", "status": "covered", "notes": "Sources, editors, mappers, methods, evidence, decisions, changes, validations and releases are linked." }, { "dimension": "ownership", "status": "covered", "notes": "Scheme authority, concept editorship, mapping responsibility, release approval and object classification are not conflated." }, { "dimension": "validation", "status": "covered", "notes": "Identity, language, label, notation, hierarchy, cycles, mappings, shapes, quality and migration checks are explicit." }, { "dimension": "access", "status": "covered", "notes": "Role, purpose, license, sensitivity, minimum projection and audit are represented." }, { "dimension": "retention and deletion", "status": "covered", "notes": "Deprecation, dispute, assignment impact, legal hold, URI continuity and tombstones are non-cascading." }, { "dimension": "interoperability", "status": "covered", "notes": "SKOS, RDF, OWL, JSON-LD, MADS, DCMI, DCAT, DataCite and RO-Crate mappings disclose inference and loss." }, { "dimension": "capabilities and possible actions", "status": "covered", "notes": "Registration, definition, labeling, relating, grouping, mapping, validation, release, replacement and projection declare controlled effects." } ], "known_omissions": [ "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." ], "conflicts": [ "SKOS broader is an informal semantic relation and does not universally distinguish generic, instance and partitive hierarchy, so explicit profiles are required.", "SKOS exactMatch is transitive while closeMatch is not; neither should silently become OWL sameAs or object identity.", "Taxonomies, thesauri, classifications, authority files and formal ontologies differ in semantics, governance and inference and cannot share one universal conformance profile." ], "regional_assumptions": [ "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." ], "adversarial_checks": [ "Reject a scheme or concept without stable authoritative identity, namespace, release, owner, source and lifecycle state.", "Reject label, notation, file path or hash used as concept identity and reject concept used as the real-world referent.", "Reject broader silently interpreted as part-of or class subsumption without a declared hierarchy profile.", "Reject closeMatch promoted to exactMatch, OWL sameAs or transitive equivalence.", "Reject a mapping without pinned source and target schemes and releases, direction, method, actor, evidence, confidence and review state.", "Reject deprecation, split, merge or deletion that breaks URI resolution or silently rewrites external classification bindings.", "Reject namespace creation, release approval, protected disclosure or irreversible removal outside delegated authority." ] }, "researchAdjudication": { "providerMode": "single-provider-waiver", "activeProviders": [ "codex" ], "waivedProviders": [ "claude", "grok" ], "providerPolicy": { "contract_version": "1.0.0", "mode": "single-provider-waiver", "effective_at": "2026-09-06T00:00:00Z", "scope": "Canonical single-stream subject-model research after the six-workstream consolidation", "active_providers": [ "codex" ], "waived_providers": [ { "provider": "claude", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "Claude produced no result on prior 1800-second and 900-second attempts and again timed out on bounded 600-second Sonnet and 300-second Haiku passes. The owner prioritized completion over provider availability." }, { "provider": "grok", "authorized_by": "repository owner", "authorized_at": "2026-09-06T00:00:00Z", "reason": "The repository owner authorized completion without Grok when Grok is unavailable, slow or schema-invalid. Grok may still be attempted as a bounded supplemental reviewer, but its failure never blocks a valid Claude plus no-tools result." } ], "review_rule": "Codex may complete source-grounded fallback research after bounded Claude and Grok attempts fail. It requires a separate no-tools adversarial audit and remains reviewable-draft with a visible absence-of-external-review hold.", "supplemental_provider_attempts": [ { "provider": "claude", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." }, { "provider": "grok", "required": false, "maximum_attempts": 1, "failure_policy": "record-and-continue", "admission_rule": "Use only a locally schema-valid result whose sources and boundaries survive adjudication." } ] }, "boundaryDecision": { "entry_kind": "aggregate", "status": "reclassified", "rationale": "The registry-plane value standalone-mm does not identify the subject-model kind. The root owns a scheme release plus identity-dependent concepts, labels, relations, collections, mappings and change sets, so aggregate is more defensible than a single entity." }, "decisions": [ { "concept": "Taxonomy / Classification Scheme aggregate boundary", "disposition": "accepted", "rationale": "The scheme owns its governed concept graph and release history while classified objects, assignments, evidence, policy and search infrastructure remain external." }, { "concept": "WM-XCT-020 parent signal", "disposition": "held-as-reference", "rationale": "A classification binding normally points to a concept in a scheme, so parentage in the opposite direction may be navigational or reversed and cannot be approved from the frozen ledger." }, { "concept": "Concept versus real-world referent", "disposition": "kept-distinct", "rationale": "Stable concept identity, definition and labels do not replace the person, place, product or other object classified by that concept." }, { "concept": "Hierarchy profiles", "disposition": "accepted-with-explicit-profile", "rationale": "Generic, instance, partitive and informal broader relations have different semantics; transitivity, cycles and polyhierarchy must be declared and validated per profile." }, { "concept": "Exact, close and formal equivalence", "disposition": "kept-distinct", "rationale": "SKOS exactMatch, closeMatch, OWL sameAs, equivalentClass and registry mappings have different inferential consequences and never silently merge identity." }, { "concept": "Labels, notations and identity", "disposition": "kept-distinct", "rationale": "Language-tagged labels and typed notations are mutable designations; canonical concept URIs and authoritative identifiers remain the identity anchors." }, { "concept": "Deprecation, split, merge and migration", "disposition": "accepted-with-uri-continuity", "rationale": "Every structural change retains prior releases, successor mappings, impact on external bindings and resolvable identifiers rather than silently rewriting history." }, { "concept": "Standards projections", "disposition": "accepted-as-versioned-loss-aware-views", "rationale": "SKOS, RDF, OWL, JSON-LD, MADS, DCMI, DCAT, DataCite and RO-Crate projections pin versions and disclose inference and round-trip loss." }, { "concept": "Automated operation boundary", "disposition": "accepted-with-delegation", "rationale": "Agents may append low-risk candidate mappings and checks but namespace creation, release approval, destructive change and protected disclosure require authority." }, { "concept": "Provider waiver and local no-tools audit", "disposition": "accepted-with-mandatory-hold", "rationale": "One bounded Claude Sonnet attempt timed out and one bounded Grok attempt returned provider error 402. Codex separately audits the frozen validated result and comparison without acquiring new facts, so assurance remains reviewable-draft." } ], "publicationHolds": [ "Absence-of-external-review hold: one Claude Sonnet attempt timed out and one Grok attempt returned provider error 402 before producing an admissible result; no external result was admitted.", "Relation hold: WM-XCT-020 remains a reference because the registered parent direction appears navigational or reversed and requires joint boundary review.", "Boundary hold: classified objects, classification bindings, evidence, organizations, policies, workflows, datasets and search indexes remain external masters.", "Hierarchy hold: generic, instance, partitive and informal broader relations require explicit inference, cycle and polyhierarchy profiles.", "Mapping hold: exactMatch, closeMatch, sameAs, equivalentClass and registry mapping semantics remain distinct and source-target versions must be pinned.", "Language hold: multilingual labels require current BCP 47 registry validation, editorial policy and language-specific review.", "Licensing hold: ISO and other licensed vocabulary profiles require legal review before reproducing protected structures or claiming conformance.", "Interoperability hold: every standards projection requires exact release pins, conformance tests, round-trip tests and semantic-loss declarations.", "Completeness hold: the 24-source draft is broad but does not claim universal domain, linguistic, ontological, legal or operational coverage.", "Independent external review was explicitly waived by the repository owner; this codex-only result remains a reviewable draft." ], "deferredResearch": [ "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." ] }, "statistics": { "sources": 24, "bundles": 6, "layers": 12, "findings": 24, "questions": 72, "artifacts": 24, "functions": 10 } }