ISSUE-56: How can clients discover LDPR PUT URLs?
Discovering LDPR PUT URLs
How can clients discover LDPR PUT URLs?
- State:
- CLOSED
- Product:
- Linked Data Platform Spec
- Raised by:
- David Wood
- Opened on:
- 2013-03-15
- Description:
- 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). - Related Actions Items:
- No related actions
- Related emails:
- ISSUE-56/ISSUE-57 (from Erik.Wilde@emc.com on 2013-05-30)
- Re: ldp-ISSUE-57 (LDP Service ID): How can a client determine that it is in communication with an LDP service? [Linked Data Platform core] (from henry.story@bblfish.net on 2013-03-16)
- Re: ldp-ISSUE-57 (LDP Service ID): How can a client determine that it is in communication with an LDP service? [Linked Data Platform core] (from kidehen@openlinksw.com on 2013-03-15)
- Re: ldp-ISSUE-57 (LDP Service ID): How can a client determine that it is in communication with an LDP service? [Linked Data Platform core] (from Erik.Wilde@emc.com on 2013-03-15)
- ldp-ISSUE-57 (LDP Service ID): How can a client determine that it is in communication with an LDP service? [Linked Data Platform core] (from sysbot+tracker@w3.org on 2013-03-15)
- Re: LDPR URL Discovery (from david@3roundstones.com on 2013-03-15)
- ldp-ISSUE-56 (Discovering LDPR PUT URLs): How can clients discover LDPR PUT URLs? [Linked Data Platform core] (from sysbot+tracker@w3.org on 2013-03-15)
Related notes:
Resolution: Close Issue-56 without changing the specification. Update Guidelines document to suggest that a 303 response of this type should include the describedby header; perhaps mention the OPTIONS pattern, but leaning against it.
See https://www.w3.org/2013/meeting/ldp/2013-06-20#resolution_4
Display change log
