EM-DAT-02 · Subject model · W2
Data product
A managed data offering with consumers, a quality promise and interfaces. The dataset itself and the pipeline are not duplicated.
Queued for research
Claude: not-started; Grok: not-started.
Research note, in Russian: Entire research brief pending
Subject boundary and candidate types
- DataProduct
- DataProductOffering
- DataConsumerAgreement
Deep research questions
- When does a dataset become a product?
- What outcome is promised to the consumer?
- How to link multiple datasets and interfaces?
Verifiable invariants
- Purpose and owner are explicit
- The quality promise is verifiable
- A DataProduct is not a copy of a dataset
End-to-end acceptance scenario
One product delivers two datasets and an API under different terms while keeping an independent data version.
Negative case
Any table is automatically declared a data product.
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-008 · Data Catalog Entry / Data Product · 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.