Re: a clarification regarding occurrence of assigner and assignee in Policy vs Rule

Hi, I think the issue you are raising is what is the difference when using Assignee/Assigner inside a “Rule” (like Duty) versus inside the “Policy” 
(as these two examples show)

Section 2.1 says "An ODRL Policy MAY also declare properties which are shared and common to all its Rules.”

In essence, the Policy-level Assignee/Assigner apply to all the enclosed Rules, but then can be augmented at the Rule level as well.

It is more fully described in Section 2.7: https://w3c.github.io/poe/model/#composition

Let us know if you have any further questions…

R


> On 5 Feb 2024, at 18:10, Sridhar Krishnamurthy <ksridhar@amagi.com> wrote:
> 
> Respected Madam/Sir,
> 
> i am a newbie to ODRL and hence this question.
> 
> context
> =======
> 
>     We see the definition of assigner and assignee as follows:
> 
>     assignee
>     ========
> 
>     :assignee
>         a rdf:Property , owl:ObjectProperty, skos:Concept ;
>         rdfs:isDefinedBy odrl: ;
>         rdfs:subPropertyOf :function ;
>         rdfs:label "Assignee"@en ;
>         skos:definition "The Party is the recipient of the Rule."@en ;
>         rdfs:domain [
>             a owl:Class ;
>             owl:unionOf ( :Rule :Policy ) ;
>         ] ;
>         rdfs:range :Party .
> 
>     assigner
>     ========
> 
>     :assigner
>         a rdf:Property , owl:ObjectProperty, skos:Concept ;
>         rdfs:isDefinedBy odrl: ;
>         rdfs:subPropertyOf :function ;
>         rdfs:label "Assigner"@en ;
>         skos:definition "The Party is the issuer of the Rule."@en ;
>         rdfs:domain [
>             a owl:Class ;
>             owl:unionOf ( :Rule :Policy ) ;
>         ] ;
>         rdfs:range :Party .
> 
>     i.e. the assigner and assignee property can occur for a Rule
>     or Policy instance
> 
> 
> question(s)
> ===========
> 
> (1) What is the semantic difference between
> 
>     (a) when they occur as properties of a Duty (Rule) instance
>         as in EXAMPLE 20 of section https://www.w3.org/TR/odrl-model/#duty
> 
>     #....
>     "obligation": [{
>           "assigner": "http://example.com/org:43",
>           "assignee": "http://example.com/person:44",
>     #....
> 
>                     AND
> 
>     (b) when they are occur as properties of a Agreement (Policy) instance 
>         as in EXAMPLE 21 of section https://www.w3.org/TR/odrl-model/#duty
> 
>     #...
>     "@type": "Agreement",
>     "uid": "http://example.com/policy:42B",
>     "profile": "http://example.com/odrl:profile:09",
>     "assigner": "http://example.com/org:43",
>     "assignee": "http://example.com/person:44",
>     #...
> 
> (2) Can some use-case(s)/example(s) be stated to highlight the difference
>     if any ?
> 
> (3) please do point me to a message in public-odrl-contrib or 
>     public-odrl-contrib in case this has already been answered as my
>     searches in these groups did not yield the required answer.
> 
> 
> thank you
> 
> 
> 
> 
> DISCLAIMER: The contents of this email, including any attachments that it may contain, are privileged and confidential information, and may also constitute as proprietary, and are intended solely for the use of the addressee(s). If you are not the intended recipient, please notify the sender by email and delete the original message. Unintended recipients are strictly prohibited from copying, disclosing, and/or distributing such contents in any manner or form. Opinions, conclusions, and other information in this transmission that do not relate to the official business of Amagi, including all its affiliates, shall be understood as neither given nor endorsed by it. Any statements made herein that are tantamount to contractual obligations, promises, claims or commitments shall not be binding on the Company unless expressly and specifically stated as otherwise, or followed by written confirmation, by an authorized signatory of the Company.