In Australia we have several initiatives of government that apply rules to items in catalogues that would be best described as ODRL policies, not licenses, which motivates the use of odrl:hasPolicy. One current example is a catalogue that is storing data generated within a project but which is only released publicly after some time. So the Use Case is: "I am a catalogue manager and I want to encode notes on data publication permissions being enabled 6 months after dataset creation. I want to use the primary catalogue model (DCAT) rather than auxillory recording system" This could be recorded something like this: ``` :Dataset_X dct:license <http://linked.data.gov.au/license/CC-BY-4.0> ; odrl:hasPolicy [ a odrl:Policy ; rdfs:label "Access to data granted 6 months after lodgement" ; odrl:permission [ odrl:action [ ...define the publishing action... ] ; odrl:constraint [ odrl:leftOperand xsd:dateTime ; odrl:operator "gt" ; odrl:rightOperand :Dataset_X_created_date + :6_months ] ] ] ``` Note that this is example is close to an ODRL Best Practice case <http://w3c.github.io/poe/bp/>, Example 1.2B -- GitHub Notification of comment by nicholascar Please view or discuss this issue at https://github.com/w3c/dxwg/issues/114#issuecomment-382381052 using your GitHub accountReceived on Wednesday, 18 April 2018 13:11:29 UTC
This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:28:22 UTC