- From: Joshua Cornejo <josh@marketdata.md>
- Date: Wed, 03 Jul 2024 11:52:45 +0100
- To: "public-odrl@w3.org Group" <public-odrl@w3.org>
- Message-ID: <48D3C653-3099-473C-94E7-430B630A526B@marketdata.md>
Hi, Has anyone considered the need for explicit affinity from left operands and actions to Rule classes? Operands: Example: odrl:payAmount should only be used in odrl:Duty Or are there use cases where implicit duties are applicable: ex:PaymentRefinement a odrl:Constraint; odrl:leftOperand odrl:payAmount; # <-- this refinement now looks like a Duty within a Permission odrl:operator odrl:eq; odrl:rightOperand "25"^^xsd:decimal. ex:ActionURI a odrl:Action; odrl:action odrl:play; odrl:unit iso4217:EUR; odrl:refinement ex:PaymentRefinement. ex:Permission a odrl:Permission; terms:created "2024-067-03T09:33:36.9180000Z"^^xsd:dateTime; odrl:target ex:AssetURI; ex:actionReference ex:ActionURI. Actions: Likewise, certain actions shouldn’t have an affinity with rule classes. An example that comes to mind would be odrl:play shouldn’t be used within an odrl:Duty. Regards, ___________________________________ Joshua Cornejo marketdata embed open standards across your supply chain
Received on Wednesday, 3 July 2024 10:52:50 UTC