- From: Roger Menday <Roger.Menday@uk.fujitsu.com>
- Date: Wed, 2 Jan 2013 16:25:42 +0000
- To: Steve Battle <steve.battle@sysemia.co.uk>
- CC: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
Received on Wednesday, 2 January 2013 16:26:08 UTC
On 2 Jan 2013, at 16:04, Steve Battle wrote: >> -----Original Message----- >> From: Roger Menday [mailto:Roger.Menday@uk.fujitsu.com] > >> Say then, I want to link <Tracker/1/Bug/3> to another (existing) > resource. >> >> The <Tracker/1/Bug/3;related> collection represents all the :related > links. >> I can discover that it requires a ldp:link property to seed the process. >> >> POST to <Tracker/1/Bug/3;related> with "<> ldp:link <Tracker/1/Bug/1> ." > > I'm not clear why you're using POST to create a link to an _existing_ > resource. > My understanding is that POST is a mechanism to create _new_ resources > within containers. > Could the example use PUT or PATCH instead? This proposal is a way to manage a resource through it's set of links. I have some other material that shows how this can be used to do directed "fine-grained" updates - i.e. then PATCH isn't needed. Roger > > Steve.
Received on Wednesday, 2 January 2013 16:26:08 UTC