<scribe> scribe: jo
Minutes of last meeting https://www.w3.org/2020/05/13-md-odrl-profile-minutes.html
RESOLUTION: Minutes of last meeting agreed
Paul: Webinar with FISD, agenda
circulated, speakers mostly agreed
... mostly an update on previous edition, but some things will
be new to some people
... so want to cover the basics as well
... ideas from Michelle and Atiq to "spice it up"
Michelle: to give some background
for people who haven't been involved before, something a little
less formal
... stepping it on with stuff we have all been doing
Atiq: it is a year on, now we
have a working group it would be good to step forward
... look at objectives, vocabulary, language and so on
... what can we do to support while we are waiting for the
vocab
... to emerge, document use cases and so so
... all about what we can do in our companies to support the
next wave of work
Paul: more about use cases, less about theory and concepts?
Atiq: need to avoid repeat,
things have moved on
... what else can we do help process move forward
ben: not an all or nothing
thing
... we can progress these things while standardisation moves
forward
Michelle: other things need to be build out, how do get licenses together and so on
ben: in terms of giving an
overview, my and Jo's section can cover it, and if you can talk
about preparing your orgs for a more automated world
... sounds good
Paul: sounds good to me. put enough explanatory stuff to get people up to speed.
mark: hoping to use /my section to help people to appreciate that they can actually understand ODRL
(discussion of collapsing parts of the agenda down)
Michelle: maybe we can talk a little more informally
Atiq: agree
Paul: like the conversational
approach
... is anyone else interested in being a speaker?
<scribe> ACTION: Paul to circulate draft agenda on list
<benws_> https://w3c.github.io/market-data-odrl-profile/NewTerms.html
(trying to find speaker)
ben: have linked to new
terms
... not a deep dive but calling out a couple of things
... agent ... people and systems that do things
... acting ... as a broker, as a principal
... have some preliminary definitions in the document
... please contribute by email or by direct editing of the
document
... in some cases regulators have come in from them
... question - how comfortable is group with using definitions
from regulators ...
Michael: European exchanges use
terminology from regulators, maybe because of MIFID 2
... required to appease the regulation
... but we are all under different regulatory obligations
... we are all talking about the same thing, in broad
terms
... licenses may be specifically different
ben: quote from CBT - what do we all care about? Basically distribution, non-display and creation of new products
Michael: agree with that, as the types of data become broader, agreements reflect value and use - e.g. indexes vs exchange data (end of day vs real time)
ben: what is the distinction
between an asset and a resource?
... resources may be data, api calls, bandwidth ... we are
mainly interested in data
... I want to get at the underlying concept of data set without
reference to the means of delivery etc.
... the slicing and dicing comes in the definition of the
asset
... wondering if the distinction makes sense, will what I am
trying to do work?
Mark: makes sense to me
... question, in this model asset has an attribute of
timing
ben: what you can do belongs at
the permission level
... goes on to explain
Phil: I like the distinction
between asset and resource
... however some aspects are just a refinement of the resource,
rather than creating an asset by adding value
<scribe> ACTION: Ben to clarify the question as an ISSUE on GitHub and to lead discussion on list in respect of it
Ben: I also described a number of actions - found it useful to do that
<scribe> ACTION: BEN to raise an ISSUE on that and ask for comments on list
Michael: following last round of
emails I thought important to engage the exchanges
... exchanges need to decide whether to participate in this
initiative and thought of writing a document
... to explain from exchanges point of view, also thought it
could be extended to look at the vendor and client point of
view too
... pointing out the value of engagement
... it will take a week or so to get this together, but what
does everyone else think about this as a means of
communication
ben: I'm disappointed that there
is no one new at this meeting. We haven't managed to translate
interest into engagement
... a while ago we talked about having a less technical
venue
... and no licensing obligation - a wider discussion
forum
... elm council supports interest groups that anyone can
join
jo: think we should create a
document of the kind Michael describes as part of the work
effort of this gropup
... if Michael will take the lead as editor of such an
educational document then I'd like us to embrace it as a work
output
mark: different exchanges have different fears, cataloguing them would be useful
Michael: FAQ kind of style to it
<scribe> ACTION: Michael to work with Mark to come up with a document outline for Engagement Document
ben: thanks Ilya for his
suggestions
... question for the group, I'd like us to have something to
say about what licenses apply to data that is running through
our systems?
... basic question is identifying data, so we can apply the
right permissions
(Atiq will join Ben in looking at this question)
Ilya: worried about the scope being beyond what this group is here to do
ben: take your point, please join the call so you can make the point that it is out of scope
(Michelle also offers to join the call)
(none)
--- 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/marl:/mark:/ Succeeded: s/ddocument/document/ Succeeded: s/fat/FAQ/ Succeeded: s/topic: Adminscribe: jo// Succeeded: s|https://w3c.github.io/market-data-odrl-profile/agendas/md-odrl-profile-agenda-2020-05-27.html|| Succeeded: s/y9u// Succeeded: s/my help to help//my section to help/ Succeeded: s/attic: agree/Atiq: agree/ Succeeded: s/timeing/timing/ Succeeded: s/.ACTION: Michael to work with Mark to come up with a document outline for Engagement Document// Succeeded: s/reagent, draft minutes// Succeeded: s/reagent, draft minutes// Succeeded: s/admin/Admin/ Succeeded: s/linked to new terms/linked to new terms https://w3c.github.io/market-data-odrl-profile/NewTerms.html/ Succeeded: s/https://w3c.github.io/market-data-odrl-profile/NewTerms.html// Succeeded: s/rrsagent: draft minues// Succeeded: s|https://w3c.github.io/market-data-odrl-profile/NewTerms.html|| Succeeded: s/scribe: ben// Present: jo Phil atic josh mark Natasha fred paul Ben ilya michelle rich olga Trisha laura Regrets: Renato 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: ben michael 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]