> Isn't that a bug of the parser in view of
> http://www.w3.org/TR/xlink/#link-locators > (item 1), which is
> called from http://www.w3.org/TR/xmlschema-2/ section
> 3.2.17.1 lexical space of anyURI ?
OK... yes, it looks as if an unescaped "%" character _is_ permissible so
it looks as if Xerces is getting it wrong here?
FWIW, the MSXML parser does accepts a "%"... But then it also seems to
accept ü in a URI.... so not much help there then.
> Seems we're up in thin air...
>
> Uhhh....
Yes, I agree, trying to fathom inconsistent behaviour across parsers is
hellish.
But in answer to your question of whether a parser "encodes" a URI - by
which I understood you meant apply any required "escaping" for the
reserved characters in the content of an element typed as xs:anyURI - I
_think_ the answer is it doesn't, and if it is required that escaping
has to be done in the element content - but I'd like someone with more
experience than me to confirm that ;-)
Pete
|