[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: XTRE1160: The fragment identifier {62;n} is not a

Subject: Re: XTRE1160: The fragment identifier {62;n} is not a valid NCName
From: "Andrew Welch" <andrew.j.welch@xxxxxxxxx>
Date: Wed, 19 Nov 2008 17:03:42 +0000
Re:  XTRE1160: The fragment identifier {62;n} is not a
2008/11/19 Michael Kay <mike@xxxxxxxxxxxx>:
> Saxon isn't 100% conformant in its handling of fragment identifiers, though
> it's a pretty fuzzy area and I'm not sure it really affects the outcome in
> this case. The reality is that when URIs are processed using the JAXP
> URIResolver concept, Saxon has no knowledge of a media type, so it cannot
> interpret a fragment identifier in a way that depends on the media type, and
> it therefore treats it as an NCName irrespective of the actual media type.
> But the root cause of the problem is that the "#" in the URI, if it is to be
> interpreted as an ordinary character, should have been escaped as %23.
> Except that in this case, the error is deeper, in that "&amp;#62;" should
> have been "&#62;".

Thanks - do I take it from that then, that it's not really feasible to
pass the kind of dubious double-escaped markup you get in RSS feeds to
the URIResolver using the data: scheme?

Andrew Welch
Kernow: http://kernowforsaxon.sf.net/

Current Thread


Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3
Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.