/ Henri Sivonen <[EMAIL PROTECTED]> was heard to say: | Is it really the best practice to use xsd:anyURI and sweep the | discrepancies under the rug
Yes, I think so. The definition of xsd:anyURI is pretty broad in
Schema 1.0 and in Schema 1.1 it's proposed definition[1] is:
[Definition:] anyURI represents an Internationalized Resource
Identifier Reference (IRI). An anyURI value can be absolute or
relative, and may have an optional fragment identifier (i.e., it may
be an IRI Reference). This type should be used when the value
fulfills the role of an IRI, as defined in [RFC 3987] or its
successor(s) in the IETF Standards Track.
| Can xsd:anyURI be
| augmented with a regexp pattern to restrict "spaces and a few other
| ASCII characters" in such a way that the resulting datatype
| restriction matches the definition of IRI?
I'm sure it can. As John points out, a really big, ugly regex. Just
out of curiosity, can you describe the application where you want this
level of validity checking on IRI values?
Be seeing you,
norm
[1] http://www.w3.org/TR/2006/WD-xmlschema11-2-20060217/#anyURI
--
Norman Walsh <[EMAIL PROTECTED]> | It is good to have an end to
http://nwalsh.com/ | journey toward; but it is the
| journey that matters, in the
| end.--Ursula K. LeGuin
pgpp4yshRL6Ig.pgp
Description: PGP signature
