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

More comments on Primer

From: Andrei Sambra <andrei@w3.org>
Date: Thu, 19 Mar 2015 14:46:52 -0400
Message-ID: <550B199C.9010808@w3.org>
To: Linked Data Platform WG <public-ldp-wg@w3.org>
Hi all,

After reading the primer again, I would also like to make a couple of

First comment.

The example in section 2.3 "Creating a RDF resource (POST an RDF
resource to an LDP-BC)" shows how a POST to a container creates a new
resource in it.

However, it does not indicate what type of resource is supposed to be
created, since no Link header is present in the request. To me, the
request should be following the client interaction model described in
the LDP spec (section One reason why I am trying to push for
an explicit interaction is that POST should not by default create member
resources. We should try to avoid overloading the semantics for a
"blank" POST to a Container, in case we or someone else would like to
use POST for a different interaction.

For that reason, I suggest adding the appropriate Link header to the

POST /alice/ HTTP/1.1
Host: example.org
Slug: foaf
Content-Type: text/turtle
Link: <http://www.w3.org/ns/ldp#Resource>; rel="type"

Second comment (related).

There are no examples showing how to create containers! Is there any
chance we can have at least one example? Again, the only difference
between creating a resource and a container lies in the Link header
being sent -- e.g. to create a "pictures" container under
http://example.org/alice/, one could do the following:

POST /alice/ HTTP/1.1
Host: example.org
Slug: pictures
Content-Type: text/turtle
Link: <http://www.w3.org/ns/ldp#BasicContainer>; rel="type"

Please let me know if you think these are reasonable changes. I suppose
I can take an ACTION and submit the changes myself, since I'm proposing

Andrei Sambra

Received on Thursday, 19 March 2015 18:46:54 UTC

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