From e3c67addd7c9a8a5a11ee4a8fd266c5d9a86db4e Mon Sep 17 00:00:00 2001 From: Nicoletta Fornara Date: Wed, 7 Feb 2024 14:57:43 +0100 Subject: [PATCH] Update index.html --- formal-semantics/index.html | 24 ++++++++++++++---------- 1 file changed, 14 insertions(+), 10 deletions(-) diff --git a/formal-semantics/index.html b/formal-semantics/index.html index 0a92a9e..ec7f6c0 100644 --- a/formal-semantics/index.html +++ b/formal-semantics/index.html @@ -34,23 +34,27 @@

Introduction

The ODRL Information Model formally defines the core abstract concepts of the model and their properties by means of an OWL 2 Ontology (available at https://www.w3.org/ns/odrl/2/), which is described in the ODRL Vocabulary & Expression specification.

- The ODRL ontology can be used as a data model to represent machine-readable Policies and associate them with digital or analog assets. By using a machine-readable language to represent policies, ODRL implementations can provide useful functionalities such as those of a policy search engine, a policy compatibility checker, an access control system or a policy planning system. + The ODRL ontology can be used as a data model to represent machine-readable Policies and associate them with digital or analog assets. By using a machine-readable language to represent policies, ODRL implementations can provide useful functionalities such as those of a policy search engine, a policy compatibility checker, an access control system, a monitoring system, or a policy planning system.

- However, neither the specification of the model (in a text form) nor the vocabulary (in an OWL ontology) accurately describe the behaviour of an ODRL implementation. - This specification defines the expected behaviour of an ODRL Evaluator. - Given a collection of ODRL policies and a particular state of the world, the objective of an ODRL Evaluator is to determine: + However, neither the specification of the model (which is in a text form) nor the vocabulary (which is in an OWL ontology) accurately describe the behaviour of an ODRL implementation. + 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:

    -
  1. Which Permissions, Prohibitions, and Obligations are active
    2. -
  2. Which Prohibitions and Obligations have been violated.
    3. +
  3. Which Permissions, Prohibitions, and Obligations are active;
    4. +
  4. Which Prohibitions and Obligations have been violated or fulfilled.
-
+
The ODRL Evaluator is expected to work in at least these two activities:
    -
  1. Policy monitoring (or compliance checking): given a set of policies and a state of the world, the task to determine whether obligations or prohibitions have been fulfilled or violated by the performance of certain actions, and which permissions have been used.
    2. -
  2. Access control: the computation that determines the access by users or software agents to digital resources considering a set of policies and the state of the world.
    3. +
  3. Access control: the computation that determines the access by users or software agents to digital resources + considering a set of policies, the state of the world, and the action that the user/agent request to perform.
    4. +
  4. Policy monitoring (or compliance checking): given a set of policies and a state of the world, the task to + determine whether obligations or prohibitions have been fulfilled or violated by the performance of certain + actions, and which permissions have been used.
    5. +
- Whereas violations are possible in a policy monitoring scenarios (and consequences can be triggered), violations are not possible in an access control system. +

This document describes the expected behaviour of this ODRL Evaluator, with a textual description, a formal semantics and a collection of examples.