Data product¶
A data product is an owned, discoverable data capability with a defined purpose, meaningful interfaces, explicit promises and a managed lifecycle. Its users should be able to understand what it means, whether it fits their use and what happens when it changes.
A dataset alone does not meet that definition. Ownership, semantics, quality evidence, access rules, support and change expectations must travel with the usable interface.
The source domain should retain authority for the meaning of the events and entities it knows. A derived product may compose source products and take responsibility for its own transformations and promises, while preserving their provenance.
Join the argument
Agree, challenge or add evidence
Architecture improves when its assumptions are challenged. Say which kind of contribution you're making:
- Challenge I disagree because…
- Evidence We've seen this too…
- Question How would this work when…?
- Alternative Another way to approach this…
- Extension This also implies…
Please keep clients, employers and colleagues unidentifiable. Strong contributions may be quoted and credited on this site. Read the contribution guidelines and the privacy notice.
Comments are provided by giscus and stored on GitHub. Posting requires a GitHub account.