11:59:31 RRSAgent has joined #poe 11:59:31 logging to http://www.w3.org/2016/05/23-poe-irc 11:59:33 RRSAgent, make logs public 11:59:33 Zakim has joined #poe 11:59:35 Zakim, this will be 11:59:35 I don't understand 'this will be', trackbot 11:59:36 Meeting: Permissions and Obligations Expression Working Group Teleconference 11:59:36 Date: 23 May 2016 11:59:41 zakim, code? 11:59:41 I have been told this is https://mit.webex.com/mit/j.php?MTID=m4a8e3a5032905e8ce9ef1f4b569fcc2e Or by phone +1-617-324-0000, access code: 648 497 127 12:00:01 michaelS has joined #poe 12:00:41 Present+ Ivan 12:00:57 Present+ Renato 12:01:00 agenda: https://www.w3.org/2016/poe/wiki/Meetings:Telecon20160523 12:01:01 present+ michaelS 12:01:09 present+ victor 12:01:15 present+ jo 12:01:24 Brian_Ulicny has joined #poe 12:02:03 Any volunteers to Scribe? Or we take the next on the list: https://www.w3.org/2016/poe/wiki/Scribes 12:02:23 present+ Brian_Ulicny 12:02:38 regrets+ Mo, Simon 12:03:22 present+ Serena 12:04:37 scribe: jo 12:05:03 topic: Last meeting minutes 12:05:08 sabrina has joined #poe 12:05:37 https://www.w3.org/2016/05/16-poe-minutes 12:05:40 PROPOSAL: Approve minutes from 15 May 12:05:52 s/15/16/ 12:05:57 +1 12:05:58 +1 12:06:04 +1 12:06:21 RESOLUTION: PROPOSAL: Approve minutes from 16 May 12:06:39 RESOLUTION: Approved minutes from 16 May 12:06:42 s/PROPOSAL:// 12:07:11 benws2 has joined #poe 12:07:31 topic: Formal Semantics Note Editors 12:07:39 present+ benws2 12:07:52 Simon, Sabrena, Victor have volunteered to be editors 12:08:26 s/Sabrena/Sabrina/ 12:08:32 s/Simon/renato: simon/ 12:09:09 topic: Name of deliverables 12:09:28 renato: Carry over from last week, Action was on Ben 12:09:41 benws: I failed to make a proposal 12:09:51 reanto: carry over to next week 12:10:02 s/reanto/renato/ 12:10:38 topic: use cases 12:11:04 michaels: Phila changes some things this morning 12:11:22 phila: I did two things, 1 add a use case from Euro Data Portal 12:11:38 ... they have had to look through all licenses attached to data 12:11:51 ... they have made a grid of what inter operates with what 12:12:02 ... I made that into a requirement 12:12:41 ... key thing is to be able to express "this interpretation is a view of person x" i.e. provenance is important 12:12:59 ... not a legal claim 12:13:13 ... I also made a trivial amenment to Stuart's use case 12:13:39 michaels: Stuart's use case - use case 07 has been added 12:13:59 ... first item also appears in many others 12:14:10 ... "supports ODRL 2.1" 12:14:28 smyles has joined #poe 12:14:28 ... so we need to collect the current ODRL requirements 12:14:39 present+ smyles 12:14:44 Requirements page https://www.w3.org/2016/poe/wiki/Requirements 12:14:54 ... should this be done in the ODRL community or here? 12:15:24 (silence) 12:15:54 -> https://www.w3.org/community/odrl/wiki/Call_for_requirements_towards_an_ODRL_Linked_Data_profile ODR:L Reqs? 12:16:11 phila: I have found a page that has a call for requirements for a linked data profile 12:16:15 james has joined #poe 12:16:17 ... a lot of material there 12:16:37 ... however there is no existing document that collects all ODRL requirements 12:16:51 renato: there so is 12:16:55 https://www.w3.org/2012/09/odrl/archive/odrl.net/2.0/WD-v2req-20050213.html 12:17:37 ... after 1.1 we put together requirements based on feedback 12:17:51 ... we used that as a baseline 12:18:11 phila: need something in a stable place ... 12:18:11 present+ sabrina 12:18:39 ... the phil tests is "can I read this and assess whether POE meets those requirements" 12:18:50 s/tests/test/ 12:19:04 renato: this is not a normal working group 12:19:24 present+ 12:19:28 ... yes, we start from the baseline of ODRL 2.1 12:19:40 Apologies for joining late! 12:19:42 ... meets community requirements 12:20:08 ... not sure whether going trough the rtequirements for 2.0 2.1 gets us anywhere 12:20:21 s/rtequirements/requirements 12:20:31 s/trough/through/ 12:20:43 ... better to move on to new stuff 12:21:31 ... don't think that everything that is supported is in the requirements 12:21:51 phila: it's the delta we need to identify 12:22:05 renato: it's a given that 2.1 requirements are supported 12:22:10 q+ 12:22:53 ... michael and ben, we havea collection of use cases on the Web site and we need to end up with a note 12:23:17 ... are you happy with the way it's going, what input do you need 12:23:46 benws: need more use cases and I need to add some. Likely to be iterative in that some will suggest others. 12:23:58 ... after that I can feed back to group what the delta is 12:24:11 q+ 12:24:25 https://www.w3.org/TR/sdw-ucr/ 12:24:31 renato: looking at what others in W3C have done 12:24:34 q- 12:25:10 ... is this something that we want to copy? 12:25:30 phila: doubt we need to produce one that long 12:25:59 https://www.w3.org/TR/shacl-ucr/ 12:26:01 ... don't expect there to be 50 use cases, but the structure is very good, in-document hyperlinks are auto generated 12:26:10 ... so less work than you might think 12:26:48 q? 12:27:04 benws: we have discussed having a primer "how ODRL can solve your rights management issues" 12:27:16 ... can the use case morph into a primer? 12:28:15 renato: current ODRL has "Scenarios" to help the reader understand what problem is being solved 12:28:18 https://www.w3.org/2016/poe/track/actions/open 12:28:37 michaels: I looked at open actions page and there are some use case actions in there 12:28:46 ... people whould close actions if they have done it 12:28:53 q+ top talk about closing actions 12:29:18 q+ 12:29:24 ack m 12:29:37 q- 12:29:44 phila: I m leaving my actions open as I am still talking 12:30:01 rrsagent, list actions 12:30:01 I see no action items 12:30:54 ACTION-7? 12:30:54 ACTION-7 -- Benedict Whittam Smith to Provide use cases on financial data -- due 2016-04-18 -- OPEN 12:30:54 https://www.w3.org/2016/poe/track/actions/7 12:31:19 ack me 12:32:40 jo: if you think you have done your action, mark it as pending review 12:33:05 ... then on the next call it can get closed during the next call\ 12:33:12 q+ to review my action-4 12:33:16 s/call\/call/ 12:33:24 -> https://www.w3.org/2016/poe/wiki/Use_Cases#POE.UC.03_Published_article_with_embargoed_dataset Use Case 12:33:40 ACTION-4? 12:33:40 ACTION-4 -- Phil Archer to Write use case from VRE project about time limited restrictions and metadata -- due 2016-04-25 -- PENDINGREVIEW 12:33:40 https://www.w3.org/2016/poe/track/actions/4 12:34:01 phil: I have completed action-4 12:34:11 +1 12:34:18 close action-4 12:34:18 Closed action-4. 12:34:33 q+ 12:34:48 q- 12:35:13 renato: any other use cases you want to discuss on this call 12:35:33 benws: want to understand the point victor made about adding additional information 12:35:58 victor: I was requested to provide additional info, but need more info from editors as to how to do this 12:36:12 q+ to talk about numbering 12:36:32 ack b 12:36:52 michaels: I have raised some thing responding to victor 12:37:08 renato: victor can you get back to michaels 12:37:16 victor: yes I did 12:37:23 michaels: then I asked more questions 12:37:29 ack me 12:37:29 phila, you wanted to talk about numbering 12:38:14 phila: trivially, we are putting numbers on the use cases, which is nice, but they get transferred across to documents which turns out weird and confusing 12:38:31 ... let's use the not numbering 12:38:39 ... or we could refer by name 12:38:51 regrets+ caroline 12:39:52 jo: surely better not to number things since it makes it more difficult to change order (i.e. name them) 12:40:23 renato: give every use case a short name 12:40:32 ... two three words at most 12:40:33 Supports short names 12:40:52 +1 12:41:19 +1 12:42:21 PROPOSAL: we use short names to refer to use cases on both wiki and in the document 12:42:28 +1 12:42:32 + 12:42:33 +1 12:42:34 0 12:42:36 +1 12:42:36 +1 12:42:37 +1 12:42:38 +1 12:42:38 +1 12:42:47 RESOLUTION: we use short names to refer to use cases on both wiki and in the document 12:43:14 renato: back to use case analysis 12:43:30 ... anything more from the editors or anyone else 12:43:50 michaels: may deadline is "in doubt" 12:44:01 renato: june? 12:44:14 michaels: more realistic 12:44:25 W3C isn't going to worry about one month delay at this stage. Later stages, yes, but not yet. 12:44:31 PROPOSAL: New deliverable date for use cases is end June 12:44:40 q+ 12:44:41 +1 12:44:43 +1 12:44:46 +1 12:44:47 +1 12:44:48 +1 12:44:49 +1 12:44:50 +1 12:44:51 +1 12:44:52 +1 12:44:59 +1 12:45:01 q? 12:45:04 RESOLUTION: New deliverable date for use cases is end June 12:45:09 ack me 12:45:10 ack p 12:45:31 phila: if we are able to publish use cases end june, then so much the better 12:45:58 ... if we can add the first drafts of the other docs 12:46:07 ... then we have baseline and delta 12:46:22 ... same day publication of all three docs 12:46:24 +1 12:46:31 renato: agree 12:47:25 ... we will publish all three end of June, give the community some idea of where we are heading 12:48:15 phila: end of June is latest it can be done as summer hols kick in 12:48:48 q+ 12:48:50 renato: any moratoria or something? 12:48:57 phila: no 12:49:16 michaels: then we need a cut off date for use cases 12:49:30 q+ to throw a spanner 12:49:47 ... we wanted them in April. Some are still missing, so we need them early June otherwise they won't be included 12:50:01 renato: agree 12:50:30 phila: actually we can't publish exactly the alst week in June, but we would in 1st week of July 12:50:38 s/alst/last/ 12:50:56 +1 to Michael's deadline suggestion 12:51:10 renato: so back to michael's point, deadline for submission of use cases is June 6 12:51:55 benws: can't guarantee that any use case that comes in after thn will make the first draft document 12:52:09 s/thn/then/ 12:52:24 renato: any more on use cases? 12:53:17 topic: open actions 12:53:24 renato: we already looked at them 12:53:31 topic: any other business 12:54:01 renato: tpac is coming, if you can come please update your status 12:54:13 ... a "fun week" worth coming! 12:54:28 -> https://www.w3.org/2016/poe/wiki/Attending_F2F1 TPAC 12:54:31 phila: also if you can't go please also fill in your info 12:55:07 ... to help with logistics 12:55:15 [meeting closed] 12:55:18 RRSAgent, make logs public 12:55:30 rrsagent, make logs public 12:55:41 rrsagent, make minutes 12:55:41 I have made the request to generate http://www.w3.org/2016/05/23-poe-minutes.html jo 12:55:57 -1 12:56:00 -1 12:56:03 +1 12:56:05 +1 12:56:15 STRAW POLL: who can come next week? 12:56:18 -1 12:56:18 0 12:56:18 -1 12:56:21 +1 12:56:21 +1 12:56:24 +1 12:56:36 +1 12:56:40 -1 12:56:44 s/[meeting closed]// 12:56:58 phila: gingoistic comment of some kind 12:57:30 renato: next week's call will go ahead 12:57:36 [meeting closed] 12:57:45 Serena has left #poe 12:57:49 rrsagent, make minutes 12:57:49 I have made the request to generate http://www.w3.org/2016/05/23-poe-minutes.html jo 12:58:05 chair: Renato 12:58:18 RRSAgent, make minutes 12:58:18 I have made the request to generate http://www.w3.org/2016/05/23-poe-minutes.html phila 12:59:21 jo has left #poe 14:22:58 jo has joined #poe 15:09:19 Zakim has left #poe 16:28:33 jo has joined #poe 16:29:33 ivan has joined #poe