diff --git a/community-vocab/community.ttl b/community-vocab/community.ttl new file mode 100644 index 0000000..13456b0 --- /dev/null +++ b/community-vocab/community.ttl @@ -0,0 +1,78 @@ +PREFIX bibo: +PREFIX dcterms: +PREFIX foaf: +PREFIX odrl: +PREFIX owl: +PREFIX profile: +PREFIX rdf: +PREFIX rdfs: +PREFIX role: +PREFIX skos: +PREFIX sw: +PREFIX vann: +PREFIX xsd: + +PREFIX odrl-comm: <#odrl-comm-namespace> + +# ------------ TODO: Ontology Metadata ------------------ # + +# ------------ Action Concepts ------------------ # + +odrl-comm:create a odrl:Action, skos:Concept ; + rdfs:isDefinedBy odrl-comm: ; + rdfs:label "Create"@en ; + rdfs:comment "To create the Asset."@en ; + skos:definition "To create the Asset."@en ; + dcterms:source . + +# ------------ Operator Concepts ------------------ # + +odrl-comm:isNotA a odrl:Operator, owl:NamedIndividual, skos:Concept ; + rdfs:isDefinedBy odrl-comm: ; + rdfs:label "Is not a"@en ; + rdfs:comment "Indicates that a given value is not an instance of the Right Operand of the Constraint."@en ; + skos:definition "Indicates that a given value is not an instance of the Right Operand of the Constraint."@en ; + skos:example "The purpose constraint of a rule can not be an instance of academic research purpose."@en ; + dcterms:source , . + +odrl-comm:seq a odrl:Operator, owl:NamedIndividual, skos:Concept ; + rdfs:isDefinedBy odrl-comm: ; + rdfs:label "Semantic equivalence"@en ; + rdfs:comment "Indicates that a given value is equal to, an instance or a subclass of the Right Operand of the Constraint."@en ; + skos:definition "Indicates that a given value is equal to, an instance or a subclass of the Right Operand of the Constraint."@en ; + skos:example "The purpose constraint of a rule can be research and development, an instance of research and development or one of its subclasses such as academic research, non-commercial research or commercial research."@en ; + dcterms:source , , . + +odrl-comm:subclass a odrl:Operator, owl:NamedIndividual, skos:Concept ; + rdfs:isDefinedBy odrl-comm: ; + rdfs:label "Subclass of"@en ; + rdfs:comment "Indicates that a given value is a subclass of the Right Operand of the Constraint."@en ; + skos:definition "Indicates that a given value is a subclass of the Right Operand of the Constraint."@en ; + skos:example "The purpose constraint of a rule can be a subclass of research and development such as academic research, non-commercial research or commercial research."@en ; + skos:note "Right operand value MUST use vocabularies that explicitely define subclass relationships, e.g., using rdfs:subClassOf."@en ; + dcterms:source , . + +# ------------ Policy Concepts ------------------ # + +odrl-comm:Preference a rdfs:Class , owl:Class, skos:Concept ; + rdfs:subClassOf odrl:Policy ; + owl:disjointWith odrl:Agreement, odrl:Offer, odrl:Privacy, odrl:Request, odrl:Ticket, odrl:Assertion ; + rdfs:isDefinedBy odrl-comm: ; + rdfs:label "Preference Policy"@en ; + rdfs:comment "A Preference Policy is a policy that contains information about the assigner's preferences over an Asset which MAY not be satisfied."@en ; + skos:definition "A Preference Policy is a policy that contains information about the assigner's preferences over an Asset which MAY not be satisfied."@en ; + skos:note "A Preference Policy MUST contain at least one Permission or Prohibition rule, an Action, a target Asset and a Party with Assigner function (in the same Permission or Prohibition). The Preference Policy MAY contain a Party with Assignee, but MUST not grant any privileges to those Parties."@en ; + skos:example "If a preference policy set by a party A does not match a request policy from party B, the request can still be accepted if party A accepts party B's request conditions."@en ; + dcterms:source , . + +# ------------ Party Concepts ------------------ # + +odrl-comm:issuedPolicy a rdf:Property, owl:ObjectProperty, skos:Concept ; + rdfs:isDefinedBy odrl-comm: ; + rdfs:label "Issued policy"@en ; + rdfs:comment "Indicates that a Party issued a Policy."@en ; + skos:definition "Indicates that a Party issued a Policy."@en ; + skos:example "Method used to indicate that a party, e.g., Alice, has issued a policy, e.g., related to her preferences for data sharing."@en ; + rdfs:domain odrl:Party ; + rdfs:range odrl:Policy ; + dcterms:source . \ No newline at end of file diff --git a/community-vocab/index.html b/community-vocab/index.html index da95e31..04e68b2 100644 --- a/community-vocab/index.html +++ b/community-vocab/index.html @@ -14,10 +14,10 @@
-

This document

- -

- +

+ This document contains a community-supplied set of general terms that are useful across difference use cases + where the usage of ODRL policies is desirable. +

diff --git a/formal-semantics/index.html b/formal-semantics/index.html index 4908e28..6378655 100644 --- a/formal-semantics/index.html +++ b/formal-semantics/index.html @@ -246,7 +246,7 @@

Example of a constrained permission

This is the situation of the following case, similar to Example 13 in the ODRL Information Model 2.2. The permission below allows the target asset http://example.com/document:1234 to be distributed, it includes the constraint that the permission may only be exercised until 2018-01-01. - The permission is granted by the organization identified by the URL http://example.com/org:616. + The permission is granted by the organization identified by the URL http://example.com/party/16. 

@@ -319,9 +319,9 @@ 
Example of a constrained permission

         
         
Monitoring scenario:
 
         
    
-            
  • If such an action belongs to the class of actions regulated by the Permission and the Permission is active, 
+            
  • (E-13-3)If such an action belongs to the class of actions regulated by the Permission and the Permission is active, 
             then the action is permitted and the Permission is used by the performed action.
    • 
-            
  • If such an action belongs to the class of actions regulated by the Permission and the Permission is inactive,
+            
  • (E-13-4)If such an action belongs to the class of actions regulated by the Permission and the Permission is inactive,
             then nothing can be deduced.
    • 
         

         
@@ -386,13 +386,13 @@ 
Example of a permission whose permitted action is refined
Access control scenario:
    
-            
  • (E14-1-ac) If such the attempted action belongs to the class of actions regulated by the Permission
+            
  • (E14-1) If such the attempted action belongs to the class of actions regulated by the Permission
             (i.e.: its type is print, 
             its object is equale to http://example.com/document:1234 and 
             its resolution is less than or equal to 1200 dpi (it satisfies the refinement))
             then the Permission is active and the attempted action can be performed.
             
    • 
-            
  • (E14-2-ac) If such the attempted action belongs to the class of actions regulated by the Permission, 
+            
  • (E14-2) If such the attempted action belongs to the class of actions regulated by the Permission, 
             but the refinement of the action is not satisfied (i.e. its resolution is more than 1200 dpi), 
             then the Permission is inactive. 
             Assuming that only this Permission is considered (this is because other permissions could regulate this action), 
@@ -458,7 +458,7 @@ 
    Example of a permission whose permitted action is refined
    
 
         
    Evaluation of conditions
     
         
    
-            A Condition is fulfilled if all its constraints are satisfied and
+            A Condition (duty) is fulfilled if all its constraints are satisfied and
             if its action, with all refinements satisfied, has been performed.