RE: [Widget URI] Internationalization, widget IRI?

(BCC original mailing lists, directing traffic to ""
for IRI issues.
There are no "IRI schemes". I'm not sure that the draft makes
this clear, or makes clear that although most other parts of
the IRI syntax extend URI syntax, the scheme is the same, cannot
contain any %xx encoded characters because it cannot contain %,

-----Original Message-----
From: On Behalf Of Marcin Hanclik
Sent: Friday, July 24, 2009 9:37 AM
Subject: [Widget URI] Internationalization, widget IRI?

Hi Robin, All,

Why is the Widgets 1.0: URI Scheme about URI and not IRI?

Widgets 1.0 P&C is using only the term/type IRI (URI cannot be found there), e.g. for id, href and name attributes.
In Widgets 1.0: URI Scheme (WUS?) document you refer in [1] to zip-rel-path.
It resembles IRI per design, since conversion of the file name field [2], that may be specified in UTF-8, to URI would entail "percent-encoding" [3].
Thus having IRI instead of URI could save processing time/power.
It seems [4] already touches upon the internationalization.

Specifically the ABNF:

widget-URI  = "widget:" "//" [ authority ] "/" zip-rel-path [ "?" query ] [ "#" fragment ]

is incorrect (depending on whether you are on byte or character level), because zip-rel-path includes non-percent-encoded characters, thus widget-URI is actually an IRI.

What then about naming the specification as "Widgets 1.0: IRI Scheme" and referring to IRIs?


Kind regards,

Marcin Hanclik
ACCESS Systems Germany GmbH
Tel: +49-208-8290-6452  |  Fax: +49-208-8290-6465
Mobile: +49-163-8290-646


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 Saturday, 25 July 2009 23:45:27 UTC