[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: Why the Infoset?
Personally, I don't have any problems identifying the need for the infoset: I've seen so many people try to attach meaning to lexical distinctions that should not carry meaning that I yearn for an authority I can point to when telling them they're wrong. But the problem with the Infoset as currently defined is that it has had to make too many compromises. Creating a common abstraction with the constraint that XML, XML Namespaces, the DOM, and XPath should all conform with it is, I think, a requirement that has proved impossible to satisfy. Which perhaps explains why the Infoset and Canonical XML, which are both essentially trying to answer the same question, have come to different conclusions. We now have the perverse situation that the core infoset of a document does not contain enough information to generate its canonical form, and the canonical form does not contain enough information to generate its core infoset. For example the two documents below have the same core infoset but different canonical forms: 1: <x:a xmlns:x="one.uri"/> 2: <y:a xmlns:y="one.uri"/> While these two have the same canonical form but different core infosets: 1: <x:a xmlns:x="one.uri"><x:b/></x:a> 2: <x:a xmlns:x="one.uri"><x:b xmlns:x="one.uri"/></x:a> So in my book, the essential question "when do two XML documents convey the same information" remains unanswered. Mike 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
|