- From: Eric Prud'hommeaux <eric@w3.org>
- Date: Tue, 13 Feb 2007 17:27:40 +0100
- To: public-rdf-dawg@w3.org
- Cc: Lee Feigenbaum <feigenbl@us.ibm.com>
- Message-ID: <20070213162740.GA8145@w3.org>
http://www.w3.org/2007/02/13-dawg-minutes [1]W3C RDF DAWG Weekly 13 Feb 2007 [2]Agenda See also: [3]IRC log Attendees Present AndyS, EliasT, Simon_Raboczi, LeeF, ericP, jeen, Orri_Erling Regrets Souri, PatH Chair LeeF Scribe ericP Contents * [4]Topics 1. [5]convene 2. [6]review action items 3. [7]test suite 4. [8]base IRI * [9]Summary of Action Items _________________________________________________________________ <SimonR> We have regrets from Souri (from previous minutes) and PatH ([10]http://lists.w3.org/Archives/Public/public-rdf-dawg/2007JanMar/00 77.html) convene RESOLUTION: accept [11]30 Jan minutes as a true record RESOLUTION: accept [12]6 Feb minutes as a true record Next Meeting: 20 Feb, scribe: EliasT review action items ACTION: [DONE] Lee to adapt text from 4.1.1 to specify how the protocol can contribute to the base IRI for query evaluation as per #relIRIs in the QL spec [recorded in [13]http://www.w3.org/2007/02/13-dawg-minutes.html#action03] ACTION: [DONE] LeeF to add Andy's bnode label scope tests to CVS as unapproved syntax tests [recorded in [14]http://www.w3.org/2007/02/13-dawg-minutes.html#action05] ACTION: [CONTINUES] AndyS to add text clarifying the prohibition on blank node labels in multiple BGPs to rq25 [recorded in [15]http://www.w3.org/2007/02/13-dawg-minutes.html#action04] ACTION: AndyS to add text clarifying the prohibition on blank node labels in multiple BGPs to rq25 [CONTINUES] [recorded in [16]http://www.w3.org/2007/02/13-dawg-minutes.html#action06] ACTION: EricP to run the yacker tool over and annotate the existing tests [CONTINUES] [recorded in [17]http://www.w3.org/2007/02/13-dawg-minutes.html#action07] ACTION: LeeF to remember that the wee, lost filter tests should be put [CONTINUES] [recorded in [18]http://www.w3.org/2007/02/13-dawg-minutes.html#action08] ACTION: Lee to talk to protocol editors re: POSTing application/sparql-query [CONTINUES] [recorded in [19]http://www.w3.org/2007/02/13-dawg-minutes.html#action09] test suite [20]Andy's blank node label tests [21]LeeF's results for these tests PROPOSED: to approve the syntax tests in data-r2/syntax-sparql4/manifest.ttl APPROVED base IRI re: base IRI and [22]rfc 3986: [23]0067 and [24]0074 LeeF: most substantial issue was the base IRI ... RFC3986 contains a series of resolution steps for base URIs ... there was text in rq?? but not in protocol LeeF: when drafting, I had a different interpretation than ericP [[ if a URI was used to retrieve the representation, that URI shall be considered the base URI ]] ... base URI should be HTTP GET with query parameters at the end ... in the SOAP/POST query, it should be just the endpoint <LeeF> Otherwise, the <LeeF> "Retrieval URI" identified in 5.1.3, Base "URI from the Retrieval URI", is <LeeF> the complete URL used to send a particular SPARQL query to a SPARQL <LeeF> protocol service implementing the SparqlQuery <LeeF> interface.Determining the Base IRI <LeeF> Relative IRIs that appear in a [SPARQL] query are resolved against a base <LeeF> IRI as per [RFC3986] section 5.1, "Establishing a Base URI". If present in <LeeF> the query, the BASE keyword defines the Base IRI used to resolve relative <LeeF> IRIs per RFC3986 section 5.1.1, "Base URI Embedded in Content". Otherwise, <LeeF> Section 5.1.2, "Base URI from the Encapsulating Entity", defines how the <LeeF> Base IRI may come from an encapsulating document, such as a SOAP envelope <LeeF> with an xml:base directive. (See 2.3 SOAP Envelope. <LeeF> If none of the above specifies the Base URI, the default Base <LeeF> URI (section 5.1.4, "Default Base URI") is used. <LeeF> (scratch that text, copy/paste issues) http://service.exmaple/SPARQL?quer=..+++++...&named="sdfd3434554654#$$ 5" WHERE { <.> ?s ?o } <http://service.exmaple/SPARQL> or <http://service.exmaple/> <EliasT> so the worry is simply if we explicitly say the endpoint URI and resolution is impacted by slashes we are in trouble. <AndyS> Only case Lee and I found was <#foo> <LeeF> [25]http://lists.w3.org/Archives/Public/public-rdf-dawg/2007JanMar/007 3.html [[ The "Retrieval URI" identified in 5.1.3, Base "URI from the Retrieval URI", is the URL from which a particular SPARQL query was retrieved. ]] <LeeF> from 1.2.2 (from Andy's email) <LeeF> [[ <LeeF> ... <LeeF> To use that access mechanism to perform an action on the <LeeF> URI's resource is to "dereference" the URI. <LeeF> When URIs are used within information retrieval systems to identify <LeeF> sources of information, the most common form of URI dereference is <LeeF> "retrieval": making use of a URI in order to retrieve a <LeeF> representation of its associated resource. <LeeF> ]] does "from which a particular SPARQL query was retrieved." contradict using http://service.exmaple/SPARQL?quer=..+++++...&named="sdfd3434554654#$$ 5" as the base? EliasT: no "from which a particular SPARQL query was retrieved. (Please note XXX in the SPARQL Protocol.)" <SimonR> Are we talking about where the query was retrieved from (e.g. an .rq file somewhere) or where the result set was retrieved from (the endpoint)? <EliasT> SimonR: both, sort of. <LeeF> SimonR, well we need the base IRI for the query... so the reading of 3986 should be the retrieval URI of the query -- but that could be either of your choices, right? <SimonR> Well, no...I'd say it would be the first. If we were being super-pedantic. <EliasT> right, but that's *if*, we currently don't support retrieving .rq queries. <LeeF> If you're processing http://example.org/sparql?query=SELECT... <LeeF> and I ask you for the retrieval URI of the query, is the correct answer "none" or "http://example.org/sparql?query=SELECT..." ? <AndyS> If there is a secondary retrive to get the query then that is the new base. c.f. <AndyS> SELECT FROM <http://example/daat <AndyS> SELECT FROM <http://example/data> which resets the base for reading the FROM <LeeF> 04 01If you're processing http://example.org/sparql?query=SELECT... <LeeF> and I ask you for the retrieval URI of the query, is the correct answer "none" or "http://example.org/sparql?query=SELECT..." ? base OR xml:base OR resolutionURI OR service-defined | service-defined is advised to default to service?mush <LeeF> [[ <LeeF> ... <LeeF> To use that access mechanism to perform an action on the <LeeF> URI's resource is to "dereference" the URI. <LeeF> When URIs are used within information retrieval systems to identify <LeeF> sources of information, the most common form of URI dereference is <LeeF> "retrieval": making use of a URI in order to retrieve a <LeeF> representation of its associated resource. <LeeF> ]] does "http://example.org/sparql?query=SELECT..." give a representation of a SPARQL query? <SimonR> +1 to extend i think rfc3986.5.1.3("http://example.org/sparql?query=SELECT...") gives a base URI for the result set <LeeF> <h20> <LeeF> <h2o> { ?chem :bondsTo <h2o> } <AndyS> also FROM <data.rdf> PROPOSED: base uri resolution in sparql protocol comes from: base OR xml:base OR resolutionURI OR service-defined where service-defined is advised to default to service?mush ... The SPARLQ Protocol does not derefrence query URIs so 5.1.3 does not apply. Per 5.1.4, services must define their own base URI, which may be the service invocation URI. ... ed(The SPARLQ Protocol does not derefrence query URIs so 5.1.3 does not apply. Per 5.1.4, services must define their own base URI, which may be the service invocation URI.) seconded by EliasT APPROVED: SimonR abstains <LeeF> ACTION: Elias to add wording for PROPOSED: ed(The SPARLQ Protocol does not derefrence query URIs so 5.1.3 does not apply. Per 5.1.4, services must define their own base URI, which may be the service invocation URI.) [recorded in [26]http://www.w3.org/2007/02/13-dawg-minutes.html#action10] LeeF: tx all for muddling through this ... tx to SimonR for review start ... all: please keep the reviews flowing <SimonR> Adjourned at 15:50 Z. Summary of Action Items [NEW] ACTION: Elias to add wording for PROPOSED: ed(The SPARLQ Protocol does not derefrence query URIs so 5.1.3 does not apply. Per 5.1.4, services must define their own base URI, which may be the service invocation URI.) [recorded in [27]http://www.w3.org/2007/02/13-dawg-minutes.html#action10] [PENDING] ACTION: AndyS to add text clarifying the prohibition on blank node labels in multiple BGPs to rq25 [recorded in [28]http://www.w3.org/2007/02/13-dawg-minutes.html#action04] [PENDING] ACTION: AndyS to add text clarifying the prohibition on blank node labels in multiple BGPs to rq25 [recorded in [29]http://www.w3.org/2007/02/13-dawg-minutes.html#action06] [PENDING] ACTION: EricP to run the yacker tool over and annotate the existing tests [recorded in [30]http://www.w3.org/2007/02/13-dawg-minutes.html#action07] [PENDING] ACTION: Lee to talk to protocol editors re: POSTing application/sparql-query [recorded in [31]http://www.w3.org/2007/02/13-dawg-minutes.html#action09] [PENDING] ACTION: LeeF to remember that the wee, lost filter tests should be put [recorded in [32]http://www.w3.org/2007/02/13-dawg-minutes.html#action08] [DONE] ACTION: Lee to adapt text from 4.1.1 to specify how the protocol can contribute to the base IRI for query evaluation as per #relIRIs in the QL spec [recorded in [33]http://www.w3.org/2007/02/13-dawg-minutes.html#action03] [DONE] ACTION: LeeF to add Andy's bnode label scope tests to CVS as unapproved syntax tests [recorded in [34]http://www.w3.org/2007/02/13-dawg-minutes.html#action05] [End of minutes] _________________________________________________________________ Minutes formatted by David Booth's [35]scribe.perl version 1.127 ([36]CVS log) $Date: 2007/02/13 16:25:41 $ References 1. http://www.w3.org/ 2. http://lists.w3.org/Archives/Public/public-rdf-dawg/2007JanMar/0075.html 3. http://www.w3.org/2007/02/13-dawg-irc 4. http://www.w3.org/2007/02/13-dawg-minutes#agenda 5. http://www.w3.org/2007/02/13-dawg-minutes#item01 6. http://www.w3.org/2007/02/13-dawg-minutes#item02 7. http://www.w3.org/2007/02/13-dawg-minutes#item03 8. http://www.w3.org/2007/02/13-dawg-minutes#item04 9. http://www.w3.org/2007/02/13-dawg-minutes#ActionSummary 10. http://lists.w3.org/Archives/Public/public-rdf-dawg/2007JanMar/0077.html) 11. http://www.w3.org/2007/01/30-dawg-minutes 12. http://www.w3.org/2007/02/06-dawg-minutes 13. http://www.w3.org/2007/02/13-dawg-minutes.html#action03 14. http://www.w3.org/2007/02/13-dawg-minutes.html#action05 15. http://www.w3.org/2007/02/13-dawg-minutes.html#action04 16. http://www.w3.org/2007/02/13-dawg-minutes.html#action06 17. http://www.w3.org/2007/02/13-dawg-minutes.html#action07 18. http://www.w3.org/2007/02/13-dawg-minutes.html#action08 19. http://www.w3.org/2007/02/13-dawg-minutes.html#action09 20. http://lists.w3.org/Archives/Public/public-rdf-dawg/2007JanMar/0068 21. http://lists.w3.org/Archives/Public/public-rdf-dawg/2007JanMar/0074 22. http://www.ietf.org/rfc/rfc3986.txt 23. http://lists.w3.org/Archives/Public/public-rdf-dawg/2007JanMar/0067.html 24. http://lists.w3.org/Archives/Public/public-rdf-dawg/2007JanMar/0074.html 25. http://lists.w3.org/Archives/Public/public-rdf-dawg/2007JanMar/0073.html 26. http://www.w3.org/2007/02/13-dawg-minutes.html#action10 27. http://www.w3.org/2007/02/13-dawg-minutes.html#action10 28. http://www.w3.org/2007/02/13-dawg-minutes.html#action04 29. http://www.w3.org/2007/02/13-dawg-minutes.html#action06 30. http://www.w3.org/2007/02/13-dawg-minutes.html#action07 31. http://www.w3.org/2007/02/13-dawg-minutes.html#action09 32. http://www.w3.org/2007/02/13-dawg-minutes.html#action08 33. http://www.w3.org/2007/02/13-dawg-minutes.html#action03 34. http://www.w3.org/2007/02/13-dawg-minutes.html#action05 35. http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm 36. http://dev.w3.org/cvsweb/2002/scribe/ -- -eric office: +1.617.258.5741 NE43-344, MIT, Cambridge, MA 02144 USA cell: +1.857.222.5741 (eric@w3.org) Feel free to forward this message to any list for any purpose other than email address distribution.
Received on Tuesday, 13 February 2007 16:27:55 UTC