diff --git a/formal-semantics/index.html b/formal-semantics/index.html
index 0aefa81..2813030 100644
--- a/formal-semantics/index.html
+++ b/formal-semantics/index.html
@@ -311,13 +311,7 @@
Semantics of Duty when it is used as an activation Condition of a Permission
Acces control scenario: if the requested print action satisfies the refinement,
the action is permitted otherwise it is not permitted and the system will block it.
-
- Monitoring scenario: 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.
-
- Acces control scenario:
+
ID |
@@ -342,9 +336,12 @@ Semantics of Duty when it is used as an activation Condition of a Permission
-
- Monitoring scenario:
+ Monitoring scenario: 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 (line E14-2) and there is not another
+ permission that permit the performed print action and assuming that default setting for the ODRL Evaluator is
+ "everything is prohibited unless explicitly permitted", then there is a violation of the defaul prohibition.
+
ID |
@@ -372,12 +369,6 @@ Semantics of Duty when it is used as an activation Condition of a Permission
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.
- If the situation is as described in row E13-2 (a print action is performed but the refinement is not satisfied)
- assuming that:
- P1 is the only permission that regulates the print action and
- "everything is prohibited unless explicitly permitted",
- then there is a violation of the defaul prohibition.
-