Skip to content

Commit

Permalink
Update index.html
Browse files Browse the repository at this point in the history
  • Loading branch information
fornaran authored Feb 8, 2024
1 parent 95b0010 commit 9cdf4a0
Showing 1 changed file with 44 additions and 8 deletions.
52 changes: 44 additions & 8 deletions formal-semantics/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -273,7 +273,7 @@ <h4>Semantics of Duty when it is used as an activation condition of a Permission
<a href="https://www.w3.org/TR/odrl-model/">ODRL Information Model</a>.<br><br>

<a href="https://www.w3.org/TR/odrl-model/#constraint-rule">Example 13</a><br>
Type of Permission: Permission P1 is constrained by the Constraint C1. <br>
<b>Type of Permission</b>: Permission P1 is constrained by the Constraint C1. <br>
(The permission allows the <code>target</code> asset to be distributed, and includes a <code>constraint</code>
of a <code>dateTime</code> condition that the permission can only be exercised until 2018-01-01).<br>
When the constraint is no longer satisfied and the permission is no longer active.<br>
Expand Down Expand Up @@ -303,29 +303,64 @@ <h4>Semantics of Duty when it is used as an activation condition of a Permission
<b>Type of Permission</b>: Permission P1 permits an action that is refined by Refinement R1. <br>
(The permission allows the target asset to be printed, and also include a refinement of less
than or equal to 1200 dpi resolution.).<br>
Acces control scenario: If the requested action to print satisfies the Refinement the action is permitted otherwise it is blocked.<br>


<b>Acces control scenario</b>: if the requested print action satisfies the refinement,
the action is permitted otherwise it is not permitted and the system will block it.<br>

<b>Monitoring scenario</b>: if a print action that satisfies the refinement is performed the permission is used.
If a print action that does not satisfies the refinement is performed and there is not another
permission that permit it and assuming that default setting for the ODRL Evaluator is:
"everything is prohibited unless explicitly permitted", then there is a violation.<br>

<b>Acces control scenario</b>:
<table border="1">
<tr>
<th>ID</th>
<th>P1.C1</th>
<th>P1.R1</th>
<th>P1</th>
</tr>
<tr>
<td>E13-1</td>
<td>E14-1</td>
<td>not-satisfied</td>
<td>inactive</td>
</tr>
<tr>
<td>E13-2</td>
<td>E14-2</td>
<td>satisfied</td>
<td>active</td>
</tr>
</table>

<hr>
<b>Monitoring scenario</b>:

<table border="1">
<tr>
<th>ID</th>
<th>P1</th>
<th>P1.Action.R1</th>
<th>P1.Action</th>
<th>P1.deontic state</th>
</tr>
<tr>
<td>E14-1</td>
<td>active</td>
<td>satisfied</td>
<td>performed</td>
<td>used</td>
</tr>
<tr>
<td>E13-2</td>
<td>active</td>
<td>not satisfied</td>
<td>performed</td>
<th>violation considering only P1</th>
</tr>
</table>

<a href="https://www.w3.org/TR/odrl-model/#duty-perm">Example 22 (Permission)</a> <br>
<hr>

<!--
<a href="https://www.w3.org/TR/odrl-model/#duty-perm">Example 22</a> <br>
The Party <code>http://example.com/assigner:sony</code> makes an Offer to play the target asset http://example.com/music/1999.mp3.
The permission includes a duty for the compensate action that has a refinement of payAmount of euro 5.00.
Expand Down Expand Up @@ -414,6 +449,7 @@ <h4>Semantics of Duty when it is used as an activation condition of a Permission
<td>depends on default setting and other permissions.</td>
</tr>
</table>
-->

<h3>Sematics of Prohibition</h3>

Expand Down

0 comments on commit 9cdf4a0

Please sign in to comment.