- From: Renato Iannella <r@iannel.la>
- Date: Mon, 22 Apr 2024 11:15:23 +1000
- To: Joshua Cornejo <josh@marketdata.md>
- Cc: "public-odrl@w3.org" <public-odrl@w3.org>
- Message-Id: <EB8D8019-825D-4A1E-8F38-A667BF3C6EE0@iannel.la>
Hi Joshua, please see the inheritance example here: https://www.w3.org/TR/odrl-model/#inheritance In your use case assumptions: - correct - yes (PartyA and B are the assigners for Rules in Policy B) - Policy A does not change - PartyA will also be the assigner of PolicyB Rules (as Party A is defined at the “policy-level”) Cheers - Renato > On 19 Apr 2024, at 22:37, Joshua Cornejo <josh@marketdata.md> wrote: > > Always in the scope of Offer definition. > > PartyA and PartyB belong to the same organisation (could be units) > PartyA is the Assigner in PolicyA. > PartyB is the Assigner in PolicyB. > PolicyB - inheritFrom -> PolicyA. > > I am assuming: > there is no restriction for this use case. > For each Rule in PolicyA that is now referenced in PolicyB, the Assigner is now a list of (PartyA, PartyB), > Rules that are defined in PolicyB, only have PartyB as the Assigner. > > Is this correct? > > I know there is a section for the use case of ‘not the same organisation’ as roles change (where the functions vocabulary is expanded, but not focused on that at this stage). > > Regards, > ___________________________________ > Joshua Cornejo > marketdata <https://www.marketdata.md/> > embed open standards > across your supply chain
Received on Monday, 22 April 2024 01:15:46 UTC