> D: FWIW I have been hacking namespaces into JUMBO2 and seem to require two
> classes:
> Namespace (one for each distinct xmlns in the document)
> UniversalName (One for each distinct elementType and each distinct attribute)
Okay. Do we really need UniversalName as a *class*, or is it sufficient
(as I continue to believe) to represent it as a String, possibly
interned? If the latter, then my ParserFilter approach will work
fine, returning all element names in the universal form of
URI + delimiter + localPart (where URI can be null), and all
attribute names in the form URI + delimiter + localPart for
global attributes, and URI + delimiter + elementLocalPart + delimiter
+ localPart for local attributes.
> If SAX can (a) process the minimisation completely and (b) return
> Namespaces for the document and (c) return a universal name for each
> Element and Attribute then I think I shall be very happy. From what various
> people have said it seems fairly straightforward.
Using my ParserFilter approach, of course, no parsers need to change
at all to support namespaces: it becomes an *application* issue,
but supported by a *universal* piece of machinery. Ditto with
inherited attributes generally.
-- John Cowan http://www.ccil.org/~cowan cowan@ccil.org You tollerday donsk? N. You tolkatiff scowegian? Nn. You spigotty anglease? Nnn. You phonio saxo? Nnnn. Clear all so! 'Tis a Jute.... (Finnegans Wake 16.5)