- From: Marcos Caceres <marcosc@opera.com>
- Date: Mon, 29 Jun 2009 11:26:42 +0200
- To: Marcin Hanclik <Marcin.Hanclik@access-company.com>
- Cc: public-webapps <public-webapps@w3.org>
Hi Marcin, For the LC DoC, can I get a quick confirmation that you are satisfied with the responses of the WG for this thread. Kind regards, Marcos On Fri, May 29, 2009 at 5:17 PM, Marcos Caceres<marcosc@opera.com> wrote: > > For the sake of the disposition of comment, please verify that you are > satisfied with the changes and response below. > > On 5/29/09 4:55 PM, Marcin Hanclik wrote: >> >> Hi Marcos, >> >> Thanks. >> Your proposal is generally ok me, feature name is just IRI. >> I have, however, 2 arguments to change your proposal a bit: >> 1. "API:" may be misunderstood, so let's use e.g. "http:" or "ftp:" or >> anything else what is universally known (and hierarchical at the same time) >> now. >> 2. To satisfy the comments from Christian, I would add at least one slash >> in the IRI, e.g. >> "http://example.org/geolocation" >> As you know in BONDI (just informatively now) we went further and the >> query part of the IRI is used for versioning of the APIs as in >> http://bondi.omtp.org/1.0/apis/BONDI_Interface_Patterns_v1.0.html#versioning. >> I do not want to discuss versioning here, but I just would like to vote >> for a slash in the IRI example, to show that IRI is more powerful than just >> to be used as a string (I mean hierarchy etc. and slash may just help here). >> >> What do you think? > > Right, but we don't want delude people into believing that it serves any > purpose beyond helping humans see the hierarchy. How and implementation > treats the URI is a matter for the implementation (in the case of BONDI, > hierarchy indicated by slashes instead of dots might be significant, or it > might not... I don't know.). > > Having said that, I've changed it to a slash to avoid any further confusion. > > Kind regards, > Marcos > > -- Marcos Caceres http://datadriven.com.au
Received on Monday, 29 June 2009 09:27:53 UTC