13:32:36 RRSAgent has joined #sparql 13:32:36 logging to http://www.w3.org/2010/08/17-sparql-irc 13:32:42 Zakim has joined #sparql 13:45:37 OlivierCorby has joined #sparql 13:54:09 bglimm has joined #sparql 13:55:05 NicoM has joined #sparql 13:56:27 AlexPassant has joined #sparql 13:57:01 SteveH__ has joined #sparql 13:58:10 trackbot, start meeting 13:58:12 RRSAgent, make logs world 13:58:14 Zakim, this will be 77277 13:58:14 ok, trackbot; I see SW_(SPARQL)10:00AM scheduled to start in 2 minutes 13:58:15 Meeting: SPARQL Working Group Teleconference 13:58:16 Date: 17 August 2010 13:59:20 Zakim, I am here. Why don't you get that? 13:59:21 I don't understand your question, bglimm. 13:59:31 heh 14:00:00 MattPerry has joined #sparql 14:00:02 Zakim, who's here? 14:00:02 SW_(SPARQL)10:00AM has not yet started, kasei 14:00:03 On IRC I see MattPerry, SteveH, AlexPassant, NicoM, bglimm, OlivierCorby, Zakim, RRSAgent, AxelPolleres, LeeF, karl, kasei, pgearon, iv_an_ru, sandro, trackbot 14:00:15 Zakim, who is on the phone? 14:00:15 SW_(SPARQL)10:00AM has not yet started, AxelPolleres 14:00:18 On IRC I see MattPerry, SteveH, AlexPassant, NicoM, bglimm, OlivierCorby, Zakim, RRSAgent, AxelPolleres, LeeF, karl, kasei, pgearon, iv_an_ru, sandro, trackbot 14:00:19 What a crap. First Zakim does not recognize that I have called and not all circuits are busy! 14:00:30 bglimm, ah, I jsut beat you I guess 14:00:39 Sandro, Ivan, any chance that this will be fixed any time soon? 14:00:48 Zakim, who is on the phone? 14:00:48 SW_(SPARQL)10:00AM has not yet started, AxelPolleres 14:00:49 On IRC I see MattPerry, SteveH, AlexPassant, NicoM, bglimm, OlivierCorby, Zakim, RRSAgent, AxelPolleres, LeeF, karl, kasei, pgearon, iv_an_ru, sandro, trackbot 14:01:00 Zakim, this is SPARQL 14:01:00 ok, AxelPolleres; that matches SW_(SPARQL)10:00AM 14:01:11 Zakim, who is on the phone? 14:01:11 On the phone I see kasei, AxelPolleres, +44.208.439.aacc, +49.911.973.4.aadd, +33.4.92.38.aaee 14:01:17 Souri has joined #sparql 14:01:28 Zakim, aacc is [Garlik] 14:01:29 +[Garlik]; got it 14:01:33 + +44.186.528.aaff 14:01:36 Yes, SteveH, but I dialed in twice before and Zakim just did not recognise that 14:01:38 Zakim, [Garlik] is temporarily me 14:01:38 +SteveH; got it 14:01:43 Zakim, aaee is me 14:01:43 +OlivierCorby; got it 14:01:44 + +1.603.897.aagg 14:01:45 Zakim, +44.186.528.aaff is me 14:01:46 +bglimm; got it 14:01:51 + +1.603.897.aahh 14:01:54 now calling via France 14:01:55 zakim, aagg is me 14:01:55 +MattPerry; got it 14:01:55 Zakim, who is on the phone? 14:01:58 On the phone I see kasei, AxelPolleres, SteveH, +49.911.973.4.aadd, OlivierCorby, bglimm, MattPerry, +1.603.897.aahh 14:02:01 zakim, aahh is me 14:02:03 +Souri; got it 14:02:03 Zakim, +49.9 is me 14:02:05 +NicoM; got it 14:02:09 bglimm, are you using the London number? the other one doesn't work at all, as far as I can see 14:02:23 scribe: OlivierCorby 14:02:27 +44.203.318.0479 that's what I use 14:02:33 As in the agenda 14:02:35 agenda: http://www.w3.org/2009/sparql/wiki/Agenda-2010-08-17 14:02:49 bglimm, yeah. that's the one I connected on 14:02:53 Zakim, who is talking? 14:03:00 very loud 14:03:00 Zakim, mute me 14:03:00 bglimm should now be muted 14:03:01 regrets: Nicholas Humfrey, AndyS 14:03:04 kasei, listening for 10 seconds I heard sound from the following: AxelPolleres (33%), bglimm (50%) 14:03:19 I just muted, I think I have a noisy line 14:03:47 chimezie has joined #sparql 14:04:31 +Sandro 14:04:42 +Chimezie_Ogbuji 14:04:44 PROPOSED: Approve minutes at http://www.w3.org/2009/sparql/meeting/2010-08-10 14:05:13 +pgearon 14:05:16 RESOLVED: Approve minutes at http://www.w3.org/2009/sparql/meeting/2010-08-10 14:05:40 topic: comment by TBL 14:05:44 + +1.617.245.aaii 14:05:49 http://lists.w3.org/Archives/Public/public-rdf-dawg-comments/2010Aug/0004.html 14:05:51 +??P34 14:05:53 Zakim, ??P34 is me 14:05:53 +AlexPassant; got it 14:06:30 http://lists.w3.org/Archives/Public/public-rdf-dawg/2010JulSep/0227.html 14:07:31 1st point about linked data 14:07:51 Should we take these one at a time for group discussion? 14:08:21 lee, yup, let'chime summarise first 14:09:59 k 14:10:27 1) One point is that, mostly, this is a book about how to implement a 14:10:27 linked data when you have an existing SPARQL server. This is clearly a good idea.. 14:10:27 That could be expressed in the abstract. 14:11:42 Chime: how can we refere to LinkedData /design issues doc... since it's not a spec 14:11:57 Relevance of linked data wrt to this doc ? 14:12:14 I don't personsally share Tim's view, but I also don't have any objections to this view (so yeah, I agree with Chime and Axel) 14:12:51 I view it as a lightweight, higly portable way to work with RDF data, that's it 14:12:58 s/higly/highly 14:13:26 ACTION: chime to add a statement reflecting TL-1 point 1) in the http-rdf-update 14:13:26 Created ACTION-294 - Add a statement reflecting TL-1 point 1) in the http-rdf-update [on Chimezie Ogbuji - due 2010-08-24]. 14:13:49 (BTW, my regrets next week - on vacation) 14:14:27 2. direct vs indirect graph manipulation 14:14:49 "I would prefer 4.2 be couched as "Graph Mirroring". This echoes the way many web sites 14:14:49 (and FTP sites) mirror another's contents, and may even provide enhanced access, while not being authoritative. 14:14:49 " 14:15:59 Axel: Graph Mirroring is a use case, but not the only one, we should make that clear in the response. 14:16:29 Chime: hostname/authority was maybe not clear, maybe just needs some rewording 14:16:30 ".. it is often the case (with HTTP graph URIs in particular) that the server associated with the hostname is not the same as the server managing the identified RDF knowledge (as a result of a change in domain name ownership, for instance), the host server is not available, or the URI is not dereferencable" 14:17:58 Chime: general tenor of the mail, is that Tim unerstand the whole document as one use case we have in mind. 14:18:27 sandro: maybe easier, if we respond and try to find some concrete suggestions we can take on board. 14:19:13 "I'd note that it may be useful to have a way of saying that. A simple P label could do." 14:19:42 this sentence not really understandable, maybe ask for clarification. 14:20:21 "so instead of 14:20:21 http://example.com/rdf-graphs/employees?graph=http%3A//www.example.org/other/graph 14:20:22 why not 14:20:22 http://example.com/rdf-graphs/www.example.org/other/graph 14:20:22 or 14:20:22 http://example.com/rdf-graphs/employees/other/graph 14:20:24 " 14:20:36 we need the http/https/urn scheme in there I think 14:21:06 Should we mention both alternatives? I.e. explicityle ecourage masking 14:21:06 the "?" URIs and adding a section that explains why that might be 14:21:07 useful? 14:21:21 I'd like to see ? as an option 14:21:38 +1 pgearon 14:21:46 yeah 14:21:47 tim wrote: "A rewrite rule on the server can of course turn this into the "?" form internally and the CGI apparatus fired up as a result." 14:22:28 Many implementations are servlet based, and ? is much easier there 14:22:29 rewrite rules aren't that bothered about ?s 14:22:43 pgearon, really? even with PUT? 14:22:50 for non static graphs, having proxies not cache anything may be a good thing 14:23:11 are proxies that don't cache ? URIs behaving as per spec or are they being naughty? 14:23:16 Axel: Should we explicitly mention the rewrite option in the doc? 14:23:18 SteveH: for me, sure. I'd expect that JS based implementations would prefer ? as well 14:23:26 Chime: wouldn't hurt, can think aobut some text. 14:23:37 pgearon, not really, you have to write your own parser either way 14:25:03 points 4) 5) ... 14:25:56 chime: maybe we should ask back for clarification whether there's specific text he had in mind. 14:26:05 sandroL: quicker if we propose text 14:26:09 chime: ok 14:27:31 "...that THE DEFAULT GRAPH OF THE QUERY IS THE ONE IN THE HTTP REQUEST. 14:27:31 Obvious really, but people can miss it." 14:28:52 chime: last TC we need to clarify protocol interaction in general. we can put that in the response 14:29:00 ... ongoing issue 14:29:37 Axel: last point 6) on MS-Author-Via header 14:29:57 Chime: some idea, but not sure what he had in mind 14:30:06 ... ask back for clarification. 14:30:36 ACTION: Chime to draft response for TL-1 14:30:36 Created ACTION-295 - Draft response for TL-1 [on Chimezie Ogbuji - due 2010-08-24]. 14:31:44 - +1.617.245.aaii 14:31:53 topic: issues to be postponed 14:32:58 http://www.w3.org/2001/sw/DataAccess/issues 14:34:06 yes, it was stuff that was left over 14:34:10 we did it by hand IIRC 14:34:16 by we, I mean other people :) 14:34:26 Zakim, mute me 14:34:26 Chimezie_Ogbuji should now be muted 14:35:14 +Lee_Feigenbaum 14:35:24 "alternative limit per resource" http://lists.w3.org/Archives/Public/public-rdf-dawg/2010JulSep/0194.html 14:35:28 the issues list was very much done by hand 14:35:38 zakim, huh? 14:35:38 I don't understand your question, LeeF. 14:35:43 the issues list was very much done by hand 14:36:47 +1 for not touching it right now 14:36:51 ISSUE: Treatment of "alternative limit per resource" http://lists.w3.org/Archives/Public/public-rdf-dawg/2010JulSep/0194.html 14:36:51 Created ISSUE-61 - Treatment of "alternative limit per resource" http://lists.w3.org/Archives/Public/public-rdf-dawg/2010JulSep/0194.html ; please complete additional details at http://www.w3.org/2009/sparql/track/issues/61/edit . 14:37:29 query syntax for algebra operators http://lists.w3.org/Archives/Public/public-rdf-dawg/2010JulSep/0193.html 14:38:12 ISSUE: shall there be more concise query syntax for all algebra operators http://lists.w3.org/Archives/Public/public-rdf-dawg/2010JulSep/0193.html 14:38:12 Created ISSUE-62 - Shall there be more concise query syntax for all algebra operators http://lists.w3.org/Archives/Public/public-rdf-dawg/2010JulSep/0193.html ; please complete additional details at http://www.w3.org/2009/sparql/track/issues/62/edit . 14:38:52 axel: ISSUE-62 related to the open issue around assignment. 14:39:55 why are these being created as ISSUES?! 14:41:14 SteveH, perhaps AxelPolleres means that it's a known limitation of the language? 14:42:29 PROPOSED: close ISSUE-61 with the understanding that we leave treatment of such queries for a coming WG 14:44:49 PROPOSED: close ISSUE-61 and ISSUE-62 with the understanding that this is out of scope of the current WG 14:45:01 close ISSUE-61 14:45:01 ISSUE-61 Treatment of "alternative limit per resource" http://lists.w3.org/Archives/Public/public-rdf-dawg/2010JulSep/0194.html closed 14:45:10 close ISSUE-62 14:45:10 ISSUE-62 Shall there be more concise query syntax for all algebra operators http://lists.w3.org/Archives/Public/public-rdf-dawg/2010JulSep/0193.html closed 14:45:41 +q 14:45:49 q- 14:46:49 Axel: so, postponed issue will only be those which we really can't close. 14:47:02 .... this way we don't put any burden to a future WG. 14:47:53 topic: mark SPARQL update member submission 14:49:29 Axel: sandro, can we add a disclaimer on the member submission? 14:49:53 Sandro: as long as we check with submitters, and find sensible wording, that should be fine. 14:50:33 Axel: What we're looking for is a text similar to the OWL1 docs... 14:51:02 I wrote a simple proposal on the list 14:51:42 just need to s/Wroking Draft/REC when we switch to rec. 14:51:43 Sandro: Alex' wording needs to be updates, that would be a problem 14:51:49 but I'm open to other proposals 14:52:13 ACITON SteveH to suggest a wording for a disclaimer text for the SPARQL update member submission 14:52:27 ACTION: member:SteveH to suggest a wording for a disclaimer text for the SPARQL update member submission 14:52:27 Sorry, bad ACTION syntax 14:52:45 ACTION: steveH to suggest a wording for a disclaimer text for the SPARQL update member submission 14:52:45 Created ACTION-296 - to suggest a wording for a disclaimer text for the SPARQL update member submission [on Steve Harris - due 2010-08-24]. 14:52:52 topic: AOB? 14:53:04 -Chimezie_Ogbuji 14:53:05 -Lee_Feigenbaum 14:53:06 -bglimm 14:53:06 -MattPerry 14:53:08 -AlexPassant 14:53:09 -Sandro 14:53:10 -SteveH 14:53:10 -AxelPolleres 14:53:12 -kasei 14:53:13 hearing none, adjourned 14:53:13 -OlivierCorby 14:53:24 -pgearon 14:53:27 -NicoM 14:53:37 rrsagent, make records public 14:54:02 OlivierCorby has left #sparql 14:54:12 -Souri 14:54:14 SW_(SPARQL)10:00AM has ended 14:54:16 Attendees were +44.186.528.aaaa, kasei, +44.186.528.aabb, AxelPolleres, +44.208.439.aacc, +49.911.973.4.aadd, +33.4.92.38.aaee, SteveH, OlivierCorby, +1.603.897.aagg, bglimm, 14:54:19 ... +1.603.897.aahh, MattPerry, Souri, NicoM, Sandro, Chimezie_Ogbuji, pgearon, +1.617.245.aaii, AlexPassant, Lee_Feigenbaum 15:21:37 SteveH has joined #sparql 17:08:29 AxelPolleres has left #sparql 17:13:34 Zakim has left #sparql 17:53:17 SteveH__ has joined #sparql