Lists Home |
Date Index |
- From: Chris Maden <email@example.com>
- To: firstname.lastname@example.org
- Date: Fri, 4 Dec 1998 16:47:15 -0500 (EST)
[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.
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.
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.
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.
<!NOTATION SGML.Geek PUBLIC "-//Anonymous//NOTATION SGML Geek//EN">
<!ENTITY crism PUBLIC "-//O'Reilly//NONSGML Christopher R. Maden//EN"
<USMAIL>90 Sherman Street, Cambridge, MA 02140 USA" NDATA SGML.Geek>
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)