Can additional identifiers be added to support a richer expression of product details? Assuming data products become ubiquitous and the structure and purpose of data products evolves then the labelling/identification may also evolve. The overall/end-to-end product handling environment itself should become more standardised (e.g. considering/speculating on an architecture, but potential future need may arise to for large scale catalogs & product discovery methods, product stores, data product supply chains, data economy etc.)
DataProduct productionProcessDescription. Is this needed?
Additional information. For example, data quality details for the data. General product details, product data sheets etc. These may not be of interest to everyone, and not necessarily needed to consume the data distribute through the service.
Additional roles beyond owner - e.g help contacts. But again, may need to consider future potential requirements
Is it only the dataset that has associated policy? Why not dataservice?
Type for Dataproduct isn't defined
In DataSet type, what does 'genre' mean?
In distribution format, is this a file, or a data structure encoding?
DataProductLifecycleStatus. Why not also retired? Also, could be recalled and other status details.
Comments from CDMC+ Data Products Workstream