diff --git a/formal-semantics/index.html b/formal-semantics/index.html
index d138496..c4c317e 100644
--- a/formal-semantics/index.html
+++ b/formal-semantics/index.html
@@ -41,7 +41,8 @@ Introduction
Therefore this specification defines the expected behaviour of an ODRL Evaluator. Namely, given a collection of ODRL policies
and a formal description of a particular state of the world, the objective of an ODRL Evaluator is to determine:
- - Which Permissions, Prohibitions, and Obligations are active;
+ - Which Permissions, Prohibitions, and Obligations (collectively named Rules)
+ are active, i.e. a Rule is said to be active if it is in effect.
- Which Prohibitions and Obligations have been violated or fulfilled.
The ODRL Evaluator is expected to work in at least these two activities:
@@ -159,9 +160,9 @@ Semantics of Permission, Prohibition, and Obligation
https://www.w3.org/2016/poe/wiki/Evaluator.
-
The deontic modalities of Permissions, Prohibitions and Obligations can be represented in ODRL as instances of the classes
odrl:Permission, odrl:Prohibition and odrl:Duty.
+
Instances of the class odrl:Duty may have different meanings in ODRL.
- An instance of the class
odrl:Duty represents an Obligation when it is connected to the odrl:Policy through the odrl:obligation property.
@@ -179,7 +180,6 @@ Semantics of Permission, Prohibition, and Obligation
-
Permissions, Prohibitions and Obligations, collectively named Rules, have a property called activation state, which can take the values of active or inactive. An inactive Rule has no effect.
Obligations and Prohibitions have a property called violation. When Obligations and Prohibitions are active, they can become violated or not-violated.