A Data Product describes information offered for a business purpose. Record its owner, datasets, lifecycle, and terms alongside the knowledge it describes. A consumer can inspect what the offering means before requesting access.
Governed data products
Connect an information offering to its purpose, owner, inputs, outputs, and terms.
Describe the offering
Make supply and demand explicit
Input ports describe the information a product needs. Output ports describe the data or services it supplies. A consuming Use Case records why that information is needed and connects that demand to the supplying product.
The fulfillment workspace remains a governed boundary. Publishing a description does not make its underlying records public.
Its Solid/LWS pod interface provides standards-based resource access alongside the product's declared business ports.
Connect the next step
Discovery helps consumers find an offering. Data usage contracts explain the conditions for using it. A particular product belongs in the Registry, where it can be described in its own business context.
For the standards mapping and its assessment boundary, read DPROD in Legra. To prepare the underlying data, start with loading a named graph.
Developer reference
Technical details
Standards-based product contract
OMG DPROD models data products, ownership, lifecycle and input/output ports. W3C DCAT describes associated datasets and data services. The Data Product retains its stable Use Case identity rather than minting a second capability identity.
A port names a service and input/output contract. A consuming Use Case references that supplied capability; resolution still checks deployment, grants and prices. The port is not unrestricted SPARQL access to the fulfillment workspace.
Version product metadata with its governed context. Publishing a DCAT service description exposes discovery metadata; it neither issues credentials nor accepts a usage contract.