Re: Clarifying POST behavior for LDPCs.

Hi Ashok,


On Wed, Feb 12, 2014 at 5:07 PM, Ashok Malhotra
<ashok.malhotra@oracle.com>wrote:

>  Hi Andrei:
> Take a look at section 6.4.5 and see if that answers your question.
> All the best, Ashok
>

The links in section 6.4.5 point to section 6.2 which is about LDPC GET.
Moreover, section 6.2 specifies that Link headers with rel=type are used in
the HTTP response. The bottom line is that there is no mention of those
headers being used during an HTTP request. I hope I've been clearer this
time.

-- Andrei


>
>  On 2/12/2014 1:18 PM, Andrei Sambra wrote:
>
> Hi all,
>
>  I'm getting really close to having a working implementation on RWW.IO[1]. However, I found that the spec section that describes POST behavior
> for LDPCs lacks some details. More precisely, how should an LDP client
> create containers within a container (details below).
>
>  From section 6.4.5., we see that LDP servers that successfully create a
> resource from a RDF representation in the request entity body must honor
> the client's requested interaction model(s). More precisely, if the request
> header specifies an LDPC interaction model, then the server must create an
> LDPC.
>
>  The link to the interaction model points to section 6.2.8, which deals
> with GET requests -- exposing the Link header with rel=type. At this point,
> one can only assume that the same Link header must be present during a
> POST, since there is no mention in the spec about it.
>
>  My suggestion would be to either add an example in section 6.4., or
> explicitly mention that LDPRs and LDPCs can be created based on the Link
> href value present in the POST request headers (either ldp:Resource or
> ldp:Container).
>
>  Best,
> Andrei
>
>  [1] https://www.w3.org/wiki/LDP_Implementations#RWW.IO
>
>
>