> I also take it as almost axiomatic that SAX should support everythin=
g in
> the spec *relevant to those areas it addresses*. IOW if it doesn't =
support
> NOTATION it could ignore everything to do with that (e.g. NDATA.
> NotationType) and might simply throw an Exception (SAX ignores NOTAT=
ION -
> or whatever). [I am not making any judgment on NOTATION - but it is=
> possibly not a core component].
I suggest that parsers using SAX should be more than welcome to
provide their own mechanisms for communicating information about
notations -- they are simply not part of the SAX information set. For
example, I might have this in the DTD:
<!NOTATION video SYSTEM "http://www.video.com/videospec">
<!ENTITY clip SYSTEM "video-clip.vid" NDATA video>
<!ELEMENT video-ptr EMPTY>
<!ATTLIST video-ptr
object ENTITY #REQUIRED>
and this in the document
<video-ptr object=3D"clip"/>
SAX will simply report that the attribute "object" has the value
"clip", without worrying that there is a notation called "video";
however, =C6lfred, for example, will let you look up the type of
"object", find out that it's an entity, look up the associated
notation, and then get the notation's system identifier.
All the best,
David
--=20
David Megginson ak117@freenet.carleton.ca
Microstar Software Ltd. dmeggins@microstar.com
http://home.sprynet.com/sprynet/dmeggins/