W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2009

Re: Feature names: Typo in example

From: Marcos Caceres <marcosc@opera.com>
Date: Fri, 29 May 2009 17:17:41 +0200
Message-ID: <4A1FFC95.8020604@opera.com>
To: Marcin Hanclik <Marcin.Hanclik@access-company.com>
CC: public-webapps <public-webapps@w3.org>, "Breitschwerdt, Christian, VF-Group" <christian.breitschwerdt@vodafone.com>

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
Received on Friday, 29 May 2009 15:18:30 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:31 GMT