Dataset, schema and contract
Dataset, versions, distribution, schema, contract for quality and permitted use. The catalog record is not the dataset itself.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
Bundle → Layer → Finding → Questions Missing, in the backlog
Not described yet. This gap is in the card backlog.
Note: Research contour: bundles not designed yet; questions are listed as open questions.
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseDAT
- Industry
- Cross-industry
- Tags
- EM-DAT-01W1subjectDatasetDatasetVersionDistributionDataSchemaDataContract
What it is Filled
Dataset, versions, distribution, schema, contract for quality and permitted use. The catalog record is not the dataset itself.
Why it exists Filled
Dataset, versions, distribution, schema, contract for quality and permitted use. The catalog record is not the dataset itself.
Distinguishing features Derived, awaiting review
- Data and schema versions are separate
- A contract has an owner and a consumer
- A catalog record references a dataset
What robots and AI may and may not do Derived, awaiting review
Must not
- Negative case: A new CSV file always creates a new semantic dataset.
Note: Negative case of the research brief, not yet a rule for agents.
Moral aspects Missing, in the backlog
Not described yet. This gap is in the card backlog.
Owners Filled
Steward
Ответственный за данные / аналитическую функцию
Master systems
- Data catalog
- DWH
- BI
- оркестратор данных
Links to other meta-models Filled
neighbor
- EM-AI-02
- EM-DAT-02
- EM-DAT-03
- EM-DAT-04
- EM-DAT-07
- EM-LEG-06
references
- WM-DAT-001 - conceptual-candidate
- WM-DAT-004 - conceptual-candidate
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Derived, awaiting review
- Dataset
- DatasetVersion
- Distribution
- DataSchema
- DataContract
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Hazards and failure modes required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Context of use required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Sources Filled
- W3C DCAT: dataset, distribution, catalog
- W3C PROV and Data Cube: provenance and observation
- SDMX and BI/data catalog practice: indicators, breakdowns, definitions and releases
Open questions
- What preserves identity across a new export?
- How to distinguish a schema from field semantics?
- When is a contract change incompatible?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-dat-01/brief.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.