13:00:19 RRSAgent has joined #shapes 13:00:19 logging to http://www.w3.org/2016/10/11-shapes-irc 13:00:21 RRSAgent, make logs rdf-data-shapes 13:00:21 Zakim has joined #shapes 13:00:23 Zakim, this will be SHAPES 13:00:23 ok, trackbot 13:00:24 Meeting: RDF Data Shapes Working Group Teleconference 13:00:24 Date: 11 October 2016 13:03:03 marqh has joined #shapes 13:03:40 agenda: https://www.w3.org/2014/data-shapes/wiki/Meetings:Telecon2016.10.11 13:03:47 chair: Arnaud 13:04:44 regrets: pano, simonstey 13:07:15 scribenick: AndyS 13:08:45 topic: Admin 13:08:48 PROPOSED: Approve minutes of the 4 Oct 2016 Telecon: http://www.w3.org/2016/10/04-shapes-minutes.html 13:08:51 +1 13:09:04 +1 13:09:17 RESOLVED: Approve minutes of the 4 Oct 2016 Telecon: http://www.w3.org/2016/10/04-shapes-minutes.html 13:09:21 present+ 13:09:24 present+ 13:09:25 present+ 13:09:25 present+ 13:09:25 present+ 13:09:26 present+ 13:09:36 Labra has joined #shapes 13:10:00 next week - Eric to chair. 13:10:25 topic: Public Comments 13:10:48 arnaud: karen reformatted the wiki page 13:10:56 https://www.w3.org/2014/data-shapes/wiki/Comments/September2016/ 13:11:19 karen: covers Aug and Sept. 13:12:06 ... adding a list of terms that need defining - will create a single issue for them 13:12:45 arnaud: better to be formal in processing comments. 13:13:05 ... thank you Karen for doing this work. 13:13:56 ... we do not need to satisfy each comment - we need to respond to all comments. 13:14:19 ... for answer - proceed with discussion and spec edits. 13:14:50 ... try to get a formal response from PFPS. 13:15:08 topic: Disposal of Raised Issues 13:15:27 ISSUE-186, ISSUE-187, ISSUE-188, ISSUE-189 13:15:47 PROPOSED: Open ISSUE-186, ISSUE-187, ISSUE-188, ISSUE-189 13:15:51 PROPOSED: Open ISSUE-186, ISSUE-187, ISSUE-188, ISSUE-189 13:16:09 holger: on 189 - seeking clarification 13:16:49 TallTed has joined #shapes 13:17:49 karen: what's an empty graph in this situation? 13:17:52 q+ 13:18:50 ack Dimitris 13:18:55 present+ 13:19:30 dimitris: suggest a wrapper with a list of results and the result can be a zero length list. 13:20:38 arnaud: at the moment, seeing if there is an issue to clarify 13:20:40 +1 open issues 186-189 13:22:20 +1 to open issues 13:23:22 +1 13:23:40 arnaud: need to bring out the knowledge in the implementations 13:23:57 q+ 13:24:14 ack hknublau 13:24:58 holger: maybe scheduling a face-to-face where WG contributes. 13:25:49 arnaud: maybe several days in a row of several hours each day 13:26:01 +1 13:26:14 RESOLVED: Open ISSUE-186, ISSUE-187, ISSUE-188, ISSUE-189 13:26:34 topic: vF2F to dispose of issues and comments 13:26:38 q+ 13:26:55 +1 for a 3 days / 4 hours per day. 13:27:13 ack marqh 13:28:38 marqh: would like to contribute to several ... like to structure the sessions so people with some areas not all camn see where to schedule time. e.g. schedule groups of issues. 13:28:58 arnaud: yes - an agenda would be produced. 13:29:47 ... we can prioritise issues 13:30:19 ... also - async means like the wiki to prepare content 13:31:14 q+ 13:31:41 STRAWPOLL: would you participate in 2 or 3 day virtual f2f - of a 3h or so per day? 13:31:45 ack AndyS 13:31:47 +1 13:32:46 +1 where I have a useful contribution 13:33:21 +1 13:33:42 +1 13:33:51 +1 13:33:51 +1 13:33:54 +1 13:34:08 +1 13:34:25 q+ to ask about upcoming conferences 13:34:32 ack ericP 13:34:32 ericP, you wanted to ask about upcoming conferences 13:35:56 topic: Filter and focus nodes 13:37:30 dimitris: meeting to happen with karen - report next week. 13:37:51 topic: ISSUE-178 13:38:03 https://www.w3.org/2014/data-shapes/track/issues/178 13:39:01 holger: reminder - possibility for a specific constraint, add a message for validation reports. 13:39:10 ... currently not legal. 13:39:25 ... proposal is to allow this in constraints 13:39:27 q+ 13:39:40 ack kcoyle 13:39:54 http://w3c.github.io/data-shapes/shacl/#results-message 13:40:35 q+ 13:40:46 ack hknublau 13:40:59 karen: seems to be different between SHACL core and SHACL full. 13:41:15 holger: intent is that can apply to both. 13:41:47 karen: my Q is about machine generated messages 13:45:20 q+ 13:47:23 ack Dimitris 13:50:42 dimitris: control of the message the engine uses to report 13:51:59 q+ to address pushback from shex 13:52:06 ack ericP 13:52:06 ericP, you wanted to address pushback from shex 13:54:06 q+ 13:54:38 ack kcoyle 13:55:43 karen: expect sh:message to be defined on a constraint. 13:56:16 ... (i.e. sec 4 - scribe) 13:56:55 arnaud: this would be done as part of the impl of resolution 13:57:07 PROPOSED: Close ISSUE-178, accepting the proposal to allow sh:message to be used in core on a constraint to override the implementation default message 13:57:16 +1 13:57:23 +1 13:57:26 +1 13:57:30 +1 13:57:32 +1 13:57:47 0 13:57:53 0 13:58:02 +1 13:58:02 +1 13:58:10 RESOLVED: Close ISSUE-178, accepting the proposal to allow sh:message to be used in core on a constraint to override the implementation default message 13:58:26 scribenick: ericP 13:58:47 topic: ISSUE-182 13:58:53 issue-182 13:58:54 issue-182 -- Clarifications needed to section 3.0 -- open 13:58:54 http://www.w3.org/2014/data-shapes/track/issues/182 13:59:24 karen: having a formal syntax would be helpful 13:59:34 ... it says "results MAY be returned" 13:59:53 ... in the library world, we talk about "mandatory" amd "mandatory if applicable" 14:00:58 ... does MAY mean "MAY if there are values"? and must ALL values be returned? 14:01:12 ... could an impl decide that it's only going to return the first two? 14:01:42 [re 3.4.1.3 and 3.4.1.8] 14:02:02 hknublau: we discussed that already. sh:value isn't used in the shapes graph so it can't be coded in the constraint 14:02:46 it is now 3.4.3 http://w3c.github.io/data-shapes/shacl/#results-value 14:02:47 kcoyle: it's not coming from the shapes graph but a value has been evaluated. 14:03:09 ... if one or more values is evaluated, it appears optional whether to return that in the report. 14:03:22 ... if there is more than one value, is it mandatory to return all of them? 14:04:17 hknublau: if a value for sh:value is produced, the constraint components explicity mention it. 14:04:20 we can say it is the value node or the binding of sh:value in SHACL Full 14:04:26 ... e.g. 4.9.1 (sh:closed) 14:04:52 ... [reads definition which mentions sh:value] 14:07:25 q+ 14:07:53 q- 14:08:12 q+ 14:08:23 ack Dimitris 14:08:34 Arnaud: i think is the sort of thing that pfps has issues with as well 14:09:07 Dimitris: so we need to describe what is required and what is returned? 14:12:36 [this is all editorial. leaving it to the editors and Karen] 14:12:45 topic: ISSUE-140 14:12:47 q+ 14:12:51 issue-140 14:12:51 issue-140 -- SHACL needs to support validation of individual nodes -- open 14:12:51 http://www.w3.org/2014/data-shapes/track/issues/140 14:13:11 current definition is here: http://w3c.github.io/data-shapes/shacl/#validation 14:13:26 https://lists.w3.org/Archives/Public/public-data-shapes-wg/2016Oct/0030.html 14:13:42 hknublau: we discussed this two weeks ago. 14:14:06 ... in the email that I linked above, i sought clarification 14:14:16 https://www.w3.org/2016/09/27-shapes-minutes.html#item08 14:14:20 ... passing this back to ericP and TallTed 14:14:42 q+ 14:14:47 q+ 14:15:23 ack hknublau 14:15:29 ack Dimitris 14:16:00 Dimitris: [reads from the spec] 14:16:13 ... i think this addresses ericP's concearns 14:16:17 http://w3c.github.io/data-shapes/shacl/#validation 14:17:02 ack ericP 14:17:12 https://shexspec.github.io/spec/#nodeKind 14:20:13 Dimitris: are we missing something or do we need to present this better? 14:21:18 ericP: the latter, but i think it needs a discearning eye to get it 14:21:48 q+ 14:21:59 ack kcoyle 14:22:17 kcoyle: i would like ericP to post his version so the group can see it. 14:24:11 topic: ISSUE-131 14:24:16 issue-131 14:24:16 issue-131 -- The definition of sh:hasShape has errors and holes -- open 14:24:16 http://www.w3.org/2014/data-shapes/track/issues/131 14:25:47 as far as I can tell the last time it was discussed was: https://www.w3.org/2016/06/09-shapes-minutes.html#item02 14:29:59 on ISSUE-140 -- what happened to the image showing the narrowing from datagraph -> targets -> filters -> focusnodes ? 14:29:59 I think that shows how to make the validation apply to a single-focusnode-within-a-graph, just by defining target as ex:node 14:30:23 trackbot, end meeting 14:30:23 Zakim, list attendees 14:30:23 As of this point the attendees have been Arnaud, hknublau, marqh, Dimitris, AndyS, kcoyle, TallTed, ericP 14:30:28 hknublau: I will propose closure for issue-131 with links 14:30:31 RRSAgent, please draft minutes 14:30:31 I have made the request to generate http://www.w3.org/2016/10/11-shapes-minutes.html trackbot 14:30:32 RRSAgent, bye 14:30:32 I see no action items