Fwd: Re: Impact of changing a specification from URI to IRI and XRI

["G. Ken Holman" <gkholman@CraneSoftwrights.com>]

Fellow CLRTC members,

I've asked someone I highly respect regarding markup and the Internet 
about any impact we have of changing our use of URI strings.

He can only comment on the use of IRI strings and from what I see 
there is no impact for us to simply say a string is an IRI wherever 
we say it is a URI.

http://en.wikipedia.org/wiki/XRI states there is some disagreement 
regarding the problems being addressed by XRI strings.  Perhaps we 
should wait to say anything about XRI until it is more widely accepted.

. . . . . . . . . . Ken

>Date: Wed, 29 Nov 2006 07:23:58 +0900
>From: "MURATA Makoto (FAMILY Given)" <eb2m-mrt@asahi-net.or.jp>
>To: "G. Ken Holman" <gkholman@CraneSoftwrights.com>
>Subject: Re: Impact of changing a specification from URI to IRI and XRI
>Cc: MURATA Makoto <eb2m-mrt@asahi-net.or.jp>
>...
>Historically, it was not clear whether URIs allow non-ASCII characters.
>But not it is clear.   URIs disallow non-ASCII charcters, while IRIs
>allow them.  More about this, see RFC 3987 and RFC 3986.
>
>The datatype xsd:anyURI allows IRIs, however.  So, we can safely
>use this datatype for allowing non-ASCII characters.


--
World-wide corporate, govt. & user group XML, XSL and UBL training
G. Ken Holman                 mailto:gkholman@CraneSoftwrights.com
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/o/
Box 266, Kars, Ontario CANADA K0A-2E0    +1(613)489-0999 (F:-0995)
Male Cancer Awareness Aug'05  http://www.CraneSoftwrights.com/o/bc
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal