<scribe> scribe: jo
<scribe> ACTION: JO to add irc details to conference call invite
Agenda https://w3c.github.io/market-data-odrl-profile/agendas/md-odrl-profile-agenda-2020-05-13.html
minutes https://www.w3.org/2020/04/29-md-odrl-profile-minutes.html
RESOLUTION: LAST MEETING MINUTES AGREED
<inserted> jo: last meeting we agreed to postpone adoption of charter to this meeting to allow time to review
RESOLUTION: Adopt Charter
ben: key output is syntax and
semantics of a profile of ODRL, i.e. a set of terms
... these will be presented in a document
... mark is to join ben in editing the doc and implementing
resolutions of the group
mark: introduces self and provides backgroud
ben: to add DataBP already has model so familiar terriotry
mark: yes, doing it for a long time
RESOLUTION: MARK TO BE CO-EDITOR
<benws_> https://github.com/w3c/market-data-odrl-profile/blob/gh-pages/Test-Cases.md
Ben: link to test cases, kindly
provided by Michelle
... this type of question gets asked day in day out
... 9 examples, derived data, distributed data, non-display
use
... if we can generate queries to get answers then we are
making peoples lives easier
... so they are part of our success crieteria
... and as we go along be confident of the utility of the
spec
... Paul and Phil are there people we can go to in Refinitv to
add to the questions?
Michelle: tried to take generic
examples
... distributor has different questions to those already
asked
... some key questions here
... hot topic redistribution, putting in 3 scenarios
... also non-display use with various scenarios
... finally looking at derived data - complicated area, many
different takes on this, gave a few examples
Ben: Question about "small amounts of data", some licenses cover it
Phil: recognise the things
Michelle is calling out, systematic and non-systematic
... limited amounts of data for non-commercial use is
common
Michelle: no exact measures hard to measure
Phil: sometimes down to not
competing with other parties
... would be good to agree standard way of expressing these
things
Michelle: rare to have a yes/no anser
Ben: we should ask CME how we
should answer these types of questions
... I also translated Deutsche Bourse "non display use", anyone
got a contact there as I'd like to get some answers
Paul: ??? within Refinitv would be a good place to go
mark: like the gradation of complexity of the examples provided by Michelle
Ben: are we involved in a purely
descriptive process or are we going in to the territory of
"best practice"
... don't have a strong opinion yet
Paul: think it's a natural outcome of what we are doing, to provide clarity
<benws_> https://w3c.github.io/market-data-odrl-profile/translations/CME-CatA.html
ben: we know CME is fairly happy
with the above, needs testing against Michelle's criteria
... if you can't find out what the data is then it's difficult
to make this work
... there is no universally scoped id for the underlying
resource
... fairly surprising but nothing other than textural
description
... we do seem to have codes for the platform where data
generated
... globes has a code
... but also other references to clear port and open
outcry
... what's the licensing significance, mark
Mark: can't comment but will take up with CME guys
<scribe> ACTION: Mark to find out details from CME
BEN: is there technology that helps us link data to the license
Ilya: need to agree standar as to
how assets and counterparts are identified
... needs to be sufficient to pick the right license
Phil: think it needs to be in
scope of work, the first thing to do ... ids of suppliers,
distributors etc.
... then we can tie back to the contracts
... also need asset type, content class ... rules that are in
contracts refer to them
... I'd like to see us address those things first
Ben: will follow up on that then
Ilya: let's not re-invent the wheel, there are pre-existing standards that we can utilise
Ben: could you circulate a list of those standards?
<scribe> ACTION: Ilya to compose a list of standards and send to list
Ben: Another point is (ref
Deutsche Bourse non-display) if we can show progress in the
most complex area of the business then this will give us some
enhanced credibility
... thanks to those who contributed to the discussion about
this on list
... what the purpose of this was
... gives rise to a list of things that have to be done as a
consequence
... often not confident in whether any particular use is a
non-display use or not
... what are the really deep issues?
... Things suppliers are sensitive to are:
... are you distributing it, are you creating financial
instruments, are you doing automated trading and at what
scale
... if we can itemise those sensitivities then maybe we won't
have to make exhaustive lists
... (ben reads a list, which he makes the point is clearly
non-exhaustive, which is not useful for automation)
... would avoiding the listing in the way suggested work?
Mark: end-users need to be
certain that their use is permitted
... don't know that can avoid making the exhaustive list
Ben: will be surprised if the
terms are actually clear enough even if you do list them
... always a level of inherent ambiguity
... so the principles are important
Michelle: think it's about separating out trading activities, so it's more down to the purpose of the application
Ben: suppliers are particularly
sensitive to some things, I hope that there is a small number
of those big ticket terms
... we will need to investigate
... we are still bootstrapping and we haven't yet got rhythm -
Mark and I will churn the terms - and add them to the
document
... main work of the group is to agree and publish the terms in
that license
... should have a decent number of terms next time we meet
Paul: we have been working with
FISD, they are interested in June, virtual, abbreviated version
of the ones in September and January
... looking for speakers
jo: let's raise as an Issue
Ben: FISD seminar asked the question - what are the most important trends - 1) standardisation of market data, 2) tools and services to support
Paul: seminar is about evangelism, would be nice if same speakers to cut down preparation time
jo: meeting closed
<scribe> ACTION: Paul will raise the question of speakers for FISD as a GitHub ISSUE
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 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/opinio0n/opinion/ Succeeded: i/RESOLUTION: Adopt Charter/jo: last meeting we agreed to postpone adoption of charter to this meeting to allow time to review Succeeded: s/Things suppliers are sensitive to ar/Ben: Things suppliers are sensitive to ar/ Succeeded: s/\names// Succeeded: s/put a list off/circulate a list of/ Succeeded: s/question fo speakers/question of speakers for FISD/ Present: jo Ben Michelle Joshua Mark_Bird Ilya phil paul_klug natasa Regrets: Renato mark_durenberger Laura Richard Michael Found Scribe: jo Inferring ScribeNick: jo 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: ilya jo mark paul 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]