13:58:45 RRSAgent has joined #sparql 13:58:45 logging to http://www.w3.org/2010/06/08-sparql-irc 13:58:52 trackbot, start meeting 13:58:55 RRSAgent, make logs world 13:58:57 Zakim, this will be 77277 13:58:57 ok, trackbot; I see SW_(SPARQL)10:00AM scheduled to start in 2 minutes 13:58:58 Meeting: SPARQL Working Group Teleconference 13:58:58 Date: 08 June 2010 14:00:03 SW_(SPARQL)10:00AM has now started 14:00:10 +kasei 14:00:42 MattPerry has joined #sparql 14:00:49 +pgearon 14:00:56 +AxelPolleres 14:01:19 Zakim, who is on the phone? 14:01:19 On the phone I see kasei, pgearon, AxelPolleres 14:01:20 +[IPcaller] 14:01:26 zakim, IPCaller is me 14:01:26 +AndyS; got it 14:01:35 + +1.603.897.aaaa 14:01:47 zakim, aaaa is me 14:01:47 +MattPerry; got it 14:01:48 zakim, dial ivan-voip 14:01:48 ok, ivan; the call is being made 14:01:49 +Ivan 14:01:54 Zakim, who is on the phone? 14:01:54 On the phone I see kasei, pgearon, AxelPolleres, AndyS, MattPerry, Ivan 14:01:56 SteveH__ has joined #sparql 14:02:10 + +1.603.897.aabb 14:02:12 Souri has joined #sparql 14:02:14 +[Garlik] 14:02:17 agenda: http://www.w3.org/2009/sparql/wiki/Agenda-2010-06-08 14:02:29 Zakim, [Garlik] is temporaily me 14:02:29 I don't understand '[Garlik] is temporaily me', SteveH 14:02:39 Zakim, [Garlik] is temporarily me 14:02:39 +SteveH; got it 14:02:39 scribe: SteveH 14:02:48 chair: AxelPolleres 14:02:52 +Sandro 14:03:03 +??P33 14:03:08 Zakim, who is on the phone? 14:03:08 On the phone I see kasei, pgearon, AxelPolleres, AndyS, MattPerry, Ivan, +1.603.897.aabb, SteveH, Sandro, ??P33 14:03:22 sandro has changed the topic to: http://www.w3.org/2009/sparql/wiki/Agenda-2010-06-08 14:03:30 zakim, aabb is me 14:03:30 +Souri; got it 14:03:30 Zakim, ??P33 is me 14:03:31 +NickH; got it 14:03:33 there's too much noise on the line 14:03:41 Zakim, who's speaking? 14:03:44 http://www.w3.org/2009/sparql/wiki/Agenda-2010-06-08 14:03:51 SteveH, listening for 10 seconds I heard sound from the following: AxelPolleres (8%), Sandro (38%), Ivan (20%) 14:04:05 better? 14:04:11 sandro, yes, thanks 14:04:12 yes 14:04:23 PROPOSED: Approve minutes at http://www.w3.org/2009/sparql/meeting/2010-06-01 14:04:40 +1 14:04:43 +1 14:04:48 RESOLVED: Approve minutes at http://www.w3.org/2009/sparql/meeting/2010-06-01 14:05:14 http://www.w3.org/2009/sparql/wiki/Comments 14:05:19 AxelPolleres: all comments are assigned, look at page please 14:05:28 ... some old ones are still open 14:05:37 +[IPcaller] 14:05:43 zakim, IPcaller is me 14:05:43 +LeeF; got it 14:06:19 ... IRI creating comment, I will reply 14:06:33 ... doesn't look too bad, but please update 14:06:58 topic: liaisons 14:07:29 Souri: rdf2rdb has progress, almost ready to publish 14:07:36 q? 14:07:47 ack sandro 14:07:52 (I don't think the RDB group needs a UC&R review from the SPARQL WG) 14:08:13 sandro: rif, today is the last day of the review period 14:08:28 ... egov, working on charter for linked data for govt. working group 14:08:45 ... lots of enthusiasm, put together some education and outreach, plus more serious stuff 14:08:52 ... might produce recommendations 14:09:16 Not able to join the telcon, the phone is out of order here ... 14:09:29 topic: http rdf update TC 14:09:33 http://www.w3.org/2009/sparql/meeting/2010-06-07 14:09:38 AxelPolleres: update minutes 14:10:15 ... no resolutions, but base URI agreement on how it's addressed, proposed text from chime 14:10:31 ... will add example for when there no BASE in the payload 14:10:46 ... resolved terminology change re. networked rdf knowledge 14:11:04 UC&R FPWD for RDB2RDF: http://www.w3.org/2001/sw/rdb2rdf/use-cases/ 14:11:09 http://www.w3.org/2009/sparql/track/issues/49 14:11:16 ... discussion about graph URIs er. ISSE-49 14:11:32 ... not sure what to do about URIs which [sth] when you reference them 14:11:52 http://www.w3.org/2001/tag/issues#httpRange-14 14:12:30 ... want to point out that we dont want to discourage, we expect that some might allow HTTP and other protocol 14:12:30 bglimm has joined #sparql 14:12:56 ... want to say that it might lead to ambiguity, give general warning, point to TAG issue 14:13:03 ... how/can we do that? 14:13:20 ... can we reference a TAG issue in a Rec track document? 14:13:26 + +0186528aacc 14:13:33 Zakim, mute me 14:13:33 sorry, bglimm, I do not know which phone connection belongs to you 14:13:38 q+ 14:13:42 ivan: I think the answer is yes, but not sure 14:13:46 Zakim, +0186528aacc is me 14:13:46 +bglimm; got it 14:13:52 Zakim, mute me 14:13:52 bglimm should now be muted 14:14:06 AndyS: the TAG findings aren't recs, what standing do they have 14:14:26 ivan: "TAG findings" - they have no other official standing 14:14:28 Can we give it as an informal reference? 14:14:57 sandro: we can't normatively reference them, but can informatively 14:15:25 ... can't say "to find out how to do this look [at TAG finding]" cos it's not a Rec 14:16:03 :-) 14:16:16 Basically it's like with Turtle and CURIEs ---- we wanted the concept, but there was no REC, so we had to write it ourselves. 14:16:16 AxelPolleres: either quote text, or reference it informatively 14:16:34 Yes, we do. 14:16:36 normative and informative references. 14:17:05 best solution is probably a combination. 14:17:07 AndyS: we take textual forms from Turtle, and include them in the document 14:17:22 AxelPolleres: explain possible ambiguity, and informally reference 14:17:37 But the Wuery spec says: This document uses the http://www.w3.org/TeamSubmission/turtle/ [TURTLE] data format to show each triple explicitly. 14:17:50 s/Wuery/Query/ 14:18:04 ACTION: axel to convey summary to chime: explain possible ambiguity, and informally reference TAG issue. 14:18:04 Created ACTION-255 - Convey summary to chime: explain possible ambiguity, and informally reference TAG issue. [on Axel Polleres - due 2010-06-15]. 14:18:29 Zakim, mute me 14:18:29 kasei should now be muted 14:18:37 AxelPolleres: there's a red box in the document, it's enough to drop it 14:18:38 s/chime/Chime/ 14:18:49 ... discussion about other terms, and distinctions 14:19:01 unclear "network-manipulable RDF dataset" and distinction from "graph store" and "endpoint" needs clarification 14:19:18 bglimm, that's for the data in examples; not the SPARQL syntax (although that isn't as formal as I'd like) 14:19:21 AxelPolleres: overall doc on good track 14:19:39 Topic: find possible slot for testcases call 14:19:44 Ah, I thought it is for the whole doc including where parts of queries 14:19:49 bglimm, c.f. "4.2 Syntax for Triple Patterns" 14:20:19 http://www.doodle.com/ctb2a6t3bxup8t4d 14:20:26 AndyS, I see what you mean 14:20:41 AxelPolleres: there are several actions on collecting testcases 14:20:51 http://www.w3.org/2009/sparql/track/actions/191 14:21:11 ... would be helpful to have emails pointing to testcases 14:21:27 ... don't need to be formal, just want to track them 14:21:40 ... people are responsible for collecting them 14:22:11 ... david, Olivier, AxelPolleres have outstanding actions 14:22:26 ... make sure that you fill out the poll 14:23:04 Topic: Function Library 14:23:06 http://lists.w3.org/Archives/Public/public-rdf-dawg/2010AprJun/0309.html 14:23:18 AxelPolleres: AndyS has added several functions 14:23:44 ... main question is what's open 14:23:53 ... put some more links about this 14:24:11 ... one question is what about xquery and xpath F&O, we have initial list proposed by AndyS 14:24:11 http://lists.w3.org/Archives/Public/public-rdf-dawg/2009JulSep/0244.html 14:24:25 http://www.w3.org/2009/sparql/wiki/Feature:FunctionLibrary#Starting_Points 14:24:29 ... incorporated in wiki doc ^ 14:24:38 ... and we have one more doc on the wiki 14:24:41 http://www.w3.org/2009/sparql/wiki/Design:FunctionLibrary 14:24:51 ... also half baked 14:25:15 ... do we reuse URIs in F&O? 14:25:58 ... AFAIR, we have had some discussion about namespaces 14:26:16 ... keywords v's namespaced URIs 14:26:30 AndyS: I don't remember that dicsussion 14:26:39 -Sandro 14:26:41 ... there are some functions that dont exsists elsewhere 14:26:55 ... have to assign URIs 14:27:14 +Sandro 14:27:31 AxelPolleres: do we have a namespace already for the sparql F&O 14:27:44 ivan: I did set one up. 14:28:04 AxelPolleres: could look at initial draft 14:28:10 http://www.w3.org/ns/sparql.html 14:28:36 that should be fine... 14:28:53 http://www.w3.org/2009/sparql/docs/query-1.1/rq25.xml#func-coalesce 14:29:10 ivan: it's obvious what you have to do to add more items 14:29:26 AxelPolleres: that would affect all the operators that are new in SPARQL 14:29:34 ivan: yes 14:29:49 AxelPolleres: things in ยง15.4 need URIs 14:30:10 ivan: I will update doc if you send me changes 14:30:29 For Ivan: http://www.w3.org/2009/sparql/docs/query-1.1/rq25.xml#SparqlOps 14:30:35 ivan, might be nice to assert rdf:type sd:Function for the functions in /ns/sparql 14:30:43 15.4.14 COALESCE 14:31:42 COALESCE, IF, IN, NOT IN, IRI, URI, BNODE, STRDT, STRLANG 14:31:44 q+ 14:31:57 ack AndyS 14:31:58 ack me 14:32:24 ivan: better decided around a table with beer 14:32:31 ... new ones are all caps, old ones are not 14:32:41 if, in 14:32:45 and not IF and IN 14:32:47 SPARQL is case-insenitive keywords (except for "a") 14:32:48 AxelPolleres: it would make sense to keep with what we had 14:32:52 they're all case insensitive in the language, though. 14:33:18 AxelPolleres: it's difficult, for the short names we have camel case 14:33:20 q+ 14:33:26 ack ivn 14:33:29 ack ivan 14:33:40 yes. was just pointing it out because we don't have URIs for the old ones yet 14:34:20 ack me 14:34:23 camelCase seems to be the URI candidates, capital used in the definition 14:34:35 Yes - the grammar uses UC for clarity. Examples use same case as section name (usually) 14:34:35 capital used in grammar/examples 14:34:43 -NickH 14:34:49 AndyS, oh, sorry, thought it was UC in examples 14:34:56 "if" looks silly 14:35:26 notIn 14:35:36 +1 to ivan 14:35:49 AxelPolleres: just make it uniform 14:36:01 ACTION: ivan to buy beers in SF 14:36:01 Sorry, amibiguous username (more than one match) - ivan 14:36:01 Try using a different identifier, such as family name or username (eg. ivan, imikhail) 14:36:52 AxelPolleres: take this to mail 14:37:07 AndyS: are we putting the F&O set in this doc, or another, or somewhere else 14:37:26 AxelPolleres: extension to core functions which we endorse should be in Q document 14:37:36 AndyS: who's going to write it 14:37:46 15.4.21 example needs a closing paranthesis: STRDT("123", xsd:integer 14:37:49 ... it will take longer if I do it 14:38:01 AxelPolleres: what new text do we need? 14:38:12 ... do we need to add examples for all these functions 14:38:14 souri - already fixed (in my copy) 14:38:43 AxelPolleres: what's missing is the formulation, and adding examples [?] 14:38:44 http://www.w3.org/2009/sparql/docs/query-1.1/rq25.xml#func-coalesce 14:40:08 http://www.w3.org/2009/sparql/wiki/Design:FunctionLibrary 14:40:21 AxelPolleres: not sure about issues around sequences 14:40:34 AndyS: functions in [uri] are directly relevant to SPARQL, no seuences 14:40:44 ... arguments all values that we grok 14:41:18 ... unclear what the proposed way forwards is about this list, how do we deal with rel. to F&O 14:41:24 3 options 14:41:25 ... see 3 proposals 14:41:39 ... 1) start from SQL 14:41:45 I think the 2nd of those proposals is the best 14:41:46 ... 2) import a speicific set 14:41:56 ... 3) point to F&O equiv 14:42:32 ... in one there are two URIs 14:43:06 AxelPolleres: LeeF thinks we should import a specific set 14:43:06 Is anyone wanting to advocate taking from SQL instead of XPath/XQuery ? 14:43:24 ... if we import we can change them slightly if needed 14:43:40 (I'm wondering about taking from RIF, which took option 3.) 14:43:41 LeeF: not sure how much support there is to import from SQL 14:44:05 AxelPolleres: We have COALESCE and IF from SQL 14:44:12 (i'd be fine with that approach as well, sandro. I don't know that much about the RIF function basis.) 14:44:14 ... strawpoll on 2) vs 3) 14:44:16 Interesting -sandro - why did it do that? 14:44:28 q+ 14:44:33 zakim, unmute me 14:44:33 Sandro should no longer be muted 14:44:44 sandro: story from RIF, having same debate 14:45:01 ... use URIs or make own, decided to make own URIs 14:45:16 ... needed to change semantics in a few places, watned to add a few things, users would like in same namesoace 14:45:24 ... operators don't have URIs anyway 14:45:28 q+ 14:45:34 q+ 14:45:39 ... should sparql and rif use same URIs 14:45:46 q- 14:46:04 ... sparql and rif could coalesce on common uris, and they're both RDFy 14:46:13 AndyS: where did you have to change the smeantics 14:46:22 q+ to speak chair-hat off 14:46:30 sandro: hoping AxelPolleres would remember, something about sequences 14:46:48 ... sequences have unusual semantics 14:46:51 erorrs, sequences, played a role 14:46:55 zakim, mute me 14:46:55 Sandro should now be muted 14:46:58 ack me 14:46:58 AxelPolleres, you wanted to speak chair-hat off 14:46:59 ... outside of that I don't remember the differences 14:47:06 q- 14:47:12 AxelPolleres: we had problems with errors too, no errors in RIF 14:47:30 ... what would we do with errors 14:47:36 SPARQL is F&O evaluation 14:47:43 (I think the errors bit is not worth doing a different URI over, personally, but I'm not a formalist.) 14:47:55 ... with errors being an extension point 14:48:32 ... if we use own namespace we dont have to think about which ones are keywords, if it has a URI in sparql namespace it can be used in syntax 14:48:40 q? 14:48:47 q- 14:49:20 AxelPolleres: poll: keep F&O namespace, or give own [sparql] namespace 14:49:34 1 - keep namespace 14:49:39 2 - sparql ns 14:49:45 2 14:49:46 2 14:49:48 Option 2 (reuse namespace + alloc a namespace for operators) 14:49:52 2 (mild preference, would like to see rif+sparql convergence) 14:49:56 2 14:49:56 2 14:49:57 1 14:50:11 0 14:50:15 0 unsure..... 14:50:30 Option 1 (reuse namespace + alloc a namespace for operators) 14:50:47 Yeah, I agree with that 14:50:50 too many keywords :) 14:52:54 AxelPolleres: op: ones are things that can be moddled with + etc. [?] 14:53:02 op :  + - ! 14:53:19 http://lists.w3.org/Archives/Public/public-rdf-dawg/2009JulSep/0244.html 14:53:22 "op:" has no namespace officially 14:53:37 AxelPolleres: we dont have a URI for them 14:53:44 yes - but what about writing "op:numeric-add(?X, ?Y)" 14:54:15 AxelPolleres: you have to write the short form in xpath etc. 14:54:50 ... datatypes depenends on how it's delegates 14:55:05 http://www.w3.org/2009/sparql/wiki/Design:FunctionLibrary 14:55:23 ... not complete, but we should have op URI + shortcut 14:55:45 ... then shortcuts come from [sth] 14:56:01 ... should take to email, running out of time 14:56:02 My pref: complete Design:FunctionLibrary as a design then take to WG. 14:56:55 AndyS: I don't have any time in next 2 weeks 14:57:01 ACTION: Axel to work out http://www.w3.org/2009/sparql/wiki/Design:FunctionLibrary within 2 weeks 14:57:01 Created ACTION-256 - Work out http://www.w3.org/2009/sparql/wiki/Design:FunctionLibrary within 2 weeks [on Axel Polleres - due 2010-06-15]. 14:57:41 http://lists.w3.org/Archives/Public/public-rdf-dawg/2010AprJun/0311.html 14:58:03 AndyS: couple of proposals, realtively decided on cardinality, want to work on details 14:58:48 -LeeF 14:59:12 AndyS: don't think there's enough detail to make proposal 14:59:59 ... matter of writing document and coming back with proposal 15:00:14 AxelPolleres: as long as you know where it's going 15:00:36 update next time 15:00:40 + other issues 15:00:51 At risk next time: AndyS 15:01:03 -bglimm 15:01:08 zakim, drop me 15:01:08 Ivan is being disconnected 15:01:09 -Ivan 15:01:10 adjourned 15:01:11 -SteveH 15:01:15 -Souri 15:01:15 quit 15:01:16 -kasei 15:01:18 -AndyS 15:01:19 -MattPerry 15:01:21 -pgearon 15:01:23 thanks steve for scribing... 15:01:23 -Sandro 15:01:26 AxelPolleres, how do I make mins from the IRC? 15:01:37 rrsagent, make records public 15:01:56 steve, will handle that... essentially: http://www.w3.org/2009/CommonScribe/manual.html 15:02:05 thanks AxelPolleres 15:03:19 -AxelPolleres 15:03:23 SW_(SPARQL)10:00AM has ended 15:03:27 Attendees were kasei, pgearon, AxelPolleres, AndyS, +1.603.897.aaaa, MattPerry, Ivan, +1.603.897.aabb, SteveH, Sandro, Souri, NickH, LeeF, bglimm 15:03:40 SteveH has joined #sparql 15:09:24 OlivierCorby has left #sparql 17:02:06 Apologies for any duplicate emails - I seem to "discovered a feature" of gmail and eventual (in?)consistency 17:18:24 Zakim has left #sparql 18:25:52 pgearon has joined #sparql 18:32:32 AndyS has joined #sparql 19:07:36 pgearon has joined #sparql 19:47:49 AndyS has joined #sparql 20:50:23 http://www.w3.org/2009/sparql/wiki/CommentResponse:MH-1 20:55:28 AxelPolleres has joined #sparql 21:04:39 AxelPolleres has left #sparql 21:12:10 LeeF has joined #sparql 21:45:40 AndyS has joined #sparql 21:49:11 bglimm has joined #sparql 21:57:18 karl has joined #sparql 22:32:40 karl has joined #sparql