W3C

- DRAFT -

Rights Automation Community Group Teleconference

10 Jun 2020

Agenda

Attendees

Present
ben, jo, attiq, laura, doug, paul, fred, ilya, josh, trisha, natasa, mark, Mar_D, Michelle, olga
Regrets
renato
Chair
Ben
Scribe
jo, Phil

Contents


admin

<jo> scribe: jo

<inserted> rick: I am here

<Phil> scribe: Phil

<scribe> chair: Jo

<Ilya_Slavin> present

<jo> https://www.w3.org/2020/05/27-md-odrl-profile-minutes.html

Mark: engagement document under way

<benws> +1

RESOLUTION: Agree minutes of previous meeting

webinar

Paul: confirmation from all speakers, all as planned and to be well attended

Atiq: how will questions be handled?

Paul: all questions submitted to email group for review

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

Editors’ Update

Ben: a set of issues being created on github site, in some depth
... issue #4 actors in supply chain, roles that orgs play in specific use cases
... we propose … originator, provider, consumer and service facilitator
... we hope to vote on set of roles at next meeting
... other issues to be discussed on github include derived data, application registration,

Mark: where is the process defined for development and agreement ?

<benws> md-odrl-profile.html

<jo> https://w3c.github.io/market-data-odrl-profile/md-odrl-profile.html

Mark: nice to have the online dialogue

Paul: good to have as an artefact

<jo> (where the developing agreements will be recorded)

Ben: other issue is source vs resource vs asset in the supply chain. Important to clarify terms.
... firm definitions are required for these terms, for humans and computers

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

Mark: summarises the goal of the thread to determine when rights cease to apply to some "thing”
... give us the ability to daisy chain down the supply chain and identify changes, making new assets.
... defines a supply chain for a source that becomes an asset

Ben: light transformations vs where something new is created. Some activities do not change the rights, some do. Needs more input on this.

Natasa: usually dependant on if a significant transformation is done. ISIN and currency change is one type, verses larger transformation. The definition of a resource is handy. Stays same resource for minimal changes, new resources for other.

Ben: irreversible is a market data standard but interpretations are not predictable. We want them to be.
... I’m assuming we can do this mathematically.

Ilya: question is can you used derived instrument as a replacement for the original
... if you can do the same business function with the data that the new instrument its based on

Laura: Same issue with “use” itself… Some of the interpretation is “we’ll know it when we see it”.

Mark: Possible a third category of transformation….
... not a complete transformation

Ben: Some transformations are currently smoothly handled, so not within scope of the current issue.
... e.g. timeliness of delivery transitions
... new issue opend on derived data
... new issue opened on when new registration with provider is required
... issues to be opened on what is a reporting duty etc

any other business

<jo> chair: jo

<jo> rrsagent: pointer

<jo> scribe: jo

<scribe> chair: jo

s/Mar_D/Mark_Durenberger/

Summary of Action Items

Summary of Resolutions

  1. Agree minutes of previous meeting
[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version (CVS log)
$Date: 2020/06/10 15:59:55 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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/bo/Bob/
Succeeded: s/reagent, pointer//
Succeeded: s|I/how does this work/rick: I am here||
Succeeded: i/how does this work/rick: I am here
Succeeded: s/toipc/topic/
Succeeded: s/recorded/recorded)/
Succeeded: s/Meeting: test meeting demo of scribing//
Succeeded: s/chair: zebidee//
Succeeded: s/scribe: dougal//
Succeeded: s/Phil: how does this work//
Succeeded: s/jo: like this//
Succeeded: s/... and by the wayt//
Succeeded: s/topic: next topic//
Succeeded: s/ben: wow!//
Succeeded: s/... zounds!//
Succeeded: s/ACTION: Jo to explain something//
Succeeded: s/action: jo to try something else//
Succeeded: s/engagement document under way/$$$/
Succeeded: s/engagement document under way//
Succeeded: s/$$$/engagement document under way/
Succeeded: s/ACTION: Jo to explain something//
FAILED: s/Mar_D/Mark_Durenberger/

WARNING: Replacing previous Present list. (Old list: Bob, ted, alice)
Use 'Present+ ... ' if you meant to add people without replacing the list,
such as: <dbooth> Present+ ben, jo, attiq, laura

Present: ben jo attiq laura doug paul fred ilya josh trisha natasa mark Mar_D Michelle olga

WARNING: Replacing previous Regrets list. (Old list: renato, God)
Use 'Regrets+ ... ' if you meant to add people without replacing the list,
such as: <dbooth> Regrets+ renato

Regrets: renato
Found Scribe: jo
Inferring ScribeNick: jo
Found Scribe: Phil
Inferring ScribeNick: Phil
Found Scribe: jo
Inferring ScribeNick: jo
Scribes: jo, Phil
ScribeNicks: jo, Phil
Agenda: https://w3c.github.io/market-data-odrl-profile/agendas/md-odrl-profile-agenda-2020-06-10.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: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


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.)


[End of scribe.perl diagnostic output]