Skip to content

Commit 2cd04d6

Browse files
committed
📝 Clarify data product definition with concrete examples to broaden scope
Adds examples like dataset, dashboard, report, and benchmark to make expectations clearer for readers
1 parent 41157eb commit 2cd04d6

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

‎Data Package Manager.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,7 @@ Data is not code, but the activities of both publishers and users of datasets re
8787
- Make sure the datasets are there for the long run. This might take different forms (using a domain name, IPFS, ...).
8888
- **Subscribable**. Datasets are not just derived from upstream data, they should actually be updated every time the upstream data is updated (e.g: recomputing a metric of wildfire risk whenever new satellite imagery becomes available).
8989
- **Dual Role Support**. Recognize that data providers are often data users and vice versa, similar to how GitHub understands that code writers are also code consumers. Design interfaces and tools that support this dual role effectively.
90-
- **Data Product**. A data product is a collection of data created explicitly to be used by someone else. Incentivize data products as they are the atomic unit of consumption for data.
90+
- **Data Product**. A data product is a collection of data created explicitly to be used by someone else (dataset, dashboard, report, benchmark, ...). Incentivize data products as they are the atomic unit of consumption for data.
9191
- Data is an _experience good_. Its true value often remains uncertain until after it has been used and analyzed. This characteristic creates information asymmetries between data collectors (like local communities) and potential buyers or users, making quality assurance and standardization crucial for building digital trust in data markets.
9292

9393
## Simple Package Manager Design

0 commit comments

Comments
 (0)