From 1cad7ae4c49f95e4035767c51307c2445e884e01 Mon Sep 17 00:00:00 2001
From: Nicoletta Fornara <fornaran@usi.ch>
Date: Thu, 8 Feb 2024 11:17:40 +0100
Subject: [PATCH] Update index.html

---
 formal-semantics/index.html | 21 ++++++---------------
 1 file changed, 6 insertions(+), 15 deletions(-)

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 @@ <h4>Semantics of Duty when it is used as an activation Condition of a Permission
 	
 	<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>
@@ -342,9 +336,12 @@ <h4>Semantics of Duty when it is used as an activation Condition of a Permission
     	</tr>
 	</table>
 	<br>
-	
-	<b>Monitoring scenario</b>:
 
+	<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 (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 <b>violation</b> of the defaul prohibition.<br>
+	
 <table border="1">
   	<tr>
     		<th>ID</th>
@@ -372,12 +369,6 @@ <h4>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.<br>
 	
-	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 <b>violation</b> of the defaul prohibition.
-	
 	<hr>
 
 	<!--