[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: [Sax-devel] RFE [ #496133 ] New resolver entry point
Norman Walsh wrote: > > So you propose to parse > > <xsl:stylesheet ...> > <xsl:import href="http://example.com/foo.xsl"/> > </xsl:stylesheet> > > without a resolver? > > I suspect that you contend that's the same as the external identifier > <!ENTITY foo SYSTEM "http://example.com/foo.xsl"> and you plan to > simply pass it through the entityResolver() hook. I think it's clear > that I disagree. Could you explain why you disagree? Why not pass the href into the SAX EntityResolver w/ publicID=null and systemID=@href? I can think of these reasons: 1) Your app may want two different resolutions of the same URI 2) You don't like mixing up XML REC entity resolution w/ the concept of general URI resolution If #1 is not the reason, then in #2, having two different resolvers seems like it would be more complex to write apps since you would need to at least provide two methods. -Edwin
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|