- From: Víctor Rodríguez Doncel <vrodriguez@fi.upm.es>
- Date: Tue, 5 Mar 2024 22:04:52 +0100
- To: public-odrl@w3.org
- Message-ID: <76d65546-423d-abdd-cac9-68e258426fd1@fi.upm.es>
Meeting notes of ODRL March 2024 monthly meeting.
0) Attendees
- Yassir Sellami
- Joshua Cornejo
- Beatriz Esteves
- Nicoletta Fornara
- Renato Ianella
- Soheil Roshankish
- Arthit Suriyawongkul
- Víctor Rodríguez-Doncel (chairs, scribes)
Apologies from Joaquín and Ben.
*1) Review of Current Set of Working Drafts*
- ODRL Profile Best Practices: https://w3c.github.io/odrl/profile-bp/
- Final feedback, which intially was set for today, extended one month.
- An ODRL Profile for Attribute based access/usage control using
Verifiable Credential claims was presented. This can serve as feedback
for the "Profile Best Practice", which should be frozen at a certain
moment. TODO: Yassir volunteers to check the profile against the profile
best practices, and do a self-assessment.
- ODRL Implementation Best Practices: https://w3c.github.io/odrl/bp/
- Final feedback, which intially was set for today, extended one month.
- Comments in the github tracker by Sridhar
(https://github.com/w3c/odrl/issues/44 and 45)
- Joshua noted several issues that needed further guidance. For
example, "party collection" might be used as "industry". A specific
party collection, duly reified, would contain the specific set of
authorised organisations. But what is expected? a list, a resource?.
Certain left operands are more targeted to be used with certain right
operands. Ex: "partOf" is expected to have a list behind. But this
should be made explicit! What if someone wants to declare a list of
countries?... how to refer to the countries?. Payments are also
conflictive. Having "pricing lists" is a common practice --e.g. the
specific, dynamic prices, being specified OUT of the policy. hasPart
sounds ok for AssetCollection and PartyCollection. How to reference
external, dynamic assets?
Not discussed
- ODRL Profile Big Data: https://w3c.github.io/odrl/profile-bigdata/
- ODRL Temporal Profile: https://w3c.github.io/odrl/profile-temporal/
- ODRL Formal Semantics: https://w3c.github.io/odrl/formal-semantics/
- Progress made, but not for review yet.
*
2) Proposal for a new Working Draft - ODRL Community Vocabulary*
- Call for all to comment on https://github.com/w3c/odrl/issues/43
- Currently, multiple webs link to profiles: main page,
https://www.w3.org/community/odrl/wiki/ODRL_Profiles,
https://www.w3.org/community/odrl/profile/. TODO: Renato to update this.
- TODO: Beatriz volunteers to create a spreadsheet with all the terms
that have been discussed.
*3) Other business*
- An ODRL Profile for Attribute based access/usage control using
Verifiable Credential claim was presented by Yassir.
https://gitlab.com/gaia-x/lab/policy-reasoning/odrl-vc-profile, also at
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
Nicoletta confirms alignment with the access control case.
- Arthit asks an example of ontology that uses ODRL Regulatory
Compliance Profile, Beatriz comments on
https://github.com/besteves4/duo-odrl-dpv (unmaintained).
4) Next meeting
- Next meeting is Monday 1 APRIL 2024 *12:00UTC *
--
Víctor Rodríguez-Doncel
D3205 - Ontology Engineering Group (OEG)
Departamento de Inteligencia Artificial
ETS de Ingenieros Informáticos
Universidad Politécnica de Madrid
https://cosasbuenas.es
Received on Tuesday, 5 March 2024 21:04:55 UTC