OK, Well, ask a stupid question, get a good answer :)
Elisha > -----Original Message----- > From: Neil Graham [mailto:[EMAIL PROTECTED] > Sent: Monday, October 31, 2005 12:54 PM > To: [email protected] > Subject: RE: Xerces issues handling recursive schema includes > > Hi Elisha, > > > > > "Elisha Berns" <[EMAIL PROTECTED]> wrote on 10/31/2005 02:52:49 PM: > > > Hi Neil, > > > > Thanks for the reply. Just one question about this. The schema in > > question includes tens of other schema files using relative URIs (they > > all exist in a large directory structure). So by what you write > > > > "that system identifier fields are always set to the same value" > > > > presumably you mean that any SystemId will have the same exact URI and > > that the test for similarity is to first resolve the absolute path name > > for an InputSource? > > > > But how would you do this if a schema is retrieved over the web and it > > includes other schemas files with relative paths? > > Well, if you can't figure out when you've encountered a document for the > second time, you can be assured the parser won't be able to figure it out > either. :) > > The means of using an EntityResolver to map documents to unique system > URIs does assume that the application knows, or knows how to find out, > enough about the graph of schemas to be able to tell when it's encountered > something before. Since the application is more special-purpose than the > parser, this is usually an acceptable assumption. Your milage may vary, > but there's not much the parser can do at its level to help you if this > gets you nowhere at all. > > Cheers! > Neil > Neil Graham > Manager, C++ Compiler Front-End and Runtime Development > IBM Toronto Lab > Phone: 905-413-3519, T/L 969-3519 > E-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
