W3C home > Mailing lists > Public > public-ldp@w3.org > March 2015

Re: GET RDF Resource

From: Magnus Knuth <magnus.knuth@hpi.uni-potsdam.de>
Date: Mon, 2 Mar 2015 15:16:06 +0100
Message-ID: <D8C93BE0-7B42-41AB-B54A-2996456556C7@hpi.uni-potsdam.de>
To: Martynas Jusevičius <martynas@graphity.org>, <public-ldp@w3.org>
Hey Martynas,

thanks for the pointer, Graphity seems to be a nice tool. But my question was actually targeting specifications, is there a specification which triples SHOULD be returned dereferencing an RDF resource, except TimBLs:

 3) When someone looks up a URI, provide useful information, using the standards

As a Linked Data consumer do I have to guess which information (from the dataset) is considered useful by the provider or are there any best practices? I am aware that this topic can be discussed very deeply, but for now I was just interested whether there is some consensus about what a resource description should contain
<R> ?p ?o triples
OR
<R> ?p ?o and ?s ?p <R> triples?
This has a major impact on consuming Linked Data. With the latter I can resolve triple patterns {?s ?p <R>} by simply dereferencing the resource’s URI, while with the first that might be impossible by dereferencing (beyond open world), i.e. something like a SPARQL endpoint is needed.

Isn't the LDP Specification or LDP Best Practices and Guidelines an appropriate place to put this?

Best
Magnus

Am 02.03.2015 um 14:33 schrieb Martynas Jusevičius <martynas@graphity.org>:

> Magnus,
> 
> non-LDP solution, but I think you should take a look at Graphity:
> https://github.com/Graphity/graphity-client
> 
> Disclaimer: I'm the main developer. Feel free to ask questions :)
> 
> Martynas
> 
> On Mon, Mar 2, 2015 at 1:47 PM, Magnus Knuth
> <magnus.knuth@hpi.uni-potsdam.de> wrote:
>> Hello,
>> 
>> reading the spec I can not find information about what content wise SHOULD to be returned upon HTTP GET on an RDF resource.
>> In the past I realized that servers return different content upon dereferencing an RDF resource, some servers return all triples where the requested resource occurs as the subject,
>> i.e. CONSTRUCT { ?s ?p ?o . } WHERE { ?s ?p ?o . FILTER (?s = <R>)}
>> others (such as DBpedia) return triples where the object occurs as subject OR object,
>> i.e. CONSTRUCT { ?s ?p ?o . } WHERE {{ ?s ?p ?o . FILTER (?s = <R>)} UNION { ?s ?p ?o . FILTER (?o = <R>)}}.
>> 
>> Are there any suggestions for that?
>> 
>> Best
>> Magnus
>> 
>> --
>> Magnus Knuth
>> 
>> Hasso-Plattner-Institut für Softwaresystemtechnik GmbH
>> Prof.-Dr.-Helmert-Str. 2-3
>> 14482 Potsdam
>> 
>> Amtsgericht Potsdam, HRB 12184
>> Geschäftsführung: Prof. Dr. Christoph Meinel
>> 
>> tel:     +49 331 5509 547
>> email:   magnus.knuth@hpi.de
>> web:     http://www.hpi.de/
>> webID:   http://magnus.13mm.de/

-- 
Magnus Knuth

Hasso-Plattner-Institut für Softwaresystemtechnik GmbH
Prof.-Dr.-Helmert-Str. 2-3
14482 Potsdam

Amtsgericht Potsdam, HRB 12184
Geschäftsführung: Prof. Dr. Christoph Meinel

tel:     +49 331 5509 547
email:   magnus.knuth@hpi.de
web:     http://www.hpi.de/
webID:   http://magnus.13mm.de/
Received on Monday, 2 March 2015 14:16:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:16:38 UTC