From e11a8909a466b070db3c360088f0327ced26da23 Mon Sep 17 00:00:00 2001 From: Nicoletta Fornara Date: Thu, 8 Feb 2024 10:09:13 +0100 Subject: [PATCH] Update index.html --- formal-semantics/index.html | 21 +++++++++++++++++---- 1 file changed, 17 insertions(+), 4 deletions(-) diff --git a/formal-semantics/index.html b/formal-semantics/index.html index 1f4e54d..2fe1bb9 100644 --- a/formal-semantics/index.html +++ b/formal-semantics/index.html @@ -191,8 +191,9 @@

Semantics of Permission, Prohibition, and Obligation

which can take the values of not-set, or violated, or fulfilled. They can become violated or fulfilled only when they are active. -
  • Permission have a property called deontic state, - which can take the value of used. It can become used only when it is active.
  • +
  • Permission have a property called usage state, + which can take the value of used or not-used. + A permission can become used only when it is active.
  • Constraint (connected to the Rule using the odrl:constraint property) has a property called satisfaction state which can take the values of satisfied or not-satisfied. @@ -302,7 +303,7 @@

    Semantics of Duty when it is used as an activation condition of a Permission Example 14
    Type of Permission: Permission P1 permits an action that is refined by Refinement R1.
    (The permission allows the target asset to be printed, and also include a refinement of less - than or equal to 1200 dpi resolution.).
    + than or equal to 1200 dpi resolution).
    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.
    @@ -318,16 +319,22 @@

    Semantics of Duty when it is used as an activation condition of a Permission ID P1.R1 P1 + P1.Action + P1.deontic state E14-1 not-satisfied inactive + blocked + not used E14-2 satisfied active + performed + used @@ -353,9 +360,15 @@

    Semantics of Duty when it is used as an activation condition of a Permission active not satisfied performed - violation considering only P1 + not-used + 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 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 violation of the defaul prohibition.