← Back to catalogue
Published

Classifications, profiles and crosswalk

EM-XCT-09 · em-xct-09

A contract for concept schemes, codes, versions, profiles and exact/broad/narrow/related mapping relations.

Enterprise profiles Enterprise contract EnterpriseXCT

Bundle → Layer → Finding → Questions Filled

2 bundles · 3 layers · 3 findings · 8 questions

Schemes and codes Concept schemes, their versions and the codes assigned from them.

Code assignment

A code from a pinned version of a scheme.

Pinned scheme version

The scheme and version a code comes from.

  1. Which scheme and which version does this code come from?
  2. Is the code deprecated, and which code replaces it, if any?
Mappings and profiles Relations between codes in different schemes and narrowing profiles.

Semantic mapping

Exact, broad, narrow or related relations with justification.

Mapping strength

The mapping relation chosen and the evidence behind it.

  1. Is the mapping exact, broader, narrower or only related?
  2. What justifies an exact match beyond a similar name?
  3. Was an ambiguous mapping sent to manual review?

Profile constraint

A profile that narrows conditions without changing identity.

Profile conformance

Whether an instance satisfies a profile while keeping its base identity.

  1. Which base model does the profile narrow, and which constraints does it add?
  2. Does the profile reject a prohibited instance?
  3. Does the instance keep its identity under the base model?

Classifiers Filled

Family
Enterprise profiles
Category
Enterprise contract
Entry kind
contract
Domain
EnterpriseXCT
Industry
Cross-industry
Tags
EM-XCT-09W0contractClassificationSchemeCodeAssignmentSemanticMappingProfileConstraint

What it is Filled

A contract for concept schemes, codes, versions, profiles and exact/broad/narrow/related mapping relations.

Why it exists Filled

A contract for concept schemes, codes, versions, profiles and exact/broad/narrow/related mapping relations.

Distinguishing features Filled

  • A similar name never establishes an exact match; exact mappings need explicit justification.
  • Codes always refer to a pinned version of their scheme, so deprecations do not change past meaning.
  • A profile narrows what is allowed but does not silently change the identity of the objects it constrains.
  • Mapping relations are graded as exact, broad, narrow or related rather than a single yes or no.

What robots and AI may and may not do Filled

Must not

  • Replace an old identifier automatically with the nearest new one.
  • Declare an exact match on the basis of a similar name.
  • Use a code without pinning the scheme version.
  • Change the identity of an object by applying a profile.
  • Remap deprecated codes in past records without keeping the original.

Only with a human decision

  • Approving exact mappings that drive automated decisions.
  • Resolving ambiguous mappings of deprecated codes.
  • Publishing a new profile that narrows a shared model.

May

  • Propose mappings with their relation type and justification.
  • Route ambiguous or deprecated codes to manual review.
  • Validate instances against a profile and report violations.
  • Report the scheme version behind every code assignment.

Moral aspects Filled

  • Wrong mappings can misclassify people, products or risks and change how they are treated.
  • Silent recoding of past records undermines trust and auditability.

Who is affected

  • Users of classified records
  • Owners of the classification schemes
  • People and organisations whose records are coded

Owners Filled

Steward

The curator of the meta-model catalogue who answers for classification schemes, mappings and profiles.

Master systems

  • Model registry
  • Source configuration files
  • Dependency lock files
  • Policy store

Links to other meta-models Filled

references

  • WM-XCT-020 - conceptual-candidate
  • WM-KNW-018 - conceptual-candidate

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • A code is identified by scheme identifier, scheme version and code value.
  • A mapping is identified by source code, target code and relation type.

Direct properties not applicable Not applicable

Not applicable

Enterprise record contour: physical properties belong to referenced world models.

Recognition optional Filled

  • A mapping record names two codes, a relation type, a justification and a status.
  • Often confused with a lookup table that has no relation type or version.

Capabilities and actions required Filled

  • Records can be translated between schemes with known loss of precision.
  • Deprecated codes can be traced to their replacements.

Hazards and failure modes required Filled

  • False equivalence from name-based matching.
  • Meaning drift when scheme versions are not pinned.
  • Profiles that quietly redefine shared objects.

Standards and interfaces required Filled

  • W3C SKOS for concept schemes and exactMatch, broadMatch, narrowMatch and relatedMatch.
  • ISO 25964 from ISO for thesauri and interoperability with other vocabularies.
  • W3C SHACL and the W3C Profiles Vocabulary for profile constraints.

Context of use required Filled

  • Used wherever several classification schemes or model versions must be reconciled.
  • Common in product, industry, risk and occupational classifications.

Sources Filled

  1. Current Vercy protocol/MMAS/whole-object and the published WM-XCT
  2. W3C PROV/SKOS/SHACL/ODRL where applicable
  3. Practice of source connectors, versioned schemas and policy enforcement
  4. W3C SKOS Simple Knowledge Organization System Reference - Checked live (HTTP 200) on 2026-10-07.
  5. W3C SKOS Simple Knowledge Organization System Primer - Checked live (HTTP 200) on 2026-10-07.
  6. W3C The Profiles Vocabulary - Checked live (HTTP 200) on 2026-10-07.

Open questions

  • When is a mapping truly exact?
  • How to carry over a deprecated code?
  • How does a profile preserve identity while narrowing conditions?
  • Установить границу и решение reuse/extend/new по действующим спецификациям.
  • Подтвердить semantic crosswalk, права и source mastership.
  • Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.

Machine files

Provenance

enterprise research programme · published-partial

Built from: enterprise/models/em-xct-09/brief.json, ver-cy/world-models/card-supplements/em-xct-09.json

Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.