W3C home > Mailing lists > Public > public-iri@w3.org > July 2009

RE: [Widget URI] Internationalization, widget IRI?

From: Marcin Hanclik <Marcin.Hanclik@access-company.com>
Date: Sun, 26 Jul 2009 22:34:21 +0200
To: Larry Masinter <masinter@adobe.com>
CC: "PUBLIC-IRI@W3.ORG" <PUBLIC-IRI@w3.org>, "public-webapps@w3.org" <public-webapps@w3.org>
Message-ID: <FAA1D89C5BAF1142A74AF116630A9F2C2890BCA4EF@OBEEX01.obe.access-company.com>
Hi Larry,

Thanks for your comments.

FYI I sent the following emails to webapps:
http://lists.w3.org/Archives/Public/public-webapps/2009JulSep/0373.html
http://lists.w3.org/Archives/Public/public-webapps/2009JulSep/0376.html

There are two topics around widgets 1.0 and IRIs:
1. IRI is P&C
2. zip-rel-path in P&C referenced from Widgets 1.0: URI Scheme

>>Again, because formally there are no "IRI schemes", there are only
>>URI schemes, even though there are IRIs which can be mapped into
>>URIs of that scheme.
OK. There is URI/IRI dualism.
The issue IMHO is that the mapping between IRI and URI seems not to be automatic, i.e. each application, in our case it seems to be P&C spec, should mandate is explicitly or at least describe how it is done.
At least this is what I understand from reading the IRI spec (I may have to read several times more...).
I posted the related questions here:
http://lists.w3.org/Archives/Public/public-webapps/2009JulSep/0365.html

Having the URI/IRI dualism, I actually wonder whether IRI scheme exists and is equivalent to URI scheme on character level.

>>I wonder if the URI registration process document should specifically
>>allow registration forms to describe the URI scheme syntax in terms of
>>IRI characters.
This seems to be the topic of my emails around Widgets 1.0: URI Scheme and usage of the Zip-rel-path grammar that currently operates on character level, and - I assume - was intended to operate on octets).

Thanks.

Kind regards,
Marcin
________________________________________
From: Larry Masinter [masinter@adobe.com]
Sent: Sunday, July 26, 2009 10:01 PM
To: Marcin Hanclik
Cc: PUBLIC-IRI@W3.ORG
Subject: RE: [Widget URI] Internationalization, widget IRI?

I'm sorry for the confusion, my email was sent by mistake. I
have not re-reviewed the "widget" URI scheme since a previous
review several months ago. I was only reacting to something
in your email. I suppose I should re-review the "widget" URI
scheme document itself, but I haven't. My goal at the moment
is to update the IRI document.

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

The short answer is that, in general,  one defines URI schemes
and automatically gets something that describes IRIs as well.


> 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.

I wonder if the URI registration process document should specifically
allow registration forms to describe the URI scheme syntax in terms of
IRI characters.

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

Again, because formally there are no "IRI schemes", there are only
URI schemes, even though there are IRIs which can be mapped into
URIs of that scheme.

Larry
--
http://larry.masinter.net


________________________________________

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 Sunday, 26 July 2009 20:35:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 30 April 2012 19:51:55 GMT