Cart
[Home] [By Thread] [By Date] [Recent Entries]
Let's say I develop software primarily for the Windows platform, in the consumer space. Let's say I'd like to get away from my products' proprietary file formats and use XML to allow the transfer of data between my applications, across the web, and into and out of databases. Why wouldn't I want to use the XML Data-derived schema language, data typing, etc., that Microsoft is using in Office 2000 and Internet Explorer 5? I can think of a few reasons why not to use it: No published specification (that I can find, anyway). Microsoft's XML pages refer you to W3C activity on XML Data that's at least 15 months old, and that does not match up closely to the XML published by Office 2000. Using DTD instead of the Microsoft XML schema would allow my data to be validated by more parsers and tools than just the MS/DataChannel parser. Someone else's schema definition might be better (but from what I can see, there is only a request for comments by the competing factions, dated 2/15/99). Then again, there are a few arguments in favor of using it: Microsoft and global domination. You can bet that all of the MS data access and programming tools (ADO, OLE DB, VB, VC++) will be built around it. Already in some kind of production today, even if it's not well documented. What would you do if you wanted to commit to a company-wide XML strategy today? Peter Zingg IMSI xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1 To (un)subscribe, mailto:majordomo@i... the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
|
