• To: "Karl Waclawek" <karl@w...>,<xml-dev@l...>
• Subject: RE: DTD parser in c#
• From: "Dare Obasanjo" <dareo@m...>
• Date: Mon, 29 Mar 2004 11:49:52 -0800
• Thread-index: AcQVxH8ZGaGV2leASDm/hz+gDxUenAAAoFiW
• Thread-topic: DTD parser in c#

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:karl@w...]
Sent: Mon 3/29/2004 11:31 AM
To: Dare Obasanjo; xml-dev@l...
Subject: Re:  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?

Karl

• Follow-Ups:
  • Re: DTD parser in c#
    • From: "Karl Waclawek" <karl@w...>
  • Re: DTD parser in c#
    • From: "Jeff Rafter" <lists@j...>

• Prev by Date: Re: DTD parser in c#
• Next by Date: Re: How to use SAX to validate XML against a schema?
• Previous by thread: RE: DTD parser in c#
• Next by thread: Re: DTD parser in c#
• Index(es):
  • Date
  • Thread