- From: Joshua Cornejo <josh@marketdata.md>
- Date: Fri, 19 Jul 2024 15:27:53 +0100
- To: "public-odrl@w3.org Group" <public-odrl@w3.org>
Received on Friday, 19 July 2024 14:27:59 UTC
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
Received on Friday, 19 July 2024 14:27:59 UTC