RE: I18N & XML Namespaces

I was meaning for example the use of an è (e-grave) in a namespace
identifier.

I give an example question in
http://lists.w3.org/Archives/Public/xml-names-editor/2002May/0001.html
(but the e-acute got screwed up somewhere before it got onto the web).

Jeremy


> -----Original Message-----
> From: Julian Reschke [mailto:julian.reschke@gmx.de]
> Sent: 14 May 2002 13:43
> To: Jeremy Carroll; www-xml-blueberry-comments@w3.org
> Subject: RE: I18N & XML Namespaces
>
>
> Hm,
>
> maybe I'm missing something, but a namespace name takes the
> syntactic form
> of a URI reference as defined in RFC2396, so isn't it restricted
> to US-ASCII
> anyway?
>
> > -----Original Message-----
> > From: www-xml-blueberry-comments-request@w3.org
> > [mailto:www-xml-blueberry-comments-request@w3.org]On Behalf Of Jeremy
> > Carroll
> > Sent: Tuesday, May 14, 2002 2:38 PM
> > To: www-xml-blueberry-comments@w3.org
> > Subject: I18N & XML Namespaces
> >
> >
> >
> > This is a comment on
> >
> > Namespaces in XML 1.1 Requirements
> > http://www.w3.org/TR/2002/WD-xml-names11-req-20020403/
> >
> >
> > I suggest an additional requirement:
> >
> > - Namespaces in XML 1.1 should clarify the use of non
> > US-ASCII characters in namespace identifiers.
> >
> > or alternatively
> >
> > - Namespaces in XML 1.1 should conform with the requirements
> > of charmod section 8 "Character Encoding in URI References"
> > http://www.w3.org/TR/charmod/#sec-URIs
> >
> >
> > Jeremy Carroll
> >
> > PS: I have been sending comments on
> > http://www.w3.org/TR/2002/WD-xml-names11-20020403/
> > to
> > xml-names-editor@w3.org
> > as specified in the draft.
> > I wonder if you meant to say www-xml-blueberry-comments@w3.org.
> >
> >
> >
> >
>
>

Received on Tuesday, 14 May 2002 09:12:24 UTC