rq23 conformance section

The grammar in appendix A defines the syntax of SPARQL Queries. Apart
from extension functions, the semantics of all SPARQL Queries are
defined within this document. A query is successful if it has been
processed in accordance with the semantics defined in this
specification and the semantics specified for any invoked extension
functions. APIs or protocols (such as SPARQL Protocol for RDF [SPROT])
that define access to SPARQL processors MUST, per the definition of
"MUST" in Key Words for use in RFCs to Indicate Requirement Levels
[RFC2119], indicate which queries were successful.
Possible Reasons for Unsuccessful Queries (informative)

Following are some, but not all, reasons for a query to not be

    * Query has unsupported extension functions.
    * Query requires excessive resources to complete.
    * Some policy prevents the execution of the query.

API and Protocol specifications are not required to indicate the
reason that a query was unsuccessful.

I didn't want to require anything exotic of all SPARQL tools, like
error codes, 'cause the error code doesn't fit in the result set and,
in many 3-party queries (or any where there's no tight coupling of the
querier and the service), there's no way to write that info down. This
wording should mean that a protocol can say that if an agent finds a
results set, the query was successful. If not, it broke.


office: +81.466.49.1170 W3C, Keio Research Institute at SFC,
                        Shonan Fujisawa Campus, Keio University,
                        5322 Endo, Fujisawa, Kanagawa 252-8520
        +1.617.258.5741 NE43-344, MIT, Cambridge, MA 02144 USA
cell:   +81.90.6533.3882

Feel free to forward this message to any list for any purpose other than
email address distribution.

Received on Saturday, 12 November 2005 16:39:28 UTC