Profile Best Practice
This page provides an outline of a Best Practice document covering the creation, publication and maintenance of ODRL Profiles.
State: as of 2019-07-01/MWS
Note: editors adding a new item should add their initials to it to help identifing the creator of the great idea.
What an ODRL Profile may define
- Walking through the items of ODRL Profile Definition of the ODRL Profile Mechanism and provding guidelines for defining additional things. (MWS)
- Address: further restrictions based on subclass constructs (ex:Offer rdfs:subclassOf odrl:Offer . ex:Offer must not have any obligations.) (SB)
- For defining a vocabulary for a profile: explain the difference between the ODRL Core Vocabulary and the ODRL Common Vocabulary (MWS)
- Templates for commonly-understood policies, with identifiers and possibilities to connect templates with their 'instances' (SB)
- Constraints: defined sets of LeftOperands, operators and values. For instance, a LeftOperand 'payAmount' must have the 'eq' operator and xsd:decimal as the value type and unit must be from {dbr:Euro, dbr:Dollar, ...} (SB)
Prerequisites for defining an ODRL Profile
- A globally unique identifier for the ODRL Profile - including a strategy for versioning of profile (MWS)
- stable location as a Web resource (SB)
- Results from walking through the items of ODRL Profile Definition of the ODRL Profile Mechanism (MWS)
- A vocabulary for terms beyond the ODRL Core Vocabulary (MWS)
- Testwise validation of ODRL Policies using this Profile ? (MWS)
- SHACL/SHEX expressions? (SB)
Documents defining an ODRL Profile
- (HTML) Document with a human readable specification of the ODRL Profile (MWS)
- OWL Ontology with a machine readable specification of the ODRL Profile (MWS)
- Optional: a JSON-LD context document for the use of the ODRL Profile in JSON-LD objects (MWS)
Making the ODRL Profile publicly available
- publish the Ontology file as a web resource with a persistent locator (MWS)
- publish the human readable specification document as a web resource (MWS)
- option: publish the JSON-LD context file as a web resource with a persistent locator (MWS)