Added refinement state (model) and narrative text to leftOperands (vo…

…cab) #282

model/index.html

@@ -798,7 +798,7 @@ <h3>Refinement property with an Action</h3>
 
 <p>An Action MAY include the <code>refinement</code> property to indicate a Constraint/Logical Constraint that narrows the semantics of the Action operation directly.
 
-	To meet this condition of narrower semantics for the Action, all of the Constraints/Logical Constraints referenced by the <code>refinement</code> property MUST be <strong>satisfied</strong>. </p>
+	To meet this condition of narrower semantics for the Action, all of the Constraints/Logical Constraints referenced by the <code>refinement</code> property MUST be used as generating a <strong>satisfied</strong> state. </p>
 
 	<p>Note: The outcome of applying refinements to an Action SHOULD NOT result in a null operation.</p>
 
@@ -1999,6 +1999,10 @@ <h3>Changes from Previous Versions</h3>
 
 
     <li>Added version "2.2" to the document title to make it clear the provenance of the specification. <a href="https://github.com/w3c/poe/issues/283"> (Issue#283)</a></li>
+
+        <li>Clarified refinement property satisfaction <a href="https://github.com/w3c/poe/issues/282"> (Issue#282)</a></li>
+
+
     </ul>
 
 

vocab/index.html

@@ -1184,7 +1184,7 @@ <h2>ODRL Common Vocabulary</h2>
 <tr><th>Included In:</th> <td><a href="#term-use">use</a></td></tr>
 <tr><th>Class:</th> <td><a href="#term-Action">Action</a></td></tr>
 </table>
-</section></section><section id="constraintLeftOperandCommon"><h2>Constraint Left Operands</h2><section id="term-absolutePosition"><h3>Absolute Asset Position</h3><table class='def propdef' >
+</section></section><section id="constraintLeftOperandCommon"><h2>Constraint Left Operands</h2><p>This section contains instances of LeftOperands that can be used as the leftOperand of a Constraint . The LeftOperands may be used in Constraints for either the constraint property (applying to a Rule) or a refinement property (applying to the Action). ODRL policy expressions should utilise Constraints that are appropriate for the intended semantics of the LeftOperand.</p><section id="term-absolutePosition"><h3>Absolute Asset Position</h3><table class='def propdef' >
 <tr><th>Definition:</th> <td>A point in space or time defined with absolute coordinates for the positioning of the target Asset.</td></tr>
 <tr><th>Label:</th> <td>Absolute Asset Position</td></tr>
   <tr><th>Identifier:</th> <td><a href="http://www.w3.org/ns/odrl/2/absolutePosition">http://www.w3.org/ns/odrl/2/absolutePosition</a></td></tr>
@@ -1934,7 +1934,8 @@ <h2>Changes from Previous Versions</h2>
 
     <li>Added version "2.2" to the document title to make it clear the provenance of the specification. <a href="https://github.com/w3c/poe/issues/283"> (Issue#283)</a></li>
 
- <li>Clarified definitions of some LeftOperand terms. <a href="https://github.com/w3c/poe/issues/284"> (Issue#284)</a></li>
+ <li>Clarified definitions of some LeftOperand terms. <a href="https://github.com/w3c/poe/issues/284"> (Issue#284)</a> and their role with constraint and refinement properties <a href="https://github.com/w3c/poe/issues/282"> (Issue#282)</a>.</li>
+
 
 
     </ul></section>

vocab/parts/changes.html

@@ -84,7 +84,8 @@
 
     <li>Added version "2.2" to the document title to make it clear the provenance of the specification. <a href="https://github.com/w3c/poe/issues/283"> (Issue#283)</a></li>
 
- <li>Clarified definitions of some LeftOperand terms. <a href="https://github.com/w3c/poe/issues/284"> (Issue#284)</a></li>
+ <li>Clarified definitions of some LeftOperand terms. <a href="https://github.com/w3c/poe/issues/284"> (Issue#284)</a> and their role with constraint and refinement properties <a href="https://github.com/w3c/poe/issues/282"> (Issue#282)</a>.</li>
+
 
 
     </ul>

vocab/parts/constraintLeftOperandCommon.html

@@ -0,0 +1 @@
+<p>This section contains instances of LeftOperands that can be used as the leftOperand of a Constraint . The LeftOperands may be used in Constraints for either the constraint property (applying to a Rule) or a refinement property (applying to the Action). ODRL policy expressions should utilise Constraints that are appropriate for the intended semantics of the LeftOperand.</p>