<jo> scribe: phil
RESOLUTION: Accept minutes of last meeting
<jo> scribe: jo
Ben: various definitions have
been circulated and reviewed
... in the end a notification refers to an event - report
refers to a state of affairs
... any comments
... straw poll
<Laura> +1
<Ilya> 0
Ilya: please clarify the definitions
ben: (illustrates the definitions)
<Ilya> Change vote to +1
RESOLUTION: Adopt the definition of notify and report as described above
https://github.com/w3c/market-data-odrl-profile/issues/17
Ben: the terms Creditor and
Debtor are confusing and we have been looking for better
terms
... we said we'd go away and look for other possible terms
Natasa: I like requiring and responsible parties
Ben: unfortunately it does not
work
... someone undertakes action and someone receives the
action
... can have different requirer and beneficiary
Ilya: licensor and licensee
ben: not quite right either
... duties may refer to different parties than the
signatories
(further discussion of possible terms)
ben: duties may be independent of data/content - needs to be independent and abstract
JFB: Obligor - beneficiary?
ben: is that clear enough
adamH: trying to understand what
actions are performed
... e.g. payment and so on?
ben: don't know how far we'd go
on that
... details on currency, count, periodicity
laura: would it help to introduce something like "agent"
JFS: not agent
phil: why do we need a term for
beneficiary?
... why do we need something to generically identify
something
<jo_> scribe: jo_
PROPOSED RESOLUTION: Promisor and Promisee are the preferred terms for the subject and object of duties
(further discussion of terms)
Laura: problem is the context dependency
Jo: that's why I prefer a grammatical construction like subject/object
ben: i agree
... let me take an action away to put some of the preferred
terms in examples for a vote next time
<scribe> ACTION: Ben to create examples where the various terms discussed in place of creditor and debtor are shown in context
ben: we were happy with using
effective dates when we spoke about this
... this means that the identifiers change and that can cause a
problem
... there is a trick to stabilise the identifier
... which is to use versioning
... add the cost of indirection from the stable
identifier
... deviation from standard ODRL
... so how important is it that something retains it
identifier
phil: prefer to maintain the id over time
jo: are we confusing labels and ids
???: important to maintain the id
ilya: important to retain stable identfier
caspar: keeps things immutable ... important for assets, less so for permissions
graham: thinking around legal proceedings, persistent ids make a clearer case
ben: can we take a vote now
... or should I go away and write some more
<scribe> ACTION: Ben to follow up after the meeting including with Caspar as to clarification of how this might be handled outside the model
https://w3c.github.io/market-data-odrl-profile/discussions/2020-08-19/topics#properties-of-resources
Ben: I've relied on Phil's work
on this
... would like him to speak to it
Phil: not sure I can pick up on
this
... most recognised, but some are resource and characteristics
but some are variable
ben: your idea of a resource is
described as a source
... resource is something like real time gold futures
... has a provider
... the property resource ... this is the delayed version of
that
... have to point back to the resource you are delaying
... also asset class, content type
... allows segmentation
... (further discussion of properties)
... are there some things missing from the list
Ilya: professional vs non-professional?
ben: constraint on the permission
phil: several geographic
aspects
... this is about the centent itself
... rather than usage rights
???: (indistinct)
ben: real time always intraday and end of day always not
laura: currency?
... not related to license, what a system might need to
know
AdamD: method of delivery?
Phil: differentiate resource from
method of delivery is useful
... we'd want to describe method of delivery spearately
ben: product might need this, at a level above
laura: same for platform
... is that a property description
Ben: think we should capture that
Olga: what is the name?
ben: it has a label plus a
universal identifier
... please look at these definitions so we can take a vote at
the next meeting
... open an issue to make a comment
(none)
--- Call closed
<jo> scribe: jo
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/LAdmin/Admin/ Succeeded: s/JFB/JFS/ Succeeded: s/vars/vers/ Succeeded: s/sohow/so how/ Succeeded: s/Propeorties/Properties/ Succeeded: s/endof/end of/ Succeeded: s/lable/label/ Succeeded: s/Topic AOB// Succeeded: s/temporal aspects/Temporal Aspects/ Succeeded: s/unknown: importnat to main the id/???: important to maintain the id/ Succeeded: s/for a vot/for a vote/ Succeeded: s/???/Olga/ Present: Jo Ben Ilya Laura Steve natasa phil joshua caspar adamD adamH sam_Gibson jfb graham Regrets: renato trisha chris MarkB MarkD Stephen_D Paul_K Rachel_K Alex_C David_S Tom_D Atiq_K Aaron_G Found Scribe: phil Found Scribe: jo Inferring ScribeNick: jo Found Scribe: jo_ Inferring ScribeNick: jo_ Found Scribe: jo Inferring ScribeNick: jo Scribes: phil, jo, jo_ ScribeNicks: jo, jo_ Agenda: https://w3c.github.io/market-data-odrl-profile/agendas/md-odrl-profile-agenda-2020-08-19.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: ben 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]