Martin Duerst wrote:
At 02:08 06/03/20, Elliotte Harold wrote:
>
>I would recommend against using xsd:anyURI for IRIs. A URI is much
more restrictive than an IRI, and one of the easiest things for a schema
validator to check about an xsd:anyURI is that it only contains
URI-legal ASCII characters.
This is indeed one of the easiest things, but it would be TOTALLY
wrong.
http://www.w3.org/TR/xmlschema-2/datatypes.html#anyURI says, among else:
The mapping from anyURI values to URIs is as defined by the URI
reference
escaping procedure 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.
If there is confusion in other venues about this issue, please help
to make sure it gets fixed.
Well,
maybe it's time that *some* specification adds new datatypes that do
*exactly* what RFC3986 and RFC3987 ask for :-)
Best regards, Julian
