Lists Home |
Date Index |
No, there is no intention to ship a SAX implementation. That doesn't change the fact that namespaces beginning with System.* are assumed to be core .NET Framework classes. This is the same way in Java package names beginning with java.* are assumed to be core parts of the JDK.
The latest version of the namespace naming guidelines for the .NET Framework are located at http://longhorn.msdn.microsoft.com/lhsdk/ndp/cpconnamespacenamingguidelines.aspx
PITHY WORDS OF WISDOM
Blessed are the meek for they shall inherit the Earth, minus 40% inheritance tax.
From: Karl Waclawek [mailto:email@example.com]
Sent: Mon 3/29/2004 11:31 AM
To: Dare Obasanjo; firstname.lastname@example.org
Subject: Re: [xml-dev] DTD parser in c#
> Just out of curiosity, if we one day Microsoft decided to ship a SAX
> implementation in the .NET Framework wouldn't this clash with the namespace
> names you have chosen? Perhaps we need some namespace naming guidelines
> for .NET libraries.
So, are you going to ship a SAX implementation?
System.Xml.Sax would be the most logical namespace, and I was using
it as I was pretty sure MS had abandoned SAX.
So, if third parties supply basic/system type libraries,
what namespaces should they use - if MS claims sole ownership
to the System namespace?