W3C home > Mailing lists > Public > public-ldp-wg@w3.org > December 2012

Re: query your API

From: Roger Menday <roger.menday@uk.fujitsu.com>
Date: Mon, 10 Dec 2012 14:52:30 +0000
CC: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
Message-ID: <5E8A614B-199C-4F5B-856F-EAB81C3EFFCC@uk.fujitsu.com>
To: Andy Seaborne <andy.seaborne@epimorphics.com>

On 10 Dec 2012, at 13:19, Andy Seaborne wrote:

> On 10/12/12 13:08, Roger Menday wrote:
>> Just a thought ...
>> 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 =
> 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? 


> I see different 
> options:
> ... 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).
> 	Andy

 Fujitsu Laboratories of Europe Limited
 Hayes Park Central, Hayes End Road, Hayes, Middlesex, UB4 8FE
 Registered No. 4153469
 This e-mail and any attachments are for the sole use of addressee(s) and
 may contain information which is privileged and confidential. Unauthorised
 use or copying for disclosure is strictly prohibited. The fact that this
 e-mail has been scanned by Trendmicro Interscan does not guarantee that 
 it has not been intercepted or amended nor that it is virus-free.
Received on Monday, 10 December 2012 14:53:21 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:11:42 UTC