Altova Mailing List Archives

RE: [xml-dev] The prefix "fgdc" for element "fgdc:fgdc" is not bound

From: "Nassar, Anthony" <ANassar@----.--->
To: <xml-dev@-----.---.--->
Date: 12/12/2007 7:29:00 PM
I hunted around, and I found this at "The
schema spec (like XSLT) generally treats the
set-of-names-in-no-namespace in the same way as a namespace, despite the
perverse insistence of the Namespaces Rec that this set of names is not
a namespace at all." Dr. Kay, when you say "perverse," are you being
ironic, i.e. you admire the recommendation's insistence, but agree that
it's unenforceable, or you disagree? 

Fwiw, Bjarne Stroustrup writes of the "pollution of the global
namespace" wrt using-declarations in C++. 

-----Original Message-----
From: Nassar, Anthony [mailto:ANassar@H...] 
Sent: Wednesday, December 12, 2007 10:54 AM
To: xml-dev@l...
Subject: RE: [xml-dev] The prefix "fgdc" for element "fgdc:fgdc" is not

I'm pretty sure that this has been explained to numerous newbies, but I
have to ask again. I've been asked to "do something" about the Nunit
test results schema, which starts out like this:



These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.