12:09:42 RRSAgent has joined #poe 12:09:42 logging to http://www.w3.org/2017/04/03-poe-irc 12:09:44 RRSAgent, make logs public 12:09:44 Zakim has joined #poe 12:09:46 Zakim, this will be 12:09:46 I don't understand 'this will be', trackbot 12:09:47 Meeting: Permissions and Obligations Expression Working Group Teleconference 12:09:47 Date: 03 April 2017 12:10:09 regrets+ Victor, Brian, Serena, Ivan 12:10:40 agenda: https://www.w3.org/2016/poe/wiki/Meetings:Telecon20170403 12:10:49 Chair: Renato 12:11:01 RRSAgent, make logs public 12:11:05 present+ 12:28:30 renato has joined #poe 12:28:33 michaelS has joined #poe 12:30:30 present+ 12:31:13 present+ 12:31:47 smyles has joined #poe 12:33:54 Sabrina has joined #poe 12:34:01 present+ sabrina 12:34:43 benws_ has joined #poe 12:34:55 I will scribe 12:34:55 present+ 12:35:29 scribe: Sabrina 12:35:32 scribeNick: Sabrina 12:35:33 https://www.w3.org/2017/03/27-poe-minutes 12:35:41 Topic: Last week's minutes 12:35:44 present+ 12:35:50 [Nothing heard] 12:35:51 Any comments on the last minutes, otherwise I take silence as approval 12:35:59 Accepted 12:36:00 https://www.w3.org/2016/poe/wiki/Deliverables 12:36:03 RESOLUTION: Last week's minutes accepted 12:36:10 Topic: Wide Review 12:36:15 Update on the wide and horizontal reviews 12:36:22 q+ 12:36:47 Renato: Just waiting for feedback. Ben did you speak to Brian about the internationalisation 12:36:52 ack m 12:37:12 Michael: Would it help to indicate who has replied. I have done this. 12:37:26 https://github.com/w3c/poe/issues/118 12:37:46 q- 12:37:54 Renato: Probably a good idea. I have done this the other way around from the issue. Good idea to populate both lists 12:38:08 renato: Back tht einternationalisation 12:38:29 benws_: I haven't had a chance yet. I will followup. 12:38:41 ivan has joined #poe 12:38:42 renato: Nothing else to report 12:39:14 Topic: Testing 12:39:15 Topic: Define and setup testing 12:39:28 s/Topic: Testing// 12:40:00 renato: After we get the feedback we need to setup things in order to get to CR e.g. leader for testing 12:40:17 phila: We haven't talked about it in a while 12:41:01 ... we need independent implementation that work the same way - one way is to setup a test suite - including inputs and outputs 12:41:16 ... This can be another note or maybe even a github repo 12:41:43 q+ 12:41:44 q+ 12:41:51 ... A set of machine readable policies and demonstrate that there is more that one implementation - given the same input we get the same output 12:42:12 Renato: How would that look for us given we don't do any processing 12:42:35 benws_: We are using a validator for the terms that we use... not the whole vocabulary 12:43:10 phila: Each individual piece of software does not need to cover everything 12:43:18 benws_: Do we need to make this public 12:43:41 phila: No it doesn't need to be public, you just need to give us the information 12:45:11 smyles: We had an ODRL engine with 3 things for testing - 1) the policy, 2) the result (yes, no or maybe) and 3) the context (who is the assignee, what country or city are they from, what action are they trying to perform) 12:45:20 ... This was enough for us 12:45:48 benws_: It sounds like you were testing a processing model. However we need to syntactically validate policies. 12:45:48 "This will require the ODRL Policy to be interpreted with the additional information identified by the URI." 12:45:57 ... is that correct Phil 12:46:20 simonstey has joined #poe 12:46:55 phila: Just did a search for interrupted - points to a concrete example - how one choses to use this information is out of scope for the working group 12:47:24 ... this is perfectly ok, however the uses need to be consistent and we must show they are consistent with one another 12:47:34 The processing model for Constraint Relations includes: 12:47:34 benws_: Sounds like a processing model 12:47:53 renato: Points to the 9 steps listed in the processing model 12:47:54 https://w3c.github.io/poe/model/#constraint-relations 12:48:15 s/interrupted/interpret/ 12:49:02 renato: Put up a test e.g. to say expressions need to be atomic 12:49:23 ... There are a few points were we can pull out a processing model and turn them into a text case 12:49:36 present+ 12:50:08 q+ 12:50:09 benws_: We can check is this a valid piece of ODRL and does it allow me to take this action 12:50:12 ack b 12:50:19 ... the 2nd is more enforcement 12:50:25 q- 12:50:32 ... I guess we need to avoid this 12:50:44 q+ 12:50:51 phila: Apart from being valid RDF, what is valid ORDL 12:51:03 benws_: Enforcement of the information model 12:51:16 phila: Yes they are different. 12:52:19 ShEx or SHACL 12:52:24 ... Vaidation could be done in various ways 1) Shacl and 2) ShEx 12:52:52 The group proposes to the director what the exit criteria should be 12:53:21 Phil: You could suggest multiple instances (at least twice) of all of the terms 12:53:46 ... For core terms they should of course be used much more 12:54:05 ... Plus examples of real live ODRL policies 12:54:57 ... It would also be good to indicate the type of uses we've heard about that would be good aswell (e..g what Ben and Stewart are doing) 12:55:16 ... Details of real world valid use 12:55:26 benws_: What needs to be in the tests 12:55:39 phila: All the terms and all the constraints 12:55:56 ... build some kind of software and test against it 12:56:20 renato: ... build the tests including invalid tests 12:56:28 phila: yes 12:56:37 q? 12:56:52 renato: does the test suite need to be complete before the F2F 12:57:06 ... How much needs to be complete by May 12:57:24 phila: It doesn't need to be complete, it should be started 12:57:40 ... with the experience in this group it should not take too long 12:57:56 ... plus you might find that you need to change it later when you are in CR 12:58:16 smyles: I would like to remind the group that ODRL is not just RDF 12:58:19 s/change/add to it/ 12:58:39 ... We will also need to do XML validation 12:59:13 +1 to smyles 12:59:27 ... It would be useful to evaluate engines that process ODRL and when 2 different engines process ODRL they come to the same answer 12:59:40 q+ 12:59:48 ack smyles 12:59:51 ... this would be ambitious by May but ultimately very helpful 13:00:05 renato: It depends on how complete it needs to be 13:00:26 ... however this would give the director confidence 13:00:47 ... we need to ask the group if someone would like to lead this piece of work 13:01:25 ... so that we have some test cases for the F2F meeting in May 13:01:49 smyles: Is the challenge organising the work or doing the testing? 13:02:17 renato: This is really about managing the process (getting the test cases ready to go) 13:03:12 phila: I could have a go... I'm not sure if I can do the whole thing but I could certainly write some examples 13:03:24 ... Sabrina are building a parser as part of SPECIAL 13:04:02 ... We are modelling at the moment, so if depends on how that goes 13:04:09 q- 13:04:17 renato: Thanks Phil for kicking that off 13:04:32 ... any other questions on the testing regime? 13:04:35 Nope 13:04:44 Topic: Notes 13:04:57 Any update Simon on the formal semantics 13:05:13 will have a call in the next weeks 13:05:39 Sabrina: We have exchanged some e-mails about formal semantics. We'll kick off next week when Ivan is back from WWW in Perth 13:05:59 renato: Ben any update on the best practices 13:06:08 https://www.w3.org/2016/poe/track/actions/open 13:06:08 Topic: Open Actions 13:06:26 renato: Ben and Phil and update on your actions 13:06:43 q+ 13:06:51 phila: No update on the accessibility usecase 13:07:18 smyles: Question on versioning 13:07:19 https://www.w3.org/2016/poe/wiki/Meetings:London2017 13:07:30 Topic: F2F London 13:07:43 benws_: I can confirm the address is correct 13:08:38 renato: I have prepared a draft agenda... wide review, horizontal review etc... 13:08:48 q+ 13:08:52 benws_: Renato will you attend in person? 13:09:08 renato: I'm not sure at this point 13:09:15 https://github.com/w3c/poe/issues 13:09:21 Topic: Issues on the github 13:09:51 michaelS: There are currently 18 issues, however it is not clear how these issues can be resolved 13:10:10 18 open issues 13:10:19 benws2 has joined #poe 13:10:27 renato: We should talk about some of these next week - especially the ones that say need working group decision 13:10:37 ... we could maybe tackle 2 per call 13:10:43 https://github.com/w3c/poe/issues/22 13:10:45 ... example is number 22 13:10:54 ack michaelS 13:11:05 ... proposal from Simon to remove the inherit relation 13:11:25 ... this is probably something that the editors can not decide as it is really a group decision 13:11:33 benws3 has joined #poe 13:11:43 phila: All of these need to be closed before seeking CR transition 13:12:40 ... one relates to the usecase document. Do we plan to do more work on the usecase document? If so we can do this and republish the usecase document. If not we should close it and say why. 13:12:59 renato: We hope to close as many as possible before the F2F 13:13:01 I'll address the ucr issue until next week 13:13:20 ... it would be good to at least discuss them before the F2F 13:13:24 I encourage everyone to read through the spec and raise issues themselves 13:13:44 ... I would like to propose a couple of github issues per week for discussion on the weekly call 13:14:01 ... will start with the ones that say need working group decision 13:14:13 Topic: AOB 13:15:04 IPTC 13:15:05 Phil: I have a talk at the IPTC, will anyone else be there? 13:15:48 ... I will endeavour to prepare the presentation in advance and get your feedback 13:16:12 simonstey: I have been briefing the IPTC group for sometime on ODRL and now POE 13:16:49 s/simonstey/smyles 13:16:55 michaelS: I think it would help to clarify what the W3C review requirements are, the IPTC people will not be familiar with these 13:17:09 RRSAgent, draft minutes v2 13:17:09 I have made the request to generate http://www.w3.org/2017/04/03-poe-minutes.html phila 13:17:45 https://www.w3.org/2008/04/scribe.html 13:18:28 RRSAgent, draft minutes v2 13:18:28 I have made the request to generate http://www.w3.org/2017/04/03-poe-minutes.html phila 14:24:28 benws3 has joined #poe 14:28:35 benws4 has joined #poe 15:19:41 Zakim has left #poe 17:10:42 benws4 has joined #poe 17:14:20 benws5 has joined #poe 19:07:04 benws5 has joined #poe 19:11:20 benws6 has joined #poe 20:03:48 benws6 has joined #poe