W3C home > Mailing lists > Public > public-ldp-wg@w3.org > October 2012

Re: Documenting an an explicit URI to be used for representing POSTed new LDPC members

From: Wilde, Erik <Erik.Wilde@emc.com>
Date: Tue, 30 Oct 2012 13:59:27 -0400
To: "public-ldp-wg@w3.org" <public-ldp-wg@w3.org>
CC: Olivier Berger <olivier.berger@it-sudparis.eu>
Message-ID: <CCB561E7.B64B%erik.wilde@emc.com>
hello.

>So, this factory_URI + '#_new' could be mandated by the specs to
>represent the URI in the posted resource, by convention (it's very
>unlikely to have a confusion between that one and other URIs of
>predicates or values.
>Would such a convention on a special fragment for representing the
>POSTed resource help solve the base URI discussions ?
>We could also make it less a convention, but an explicit URI, provided
>by the container/factory.

that would be much better. any kind of URI-based magic baked into web
specs tends to get into some trouble sooner or later. fyi, in AtomPub
(which is pretty much what we're trying to build here, and looking at it
quite a bit could help us to inform many of our design decisions), the
magic is built into the fact that you're supposed to POST to the same URI
you're GETting the collection contents from. AtomPub (implicitly)
establishes a "create" link between the collection URI that provides
access to the collection to the same URI, specifies that clients can try
to POST to that URI, and that servers are expected to treat those POST
requests as create requests.

http://tools.ietf.org/html/rfc5023#section-5.3

cheers,

dret.
Received on Tuesday, 30 October 2012 18:00:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:17:32 UTC