- From: Steve Speicher <sspeiche@gmail.com>
- Date: Tue, 3 Mar 2015 09:58:02 -0500
- To: David Booth <david@dbooth.org>
- Cc: Magnus Knuth <magnus.knuth@hpi.uni-potsdam.de>, "public-ldp@w3.org" <public-ldp@w3.org>
- Message-ID: <CAOUJ7JpbfVEon6x+EqzEKfPucg_EhDc8aX0Uk_nwW79u0V7bbg@mail.gmail.com>
On Mon, Mar 2, 2015 at 9:53 AM, David Booth <david@dbooth.org> wrote: > On 03/02/2015 09:23 AM, Steve Speicher wrote: > >> Hi Magnus, >> >> On Mon, Mar 2, 2015 at 7:47 AM, Magnus Knuth >> <magnus.knuth@hpi.uni-potsdam.de >> <mailto: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. >> >> The reason the spec doesn't define anything is that the intent is >> whatever RDF defines that resource. In other words, it doesn't define >> any restrictions unless the LDP RDF Source is also an LDP Container. >> > > This would be good to say explicitly in the spec, so that readers are not > left wondering. > Hi David, There is always this balance of how much to say and when to say "the spec doesn't constrain this". Hearing this feedback for a couple folks, I'd propose to put something in the "LDP Best Practices and Guidance" [1] as it is not a REC document. [1]: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp-bp/ldp-bp.html Regards, Steve Speicher http://stevespeicher.me > > Thanks, > David > > >> 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? >> >> These are implementation decisions and spec doesn't restrict it. Though >> I would expect it to be fairly symmetrical. In the sense, if you allow >> writing to your server then you'd expect that whatever is allowed on PUT >> (or POST), on a subsequent GET you'd get nearly the same triples that >> were written by the client. I say nearly in that some servers will add >> some triples such as dc:modified, etc. >> >> Let me know if there are still any questions. >> >> Regards, >> Steve Speicher >> http://stevespeicher.me <http://stevespeicher.me/> >> >> >> 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 <mailto:magnus.knuth@hpi.de> >> web: http://www.hpi.de/ >> webID: http://magnus.13mm.de/ >> >> >>
Received on Tuesday, 3 March 2015 14:58:31 UTC