[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: About Infosets
Title: RE: About Infosets > -----Original Message-----
> So, what is needed to help access an infoset is an API
> Maybe some political good reasons behind this decision.
I don't think the DOM group is asleep ... dazed maybe, by trying to make sense out of the implications of one abstract InfoSet, multiple data models, the distinct but partially-overlapping roles of Schemas and DTDs, whatever the PSVI really is, and the fact that it looks like multiple XML Schema specifications are going to viable in the Real World. My post at http://lists.xml.org/archives/xml-dev/200103/msg00183.html went through some of the very real dilemmas that the group faces in trying to do an XPath API. I assure you that they are not "political", or knee-jerk opposition to Microsoft innovations. A year ago I thought that a simple selectNodes-like interface was an expedient way of offering an API to extract nodelists from xpath expressions. It turns out that Microsoft has (quite pragmatically) skated around some of the thin ice, but a W3C WG has little choice but to rigorously define what the relationship between the DOM and XPath data model is, how to specify bind namespaces to the XPath expression, and how to handle the implication that a NodeList returned by the XPath expression would stay "live" as the tree changes. I won't defend the W3C "front desk" for filling the deck with Jokers, but I'm convinced that the DOM group is playing the hand it was dealt about as well as it can.
|
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
|