12:09:04 RRSAgent has joined #poe 12:09:04 logging to http://www.w3.org/2016/10/17-poe-irc 12:09:06 RRSAgent, make logs public 12:09:06 Zakim has joined #poe 12:09:08 Zakim, this will be 12:09:08 I don't understand 'this will be', trackbot 12:09:09 Meeting: Permissions and Obligations Expression Working Group Teleconference 12:09:09 Date: 17 October 2016 12:09:19 present+ victor 12:09:19 scribe: Brian 12:09:23 scribeNick: Brian_Ulicny 12:09:46 Resolution: Accept last week's minutes https://www.w3.org/2016/10/10-poe-minutes 12:10:14 regrets+ Renato, Sabrina 12:10:21 Simon has gone through all the requirements based on the TPAC. 12:10:50 present+ Ben, Brian, Caroline, Michael, Phil, Simon, Victor 12:11:00 RRSAgent, make logs public 12:11:02 benws: "the list of requirements on the sheet were the ones that had been accepted" 12:11:06 RRSAgent, draft minutes 12:11:06 I have made the request to generate http://www.w3.org/2016/10/17-poe-minutes.html phila 12:11:35 q? 12:11:37 smyles has joined #poe 12:11:39 https://www.w3.org/2016/poe/wiki/Requirements 12:11:44 chair: Ben 12:11:54 q+ 12:12:00 Simon asks the group before the next call to go through the wiki requirements and check whether Simon has correctly captured the status of the requirements. 12:12:03 present+ Serena 12:12:11 ok, so we are supposed to read this again and provide feedback. 12:12:24 present+ smyles 12:12:25 present+ 12:13:18 Simon directs attention especially to the blue colored requirements. 12:13:33 q+ 12:13:39 ack m 12:13:47 So group is enjoined to please look at the use case doc and requirements. 12:14:07 James has joined #poe 12:14:18 present + 12:14:40 +q 12:14:46 present+ 12:14:52 Michael mentions that the contributor of the use case should make sure that the use cases and requirements line up. 12:15:13 Michael "especially the ones marked agreed without discussion" 12:15:18 q? 12:15:28 benws: "how could they be agreed without discussion?" 12:15:55 zakim, who's here? 12:15:55 Present: victor, Ben, Brian, Caroline, Michael, Phil, Simon, Serena, smyles, simonstey 12:15:57 On IRC I see James, smyles, Zakim, RRSAgent, CarolineB, benws, Brian_Ulicny, victor, michaelS, phila, Serena, simonstey, trackbot 12:16:23 ack me 12:16:25 michael: "they were assumed to be agreed based on call to discuss" 12:16:35 q- 12:16:41 Phil: "am I supposed to be looking at wiki or editor's draft?" 12:16:50 q 12:16:54 q- 12:17:00 Simon: "look at wiki" 12:17:31 benws: "agreed that wiki is canonical version" 12:17:58 "for now ...2 12:18:39 phil: do we need to assign action items? Or agree that after a certain date, everything will be transferred from wiki to editor's draft. 12:18:52 "we need to concentrate the mind" 12:19:45 simon: "there's only one requirement left that has 'agreed without discussion'" 12:20:20 q+ 12:20:24 has to do with notes and formal semantics 12:20:30 q? 12:20:42 michael: "on lowest part of page, we have a 'needs consideration'" 12:20:53 "three have undefined status -- only proposed" 12:21:09 "so are they still under consideration" 12:21:34 Simon: "no, I forgot to change status. Discussed on 23d. Will change" 12:21:37 q? 12:21:40 q- 12:21:48 q- 12:22:09 benws: "let's move on to tech discussion - constraints on constraints" 12:22:15 "three possibilities" 12:22:25 "let's take use case of embargo" 12:22:45 "one suggestion: create an emargo" 12:22:53 q+ 12:23:14 q+ 12:23:16 "another solution (ivan): create two kinds of has constraint property -- one like we already have, another a qualified containt" 12:23:30 "third option: chain constraints together" 12:23:39 q? 12:23:45 "any other options?" 12:24:08 victor: "sent an example earlier this am as Sparql query" 12:24:23 http://cosasbuenas.es/static/ComplexrestrictionswithSPARQL.pdf 12:24:39 victor posts suggestion 12:25:03 victor: "requires sparql endpoint" 12:25:04 which is actually SHACL 12:25:09 "using SPIN" 12:25:31 "example is self-explanatory" 12:25:56 benws: "isn't this an example of the first use case - creation of a complex object" 12:26:08 q+ to say that any one of those three objections on their own out this solution 12:26:09 victor: "Yes that's right" 12:26:18 q? 12:26:35 ack m 12:26:59 michael: "i could only join meeting by audio in lisbon" 12:27:08 "can't understand model behind these examples" 12:27:22 "would be great help for everyone on the call" 12:27:33 benws: "I will publish some example" 12:27:54 "existing constraint model allows contraint only on one predicate or property" 12:28:15 "let's say there's an embargo on extract from football match" 12:28:31 "need to know end of event time and offset interval" 12:28:54 "our existing constraint model can only handle one parameter" 12:29:35 benws: "the first model is where object of predicate is a complex item -- e.g. an embargo object" 12:30:48 "second option allows two types of constraint: one standard, the second is qualified constraint qualified by external object" 12:31:02 "inject the additional constraints into the external object" 12:31:23 "third option: multiple constraints chained together" 12:31:26 q? 12:31:37 ack s 12:31:43 simon: "have a lot to say" 12:32:10 "before we introduce fancy constraints, we need to understand what we want ODRL to be/allow" 12:32:18 "do we want to do constraint checking?" 12:32:28 "do we want to verify that constraints hold?" 12:33:03 simon: are we just concerned with expressiveness? 12:33:45 http://w3c.github.io/data-shapes/shacl/ 12:34:01 "SHACL working group output could be used to express constraints" 12:34:37 "if we go with chaining, which looks attractive,...there are problems" 12:34:44 "looping, for example" 12:34:59 q+ 12:35:06 "i really want to discourage going down chaining route" 12:35:29 phil: "whichever option is chosen, need to build it" 12:35:55 "someone should try to implement this stuff -- W3C suggests that you need to do this stuff" 12:36:10 benws: "I am writing code around this" 12:36:34 ack me 12:36:34 phila, you wanted to say that any one of those three objections on their own out this solution 12:36:41 benws: "can simon provide some concrete examples of dangers of chaining?" 12:36:47 simon: "yes" 12:37:30 phil: "problems listed in the PDF show why this solution is not the right one" 12:37:46 ack sm 12:38:01 sm: "plea for non-complex constraints" 12:38:25 "video editors have these constraints all the time" 12:39:13 "often an embargo is turned from relative time to concrete time: embargo will definitely be over by x o'clock" 12:39:31 +q 12:39:35 benws: "embargoes are not the only complex constraint" 12:39:44 "payments are another example" 12:39:55 q? 12:40:29 simon: "regarding renato's chaining example, not sure if example is complex enough" 12:41:02 odrl:constraint [ a odrl:Constraint ; odrl:operator odrl:eq ; odrl:event ; odrl:constraint ; ]. a odrl:Constraint ; odrl:operator odrl:eq ; odrl:dateTime "P30M"^^xsd:duration . 12:41:02 "permission is granted during an event" 12:41:57 "point is that I've encountered a situation where there is no property that can be used" 12:42:18 "the property is not adequate to address the use case" 12:42:28 q? 12:42:41 q- 12:42:51 benws: "let's take this discussion to mailing list and reconvene next week" 12:42:58 "will provide concrete examples" 12:43:11 +q 12:43:47 https://github.com/w3c/poe/issues/45 12:44:00 simon: "raised an issue on github wrt relations" 12:44:19 "does it make sense to have extended relations for permissions?" 12:44:30 https://w3c.github.io/poe/model/#extended-relations 12:45:22 "spec says that if you and permissions then you have to do all of them. this is wrong" 12:45:35 "you have to do all ANDed duties, not permission" 12:45:41 "permissions" 12:45:55 "what does it mean to tie permissions with an OR?" 12:46:25 q? 12:46:37 simon: "either you have to satisfy this constraint or that constraint" 12:46:39 q+ 12:46:57 "specification is wrong. Uses 'may not', which is not defined." 12:47:11 q- 12:47:24 ack s 12:47:48 serena: "I agree with simon. Connectors for duties and constraints, not relations" 12:48:16 PROPOSED: That the extended relations (AND, OR, XOR) will only apply to Duties and Constraints, not Permissions and Prohibitions 12:48:41 +1 12:48:48 +1 12:48:48 +1 12:49:04 not sure 12:49:50 +1 12:50:24 present+ James 12:50:30 victor: +1 12:50:35 RESOLUTION: That the extended relations (AND, OR, XOR) will only apply to Duties and Constraints, not Permissions and Prohibitions 12:50:36 +1 12:50:41 +1 12:50:54 benws: "will quickly run through open actions" 12:51:01 https://www.w3.org/2016/poe/track/actions/open 12:51:28 action-25? 12:51:28 action-25 -- Víctor Rodríguez-Doncel to Provide an example of how good relations vocab support 'unit-of-count' -- due 2016-09-29 -- OPEN 12:51:28 https://www.w3.org/2016/poe/track/actions/25 12:51:34 "victor, you were going to provide an example of unit-of-count" 12:51:42 action-30? 12:51:42 action-30 -- Stuart Myles to Can we only have a json-ld serialisation? will it impact righstml? -- due 2016-09-30 -- OPEN 12:51:42 https://www.w3.org/2016/poe/track/actions/30 12:52:52 "simon, yours will always be open" 12:52:56 "issues raised" 12:53:03 q+ 12:53:11 ack me 12:53:44 phila: "do we need to follow issues in github as well?" 12:54:02 "we just need to make sure that we track ALL the issues" 12:54:18 simon: "is there integration with IRC and the github tracker?" 12:54:25 phila: "No" 12:54:29 -> https://github.com/w3c/poe/issues GitHub Tracker 12:54:45 15 issues on github tracker currently 12:55:00 phila: "Most raised by renator" 12:55:06 *renato 12:55:53 issue-1 12:55:53 issue-1 -- The number of times we need to refer to the target -- closed 12:55:53 https://www.w3.org/2016/poe/track/issues/1 12:56:05 simon: "easier to look up issues in IRC via trackbot" 12:56:07 I can solve mine inmediatly Action 25. the example that is requested can be seen in slide 18 of http://tutorials.oeg-upm.net/rightslinkeddata/session4b.pdf 12:56:57 Topic: AOB 12:57:05 benws: "can bring this up next week." 12:57:40 victor: "next f2f: when, where, who (ben is necessary)" 12:57:43 phila: I think Renato might well be there 12:58:03 RRSAgent, draft minutes 12:58:03 I have made the request to generate http://www.w3.org/2016/10/17-poe-minutes.html phila 12:58:04 phila: "suggest a date, we'll take it from there" 12:58:18 Serena has left #poe 12:58:36 s/phila/benws/ 12:58:41 RRSAgent, draft minutes 12:58:41 I have made the request to generate http://www.w3.org/2016/10/17-poe-minutes.html phila 15:22:32 Zakim has left #poe 16:38:57 benws has joined #poe 16:42:45 benws2 has joined #poe 18:19:40 benws has joined #poe 18:23:26 benws2 has joined #poe