[
Lists Home |
Date Index |
Thread Index
]
Our XML APIs support both internal and external entities. If you are
having difficulty with finding the .NET Framework SDK documentation
online, the link for the section on working with XML is
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide
/html/cpconemployingxmlinnetframework.asp
If you have problems with our APIs you and can provide a bug report plus
repro you can either post to one of our newsgroups
(microsoft.public.dotnet.xml) or mail me directly.
--
PITHY WORDS OF WISDOM
The hurrier you go, the behinder you get.
This posting is provided "AS IS" with no warranties, and confers no
rights.
>
>
> -----Original Message-----
> From: Doug Ransom [mailto:Doug.Ransom@pwrm.com]
> Sent: Tuesday, December 17, 2002 6:46 PM
> To: Xml-Dev@Lists. Xml. Org (E-mail)
>
> With the Microsoft .net (dotnet) platform, it seems one
> really has to go out of ones way to develop code which can
> read an XML file with entity references, even internal entity
> references. I ran into this when I tried some XSLT programs
> that worked successfully with saxon (java based xslt
> processor) and msxsl (COM based xslt processor) with a .net
> based XSLT processor.
>
> The default mechanismsms (XMLReader and XMLDocument) to load
> and read XML documents or XSLT programs simply fail when
> presented with a valid XSLT program which is serialized in
> valid XML.
>
> I wonder if a whole bunch of existing XML files that work
> fine with existing applications are going to break new
> applications designed to work with the same XML documents
> (i.e. a .net XSLT processor to replace msxsl). I suspect
> there are a fair number of valid XML documents out there that
> simply won't parse under .net.
>
> I think Microsoft has essentially removed entity references
> from XML, because now document authors won't dare produce XML
> documents that the majority of programs built on the .net
> platform will barf on. Users will be pretty upset at an
> author if they receive an XML document from them which won't
> load with their .net program.
>
> The WS-Interoperability profile also suggests entities not be
> used in SOAP messages. It seems like there are two versions
> of XML now; one that works with .net and WS-I, and an XML
> 1.0 document with a DOCTYPE section that cannot be parsed by
> what will replace the most commonly used XML Platform (as
> .net replaces COM on windows).
>
> Any comments? Maybe removing entity references is a good
> thing (I know implementators of embedded system platforms
> think so), and mabe Microsoft is doing the right thing by
> making entity expansion a thing developers have to go out of
> their way to make their software perform.
>
>
> Doug Ransom
>
>
>
> -----------------------------------------------------------------
> 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>
>
>
|
