[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] RE: repercussions
> > It is now crystal-clear that allowing qnames to escape from element & > > attribute names into content was a terrible mistake that we're now > > stuck with forever. I struggled against this idea but lost. -Tim > > > Well, we're not stuck with these things "forever." If they are really > lorts more trouble than they are worth, Father Darwin will fix them by Right. I don't think many people rely on qnames in content, or when they do only for very limited scenarios. There are many places that qnames in content just don't work (get treated as opaque strings so test equal with different ns uris, fail to copy relevant namespace decls when cloning subtrees, and so on). The Darwinian situation doesn't look good for qnames in content.
|
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
|