← Back to catalogue
Published

Document, knowledge and terminology

EM-KNW-01 · em-knw-01

Information object, revisions, publications, concepts and definitions. The file is a carrier, while claims and decisions have their own references.

Enterprise profiles Enterprise subject EnterpriseKNW

Bundle → Layer → Finding → Questions Filled

3 bundles · 3 layers · 5 findings · 9 questions

Document and carrier The information object, apart from the files and URLs that carry it.

Identity and carriers

One document across formats, locations and systems.

Document identity

A stable identifier independent of file name and URL.

  1. Which stable identifier names this document across systems?
  2. Which files and URLs are carriers of the same document?
Revisions and publication How a document changes and when a version becomes official.

Revision history

Revisions with authors, dates and sources.

Revision

A revision with provenance and a link to the one it replaces.

  1. Who made this revision, when and from which source?
  2. Which revision is the published one, and since when?

Status

Marks for obsolete, superseded or disputed content.

  1. Is the content current, superseded or disputed, and who says so?
Concepts and terms Concepts and their definitions, each valid in a stated scope.

Terminology

Terms, definitions and mappings between vocabularies.

Concept and definition

A concept with one or more definitions bound to their scope.

  1. Which concept does this term denote in this context?
  2. Which scope or department is a definition valid in?

Concept mapping

Explicit, justified links between concepts in different vocabularies.

  1. Is the mapping exact, close or broader, and who asserted it?
  2. Do two identical words actually denote different concepts?

Classifiers Filled

Family
Enterprise profiles
Category
Enterprise subject
Entry kind
subject
Domain
EnterpriseKNW
Industry
Cross-industry
Tags
EM-KNW-01W1subjectDocumentDocumentRevisionKnowledgeArticleConceptTermDefinition

What it is Filled

Information object, revisions, publications, concepts and definitions. The file is a carrier, while claims and decisions have their own references.

Why it exists Filled

Information object, revisions, publications, concepts and definitions. The file is a carrier, while claims and decisions have their own references.

Distinguishing features Filled

  • A document is an information object; files and URLs are only carriers of it.
  • Every revision keeps its provenance, so moving between systems does not reset history.
  • Two terms are treated as one concept only by an explicit mapping, never by matching spelling.
  • Distinct from the decision and evidence contour, which records claims and choices rather than texts.

What robots and AI may and may not do Filled

Must not

  • Treat a page with a new URL as new knowledge.
  • Merge two concepts because their names match.
  • Overwrite a revision so that its earlier content and author are lost.
  • Present a definition outside the scope in which it was accepted.

Only with a human decision

  • Publishing a revision as the official version.
  • Accepting a term definition for the whole organisation.
  • Retiring a document or removing it from records.

May

  • Link files and URLs to the document they carry.
  • Propose concept mappings for a person to confirm.
  • Flag documents with no owner or with an obsolete status still in use.
  • Show conflicting definitions of one word with their scopes.

Moral aspects Filled

  • Lost provenance makes it impossible to hold anyone accountable for content.
  • Merged definitions can change the meaning of rules and contracts that rely on them.
  • Documents can contain personal or confidential data that must keep its access scope.

Who is affected

  • Authors and editors
  • Employees who rely on the knowledge
  • Records and compliance staff

Owners Filled

Steward

The knowledge and records owner who answers for documents, terms and decision logs.

Master systems

  • Document management system
  • Wiki
  • Decision log

Links to other meta-models Filled

neighbor

  • EM-KNW-02
  • EM-LEG-01

references

  • WM-REC-001 - conceptual-candidate
  • WM-KNW-006 - conceptual-candidate
  • WM-KNW-018 - conceptual-candidate

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Identified by a persistent document identifier with a revision number; concepts by a URI in their concept scheme.

Direct properties not applicable Not applicable

Not applicable

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

Recognition optional Filled

  • Marked by a title, an owner, a revision history and a publication status.
  • Often confused with the file, the web page or the storage folder that holds it.

Capabilities and actions required Filled

  • Documents can move between systems with revisions and links preserved.
  • Vocabularies can be mapped while keeping conflicting definitions side by side.

Hazards and failure modes required Filled

  • Broken links and lost history after migration.
  • Silent meaning drift when a shared term is redefined.
  • Obsolete content served as current.

Standards and interfaces required Filled

  • W3C SKOS for concepts, definitions and mappings.
  • W3C PROV-O for provenance of revisions.
  • ISO 15489 for records management.
  • Dublin Core metadata terms by DCMI, also published as ISO 15836.

Context of use required Filled

  • Used for policies, manuals, specifications, glossaries and knowledge bases.
  • Agents rely on it to cite the right version of a source.

Sources Filled

  1. W3C PROV: claims, sources and actions
  2. SKOS: concepts, definitions and mapping
  3. DMS/wiki/ADR practice: document, version, carrier and decision
  4. W3C PROV-O: The PROV Ontology - Checked live (HTTP 200) on 2026-10-07.
  5. W3C SKOS Simple Knowledge Organization System Reference - Checked live (HTTP 200) on 2026-10-07.
  6. DCMI Metadata Terms - Checked live (HTTP 200) on 2026-10-07.
  7. W3C PROV Overview - Checked live (HTTP 200) on 2026-10-07.

Open questions

  • How to separate a document from a file and a URL?
  • When do two terms denote one concept?
  • How to mark obsolete or disputed knowledge?
  • Установить границу и решение reuse/extend/new по действующим спецификациям.
  • Подтвердить semantic crosswalk, права и source mastership.
  • Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.

Machine files

Provenance

enterprise research programme · published-partial

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

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