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

RE: [widget-uri] Widget URI ABNF definition comments

From: Marcin Hanclik <Marcin.Hanclik@access-company.com>
Date: Wed, 16 Sep 2009 14:21:01 +0200
To: "Jere.Kapyaho@nokia.com" <Jere.Kapyaho@nokia.com>, "timeless@gmail.com" <timeless@gmail.com>
CC: "public-webapps@w3.org" <public-webapps@w3.org>, "robin@berjon.com" <robin@berjon.com>, "public-iri@w3.org" <public-iri@w3.org>
Message-ID: <FAA1D89C5BAF1142A74AF116630A9F2C2890C662A7@OBEEX01.obe.access-company.com>

I think we should not mix Resource Identifiers with schemes and scheme names (aka semantics and syntax).
As for me WRI and XRI are schemes that follow URI/IRI syntax and define new scheme names and add semantics/interpretation.

I hope that the terms "scheme", "scheme-name" will be fixed in the upcoming IRI spec [1] (thus I CCed public-iri).


[1] http://lists.w3.org/Archives/Public/public-iri/2009Jul/0029.html

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
From: public-webapps-request@w3.org [mailto:public-webapps-request@w3.org] On Behalf Of Jere.Kapyaho@nokia.com
Sent: Tuesday, September 15, 2009 1:17 PM
To: timeless@gmail.com
Cc: public-webapps@w3.org; robin@berjon.com
Subject: Re: [widget-uri] Widget URI ABNF definition comments

On 15.9.2009 13.55, "ext timeless" <timeless@gmail.com> wrote:
On Tue, Sep 15, 2009 at 1:49 PM, <Jere.Kapyaho@nokia.com> wrote:
> Maybe changing the document name to "Widgets 1.0: Widget Resource
> Identifiers" would sidestep some of the problem. :-)

So we can have URNs, URLs, URIs, IRIs, and WRIs? i'm not sure that's
an improvement :)
Well, maybe not. But you forgot XRI by OASIS [1]. :-)


[1] http://en.wikipedia.org/wiki/Extensible_Resource_Identifier


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 Wednesday, 16 September 2009 12:21:54 UTC

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