Cart
[Home] [By Thread] [By Date] [Recent Entries]
Elliotte Harold wrote: > It occurred to me that it might be possible to design this as some > sort of iterator interface like DOM's NodeIterator. Streaming > implementations would only be able to walk this in a forward fashion. I can see this working for pull parsers, but it's not clear to me how it might integrate with a callback-style API. > Then there could be a tree-based subclass of this interface that > added methods for moving backwards, and along the independent axes. This is exactly what I proposed: >> an object resembling a tree navigator that can be used to iterate >> over the nodes in the tree and retrieve individidual node objects >> (more complex but object model agnostic, should perhaps be combined >> with a property (a URI?) indicating the object model(s) supported). As well as navigating around the tree (previous, next, first-child, parent) it could be used to retrieve properties of the current node (name, type, value), using a node adapter specific to the object model. -- Chris Burdess
|
