Altova Mailing List Archives

Re: [xml-dev] Shouldn't colon be reserved?

From: Tom Bradford <bradford@----------.--->
To: <keith@---.--->
Date: 9/9/2002 7:04:00 PM
On Monday, September 9, 2002, at 11:05 AM, Keith W. Boone wrote:
> According to Tom Bradford:
>> But let's be honest.  Very few applications, perhaps only those that
>> have lived in a vacuum since 1997, can get by without having to be
>> namespace aware.  Just about anything that a person might actually want
>> to *do* with or to a document requires namespaces.
> That's a blanket statement.  It may hold true for some, but certainly 
> not
> all users of XML.  I regularly develop applications using XML that have 
> no a
> priori requirement to deal with namespaces.  There are a large number of
> developers like me who use XML for purposes like serialization of data
> structures, or marking up text documents, that could care less about 
> them.

I don't think it's a blanket statement at all.  Any application that 
utilizes any specification developed by the W3C over the past few years, 
other than XML 1.0 itself, must, even if you don't care, be 
namespace-aware.  This is what I mean by 'all the stuff that you might 
want to *do* with or to a document'.  If an application developer can 
live happily only having to parse and serialize non-namespaced data, 
then they should consider themselves lucky.

> It is ridiculous to assume that everyone needs or requires namespaces, 
> and
> I'm glad its an optional part of XML.

Who said that I believe everyone needs and/or requires namespaces?  
Personally, I avoid them like the plague.  They present API layerings 
that I'd much rather live without.

Tom Bradford - CTO - The dbXML Group -
Apache Xindice (XML Database) -
Labrador (Web Services Hub) -


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.