SAX is no longer very useful. DOM is OK, but the tree traversal is difficult. XPath is the way to go, I think. Declarative node retrievals rather than iterative logic. XQuery is also very interesting. XQuery APIs and products are relatively immature. XSLT is complex, but much more mature.
Sabina wrote:What one is trying to say by the following?
I just do not understand what this mix of technologies has in common (because I am not familiar with ones that underlined)? Or is it just blabbering about everything....SAX is no longer very useful. DOM is OK, but the tree traversal is difficult. XPath is the way to go, I think. Declarative node retrievals rather than iterative logic. XQuery is also very interesting. XQuery APIs and products are relatively immature. XSLT is complex, but much more mature.
Sabina
leprechaun wrote:He probably wanted to emphasize that the direct access to the information you need is preferred over the iterative approach. Instead of going thru the whole lot of data until you find what you need, you just go straight there following the correct reference/path.
Sabina wrote:What one is trying to say by the following?SAX is no longer very useful. DOM is OK, but the tree traversal is difficult. XPath is the way to go, I think. Declarative node retrievals rather than iterative logic. XQuery is also very interesting. XQuery APIs and products are relatively immature. XSLT is complex, but much more mature.
XPath is a language for addressing parts of an XML document, designed to be used by both XSLT and XPointer.
Definition: XQuery operates on the abstract, logical structure of an XML document, rather than its surface syntax. This logical structure is known as the data model, which is defined in the [XQuery 1.0 and XPath 2.0 Data Model] document.]
XQuery Version 1.0 is an extension of XPath Version 2.0.
geek7 wrote:%90 "Я знаю карате, дзюдо, айкидо и еще ДО.. в общем много страшных слов"
Парсер использует .SAX чтобы построить DOM ..
если DOM is OK,.. "SAX is no longer very useful."
