IBM Beats Microsoft Over the Head With Their Own Code
bednarz writes "IBM has added a twist to its new commitment to help OpenOffice.org battle Microsoft Office by donating code that was originally derived in part from a Microsoft-developed technology. IBM's iAccessible2, code-named Project Missouri, is a specification for technology used to help the visually impaired interact with Open Document Format (ODF)-compliant applications and was developed in part using Microsoft Active Accessibility (MAA). 'When the specification was donated to the Linux Foundation, Oracle, Sun, and SAP committed to help with future development. Mozilla is committed to incorporating it into its Firefox browser, and vendors GW Micro and Freedom Scientific will also use it in their own screen reader products. In addition, Project Missouri has won accolades from the American Association of People with Disabilities, the American Foundation for the Blind, and the National Federation of the Blind in Computer Science.'"
I don't know where "beats Microsoft over the head" comes in. IBM is donating Microsoft-developed code that empowers the blind to use software better.
Gee, I'm sure MS doesn't want that kind of bad PR...
Next up: Bill Gates donates large sums to the UN to help with immunizations! Oh, MS! BURRRNN!
These sensational headlines are kinda getting boring.
"Thanks for all the money you paid to us. We've used it to buy off ISO among other things" -Microsoft
This is now even more promising: a Microsoft spec, Lotus Notes code and a Brooksian army of offshored developers! It's hard to imagine how this couldn't work!
What I'm listening to now on Pandora...
in the Microsoft platform that many people never see or think about. We end up making extensive use of them for automated testing, actually.
It turns out that the same sort of API that makes it easier to build accessible products, whereby you can ask any UI element about its current visibility, text, or whatever, is also good for writing test automation. When you couple that with the ability to send windows events or messages to an arbitrary control, now you've got something foundational for doing automated UI testing in a pretty robust way.
Internally we work pretty hard on accessibility features because they're great for enabling users with different adaptive needs, they're required to sell to many government offices, and because they're excellent for our internal testing efforts.
My opinions are my own, and do not necessarily represent those of my employer.
More specifically, the IAccessible2 header files are copied almost directly from the OpenOffice.org UNO Accessibility API - the IAccessible2 headers contain a Sun copyright! See http://blogs.sun.com/korn/date/20070910 and http://blogs.sun.com/korn/date/20061214 for more on this.
Bear in mind that it's probably fairly old code.
I daresay IBM were granted sublicensing rights at a time when Microsoft hadn't even considered that such a license as the GPL could exist, let alone be in any sort of common use. I bet you anything you like they wouldn't license code in such a way today.
This is precisely why the license for OOo changed to LGPL (which happened just prior to OOo 2.0). Under the previous license, code did not need to be contributed back (and the OOo derived functionality in IBM's Lotus Notes 8 came from OOo 1.9.x). The big news in the IBM announcement is that IBM is returning to the community from whence it forked OOo, and contributing back (many? most? all) of their changes. One thing that is being highlighted (and discussed in this thread and erroneously attributed to a Microsoft original source) is that among their first contributions back is the newly created by them Windows edition of the accessibility work that they derived from OOo.