13:56:01 RRSAgent has joined #sparql 13:56:01 logging to http://www.w3.org/2011/04/05-sparql-irc 13:56:01 trackbot, start meeting 13:56:03 RRSAgent, make logs world 13:56:05 Zakim, this will be 77277 13:56:05 ok, trackbot; I see SW_(SPARQL)10:00AM scheduled to start in 4 minutes 13:56:06 Meeting: SPARQL Working Group Teleconference 13:56:06 Date: 05 April 2011 13:56:14 trackbot, close ACTION-353 13:56:14 ACTION-353 Update the comments table on the wiki and approach people for drafting responses closed 13:56:19 zakim, this will be SPARQL 13:56:19 ok, LeeF; I see SW_(SPARQL)10:00AM scheduled to start in 4 minutes 13:56:48 SW_(SPARQL)10:00AM has now started 13:56:54 +??P2 13:57:01 Zakim, ??P2 is me 13:57:01 +SteveH; got it 13:57:03 +??P3 13:57:26 zakim, ??P3 is me 13:57:26 +AndyS; got it 13:57:34 zakim, who is on the phone? 13:57:34 On the phone I see SteveH, AndyS 13:57:44 MattPerry has joined #sparql 13:58:40 + +1.310.729.aaaa 13:58:45 Zakim, aaaa is me 13:58:45 +kasei; got it 13:58:46 +LeeF 13:59:53 +MattPerry 14:02:30 bglimm has joined #sparql 14:02:33 scribenick: kasei 14:03:06 zakim, who's on the phone? 14:03:06 +Sandro 14:03:08 On the phone I see SteveH, AndyS, kasei, LeeF, MattPerry, Sandro 14:03:41 + +41.86.528.aabb 14:03:51 topic: Admin 14:03:55 PROPOSED: Approve minutes at http://www.w3.org/2009/sparql/meeting/2011-03-29 14:04:01 Zakim, +41.86.528.aabb is me 14:04:02 +bglimm; got it 14:04:30 RESOLVED: Approve minutes at http://www.w3.org/2009/sparql/meeting/2011-03-29 14:04:40 Zakim, mute me 14:04:40 bglimm should now be muted 14:04:49 Regrets: Chime, Axel, Alex, Carlos, Olivier 14:05:02 Next regular meeting: 2011-04-12 @ 15:00 UK / 10:00 EST (scribe: Axel or Alex) 14:05:24 +pgearon 14:05:27 My regrets for next week. 14:05:27 +Souri_ 14:05:34 Souri has joined #sparql 14:05:37 I'm at risk for next week 14:05:57 LeeF: new comments. one from last friday. 14:06:22 scribe: sandro 14:06:23 ... about response codes for protocol. is 204 acceptable in case where there is no content returned? 14:09:19 204 means empty entity -- we do return an entity for an empty results table in SELECT. No "semantic" level meaning. it also means "no change of focus." unlike 200 14:09:57 zakim, agenda? 14:09:57 I see nothing on the agenda 14:10:08 sandro has changed the topic to: agenda: http://www.w3.org/2009/sparql/wiki/Agenda-2011-04-05 14:10:21 Agenda: http://www.w3.org/2009/sparql/wiki/Agenda-2011-04-05 14:10:31 SteveH: There's a bit of the Algebra I still need to look at. Very short on time, though. 14:11:03 Lee: Steve, there are some Aggregrate-related comments for you, too... Maybe you can look at them at the same time. 14:12:04 AndyS: Lee, are you still going to do your action? 14:12:12 Lee: I'm not sure, but I hope to. 14:12:44 close ACTION-409 14:12:45 ACTION-409 Edit Update document to note that blank nodes in DELETE templates are an error closed 14:12:46 Lee: Paul, has Update Doc been updated to reflect blank nodes being prohibited in templates? 14:12:53 Paul: Yes. 14:13:50 Lee: Greg, did we say we were ready for you to review update? 14:14:01 Greg: We did, I hope to do it this week. 14:14:17 Lee: I hope to do a large amt of work on Protocol Doc today. 14:14:44 Lee: I have an email to Chime about come outstanding comments on Graph Store Protocol doc. 14:14:45 Zakim, unmute me 14:14:45 bglimm should no longer be muted 14:14:54 Lee: We got a review from Jeff Pan, which Birte replied to. 14:15:30 bglimm: I need some clarification from Jeff, but I don't think there's anything that will need WG discussion. But we do have to discuss issues with Canonical Representation for D-Entailment. 14:15:50 Lee: Fed Query still waiting on Carlo or me to check status. 14:16:01 q+ to give an announcement 14:16:14 ack sandro 14:16:14 sandro, you wanted to give an announcement 14:16:34 sandro: New working group - provenance working group just announced 14:16:39 ... first meeting in a couple of weeks 14:16:51 ... sign up! 14:17:02 ... also government linked data working group has been sent to the Advisory Committee 14:17:25 http://www.w3.org/2011/gld/charter.html 14:17:33 http://www.w3.org/2011/prov/wiki/Main_Page 14:18:25 sandro: RDFa WG has been renamed RDF Web Applications WG, working on RDF Web Api 14:18:31 ... (re-)starting up, good time to join 14:18:47 topic: Canonicalization 14:19:20 Lee: I didn't read enough of the discussion between Birte and Bijan on this; can you summarize? 14:20:23 bglimm: XSD 1.0 canonical reprs have some problems. Decimal and integer have a bit of a contradiction. Take canon of the base type. Which alas means for int it's like 1.0, even though that's not a valid int rep! 14:20:55 bglimm: the next version is scheduled for LC in April, this month. 14:21:05 LeeF: If they really are on that schedule. 14:22:39 sandro: (tells story of OWL and RIF xsd finesse note.) 14:22:47 Lee: Should we do the same thing, Birte? 14:23:08 bglimm: Yes, I think so. Anything else -- using XSD 1.0 -- doesn't make sense. 14:23:27 Lee: It doesnt seem to help anyone to point at the defns in a broken spec. 14:23:49 Lee: I kinda think we oughta do the same thing as OWL 2 and RIF, depending on 1.1 14:24:05 Lee: ... if they don't actually move forward faster than us. 14:24:18 Lee: I think that's what we have to do. :-| 14:24:36 bglimm: That sounds right to me. 14:24:48 Lee: I don't think we need a WG decision on this. 14:25:12 AndyS: At the worst, we could lift a def'n from 1.1 just before we go to CR. 14:25:19 topic: Service URL vs. URI vs. Endpoint 14:25:24 Zakim, mute me 14:25:24 bglimm should now be muted 14:25:41 http://lists.w3.org/Archives/Public/public-rdf-dawg/2011AprJun/0000.html 14:25:45 Lee: Terminology from a comment by Bob Scanlon, on svg descr doc. 14:26:50 Lee: What is the name of the URI that services SPARQL protocol requests. "Service URL", "Service Name", "SPARQL Ends Point" (the URI at which a SPARQL protocol service listens....) 14:27:02 Lee: Greg suggested "service URI" 14:27:30 AndyS: i think the naming has to reflect the difference between the service and where you access it. 14:27:54 AndyS: Using "URI" suggests the service ... I think we need to use the word "End Point" 14:27:58 +1 End Point 14:28:10 http://www.w3.org/2009/sparql/docs/service-description-1.1/xmlspec.xml#sd-url 14:28:43 Andy is suggesting that sd:url relates the service to the service endpoint 14:28:50 LeeF, : sd:url relates the service to the service endpoint 14:29:19 q+ 14:29:24 q- 14:29:34 SERVICE 14:29:40 q+ 14:29:47 kasei: foo is an endpoint 14:29:59 ack sandro 14:31:09 sandro: is the range of sd:url a URL or a character string? 14:31:25 ... is it a literal or not? 14:31:34 sandro: In my mind, a URL is a kind of Literal. 14:31:36 kasei: it's meant to point at the endpoint, not point at the literal with a URL string 14:32:15 sandro: sd:endPoint or endPointAddress (if it's a string) 14:32:58 endpoint 14:33:09 +1 sd:endpoint 14:33:32 AndyS: i wouldn't use a capital in the middle :-) 14:33:55 Lee: I think it makes sense to call the property "endpoint" 14:34:22 kasei: Without concern for people who might be using this already, yeah, I have a mild preference for endpoint, too. 14:34:30 service-identifier sd:endpoint service-endpoint-url 14:35:17 Lee: where service-endpoint-url is a non-Literal Resource. 14:35:47 (mild digression about whether that could a blank node.) 14:37:24 AndyS: the endpoint is necessarily 1-1 to the endpoint URL 14:37:33 sandro: what about changes in case of the hostname? 14:38:02 AndyS: It's still 1-1 --- different case in hostname is a DIFFERENT ENDPOINT -- because you'll have a different base for your queries and responses. 14:38:17 ACTION: Greg to make sure SD terminology is consistent with "service endpoint" as the place you poke to use a (protocol) service 14:38:17 Created ACTION-432 - Make sure SD terminology is consistent with "service endpoint" as the place you poke to use a (protocol) service [on Gregory Williams - due 2011-04-12]. 14:38:31 ACTION: Lee to work with Carlos to make sure Fed terminology is consistent with "service endpoint" as the place you poke to use a (protocol) service 14:38:32 Created ACTION-433 - Work with Carlos to make sure Fed terminology is consistent with "service endpoint" as the place you poke to use a (protocol) service [on Lee Feigenbaum - due 2011-04-12]. 14:38:40 sandro: then, yeah, I guess i'm okay with endpoint's range being EndPoint, instead of URL. 14:39:14 Lee: let's change sd:url to sd:endpoint -- it'll help communitcate our view 14:39:26 sandro: sd:endpoint range sd:Endpoint ? 14:39:39 kasei: That's not the sort of thing we currently do. 14:39:57 topic: RDF dataset merge 14:40:06 sandro, I'll think over that... 14:40:44 Lee: RDF-WG discussion - what does it mean to merge datasets? 14:41:08 AndyS: putting the defns side by side 14:41:22 LeeF: Would that change any semantics, or is this just editorial? 14:41:37 AndyS: I wouldn't use the word merging. 14:41:50 AndyS: Union affects graph store. 14:42:04 AndyS: ... around handling of bnodes, in a way that doesnt apply in query. 14:42:37 LeeF: My main concern was that since our specs dont use Merge, we'd be including text we dont need, that's not right for RDF-WG. 14:43:08 AndyS: Normally I'd agree, but I can't think of another defn of RDF Merge that would work with the definitions we have. 14:43:55 Lee: I'm hearing that we use RDF datasets, and given how we define them, there's really only one way to merge them. And then RDF-WG can use SPARQL Datasets, or something else if they don't like our merge. 14:44:46 sandro: Maybe ask RDF-WG to look at this at their F2F next week. 14:45:10 Lee: Andy, can you put it in SPARQL Query, and I'll raise it to RDF-WG? 14:45:30 ACTION: Andy to add RDF Dataset merge definition to Query document 14:45:31 Created ACTION-434 - Add RDF Dataset merge definition to Query document [on Andy Seaborne - due 2011-04-12]. 14:45:40 ACTION: Lee to ping RDF WG about RDF Dataset Merge definition once in place 14:45:40 Created ACTION-435 - Ping RDF WG about RDF Dataset Merge definition once in place [on Lee Feigenbaum - due 2011-04-12]. 14:45:52 topic: tests 14:45:58 subtopic: property path tests 14:46:29 LeeF: a bug was found.... 14:46:42 http://www.w3.org/2009/sparql/docs/tests/data-sparql11/property-path/ 14:46:57 :pp29 in http://www.w3.org/2009/sparql/docs/tests/data-sparql11/property-path/manifest.ttl 14:47:07 path-3-4.rq 14:47:12 data-diamond-loop.ttl 14:47:45 :p{2,} 14:47:59 AndyS: If you look at that query, the core of it is :p{2,} 14:48:04 a -> b -> z a -> c -> z c -> c 14:48:14 ... part of it is an unbounded operation 14:48:27 ... they don't behave the same in how they treat cardinalities 14:48:37 ... so we can't reverse the operation 14:48:54 diamond-loop-6.srx 14:48:58 ... my implementation was doing it the wrong way around. 14:49:08 c / a / a / a 14:49:17 should be 14:49:23 c / c / a / a / a 14:49:35 AndyS: Correct result is c / c / a / a / a 14:50:38 Lee: I'm updating srx file now. 14:51:00 http://www.w3.org/2009/sparql/docs/tests/data-sparql11/property-path/diamond-loop-6.srx 14:52:03 Zakim, list attendees 14:52:03 As of this point the attendees have been SteveH, AndyS, +1.310.729.aaaa, kasei, LeeF, MattPerry, Sandro, bglimm, pgearon, Souri_ 14:52:43 kasei: I havent looked at 34 or 35, but I have passed them. 14:52:49 lee: that's good enough, I think. 14:52:56 PROPOSED: Re-approve :pp29 with change made in this teleconference and approve :pp34 and :pp35 14:53:07 seconded 14:53:18 RESOLVED: Re-approve :pp29 with change made in this teleconference and approve :pp34 and :pp35 14:54:41 PROPOSED: Approve all of the tests in syntax-query, syntax-update-1, syntax-update-2 14:54:47 +1 14:54:58 RESOLVED: Approve all of the tests in syntax-query, syntax-update-1, syntax-update-2 14:55:07 ACTION: Lee to mark property path and syntax tests as approved 14:55:07 Created ACTION-436 - Mark property path and syntax tests as approved [on Lee Feigenbaum - due 2011-04-12]. 14:55:59 ADJOURN 14:56:02 bye 14:56:03 54, 52, 1 tests 14:56:04 bye 14:56:04 -Sandro 14:56:06 -LeeF 14:56:06 -AndyS 14:56:07 -bglimm 14:56:07 -SteveH 14:56:11 -kasei 14:56:18 -pgearon 14:56:20 -MattPerry 14:56:53 LeeF, are you going to update the test manifests to mark approved tests? 15:10:25 kasei, yes, I will 15:11:01 sandro, do you want to do the commonscribe stuff or would you like me to? 15:11:38 LeeF, I think I did it. 15:11:45 (on another call right now) 15:14:48 http://www.w3.org/2009/sparql/meeting/2011-04-05 looks good, sandro, thanks 15:28:02 -Souri_ 15:28:03 SW_(SPARQL)10:00AM has ended 15:28:05 Attendees were SteveH, AndyS, +1.310.729.aaaa, kasei, LeeF, MattPerry, Sandro, bglimm, pgearon, Souri_ 15:31:21 kasei, I've checked in updated manifests with everything marked approved 15:31:27 trackbot, close ACTION-436 15:31:27 ACTION-436 Mark property path and syntax tests as approved closed 15:32:44 thanks LeeF 15:33:13 I've also just committed the sd doc with the updated sd:endpoint (ACTION 432) 15:35:01 oh. I had "is a URI reference" in the SD RDF, but it seems it was missing in the document. think that might satisfy sandro? 15:45:28 pgearon has joined #sparql 15:56:29 kasei, can't speak for sandro but it does the trick for me :) 15:57:24 not sure why it disappeared from the doc text, but I'll add it back in. 15:57:33 kills me that there's no way to represent that in the RDF, though. 16:24:57 SteveH has joined #sparql 16:25:57 aye, me too 17:08:03 trackbot, close ACTION-434 please 17:08:03 Sorry, AndyS, I don't understand 'trackbot, close ACTION-434 please'. Please refer to http://www.w3.org/2005/06/tracker/irc for help 17:08:14 trackbot, close ACTION-434 17:08:14 ACTION-434 Add RDF Dataset merge definition to Query document closed 17:08:30 (Never be nice to bots.) 17:16:52 karl has joined #sparql 17:18:11 Zakim has left #sparql 17:26:53 ACTION-435? 17:26:53 ACTION-435 -- Lee Feigenbaum to ping RDF WG about RDF Dataset Merge definition once in place -- due 2011-04-12 -- OPEN 17:26:53 http://www.w3.org/2009/sparql/track/actions/435 17:27:02 trackbot, close ACTION-435 17:27:02 ACTION-435 Ping RDF WG about RDF Dataset Merge definition once in place closed