<benws> https://www.w3.org/2020/06/10-md-odrl-profile-minutes.html
<Natasa> Overview of the webinar
<scribe> meeting: Rights Automation Community Group Teleconference
<scribe> chair: Ben
<scribe> scribe: Phil
https://www.w3.org/2020/06/10-md-odrl-profile-minutes.html
Mark: described webinar and the poll results
Ben: warm welcome to new members of the group
Ben: good activity on the github
group
... roles in the supply chain is first area being
modelled
... we have originators
... then we have providers, dont generate but do distribute
resources
... then we have distributors who are assignees of rights
... then we have service facilitators, not part of the exchange
of rights in the supply chain
... organisations typically play multiple roles
Mark: introduced new part in the
supply chain
... we cant assume creator always administers the rights
... some creators will contract this out to a third party
... so mark proposes the term "administrator"
Ben: is the administrator involved in distribution?
Mark: sometimes yes and sometimes no
Ben: can we distinguish between those roles?
Mark: sounds right
... interesting that the originator is at the top of the supply
chain, and assigns the role to another
Michael: raised some questions around this
Steven: ceratin firms do licence on behalf of exchanges, idea of administrator could work
Mark: asked about tech distribution of CME data
Michael: CME uses S&P and DME for distribution
Graham V: in previous standard we had role of licensing "agent"
Ben: sounds like the "administrator"
Mark: agree
Ben: suggest we resolve to add terms to standard, asks for objections
RESOLUTION: terms to be added to standard
Ben: assets, sources and
resources is the next set of definitions
... ODRL defines an asset
... allows us to segment resource using rules
... we have a use case where and asset become a resource and it
moves down the supply chain
... therefore we want a source to be a root resource, the
original origin of the data
Phil: i agree that source, resource and asset works as described for refinitiv
Ben: in answering a question
about when a resource changes
... we are trying to capture a number of transformations that
do not change the resource
... if we comingle two resources under two rules, then control
over the combination is a combined rule
Mark D: re tick history, we have a licence from a provider to capture tick history, but provider said it was their property
scribe: we have to deal with provider and originator
Ilya: this is a bit different from a derived product, a combination of orinator and deriver's rights
Ben: What we are definitely
trying to model is where a new licence is created, but where it
must be compliant with rights received from originator
... we want compliance checks to be automatic
... including where it's derived
Ilya: an exchange may have an embargo period, but the transit provider may want to apply additional restrictions
Ben: yes that needs to factored in
Atiq: two use case
... redistribution
... derivation
... consider firstly versioning of restrictions we need to work
out
... second two independant sources means unique identity needs
to be resolved
Ben: yes, two complex
points
... please could Atiq create an issue on github for the
versioning
... either need some provenance or create a new licence that
will always satisfy the original licences before comingling
Atiq: i think there's a debate to be had between those two approaces to the combining issue
Ben: asks Atiq to create an issue on github for this one too
RESOLUTION: terms for source and resource and asset to be added to standard
Ben: next issue is #5 on
github
... derivation of new original works, provider want to control
how derived works are used
... want to restrict consumer rights
... provider can put a duty in to control redistribution or
derivation
... when a consumer writes a policy they are under a duty to
check compliance from original provider
... it's a "subsumption" check
... in this way we can control using "next policy" construct
down the supply chain
... asks Mark for view on this, needed? meets use cases?
Mark: yes, needed.
... typically this is done using a general set of policies,
augmented by a specific set of policies
... the specific licensing agreement means the provider
controls downstream
Ben: does the CME put this in the lliceces?
Mark: some cases yes, other cases needs a new specific licence on request
Michelle: where index or other financial product where does this fit in?
Ben: seen examples where derivations can be allowed but with refinements that prohibit certain actions
Stephen: CME typically have a
direct licence for rights to derive with refinements and
limitations in a number of areas, i.e. index can be used on
certain platforms only
... sometimes derived is governed just as distribution,
sometime very specific to the thing derived
Ben: we will explore this over
coming weeks and see if we can capture where derivations vs
just distribution
... terms around duties will be discussed in the next
session
Ben: none, thanks everyone
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/What do we have left to do?// Succeeded: s/nooo!// WARNING: Replacing previous Present list. (Old list: Ben, Aaron, Atiq, Elizabeth, Fred, Graham, Josh, Jeremy, Michael, Laura, Mark_B, Mark_D, Natasa, Ilya, Stephen, Trisha) Use 'Present+ ... ' if you meant to add people without replacing the list, such as: <dbooth> Present+ Mark, Ben, Graham, Josh, Laura, Natassa Present: Mark Ben Graham Josh Laura Natassa Mark_D Ilya Michelle Atiq Michael Elizabeth Aaron Stephen WARNING: Replacing previous Regrets list. (Old list: renato, Jo) Use 'Regrets+ ... ' if you meant to add people without replacing the list, such as: <dbooth> Regrets+ jo, Renato Regrets: jo Renato Found Scribe: Phil Inferring ScribeNick: phil Agenda: https://w3c.github.io/market-data-odrl-profile/agendas/md-odrl-profile-agenda-2020-06-24.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.)[End of scribe.perl diagnostic output]