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

Re: Explaining the "semantics" of the HTTP methods

From: Raúl García Castro <rgarcia@fi.upm.es>
Date: Fri, 28 Sep 2012 16:51:08 +0200
Message-ID: <5065B95C.9070902@fi.upm.es>
To: Olivier Berger <olivier.berger@it-sudparis.eu>
CC: public-ldp-wg@w3.org
El 28/09/12 16:37, Olivier Berger escribió:
> Hi.
> I've read the editor's draft again, and I'd like to point out a
> problem with the following excerpt :
>   4.3 HTTP POST
>   There are no additional requirements on HTTP POST for BPRs.
>   4.4 HTTP PUT
> I'm a bit short on how to implement that ;-) No additional requirements,
> compared to ?
> Maybe one needs to have fully read other HTTP specs before, which
> shouldn't be repeated in LDBP, but I fear we are a bit short on
> explaining when to use PUT vs POST for instance.
> More generally, shouldn't one sentence be repeated for each of the BPR
> methods to explain that they are used for retrieval, modification,
> removal, etc ?
> I'm not sure this is worth creating an issue in the tracker.
> Hope this helps.
> Best regards,

Hi everyone,

I agree with Olivier.

Even if this specification is supported by other specifications, to read 
those other ones should not lead to more confusion. :)

For example, some clarification should be made about the behaviour of a 
BPR when POSTing to it.

The HTTP specification says that the entity in the request is a 
subordinate of the resource identified by the URI.

So, a BPR could be transformed into a BPC (or not) just by means of 
POSTing to it?

I think that we need some clear guidelines here.

Kind regards,


Dr. Raúl García Castro

Ontology Engineering Group
Departamento de Inteligencia Artificial
Universidad Politécnica de Madrid
Campus de Montegancedo, s/n - Boadilla del Monte - 28660 Madrid
Phone: +34 91 336 36 70 - Fax: +34 91 352 48 19
Received on Friday, 28 September 2012 14:51:38 UTC

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