- From: Andy Seaborne <andy.seaborne@epimorphics.com>
- Date: Sat, 20 Oct 2012 11:31:52 +0100
- To: public-ldp-wg@w3.org
On 17/10/12 16:18, James M Snell wrote: > > > On Wed, Oct 17, 2012 at 8:11 AM, Steve Battle > <steve.battle@sysemia.co.uk <mailto:steve.battle@sysemia.co.uk>> wrote: > > [snip] > > __ __ > > RFC 3986 is written more from the perspective of HTTP GET, so for > HTTP POST we have to read between the lines.____ > > Returning to the issue, we would like to know if it is OK to assume > in the context of an HTTP POST and the above scenario that:____ > > __ __ > > 1. If there is no embedded @base and..____ > > 2. there is no retrieval context for POST and..____ James, Question on one detail: Does the request URI constitute a context for POST? This is question is about how much weight to put on "retrieval". 3986/sec5.1.3 is the only one of the 5.1 sections that says "retrieval". Does it imply it also applies to the request, not just the response. Andy > > 3. no URI was used to retrieve the representation, then..____ > > 4. the default base URI can be set by the application to be the URI > of the created resource.____ > > __ > > > I would say this is certainly a reasonable and logical assumption. Note, > however, that you need to account for the possible presence of the > Content-Location header within the POST request. If the POST includes a > Content-Location, it's value effectively establishes the base URI. > > - James > > __ > > It might also be helpful if 2616 could provide clarification on > these issues.____ > > __ __ > > Thanks for your considered opinions,____ > > Steve.____ > > __ __ > > --____ > > Steve Battle > Semantic Engineer > > Mobile: +44 (0)7503 624 613____ > > E-mail: steve.battle@sysemia.co.uk <mailto:steve.battle@sysemia.co.uk> > Web: www.sysemia.com <http://www.sysemia.com/>____ > > __ __ > > Sysemia Limited > The Innovation Centre, Bristol & Bath Science Park, Dirac Crescent, > Emerson's Green, Bristol BS16 7FR > Registered in England and Wales. Company Number: 7555456 > > DISCLAIMER____ > > Information contained in this e-mail is intended for the use of the > addressee only, and is confidential and may also be privileged. If > you receive this message in error, please advise us immediately. If > you are not the intended recipient(s), please note that any form of > distribution, copying or use of this communication or the > information in it is strictly prohibited and may be unlawful. > Attachments to this e-mail may contain software viruses which may > damage your systems. Sysemia Ltd have taken reasonable steps to > minimise this risk, but we advise that any attachments are virus > checked before they are opened.____ > > __ __ > >
Received on Saturday, 20 October 2012 10:32:22 UTC