- From: Joshua Cornejo <josh@marketdata.md>
- Date: Thu, 29 Feb 2024 10:43:17 +0000
- To: Yassir Sellami <yassir.sellami@gaia-x.eu>
- CC: "public-odrl@w3.org" <public-odrl@w3.org>
- Message-ID: <99677724-EBCC-43DD-9B98-8DCF459491AE@marketdata.md>
Hi Yassir, "assignee": { "ovc:constraint": [ { "ovc:leftOperand": "$.credentialSubject.gx:legalAddress.gx:countrySubdivisionCode", "operator": "http://www.w3.org/ns/odrl/2/in", "rightOperand": [ "FR-HDF", "BE-BRU" ], "ovc:credentialSubjectType": "gx:LegalParticipant" } ] } A couple of comments on the code: Assignee You’re defining an Offer (says nothing about mandatory Assignee – so I assume it could go there) According to the definition: “The Party is the recipient of the Rule.” In your example, you seem to be using it as a category/type. I had the same conceptual problem and it is something that I have on my “list” of questions for v3.0. In my interpretation - it is possible that the term ‘Collection’ could be used orthogonally – to define a “collectionOf” where the origins allow for ‘basket categories’ that would filter down to apply constraints when you transform an Offer -> Agreement (in your case: you want to restrict to a physical location). And also “partOf”, where you have a consortium (e.g. Sony) with multiple organisational divisions of types (“collectionOf”) in different locations (to apply your constraint). Operators https://www.w3.org/TR/odrl-vocab/#constraintRelationalOperators “in” is not an (active) operator, I think you are referring to: http://www.w3.org/ns/odrl/2/isAnyOf And a separate thought: Having ISO 3166 as separate attributes/operands/elements for constraints will prove to be more convenient (if you are expecting third parties to consume your policies). Regards, From: Yassir Sellami <yassir.sellami@gaia-x.eu> Date: Thursday 29 February 2024 at 09:40 To: "public-odrl@w3.org" <public-odrl@w3.org> Subject: ODRL Profile using Verifiable Credential Resent-From: <public-odrl@w3.org> Resent-Date: Thu, 29 Feb 2024 09:40:02 +0000 Hello, I am happy to share with you this ODRL Profile for Attribute based access/usage control using Verifiable Credential claims. Here are some useful links on the ODRL Profile: The ODRL Profile (a specification document and a .ttl definition): https://gitlab.com/gaia-x/lab/policy-reasoning/odrl-vc-profile Also available through: https://w3id.org/gaia-x/ovc/1/ An open-source demonstration tool is available (not all features are implemented): https://wizard.lab.gaia-x.eu/policyStepper I am looking forward to hearing any feedback from you. Feel free to reach out for any questions or contributions. Best regards, Yassir Sellami | Software Developer Gaia-X European Association for Data and Cloud AISBL yassir.sellami@gaia-x.eu | www.gaia-x.eu | Avenue des Arts 6-9 1210 Bruxelles/Brussels Belgium News & Press | Events | Media| Membership | www.gaia-x.eu PRIVACY AND CONFIDENTIALITY NOTICE: For details about what personal information we collect and why, please see our Privacy Policy on our website at http://www.gaia-x.eu/privacy-policy. This e-mail message and any attachments are for the sole use of the intended recipient(s) and may contain confidential and/or legally privileged information. Any unauthorized use or disclosure, copying and/or distribution of the content of this e-mail message and attachments is prohibited. If you are not the intended recipient, please contact us by reply e-mail and destroy all copies of the original message and attachments immediately. Thank you. Please consider the environment before printing this e-mail. Save about 200ml water, 2g CO2, 0.05kWh power, and 2g wood.
Received on Thursday, 29 February 2024 10:43:27 UTC