W3C home > Mailing lists > Public > public-ldp-wg@w3.org > November 2013

Re: ldp-ISSUE-90 (Named Graph): An LDPC/LDPR is a Named Graph [Linked Data Platform Spec]

From: Eric Prud'hommeaux <eric@w3.org>
Date: Sun, 24 Nov 2013 09:42:44 -0500
To: Linked Data Platform Working Group <public-ldp-wg@w3.org>
Message-ID: <20131124144242.GA20845@w3.org>
* Linked Data Platform (LDP) Working Group Issue Tracker <sysbot+tracker@w3.org> [2013-11-22 21:22+0000]
> ldp-ISSUE-90 (Named Graph): An LDPC/LDPR is a Named Graph [Linked Data Platform Spec]
> 
> http://www.w3.org/2012/ldp/track/issues/90
> 
> Raised by: Alexandre Bertails
> On product: Linked Data Platform Spec
> 
> An LDPC/LDPR acts as a Named Graph (now defined in RDF 1.1 [1]). An HTTP GET on an LDPR URL should return its representation, and *nothing* else.
> 
> The specification currently says:
> [[
> 4.3.3 LDP servers MUST provide a text/turtle representation of the requested LDPR [TURTLE].
> ]]

Is the goal to prohibit content negotiation to other representations?


> I propose that the specification explicitly refers to RDF Named Graphs and makes the constraint on the GET explicit.

Referring to named graphs implies an RDF dataset in all specs that refer to named graphs (SPARQL, Trig, RDF Concepts). Are there specific dataset features that you would like to enable in LDP?


> This does not prevent one to later define a service (eg. SPARQL) which would allow a user to retrieve the representations of an LDPC and its LDPR in one single request.
> 
> Also, all the examples (eg. 1, 2, 9, etc.) with GETs on LDPCs must not return the content of the "contained" LDPRs. They should be rewritten in terms of several GETs, one for the LDPC and one for each LDPR.

I read this as a proposal to change
<https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldp-rdfconcepts-extra-triples-members>
from
[[
The representation of an LDPC can include an arbitrary number of
additional triples whose subjects are the members of the container, or
that are from the representations of the members (if they have RDF
representations). This allows a LDP server to provide clients with
information about the members without the client having to do a GET on
each member individually.
]]
to
[[
The representation of an LDPC MUST NOT include any
additional triples whose subjects are the members of the container, or
that are from the representations of the members (if they have RDF
representations).
]]

> Alexandre.
> 
> [1] http://www.w3.org/TR/rdf11-concepts/#dfn-named-graph
> 
> 
> 

-- 
-ericP

office: +1.617.599.3509
mobile: +33.6.80.80.35.59

(eric@w3.org)
Feel free to forward this message to any list for any purpose other than
email address distribution.

There are subtle nuances encoded in font variation and clever layout
which can only be seen by printing this message on high-clay paper.
Received on Sunday, 24 November 2013 14:43:14 UTC

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