- From: Nandana Mihindukulasooriya <nmihindu@fi.upm.es>
- Date: Mon, 5 May 2014 14:30:19 +0200
- To: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
- Message-ID: <CAAOEr1=6TKFwYmsxAbdMnSaRt_u077S8WZ0veh915d2euLjk6g@mail.gmail.com>
Hi, 5.2.3.4 put a constraint on the server that it should honor the interaction model if a client specifies one. Does this imply that if a client wants a guarantee that the created resource to act like an LDPR/LDPC, it should include the link header in the creation requests (though we don't have any restriction on the client saying that it MUST send this link header when creating LDPRs)? The reason for asking this question is to decide whether the Link header should be included in all examples of creating an LDPR or just in the case of creating LDPCs. As it reads now, my intuition is to include the header in all examples including the creation of non-RDF LDPRs (LDP-NRs). [[ 5.2.3.4 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). If any requested interaction model cannot be honored, the server must fail the request. - If the request header specifies a LDPR interaction model, then the server must handle subsequent requests to the newly created resource's URI as if it is a LDPR. (even if the content contains an rdf:type triple indicating a type of LDPC). - If the request header specifies a LDPC interaction model, then the server must handle subsequent requests to the newly created resource's URI as if it is a LDPC. - This specification does not constrain the server's behavior in other cases. ]] Best Regards, Nandana
Received on Monday, 5 May 2014 12:31:05 UTC