11:59:38 RRSAgent has joined #poe 11:59:38 logging to http://www.w3.org/2016/10/10-poe-irc 11:59:40 RRSAgent, make logs public 11:59:40 Zakim has joined #poe 11:59:42 Zakim, this will be 11:59:42 I don't understand 'this will be', trackbot 11:59:43 Meeting: Permissions and Obligations Expression Working Group Teleconference 11:59:44 Date: 10 October 2016 11:59:51 RRSAgent, make logs public 11:59:59 present+ renato 12:00:07 chair: renato 12:00:17 Present+ ivan 12:00:29 Agenda: https://www.w3.org/2016/poe/wiki/Meetings:Telecon20161010 12:00:35 CarolineB has joined #poe 12:01:12 victor has joined #poe 12:01:12 Brian_Ulicny has joined #poe 12:01:15 present+ James 12:01:19 present+ victor 12:01:20 present+ 12:01:27 Call for a Scribe? 12:01:40 present+ michaelS 12:01:47 Get your name immortalised here: https://www.w3.org/2016/poe/wiki/Meetings 12:02:05 present+ CarolineB 12:02:27 (I would rather not to scribe today. will volunteer in another ocasion as soon as possible) 12:02:37 Noted ;-) 12:03:32 scribe michaelS 12:03:40 scribe: michaelS 12:03:47 scribenick: michaelS 12:03:48 present+ 12:03:55 Sabrina has joined #poe 12:04:10 present+ sabrina 12:04:36 present+ phila 12:04:42 topic: last meeting minutes 12:04:45 RRSAgent, draft minutes 12:04:45 I have made the request to generate http://www.w3.org/2016/10/10-poe-minutes.html phila 12:04:50 https://www.w3.org/2016/10/03-poe-minutes.html 12:05:29 Resolution: the minutes of the last call are accepted 12:05:49 Topic: 2. Use Cases and Requirements 12:06:20 michaelS: No, I haven't 12:06:23 Simon was active on adding references 12:07:28 topic: 3: Technical Discussion 12:07:44 topic: 3.1 Constraints on Constraints 12:08:21 renator: key issue is that we currently have only a single constraint, how to extend this? 12:08:42 s/renator/renato/ 12:09:32 renato: One of the use cases were in Lisbon: a relative constraint like "may be published 30 minutes after the game" 12:09:50 q+ 12:10:15 +1 12:10:16 phila: doesn't seem to me so over-complicated 12:10:17 +1 12:10:23 ... supports to include it. 12:10:23 ack me 12:10:58 q+ 12:11:07 ack i 12:11:41 q+ 12:11:53 ivan: is this about only a time constraint - or a more generic requirement 12:12:29 ... But this could be solve by starting with the time constraint first and then to make it more generic 12:12:35 ack b 12:12:58 ben: thinks this is a general issue, not only about time 12:13:23 ... there are use cases related to payments which are very similiar 12:13:41 ... we need a generic solution 12:13:44 q+ 12:14:09 phila: supported ben's thoughts. 12:14:47 s/phila: supported ben's thoughts.// 12:15:17 q+ 12:15:18 renato: we need also to express relations between constraints - something "constraint A depends on constraint B" 12:16:11 phila: are all relative time use cases about a related event 12:16:35 ... in this case we only need a new "related event" 12:16:35 ac me 12:16:37 ack me 12:17:17 ben: another relative relationship is : payment per account, payment per person 12:18:30 ivan: asked renato to put in IRC his draft of a discussed new solution 12:19:22 renato: has no clear outline, only first ideas 12:20:16 ... we need some thoughts how to do that in the ontology first, then think about encoding 12:20:55 q+ 12:20:56 ... issue: we have to be aware that one thing may occur before the other ... maybe next week. 12:20:59 ack i 12:21:42 ivan: should we reorder the sequence of solving things 12:22:06 q- 12:22:27 renato: ok, we could look at relatives time constraints first 12:22:27 sounds a good approach to try 12:22:38 Seems like a reasonable suggestion to me! 12:24:02 phila: use case "30 minutes after game ended" - what is the right expression to express this logic 12:24:29 ben: maybe the best way to test this examples 12:26:01 renato: constraints on constraints or dependancies across constraints? 12:26:50 renato: let's talk about extended relations 12:27:54 ... to express alternative options, like 'pay' or 'subscribe to a service' 12:28:04 ... what is the model for hat? 12:28:30 q+ 12:29:00 q? 12:29:04 ... does W3C has similar solutions for that? 12:29:06 s/hat?/that?/ 12:29:10 ack i 12:29:38 ivan: cannot recall such a solution. What renato describes is very close to the previous use case 12:30:53 ... - first you have the triples of the statement and then you want to make a statement about one or more of these triples. 12:31:21 ... this is the typical case for using a named graph 12:31:34 q+ 12:31:42 ack b 12:33:06 Brian_Ulicny and ivan discussed options for solving that issue 12:34:47 ivan: thinks what is discussed must be expressed properly in RDF 12:35:09 ben: is this the case for latests suggestions? 12:35:10 Agreed.... This is what we need to look into.... 12:35:17 q+ 12:35:25 ivan: not sure, needs to be checked in detail. 12:35:26 q- 12:35:26 I"m happy to look into this 12:35:31 q 12:35:36 q+ 12:36:02 phila: feels this goes in a very complex direction 12:36:19 ... we might go outside OWL - will users want to do that 12:36:42 q+ 12:37:25 Discussion about the need for a reasoner. 12:38:22 ack i 12:38:24 ack s 12:39:28 q+ 12:39:42 ack i 12:39:43 renato: we need to make a model and include that into the existing one but next we need to fit this into the OWL of the ontology 12:40:45 ivan: we might define a reifiction-like object which might have additional information attached to it 12:41:08 ... we might apply a specific URI to a constraint 12:41:50 ... in a next step we could created a list of URIs/constraints and apply a next level of relationships/dependancies to them 12:42:17 ... we should try that - may there are hidden problems 12:43:04 renato: the additional constraints should be added as additional data - the basic date should always be the same 12:44:28 ... it would be great if some come up with example solutions this week and we could look at them at the next call 12:44:41 I don't mind 12:44:51 ... who volunteers for that`? 12:45:12 sure 12:45:22 Me too 12:45:22 Be good to have more than pair of eyes 12:45:31 *one pair 12:45:43 ivan: voluteers to look at the examples, but will be in China next week 12:45:51 I will look into OWL 12:46:07 I am also not here next week as I will be at ISWC in Japan 12:46:08 renato: will communicate next steps with the volunteers 12:46:20 (please count me in) 12:46:37 q+ 12:46:42 RRSAgent, draft minutes 12:46:42 I have made the request to generate http://www.w3.org/2016/10/10-poe-minutes.html phila 12:46:44 sck b 12:46:47 ack b 12:46:57 https://en.wikipedia.org/wiki/Allen%27s_interval_algebra 12:47:01 s/sck b// 12:47:17 q+ to talk about Allen's algebra 12:47:31 ack me 12:47:31 phila, you wanted to talk about Allen's algebra 12:47:33 Brian_Ulicny: we should investigate the different types of temporal relations 12:48:16 phila: Special Data WG is behind registering such temporal relations 12:48:42 topic: 3.2 Validity of Policy 12:49:18 renato: how to express that a policy is only valid in a stricly defined period - by what means to express that? 12:49:32 q+ 12:49:45 q? 12:51:04 -> http://lov.okfn.org/dataset/lov/terms?q=valid%20from%20(0..1) LOV search for valid from 12:51:20 ben: aren't there already existing time constraint properties? 12:51:40 phila: searched for "valid from" and found many 12:51:44 q+ 12:51:50 q- 12:51:55 ack i 12:52:39 ivan: looks a provenance ontology, has some very specific time related properties - this group did not try to find a generic solution 12:53:00 I think we want "expires" 12:54:37 renato: common wording is "valid from" and valid to" 12:55:00 ... clarified the suggestion of "expires": is the same as "valid to" 12:56:19 victor: how to proceed, by exchanging emails? 12:56:23 renato: yea 12:56:37 Topic: 4 Deliverables List 12:57:12 renato: the group has discussed already what should be put on this list. There is a list of documents in the Charter 12:57:22 https://www.w3.org/2016/09/poe6 12:57:58 renato: went over the items shown in https://www.w3.org/2016/09/poe6 13:00:08 phila: will support finding a solution for item 5, mapping 13:00:12 https://www.w3.org/2016/09/poe8 13:00:35 Topic: 5 WG Timeline 13:00:54 renato: went over the draft at https://www.w3.org/2016/09/poe6 13:02:09 Topic: 6 Action items + issues 13:02:40 q+ 13:03:03 ack i 13:03:06 victor: volunteered to organize the f2f meeting in March - details at the next call 13:03:32 RRSAgent, draft minuytes 13:03:32 I'm logging. I don't understand 'draft minuytes', phila. Try /msg RRSAgent help 13:03:35 RRSAgent, draft minutes 13:03:35 I have made the request to generate http://www.w3.org/2016/10/10-poe-minutes.html phila 13:03:40 ivan: will send out an email about what he discussed above 13:04:05 renato: thanked all participants and closed the call 13:04:12 RRSAgent, draft minutes 13:04:12 I have made the request to generate http://www.w3.org/2016/10/10-poe-minutes.html phila 15:03:31 Zakim has left #poe 16:43:01 benws has joined #poe 16:46:26 benws2 has joined #poe 17:04:15 ivan has joined #poe