Dave> <define name="anyuri">
Dave> <data type="string">
Dave> <param name="pattern">(([a-zA-Z][0-9a-zA-Z
Dave> +\-\.]*:)?/{0,2}[0-9a-zA-Z;/?:@&=+$\.\-_!
Dave> ~*'()%]+)?(#[0-9a-zA-Z;/?:@&=+$\.\-_!~*'()%]+)?</param>
Dave> </data>
Dave> </define>
This does not allow non-ASCII characters. I am very sure that
a lot of people want to use non-ASCII characters.
"URI" is a strange word. In the XML family, this word usually means
IRIs (Internationalized Resource Identifiers), which was published
by RFC 3987 only recently. T
The following paragraphs are quoted from 4.2.2 of the XML spec.
[Definition: The SystemLiteral is called the entity's system
identifier. It is meant to be converted to a URI reference (as
defined in [IETF RFC 2396], updated by [IETF RFC 2732]), as part
of the process of dereferencing it to obtain input for the XML
processor to construct the entity's replacement text.] ...
System identifiers (and other XML strings meant to be used as
URI references) MAY contain characters that, according to [IETF
RFC 2396] and [IETF RFC 2732], must be escaped before a URI can
be used to retrieve the referenced resource. ...
And the following para is quoted from 3.2.17 of W3C XML Schema Part 2.
> The mapping from anyURI values to URIs is as defined in Section 5.4
> Locator Attribute of [XML Linking Language] (see also Section 8
> Character Encoding in URI References of [Character Model]). This means
> that a wide range of internationalized resource identifiers can be
> specified when an anyURI is called for, and still be understood as URIs
> per [RFC 2396], as amended by [RFC 2732], where appropriate to identify
> resources.
Cheers,
Makoto
--
MURATA Makoto (FAMILY Given) <[EMAIL PROTECTED]>
YAHOO! GROUPS LINKS
- Visit your group "rng-users" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
