<scribe> scribe: Jo

Minutes of Last Meeting

Last Meeting: https://www.w3.org/2020/06/24-md-odrl-profile-minutes.html

Jo: Clarification of Resolutions

Ben: Resolutions of roles in supply chain - role of party - ISSUE 4
... other resolution: distinction source resource and asset ISSUE 3

RESOLUTION: With those amendments, Minutes accepted, and close ISSUE 3 and ISSUE 4

Duties

Ben: clarifies what a duty is, have identified common duties
... are there additional duties to be modelled?
... mark prepared a presentation

<benws_> https://github.com/w3c/market-data-odrl-profile/issues

mark: concept of duties https://github.com/w3c/market-data-odrl-profile/issues/6
... important to our industry's licensing rights
... in odrl this is an obligation to perform and action, which is an attribute of duty
... other attributes are creditor and debtor

Ben: debtor is the party must take the action
... creditor is the party who recives the actiopn

mark: is creditor always assigner of rights

ben: no either party can be either, or could be someone else
... e.g. when receiving data from Refinitiv, it may be the assigner, whereas creditor might be an exchange

mark: other attributes: time interval and deadline
... action is most important
... an operation on an asset
... simple example - issue an iaction .... more complex amount, quantity, currency
... so let's start with payment duties

Payment Duties

ben: compensation duty
... example https://github.com/w3c/market-data-odrl-profile/issues/8
... doesn't say how often, time interval and so on
... more detail as we work down the issue
... including the idea of needing to issue an invoice - being a debtor (of he invoice)

Natasa: can we tied those together

ben: yes

zayed: is the invoice duty actually a duty or is it optional

ben: we want the payment duty to flag up as active once the invoice is recieved
... but could be decoupled
... point of meeting is determine does this cover all the things we want to cover
... so we need to go away and comment on use cases that can't be covered

jo: point would be to take a resolution next week closing this if no comments

Notification, Request and Consent Issue 6

ben: notification duty and request for consent
... example from Deutsche Borse
... consenting to a service facilitator
... they are the debtor, but they don't have to do this, so that prevents the assignee using a service facilitator
... all captured in the interaction between the two duties and the permission
... issue is here: https://github.com/w3c/market-data-odrl-profile/issues/6

olga: what is the difference between request, notification and report

ben: good question, I defined them here
... https://github.com/w3c/market-data-odrl-profile/blob/gh-pages/Vote.md
... (discusses the linked paper)

Comprehensibility

jo: want to understand that everyone is comfortable with the level of detail

ben: poll Jeremy and MarkD
... (in response to comment from MarkD) we need to do both rights and Duties

MarkD: I assume that without the contract none of this will be seen in the system

Ben: (gives an example of researching permissions and finding that obligations may need to be fulfilled as well as the permissions, which will be part of the decision making)

markD: makes sense if we want incremental rights

Graham: as an outsider - getting stuck with the creditor/debtor terms, is that widely understood?

ben: no, there is a danger that this could be misunderstood
... creditor is beneficiary of an action etc. avoids having to have specific terms for the parties for each action

Graham: what would be a non-academic terms?

zayed: would be obligor obligee in law

ben: please comment the issue and we can consider the terms

graham: can understand the need, but quite challenging

ben: suggestions for better terms gratefully recieved

zayed: can this model multi-party

ben: yes, but haven't found example

olga: how do you fulfil pass through
... all three parties need to issue consent

ben: that use case often comes up in redistribution use cases
... example of data flow leading to derivation of data which want to distribute to customers
... might need consent of exchange
... that rule would be present in the vendor
... provider would need to make sure that what it issues is compliant
... so it all flows down thew supply chain
... needs a compliance check down the chain

jo: if you don't have a relationship with upstream party, how would you fulfil the obligation

ben: modelling what you have to do, rather than how you have to do it
... so we need to compliance check at every step, which guarantees that nothing can be lost

AOB

jo: please feed back if you are concerned to the chairs on pace and comprehensibility

ben: so please comment on the issues to feed back

jo: and if you are having difficulty with the issue commenting etc. likewise let us know
... meeting closed

This is scribe.perl Revision of Date 
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/alba/olba/
Succeeded: s/olba/olga/
Succeeded: s/payed/zayed/
Succeeded: s|I/jo:please/Topic: AOB||
Succeeded: s/ISSUE3 and IISSUE 4/ISSUE 3 and ISSUE 4/
Succeeded: s/Topic: ISSUE 6 Duties/Topic: Duties/
Succeeded: s|I/jo:||
Succeeded: s|please/Topic: AOB||
Succeeded: s|I/jo:||
Succeeded: s|I/jo: please feed back/Topic: AOB/||
Succeeded: i/jo: please feed back/Topic: AOB
Succeeded: s/com,prehensibility/comprehensibility/
Succeeded: i/jo: want to understand that/Topic: Comprehensibility
Succeeded: s/definitive/Refinitiv/
Succeeded: s/gracefully/gratefully/
Present: Jo Ben Jeremy Fred Elizabeth Mark MarkD Natasa Zayed Paul Olga olbalogun Trisha graham aaron
Regrets: Renato Ilya Laura Phil Josh Richard Atiq Stephen Ken
Found Scribe: Jo
Inferring ScribeNick: jo
Agenda: https://w3c.github.io/market-data-odrl-profile/agendas/md-odrl-profile-agenda-2020-07-08.html

WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)