1) Abstract

vroddon · vroddon · commit 4e252afa2a7e · 2024-09-24T00:48:43.000+02:00
The abstract was inacurate. We had this:

    This document discusses the importance of providing a formal semantics for ODRL.

I have now created this text:

    This document specifies the expected behaviour of an ODRL Evaluator, a piece of software that performs computations based on a set of policies and a certain state of the world. Both a monitoring scenario and an access control scenarios are considered.

2) Section 1 and 2.
I have not encountered contradiction in these sections with what we have discussed today. They can remain. They insist on the representation of the world with RDF --but we provide no example, though.

3a) Section 3, Consequences and Remedies
I have harmonized the terms Consequence and Remedy (boldface, capital) with the two previous concepts (Obligation, Condition). Same text, different format.
But I think we need examples with Consequences and Remedies.

3b) Section 3,
This text is anomalous (properties of what?). Constraints and Refinements were used without further introduction. I think we needed to list the basic concepts of the model. Therefore, I have replaced this text:

    Here follows a list of properties (with their possible values) needed by the ODRL Evaluator:

With a new one that introduces the missing objects. In addition, I had to make a reference to Constraints and Refinements --stressing what is the in Information Model.
diff --git a/formal-semantics/index.html b/formal-semantics/index.html
@@ -11,7 +11,8 @@
 	</head>
 	<body>
 		<section  id="abstract">
-			<p>This document discusses the importance of providing a formal semantics for ODRL.
+			<p>
+                            This document specifies the expected behaviour of an ODRL Evaluator, a piece of software that performs computations based on a set of policies and a certain state of the world. 
 			</p>
 			 
 		</section>
@@ -152,13 +153,16 @@ <h2> Semantics of Permission, Prohibition, and Obligation</h2>
 		This is a crucial difference between a Duty that represents an activation condition of a Permission and a Duty that represents an Obligation.-->
 		</li>
 		
-		<li>An instance of the class <code>odrl:Duty</code> represents a consequence for a <code>odrl:Duty</code> 
+		<li>An instance of the class <code>odrl:Duty</code> represents a <b>Consequence</b> for a <code>odrl:Duty</code> 
 			when the <code>odrl:Duty</code> refers to it by means of the <code>odrl:consequence</code> property. </li>
-		<li>An instance of the class <code>odrl:Duty</code> represents a remedy for a <code>odrl:Prohibition</code> 
+		<li>An instance of the class <code>odrl:Duty</code> represents a <b>Remedy</b> for a <code>odrl:Prohibition</code> 
 			when the <code>odrl:Prohibition</code> refers to it by means of the <code>odrl:remedy</code> property. </li>
 	</ul>
 	
+	In addition to this, an instance of the class <code>odrl:Constraint</code> is a <b>Constraint</b> of a <code>odrl:Rule</code> when the rule refers to it by means of the <code>odrl:constraint</code> property. An instance of the class <code>odrl:Constraint</code> is a <b>Refinement</b> when an <code>odrl:Action</code>, <code>odrl:AssetCollection</code> or <code>odrl:PartyCollection</code> refers to it by means of the <code>odrl:constraint</code> property. 
+
 	<hr>
+	The concepts (objects) to be understood by an ODRL Evaluator therefore include: Policy, Permission, Prohibition, Obligation, Condition, Consequence, Remedy, Refinement, Constraint and State of the World. 
 
 	Here follows a list of properties (with their possible values) needed by the ODRL Evaluator:
 	<ul>
