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

Re: LDPR URL Discovery

From: David Wood <david@3roundstones.com>
Date: Fri, 15 Mar 2013 11:32:17 -0400
Message-Id: <3C63F75E-65A7-4D69-8F69-D8CF20E8D9E1@3roundstones.com>
Cc: "public-ldp@w3.org" <public-ldp@w3.org>, "public-ldp-wg@w3.org Working Group" <public-ldp-wg@w3.org>
To: James Leigh <james@3roundstones.com>
Hi James,

Thank you for your comment.  This issue is being formally tracked here:
  https://www.w3.org/2012/ldp/track/issues/56

On Thu, 14 Mar 2013 09:21:23 -0400, James Leigh wrote:
> 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).


Regards,
Dave
--
http://about.me/david_wood





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

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:03:10 UTC