LDPR Interaction Model on Create

Hello,

Section 5.2.3.4 (copied below) could use some more explanation. In
particular the first bullet point is not clear. The example given is
when the created content contains an rdf:type triple indicating a type
of LDPC, but specifies a LDPR interaction model.

Given section 5.2.1.1 (each LDPC MUST also be a conforming LDPRS) and
section 4.3.11 (each LDPRS MUST also be a conforming LDPR), I don't
understand under what conditions a LDPC could NOT also be a LDPR
interaction model.

Furthermore given the LDP schema, I would expect a POST to a container
with a Link:<http://www.w3.org/ns/ldp#Resource>;rel="type" that created
a LDPC member to be successful, since ldp:Container rdfs:subClassOf+
ldp:Resource and with RDFS entailment all ldp:Container members are also
ldp:Resource members.

Regards,
James Leigh
---
http://www.w3.org/TR/ldp/#h5_ldpc-post-createrdf

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.

    Clients use the same syntax, that is HTTP Link headers, to specify
the desired interaction model when creating a resource as servers use to
advertise it on responses.

    Note: A consequence of this is that LDPCs can be used to create
LDPCs, if the server supports doing so.

Received on Tuesday, 7 October 2014 19:49:05 UTC