> From [log in to unmask] Thu Oct 17 18:10 MET 2002
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> X-Priority: 3 (Normal)
> X-MSMail-Priority: Normal
> Importance: Normal
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
> Date: Thu, 17 Oct 2002 17:12:10 +0100
> From: Pete Johnston <[log in to unmask]>
> Subject: Re: URIs in XML encoding of DC and RSS 2.0
> To: [log in to unmask]
>
> > 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 ;-)
Probably there is a chance for an XML validator to escape work:
Say the validator finds the entire document well-formed. Then it might
might believe, that executing whitespace handling and the full
escape mechanism will deliver a valid URIref.
The issue for a subsequent application then would be to figure,
which URIref is intended -
that is the subsequent application would have to do the escape work.
Whatever...think we need to get an "authoritive" answer - otherwise
we probably will store wrong stuff in databases or XSLTs to create
RDF run crazy (maybe miss a necessary escape algorithm or do one to much) -
By the way: To my great pleasure XML 1.1 will slightly extend the notion
"well-formed" - more fun with character escape issues ahead....
This type of questions i honestly hate.
rs
>
> Pete
>
>
|