• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: NSXLMDocument and malformed XML
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSXLMDocument and malformed XML


  • Subject: Re: NSXLMDocument and malformed XML
  • From: Chris Gregg <email@hidden>
  • Date: Fri, 26 May 2006 15:21:55 -0400
  • Thread-topic: NSXLMDocument and malformed XML

Thanks for the NSXMLParser suggestion -- it worked like a charm.  Cheers!

-Chris

On 5/26/06 12:26 AM, "Klaus Backert" <email@hidden> wrote:

> Hi,
>
> NSXMLDocument has an option NSXMLDocumentTidyXML for
> initWithContentsOfURL:option:error:. The documentation says: "Changes
> malformed XML into valid XML during processing of the document".
>
> This would be a devastating functionality for a xml parser.
>
> But look at this from the Tree-Based XML Programming Guide:
> "Note: Even though the NSXMLParser has the same prefix as the NSXML
> classes, it is not part of NSXML. It is based on a different model
> for processing XML".
> Therefore, some may say, "the" parser is not involved, and everything
> is ok ;-)
>
> But the input data has to be parsed with NSXML too, of course. If
> malformed XML is changed into valid XML during processing, then this
> parser is not conformant to the W3C recommendations for xml parsers.
> This is really bad.
>
> There are opportunities for Chris:
> (a) Try the NSXMLDocumentTidyXML option with NSXML.
> (b) Try NSXMLParser, calling [theParser setShouldProcessNamespaces:
> YES], because NO is the default value.
>
> Klaus
>
> Am 26.05.2006 um 02:31 schrieb Greg Herlihy:
>
>> An XML parser is not allowed to perform any type of error recovery
>> after
>> detecting that the XML document it is parsing is malformed. Rather the
>> parser must notify the application of the error and must stop
>> parsing the
>> document at that point (though the parser is allowed to search the
>> remainder
>> of the document for possible, additional errors and report them as
>> well.)
>
> <snip>
>>
>> The XML (and XHTML) philosophy avoids this entire debacle. All XML
>> parsers
>> adhere only to standard, defined behavior. An application
>> generating or
>> parsing XML documents pledges not to go off on its own - and
>> pretend to
>> understand a document that it does not. But it is exactly this
>> tough-minded,
>> intolerant approach that really serves the user's best interests
>> when the
>> entire picture is considered as a whole.
>>
>> Greg


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Re: NSXLMDocument and malformed XML (From: Klaus Backert <email@hidden>)

  • Prev by Date: Writing out a BOOL value to a .plist
  • Next by Date: Re: Core data dependent attributes
  • Previous by thread: Re: NSXLMDocument and malformed XML
  • Next by thread: Re: NSXLMDocument and malformed XML
  • Index(es):
    • Date
    • Thread