diff --git a/formal-semantics/index.html b/formal-semantics/index.html index fed4151..acdd5ac 100644 --- a/formal-semantics/index.html +++ b/formal-semantics/index.html @@ -465,7 +465,8 @@

Examples (Permission with duties)

Example 22 (similar to the one in the ODRL Information Model 2.2, with the differences that the type is - odrl:Agreement and the permission has an odrl:assignee).

+ odrl:Agreement and the permission has an odrl:assignee, this is to make explicit + which agent will have the active permission if the duty is fulfilled).

Type of Permission: Permission that is constrained by a Duty. The Duty has not Constraints. @@ -506,15 +507,15 @@

Examples (Permission with duties)

Evaluation of the Duty.
-The Duty has not Constraints, so it is never inactive. It starts to be active and it is fulfilled +The Duty has not Constraints, so it is never inactive. It starts to be active and it is fulfilled when in the state of the world there is a representation of an executed action that matches with the -the class of actions described in the duty: i.e. its type is compensate, its +the class of actions described in the duty. I.e. the type of the action is compensate, its payAmount is equal to 5 euro, and (given that the odrl:compensatedParty of the odrl:compensate action is not specified) its beneficiary is the assigner of the permission http://example.com/assigner:sony. It is not required that the agent who performs the compensate action is http://example.com/party:person:billie because, for example, a company can pay for its employees -(it would be useful for actions of compensation or payment to contain a reference to the contract and the party for which -they are executed).
+(feature for an ODRL profile: it would be useful for actions of compensation or payment to contain a reference to a policy or a rule and to +the party for whom they are executed).