- From: Martynas Jusevičius <martynas@graphity.org>
- Date: Fri, 13 Dec 2013 02:46:21 +0100
- To: Steve Speicher <sspeiche@gmail.com>
- Cc: "public-ldp@w3.org" <public-ldp@w3.org>
Hey Steve, so lets say the request with RDF entity is (prefixes assumed): POST /docs <http://external.org> a foaf:Document . then /docs creates a new resource with the representation above (section 5.4.4) and newly minted URI like /docs/12345 (section 5.4.8). Then subsequent GET /docs/12345 returns <http://external.org> a foaf:Document . Is that a correct understanding? In that case, how does that align with 4.2.2 which says: "LDPR servers must provide an RDF representation for LDPRs. The HTTP Request-URI of the LDPR is typically the subject of most triples in the response." Is the RDF above the representation of </docs/12345> or something else, like <http://external.org>? In any case, the request URI is not the subject in that triple. Martynas On Thu, Dec 12, 2013 at 7:15 PM, Steve Speicher <sspeiche@gmail.com> wrote: > Hi Martynas, > > > On Tue, Dec 10, 2013 at 9:30 PM, Martynas Jusevičius <martynas@graphity.org> > wrote: >> >> Hey, >> >> I was wondering what happens if multiple resource representations are >> contained in the entity body during LDPC POST? > > How would a server know it was multiple? Depends on the representation. > > Currently undefined. This requirement isn't about RDF representations, it > is about any kind representation being POSTed to create a resource and have > it as a member of a container. For RDF representations, I could see one > implementation simple creating a new named graph, with the name being the > newly minted URL for it and then returning that URL in the Location header. > I could see another implementation rejecting it, with some indication that > it can't do batch creates of resources. If it wanted to create multiple > resources, it should send multiple POST requests. If there is a requirement > to do this, perhaps we can add this to our wishlist for future enhancements. > > >> >> "Location header set to the new resource" -- what is the new resource, >> exactly? > > For RDF-based resources (LDPRs), the URL for the graph holding the triples > for the resource created. > > >> Section 5.4.1 is not so clear on this: >> http://www.w3.org/TR/ldp/#ldpc-HTTP_POST >> >> Besides, "clients shall not expect" does not look like a formal >> requirement to me. > > Correct, this isn't a formal requirement and was carefully constructed > without using keywords from RFC2119. It is just an informative statement. > > - Steve Speicher > >> >> Martynas >> graphityhq.com >>
Received on Friday, 13 December 2013 01:46:49 UTC