14:54:50 RRSAgent has joined #sparql 14:54:50 logging to http://www.w3.org/2010/11/30-sparql-irc 14:54:52 RRSAgent, make logs world 14:54:52 Zakim has joined #sparql 14:54:54 Zakim, this will be 77277 14:54:54 ok, trackbot; I see SW_(SPARQL)10:00AM scheduled to start in 6 minutes 14:54:55 Meeting: SPARQL Working Group Teleconference 14:54:55 Date: 30 November 2010 14:54:56 zakim, this will be SPARQL 14:54:56 ok, LeeF; I see SW_(SPARQL)10:00AM scheduled to start in 6 minutes 14:55:08 SW_(SPARQL)10:00AM has now started 14:55:15 +??P6 14:55:25 Zakim, +??p6 is me 14:55:26 sorry, cbuilara, I do not recognize a party named '+??p6' 14:55:38 Zakim, ??P6 14:55:38 I don't understand '??P6', cbuilara 14:55:48 Zakim, ??P6 is me 14:55:48 +cbuilara; got it 14:55:54 + +1.617.553.aaaa 14:56:02 zakim, aaaa is me 14:56:02 +LeeF; got it 14:56:05 NicoM has joined #sparql 14:56:28 +??P9 14:56:35 zakim, ??P9 is me 14:56:35 +AndyS; got it 14:57:12 +kasei 14:57:38 +??P11 14:58:01 zakim, ??P11 is me 14:58:01 +NickH; got it 14:58:49 + +49.911.973.4.aabb 14:59:04 Zakim, +49 is me 14:59:04 +NicoM; got it 14:59:09 Chair: LeeF 14:59:24 Regrets: SteveH 15:00:02 Agenda: http://lists.w3.org/Archives/Public/public-rdf-dawg/2010OctDec/0316.html 15:00:07 +OlivierCorby 15:00:21 MattPerry has joined #sparql 15:00:23 Zakim, who is talking? 15:00:34 kasei, listening for 11 seconds I heard sound from the following: AndyS (17%) 15:00:56 very strage sounding jack hammers :) 15:01:04 ok, guess not then :) 15:01:06 bglimm has joined #sparql 15:01:11 zakim, who's on the phone? 15:01:11 On the phone I see cbuilara, LeeF, AndyS, kasei, NickH, NicoM, OlivierCorby 15:01:17 +MattPerry 15:01:21 Scribenick: cbuilara 15:01:23 Scribe: Carlos 15:02:11 I can't hear anything 15:03:11 topic: Admin 15:03:24 PROPOSED: Approve minutes from http://www.w3.org/2009/sparql/meeting/2010-11-23 15:03:44 +AxelPolleres 15:03:46 LeeF: shorcuts, ask for feedback 15:04:04 Leef: ask for implementation experience about update shorcuts 15:04:22 RESOLVED: Approve minutes from http://www.w3.org/2009/sparql/meeting/2010-11-23 15:04:50 Next meeting: Tuesday December 7, 2010 - usual time and place 15:04:58 pgearon_ has joined #sparql 15:05:02 LeeF: next meeting 7th December 15:05:16 regrets next week: cbuilara 15:05:26 regrets also 15:05:43 regrets for me next week as well 15:05:55 LeeF: 28th week of 15:06:21 LeeF: tomorrow working session on protocol document 15:06:27 + +44.186.528.aacc 15:06:27 -AndyS 15:06:42 + +1.540.841.aadd 15:06:45 +[IPcaller] 15:06:48 LeeF: goal: have a protocol proposal for the group 15:06:52 +Sandro 15:06:55 Zakim, +44.186.528.aacc is me 15:06:55 +bglimm; got it 15:06:55 Zakim: IPcaller is me 15:07:01 Zakim: aadd is me 15:07:05 +??P31 15:07:06 (sorry I'm late) 15:07:11 Zakim: +IPcaller is me 15:07:14 LeeF: look at the entailment decision for next week 15:07:17 zakim, ??P31 is me 15:07:17 +AndyS; got it 15:07:19 next week... entailment decisions 15:07:26 zakim, who's on the phone? 15:07:26 On the phone I see cbuilara, LeeF, kasei, NickH, NicoM, OlivierCorby, MattPerry, AxelPolleres, bglimm, +1.540.841.aadd, [IPcaller], Sandro, AndyS 15:07:36 zakim, aadd is pgearon 15:07:36 +pgearon; got it 15:07:38 Zakim, [IPcaller] is me 15:07:38 +AlexPassant; got it 15:08:30 topic: which functions? 15:08:41 -AlexPassant 15:09:12 PROPOSED: SPARQL 1.1 Function Library includes all of the functions listed at http://lists.w3.org/Archives/Public/public-rdf-dawg/2010OctDec/0188.html except for fn:error and the DateTime functions 15:09:45 PROPOSED: SPARQL 1.1 Function Library includes all of the functions listed at http://lists.w3.org/Archives/Public/public-rdf-dawg/2010OctDec/0188.html except for fn:error and the DateTime functions and including RAND() and RAND(X) 15:09:47 +AlexPassant 15:10:38 q+ 15:10:42 ack kasei 15:10:55 CONCAT has turned out *potentially* different. 15:11:18 q+ 15:11:25 kasei: date time functions are useful, but not necessarily with keywords 15:11:31 ack pgearon 15:11:52 pgearon: everybody is going to support date/time, I want see them in 15:12:43 AndyS: we need to provide keywords, testing to see where the boundary is here 15:13:19 PROPOSED: SPARQL 1.1 Function Library includes all of the functions listed at http://lists.w3.org/Archives/Public/public-rdf-dawg/2010OctDec/0188.html except for fn:error and including RAND() and RAND(X) 15:13:50 LeeF: is anybody who feels that should not include these date time functions? 15:13:55 (silence) 15:14:02 :-D 15:14:19 fn:round-half-to-even 15:14:30 LeeF: dodgy ones are fn:round-half-to-even 15:14:34 s/LeeF/AndyS 15:15:42 AndyS: dodgyness: in applications type float cannot be intuitive 15:15:49 http://www.w3.org/TR/xpath-functiofn:round-half-to-evenns/#func-round-half-to-even 15:16:02 http://www.w3.org/TR/xpath-functions/#func-round-half-to-even 15:16:08 LeeF: anybody has experinece with that round-half-to-even? 15:16:21 s/experinece/experience 15:16:34 was the proposal to implement both the one and two-arg forms? 15:17:28 anyone really wanting round-half-to-even? 15:17:35 LeeF: the proposal would be to include all forms, all related functions of fn form 15:18:11 AndyS: omitt it 15:18:13 +1 omit 15:18:16 +1 omit 15:18:23 +1 omit 15:18:26 LeeF: ample support for omit 15:18:31 +1 omit 15:18:36 PROPOSED: SPARQL 1.1 Function Library includes all of the functions listed at http://lists.w3.org/Archives/Public/public-rdf-dawg/2010OctDec/0188.html except for fn:error, fn:round-half-to-even and including RAND() and RAND(X) 15:19:36 ±1 15:19:48 AndyS: the operators are already there, the question is whether you can call it 15:20:02 http://www.w3.org/2009/sparql/docs/query-1.1/rq25.xml#OperatorMapping 15:20:49 ANdyS: the ones missing are dates ones 15:21:01 s/ANdyS/AndyS 15:21:10 q+ 15:21:15 ack AxelPolleres 15:21:41 +Chimezie_Ogbuji 15:21:45 LeeF: leave it as it is, comparison support, add date time functions 15:21:50 PROPOSED: SPARQL 1.1 Function Library includes all of the functions listed at http://lists.w3.org/Archives/Public/public-rdf-dawg/2010OctDec/0188.html except for fn:error, fn:round-half-to-even, the op:* and including RAND() and RAND(X) 15:22:29 http://www.w3.org/TR/xpath-functions/#func-compare 15:22:43 chimezie has joined #sparql 15:22:50 LeeF: I'd like to include it, opinions? 15:22:53 kind of a coinflip decision... 15:23:00 Zakim, mute me 15:23:00 Chimezie_Ogbuji should now be muted 15:23:16 the version without collation can be emulated with IF( ... < ... 15:23:36 LeeF: any implementors have an opinion 15:23:57 +q 15:24:12 ack pgearon 15:24:40 PROPOSED: SPARQL 1.1 Function Library includes all of the functions listed at http://lists.w3.org/Archives/Public/public-rdf-dawg/2010OctDec/0188.html except for fn:error, fn:round-half-to-even, the op:*, and fn:compare and including RAND() and RAND(X) 15:24:43 pgearon: I'd put it in, happy not to require to implementors 15:24:50 +q 15:24:56 ack pgearon 15:25:33 +1 15:25:34 might be nice 15:25:48 pgearon: what about a SHA1 function? 15:25:53 pgearon: wondering if SHA1 one should be part of the function library? 15:25:55 http://commons.apache.org/codec/apidocs/org/apache/commons/codec/digest/DigestUtils.html 15:25:55 md5 may be useful as well 15:26:05 128 bit length? 15:26:14 especially for UPDATE (e.g. inserting passwords in a rdf store) 15:26:17 LeeF: useful thing 15:26:25 q+ 15:26:29 LeeF: but not sure if we require it 15:26:32 LeeF, no. 15:26:52 kasei: thinks it's useful, but shouldn't be required. 15:26:55 q- 15:27:14 AndyS: what would it return? 15:27:46 I'd imagine you'd get out of it the ability to query for foaf:mbox_sha1sum based on an foaf:mbox value. 15:28:24 LeeF: would anybody be unhappy including SHA1? 15:28:32 sha1 only or also md5 ? 15:29:09 pgearon: send an email to the list with the proposal about SHA1 and md5 15:29:26 PROPOSED: SPARQL 1.1 Function Library includes all of the functions listed at http://lists.w3.org/Archives/Public/public-rdf-dawg/2010OctDec/0188.html except for fn:error, fn:round-half-to-even, the op:*, and fn:compare and including RAND() and RAND(X) 15:29:43 -OlivierCorby 15:29:49 LeeF: any addition to this proposal? if there is ample support we will ammend the list 15:30:08 seconded 15:30:08 seconded 15:30:13 LeeF: changes to this proposal? 15:30:23 +OlivierCorby 15:30:26 LeeF: any abstention or reject? 15:30:28 RESOLVED: SPARQL 1.1 Function Library includes all of the functions listed at http://lists.w3.org/Archives/Public/public-rdf-dawg/2010OctDec/0188.html except for fn:error, fn:round-half-to-even, the op:*, and fn:compare and including RAND() and RAND(X), no objections or abstentions 15:31:00 topic: keywords and URIs 15:31:05 LeeF: next keywords and URIs 15:32:07 LeeF: do all of these functions get their keywords in the SPARQL syntaxt and if not can we get keywords? good to have keywords for all functions? opinions? 15:32:10 +1 for keyqords 15:32:13 q+ 15:32:17 ack AxelPolleres 15:32:38 Zakim, mute me 15:32:38 bglimm should now be muted 15:33:18 AxelPolleres: we expect that implementations support for functions, strongly support for funcitons to be accessible by keywords 15:33:43 AxelPolleres, how is this different from the xsd constructor functions we already require but don't have keywords? 15:33:52 q? 15:33:53 Some possible names: http://lists.w3.org/Archives/Public/public-rdf-dawg/2010OctDec/0283.html 15:33:53 LeeF: SPARQL users do not realize of all the functions they have available 15:35:03 LeeF: Axel is in favor, Kasei has objections 15:35:06 Yes - I'd put in names as per emaikl (not DateTime ones 'cos I can't think of names) 15:35:13 http://lists.w3.org/Archives/Public/public-rdf-dawg/2010OctDec/0283.html 15:35:22 +q 15:35:28 ack pgearon 15:35:43 pgearon: rather not include a particular prefix 15:35:57 pgearon: just say date, day 15:36:16 pgearon: it should be common for all queries 15:36:31 LeeF: not in favor 15:36:36 pgearon, like virtuoso's bif: prefix? 15:36:51 +1 to LeeF - principle is URIs - else keywords 15:37:31 implicit prefixes need some more things to define... although I am not strongly opposing that, that would cost more time to agree than we have, I am afraid... keywords are the shorter route, it seems 15:37:58 LeeF: any other proposal? 15:38:11 I'd support keywords for everything for simplicity as long as the keywords remain \w+ (with no dashes, underscores) including dateTime functions. 15:38:14 Zakim, unmute me 15:38:14 Chimezie_Ogbuji should no longer be muted 15:38:21 the keywords would just be the function names with fn: stripped off. 15:38:36 chimezie: any criteria on whihc functions have keywords? 15:38:41 Axel - see email - not quite. 15:38:55 LeeF: multiword ones 15:39:25 CamelCase? 15:39:41 possible dateTime functions without multiwords: YEAR(), MONTH(), DAY(), HOURS(), MINUTES(), SECONDS(), TIMEZONE() 15:40:08 +1 to kasei's, sounds fine to me 15:40:13 straw poll: (1) keywords as per AndyS's mail (excludes date time functions) (2) keywords for all (some keywords not yet specified anywhere) 15:40:26 1 15:40:28 LeeF: strawpoll, two choices 1- keywords as per AndyS 2- keywords for all some not specified anywhere 15:40:31 2 ... kasei's proposal on IRC seems just fine 15:40:34 0 can't decide 15:40:42 0 15:40:44 0 15:40:44 0 - don't care 15:40:47 0 15:40:53 2 15:41:09 0 - neutral after this discussion 15:41:11 2 15:41:15 0 15:41:17 1 15:41:20 0 15:41:53 OlivierCorby: maybe we align with xquery 15:42:15 In xquery, I can use the fn: functions without prefix, BTW. 15:42:25 OlivierCorby: problem: introducing more and more keyword, maybe to align to xquery 15:43:36 LeeF: slight preference to include keywords for all of this 15:43:43 ?? Xquery uses base URI resolution to make URIs of name without ":" 15:44:21 PROPOSED: SPARQL 1.1 includes keywords for all functionsin function library, as per suggestions in http://lists.w3.org/Archives/Public/public-rdf-dawg/2010OctDec/0283.html and using YEAR, MONTH, DAY, HOURS, MINUTES, SECONDS, TIMEZONE for the date time accessor functions 15:44:45 PROPOSED: SPARQL 1.1 includes keywords for all functionsin function library, as per suggestions in http://lists.w3.org/Archives/Public/public-rdf-dawg/2010OctDec/0283.html and using YEAR, MONTH, DAY, HOURS, MINUTES, SECONDS, TIMEZONE for the date time accessor functions and RAND 15:44:56 seconded 15:45:24 RESOLVED: SPARQL 1.1 includes keywords for all functionsin function library, as per suggestions in http://lists.w3.org/Archives/Public/public-rdf-dawg/2010OctDec/0283.html and using YEAR, MONTH, DAY, HOURS, MINUTES, SECONDS, TIMEZONE for the date time accessor functions and RAND 15:45:25 LeeF: anybody objects or abstain? 15:45:33 yay 15:46:03 no, but we've recently got this: http://www.w3.org/ns/sparql# 15:46:04 http://lists.w3.org/Archives/Public/public-rdf-dawg/2010OctDec/0283.html 15:46:06 LeeF: what URIs to use? SPARQL 1.0 has well defined URIs? 15:46:12 AndyS: no 15:46:19 Andy, does Xquery say something about default for the BASE URI to fn: (... at least more than one XQuery processr I played around with did that)? 15:46:56 AndyS: all SPARQL 1.0 in SPARQL 1.1 with their own namespace 15:47:34 Axel - would need to check the details for XQ formal spec. 15:47:36 zakim, who's talking? 15:47:46 LeeF, listening for 10 seconds I heard sound from the following: LeeF (80%), Sandro (84%) 15:47:47 Zakim, mute me 15:47:47 Lots of echo! 15:47:49 Chimezie_Ogbuji should now be muted 15:47:58 zakim, mute sandro please 15:47:58 Sandro should now be muted 15:48:26 http://www.w3.org/ns/sparql# 15:48:55 LeeF: use http://www.w3.org/ns/sparql# namespace for SPARQL 1.0 functions, any objection? 15:49:08 q+ to ask about mapping to F&O (can wait) 15:49:31 sandro: is that the same as service description? 15:49:38 kasei: no, not the same - similar 15:49:38 andy, hmmm, in http://www.w3.org/TR/xquery-semantics/ I didn't find anything indicating that... 15:49:43 sandro: should it be sparql-functions#? 15:49:58 Axel - try the grammar/syntax. 15:50:24 service description namespace is: http://www.w3.org/ns/sparql-service-description 15:50:33 sandro: or sparql-function# ? 15:50:46 AndyS: need prefixes also for entailment regimes, ... what else? 15:51:01 LeeF: unclear when naming aggregates 15:51:03 profiles in ent. regimes (OWL EL, RL, QL) 15:51:16 that's used in the service descriptions 15:51:45 AndyS: put all service descriptions in one wikipage 15:51:51 AndyS: all prefixes 15:51:51 AndyS: Can someone pull namespace issues together in one place? 15:51:59 we have yet another namespace for ent-regiems, BTW, right? 15:52:13 kasei: I can try to sumarize 15:52:37 items that need URIs and which namespace we currently use. 15:52:51 ACTION: Greg to summarize what items we need URIs for and what URI prefixes we're currently using 15:52:51 Created ACTION-338 - Summarize what items we need URIs for and what URI prefixes we're currently using [on Gregory Williams - due 2010-12-07]. 15:53:25 PROPOSED: All SPARQL 1.0 and SPARQL 1.1 functions have URIs in a SPARQL-owned namespace to be determined 15:54:03 q- 15:54:17 +1 LeeF 15:54:32 q+ 15:54:33 LeeF: any objection 15:54:37 ack kasei 15:54:49 LeeF: Simplist to have all functions in one space 15:55:26 +1 15:55:26 FYI: Can call aggs by URI currently 15:55:30 RESOLVED: All SPARQL 1.0 and SPARQL 1.1 functions have URIs in a SPARQL-owned namespace to be determined 15:56:22 LeeF: remaining issues, simple literal, access string stuff 15:56:42 LeeF: remaining: string concatenation 15:56:50 LeeF: latests proposals from AndyS 15:56:54 http://lists.w3.org/Archives/Public/public-rdf-dawg/2010OctDec/0283.html -- has a proposal for how to handle simple literals, xsd:strings, and language tags in concat 15:57:00 If we have CONCAT, I'm happy to drop overloading "+" 15:57:13 http://lists.w3.org/Archives/Public/public-rdf-dawg/2010OctDec/0302.html - proposes not to require overloading + for concatenation 15:57:24 "CONCAT("a"^^xsd:string, "b") -> "ab"^^xsd:string (?? choice point)" ... 15:57:45 the coin flip is basically whetherr to default to return type plain lit, or string, isn't it? 15:57:50 LeeF: people to catch up in the mail threads, comments please 15:58:48 bye 15:58:50 -Chimezie_Ogbuji 15:58:51 -LeeF 15:58:51 -MattPerry 15:58:51 bye 15:58:52 -AxelPolleres 15:58:53 -AlexPassant 15:58:56 -bglimm 15:58:57 \quit 15:58:57 -Sandro 15:58:57 -pgearon 15:58:58 -OlivierCorby 15:58:59 -AndyS 15:59:01 -NicoM 15:59:05 -cbuilara 15:59:07 -NickH 15:59:09 -kasei 15:59:11 SW_(SPARQL)10:00AM has ended 15:59:13 Attendees were cbuilara, +1.617.553.aaaa, LeeF, AndyS, kasei, NickH, +49.911.973.4.aabb, NicoM, OlivierCorby, MattPerry, AxelPolleres, +1.540.841.aadd, Sandro, bglimm, pgearon, 15:59:16 ... AlexPassant, Chimezie_Ogbuji 16:00:22 OlivierCorby has left #sparql 16:12:15 cbuilara has joined #sparql 16:16:24 AxelPolleres_ has joined #sparql 16:59:17 SUBSTRING or SUBSTR? (we have STR) 17:09:58 LENGTH or STRLEN ? Put STR* on all string functions (except SUBSTR...) 17:14:57 STRLEN seems to avoid confusion with LENGTH of list, seq, path, etc 17:15:01 kasei 17:20:24 pgearon_ has joined #sparql 17:21:02 CONTAINS might also be confusing but alts aren't nice. STRCONTAINS is a bit long. 17:23:22 CEIL vs CEILING? 17:25:45 AndyS? 17:26:08 agree STRCONTAINS feels long. 17:26:17 I'm happy with CEIL. 17:26:40 Could go either way on SUBSTR(ING) and LENGTH/STRLEN. 17:28:14 CEIL then 17:28:20 LENGTH is now looking scary (= trouble causing :-) given lists, seq, bag 17:28:46 CONTAINS is sort-of OK. More stringish than listish (member, index) 17:30:57 if you're worried about it, let's do STRLEN then. 17:31:55 I'm not a huge fan, but I agree it might be confused with list/seq ops. 17:33:35 Maybe its because I was thinking about the path comment I need to reply to. 17:36:32 not sure if you've got any of these implemented in arq, but was hoping you might take a look at the function tests I committed at some point. 17:37:28 as for string ops, I think I'm leaning towards xsd:string if all args are xsd:string, and similarly for language tags. dropping back to simple literals otherwise (no errors as long as the args are literals). 17:52:50 I have just found I do have most of them -- didn't realise I'd added fn:XYZ versions before. My versions are all simple literal returning but will add xsd:string, lang versions to follow eventual WG decision. 17:53:24 ARQ also has xsd:date and xsd:g*. 17:55:07 Tricky case: starts("foo"@en, "f") :: I say arg must be pure characters -> simple + xsd:string only. Avoid ss and ß 17:58:51 Zakim has left #sparql 17:58:53 both args must be just chars? 17:59:00 that is a good (tricky) case 17:59:05 any notion of why fn:year-from-dateTime doesn't return a xsd:gYear? 17:59:31 brb 18:06:13 cbuilara has left #sparql 18:15:37 Because then you need "get the year as a number" from xsd:gyear? Symmetry with other suggests number. 18:16:19 Opps - dajobe not going to be keen on todays decisions :-) 18:16:31 yeah, I know 18:16:55 when I write it up for the namespace(s) page, should I list LENGTH or STRLEN? 18:20:05 STRLEN 18:30:22 http://www.w3.org/2009/sparql/wiki/SPARQL_Namespaces 18:30:44 yikes. written out like that, it really does look like a lot of new keywords. 18:39:41 that's odd 18:39:52 isBlank is missing from the SPARQL 1.0 keywords table. 18:41:08 ah. i see it's been added ot the 1.1 draft. 18:41:48 Was going to remove some duplication - there's more than one list of keywords. 18:42:32 oh, really? 18:48:02 i wonder how much use fn:timezone-from-dateTime gets. 18:49:17 seems like the odd one out for inclusion in sparql. easy enough to implement, but a rather odd return value unless you natively support durations. 19:11:31 Maybe a different return for SPARQL? String (to cover Z) 19:14:14 pgearon_ has joined #sparql 19:15:57 Anyone know what's the state of python, ruby, (insert lang here) for SPARQL 1.1? 19:26:47 only that redland has partial support and there are bindings for most of those languages... 19:26:59 and there's excellent support in perl :)