[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: SAX 2.0 baseURI property was: Re: SAX 2.0 Enhancement proposal(2nd Ed)
Jonathan Borden wrote: > > > > Can I take that as a vote for option (b) - the creation of a new property, > > leaving the systemId to contain just the system identifier from the xml > > document? > > Yes, to be clear, and for reasons including this, but also for other > reasons, SAX needs to have a standard way to communicate the base URI to an > application. > > > If we are going to have a property containing the baseURI, there > > is no need to overload the systemId parameter with it. > > perhaps this is true. Given an (absolute URI form) systemId and a base URI, > cannot we -reconstruct- a relative URI used to get from the base URI to the > systemId in URI space: i.e. > > relativeURI = absolutizedSystemId - baseURI > > via an inverse of the rules that create: absolutizedSystemId = baseURI + > relativeURI > > (where + and - are not literal string operations but rather represent the > absolutization transform in RFC 2396) > Jonathan, I like this proposal... a lot. Unless I am missing something I imagine others will feel the same. It has the advantage of leaving EntityResolver, DTDHandler and Locator unchanged, but seems to provide the required information. When others have had a chance to respond I will re-amend my proposal. Regards Rob --- Rob Lugt ElCel Technology http://www.elcel.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC