[Home] [By Thread] [By Date] [Recent Entries]
At 06:48 AM 15/01/98 -0500, David Megginson wrote: >The third alternative is, of course, to provide no access to this >information at all. I would do this only if I had clear indication >from the WG that data entities and notations are deprecated relics >from full SGML that will likely be removed in XML 1.1; otherwise, I >have to assume that, as in full SGML, they will be the standard method >for including non-XML objects such as graphics, audio, and video, and >that even a simple API needs to provide access to them. It is very unlikely that they'll be deprecated. But it is also highly unclear that they'll actually be used very much in the type of lightweight app that I think we're building SAX for. My incliniation would be to get elements, attributes, and text right first, then expand as need becomes clear. -Tim xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ To (un)subscribe, mailto:majordomo@i... the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
|

Cart



