Gates Embraces Web Service Interoperability
djh101010 writes "In a CNN article which looks more like something out of The Onion, Bill Gates expresses his interest in participating in interoperability with rival technologies, through common standards. Specifically mentioned are IBM's WebSphere, and Linux. 'We're being as inclusive as we can,' Gates said of Microsoft's role in the cross-platform project. 'This is a fabric for someone to do e-commerce that's independent of the operating systems that are out there.'
The point is just because he said lots of fuzzy words today it doesn't mean he won't try to "cut off the oxygen supply" of those same groups tomorrow. Is he suddenly buddy-buddy with Linux? Nope, his company is still fighting it tooth and nail around the world, putting out FUD, doing whatever it takes to head it off at the pass.
Good PR moments such as this do not negate the overall approach Gates will take. Do not be fooled, he's the same old monopolist.
The whole POINT of XML is interoperability. So can this XML be used by someone else? Is it limited to Office?
If the namespaces can't be reused by another applicaiton, then NO, it isn't "cool" what MS did. It's the classic MS crap. They may as well have forgone the entire process and left it in a binary format.
"Proprietary" XML is marketing blather and not something that adds value to the end user...
Computer Science is Applied Philosophy
Standards from Microsoft are dangerous, even when royalty-free licensing is offered so that they can be implemented in Free Software.
Consider for example the ECMA standards 334 and 335 for the core parts of .NET - while Microsoft has promised royalty-free licensing for any and all patents that may be neccessary for implementing that standard, they are at the same time embracing and extending their own standard, and they have filed at least one patent application that seems to be designed to give them a monopoly on their extensions to the standard.
In some situations it may work to simply refuse to go along with the standards attempts from MS. Unfortunately, MS has so much leverage that this won't always work. For example, with .NET just ignoring it IMO won't work, that's why we're working on creating a competing "standard set of libraries" for the stuff which goes beyond the stuff that is safe from patent-based attacks (the safe parts are what is specified in the ECMA specs, for which MS has promised royalty-free licensing, plus everything which is thin wrappers around stuff that is simply too old to be affected by .NET patents, such as for example System.Windows.Forms). The strategy of the DotGNU project is to re-use a good number of existing Free Software libs (written in C) and compile them for .NET - again since those libs are old, they're safe from being affected by any .NET patents.
Greetings,
Norbert.
Let me clarify for you:
I send him the file with basic formatting and it looks fine in Word 2000. (office 2000) I send him the file and he opens it, and the words are in the wrong place, the formatting is either gone or changed.
This is even based on templates from within Word itself. He even sent me the file back to make sure it wasn't corrupted, and the file was fine on word 2000.
This is _not_ a user error, it's simple lack of proper backwards compatibility.