Re: SPARQL 1.1 Protocol Conformance

On 02/08/11 14:08, Lee Feigenbaum wrote:
> On 8/2/2011 8:44 AM, Andy Seaborne wrote:
>>

  Both of
> these decisions are reflected in the editor's draft at:
>
> http://www.w3.org/2009/sparql/docs/protocol-1.1/Overview2.xml

Sorry about that but I would point out that the doc is not visible.  If 
you go to docs/protocol-1.1/ you get a document "SPARQL 1.1 Protocol for 
RDF", not a directory listing.

>> So I think we should check, then if we can't get coverage, drop SOAP,
>> and if we do, drop WSDL in favor of a descriptive style. This isn't a
>> trivial change to the doc but it isn't huge either; we don't have the
>> WSDL for update yet.
>
> This has already all been done.
>
>> Operation: query
>> Parameters:
>> query .... occurs once, required ...
>> default-graph-uri ....
>> named-grap-uri=...
>> Result formats:
>> ...
>>
>> WSDL does not help the HTTP implementer; is there an alternative, more
>> widely used protocl descritption system for HTTP? Most web APIs seem to
>> have description +a table and examples.
>>
>> Not sure where 5 comes from; there are actually two variations of query,
>> implicit and explicit dataset description, +, arguably, FROM/FROM NAME
>> handling.
>
> The 5 are:
>
> query via GET (same as SPARQL 1.0)
> query via POST with URL-encoded parameters (same as SPARQL 1.0)
> query via directly POSTed query string (new for SPARQL 1.1)
> update via POST with URL-encoded parameters
> update via directly POSTed update request string
>
> Whichever of these mechanisms is implemented, it must support the full
> protocol, which includes the default-graph-uri and named-graph-uri
> parameters and their relationship with FROM/FROM NAMED/USING/USING NAMED.

Are you including "error" in "implement"?

A common usage is to publish specific dataset at an endpoint.

	Andy

>
> Lee
>
>> I am planning on reporting on HTTP, query and update and HTTP graph
>> protocol; on different endpoints. Query will be for both implicit
>> dataset and specified dataset (this latter item is recurrent request for
>> users for Fuseki which lacks the feature).
>>
>> I'm willing to help redraft the protocol doc if it's de-SOAPed.
>>
>> Andy
>>
>>>
>>> Lee
>>>
>>
>>

Received on Tuesday, 2 August 2011 13:30:46 UTC