ldp-ISSUE-56 (Discovering LDPR PUT URLs): How can clients discover LDPR PUT URLs? [Linked Data Platform core]

ldp-ISSUE-56 (Discovering LDPR PUT URLs): How can clients discover LDPR PUT URLs? [Linked Data Platform core]

http://www.w3.org/2012/ldp/track/issues/56

Raised by: David Wood
On product: Linked Data Platform core

This issue was raised by James Leigh on the public-ldp mailing list:

After reading the current version, I was unable to determine how to
discover the PUT LDPR URL, given a container member URI.

If the member URI resolves to a 303 (See other), should the PUT request
be sent to the 303 Location or the original URI?

In Callimachus we recommend using an OPTIONS request to the original URI
and using the rel=describedby in the Link response header to send
modifications to. This follows httpRange-14 and keeps the URL of the
description document (in turtle) separate from the URI for the
conceptual thing.

I think the spec should include something similar like including a
triple from the member URI to the LDPR URL (perhaps wdrs:describedby).

Received on Friday, 15 March 2013 15:32:01 UTC