Re: ODRL Profile for Data Sovereignty

Hello,

 

Re:operators

In some demo of “ODRL to AWS” integration, I proposed to have a map of actions as it simplifies the vocabulary in the “end user space” whilst keeping the functional requirements in check (by internally the mappings).

                

If in your use case, you ingest external policies odrl:isPartOf -> ods:in will need to be implemented anyway.

 

Re:PxP

                I don’t know your requirements and if you plan for interoperability (other relevant open standards) in DCAT and DPROD, the relationship to the end-point is specified by the Asset (or Collection).

 

                DCAT example: https://www.w3.org/TR/vocab-dcat-3/#Property:distribution_access_service

                DPROD example: https://ekgf.github.io/data-product-spec/dprod#accessservice

 

Regards,

___________________________________

Joshua Cornejo

marketdata

embed open standards 

across your supply chain

 

From: "Hosseinzadeh, Arghavan" <arghavan.hosseinzadeh@iese.fraunhofer.de>
Date: Thursday 22 August 2024 at 14:42
To: Joshua Cornejo <josh@marketdata.md>, "public-odrl@w3.org" <public-odrl@w3.org>
Cc: "Chwalek, Jessica" <jessica.chwalek@iese.fraunhofer.de>, Brandstädter, Robin <robin.brandstaedter@iese.fraunhofer.de>, "Feth, Denis" <denis.feth@iese.fraunhofer.de>
Subject: RE: ODRL Profile for Data Sovereignty

 

Dear Joshua

 

Thanks for your message.

 

You are right. Both operators “ods:in meaning one element in a set” and “ods:subset meaning a set included in another set” can be expressed by “odrl:isPartOf” as well. We have decided to keep them in our profile because they have been used by IDS community for some time. We shall discuss it further internally and maybe deprecate them from the profile.

 

Regarding the hasPXP and hasPIP you mentioned the right point. Several PIPs may be implemented for providing a piece of information and several PXPs can be implemented to execute an action. If a user specifies a particular PIP or PXP when specifying a policy, it will be clear during policy enforcement which endpoint should be used to retrieve the information or execute the user’s order.

 

Best regards

Arghavan

 

 

---

Arghavan Hosseinzadeh 

Senior Security Engineer 
Dept. Security Engineering

 

Fraunhofer IESE 

Fraunhofer-Platz 1 | 67663 Kaiserslautern 

+49 631 6800-2169 

arghavan.hosseinzadeh@iese.fraunhofer.de

www.iese.fraunhofer.de

 

 

From: Joshua Cornejo <josh@marketdata.md> 
Sent: Friday, August 16, 2024 10:52 AM
To: Hosseinzadeh, Arghavan <arghavan.hosseinzadeh@iese.fraunhofer.de>; public-odrl@w3.org
Cc: Chwalek, Jessica <jessica.chwalek@iese.fraunhofer.de>; Brandstädter, Robin <robin.brandstaedter@iese.fraunhofer.de>; Feth, Denis <denis.feth@iese.fraunhofer.de>
Subject: Re: ODRL Profile for Data Sovereignty

 

Very impressive work!

 

Inquiries:

 
On your figure, the extension operators:
In -> is equivalent to “isPartOf”?
Subset -> is equivalent to “isAllOf”?
 
I am interpreting the relationships “hasPXP” and “hasPIP” as an expectation that the individual constraint/actions in a relationship will be segmented to (possibly) different PxP’s ?
 

Regards,

___________________________________

Joshua Cornejo

marketdata

embed open standards 

across your supply chain

 

From: "Hosseinzadeh, Arghavan" <arghavan.hosseinzadeh@iese.fraunhofer.de>
Date: Thursday 15 August 2024 at 17:44
To: "public-odrl@w3.org" <public-odrl@w3.org>
Cc: "Chwalek, Jessica" <jessica.chwalek@iese.fraunhofer.de>, Brandstädter, Robin <robin.brandstaedter@iese.fraunhofer.de>, "Feth, Denis" <denis.feth@iese.fraunhofer.de>
Subject: ODRL Profile for Data Sovereignty
Resent-From: <public-odrl@w3.org>
Resent-Date: Thu, 15 Aug 2024 16:44:10 +0000

 

Dear ODRL Community Group,

 

We would like to register our ODRL profile. Here are the needed details of the profile:

 
Business name of the profile: 
ODRL Profile for Data Sovereignty
Name and web URL of the party having created and planning to maintain the profile
Arghavan Hosseinzadeh, Jessica Chwalek, Robin Brandstädter from Fraunhofer IESE (https://www.iese.fraunhofer.de/)
Identifier of the profile
ODS
URL of the human-readable specification document
https://profile.mydata-control.de/ods/
https://github.com/Fraunhofer-IESE/ODS/
URL of the OWL Ontology and the name of the used format 
RDF/Turtle: https://github.com/Fraunhofer-IESE/ODS/blob/main/ods-profile.ttl?raw=true
 

Please, let us know if you need any further information.

 

Thank you and best regards

Arghavan Hosseinzadeh

 

 

---

Arghavan Hosseinzadeh 

Senior Security Engineer 
Dept. Security Engineering

 

Fraunhofer IESE 

Fraunhofer-Platz 1 | 67663 Kaiserslautern 

+49 631 6800-2169 

arghavan.hosseinzadeh@iese.fraunhofer.de

www.iese.fraunhofer.de

 

-------------------------------------------------------------------------

++ Data sovereignty with the help of Data Usage Control ++

-------------------------------------------------------------------------