SAX and delayed entity loading

Chris Maden crism at
Fri Dec 4 21:49:30 GMT 1998

[W. Eliot Kimber]
> Let's try this code from my PHyLIS tool, which associates grove
> constructor objects (COM objects in this case, because I'm
> implementing on Windows), with the external IDs for the notations
> those grove constructors support.  A grove constructor is a software
> component that takes an entity (or another grove or subgrove) as
> input and constructs a grove from it.

I don't think anyone was arguing that it's not possible to associate
notations with processing.

Here's why MIME is better than notations for general use:

o Usable in and out of XML.
  MIME is meaningful to MIME processors; notations are meaningful to
  XML processors.  XML processors can easily be MIME processors; the
  reverse is not true, especially for legacy reasons.

o Hierarchical.
  MIME has built-in fallback behavior.  Notations do not.  You've
  shown that it's possible to implement fallback, but it's not
  inherent in the system.

o Interchangeable.
  MIME works now, and it works well.  Notations *could* work in
  interchange, but they don't now.  If you give someone a notation
  declaration, odds are good that their software won't immediately
  know what to do with things in that notation.

o Flexible.
  As Liam pointed out, data notation information properly belongs with
  an entity.  XML stores that information with the *reference* to the
  entity, a place where the information is not always know.

So, I would recommend that we standardize an FPI for MIME itself, and
use that as the notation declaration for any external entity.  The
processor can then determine the actual data content notation of the
entity just as it would for any other object (explicit MIME type, file
extension lookup) and take appropriate action.

<!ENTITY crism PUBLIC "-//O'Reilly//NONSGML Christopher R. Maden//EN"
"<URL> <TEL>+1.617.499.7487
<USMAIL>90 Sherman Street, Cambridge, MA 02140 USA" NDATA SGML.Geek>

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at
Archived as:
To (un)subscribe, mailto:majordomo at the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at

More information about the Xml-dev mailing list