← Back to catalogue
Published

Standard / Spec Artifact

vr.wm-rec-005 · wm-rec-005-standard-spec-artifact

Published standards and specifications as versioned artifacts with issuer, status and scope.

World Models Information and virtual systems INF.REC.STD

Bundle → Layer → Finding → Questions Filled

3 bundles · 3 layers · 5 findings · 11 questions

Identity and edition Which artifact and which version is meant.

Edition

Issuer, designation, edition and status.

Designated edition

The artifact has an issuer, a designation and a dated or numbered edition.

  1. Which body issued the artifact, and under which designation?
  2. Which edition or version is meant, and when was it published?
  3. Is the edition current, withdrawn, superseded or a draft?

Supersession

Links between editions and to replacing artifacts.

  1. Which earlier edition does it replace, and which later one replaces it?
  2. What transition period applies between editions?
Content and scope What the artifact defines.

Normative content

Scope, normative parts and referenced artifacts.

Scope and references

The artifact states its scope and the other artifacts it normatively references.

  1. What is the stated scope of the artifact?
  2. Which other artifacts does it reference normatively, and in which editions?

Machine-readable form

Schemas, ontologies or code lists published with the artifact.

  1. Is a machine-readable form published, such as a schema or ontology file?
  2. Does the machine-readable form match the published edition?
Use and rights Who may use it and how conformance is claimed.

Licence and conformance

Licence, access terms and conformance rules.

Use terms

The artifact states its licence and how conformance may be claimed.

  1. Under which licence or access terms is the artifact available?
  2. Does the artifact define conformance classes or a test suite?

Classifiers Filled

Family
World Models
Category
Information and virtual systems
Entry kind
entity
Navigation path
NAV.INF.REC.STD
Domain
INF.REC.STD
Industry
Cross-industry
Tags
standardspecartifactinf.rec.std
Also called
N6

What it is Filled

A standard or specification artifact is a published normative document or formal model, such as an international standard, a technical specification, a data model or an ontology, treated as a versioned object with an issuer, a status and a scope. The subject is the artifact and its editions, not the requirements an organisation derives from it, the conformity of a product to it, or a general document record.

In scope

  • Work, edition and rendition identity; issuer and maintainer references; titles and designation aliases
  • Scope, normative part locators, reference pins, profile and adoption links
  • Publication status, revisions, errata, formats, rights and provenance of recorded assertions

Out of scope

  • Semantic model and ontology internals, term systems and mapping engines
  • Derived organization requirements, adoption authority, legislation, product assessments and certification decisions
  • Full-text redistribution without permission, executing embedded code, or operational instructions for dangerous subject matter

Why it exists Filled

Published standards and specifications as versioned artifacts with issuer, status and scope.

Distinguishing features Filled

  • It is the published normative artifact with editions, not the internal requirements derived from it.
  • Status and supersession are central: the same designation can point to several editions.
  • Models and ontologies are included as first-class artifacts with their own version identifiers.
  • Distinct from a certificate or conformity claim, which states that something meets the artifact.

What robots and AI may and may not do Filled

Must not

  • Reproduce paywalled standard text beyond what its licence allows.
  • Cite a withdrawn or superseded edition as current.
  • Claim conformance to an artifact without assessment evidence.
  • Alter a published artifact in place instead of issuing a new version.
  • Present a draft as an adopted standard.

Only with a human decision

  • Adopting or withdrawing an edition within the issuing body.
  • Declaring an organisation's or product's conformance.
  • Deciding which edition becomes binding in a contract or regulation.

May

  • Resolve the current edition of an artifact and its supersession history.
  • Cite artifacts with issuer, designation and edition.
  • Check that referenced editions match those the artifact requires.

Moral aspects Filled

  • Standards referenced in law should be accessible to those who must comply with them.
  • Standard-setting can favour well-resourced participants over smaller ones and the public.
  • Using outdated editions can expose people to known safety or security risks.

Who is affected

  • Implementers and users of the artifact
  • Standards bodies and editors
  • Regulators referencing the artifact
  • People protected by the requirements

Owners Filled

Steward

The standards body or specification consortium that issues and maintains the artifact.

Roles

Specification steward
Own local scope, namespace, lifecycle policy and adoption profile.
Evidence curator
Resolve designations and editions; maintain source assertions and restricted payloads.
Technical reviewer
Assess scope, reference and representation differences without claiming certification.
Rights reviewer
Review intended use, disclosure, licensing and retention constraints.
Read-only consumer
Use edition pins and observe access and assurance limits.

Master systems

  • Standards body catalogue
  • Specification repository with version history
  • Ontology registry

Links to other meta-models Filled

