[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Which XML Processor is behaving correctly.

  • To: "Doug Ransom" <Doug.Ransom@p...>,"Xml-Dev@Lists. Xml. Org (E-mail)" <xml-dev@l...>
  • Subject: RE: Which XML Processor is behaving correctly.
  • From: "Dare Obasanjo" <dareo@m...>
  • Date: Mon, 20 Jan 2003 16:32:59 -0800
  • Thread-index: AcLA1Tqq4bI5nwEKTleWaUYgpZR/ewADsIHg
  • Thread-topic: Which XML Processor is behaving correctly.

reference to undeclared namespace msxml
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

An expert is one who knows more and more about less and less until he
knows absolutely everything about nothing.                            

This posting is provided "AS IS" with no warranties, and confers no

> -----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);
> B  returns an error message "Reference to undeclared 
> namespace prefix: 'xsl'. Error processing resource 
> 'file:///D:/junk/foo.xml'. Line 1, Position 43 " due to the 
> use of a namespace within an entity definition. 
> <?xml version="1.0" encoding="iso-8859-1" ?> <!DOCTYPE 
> xsl:stylesheet [
> 	<!-- Namespaces -->
> 	<!ENTITY  xsl "http://www.w3.org/1999/XSL/Transform">
> 	<!-- Match strings -->
> 	<!ENTITY CopyAttsAndNodes 
> 	"<xsl:apply-templates select='node()|@*' />"> ]> 
> <xsl:stylesheet xmlns:xsl="&xsl;"> &CopyAttsAndNodes; 
> </xsl:stylesheet>
> Note the above sample is intended to be good xml, not 
> necessarily good xslt.  I ripped it out of a working XSLT.  
> Note both parsers are capable of expanding internal entity 
> references -- only when the prefix is included above does B 
> run into problems.
> I am leaning towards believing parser A behaving correctly, 
> because the infoset is the tree created after the entity 
> references have been expanded;  the entities in the DOCTYPE 
> section should be namespace unaware (i.e. just text).
> Doug Ransom
> Interoperability Architect
> Power Measurement
> 2195 Keating X Road
> Saanichton, BC, Canada  V8M 2A5
> Tel: 1-(250) 652-7100
> E-Mail: <mailto:doug.ransom@p...>
> Website: <http://www.pwrm.com/>
> ION(r)  smart energy everywhere(tm)
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org 
> <http://www.xml.org>, an initiative of OASIS 
> <http://www.oasis-open.org>
> The list archives are at http://lists.xml.org/archives/xml-dev/
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>


Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.

Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.