[poe] Issue: fix for examples in 3.3 ODRL Profile Mechanism marked as Model

simonstey has just labeled an issue for https://github.com/w3c/poe as "Model":

== fix for examples in 3.3 ODRL Profile Mechanism  ==
http://w3c.github.io/poe/model/#profile-mechanism

- [x] s/;/./ 
- [x] added missing `odrl:` namespace 
- [ ] fix inconsistent formatting, e.g.:
   + _"Create an instance of an Action and define its **includedIn** parent Action."_
   + _"The new Action MAY be defined as **\<code>includedIn\</code>** to any existing Action."_
   + _"Create a sub-property of the abstract **\<em>function\</em>** property."_

```html
<table class="def">
 <tbody>
   <tr>
     <th style="width:40%">ODRL Profile Definition</th>
     <th>Example</th>
   </tr>
   <tr>
    <td>Additional Policy Subclasses:<br/>Create a subclass the ODRL Policy class.</td>
     <td><code>ex:myPolicyType rdfs:subClassOf odrl:Policy .</code></td>
   </tr>
   <tr>
     <td>Additional Asset Relationships:<br/>Create a sub-property of the abstract <em>relation</em> property.</td>
     <td><code>ex:myRelation rdfs:subPropertyOf odrl:relation .</code></td>
   </tr>
   <tr>
     <td>Additional Party Functional roles:<br/>Create a sub-property of the abstract <em>function</em> property.</td>
     <td><code>ex:myFunctionRole rdfs:subPropertyOf odrl:function .</code></td>
   </tr>
   <tr>
     <td>Additional Actions for Rules:<br/>
   Create an instance of an Action and define its includedIn parent Action.<br/>
      The new Action MAY be defined as <code>includedIn</code> to any existing Action. <br/>
        If the new Action forms a dependency with another new or existing Action, then define the two actions with the <code>implies</code> property
    </td>
     <td><code>ex:myAction a :Action .</code><br/>
          <code>ex:myAction odrl:includedIn odrl:use .</code>
   <br/><br/><br/>
   <code>ex:myAction odrl:implies odrl:distribute .</code>
   </td>
   </tr>
   <tr>
     <td>Additional Constraint left operands:<br/>Create an instance of the LeftOperand class.</td>
     <td><code>ex:myLeftOperand a odrl:LeftOperand .</code></td>
  </tr>
   <tr>
     <td>Additional Constraint right operands:<br/> Create an instance of the RightOperand class.</td>
     <td><code>ex:myRightOperand a odrl:RightOperand .</code></td>
   </tr>
   <tr>
     <td>Additional Constraint relational operators:<br/>Create an instance of the Operator class.</td>
     <td><code>ex:myOperator a odrl:Operator .</code></td>
   </tr>
   <tr>
     <td>Additional Logical Constraint operands:<br/>Create a sub-property of the abstract <em>operand</em> property.</td>
     <td><code>ex:myLogicalOp rdfs:subPropertyOf odrl:operand .</code></td>
   </tr>
   <tr>
     <td>Additional Policy Conflict strategies:<br/>Create an instance of the ConflictTerm class.</td>
     <td><code>:myStrategy a odrl:ConflictTerm .</code></td>
   </tr>
   <tr>
     <td>Additional Rule class:<br/>Create a subclass of the Rule class and define it as disjoint with the other Rule subclasses.</td>
     <td><code>:myRule rdfs:subClassOf odrl:Rule ;</code><br/>
     <code>owl:disjointWith odrl:Prohibition, odrl:Duty, odrl:Permission . </code></td>
   </tr>
</tbody>
</table>
```

See https://github.com/w3c/poe/issues/271

Received on Thursday, 28 September 2017 06:04:02 UTC