- From: Steve Speicher <sspeiche@gmail.com>
- Date: Wed, 16 Jan 2013 16:01:20 -0500
- To: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
This issue seems to be unnecessary in the sense that it focuses on how resources are created, which is covered already in the specification by POST'ing the representation of the resource to the container. See 5.4.1 [1] which states: [[ 5.4.1 LDPC clients should create member resources by submitting a representation as the entity body of the HTTP POST to a known LDPC. LDPCservers must respond with status code 201 (Created) and the Location header set to the new resource’s URL. ]] Proposal: close issue as this already defined by this referenced section. Emails associated with issues appear to be tangled in other issues, like actual creation of container, etc. There is no need to tie a representation limitation on what is created within a container and this doesn't. [1]: https://dvcs.w3.org/hg/ldpwg/raw-file/default/ldp.html#ldpc-5_4_1 -- - Steve Speicher
Received on Wednesday, 16 January 2013 21:01:48 UTC