17:58:09 RRSAgent has joined #shapes 17:58:09 logging to http://www.w3.org/2016/03/24-shapes-irc 17:58:11 RRSAgent, make logs rdf-data-shapes 17:58:11 Zakim has joined #shapes 17:58:13 Zakim, this will be SHAPES 17:58:13 I do not see a conference matching that name scheduled within the next hour, trackbot 17:58:14 Meeting: RDF Data Shapes Working Group Teleconference 17:58:14 Date: 24 March 2016 17:58:27 pfps has joined #shapes 17:58:43 present+ 18:00:36 Dimitris has joined #shapes 18:01:42 hknublau has joined #shapes 18:02:31 agenda: https://www.w3.org/2014/data-shapes/wiki/Meetings:Telecon2016.03.24 18:02:49 chair: Arnaud regrets: labra, ericP 18:03:31 present+ 18:04:19 kcoyle has joined #shapes 18:04:38 regrets: labra, ericP, hsolbrig 18:04:54 present+ 18:05:38 jamsden has joined #shapes 18:06:34 present+ 18:06:41 scribenick: TallTed topic: Admin 18:07:44 PROPOSED: Approve minutes of the 17 March 2016 Telecon: http://www.w3.org/2016/03/17-shapes-minutes.html 18:08:04 RESOLVED: Approve minutes of the 17 March 2016 Telecon: http://www.w3.org/2016/03/17-shapes-minutes.html 18:09:20 TOPIC: F2F? 18:09:23 q+ 18:09:46 ack pfps 18:10:36 pfps: I don't think face- nor meeting-time is the bottleneck at the moment 18:11:08 ... gaps in the design/spec need to be filled 18:12:11 q+ 18:12:18 ... which needs external inputs and/or increased attention from some quarters 18:12:23 ack hknublau 18:15:31 hknublau: what are the dramatic holes at the moment? 18:16:03 pfps: prebinding and hasShapes 18:17:09 Arnaud: there's been recent email traffic on prebinding 18:17:43 hknublau: hasShape has not been updated because we're still working on recursion, which resolution has significant impact there 18:19:42 simonstey has joined #shapes 18:20:57 q+ 18:21:34 ack TallTed 18:25:11 present+ simonstey 18:25:47 [ back-and-forth about F2F impact/utility ] 18:27:41 hknublau: what is current timeline? 18:28:29 Arnaud: we are chartered until June 2017, so there should be plenty of time, even though we have not kept up with original forecast schedule 18:30:50 q+ 18:30:54 ack pfps 18:32:19 q+ 18:32:41 ack simonstey 18:33:24 pfps: another implementation, especially one that includes the extension mechanism, would help a lot in boosting confidence 18:34:32 q+ 18:35:23 q- 18:35:24 simonstey: I'm doing a fair amount of work with hknublau's draft API. do we need to re-implement that to be counted as multiple implmentations? 18:35:51 I am planning to implement the spec 18:37:12 TallTed: I do expect that OpenLink will implement SHACL including extension mechanism. timing is indeterminate, but we do try to do such within CR->PR window. topic: Disposal of Raised Issues 18:37:58 PROPOSED: Open ISSUE-138 Property constraints as lists, ISSUE-139 Universal applicability, ISSUE-140 Individual validation, ISSUE-141 Mixed ranges 18:38:10 +1 18:38:14 +1 18:38:16 +1 18:38:16 +1 18:38:37 +1 18:38:37 I think that it would be very much better if OpenLink did an implementation before CR. This gives the WG much needed confidence that the design is workable. 18:38:39 +1 18:38:56 RESOLVED: Open ISSUE-138 Property constraints as lists, ISSUE-139 Universal applicability, ISSUE-140 Individual validation, ISSUE-141 Mixed ranges 18:39:05 It would also be very helpful if OpenLink can contribute to the design of hasShape and pre-binding. 18:40:05 topic: ISSUE-128: rdfs:range 18:40:09 ISSUE-128? 18:40:09 ISSUE-128 -- sh:defaultValueType is rdfs:range -- open 18:40:09 http://www.w3.org/2014/data-shapes/track/issues/128 18:40:15 PROPOSED: Close ISSUE-128, without action. 18:40:46 hknublau's email -- https://lists.w3.org/Archives/Public/public-data-shapes-wg/2016Mar/0252.html 18:42:26 pfps: as far as I can tell, defaultRange is trying to mirror part of RDFS, so we don't have to put class links on some shapes, in order to support a particular version of the metamodel 18:42:36 q+ 18:42:48 ack simonstey 18:43:13 s/defaultRange/defaultValueType/ 18:45:01 q+ 18:45:11 ack pfps 18:46:25 pfps: this seems to be a special purpose crutch to enable metamodel validation, and of no use elsewhere 18:47:16 PROPOSED: Close ISSUE-128, without action. 18:47:20 -1 18:47:25 +1 18:47:36 -0.5 18:47:38 -.5 18:47:40 0 18:47:45 0 18:47:49 +0.5 18:47:59 PROPOSED: Close ISSUE-128, dropping sh:defaultValueType 18:48:07 -1 18:48:10 q+ 18:48:14 +1 18:48:19 0 18:48:20 0 18:48:22 .5 18:48:26 ack TallTed 18:49:42 +q 18:50:03 ack kcoyle 18:50:04 q+ 18:50:46 kcoyle: I believe we've decided definitively that SHACL includes no inferencing. that makes me wonder how using rdfs:range could help us here. 18:51:23 hknublau: this is about pre-validation inferencing on the shapes graph 18:53:19 ack simonstey 18:53:25 hknublau: the difference is that rdfs:range effectively always adds a type triple, while sh:defaultValueType only applies if there is no other type triple 18:53:43 sh:property [ a sh:PropertyConstraint; sh:predicate ex:property; sh:minCount 1 ] vs. sh:property [sh:predicate ex:property; sh:minCount 1 ] 18:54:28 q+ 18:55:27 simonstey: this seems to be just a bit of shorthand sugar, allowing some explicit statements to be left out 18:55:59 ack Dimitris 18:56:41 Dimitris: I think we need to finalize the metamodel before we'll know whether this is useful or not 18:56:46 q+ 18:57:34 Arnaud: do we break anything if we drop sh:defaultValueType? 18:57:37 hknublau: no 18:57:37 ack TallTed 18:58:37 TallTed: what about marking it Feature At Risk? 18:58:39 q+ 18:58:44 ack pfps 19:01:29 after this discussion, I revise my votes above to +1, -1 19:01:43 s/after this/TallTed: after this/ 19:02:03 q+ 19:02:26 ack kcoyle 19:03:10 kcoyle: I wonder if we're not talking so much about the standard, as implementation variance 19:04:20 Arnaud: anyone else adjusting votes? 19:04:26 RESOLVED: Close ISSUE-128, without action. 19:05:49 topic: Syntax and metamodel Complexity and Possible simplifications 19:06:17 q+ 19:06:24 ack hknublau 19:06:38 background https://lists.w3.org/Archives/Public/public-data-shapes-wg/2016Mar/0255.html 19:08:14 q+ 19:09:21 ack hknublau 19:09:52 q+ 19:10:38 ack pfps 19:11:27 q+ 19:12:17 ack Dimitris 19:13:19 Dimitris: we have two considerations -- metamodel simplification, and syntax simplification. making one simpler tends to make the other more complex. do we simplify life for "engine user" or for "engine writer"? 19:13:38 q+ 19:14:27 ack pfps 19:16:31 pfps: the current design with mixed up PropertyConstraints and property paths is broken. there is some patch in consideration, but it's not clear whether that resolves the whole break. 19:19:23 topic: ISSUE-41: property paths 19:19:23 Arnaud: in the course of this, Property Paths were raised again, and appear to be more broadly acceptable and implementable 19:19:28 q+ 19:19:46 ack Dimitris 19:20:06 q+ 19:20:26 I don't see that closing this the other way is a possibility today. 19:20:33 ack simonstey 19:20:41 Dimitris: ShEx people are likely to have objections here, so if we reopen, shouldn't reclose without them 19:21:26 q+ 19:21:32 ack hknublau 19:22:21 if the extension mechanism will be dropped, we need those paths 19:22:40 hknublau: I wonder whether we now have solutions to a problem that doesn't really exist or isn't that important 19:23:00 ... would probably want this to be in extension mechanism, not core 19:23:20 Yes, we could postpone it. 19:24:05 PROPOSED: Reopen ISSUE-41, based on Peter's email https://lists.w3.org/Archives/Public/public-data-shapes-wg/2016Mar/0290.html 19:24:24 +1 19:24:34 +0.5 as I find them very useful in my implementation 19:24:41 +1 19:25:04 0 19:25:06 -0 19:25:17 +0 19:25:44 RESOLVED: Reopen ISSUE-41, based on Peter's email https://lists.w3.org/Archives/Public/public-data-shapes-wg/2016Mar/0290.html 19:26:12 topic: ISSUE-130: rdf dataset assumption 19:26:16 ISSUE-130? 19:26:16 ISSUE-130 -- SHACL should not assume that the data graph is in an RDF dataset -- open 19:26:16 http://www.w3.org/2014/data-shapes/track/issues/130 19:26:28 q+ 19:26:37 ack Dimitris 19:27:17 q+ to say that the current draft does not depend on datasets 19:27:36 ack pfps 19:27:36 pfps, you wanted to say that the current draft does not depend on datasets 19:29:30 PROPOSED: Close ISSUE-130, as is - the latest draft doesn't require/assume a dataset 19:29:41 +1 19:29:45 +1 19:29:47 +1 19:29:49 +1 19:29:54 +1 19:29:55 +1 19:29:59 0 19:30:11 RESOLVED: Close ISSUE-130, as is - the latest draft doesn't require/assume a dataset 19:30:53 adjourned! 19:30:58 trackbot, end meeting 19:30:58 Zakim, list attendees 19:30:58 As of this point the attendees have been pfps, hknublau, Arnaud, TallTed, simonstey, kcoyle, Dimitris, jamsden 19:31:06 RRSAgent, please draft minutes 19:31:06 I have made the request to generate http://www.w3.org/2016/03/24-shapes-minutes.html trackbot 19:31:07 RRSAgent, bye 19:31:07 I see no action items 19:31:10 Dimitris has left #shapes