13:57:09 RRSAgent has joined #sparql 13:57:09 logging to http://www.w3.org/2012/04/03-sparql-irc 13:57:11 RRSAgent, make logs world 13:57:11 Zakim has joined #sparql 13:57:13 Zakim, this will be 77277 13:57:13 ok, trackbot; I see SW_(SPARQL)10:00AM scheduled to start in 3 minutes 13:57:14 Meeting: SPARQL Working Group Teleconference 13:57:14 Date: 03 April 2012 13:57:21 zakim, this will be sparql 13:57:21 ok, LeeF; I see SW_(SPARQL)10:00AM scheduled to start in 3 minutes 13:57:33 cbuilara has joined #sparql 13:57:44 SteveH_ has joined #sparql 13:57:44 http://www.w3.org/2009/sparql/meeting/2012-03-27#resolution_2 13:58:06 SW_(SPARQL)10:00AM has now started 13:58:13 +LeeF 13:58:25 +pgearon 13:58:31 MacTed has joined #sparql 13:58:45 +kasei 13:59:06 +??P15 13:59:08 +Olivier_ 13:59:10 Zakim, ??P15 is me 13:59:10 +SteveH; got it 13:59:26 bglimm has joined #sparql 13:59:45 +[IPcaller] 13:59:48 zakim, IPCaller is me 13:59:48 +AndyS; got it 14:00:02 +??P19 14:00:09 MattPerry has joined #sparql 14:00:13 Zakim, ??P19 is me 14:00:13 +bglimm; got it 14:00:22 + +1.213.457.aaaa 14:00:32 zakim, aaa is me 14:00:32 sorry, cbuilara, I do not recognize a party named 'aaa' 14:00:39 zakim, aaaa is me 14:00:39 +cbuilara; got it 14:01:02 I can do it 14:01:06 +MattPerry 14:01:09 scribenick: cbuilara 14:01:31 regrets: Axel, Chime 14:01:46 topic: admin 14:01:54 PROPOSED: Accept last week's minutes at http://www.w3.org/2009/sparql/meeting/2012-03-27 14:02:46 LeeF: the csv/tsv we have to work with Sandro about it so we can publish it 14:02:55 RESOLVED: Accept last week's minutes at http://www.w3.org/2009/sparql/meeting/2012-03-27 14:03:01 LeeF: any concertns with last week minutes? 14:03:11 LeeF: April 10th, any regrets? 14:03:17 (none) 14:03:19 at risk here 14:03:26 topic: Overview 14:04:10 LeeF: status, need one more review from LeeF, I still have to do it, anybody would be unconfortable to publish document as conditional LC? 14:04:27 PROPOSED: Publish Overview document as Last Call, conditional on review & changes in wake of review from LeeF 14:04:53 abstain 14:05:10 +1 14:05:12 LeeF: anybody wants to second? 14:05:24 +1 14:05:25 +1 14:05:27 +1 14:05:30 RESOLVED: Publish Overview document as Last Call, conditional on review & changes in wake of review from LeeF, AndyS abstaining 14:05:37 topic: Property paths 14:05:56 Axel's summary of property path options: http://lists.w3.org/Archives/Public/public-rdf-dawg/2012AprJun/0000.html 14:05:56 LeeF: Axel's summary 14:06:27 Axel's summary of path forward for property paths: http://lists.w3.org/Archives/Public/public-rdf-dawg/2012AprJun/0001.html 14:07:08 LeeF: the basic impression is that we have one consensus, try to generate a response to all 3 commenters and move forward 14:10:03 q+ to ask about option 8 wording 14:10:14 LeeF: summary of remaining options: option 3 was the most supported option last option, solved problems with one commenter, option 6 is the newest and scales back, pp can be viewd as syntactic shortcut, it has support in the mailinglist, will be discussed, option 7 adding distict and all keywords for wrapping, option 8 leave semantics unspecified 14:11:00 ack kasei 14:11:00 kasei, you wanted to ask about option 8 wording 14:11:22 Andy's option 6 - http://lists.w3.org/Archives/Public/public-rdf-dawg/2012JanMar/0285.html 14:11:26 LeeF: option 6 by Andy 14:11:31 Andy's option 6 - http://lists.w3.org/Archives/Public/public-rdf-dawg/2012JanMar/0286.html 14:11:47 6.A: /, |, ! as there are in 2LC. 14:11:48 6.B: *, +, ? are non-counting 14:11:48 6.C: No DISTINCT 14:11:48 6.D: No {} forms: {n}, {n,m}, {n,}, {,m} 14:13:10 LeeF: it does not cover all the possible use cases 14:13:41 LeeF: it seems that covers most common cases 14:13:56 LeeF: it cuts complexity that was getting PP 14:14:13 q+ 14:14:17 ack bglimm 14:14:18 LeeF: questions? 14:14:31 bglimm: did you check with commenters? 14:14:48 LeeF: we did, if we agree we will submit the answer 14:15:08 bglimm: we make the most complex operators non counting 14:15:38 +EricP 14:15:57 I think 6 is the best path forward. 14:16:01 LeeF: support or comments for option 6? 14:16:09 +1 for option 6, others were getting too complicated 14:16:11 zakim, who's here? 14:16:11 On the phone I see LeeF, pgearon, kasei, SteveH, Olivier_, AndyS, bglimm, cbuilara, MattPerry, EricP 14:16:13 On IRC I see MattPerry, bglimm, MacTed, SteveH, cbuilara, Zakim, RRSAgent, Olivier, AndyS, LeeF, pgearon, NickH, trackbot, kasei, ya, ericP, sandro 14:16:18 +1 14:16:21 +1 for option 6 14:16:22 +1 to option 6. 14:16:25 +1 14:16:33 +1 14:17:29 LeeF: lets go with option 6, I will make the response based on AndyS summary 14:18:18 AndyS: I think question mark operator, I have not seen much of it 14:19:49 AndyS: leaving it is the better chice 14:19:56 s/chice/choice 14:19:59 PROPOSED: Adopt option 6 as per http://lists.w3.org/Archives/Public/public-rdf-dawg/2012JanMar/0285.html and http://lists.w3.org/Archives/Public/public-rdf-dawg/2012JanMar/0286.html 14:20:38 LeeF: we go ahead and adopt option 6 14:20:44 +1 14:20:45 +1 14:20:48 +1 14:20:52 +1 14:20:58 +0 # too ignorant to vote 14:20:59 +1 14:21:07 RESOLVED: Adopt option 6 as per http://lists.w3.org/Archives/Public/public-rdf-dawg/2012JanMar/0285.html and http://lists.w3.org/Archives/Public/public-rdf-dawg/2012JanMar/0286.html, EricP abstaining 14:21:47 LeeF: amount of work perspective about the option 6? 14:22:12 ACTION: Lee to contact the 3 property path commenters to see if option 6 addresses their concerns with property paths 14:22:12 Created ACTION-605 - Contact the 3 property path commenters to see if option 6 addresses their concerns with property paths [on Lee Feigenbaum - due 2012-04-10]. 14:22:23 AndyS: I will start working on it, but I can't work properly until next week 14:23:09 LeeF: any topic for discussion? 14:23:33 LeeF: AndyS, what about the comments from the RDF WG? 14:23:43 +q 14:23:50 q+ 14:23:51 q- 14:23:52 AndyS: there is an email 14:24:00 -AndyS 14:24:06 topic: colons 14:24:07 http://lists.w3.org/Archives/Public/public-rdf-dawg/2012JanMar/0284.html 14:24:51 {a:b:c:d} 14:25:00 { a:b :c :d } 14:25:16 ericP: this is how it parses now 14:25:31 ericP: there is a backwards incompatibility 14:26:11 LeeF: do we do this change too? or it works for the wg? 14:26:18 +q 14:26:22 ack pgearon 14:26:24 ack ericP 14:26:24 q- 14:26:52 pgearon: it is a good idea, but does it changes the grammar very much? 14:28:05 people have already suggested / and how property paths will end up preventing that... 14:28:39 SteveH; I can't think of a big issue 14:29:02 so long as it doesn't break anything existing, then I'm all for these changes 14:29:27 q+ to also discuss http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/index.html#term-turtle2-BLANK_NODE_LABEL 14:30:04 PROPOSE: bare ':'s are allowed in local names (\'d ':'s not allowed) 14:30:14 PROPOSED: bare ':'s are allowed in local names (\'d ':'s not allowed) 14:30:23 +1 14:30:25 +1 14:30:35 +1 14:30:36 0 14:30:37 0 14:30:40 +1 14:30:47 0 not much clue about this... 14:30:51 0 14:30:55 RESOLVED: bare ':'s are allowed in local names (\'d ':'s not allowed), Greg and Carlos and Birte and Olivier abstaining 14:31:49 ACTION: Andy to update grammar to allow colons in local names 14:31:50 Created ACTION-606 - Update grammar to allow colons in local names [on Andy Seaborne - due 2012-04-10]. 14:32:27 http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/index.html#term-turtle2-BLANK_NODE_LABEL 14:33:08 ericP: if we allow scaping in local names, p and local, it allows the scape medical characters 14:34:19 _:\:foo 14:34:19 ericP: the blank node labels in triple are the same than blank nodes lables in turtle 14:34:48 ericP: no more labels like that _:\:foo 14:34:57 LeeF: Does anybody care? 14:35:02 (silence) 14:35:05 +1 14:35:35 Zakim, mute me 14:35:36 bglimm should now be muted 14:36:01 PROPOSED: Change SPARQL blank node production to be in sync with the Turtle production (e.g. exclude escapes and encodings) 14:36:27 +1 14:36:35 +1 14:36:41 RESOLVED: Change SPARQL blank node production to be in sync with the Turtle production (e.g. exclude escapes and encodings) 14:37:03 ACTION: Andy to update SPARQL grammar for blank node label to match http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/index.html#term-turtle2-BLANK_NODE_LABEL 14:37:03 Created ACTION-607 - Update SPARQL grammar for blank node label to match http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/index.html#term-turtle2-BLANK_NODE_LABEL [on Andy Seaborne - due 2012-04-10]. 14:37:31 Adjourned. 14:37:33 LeeF: anyother business= 14:37:41 -LeeF 14:37:44 bye 14:37:45 -EricP 14:37:46 -SteveH 14:37:46 -MattPerry 14:37:47 bye 14:37:47 -Olivier_ 14:37:47 -bglimm 14:37:49 -kasei 14:37:52 -pgearon 14:38:21 -cbuilara 14:38:22 SW_(SPARQL)10:00AM has ended 14:38:22 Attendees were LeeF, pgearon, kasei, Olivier_, SteveH, AndyS, bglimm, +1.213.457.aaaa, cbuilara, MattPerry, EricP 14:52:14 Re: action 607 - that's what it already says! 14:53:06 The Turtle one was copied from SPARQL. The RDF-WG explicitly decided not chnage it , so I didn't in SPARQL. 14:53:07 [134] BLANK_NODE_LABEL ::= '_:' ( PN_CHARS_U | [0-9] ) ((PN_CHARS|'.')* PN_CHARS)? 14:53:27 is SPARQL and 14:53:37 [134t]       ::=    '_:' ( PN_CHARS_U | [0-9] ) ( ( PN_CHARS | '.' )* PN_CHARS )? is Turtle. 14:53:59 (ericP) 15:04:52 interesting, i don't understand the history of why i ended up changing BLANK_NODE_LABEL to the production you've pasted, but it looks like this is resolved 15:19:46 close ACTION-607 15:19:46 ACTION-607 Update SPARQL grammar for blank node label to match http://dvcs.w3.org/hg/rdf/raw-file/default/rdf-turtle/index.html#term-turtle2-BLANK_NODE_LABEL closed 15:19:51 ACTION-605? 15:19:51 ACTION-605 -- Lee Feigenbaum to contact the 3 property path commenters to see if option 6 addresses their concerns with property paths -- due 2012-04-10 -- OPEN 15:19:51 http://www.w3.org/2009/sparql/track/actions/605 15:19:54 close ACTION-605 15:19:54 ACTION-605 Contact the 3 property path commenters to see if option 6 addresses their concerns with property paths closed 15:48:55 SteveH has joined #sparql 15:49:07 SteveH_ has joined #sparql 17:01:31 Zakim has left #sparql