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

RE: Feature names: Typo in example

From: Marcin Hanclik <Marcin.Hanclik@access-company.com>
Date: Fri, 29 May 2009 16:55:59 +0200
To: Marcos Caceres <marcosc@opera.com>
CC: public-webapps <public-webapps@w3.org>, "Breitschwerdt, Christian, VF-Group" <christian.breitschwerdt@vodafone.com>
Message-ID: <FAA1D89C5BAF1142A74AF116630A9F2C0A26ED8FA5@OBEEX01.obe.access-company.com>
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?

Thanks.

Kind regards,
Marcin

Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452  |  Fax: +49-208-8290-6465
Mobile: +49-163-8290-646
E-Mail: marcin.hanclik@access-company.com

-----Original Message-----
From: Marcos Caceres [mailto:marcosc@opera.com]
Sent: Friday, May 29, 2009 4:44 PM
To: Marcin Hanclik
Cc: public-webapps; Breitschwerdt, Christian, VF-Group
Subject: Re: Feature names: Typo in example


Hi Marcin,

On 5/29/09 4:26 PM, Marcin Hanclik wrote:
> Hi Marcos,
>
> The following typo has been found by BONDI contributors.
>
> The example in http://dev.w3.org/2006/waf/widgets/#the-feature-element now specified as:
>
> <widget xmlns="http://www.w3.org/ns/widgets">
>
>     <feature name="http://example.org/api.geolocation"
>              required="false"/>
> </widget>
>
> should read:
>
> <widget xmlns="http://www.w3.org/ns/widgets">
>
>     <feature name="http://example.org/api/geolocation"
>              required="false"/>
> </widget>
>
> to follow the convention contributed by BONDI.
> The api.geolocation shall be changed to api/geolocation.
>
> I/we hope it can be fixed soon.

That is not an error; it's on purpose. It's just showing that it's just
a URI that can be structured in any way so long as it is valid. It also
deliberately non-conforming to the stylistic decisions of BONDI. It's
just an example. If anything, I should change the example to:

<feature name="API:example.org.geolocation"
              required="false"/>


________________________________________

Access Systems Germany GmbH
Essener Strasse 5  |  D-46047 Oberhausen
HRB 13548 Amtsgericht Duisburg
Geschaeftsfuehrer: Michel Piquemal, Tomonori Watanabe, Yusuke Kanda

www.access-company.com

CONFIDENTIALITY NOTICE
This e-mail and any attachments hereto may contain information that is privileged or confidential, and is intended for use only by the
individual or entity to which it is addressed. Any disclosure, copying or distribution of the information by anyone else is strictly prohibited.
If you have received this document in error, please notify us promptly by responding to this e-mail. Thank you.
Received on Friday, 29 May 2009 14:57:10 GMT

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