Slashdot Mirror
Microsoft Releases First Open XML SDK
Kurtz'sKompund tips us to news that Microsoft has released a finished version of the Open XML software development kit. Microsoft has made additional resources available with the download. Quoting Techworld:
"The SDK includes an application programming interface (API) simplifying the creation of code for searching documents, creating documents, validating document parts, modifying data and other tasks, Microsoft said. The API can be used in any language supported by the Microsoft .Net Framework, the company said. The current SDK supports the version of Open XML supported by Office 2007, which is not the same as that ratified as a standard by the ISO, due to changes effected during the ratification process."
"It's a trap!"
Circumcision is child abuse.
This is Microsoft Office 2007 Open XML, not Open XML. An API for producing documents containing deprecated features is of no use to anyone bar Microsoft, who can claim tha they are making available tools that support a yet-to-be-defined standard.
For all we know, the next version of Office will support the officially defined and documented standard, which will have hundreds of changes compared to the current O2K7 format of Open XML. Thus, everyone will have to recode all new stuff just to stay in sync. A wasted effort, in my opinion.
If you keep throwing chairs, one day you'll break windows....
The current SDK supports the version of Open XML supported by Office 2007, which is not the same as that ratified as a standard by the ISO, due to changes effected during the ratification process.
Because anyone who follows Microsoft knows the game is to never have the two match.
Continue the charade all you want microsoft, but we don't buy it, and your mockery of the open standards process is now under heavy attack in the form of appeals.
Nobody but the people you pay to think otherwise is fooled.
VLC FOR MAC IS DYING! IF YOU DEVELOP, PLEASE SAVE IT!!
The "API" is useless without a fully documented format. The API will die over time just as certainly as the applications that use it. The only real answer to long term data storage is full documentation that can be used to create applications, on any platform, free of encumbrances, that can read and format the documents that you create on your systems that you've paid for.
An API for suck does not undo the suck.
This is my signature. There are many signatures like it, but this one is mine.
What a steaming pile of bullshit! First off, it hasn't really been ratified yet, ahem. Second, the draft that Microsoft submitted did not match the version used in Office 2007, before any changes were made.
> The current SDK supports the version of Open XML supported by Office 2007, which is not
> the same as that ratified as a standard by the ISO
No version of Microsoft's "Open XML" has been ratified as a standard by the ISO.
Warning: this article may contain humor, sarcasm, parody, and perhaps even irony. Read at your own risk.
Copyright infringement is "piracy" in the same way DRM is "consumer rape"
"You can use the Open XML API in any language supported by the Microsoft .NET Framework®. The help topics presented in this SDK provide code samples in Microsoft Visual C#® and Microsoft Visual Basic® .NET."
Instead, just call it OOXML.
I hate to break it to you, but Microsoft only has a product to sell there in the first place by the grace of those countries' copyright laws. Since they are the sovereign entities, not Microsoft, if Microsoft tried to pull that kind of stunt they'd be well within their rights to simply declare Microsoft's software to be Public Domain and use it all they want!
"[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz
MSFT's next initiative: Source Open Software (SOS), to source all software technology from open source. By ISO submission time the word 'Source' will be dropped and it will simply be known as the Open Software Standard, at which time all lawsuit against MS shall be dismissed due to the fact that the 'OS' in Windows product line will no longer stand for 'operating system'... Hey Microsoft, pay me for the idea! I patented it...
Others have said no, it needs (x) so let me add one.
No, it needs to be ignored. Let's talk to the customers on this one.
A businessman's hope for his business is that it persist and grow for several decades at least, until he can reap his reward and exit phenomenally wealthy. If you architect your business intelligence on the platform of a corporation whose business model is to obsolete its platforms every five years at the most, you're an idiot and you deserve to be have your resources drained by this decade's P.T. Barnum until in the ferocious environment of the day you and your grand ideas are forgotten.
In the public sector the objective is to conduct the public's business in such a way that resources are not wasted and required openness can be delivered. It's essential that the public's investment in creating information is well preserved. If you're in the public sector and architect public infrastructure on such a platform as Office 2007 OXML you're worse than incompetent - you're a traitor to the cause of public service.
OOXML is irrelevant. The problem of construction of a document is solved. The user interface is an interesting diverse field where members compete but all the options that don't lead to truly open documents are blind alleys. Office 2007 formats are some of these blind alleys that will yield only wasted efforts because the vendor needs to obsolete your documents every five years in order to maintain its current cash flow. If you succeed in hitching your cart to this train it will come off its rails in less than five years when the provider needs to sell you new applications. Why would you do that? Trust me, if you're in public service and you choose to do that eventually somebody is going to follow the money right to you. Have you got longer than that to retirement? If you're in business the problem will solve itself and not to your benefit.
Help stamp out iliturcy.
Uh, everything in DotNet is implemented in a proprietary dev environment. This has nothing to do with the openness of standards being implemented. Setting aside your initial claim that the ISO is supposed to validate a standard as being free of patents (which I don't believe to be true), the GP post seemed to be trying to claim that the fact that Microsoft happens to be providing a DotNet SDK has some kind of relevance to this standard not being open.
The DotNet API is not "the" API. It's an API that Microsoft provides. Furthermore this API, nor any other API for OOXML is the standard -- it's just a method of using the standard. The fact that Microsoft has created an API to help some of their paying customers to manage OOXML documents more easily really has nothing to do with whether OOXML is a good standard. The standard -- good or bad -- is the definition of the format, not the method of accessing it.
Microsoft provides DotNet APIs for working with standards such as SMTP, TCP/IP, HTML, GZip, and a whole host of standards that probably everyone would agree are open. Do you think this somehow compromises their open-ness? It also provides DotNet APIs for a heap of things that aren't open, or are even very Microsoft-specific. But it's not the presence of Microsoft APIs that makes those standards closed -- it's the fact that the standards aren't clearly published in a way that allows them to be implemented.
It's actually valid to argue that nobody else can write a valid API based on the specification, but this doesn't seem to be what either yourself or the GP post, or most of the responses to this article for that matter, are doing. Trying to draw some kind of imaginary causation between the standard being broken and Microsoft happening to provide a method of using it more easily on its own platform is ridiculous.