- From: Michael Steidl \(NIT\) <mwsteidl@newsit.biz>
- Date: Mon, 2 Sep 2019 15:18:24 +0200
- To: <public-odrl@w3.org>
- Message-ID: <052101d56190$e693abc0$b3bb0340$@newsit.biz>
Notes of the ODRL CG teleconference held on 2019-09-02 Participants: Jaroslav Pullmann /JP, Víctor Rodríguez Doncel /VRD, David Filip /DF, Michael Steidl /MS Jaroslav Pullmann: he is not with Fraunhofer anymore. Still involved in Data Space activities as consultant, rules like the ODRL policies are of interest there. Currently he has no use cases, but this may change in one or two months when he consults companies. MS: also this group is interested in real world use cases. **) Profile BP VRD: what about the generic BP document. Should we merge both PC documents? JP: prefers to keep them split. MS: two different audiences: generic BP for any user of ODRL, Profile BP only for those creating a profile VRD: will continue working on the generic BP - and a lot needs to be done. What about publishing both at the same time? VRD: what (formal) next steps are required for removing the "Draft" qualifier of the Profile BP document? Renato Iannella should be asked about that. Open issue: is there any ODRL validator available which is able to combine the Core Profile and a user-created Profile? VRD: will check the one created by his team. This action will refer to the use of SHACL for validation. * ODRL and the W3C Profile Vocab MS: by his understanding a first agreed step is to use the Profile Vocab to define which resources (artifacts) are required to validate an ODRL Policy with a specific profile. The example in section 5.3 shows that. JP: isn't nore Profile Vocab-specific required? MS: an ontology for a profile should be sufficient, it should be included into this list of resources. JP, after a look into the example of 5.3: good example for how to incorporate a std speicific profile into the more generic Profile Vocab universe. JP: has worked for this dx-prof group, will contact Nic Car and and Rob Atkinson there and ask them to review the specific example is in section 5.3. * Other open issues MS: in section 6 an invitation to register a new profile with the ODRL Community Group is missing. DF: suggested to invite to a public review of this draft. MS agreed. On which channels to communicate that? David: use ODRL on Twitter (https://twitter.com/odrl - who controls this account?), use LinkedIn, ... **) Generic BP VRDr: a first version dates back to the POE WG time, then it was transferred to the ODRL Community Group. He has fixed a few issues, would be happy to get feedback from reviews. MS' feedback: in all the examples using terms beyond the ODRL Core Profile the profile property is missing. VRD: in the next months more people of the Horizon 2020 project Protect will be using ODRL. They could provide needs and feedback to this draft. See: https://euraxess.ec.europa.eu/jobs/438002 "PhD on Digital Representation of Consent Forms and Privacy Terms" https://euraxess.ec.europa.eu/jobs/438027 "PhD on Stack of Privacy Enhancing Technologies supporting compliance with the new GDPR " David Filip: ELITE-S is also involved - http://elite-fellowship.eu/ **) Next Call Monday, 7 October, 1200 GMT (1300 BST, 14:00 CEST) ============================================================= Gesendet von / sent by: Michael W. Steidl Email: mwsteidl@ <http://www.newsit.biz/> newsit.biz 1180 Wien/Vienna – Österreich/Austria
Received on Monday, 2 September 2019 13:18:49 UTC