|
[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: What should TrAX look like? (Was: Re: Article on
> > I suspect it would be much cleaner to take an approach like > Jaxen's. In > this approach there's a core set of basic operations that all > model-connectors must implement (getChild, getAttribute, getParent, > etc.). However most other axes have default implementations > that build > on top of the basic operations. For instance, the ancestor axis is > easily implemented on top of getParent. Thus a minimal implementation > only has to provide about 20 fairly straight-forward operations. This is similar to the design of Saxon's NodeInfo interface, except that in NodeInfo there are no methods such as getParent and getChild, instead the provider must implement a minimum set of axes: ancestor, child, attribute. For other axes, the provider can call on helper implementations provided by Saxon. Michael Kay
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|
|||||||||

Cart








