Hi folks,
After some valuable feedback from Glenn, here's a revised version of the
XMLDTDDescription (should this be renamed DTDDescription?) class. This is
based on the observation that to distinguish two DTD's, one might in
principle require the entirety of the (unparse) representation of their
internal subsets, as well as their root names, systemId's and publicId's.
Further, I've now assumed that what we'll want to cache is entire
DTD's--internal subset+external references--rather than particular
entities. This would certainly make DTD grammar management dramatically
easier--and more comprehensible--though there's the usual trade-off of
flexibility.
What do people think? Is this better than the former interface? This
wouldn't really be a part of XNI, so it isn't critical that we get it
absolutely right up-front; but the closer we get the easier everything else
will be.
public class XMLDTDDescription implements XMLGrammarDescription {
// return the root name of this DTD
public String getRootName();
// return the internal subset. Entities should not be expanded;
// this is simply the raw string representation of the stuff
// between [ and ]>
public String getInternalSubset ();
} // class XMLDTDDescription
Cheers,
Neil
P.s.: anyone have preferences on where this class and XSDescription should live? My
$0.02 would be to
put them in the appropriate packages under xerces.impl.
Neil Graham
XML Parser 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]
