• To: Dare Obasanjo <dareo@m...>
• Subject: Re: Which XML Processor is behaving correctly.
• From: Bill de hÓra <bill.dehora@p...>
• Date: Tue, 21 Jan 2003 11:00:33 +0000
• Cc: Doug Ransom <Doug.Ransom@p...>, "Xml-Dev@Lists. Xml. Org (E-mail)" <xml-dev@l...>
• Organization: Propylon
• References: <B885BEDCB3664E4AB1C72F1D85CB29F804B7C822@R...>
• Reply-to: bill.dehora@p...
• User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826

Dare Obasanjo wrote:
> I believe parser A is correct and parser B is not. We currently do not
> handle this case correctly in the most recent versions of MSXML. The XML
> parser in the System.Xml namespace of the .NET Framework handles this
> correctly. 
> 

(OT: do consider not using a top posting style on this list - it 
makes browsing threads you're involved in a two pass effort as well 
as having to skip over your .sig - aside from the fact that placing 
your sig in the middle of a post will truncate that post in some muas)


-----Original Message-----
 > From: Doug Ransom [mailto:Doug.Ransom@p...]
 > Sent: Monday, January 20, 2003 2:43 PM
 > To: Xml-Dev@Lists. Xml. Org (E-mail)
 >
 > I have one parser ("A") that loads the document inline below,
 > and one that does not (B);
 > [...]

A - entity expansion should really complete before either the 
namespace or XSLT lavels start kicking in. B /might/ be correct for 
an external entity (the parser is not always obligated to read it in)

Bill de hÓra

• Follow-Ups:
  • Re: Which XML Processor is behaving correctly.
    • From: "J.Pietschmann" <j3322ptm@y...>

• References:
  • RE: Which XML Processor is behaving correctly.
    • From: "Dare Obasanjo" <dareo@m...>

• Prev by Date: OT: adobe svg plugin namespacing problem
• Next by Date: Re: problem with #&233; characters and such in URL
• Previous by thread: RE: Which XML Processor is behaving correctly.
• Next by thread: Re: Which XML Processor is behaving correctly.
• Index(es):
  • Date
  • Thread