Re: of Duties

Are we covering the “why” as part of the Semantics work?

 

Overall, I think it is useful for compliance (“Assignee didn’t erase Asset when they had an obligation to do it”), but that implies that the action “delete/erase” is explicitly listed as permission (probably the best option, either manually, or “surfaced” in the final agreement from the obligation) or that the PDP/PEP’s can extrapolate the ‘permission to delete’ from the ‘obligation to delete’ (but I don’t like this path, sounds like unnecessary complexity).

 

Cheers,

___________________________________

Joshua Cornejo

marketdata

embed open standards 

across your supply chain

 

From: Renato Iannella <r@iannel.la>
Date: Sunday 21 July 2024 at 04:19
To: "public-odrl@w3.org Group" <public-odrl@w3.org>
Subject: Re: of Duties
Resent-From: <public-odrl@w3.org>
Resent-Date: Sun, 21 Jul 2024 03:19:33 +0000

 

The two examples are primarily used to demonstrate “how” to express an Obligation, not necessarily “why”.

 

But they should show how to use these in a more complex scenario…such as inheriting the obligation, or as part of a workflow….

 

Cheers…R

 



On 20 Jul 2024, at 00:27, Joshua Cornejo <josh@marketdata.md> wrote:

 

Hello,

 

I am reading 2.6.4 Obligation property with a Policy and trying to understand in which use case a Party will have to fulfil an obligation without it being triggered by odrl:Permission or by a odrl:consequence. 

 

Example 20 implies that assignee person:44 has to pay €500 … but it is getting nothing (no Target nor Action) and has done nothing (no Action), so it doesn’t explain “why” it has to be fulfilled.

 

Example 21 expands a bit by having an action and a target. It is good to illustrate the structure, it shows how to articulate a Duty, but doesn’t explain what triggered the rule. This on actually looks like a separate dimension for an “audit” type role (obligation says delete – assignee didn’t execute the action “delete”, therefore must compensate) and can’t be evaluated.

 

Regards,

___________________________________

Joshua Cornejo

marketdata

embed open standards 

across your supply chain