11:50:18 RRSAgent has joined #poe 11:50:18 logging to http://www.w3.org/2016/09/05-poe-irc 11:50:20 RRSAgent, make logs public 11:50:20 Zakim has joined #poe 11:50:22 Zakim, this will be 11:50:22 I don't understand 'this will be', trackbot 11:50:23 Meeting: Permissions and Obligations Expression Working Group Teleconference 11:50:23 Date: 05 September 2016 11:57:27 michaelS has joined #poe 11:57:58 renato has joined #poe 11:58:24 james has joined #poe 11:58:56 Serena has joined #poe 11:59:12 present+ Serena 11:59:44 present+ michaelS 12:00:04 CarolineB has joined #poe 12:00:49 present+ renato 12:01:25 RRSAgent, make logs public 12:01:38 victor has joined #poe 12:01:46 present+ victor 12:01:47 present+ james 12:03:02 present +CarolineB 12:04:28 present+ Ivan 12:04:45 agenda: https://www.w3.org/2016/poe/wiki/Meetings:Telecon20160905 12:05:18 scribenick: CarolineB 12:05:27 scribe Carline 12:05:35 scribe: CarolineB 12:05:35 scribe: Caroline 12:05:39 scribeNick: CarolineB 12:05:49 Approve: https://www.w3.org/2016/08/29-poe-minutes 12:06:07 Hmmm - when I try to join the webex I get: The meeting has been cancelled or ended! 12:06:19 s/Approve:/Proposed to approve last week's minutes / 12:06:20 Is there something I missed while away? 12:06:34 Click on the webex link here: 12:06:36 https://www.w3.org/2016/poe/wiki/Meetings:Telecon20160905 12:06:57 last weeks minutes approved 12:07:01 Topic: Use Cases 12:07:41 Topic: UC17 12:07:43 Many thanks 12:07:45 UC.17 http://w3c.github.io/poe/ucr/#assetInSet 12:08:58 UC 17 concerns groups of assets that are all subject to the same offer 12:09:32 ... wants to link offer to the set with contstraint saying "applies to 1" 12:10:07 james: offer would point to set rather than single assets 12:10:20 q+ 12:10:24 ... and you'd choose one 12:10:30 q+ to talk about https://www.w3.org/TR/powder-grouping/ 12:11:33 ack b 12:12:23 benws116: TR shares this one. Can we borrow terminology from elsewhere? 12:13:11 The requirement derived from UC17 is also supported by one of the five requirements from UC1, which claims the same. The idea of saying "this policy applies to EACH of the assets in this group" is equivalent to the semantics of the Group, where an equivalent idea is convey ("each party in this group is an assignee") 12:13:36 phila: is leaving in 15mins. puffs up powder but nobody uses it 12:14:31 -> https://www.w3.org/TR/powder-grouping/ POWDER Grouping 12:14:38 ... but it provides good mechainism for grouping things and listing exceptions. Its based on idetnifier patterns 12:16:16 renato: yes this ties to UC1 as victor says and there is a definite need 12:16:32 present+ phila 12:16:47 present+ benws 12:17:20 US.22 https://www.w3.org/2016/poe/wiki/Use_Cases#Deletions_Must_be_Propagated 12:17:36 UC.22 12:17:41 james_ has joined #poe 12:17:46 Topic: UC.22 12:18:02 .. apologies, my connection is a bit flakey 12:18:53 benws116: its where changes in master set must be reflected in related data 12:19:03 renato: its a duty then? yes 12:19:18 q? 12:19:27 q- 12:19:58 benws116: re personal data - this will be needed in EU from 2018 12:20:25 UC.23 https://www.w3.org/2016/poe/wiki/Use_Cases#Synchronization_in_a_multilayer_music_description_environment 12:20:46 Topic: UC.23 12:22:02 renato: relates to packaging up music and score etc together. Needs a new action around permission and prohibition around sync. Its about coleections of resources and being able to refer to ndividuals 12:22:11 ... or individuals that is 12:22:55 ... when play audio and there are graphical notes, to follow notes- keep music and notes synched 12:24:33 benws116: can we all think about other examples of sync in this way? 12:25:11 Within the Media Value Chain Ontology (ISO/IEC 21000:19), we also defined Synchronization as a first class action that was needed. 12:26:04 NON official spec http://dmag.ac.upc.edu/ontologies/mvco/ 12:26:11 victor: for mpeg21 is was one of the main actions along with "distribute" etc 12:27:15 renato: next week 12th is last call before F2F lets finish off the current use cases 12:28:39 https://www.w3.org/2016/poe/wiki/Requirements 12:28:43 renato: we need to prep use cases for discussion at F2F. By putting requirements on a wiki? 12:29:10 benws116: happy to work on this 12:29:59 michaelS: some reqs have open issues. will I filter these out? yes 12:31:05 michaelS: asks question about style. Would we propose solution? Not yet 12:32:36 victor: will original ODRL requirements be in the list? 12:33:14 renato: not those that are already in 2.1. just starting from the base line and moving forward from there 12:33:37 https://www.w3.org/2012/09/odrl/archive/odrl.net/2.0/WD-v2req-20050213.html 12:34:28 Topic: Admin 12:35:05 Serena: Done action 19 this morning 12:35:40 https://www.w3.org/2016/poe/track/issues/raised 12:36:13 renato: we still need to talk about ODRL profiles 12:37:00 ... issue 8. heading towards this: from UCR document the group will decide whcih will be accepted and implemented 12:37:40 ...... issue 9. potential note about best practice 12:37:46 TOpic: AOB 12:40:58 trackbot, end telcon 12:40:58 Zakim, list attendees 12:40:58 As of this point the attendees have been Serena, michaelS, renato, victor, james, Ivan, phila, benws 12:41:06 RRSAgent, please draft minutes 12:41:06 I have made the request to generate http://www.w3.org/2016/09/05-poe-minutes.html trackbot 12:41:07 RRSAgent, bye 12:41:07 I see no action items