- From: Robert Sanderson <azaroth42@gmail.com>
- Date: Thu, 11 Sep 2014 16:29:16 -0700
- To: "public-ldp-wg@w3.org Working Group" <public-ldp-wg@w3.org>
- Message-ID: <CABevsUF597-sPJd5QutvQyMPiK2YvVGD527OONv6i=8SuwTgBA@mail.gmail.com>
Some questions on functionality that isn't explicitly covered by the specification, but just want to make sure that's intentional: 1. It seems like an LDP system can create all of the resources POSTed to a container in one operation, and should arbitrarily pick one for the response. For example, if the entity-body of the post contains a graph with five blank nodes, the server can (should?) create all five and return whichever one of them it wants. 2. It is unspecified what happens when the entity-body POSTed to an IndirectContainer does not contain the insertedContentRelation predicate, and thus the system can do what it thinks best (either fail the request, or assume that <> I-C-R <> in the manner of a DirectContainer would be two obvious choices). 3. Systems should support multiple containers with the same membershipResource and the same hasMemberRelation? For example one resource with both direct and indirect containers, both of which contribute to populating the same pool of members in the membership resource. It's not specified, but it seems like a logical conclusion from the spec. Thanks! Rob -- Rob Sanderson Technology Collaboration Facilitator Digital Library Systems and Services Stanford, CA 94305
Received on Thursday, 11 September 2014 23:29:43 UTC