See also: IRC log
<victor> today I prefer *not* to scribe, as being a day-off in Spain I am not in my office
<renato> Scribe: serena
victor: are we supposed to distribute the link of the pubs on the experts to ask for feedback?
renato: yes, feel free to send the link to everyone
<renato> Proposed: approve https://www.w3.org/2016/07/18-poe-minutes
+1
<mmcrober> +1
<benws2> +1
<smyles> +1
<victor> +1
RESOLUTION: https://www.w3.org/2016/07/18-poe-minutes
renato: in the next few meetings, we will analyse sets of use cases, look at them and make them clearly understandable
<smyles> https://w3c.github.io/poe/ucr/#busProcRegulation
renato: use case 4
<renato> serena: technical documents which are regulations (eg first use of product has these constraints)
<renato> ... also different versions of these documents
<renato> renato: what new req are needed for this UC?
<renato> requirement: the first usage
<renato> mo: very broad UC
<renato> ... break down into lower level UCs...eg combinations of conditions
<renato> ACTION: serena break down into lower level UCs [recorded in http://www.w3.org/2016/07/25-poe-minutes.html#action01]
<trackbot> Created ACTION-19 - Break down into lower level ucs [on Serena Villata - due 2016-08-01].
<smyles> https://w3c.github.io/poe/ucr/#newsPermAndRest
renato: use case 7
smyles: new situation where you have two kind of people involved: editor, rights holders. They want to get paid for photos, you can use this if attribution. Editors: can I publish it with my mobile app? Can I combine this photo with others? They do need to know if there are restrictions, and so on. Often the relationship between the two kinds of users is a kind of repeated thing.
ODRL allows the expression of permission and restrictions over a piece of content, but not support for expressing reuse.
smyles: create a bundle of
permission and restrictions.
... with odrl you need an asset
mmcrober: not in RDF. The inherent flexibility of RDF should apply to the other encodings as well.
<smyles> https://www.w3.org/ns/odrl/2/ODRL21#sec-examples
smyles: for the editorial example: I have an action and a location, but it is not exactly a policy so no asset
mmcrober: it is a philosophical
issue. Similar to CC licenses.
... interesting point: xml model of ODRL requires you to
associate a set to an asset, then it is impossible to express a
licence without RDF. Am I inventing a use case now?
<smyles> https://www.w3.org/community/odrl/model/2.1/
benws: one of the issues is to identify a subset of data, there is not a clear answer to that. Answering this question is not a goal of the ODRL specification.
smyles: when you see a photo, what are you identifying? we need to be clear on that
victor: no special problem here, if the asset is properly defined
benws: I want this policy to apply to the data returned by this query, how to represent that?
victor: this example is implemented in practice. for use the asset is the result of the asset.
but it was our interpretation
renato: if I do create a set, how do I refer to it in a real policy? We need to solve the problem of referring to the sets.
mmcrober: new level of indirection. In RDF you have subject URI for free, differently from xml. If you define a set having an identifier (uid), that is missing in xml but not in rdf, tyou may express that the policy which applies is x.
renato: q?
<renato> Clarify the concept of "Set" across all encodings
smyles: clarify and making equivalent the encodings, and multiple instances of content and be able to apply policies to a list of items.
mmcrober: the key thing of collection of set is to be able to apply a policy to all of the members as it is done to all the individuals.
renato: party is an individual or a group?
mmcrober: the complication with asset is that they can be combined
: with assets if you grant the group it could apply to the combination of the asset or the group
: there is plenty of situations where both of them are used, the latter has to be consistent with the former one
victor: very nice to be able to specify flexible specifications, but abuse of the semantics
mmcrober: URI schemas
smyles: policy: you can use this if you pay me 30Euros? I can use anyone of these photos or some of them.
renato: asset are the 50 photos
<renato> Req: update Asset model to enable identification of group of items?
mmcrober: if it is a group of asset then the policy applies to the asset as an entity
renato: we will update the list
of requirements with this additional requirements
... use case 9
<smyles> https://w3c.github.io/poe/ucr/#baseProduct
benws: for the moment if you have a price this is a permission, but if you have several permissions, and we bundle together with a price it is difficult.
renato: like a duty on the entire policy
: the duty or a payment on the whole policy
benws: payment, but we express payment as duty
mmcrober: it is possible that it is in the latest version of RDF
victor: yes, the price can be applied to the rule
mmcrober: the domain of the duty property is the only thing that could be missing
: missing property domain
renato: we will continue next week
: the rest of the agenda items is about issues in the tracker
renato: any other business?
This is scribe.perl Revision: 1.144 of Date: 2015/11/17 08:39:34 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found Scribe: serena Inferring ScribeNick: Serena WARNING: No "Topic:" lines found. Present: renato serena victor CarolineB smyles mmcrober Regrets: Michael Sabrina Phil Ivan Brian James Agenda: https://www.w3.org/2016/poe/wiki/Meetings:Telecon20160725 Found Date: 25 Jul 2016 Guessing minutes URL: http://www.w3.org/2016/07/25-poe-minutes.html People with action items: serena WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report[End of scribe.perl diagnostic output]