Minutes of the W3C Rights Automation Community Group 2021-09-15

Please find the minutes of today’s meeting here <https://www.w3.org/2021/09/15-md-odrl-profile-minutes.html> and pasted below. Please note the highlighted resolutions!

Congratulations to us for publishing our draft for formal public comment and thanks to the editors for their work so far!
Summary of action items

  1.  Ben to add scope note clarifying when the one term is used as opposed to the other (temporal/timeliness of delivery)<https://www.w3.org/2021/09/15-md-odrl-profile-minutes.html#a01>
  2.  Ben to request change in Zoom booking (if necessary)<https://www.w3.org/2021/09/15-md-odrl-profile-minutes.html#a02>

Summary of resolutions

  1.  The current definition is clear<https://www.w3.org/2021/09/15-md-odrl-profile-minutes.html#r01>
  2.  We will publish this as a public working draft and formally invite comments<https://www.w3.org/2021/09/15-md-odrl-profile-minutes.html#r02>
  3.  Group will move to meeting 2nd Wednesday of the month from now on (next meeting 13th October)<https://www.w3.org/2021/09/15-md-odrl-profile-minutes.html#r03>

Market Data Rights Automation Teleconference
15 September 2021
[IRC log.]<https://www.w3.org/2021/09/15-md-odrl-profile-irc>
Attendees
Present
adam, ben, caspar, flora, jo, john_ikel, laura, markb, markd, nigel, olga, rmason
Regrets
atif, chris, michelle
Chair
ben
Scribe
jo
Contents

  1.  Admin<https://www.w3.org/2021/09/15-md-odrl-profile-minutes.html#t01>
  2.  New terms<https://www.w3.org/2021/09/15-md-odrl-profile-minutes.html#t02>
  3.  clarify distinction between two constraints<https://www.w3.org/2021/09/15-md-odrl-profile-minutes.html#t03>
  4.  Vote on whether to publish draft<https://www.w3.org/2021/09/15-md-odrl-profile-minutes.html#t04>
  5.  next steps<https://www.w3.org/2021/09/15-md-odrl-profile-minutes.html#t05>
  6.  AOB<https://www.w3.org/2021/09/15-md-odrl-profile-minutes.html#t06>
  7.  Summary of action items<https://www.w3.org/2021/09/15-md-odrl-profile-minutes.html#ActionSummary>
  8.  Summary of resolutions<https://www.w3.org/2021/09/15-md-odrl-profile-minutes.html#ResolutionSummary>

Meeting minutes
Admin

ben: No admin items to discuss

New terms

ben: I was asked to sharpen the definition of temporal constraint and reporting code
… unique identifier pointing to the data package or information product to be reported against
… also called product code

Resolution: The current definition is clear

(group further noted similarities between definition of reporting code and permissions)

clarify distinction between two constraints

ben: timeliness of delivery (6.1.2) distion between real-time data and so on when do we receive it vs when can we use it
… whereas temporal refers to data already in the system, as distinct from how quickly is data delivered into the system
… temporal 6.1.8

ben: can add two examples

nigel: is timeliness of delivery a temporal constraint, only with the time relative to now rather than absolute

ben: yes, probably
… could be regarded as a sub-property
… but worth calling out as it's important to contracts

nigel: don't want two different ways of expressing the same idea

markb: does temporal refine timeliness of delivery

ben: think it's the other way round
… historical is not covered by timeliness of delivery

nigel: also historical becomes a time sequence
… do we need soemthing in here that informs people when they should use one rather than the other

ben: the delivery issues are the focus of the timeliness of delivery
… temporal refers to date range of historical data

markb: is the problem with the use of the term 'temporal'

ben: reason is that other ontologies use the term in similar way

ben: we are looking for a scope note explaining when to use the properties

Action: Ben to add scope note clarifying when the one term is used as opposed to the other (temporal/timeliness of delivery)

Vote on whether to publish draft

(jo explains what the point of first public draft is, including the implicit need to record the feedback and make formal responses)

ben: are we happy with saying we are at that point?

markb: yes I think we are

markd: we have cleared the bar for what is needed in a draft

laura: yes, I think it's a good point to call the draft official

jo: are we done with references and so on, acknowledgements?

ben: yes, believe so, will add acknowledgements

PROPOSED RESOLUTION: We will publish this as a public working draft and formally invite comments

Resolution: We will publish this as a public working draft and formally invite comments

next steps

ben: how often should we meet, what is our focus and what kinds of communications
… starting with communications
… historically through industry events, draft may not be enough to hold a specific event
… need soemthing a bit more substantial
… implementation work reaching a demo-able stage would be a good reason for doing an event

laura: for publicity and to show progress on implementation work, we should show at WFIC in Prague, October 2022
… that would be the most comprehensive conference
… could book some time

johnI: I'm meeting David Anderson tomorrow, do you want me to have a word, please give me a script

ben: thanks

markb: we're moving to an implementation phase
… periodic communication in period leading up to that event

ben: yes great use of the communiity group, and use it to discuss implementation issues, move to monthly cadence

markd: yes, need to think about the tangible things, what resources are going to be needed etc. seems like less an exchange product more a client/vendor thing

markb: yes, looks that way

ben: another vehicle is cloud data management council? can adam give insight into that?
… feel that cloud will be quickest implementation

adam: everyone is distributing their data through us
… don't have people piloting on us (AWS)
… need someone who wants to pilot ... some customers use kafka/kubernetes and the permissions are on the topics

ben: can collaborate and make some noise about it

adam: one of the things that hasn't been solved is how militant people want to be about location
… there are tax implications
… so it's a semi-fair point

ben: do we want to move to monthly pattern

PROPOSED RESOLUTION: Group will move to monthly (4 weekly) working pattern

PROPOSED RESOLUTION: Grpoup will move to meeting 2nd Wednesday of the month from now on

Resolution: Group will move to meeting 2nd Wednesday of the month from now on (next meeting 13th October)

Action: Ben to request change in Zoom booking (if necessary)

AOB

ben: have a PhD student working on formal underpinnings of the ODRL formality

--- meeting closed



---
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to https://www.db.com/disclosures for additional EU corporate and regulatory disclosures and to http://www.db.com/unitedkingdom/content/privacy.htm for information about privacy.