Re: query your API

hello all.

On 10 Dec 2012, at 06:54, "Roger Menday" <roger.menday@uk.fujitsu.com<mailto:roger.menday@uk.fujitsu.com>> wrote:
On 10 Dec 2012, at 13:19, Andy Seaborne wrote:
Query is something coming from read-only Linked Data (well, with SPARQL 1.0 anyway), and, so, it is something we can simply assume for LDP ... However, I noticed that "retrieve resource description" is on the use-cases list, and so maybe it is a good idea to also be explicit about 'Query your API' in the UC&R doc ...
Roger - what in your mind is the scope of the query ?
That's a good question. not sure. boundaries of the service ..? the graph on the system where the root resource of the service is hosted ? Then: what really is the definition of service ? after all, once something is linked this expands the surface of the service ?
related point: how do service consumers discover a "well known" root resource in LDP?

should i add this to ISSUE-37? atompub uses its own service document as the starting point, or there's http://tools.ietf.org/html/draft-nottingham-json-home-02 as a generic way of exposing information about starting points of a REST service.

... Query the RDF graph that describes a resource
... Query something that returns a list of resources that match a condition
... Query an RDF graph, or RDF dataset, that is all RDF in this LDP instance
... Query a containers and it's contained resources (graph? dataset?)
...  and there probably other units (container that is automatically all
resources matching some pattern).

we had some agreement that we cannot depend on LDP being implemented on top of a SPARQL-capable back-end. which means that any generic SPARQL capabilities are not possible. instead, we need LDP-specific query capabilities, specifying queries of the LDP model.

cheers,

dret.