11:54:53 RRSAgent has joined #poe 11:54:53 logging to http://www.w3.org/2016/04/04-poe-irc 11:54:55 RRSAgent, make logs public 11:54:55 Zakim has joined #poe 11:54:57 Zakim, this will be 11:54:57 I don't understand 'this will be', trackbot 11:54:58 Meeting: Permissions and Obligations Expression Working Group Teleconference 11:54:59 Date: 04 April 2016 11:56:05 zakim, code? 11:56:05 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 11:57:18 michaelS has joined #poe 11:57:23 present# michaelS 11:57:26 magyarblip has joined #poe 11:58:13 present+ simonstey 11:58:15 phila has changed the topic to: agenda is at https://www.w3.org/2016/poe/wiki/Meetings:Telecon20160404 access code: 648 497 127, password poe 11:58:38 agenda: https://www.w3.org/2016/poe/wiki/Meetings:Telecon20160404 11:58:43 chair: Renato 11:58:44 renato has joined #poe 11:59:04 present+ james 11:59:12 present+ phila 11:59:16 mmcrober has joined #poe 11:59:33 victor has joined #poe 11:59:36 present+ renato 11:59:46 present+ jo 11:59:51 present+ victor 11:59:53 present+ ivan 12:00:11 present+ paulj 12:00:23 rrsagent, draft minutes 12:00:23 I have made the request to generate http://www.w3.org/2016/04/04-poe-minutes.html jo 12:00:46 regrets+ whoever 12:00:47 rrsagent, make logs public 12:00:57 regrets+ Sabrina Kirrane 12:01:00 regrets- whoever 12:01:02 rrsagent, draft minutes 12:01:02 I have made the request to generate http://www.w3.org/2016/04/04-poe-minutes.html jo 12:01:06 present+ mmcrober 12:01:26 present+ michaels 12:01:49 present+ magyarblip 12:02:25 scribe: simonstey 12:03:13 agenda https://www.w3.org/2016/poe/wiki/Meetings:Telecon20160404 12:03:15 topic: Preliminaries 12:03:16 present+ nandana 12:03:37 renato: approval of last week's minutes 12:03:45 https://www.w3.org/2016/03/24-poe-minutes 12:04:01 PROPOSED: Accept last week's minutes 12:04:06 +1 12:04:08 +1 12:04:08 +1 12:04:17 +1 12:04:33 RESOLVED: Accept last week's minutes 12:04:33 topic: use case template 12:04:34 +1 12:04:37 https://www.w3.org/2016/poe/wiki/Use_Cases 12:04:44 +1 12:04:49 renato: michael proposed a first template 12:05:05 something weird happening on webex - apparently i am now host 12:05:35 i am rejoining webex now too... 12:06:05 benws has joined #poe 12:06:10 [some issues with webex] 12:07:12 michaelS: the use case page now contains a uc template 12:07:13 present+ benws 12:07:28 ... inspired from other group's template 12:07:45 ... demographic information about uc owner 12:07:59 @phila how do I do that? 12:08:38 ... template also contains natural & formal language expression sections for describing the uc 12:08:43 I have made the request to generate http://www.w3.org/2016/04/04-poe-minutes.html phila 12:09:10 (done, I am host) 12:09:20 ... technical expression may include information relating to data model 12:09:53 ... based on that template, I've created an example uc 12:10:15 q+ to talk about process 12:11:10 ack me 12:11:10 phila, you wanted to talk about process 12:11:12 ... the included "dummy use case" is actually a real world uc 12:12:01 phila: one thing that worried me was the fact that you said you had an offline discussion with james to set up the template 12:12:26 q+ 12:12:34 ... such discussions need to be made online/with consent of the group 12:12:38 q+ 12:12:53 q? 12:13:08 michaelS: do we need contact details for ucs? 12:13:31 phila: if you want to, that's good.. but it's not essential 12:14:07 ... the more real world a uc is, the better 12:15:09 ack mag 12:15:11 magyarblip: looking at the uc, it's way more extensive than I would have expected at this stage 12:15:36 I'd echo that - it seems like an expression of how ODRL is actually used in practice, rather than a *desirable* usecase 12:15:52 renato: I think we should clearly state what parts are optional/mandatory 12:16:58 renato: we should try to express what we want to have/what we require, rather than already providing a solution 12:17:27 ack me 12:17:44 mmcrober: I'm happy with the template 12:17:57 ... I would like to see a minimum dummy uc 12:18:39 ... I can provide research related ucs 12:19:05 action: Mo to provide use case from research and education domain 12:19:05 Created ACTION-1 - Provide use case from research and education domain [on Mo McRoberts - due 2016-04-11]. 12:19:07 for info, the Research & Education Space I refer to is: https://bbcarchdev.github.io/res/ 12:19:24 victor: we should also consider requirements 12:20:45 q+ to talk about Reqs 12:20:51 q+ 12:21:28 phila: yes, requirements need to be explicit 12:21:41 ack phila 12:21:41 phila, you wanted to talk about Reqs 12:21:50 ... the same requirements can come from multiple ucs 12:21:51 q+ 12:22:20 ... you may end up merging requirements, point to other requirements, ... 12:22:31 ... we should have them at the end of each uc 12:23:01 simonstey: Just think about what you said earlier about there being no new requirements. We need to somewhere make those old requiremetns explicit 12:23:30 ... No one knows all the old ODRL requirements. We can take tham as a basis and revise them, rather than just storing new requirements. 12:24:01 benws: I wanted to say we should distinguish between uc and requirements gathering 12:24:18 ... we shouldn't set the bar so high 12:24:22 q? 12:24:26 ack s 12:24:29 ack b 12:24:37 ... but should try to gather as much input as possible 12:25:23 renato: I think we should first collect use cases and in a later phase decide whether we want to keep them -> derive requirements 12:25:55 ... we should set an easy entry point for people to contribute 12:26:38 ... we might end up with removing the technical expression part 12:27:02 TOPIC: Use Case collection and review process 12:27:43 action: Renato to go to the ODRL CG to ask for use cases 12:27:43 Created ACTION-2 - Go to the odrl cg to ask for use cases [on Renato Iannella - due 2016-04-11]. 12:27:46 renato: should we make a wider call for use cases? e.g. ODRL community group or any other group? 12:27:56 q+ 12:28:00 action: phila to gather use cases from BigDataEurope project 12:28:00 Created ACTION-3 - Gather use cases from bigdataeurope project [on Phil Archer - due 2016-04-11]. 12:28:20 ... or do we think we will have enough input from our group members? 12:28:29 Use cases can come from anywhere - and are welcome 12:28:37 It is then for the Wg to decide whether to act on them 12:28:44 michaelS: are we allowed to ask colleagues for suitable input? 12:29:43 q+ to wonder about the IP context around contribution of use cases 12:29:50 q+ to talk about public-poe-comments 12:30:01 ack m 12:30:07 ack me 12:30:07 jo, you wanted to wonder about the IP context around contribution of use cases 12:30:10 paulj: we may consider asking formally for external input 12:30:38 public-poe-comments@w3.org 12:30:46 jo: how can the group accept input from non-members? 12:30:53 smyles has joined #poe 12:31:24 phila: I think it would be wise to ... [broke up] 12:31:50 q+ 12:31:57 ack p 12:31:57 phila, you wanted to talk about public-poe-comments 12:31:58 ack phila 12:32:06 present+ smyles 12:32:08 Use cases are pretty free of IP 12:32:23 ivan: I think the question is really related to uc now, but the same question may also come up later 12:32:34 The danger might be that we include a load of reqs that can *only* be met by using a specific piece of software - then we'd be in trouble. 12:32:45 ... if someone external wants to contribute to the spec 12:33:04 Use Case doc is a Note (non-normative) so IP considerations are less important. 12:33:16 ... that's not relevant now, but keep in mind that it might come up later 12:33:35 q? 12:33:36 q? 12:33:37 ack i 12:33:40 q+ 12:34:00 ack j 12:35:03 jo: can we formally note how external contributions shall be made 12:35:29 Summary - we don't need to be too concerned about IP issues related to the use case document due teo the nature of the document. However, the ideal method of submission is vai the public comments lailing list which carries some IP disclosure info. 12:35:55 s/ vai the public comments lailing/ via the public comments mailing 12:36:07 public-poe-comments 12:36:20 PROPOSED RESOLUTION: ANyone (outside the grou) can corntribute use cases without there being an IP impediment, however it's alwyas best to contribute on public-poe-comments@w3,org 12:36:47 s/ANyone (outside the grou/Anyone (outside the group 12:36:56 +1 12:37:00 I think that's fair 12:37:07 +1 12:37:09 PROPOSED RESOLUTION: Anyone (outside the group) can corntribute use cases without there being an IP impediment, however it's alwys best to contribute on public-poe-comments@w3.org 12:37:20 +1 12:37:25 james has joined #poe 12:37:26 +1 12:37:28 s/ corntribute/ contribute 12:37:56 RESOLVED: Anyone (outside the group) can contribute use cases without there being an IP impediment, however it's alwys best to contribute on public-poe-comments@w3.org 12:38:33 renato: wg members can create additional uc in the wiki 12:38:52 ... externals will be asked to provide their uc via mail using our template 12:39:10 ... we will then move them to the wiki 12:39:21 q+ 12:39:22 i am going to reach out to the bisg (book industry standards group) who have been doing related work, not so much odrl as best practices for the industry 12:39:28 q+ 12:39:38 ack m 12:39:41 Yes, WG members should subscribe to the public comments list (it's not automatic) 12:39:43 oh bother 12:40:07 q- mmcromber 12:40:10 mmcrober: may I propose to note that resolution on the uc wiki page? 12:40:17 simonstey: yes please 12:40:17 q+ mSteidl 12:40:20 q- 12:40:21 ack mm 12:40:24 +1 anything we can point folks to that introduces them *gently* to the area 12:41:18 Our wiki is only writable by WG members 12:41:21 renato: editing the wikipage is limited to whom exactly? 12:41:27 phila: only wg members can edit it 12:41:37 q? 12:42:04 ack m 12:42:29 michaelS: I'll update the uc page tomorrow 12:43:02 TOPIC: Deliverables 12:43:07 renato: 12:43:18 s/renato:// 12:43:45 renato: in the charter we've listed 5 contributions 12:44:09 ... we wanted to get the core specs/recommendations out asap 12:44:53 ... we need to come up with editors for each of the 5 specs 12:45:31 ... the vocabulary and the ontology might be very similar contentwise 12:46:14 ... we might consider merging them into one document in order to avoid any update inconsistencies 12:47:15 ... the ontology would then become a normative document 12:48:14 q+ 12:48:36 ... I think it's probably reasonable to define the ontology as our normative basis (rather than xml schema) 12:49:02 ... we also have to decide on a name/versioning approach 12:49:54 james: what's the best approach to propose properties/concepts to be added to odrl? 12:50:21 renato: we should start using the mailing list more often 12:51:13 james: e.g. it would be nice to have a top level link to the target rather than referring to it in each permission/prohibition seperately 12:51:21 q+ 12:51:25 q+ to say that sounds like an issue 12:51:34 ack j 12:51:40 q+ to say we should use issue tracking 12:52:02 q- 12:52:09 benws: james, you might should root that in a uc 12:52:27 q+ 12:52:28 q+ 12:52:34 ack benws 12:52:39 q+ 12:52:47 ack me 12:52:47 phila, you wanted to say that sounds like an issue 12:53:03 ... we might want to reconsider whether we really want to use an ontology as normative basis for our language 12:53:26 phila: the action tracker is also an issue tracker 12:53:50 issue: The number of times we need to refer to the target 12:53:50 Created ISSUE-1 - The number of times we need to refer to the target. Please complete additional details at . 12:54:09 close issue-1 12:54:10 Closed issue-1. 12:54:26 q 12:54:28 sounds good thanks @phila 12:54:36 -> https://www.w3.org/TR/vocab-duv/ DUB Voc 12:55:28 phila: you can put multiple examples in multiple encodings in the spec 12:55:38 +q 12:55:42 -q 12:55:54 q+ to make a comment about normative encodings 12:56:19 q+ also to echo victor's point about verbosity being an issue or not 12:56:22 ivan: having gone through several groups having the same issues as ben mentioned 12:56:24 http://w3c.github.io/web-annotation/ 12:57:29 q- json/json-ld point already made 12:57:36 q- 12:58:45 ... [explaining how web-annotation group handled that issue -> json(-ld) based] 12:59:14 ack i 12:59:32 I have made the request to generate http://www.w3.org/2016/04/04-poe-minutes.html phila 12:59:34 ack m 12:59:57 mmcrober: the current ontology document is pretty RDF skewed 13:00:11 q- 13:00:24 q+ 13:01:17 zakim, close queue 13:01:17 ok, phila, the speaker queue is closed 13:01:21 ... I think we could beef up the ontology document pretty straight forward once we have the underlying links/connections to the other specs 13:01:58 ivan: the real description of the model is only done once in the json-ld spec 13:02:40 ... we do not repeat the human prose 13:03:48 topic: F2F meeting 13:03:49 https://www.w3.org/2016/poe/wiki/Attending_F2F1 13:04:08 renato: if you know that you'll be able to attend the f2f meeting, please add your name 13:04:40 In the next call, I would like to see dicussed the need of a test bed / compliance document (or section within existing documents). 13:04:44 will post in the list 13:04:45 ciao! 13:04:56 thanks. 13:05:02 Thanks everyone, bye. 13:05:03 RRSAgent, draft minutes 13:05:03 I have made the request to generate http://www.w3.org/2016/04/04-poe-minutes.html phila 13:05:05 bye 13:05:52 jo has left #poe 13:47:24 phila has joined #poe 13:59:46 zakim, bye 13:59:46 leaving. As of this point the attendees have been simonstey, james, phila, renato, jo, victor, ivan, paulj, mmcrober, michaels, magyarblip, nandana, benws, smyles 13:59:46 Zakim has left #poe 13:59:51 RRSAgent, bye 13:59:51 I see 3 open action items saved in http://www.w3.org/2016/04/04-poe-actions.rdf : 13:59:51 ACTION: Mo to provide use case from research and education domain [1] 13:59:51 recorded in http://www.w3.org/2016/04/04-poe-irc#T12-19-05 13:59:51 ACTION: Renato to go to the ODRL CG to ask for use cases [2] 13:59:51 recorded in http://www.w3.org/2016/04/04-poe-irc#T12-27-43 13:59:51 ACTION: phila to gather use cases from BigDataEurope project [3] 13:59:51 recorded in http://www.w3.org/2016/04/04-poe-irc#T12-28-00