- From: Leigh Dodds <leigh@ldodds.com>
- Date: Fri, 7 Dec 2012 16:12:10 +0000
- To: public-rdf-dawg-comments@w3.org
Hi, Section 2 of the SPARQL Service Description Document [1] says: "SPARQL services made available via the SPARQL Protocol should return a service description document at the service endpoint when dereferenced using the HTTP GET operation without any query parameter strings provided. This service description must be made available in an RDF serialization, may be embedded in (X)HTML by way of RDFa [RDFA], and should use content negotiation [CONNEG] if available in other RDF representations." However it doesn't recommend a *default* serialization for the description. An RDF serialization MUST be provided and several may be provided via content negotiation, but if a service is only going to support a single format, the specification doesn't recommend one. Presumanbly the intention is that RDF/XML should be the default although with Turtle being standardised an implementor might reasonably choose that instead. In practice I assume that most services will probably support multiple serializations, but I think having a recommended default would be useful. Cheers, L. [1]. http://www.w3.org/TR/sparql11-service-description/#accessing -- Leigh Dodds Freelance Technologist Open Data, Linked Data Geek t: @ldodds w: ldodds.com e: leigh@ldodds.com
Received on Friday, 7 December 2012 16:12:40 UTC