references

  • WM-REC-001 - Candidate generic document custody and rendition-record link; no required runtime inheritance.
  • WM-KNW-001 - Candidate semantic asset reference when the publication describes a model or ontology; reconcile N6 without merging subjects.
  • WM-REC-006 - Candidate external requirement records cite edition and clause locators; no automatic derivation or satisfaction.
  • WM-KNW-018 - Candidate scheme link for a classification specification; the scheme hierarchy remains external.

aligned

  • DCMI Metadata Terms 2020-01-20 - Conceptual metadata vocabulary mapping; no implemented RDF binding or automatic conformsTo claim.
  • PROV-O 2013-04-30 - Conceptual attribution and revision mapping; provenance does not imply endorsement.

neighbor

  • WM-KNW-001 Model / Ontology - The N6 legacy primary subject remains here. WM-REC-005 describes a published specification artifact and links a semantic asset when one exists; it does not absorb the asset registry or assume every ontology is a standard.
  • WM-REC-001 Document / Record - Generic record custody and file retention can be delegated. Issuer status, normative scope and edition lineage distinguish this subject; no automatic inheritance is ratified.
  • WM-REC-006 Requirement - A clause locator may be cited by an independently managed requirement. Recording normative parts does not create, interpret or satisfy adopter obligations.
  • WM-KNW-018 Taxonomy / Classification Scheme - A scheme can have a specification edition, but concept hierarchies and classification assignments remain external.
  • Implementation, assessment and adoption records - Separate references identify what was assessed, against which edition, and who decided adoption. An artifact status, checksum or metadata link proves none of those outcomes.

extends

  • wm-rec-001-document-record - A standard is a document record with normative status and editions.

related

  • wm-rec-006-requirement - Requirements are often derived from standards.
  • wm-knw-018-taxonomy-classification-scheme - Classification schemes are often published as specification artifacts.
  • world-n6-model-and-ontology - Split off from this legacy card on 2026-10-05; the legacy card keeps the primary subject.

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • A standard is identified by its issuer, designation and edition, such as a number with publication year.
  • Specifications and ontologies are identified by persistent URIs, often with a separate version IRI, or by a DOI.

Direct properties not applicable Not applicable

Not applicable

A standard or specification is an information artifact with no physical properties to measure.

Recognition optional Filled

  • An artifact is recognised by its issuer, designation, edition and normative language.
  • Often confused with guidance documents, drafts, or an organisation's internal policy based on it.

Capabilities and actions required Filled

  • Editions can be tracked with status and supersession.
  • Normative references can be resolved to specific editions.
  • Machine-readable forms can be validated against the published edition.

Hazards and failure modes required Filled

  • Implementing a withdrawn or superseded edition.
  • Drift between the published text and its machine-readable form.
  • Licence breaches when copying protected standard text.

Standards and interfaces required Filled

  • OWL 2 ontology and version IRIs for published ontologies.
  • Persistent identifiers such as DOI for published specifications.
  • Dublin Core metadata for describing artifacts.

Context of use required Filled

  • Used in engineering, regulation, procurement and data exchange.
  • Many standards are referenced in law, contracts and certification schemes.

Sources Filled

  1. W3C Process Document - World Wide Web Consortium
  2. DCMI Metadata Terms - Dublin Core Metadata Initiative
  3. Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words - Internet Engineering Task Force
  4. QA Framework: Specification Guidelines - World Wide Web Consortium
  5. OWL 2 Structural Specification and Functional-Style Syntax - World Wide Web Consortium
  6. RFC Format Framework - Internet Architecture Board
  7. PROV-O: The PROV Ontology - World Wide Web Consortium
  8. Date and Time on the Internet: Timestamps - Internet Engineering Task Force
  9. ISO/IEC Directives, Part 2: Principles and rules for the structure and drafting of ISO and IEC documents (ISO and IEC)
  10. W3C Process Document (W3C)
  11. OWL 2 Web Ontology Language Document Overview (W3C)

Open questions

  • Verify HTTP retrieval and current update chains, then review exact issuer, jurisdiction, language and rights profiles for each adopted artifact family.
  • Develop nested instance bindings and fixtures for duplicate titles, absent edition pins, draft status, disputed errata, cyclic references, conflicting renditions, restricted payloads and retirement.
  • Restore independent external review before any canonical or publishable-draft promotion.
  • Issuer-specific lifecycle profiles beyond selected open web examples, sector standards and national adoption rules require specialist review.
  • Nested instance schemas, runtime permissions, pinned neighbor versions, vocabulary mappings and adversarial fixtures remain unimplemented.
  • Full-text, translation, licensing, patent and legal applicability reviews are not complete; no compliance advice is asserted.
  • Direct HTTP checks were not attempted under the owner-reported sandbox block; browser retrieval is not HTTP-status verification.

Machine files

Provenance

world-models research · reviewable-draft

Built from: models/wm-rec-005-standard-spec-artifact/spec.yaml, ver-cy/world-models/card-supplements/wm-rec-005-standard-spec-artifact.json