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

POSTing RDF to LDPC without null URIs

From: Andreea State <andreea.state@factmint.com>
Date: Tue, 6 Jan 2015 16:50:36 +0000
Message-ID: <CAESeULf5ynJ6eo6VvoKmgzZxZiXKXkOYJ2Jhs7PvsWLVVh6_7w@mail.gmail.com>
To: public-ldp-comments@w3.org

I have a query regarding LDP behaviour in the case of POSTing against a
container. Let us assume "http://example.com/c1" is a container, and I POST
the following turtle document:

@prefix <http://example.com>
<dog> a <Animal> .
<cat> a <Animal> .

The specification says that for null relative URIs the server returns a
'Location' header with a newly created resource. It does not appear to be
obvious what the behaviour should be in the case of the above example -
where there are no null URIs.

>From the draft recommendation:

" LDP clients should create member resources by submitting a
representation as the entity body of the HTTP POST to a known LDPC. If the
resource was created successfully, LDP servers must respond with status
code 201 (Created) and the Location header set to the new resource’s URL.
Clients shall not expect any representation in the response entity body on
a 201 (Created) response."

Does that only apply to LDP clients?

Some guidance would be appreciated.

Thank you,
Andreea State
Received on Wednesday, 7 January 2015 10:07:48 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 10:07:48 UTC