I would like to see if there is some consistency across industries in terms of definitions for data asset, data domain, and data product?
Sort By:
Oldest
Director of Data & AI Services in IT Services8 days ago
To add to David's response above, data product like any other product should have product specifications documented. This should contain details of the data product and if it is meant to be shared, should have data sharing agreements.
Chief Data Officer in Software5 days ago
The short answer here is 'no'. For an industry that is focused on managing meaning/semantics, we do a horrible job at having any consistent approach to doing so. When it comes to data products, the definition exists on a spectrum. On one side of the spectrum, data products are focused on enabling scalability within a data function where the product is essentially a raw material which is used by a downstream consumer to create an analytical insight. On the other side of the spectrum, data products are finished goods that are consumed by end users (typically in a business role), where the primary goal is to drive business value / business outcomes.
Data assets and data products are closely related, data domains are a completely different beast.
Data assets are sets of data (operational or analytical) that provide value to the organization. Personally, I really only refer to data assets in an analytical sense.
Data Products are Data Assets that have a product mindset applied to them. Meaning they are something that will grow and evolve over time, they are measured for usage and benefit, etc. Not all Data Assets are Data Products.
Data Domains are just another term for a Data Subject. They are the enterprise level data categories that a company has. E.g., customer, business partner, order, employee, etc. These will have data standards, attributes, relationships, etc. defined per domain.
Hope that helps!