[
Lists Home |
Date Index |
Thread Index
]
james anderson <james.anderson@setf.de> wrote:
| Bill de hÓra wrote:
|> In a namespaced world, t[XML elements] are not [self-contained]:
|>
|> elementname, namespace, elementprefix
|
| the programming problem is an artifact of the misconception that names
| in a namespaced world need be modeled at the application level as tuples.
True. They would need to be modeled as objects (in languages without
support for symbols.)
|> For a direct example of how the structural issues of using a tuple
|> affect code, see the SAX startElement call, and try operating on
|> various bits of markup with a handler. For anyone that has Dave
|> Brownell's SAX book, he has a good discussion on this. Or go through
|> the xml-dev archives..
|
| in this regard, maybe one should consider whether the sax interface
| and the sax processing model is all (or perhaps _is_) that one needs
| for working with namespaces.
It's one where the app has to do all the work, mainly because the API
dribbles out namespaced names in their parts, not as wholes. For
instance, where in SAX1 you get called with something on the order of
startElement( String gi, Attributes atts )
in SAX2 this ought to have been an "equivalent"
startElement( QName gi, Attributes atts )
But then, of course, there's the meta-question: why is such "abstraction"
necessary?
|
