← Catalogue
World Models · legacy example

Model & Ontology

This meta-model describes models and ontologies as first-class objects of the world: meta-models, schemas, vocabularies and ontologies with registered identity, versions, semantic fingerprints, alignments to other models, and assessed conformance. It is its own model because the ecosystem's semantic assets need the same registry discipline as any other asset, and because datasets, software and standards all point into this registry rather than describing their schemas ad hoc.

AI YAMLAGENTS.mdSource
IDworld.n6-model-and-ontology
Version history0.2.0-legacy
CategoryReference example
IndustryCross-industry
Domainknowledge-information
Tagsmodel, ontology
Data structure

Bundles and layers

Bundle

registry

Who the model is and which state it is in

Layers

modelIdentity`: models, kinds, stewards, namespaces · `versionAndFingerprint`: released versions and their semantic fingerprints

Bundle

semantics

What the model says and how it relates

Layers

structureDescription`: described bundles, classes, terms · `mappingAndAlignment`: declared alignments between model versions

Bundle

conformance

Whether the model meets its claims

Layers

conformanceProfile`: profiles, levels, claims · `validationEvidence`: validation runs and reports

Findings

Catalogue-native findings must describe the information grouped by each layer. This legacy version does not declare them separately.

Questions & artifacts

Questions, artifact requirements and serial naming rules are required by Vercy vNext; they remain unassigned in this reference version.

Service layers

How this specification operates

Dimension & namespace

  • REFERENCE `world.dataset` (N3): datasets resolve their schema references against this registry.
  • REFERENCE `world.softwareProduct` (N4): implementations and validators of registered models are software products.
  • REFERENCE `world.identifierNaming` (N8): namespace URIs and model identifiers come from registered schemes.
  • REFERENCE `world.documentRecord` (N1): specification texts behind a version are governed documents.
  • imports: meta-universe-mmas (ALIGN): registered meta-models are described using the MMAS composition hierarchy.
  • imports: w3c-owl (REFERENCE): formalism referenced for ontology-kind entries.
  • imports: w3c-skos (REFERENCE): formalism referenced for vocabulary and concept-scheme entries.

Canon, patches & standards

  • REFERENCE `world.dataset` (N3): datasets resolve their schema references against this registry.
  • REFERENCE `world.softwareProduct` (N4): implementations and validators of registered models are software products.
  • REFERENCE `world.identifierNaming` (N8): namespace URIs and model identifiers come from registered schemes.
  • REFERENCE `world.documentRecord` (N1): specification texts behind a version are governed documents.
  • imports: meta-universe-mmas (ALIGN): registered meta-models are described using the MMAS composition hierarchy.
  • imports: w3c-owl (REFERENCE): formalism referenced for ontology-kind entries.
  • imports: w3c-skos (REFERENCE): formalism referenced for vocabulary and concept-scheme entries.

Artifact formats & serial data

Format-independent core. Concrete artifact formats and naming prefixes are not declared in this legacy version.

Policies & accepted processes

  • `modelUsageLicenseContract`: license terms for reuse of a registered model.
  • `registryListingContract`: terms between steward and registry operator for listing and updating entries.
  • `conformanceAssessmentContract`: engagement with an assessor for validation and certification.

Read / add / edit / delete

CRUD procedures and interface bindings are not declared in this legacy version.

Ownership, roles & access

The neutral owner archetype is the model steward, the party accountable for a model's evolution and claims; the registry operator lists entries without owning them. Access to non-public drafts and evidence is always granted by the steward through the catalogue's S1/S2 ownership and access models, with assessment activity audited via S4.

Existing assembly

Objects, relationships, events and projections

Objects

  • `model`: a registered model, schema, vocabulary or ontology; key attributes: modelId, namespaceRef, modelKind, stewardRef.
  • `modelVersion`: a released state of a model; key attributes: version, releasedAt, changeClass, status.
  • `namespace`: the naming scope a model is declared in; key attributes: namespaceUri, prefix, authorityRef.
  • `fingerprint`: the semantic fingerprint of a version; key attributes: algorithm, digest, computedAt.
  • `mapping`: a declared alignment between two model versions; key attributes: mappingType, coverage, direction.
  • `conformanceClaim`: a claimed level against a profile; key attributes: profileRef, level, claimedBy, claimedAt.
  • `validationReport`: evidence from a validation run; key attributes: validatorRef, outcome, findingsCount, runAt.

Relationships

  • `model` -> hasVersion -> `modelVersion` (1:N): the release history of the model.
  • `modelVersion` -> identifiedBy -> `fingerprint` (1:1): the fingerprint fixes the version's semantics.
  • `model` -> declaredIn -> `namespace` (N:1): naming sovereignty over the model.
  • `mapping` -> aligns -> `modelVersion` (N:N): field-level equivalences between sovereign models.
  • `modelVersion` -> extends -> `modelVersion` (N:N): specialization of an imported model version.
  • `conformanceClaim` -> claims -> `modelVersion` (N:1): the claim is about one released state.
  • `validationReport` -> verifies -> `conformanceClaim` (N:1): evidence behind the claim.

Events

  • `modelRegistered`: a model entered the registry with identity and steward.
  • `versionReleased`: a new version of a model was published.
  • `fingerprintComputed`: the semantic fingerprint of a version was fixed.
  • `mappingPublished`: an alignment between two models was declared.
  • `conformanceAssessed`: a validation run assessed a conformance claim.
  • `modelDeprecated`: the steward marked a model or version as superseded.

Projections

  • `publicRegistryView`: identity, current version, fingerprint and conformance level; omits validation findings detail.
  • `dependencyGraphView`: the extends and mapping graph between versions; omits descriptive prose.
  • `versionDiffView`: what changed between two versions of one model; omits unrelated registry entries.