Re: NSXMLDocument

>> There's no reason why there can't be two implementations available  
>> in base ... we already have two versions of NSXMLParser ... one  
>> using libxml2 which is fairly strict about getting valid XML, the  
>> other writing in pure objective-c and tolerant of the invalid XML  
>> produced by some of the Apple tools.

If Apple's own implementation is a wrapper around libxml2, how do they  
manage to parse this invalid XML that their own tools produce ? ;-)

Maybe they set some permissive flags in libxml2 ?

Thanks