Lists Home |
Date Index |
- From: John Cowan <email@example.com>
- To: firstname.lastname@example.org
- Date: Mon, 13 Sep 1999 10:30:35 -0400 (EDT)
Takuki Kamiya scripsit:
> I have encountered a usage of namespace'd XML where namespace name (i.e. URI)
> contains non-ascii characters, and is wondering how namespace-aware XML software
> should handle the URIs.
> As an example, think of the instance shown below.
> <x xmlns:ns1="http://www.富士通.co.jp"
> xmlns:ns2="http://www.%E5%AF%8C%E5%A3%AB%E9%80%9A.co.jp" >
> <good n1:a="1" n2:a="2" />
> Both of the URIs conceptually denotes "http://www.fujitsu.co.jp" except that
> the part "fujitsu" is represented by using numeric character references in the
> first case and is represented as being encoded as mentioned in XML 1.0 spec.
> (I mean "4.2.2 External Entities")
Technically, the first URI is not conforming, because the surface form of
an URI can only contain plain ASCII. However, applications should
treat such an URI as identical to the URLencoded UTF-8 in the second
> My question is, is a namespace-aware XML processor supposed to identify the
> two URLs shown above as identical ones so that the XML instance above is in
> error since n1:a and n2:a really means the same?
> If the answer to the question is "yes", then I believe XML processors should
> return encoded representation such as "http://www.%E5%AF%8C%E5%A3%AB%E9%80%9A.co.jp"
> to using applications as namespace name. Is my understanding correct?
It's a reasonable thing to do as a matter of error recovery.
An alternative action is to reject the URI as ill-formed.
John Cowan email@example.com
I am a member of a civilization. --David Brin
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)