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

Re: Re: [Sax-devel] RFE [ #496133 ] New resolver entry point

  • To: Edwin Goei <edwingo@s...>
  • Subject: Re: Re: [Sax-devel] RFE [ #496133 ] New resolver entry point
  • From: Daniel Veillard <veillard@r...>
  • Date: Fri, 25 Jan 2002 18:49:35 -0500
  • Cc: Norman Walsh <ndw@n...>, sax-devel@l..., "xml-dev@l..." <xml-dev@l...>
  • In-reply-to: <3C51AFCC.C97910DB@s...>; from edwingo@s... on Fri, Jan 25, 2002 at 11:19:40AM -0800
  • References: <87666iq9ye.fsf@n...> <0f0601c19569$4f44d3e0$6800000a@b...> <87elkwvs1q.fsf@n...> <22cc01c19ad0$516c1f40$6800000a@b...> <87d70gtywn.fsf@n...> <251b01c19af5$d61a5700$6800000a@b...> <87n0zdgglw.fsf@n...> <026d01c1a5cb$09909920$6800000a@b...> <87pu3yz35o.fsf@n...> <3C51AFCC.C97910DB@s...>
  • Reply-to: veillard@r...
  • User-agent: Mutt/1.2.5.1i

different resolutions xslt xsl stylesheet
On Fri, Jan 25, 2002 at 11:19:40AM -0800, Edwin Goei wrote:
> 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.

  I actually expressed disagreement with Norm on this point while implementing
XML Catalog in libxml. Basically nobody except the XML Catalog group seems
to understand why the resolution of an URI reference here and there should
be different but they stick to the position that it's trivially different
without any good explanation.

  I think Norm and TimBL should talk about it at a W3C TAG meeting, and
get back with an answer saying if they should be different, and if yes why !!!

   Have fun :-)

Daniel

P.S.: as said already I really like the XML catalog spec except for this 
     bizarre duality of the 7.1 and 7.2 resolution mechanism which forces the
     code doing an URI reference based catalog lookup to know the *context*
     of that reference once the XML-Base has been computed and the RFC-2396 
     algorithm has been applied to build the URI used for the actual
     reference. This seriously break layering, and for no known reason.

-- 
Daniel Veillard      | Red Hat Network https://rhn.redhat.com/
veillard@r...  | libxml Gnome XML XSLT toolkit  http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/

PURCHASE STYLUS STUDIO ONLINE TODAY!

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.
Email
First Name
Last Name
Company
Subscribe in XML format
RSS 2.0
Atom 0.3
 

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.


Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

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.