The following is an example of a simple ecosystem of assets (from DCAT and DPROD) and a policy the dcat:DataProduct.
We will use our DSLs to first showcase each element in a easy to understand way, followed with a full continuous TTL output at the end.
DPROD
DataProduct
For simplicity, the product shown below contains only the relevant elements for this example.
As can be seen, multiple policies are associated with the product (so cardinality within properties is visible). We only will focus on the 2nd one from the list in this post.
DCAT
Dataset
Here are the two associated datasets for the input/output dataset from above. The redlining indicates that there are several missing properties and the asset is not capable of a release.
For simplicity, the ingestion of external assets is not part of this flow and every element is already part of the example_bank.
DataService
Here we follow with the Services associated to the corresponding datasets:
As you can see, the descriptions support multiple entries, in multiple languages.
Distribution
Here we have the distributions as final elements, with a few properties:
ODRL
Policy
We create a policy that will allow the grouping of performance rules:
And use it as the ancestor for our rights-management policies:
Our policy describes that it is prohibited to aggregate by any recipient of the party collection (demo_exchange), but that those recipients can use it up to 10 times. With a duty to compensate (that is found in a pricing list that references the data product.
It finally showcases that it has references to the same instance of a constraint (dm_cnstrint_one) in multiple rules.
CAVEAT: an ODRL gap has been identified, there is no equivalent in TTL for action refinements (in the file odrl:Action) at this stage.
Leave a Reply