18:59:14 RRSAgent has joined #shapes 18:59:14 logging to http://www.w3.org/2016/02/25-shapes-irc 18:59:16 hknublau has joined #shapes 18:59:16 RRSAgent, make logs rdf-data-shapes 18:59:16 Zakim has joined #shapes 18:59:18 Zakim, this will be SHAPES 18:59:18 I do not see a conference matching that name scheduled within the next hour, trackbot 18:59:19 Meeting: RDF Data Shapes Working Group Teleconference 18:59:19 Date: 25 February 2016 18:59:26 Dimitris has joined #shapes 19:00:25 present+ 19:01:32 agenda: https://www.w3.org/2014/data-shapes/wiki/Meetings:Telecon2016.02.25 19:01:38 chair: Arnaud 19:01:43 pfps has joined #shapes 19:01:47 present+ 19:01:57 present+ 19:02:28 aryman has joined #shapes 19:03:04 present+ 19:03:07 present+ aryman 19:03:15 scribe: dimitris 19:03:35 present+ 19:03:53 present+ 19:03:55 jima has joined #shapes 19:04:07 present+ Dimitris: I have an open source implementation of SHACL people can try Arnaud: That's great, please, add it to the list on the WG page 19:04:35 It would be interesting to know the implementation philosophy of Dimitris's implementation 19:04:38 regrets: labra 19:04:46 present+ 19:04:52 @Dimitris great news 19:05:08 https://github.com/AKSW/RDFUnit/issues/62 topic: Admin 19:05:17 PROPOSED: Approve minutes of the 18 February 2016 Telecon: http://www.w3.org/2016/02/18-shapes-minutes.html 19:05:33 looks good 19:05:38 looked fine to me 19:05:46 arnaud: any objection to approve theminutes of last week? 19:06:06 hsolbrig has joined #shapes 19:06:09 RESOLVED: Approve minutes of the 18 February 2016 Telecon: http://www.w3.org/2016/02/18-shapes-minutes.html 19:07:38 arnaud: there is a change in WG membership, Arthur is retiring from the WG due to other commitments ... on behalf of the W3C, I want to publicly thank Arthur for his contribution, we will miss him 19:08:25 sad to see you go, aryman! you've made significant contributions to our progress. 19:08:46 thanks 19:08:49 sad to see you go as well 19:09:18 you will be missed topic: Formal Specification 19:10:28 arnaud: Arthur had an action to draft a semantics document for the specification, I want to give the option to WG, instead of closing this action someone can take over 19:10:55 .. is anyone interested to take over or should we close it? Arnaud: hearing none we will then close Arthur's action, anyone is still free to make a proposal later on if they want to 19:11:25 topic: ISSUE-95 19:11:25 ISSUE-95 -- Proposed simplification and clean up of template mechanism -- open 19:11:25 http://www.w3.org/2014/data-shapes/track/issues/95 19:12:10 Arnaud: Arthur, Holger and Simon came back with two proposals 19:12:54 https://www.w3.org/2014/data-shapes/wiki/ISSUE-95:_Metamodel_simplifications#Proposal_3 19:13:01 ... let's discuss the agreements 19:15:05 hknublau: we had a lot of redundant metaclasses and made very good progress thanks to Arthur 19:16:00 ... we agreed that the term "template" is misleading and arguments have been renamed to parameters 19:17:02 ... (... reading and explaining the proposal...) 19:28:05 I thought that this was supposed to be a simplification! 19:36:47 +q 19:36:55 ack Dimitris 19:40:22 dimitris: asking when we use the constraints in filter if we need a different query (decided to take it offline) 19:41:36 aryman: the motive for doing this was to avoid the same sparql code in different queries and holger tried to refactor that 19:42:22 ... in holger's design the sparql engine has to do the surgery, it's a little more complex and requires more implementation 19:43:19 ... easier to debug your queries too but the downside is that you might have 3 very similar queries but maybe it's not so bad 19:43:33 http://w3c.github.io/data-shapes/shacl/#functions 19:44:12 ... in my proposal it corresponds to simple rdfs classes 19:44:30 q+ 19:45:13 simonstey: proposal 3 is much inline with arthur's proposal 19:46:01 ... we already have defined functions in the spec and we allow users to define their functions 19:47:57 ... it's kind of difficult, extending shacl should be different from using shacl and I'm inclined in option a 19:48:00 ack pfps 19:48:24 pfps: I thought we would simplify but it's still complex 19:48:58 ... our syntax is complicated and hard to understand 19:49:13 aryman_ has joined #shapes 19:49:48 ... another complexity is the support for different execution languages that noone implements 19:50:19 .. that's why I like Arthur's proposal 19:50:31 q+ 19:50:32 q+ 19:50:50 q+ 19:50:52 ack hknublau 19:51:25 hknublau: we have javascript support in spin already 19:52:21 ... node validation functions are not that hard to implement and people can use the verbose approach 19:52:59 q+ 19:53:08 ack jima 19:53:09 ... what I do not like about Arthurs constraint classes is that they are never instantiated 19:54:36 jima: I have sympathy for adding complexity to solve problems, I need time to read the proposals more 19:54:47 ack pfps 19:55:40 pfps: both proposals are not simple but I see Arthurs simpler. 19:55:44 q+ 19:55:47 ack aryman 19:56:36 aryman: in my view the classes are instantiated, sh:property is an sh:propertyConstraint and are instantiated 19:57:20 hknublau: then you need rdfs inferencing 19:57:30 aryman: it will be an engine rule 19:58:15 ... this will be how a shacl engine will treat a shacl program 19:58:26 ack Dimitris 19:59:27 dimitris: in my implementation Arthurs proposal will be easier to implement 20:00:01 arnaud: let's leave it at this for today 20:00:04 topic: ISSUE-22 20:00:04 ISSUE-22 -- Treatment of recursive shape definitions -- open 20:00:04 http://www.w3.org/2014/data-shapes/track/issues/22 20:00:35 what about http://w3c.github.io/data-shapes/shacl/#functions if we don't want/can process custom functions? 20:01:26 arnaud: Arthur had an action for a recursion proposal and said he cannot deliver. We are free to be 20:01:47 ... completely silent or have a statement about recursion 20:02:05 q+ 20:02:19 @simonstey agreed, plus we decided to not limit ourselves to SPARQL endpoints. Furthermore, I believe implementations can just inject the ASK part into a new query template. 20:02:41 ack aryman 20:03:47 aryman: I send a part of a recursion spec I did write. It was recursion for OSLC RS but SHACL is more powerfull 20:04:38 ... there is a huge intersection of RS and SHACL and we can define recursion only on that part 20:05:10 q+ 20:05:19 ack jima 20:05:33 q+ 20:06:14 jima: isn't the problem still there? (grey recursion areas) 20:07:14 ack pfps 20:07:15 aryman: by defining recursion in a subset we move some obstacles in SHACL adoption 20:08:19 pfps: Arthurs semantics are not tight to anything we understand (Z language) 20:08:50 ... something in the lines of the RDF semantics would be useful 20:10:02 (didn't hear Eric, voice was breaking) 20:10:07 q+ 20:10:16 ack aryman 20:10:55 aryman: we can be conservative with recursion like static analysis and reject all loops 20:11:54 ... Eric is taking a conservative approach 20:12:38 arnaud: what do we do now? will someone pick this up? 20:12:54 ... if not we need to discuss how to close this 20:13:40 q+ 20:14:04 ack jima 20:15:07 jima: we can say nothing, leave it to implementers or say will be supported in a later version 20:16:50 topic: ISSUE-92 20:16:50 ISSUE-92 -- Should repeated properties be interpreted as additive or conjunctive? -- open 20:16:50 http://www.w3.org/2014/data-shapes/track/issues/92 20:17:14 q+ 20:17:24 ack aryman 20:18:02 aryman: I got a note from iovka for a proposal related to this. She found the partition proposal well founded 20:19:12 ericp: I hope to get a little of her time next week 20:20:50 topic: ISSUE-99 20:20:50 ISSUE-99 -- special treatment of rdfs:Resource and rdf:List in sh:valueClass (and possibly elsewhere) -- open 20:20:50 http://www.w3.org/2014/data-shapes/track/issues/99 20:21:52 pfps: special treatment of rdf:List and rdfs:Resource should be removed 20:22:05 ... if we do something for rdf:List we should do it right 20:22:15 q+ 20:22:32 ack hknublau 20:23:10 hknublau: we just try to identify that it is an rdf:List 20:23:54 ... for rdfs:Resource we can use sh:nodeKind 20:24:14 q+ 20:24:40 ack Dimitris 20:24:43 ... we can add an issue for better support of rdf:Lists, I am not against to what Peter suggests 20:26:06 +1 20:26:16 dimitris: prefer to remove the checks of rdf:List and rdfs:REsource to sh:nodeKind 20:30:53 trackbot, end meeting 20:30:53 Zakim, list attendees 20:30:53 As of this point the attendees have been Arnaud, simonstey, pfps, Dimitris, aryman, hknublau, kcoyle, TallTed, ericP, hsolbrig 20:31:01 RRSAgent, please draft minutes 20:31:01 I have made the request to generate http://www.w3.org/2016/02/25-shapes-minutes.html trackbot 20:31:02 RRSAgent, bye 20:31:02 I see no action items