EM-KNW-01 · Subject model · W1
Document, knowledge and terminology
Information object, revisions, publications, concepts and definitions. The file is a carrier, while claims and decisions have their own references.
Queued for research
Claude: not-started; Grok: not-started.
Research note, in Russian: Entire research brief pending
Subject boundary and candidate types
- Document
- DocumentRevision
- KnowledgeArticle
- Concept
- TermDefinition
Deep research 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?
Verifiable invariants
- A revision has provenance
- Matching words do not prove same-as
- An accepted term applies within its stated scope
End-to-end acceptance scenario
Move a document between systems while preserving revisions and two conflicting definitions of one word in different contexts.
Negative case
A page with a new URL becomes new knowledge, while identical names get merged.
Approaches to compare
- W3C PROV: claims, sources and actions
- SKOS: concepts, definitions and mapping
- DMS/wiki/ADR practice: document, version, carrier and decision
Candidates in the live catalogue
- WM-REC-001 · Document / Record · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-KNW-006 · Concept / Term · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-KNW-018 · Taxonomy / Classification Scheme · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card.
Result requirements
Every card is executed together with the full research contract: definitions, fields and cardinalities, lifecycle, sources, data mastership, rights, the five object facets, at least eight invariants, positive and negative examples, dependencies, migration and applicability limits.