<jo_> scribe: joshuaCornejo
<jo_> Agenda: https://w3c.github.io/market-data-odrl-profile/agendas/md-odrl-profile-agenda-2020-11-11.html
<jo_> Last Meeting: https://www.w3.org/2020/10/28-md-odrl-profile-minutes.html
Jo: zoom access
Ben: to get automated transcription, you have to buy at least 10 licences
Jo: seeing if we can get W3 Zoom's access, wait to see feedback
Ben: move to Teams as plan B
Jo: maybe we can try that
out
... check on archived - public but not listed. So that
conversations of PoC are not listed. W3 is looking into it.
Mark: we will be hearing from Atiq today, Roy maybe next session.
RESOLUTION: Accept minutes of last meeting
Jo: we've reviewed the actions, we can record that the minutes of the last meeting are accepted.
Jo: item #2 updates from Ben and Mark
<ben> https://w3c.github.io/market-data-odrl-profile/md-odrl-profile.html
Ben: I will put the link to the
standards document in the chat, finding myself with more time
that I had previously.
... I've made much progress, writing up
... quickly take people through it and discuss next steps
... you will see big sections - supply chain with party roles,
resources, sources, assets, activities and other items in terms
of market data licensing
... things that market data likes to count and some other
specifications
... things like asset classes and a whole lot of concepts that
exist in our industry
... some concepts are much more specific on the validity of a
license
... And there is another section on constraints
... critical to the validity of a license, for example
timeliness of delivery, deriving data, purposes, etc
... these are all things market data licenses control
... and there is a section on time
... at this stage what we need to get right is if we got the
right concepts, the right names and the right definitions
... I am going to ask and get the people to pick a section and
check that we got the right concepts
... and that the definition in blue of the concepts are
accurate
... and we can iterate and improve
... one section missing is on what actions
<ben> https://github.com/w3c/market-data-odrl-profile/edit/gh-pages/ActionsAndPurposes.md
Ben: we can see a number of
patterns arriving
... (speaks about some specific example)
Jo: do we want to record names of people vs sections
Ben: let's put the section name in the chat
Jo: in the webex
(Logistics going on Webex for assigning sections)
<jo_> ACTION: All to review doc as stands for meaning and so on
<jo_> ACTION: Ben will take clarification of actions to the list
Jo: let us move to PoC update
Mark: Ilya gave us a high level overview during the last section, Atiq if we could hear from you but not too deep
Atiq: Unfortunately I missed Ilya's as I was on holiday
Mark: it is technical control
Atiq: it is a question of usage
rights, were we see more than yes/no answers and look at ODRL
in more detail.
... we are keen of leveraging the aspect of obligations and
duties
... Duties ...
... to see if this is something that is achievable
... we can focus on disclaimers and attributions
... the specific scenario is redistribution
... we want to go down this path as it provides a bit more
criteria
... it is a good balance for technical exploration and provides
a healthy debate
... we can represent it in ODRL and validate the results we can
get from the query, more than yes/no
... and we are keen to explore the workflow aspects that come
at the back of the obligations
... we can have a system of disclaimers, so they can be set up
at the center of the data.
... there will be a number of things that will come out at the
end of this and some things will be useful feedback and
discussion points
... for example at what point obligations, responsibilities and
if the vendor provides the sufficient language, how and where
do they provide it.
... can we flexibly express this or push to standardise
it?
... we believe that automation will allow for better
compliance
... that is where we are going with this, still need to work
out which contract will be scoped within this.
... this side of Christmas is not realistic, but maybe go to
February/March
Jo: open for questions for Atiq?
Mark: I love that the focus of
this PoC is so complementary to Ilya's
... and that the focus of attribution is complex but
interesting for a PoC
Jo: I was going to ask, presumably you are confident this is a good bite size PoC
Atiq: maybe the end of January is too tight, we want a bit longer time to make sure
Jo: let's keep that under review,
we don't mind terribly if we slip a bit more than
January.
... any other comments?
Ben: does that mean if a permission is valid or not? And you are going to be able to check with the attribution system if the duty has been fulfilled and if this permission is still valid?
Atiq: yes, (explains the mechanics of that fulfilment)
<jo_> ACTION: MarkB to arrange for PoC Leads to document their PoC's in GitHub
Jo: anymore questions for Atiq?
<jo_> Thanks to Josh for Scribing! (Again)
<jo_> --- Meeting closed ---
<jo_> ACTION: MarkB to review Supply Chain MetaModel
<jo_> ACTION: Caspar and Atiq to review Duties
<jo_> ACTION: Nigel and Colleagues to review all sections
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/duries/duties/ Succeeded: s/So conversations/So that conversations/ Succeeded: s/Duties .../... Duties .../ Succeeded: s/Acion/Action/ Succeeded: s/Caspar/Caspar and Atiq/ Succeeded: s/ACTION: Caspar and Atiq to review Duties// Succeeded: s/ACTION: MarkB to review Supply Chain MetaModel// Present: jo ben josh mard markb adam atiq caspar fred_schultz laura nigel_phelan phil samantha trisha michelle olga NSE Regrets: renato Found Scribe: joshuaCornejo Inferring ScribeNick: joshuaCornejo Agenda: https://www.w3.org/2020/10/28-md-odrl-profile-minutes.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: actions all atiq ben caspar clarification colleagues markb nigel of take will 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]