W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2009

RE: [Widget URI] Internationalization, widget IRI?

From: Marcin Hanclik <Marcin.Hanclik@access-company.com>
Date: Thu, 3 Sep 2009 13:32:17 +0200
To: Robin Berjon <robin@berjon.com>
CC: public-webapps WG <public-webapps@w3.org>
Message-ID: <FAA1D89C5BAF1142A74AF116630A9F2C2890C65F05@OBEEX01.obe.access-company.com>
Hi Robin,

Thanks for your comments.

I believe the terminology could be clarified once the IRI/URI issue from P&C gets solved in I18N, hopefully together with HREF and all related stuff.

+1 for simplification.


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: Robin Berjon [mailto:robin@berjon.com]
Sent: Wednesday, September 02, 2009 11:17 PM
To: Marcin Hanclik
Cc: public-webapps WG
Subject: Re: [Widget URI] Internationalization, widget IRI?

Hi Marcin,

On Jul 24, 2009, at 18:36 , Marcin Hanclik wrote:
> Why is the Widgets 1.0: URI Scheme about URI and not IRI?

Because it was written quickly :) And also because I'm sick and tired
of the level of terminology needed to address (no pun intended) what
should be a simple field - I'd like to just say "URI" and since this
isn't a legacy context obviously it means IRI with the added advantage
that it doesn't hurt the brains of the majority of readers... Anyway,
no point in ranting over spilt beer I guess.

Based on the follow-up discussion what I've done is that I've used IRI
throughout the specification except when discussing URI schemes. I've
also updated the reference to be to RFC 3987 and the syntax to
reference iauthority, iquery, and ifragment - which is indeed more


Robin Berjon - http://berjon.com/


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


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 Thursday, 3 September 2009 11:33:18 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:18 UTC