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 9cdf4a0 commit e11a890
Showing 1 changed file with 17 additions and 4 deletions.
21 changes: 17 additions & 4 deletions formal-semantics/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -191,8 +191,9 @@ <h2> Semantics of Permission, Prohibition, and Obligation</h2>
which can take the values of <b>not-set</b>, or <b>violated</b>, or <b>fulfilled</b>.
They can become violated or fulfilled only when they are active.</li>

<li>Permission have a property called <b>deontic state</b>,
which can take the value of <b>used</b>. It can become used only when it is active.</li>
<li>Permission have a property called <b>usage state</b>,
which can take the value of <b>used</b> or <b>not-used</b>.
A permission can become used only when it is active.</li>

<li>Constraint (connected to the Rule using the odrl:constraint property) has a property called
<b>satisfaction state</b> which can take the values of <b>satisfied</b> or <b>not-satisfied</b>.
Expand Down Expand Up @@ -302,7 +303,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/#constraint-action">Example 14</a><br>
<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>
than or equal to 1200 dpi resolution).<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>
Expand All @@ -318,16 +319,22 @@ <h4>Semantics of Duty when it is used as an activation condition of a Permission
<th>ID</th>
<th>P1.R1</th>
<th>P1</th>
<th>P1.Action</th>
<th>P1.deontic state</th>
</tr>
<tr>
<td>E14-1</td>
<td>not-satisfied</td>
<td>inactive</td>
<td>blocked</td>
<td>not used</td>
</tr>
<tr>
<td>E14-2</td>
<td>satisfied</td>
<td>active</td>
<td>performed</td>
<td>used</td>
</tr>
</table>

Expand All @@ -353,9 +360,15 @@ <h4>Semantics of Duty when it is used as an activation condition of a Permission
<td>active</td>
<td>not satisfied</td>
<td>performed</td>
<th>violation considering only P1</th>
<td>not-used</td>
</tr>
</table>
In this scenario the permission is active even if the refinement is not satisfied, because the activation state of the permission
is computed independently from the refinement of the regulated action.<br>

If the situation is as described in row E13-2 and assuming that P1 is the only permission
that regulates the print action and assuming that "everything is prohibited unless explicitly permitted",
then there is a <b>violation</b> of the defaul prohibition.

<hr>

Expand Down

0 comments on commit e11a890

Please sign in to comment.