EM-DAT-01 · Subject model · W1
Dataset, schema and contract
Dataset, versions, distribution, schema, contract for quality and permitted use. The catalog record is not the dataset itself.
Queued for research
Claude: not-started; Grok: not-started.
Research note, in Russian: Entire research brief pending
Subject boundary and candidate types
- Dataset
- DatasetVersion
- Distribution
- DataSchema
- DataContract
Deep research questions
- What preserves identity across a new export?
- How to distinguish a schema from field semantics?
- When is a contract change incompatible?
Verifiable invariants
- Data and schema versions are separate
- A contract has an owner and a consumer
- A catalog record references a dataset
End-to-end acceptance scenario
One dataset with two delivery formats and a schema change preserves provenance and explicit compatibility.
Negative case
A new CSV file always creates a new semantic dataset.
Approaches to compare
- W3C DCAT: dataset, distribution, catalog
- W3C PROV and Data Cube: provenance and observation
- SDMX and BI/data catalog practice: indicators, breakdowns, definitions and releases
Candidates in the live catalogue
- WM-DAT-001 · Dataset · 0.3.0-research.1 · installable
Semantic fit requires boundary research; a published model does not by itself complete this card. - WM-DAT-004 · Data Schema / Data Contract · 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.