Re: Question regarding POST versus PUT for creating an LDPC

hello andy.

On 2013-04-19 06:21 , "Andy Seaborne" <andy.seaborne@epimorphics.com>
wrote:
>Example 2:
>The WMO (World Meteorological Organisation) publishes code lists,
>currently as books and PDFs maybe soon as linked data.  The code items
>exist and the names are fixed.  Client-side control of URI is very
>important to them.
>/0-20-086/6 is the code for "slush"
>/C-6/001 is the code for the unit "meters" ... and it must be 001, not 1.

just to be very clear here: of course being able to pick URIs can be very
important. but in the end, the URI namespace exposed by an LDP service is
under control of some server, and LDP is a protocol that allows clients to
interact with that server. so we want to allow the kind of thing you're
asking for, but we also have make sure LDP is driven by hypermedia, so
that clients interacting with servers are able to interact with them
within the constraints of specific server configurations. for example, i
could very well imagine that many implementations might be slightly
unhappy about "item names" containing slash characters, but that is of
course just an implementation issue. so some implementations might choose
to disallow names like this (because they implement some naïve mappings of
path components to container/item names), whereas the WMO LDP service
obviously shouldn't.

cheers,

dret.

Received on Friday, 19 April 2013 15:47:19 UTC