Slashdot Mirror

"Linux and open-source software have had to contend with intellectual property legal challenges for years," writes ZDNet. "Now, Google has started a new effort to bring peace to potential Android IP sore points: PAX... a royalty-free, community-patent cross-license." PAX is starting with nine members: Google, Samsung Electronics, LG Electronics, HTC, Foxconn Technology Group, Coolpad, BQ, HMD Global, and Allview. These companies own more than 230,000 global patents. PAX's purpose is to create a "community-driven [patent] clearinghouse, developed together with our Android partners, [that] ensures that innovation and consumer choice -- not patent threats -- will continue to be key drivers of our Android ecosystem. PAX is free to join and open to anyone."
Slashdot reader Andy Updegroved writes: The question is why? The announcement and the related website are extremely brief, and although everyone is invited to get a copy of the cross license, Google reserves the right to decide first whether your motives are pure and you can keep a secret. And so far, the only members of the "PAX Community" listed are existing Google business partners. Is Google aware of some new patent tempest brewing just over the horizon, about to burst into public view? And will any other company names and logos be added to the PAX Community Web page? We'll just have to stay tuned to find out.
Andy Updegrove tells ZDNet it does involve "formal cross-licenses between participants, and therefore enforceable rights, but not an infrastructure to do more (at least insofar as one can tell from the initial announcement)."

Andy Updegrove writes: Humanity today is almost completely dependent on huge pharmaceutical companies to create the drugs we need. But these companies focus exclusively on drugs that can be sold at high prices to large populations — in other words, to patients in developed nations. This means that those who live in the emerging world that suffer from the remaining 'neglected diseases,' like Malaria and drug resistant TB, have no one to depend on for relief except huge charities, like the Gates Foundation. They also have no way to afford many of the patented drugs that do exist. But there is another way, modeled on open source software development, which relies on crowd sourced knowledge, highly distributed, volunteer efforts, and advanced open source tools. That methodology is called Open Source Pharma, and it has the potential to dramatically drive down drug development while saving millions of lives every year.

Andy Updegrove writes During the mobile platform patent wars of recent years Apple, Microsoft, Samsung, Motorola and the rest of the major vendors sought injunctions against each other to prevent their competitor from selling their products at all. The suits were often based on claims that a vendor had to pay a reasonable royalty on a 'standards essential patent.' The resulting litigation clogged up the courts, and the regulators were not amused. Now, after almost two years of vigorous debate, the standards development organization behind WiFi and thousands of other ICT standards (IEEE-SA) has received the blessing of the U.S. Dept. of Justice to forbid members that have pledged to license such patents from seeking an injunction until all other remedies have been exhausted. Whether other standards organizations will follow suit remains to be seen.

Andy Updegrove writes: The Linux Foundation this morning announced the latest addition to its family of major hosted open source initiatives: the Open Platform for NFV Project (OPNFV). Its mission is to develop and maintain a carrier-grade, integrated, open source reference platform for the telecom industry. Importantly, the thirty-eight founding members include not only cloud and service infrastructure vendors, but telecom service providers, developers and end users as well. The announcement of OPNFV highlights three of the most significant trends in IT: virtualization (the NFV part of the name refers to network function virtualization), moving software and services to the cloud, and collaboratively developing complex open source platforms in order to accelerate deployment of new business models while enabling interoperability across a wide range of products and services. The project is also significant for reflecting a growing recognition that open source projects need to incorporate open standards planning into their work programs from the beginning, rather than as an afterthought.

Andy Updegrove writes: "The U.K. Cabinet Office accomplished today what the Commonwealth of Massachusetts set out (unsuccessfully) to achieve ten years ago: it formally required compliance with the Open Document Format (ODF) by software to be purchased in the future across all government bodies. Compliance with any of the existing versions of OOXML, the competing document format championed by Microsoft, is neither required nor relevant. The announcement was made today by The Minister for the Cabinet Office, Francis Maude. Henceforth, ODF compliance will be required for documents intended to be shared or subject to collaboration. PDF/A or HTML compliance will be required for viewable government documents. The decision follows a long process that invited, and received, very extensive public input – over 500 comments in all."

Andy Updegrove writes "Three weeks ago, we heard that Francis Maude, a senior UK government minister, was predicting the conversion to open source office suites by UK government agencies. Lost in the translation in many stories was the fact that this was based not on an adopted policy, but on a proposal still open for public comment — and subject to change. It should be no surprise that Microsoft is trying to get the UK to add OOXML, its own format standard, to the UK policy. Why? According to a messaging sent to its UK partners, because it believes that a failure to include OOXML 'will cause problems for citizens and businesses who use office suites which don't support ODF, including many people who do not use a recent version of Microsoft Office or, for example, Pages on iOS and even Google Docs.' Of course, that's because Microsoft pushed OOXML as an alternative to ODF a decade ago. If you don't want the same objection to be valid a decade from now, consider making your views known at the Cabinet Office Standards Hub. The deadline is February 26."

Andy Updegrove writes "Between 2005 and 2008, an unparalleled standards war was waged between Microsoft, on the one hand, and IBM, Google, Oracle and additional companies on the other. At the heart of the battle were two document formats, one called ODF, developed by OASIS, a standards development consortium, and Open XML, a specification developed by Microsoft. Both were submitted to, and adopted by, global standards groups ISO/IEC. But then Microsoft never fully adopted its own standard. Instead, it implemented what it called 'Transitional Open XML,' which was better adapted for use in connection with documents created using older versions of Office. Yesterday, Microsoft announced in a blog entry that it will finally make it possible for Office users to open, edit and save documents in the format that ISO/IEC approved."

geek4 sends in an analysis indicating that Microsoft may have the most to lose if hedge-fund operator Elliot buys Novell. (The eWeekEurope piece is based on a longer and geekier writeup by Andy Updegrove on how the mechanics of unsolicited tender offers can play out in the tech world.) To avoid meltdown or asset-stripping, Novell can try and find a preferred bidder — a company with some interest in running Novell as a business, and preferrably a tech company. Or another company may make a move independently. But who might that be? A couple of analysts have suggested IBM, Oracle, or SAP. These all have problems... Microsoft is in a similar category, with one added problem. ... Microsoft has staked any open source credibility that it has on Novell's SUSE distribution. If Novell falls to bits, then Microsoft's efforts to gain open source cred pretty much disappear with it. It's something that would have been impossible to imagine a few years back, but if we're looking for someone to prop Novell up, Microsoft would now be a prime candidate."

Andy Updegrove writes "A short while ago the parties to one of the most closely watched FOSS cases filed a settlement agreement with the US Federal District Court for the Northern District of California ending one of the most important F/OSS legal cases to date. That case is Jacobsen vs. Katzer, and the settlement marks a complete victory for Jacobsen, a member of the Java Model Railroad Interface (JMRI) Project. Jacobsen's victory establishes several important rights for the first time in the US: the right to prevent their copyright and authorship acknowledgments from being removed from their code, and the right to collect damages if the terms of the licenses they choose are violated. Until now, those rights had never been tested in court."

Andy Updegrove writes "Think of the words 'standards war,' and if you're of a certain age you're likely to think of the battle between the Betamax and VHS video tape formats. Fast forward, and you'll recall we just finished another video standards war between most of the same companies, this time between HD DVD and Blu-ray. Well, here we go again, except this time its the movie studios that are duking it out, and DRM issues are a big part of it. On the one side are five of the six major studios, dozens of cable, hardware, software, distribution and device vendors, and on the other side there's just Disney — and maybe Apple as well, and that's enough to have the other side worried."

Andy Updegrove writes "As you may recall, Microsoft announced back on September 10 that it had launched a new, open source organization called the CodePlex Foundation. Since then, it has announced Project Acceptance and Operation Guidelines, its first 'Gallery' (a project area), supporting Microsoft's ASP.NET, and two projects in that gallery. But it had also launched in a 'less than open' state with an interim Board of Directors, and a promise to elect a permanent one in 100 days. Problem is, December 19 — the 100 day mark — passed quietly, with no announcement of a new Board or a status update on the other goals it had set for the launch period. So what's up with the CodePlex Foundation, and its pledge to promptly transition into a more independent organization?"

alphadogg writes 'Microsoft's new CodePlex Foundation has serious flaws to correct if it wants to become a credible force in the open source industry, and attract a diverse collection of developers and participants, according to an expert in forming consortia and foundations. Andy Updegrove, a lawyer and founder of ConsortiumInfo.org, says Microsoft has created with CodePlex a rigid foundation that has almost no wiggle room and a poorly crafted governance structure that concentrates authority at the top and leaves little power to others who might join the foundation.' Here is Andy's detailed analysis of CodePlex's structure: "Over the past 22 years, I've helped structure scores of open, consensus based consortia and foundations, and represented over 100 in all... In this blog entry, I'll show where I think the legal and governance structure of CodePlex has wandered off the open path, and offer specific recommendations for how the structure could be changed to give people (other than Microsoft business partners) confidence that CodePlex will be an organization worth joining."

Andy Updegrove writes "Long-time followers of the ODF-OOXML story will recall that there is a third editable, XML-based document format in the race to create the documentary record of history. That contender is called UOF, for Uniform Office Format, and it has been under development in China since 2002. Last summer, UOF was adopted as a Chinese National Standard, and on Friday the first complete office suite based upon UOF was released. It's called Evermore Integrated Office 2009 (EIOffice 2009 for short). How successful could this new entrant be in China? For starters, Evermore Software Co. Ltd., its developer, is reportedly the largest software vendor to the Chinese government. And then there's price: Evermore's professional edition is less than a quarter of the price of the comparable version of Office 2007. And finally, it's clearly no coincidence that on July 11, Evermore Vice President Cao Shen called for Microsoft to be the first target for China's new anti-monopoly law, which will take effect in just ten days' time. Whether Shen is speaking to, or for, the government remains to be seen."

An anonymous reader passes along word that ISO has responded to the four appeals filed against the approval of OOXML as a standard. To no one's surprise, ISO says that there was nothing wrong with the process. Groklaw's coverage is (as usual) the most comprehensive. Andy Updegrove summarizes ISO's position this way: "1. All judgments made during the course of the process were appropriately made under the applicable Directives. 2. The fact that the BRM voted on all proposed resolutions in some fashion satisfies the requirements of the Directives. 3. The fact that a sufficient percentage of National Bodies (NBs) ultimately voted to approve DIS 29500 ratifies the process and any flaws in that process. 4. Many objections, regardless of their merits, are irrelevant to the appeals process."

Andy Updegrove writes "About two hours ago, Microsoft announced that it will update Office 2007 to natively support ODF 1.1, but not to implement its own OOXML format. Not until Office 14 is released (no date given so far for that) will anyone be able to buy an OOXML ISO-compliant version. Why will Microsoft do this after so many years of refusal? Perhaps because the only way it can deliver a product to government customers that meets an ISO/IEC document format standard is by finally taking the plunge, and supporting 'that other format.' Still, many questions remain, such as when this upgrade will actually be released, how good a job it will do, and whether the API Microsoft has said it will make available to permit developers to supply 'save to ODF' default plugins will be supported by a patent non-assertion promise allowing implementations under the GPL (the upgrade supplied by Microsoft will not allow ODF as the default setting)."

Tokimasa notes a CNet blog predicting that OOXML will make the cut. Updegrove agrees, as does the OpenMalasia blog. Reports of irregularities continue to surface, such as this one from Norway — "The meeting: 27 people in the room, 4 of which were administrative staff from Standard Norge. The outcome: Of the 24 members attending, 19 disapproved, 5 approved. The result: The administrative staff decided that Norway wants to approve OOXML as an ISO standard." Groklaw adds reportage of odd processes in Germany and Croatia.

Andy Updegrove writes "The vote on Microsoft's OOXML closes today. The final result will not be announced (or leak) before sometime early next week. Meanwhile the votes of individual countries continue to come in, currently with more reported switching in favor of OOXML than against it. For the benefit of those who want to keep track of how the vote is tending until it's official, I'm posting the running tally of which votes have switched, what the net change has been, now many votes have come to light, and how many remain to be announced. It's likely that it will not be possible to know the final result until all votes are in, due to the complex double test for approval, and the complication that the final number of abstentions — and whether they move from 'yes' or 'no' votes — can decrease the total number of votes that need to switch to 'yes' in order for OOXML to be approved. For that reason, I also include the algorithm for arriving at a final result."

ericatcw writes "Critics have charged that last week's ISO Ballot Resolution Meeting (BRM) to decide the fate of changes to Office Open XML standards proposal was too perfunctory and deviated from accepted ISO practices, possibly in an attempt to smooth the passage of the Microsoft format. This week, the ISO 'convener' of the BRM disputed those charges, saying that voting to dispose of 900 changes to the spec at once and allowing 'O' Observer countries to vote were the correct moves. ISO released a statement backing him up. Also, Patrick Durusau, editor of the competing OpenDocument Format specification and a late convert to OOXML's passage, also said that claims the process was flawed were overstated."

Andy Updegrove writes "For a few years now we've been reading about the urgency of adopting open document formats to preserve written records. Now, a 74-page report from the Academy of Motion Picture Arts and Sciences warns that digital films are as vulnerable to loss as digitized documents, but vastly more expensive to preserve — as much as $208,569 per year. The reasons are the same for video as for documents: magnetic media degrade quickly, and formats continue to be created and abandoned. If this sounds familiar and worrisome, it should. We are rushing pell-mell into a future where we only focus on the exciting benefits of new technologies without considering the qualities of older technologies that are equally important — such as ease of preservation — that may be lost or fatally compromised when we migrate to a new whiz-bang technology." Here's a registration-free link for the NYTimes article cited in Andy's post.

Munchkinguy writes "First, they dropped support for their namesake OpenDocument Format and declared a switch to the W3C's 'Compound Document Format.' Then, W3C's Chris Lilley clarified that CDF 'was not created to be, and isn't suitable for use as, an office format.' Now, the Foundation has mysteriously closed up shop, leaving the following message: 'The OpenDocument Foundation, Inc. is closed. We sincerely wish our friends and associates in the OpenDocument Community all the best and much success going forward. Good-bye and good luck.'"

Andy Updegrove writes "Microsoft's OOXML did not get enough votes to be approved the first time around in ISO/IEC — notwithstanding the fact that many countries joined the Document Format and Languages committee in the months before voting closed, almost all of them voting to approve OOXML. Unfortunately, many of these countries also traded up to 'P' level membership at the last minute to gain more influence. Now the collateral damage is setting in. At least 50% of P members must vote (up, down, or abstain) on every standard at each ballot — and none of the new members are bothering to vote, despite repeated pleas from the committee chair. Not a single ballot has passed since the OOXML vote closed. In the chairman's words, the committee has 'ground to a halt.' Sad to say, there's no end in sight for this (formerly) very busy and influential standards committee."

Andy Updegrove writes "Public announcements of how Participating members of ISO have voted on OOXML are now rolling in one at a time, and the trend thus far is meaningfully weighted towards 'No with comments.' By my count, there are now four announced Yes votes, with comments, two abstentions, and seven public No with comments votes for OOXML in ISO/IEC JT1. Korea has reportedly voted no as well, and I expect at least Canada, Japan and the United Kingdom to announce 'No with comments' today or tomorrow. There will be more no votes on the roster when the final results are announced in a day or two. But even if the 11 votes I know of now were the only votes, the vote would now have failed — but for the 11 countries that upgraded their status from Observer to Participating member status in the last few weeks. Without those extra 11 'P' countries, it would only require 10 votes to block OOXML from immediate approval. If most or all of those additional 'P' members vote 'yes' as expected, it will confirm suspicions that Microsoft has promoted extra votes in favor of OOXML not only within National Bodies, but within ISO itself."

walterbyrd writes "Massachusetts has decided to use Microsoft's Open-XML standard. This decison: 'stands in sharp contrast to the positions taken by predecessor CIOs Peter Quinn and Louis Gutierrez, backed by then governor (and now-presidential hopeful) Mitt Romney. Both Quinn and Gutierrez insisted on including only "open standards" in the ETRM, and withstood significant pressure from Microsoft to give ground and accept OOXML...'"

Andy Updegrove writes "As you may know, V1, the INCITS Technical Committee that had charge of the US vote on Microsoft's OOXML, failed to reach consensus on either approving or disapproving the specification. As expected, Microsoft has turned to the full INCITS Executive Board in an effort to salvage the situation. Between now and Labor Day, a complicated series of fall-back ballots and meetings has been scheduled to see whether the Executive Board can agree to approve or disapprove OOXML, in either case "with comments." A vote to approve would mean that addressing the comments would not be required for the US vote to stand, while a vote to disapprove would hold the possibility of US approval if the comments are satisfactorily addressed. The bottom line is that a vote to approve (either in the US or in many other nations around the world) does not appear likely, due to the sheer number of technical issues that have been raised with OOXML, and the expedited schedule upon which Microsoft has insisted throughout the process."

Andy Updegrove writes "Today, Microsoft announced its own interoperability project to bridge the gap between China's domestically developed Uniform Office Format (UOF) and Microsoft's OOXML. In the continuing tit for tat battle between ODF and OOXML, this announcement tracks the intent of an already-existing 'harmonization' committee, hosted by OASIS, that is exploring interoperability options between ODF and UOF. Like the OOXML-ODF translator project announced by Microsoft last year, the new effort will be an open source project hosted by SourceForge. The announcement is, in one sense, no surprise. Microsoft has been waging a nation-by-nation battle for the hearts and minds of ISO/IEC JTC1 National Bodies, in an effort to win adoption of OOXML (now Ecma 376) as a global standard with equal status to ODF (now ISO 26300). In order to do so, it needs to offset the argument that one document format standard is not only enough, but preferable. With UOF representing a third entrant in the format race, easy translation of documents would obviously be key to lessen the burden on customers of products based upon one format or the other."

Andy Updegrove writes "By now you've probably read more than you want to about Microsoft's announcement that it owns 235 patents underlying leading open source software, including many opinions about whether Microsoft's new assertions do, or don't, represent a real threat to Linux, OpenOffice, and other OSS. To get to the bottom of the issue, though, you have to take a deep dive into how patent cross licensing works these days. When you do, you realize that patents don't mean what they used to, and have far more defensive than offensive value in the marketplace today. It also becomes apparent that it really doesn't matter whether Microsoft has valid patents or not, because so many other companies do as well. Today, what companies worry about isn't asserting their patents against other companies, but maintaining their freedom of activity. In this case, the open source community can simply ride the coattails of the major vendors, because Microsoft doesn't hold enough cards to win the hand, much less the game." Relatedly The Register is reporting that the author of the main report being used by Microsoft to support their patent claims has come out against Microsoft's interpretation of his work and Jonathan Schwartz gives some free advice to the overly litigious.

Andy Updegrove writes "Norway has become the latest European country to move closer to mandatory government use of ODF (and PDF). According to a press release provided in translation to me by an authoritative source, Norway now joins Belgium, Finland, and France (among other nations) in moving towards a final decision to require such use. The Norwegian recommendation was revealed by Minister of Renewal Heidi Grande Roys, on behalf of the Cabinet-appointed Norwegian Standards Council. If adopted, it would require all government agencies and services to use these two formats, and would permit other formats (such as OOXML) to be used only in a redundant capacity.Reflecting a pragmatic approach to the continuing consideration of OOXML by ISO/IEC JTC 1, the recommendation calls for Norway to 'promote the convergence of the ODF and OOXML, in order to avoid having two standards covering the same usage.' According to the press release, the recommendation will be the subject of open hearings, with opinions to be rendered to the Cabinet before August 20 this summer.The Cabinet would then make its own (and in this case binding) recommendation to the Norwegian government."

Andy Updegrove writes "Governments are beginning to realize that perhaps the Internet really has changed everything, at least for them, and that they are going to have to deal with new responsibilities in this area. How will they deal with financial and medical data breaches? What can they do to ensure that first responders will be able to communicate the next time that terrorists strike in the Homeland, and how will the refugees of the next Katrina be able to access their electronic medical records? And what must governments do to ensure that public records will be available in fifty years, if they no longer maintain paper archives? Whether government should incline towards leading, following or simply getting out of the way is a matter upon which there are likely to be strongly held differences of opinion. It's also likely, though, that government will not have the luxury of opting for the third choice in some of the areas just mentioned. How well government chooses among those roles, and how well it executes when it chooses to lead, will likely have a profound impact on our lives in the years ahead."

christian.einfeldt writes "Sun's Chairman Scott McNealy has asked the world's most populous nation to merge its Uniform Office Format with the Open Document Format. Tech lawyer Andy Updegrove thinks that McNealy would not have flown to China and taken this chance of rejection if McNealy didn't think that there was a good likelihood of success."

Andy Updegrove writes "A legislator in California has decided that it's time for California to get on the open formats bandwagon. If all of the bills filed in the last few weeks pass, California, Texas, and Minnesota will all require, in near-identical language, that 'all documents, including, but not limited to, text, spreadsheets, and presentations, produced by any state agency shall be created, exchanged, and preserved in an open extensible markup language-based, XML-based file format.' What type of formats will qualify? Again, the language is very uniform (the following is from the California statute): 'When deciding how to implement this section, the department in its evaluation of open, XML-based file formats shall consider all of the following features: (1) Interoperable among diverse internal and external platforms and applications; (2) Fully published and available royalty-free; (3) Implemented by multiple vendors; (4) Controlled by an open industry organization with a well-defined inclusive process for evolution of the standard.'"

Unpaid Schill writes "Over on the O'Reilly Network, there's an interesting piece about how Microsoft tried to hire people to contribute to Wikipedia. Not wanting to do the edits directly, they were looking for an intermediary to make edits and corrections favorable to them. Why? According to the article, it was apparently both to let people know that Microsoft will not 'enable death squads with their UUIDs' and also to fight the growing consensus that OOXML contains a useless pile of legacy crap which is unfit for standardization."

Andy Updegrove writes "On Sunday afternoon, the Free Standards Group (FSG) signed an agreement to combine forces with Open Source Development Labs (OSDL) to form a new organization — The Linux Foundation. The result of this consolidation will be to dedicate the resources of the combined membership to 'accelerate the growth of Linux by providing a comprehensive set of services to compete effectively with closed platforms.' Jim Zemlin, currently the head of FSG, will lead the new organization as its Executive Director. The new organization will continue to support Linux in a variety of ways, including by providing economic support to Linus Torvalds and other key kernel developers, managing the Linux trademark, and providing legal protection to developers through such initiatives as the Open Source as Prior Art project, the Patent Commons, and the Linux Legal Defense Fund. All in all, a tall order, but eminently possible given its membership: The Linux Foundation's founding members will include every major company in the Linux industry, including Fujitsu, Hitachi, HP, IBM, Intel, NEC, Novell, Oracle and Red Hat, as well as many community groups, universities and industry end users."

Andy Updegrove writes "Carol Sliwa at ComputerWorld has posted two excellent stories just now on ODF in Massachusetts, based on over 300 emails secured under the Massachusetts Public Records Law (the local analogue of the Federal Freedom of Information Act). The longer and more intriguing article focuses on Microsoft's lobbying efforts in Massachusetts, and confirms, as I reported last week, that Microsoft lobbyist Brian Burke was spearheading an effort to bring pressure on the state's Information Technology Division (ITD) by promoting an amendment that would have taken away much of the ITD's power to make technology policy. The article goes on to describe the back-channel negotiations between State CIO Louis Gutierrez and Microsoft's Alan Yates, and the way that Microsoft played the lobbying card throughout those discussions in an effort to protect its wildly profitable Office software franchise against potential erosion by competing products that support ODF." Andy has a blog entry on the lobbying effort.

Andy Updegrove writes "For the last year and a half, Massachusetts has been a battleground between Microsoft, on the one hand, and IBM, Sun and open standards advocates on the other over the state's plans to implement ODF. That effort has sparked similar initiatives around the world that threaten to erode Microsoft's multi-billion dollar profits on Office software. Now, we have a new governor set to take office, and observers are waiting to see if he will continue to support ODF like his predecessor, or back off in favor of Microsoft Office. Last week, Governor-Elect Deval Patrick named a new transition advisory group to make recommendations on the state's IT structure, and one of the eight members he appointed was none other than the Microsoft lobbyist that has been leading the charge to not only defeat ODF in the Bay State, but to gut the power of the State's CIO and Information Technology Division as well. Not a good sign of independence from special interests for an administration that has yet to even take office."

Andy Updegrove writes "Far too much attention has been paid to whether or not the Wikipedia is accurate enough. The greater significance of the Wikipedia today, and even more for those in the future, is its reality as the most detailed, comprehensive, concise, culturally-sensitive record of how humanity understands itself at any precise moment in time. Moreover, with its multiple language versions, it also demonstrates how different cultures understand the same facts, historical events and trends at the same time. Today, archaeologists are doing digs to understand how people lived only 150 years ago, making guesses based on the random bits and pieces of peoples' lives that they find. In the future, that won't be necessary, as archaeologists are replaced by anthropologists that mine this treasure-trove for data."

Andy Updegrove writes, "Microsoft has just posted the text of a new promise not to assert its patents with respect to 35 listed Web Services standards. The promise is similar to the covenant not to assert patents that it issued last year with respect to its Office 2003 XML Reference Schema, with two important improvements intended to make it more clearly compatible with open source licensing. Those changes are to add an explicit promise not to assert any relevant patents against anyone in the distribution chain of a product, from the original vendor through to the end user; and to clarify that the promise covers a partial as well as a full implementation of a standard. It's all part of a recent wave of such pledges made by companies such as IBM, Nokia, and Oracle, and a significant shift in how Microsoft is dealing with open standards."

Andy Updegrove writes "It's been a week now since Microsoft announced its ODF/Office open source converter project - time enough for 183 on-line stories to be written, as well as hundreds of blog entries (one expects) and untold numbers of appended comments. Lest all that virtual ink fade silently into obscurity, it seems like a good time to look back and try to figure out what it all means. In this entry, I report on a long chat with Microsoft's Director of Standards Affairs Jason Matusow, and match up his responses with the official messaging in the converter press release. The result is a picture of a continuing, if slow and jerky, evolution within Microsoft as those that recognize market demands for more openness debate those that want to follow the old way. This internal divide means that the proponents of change need to point to real market threats in order to justify incremental changes. This adaptation by reaction process leaves Microsoft still lagging the market, but has allowed those that favor a more open approach to gradually turn the battle ship a few degrees at a time."

Andy Updegrove writes "It's been a week now since Microsoft announced its ODF/Office open source converter project - time enough for 183 on-line stories to be written, as well as hundreds of blog entries (one expects) and untold numbers of appended comments. Lest all that virtual ink fade silently into obscurity, it seems like a good time to look back and try to figure out what it all means. In this entry, I report on a long chat with Microsoft's Director of Standards Affairs Jason Matusow, and match up his responses with the official messaging in the converter press release. The result is a picture of a continuing, if slow and jerky, evolution within Microsoft as those that recognize market demands for more openness debate those that want to follow the old way. This internal divide means that the proponents of change need to point to real market threats in order to justify incremental changes. This adaptation by reaction process leaves Microsoft still lagging the market, but has allowed those that favor a more open approach to gradually turn the battle ship a few degrees at a time."

Andy Updegrove writes "In this fourth in-depth interview focusing on ODF-compliant office productivity suites, I interview Dr. Martin Sommer, of Germany's SoftMaker Software. Most people know about OpenOffice, StarOffice, and KOffice, the ODF poster child software suites. But there are also other products available as well, including this one, which bundles word processing and spreadsheet capabilities (with more modules on the way), runs on both Windows, Linux and mobile platforms, is designed for home users, is available on-line, is localized in many languages - and is dirt cheap, besides. It's also been selected by AMD for use in connection with its ambitious "50x15" plan, which hopes to connect 50% of the world population to the Internet by 2015. This interview series amply demonstrates how a useful standard - in this case ODF - can rapidly lead to the evolution of a rich and growing environment of compliant products, providing customers with variety, choice, price competition, and proprietary as well as open source product alternatives - in stark contrast to the situation that has prevailed in office suite software for the last many years."

Andy Updegrove writes "In this fourth in-depth interview focusing on ODF-compliant office productivity suites, I interview Dr. Martin Sommer, of Germany's SoftMaker Software. Most people know about OpenOffice, StarOffice, and KOffice, the ODF poster child software suites. But there are also other products available as well, including this one, which bundles word processing and spreadsheet capabilities (with more modules on the way), runs on both Windows, Linux and mobile platforms, is designed for home users, is available on-line, is localized in many languages - and is dirt cheap, besides. It's also been selected by AMD for use in connection with its ambitious "50x15" plan, which hopes to connect 50% of the world population to the Internet by 2015. This interview series amply demonstrates how a useful standard - in this case ODF - can rapidly lead to the evolution of a rich and growing environment of compliant products, providing customers with variety, choice, price competition, and proprietary as well as open source product alternatives - in stark contrast to the situation that has prevailed in office suite software for the last many years."

Andy Updegrove writes "In early May, Massachusetts issued a 'Request for Information' on plugins that could help ease the transition from a Microsoft Office based environment to one relying on ODF compliant software. Now the seven responses received have been posted by the ITD: six from vendors large and small — and one from Microsoft that purports to be informational, but in fact gives no information beyond what is already publicly available. Like everything else in the ODF saga, many of the responses are as much political as technical, with some delivering off-topic messages, one (from the ODF Foundation, strangely) refusing to disclose much at all, and several contradicting each other on the technical challenge of working with Office absent further code disclosures by Microsoft. All in all, they make for an intriguing read on multiple levels — offering more of an Easter egg hunt than informative offering. It will be interesting to see which, if any, of these offerings the Mass. ITD decides to utilize."

Andy Updegrove writes "In early May, Massachusetts issued a 'Request for Information' on plugins that could help ease the transition from a Microsoft Office based environment to one relying on ODF compliant software. Now the seven responses received have been posted by the ITD: six from vendors large and small — and one from Microsoft that purports to be informational, but in fact gives no information beyond what is already publicly available. Like everything else in the ODF saga, many of the responses are as much political as technical, with some delivering off-topic messages, one (from the ODF Foundation, strangely) refusing to disclose much at all, and several contradicting each other on the technical challenge of working with Office absent further code disclosures by Microsoft. All in all, they make for an intriguing read on multiple levels — offering more of an Easter egg hunt than informative offering. It will be interesting to see which, if any, of these offerings the Mass. ITD decides to utilize."

Andy Updegrove writes "A big story in Massachusetts last week was the announcement by Microsoft that it would give $30 million in software to Bay State high schools and universities. Less noticed was the fact that an important economic stimulus bill adopted by the legislature lacked the amendment that sought to gut the power of the State CIO to set any new IT policies that might require compliance with certain standards (like ODF) or favor open source software. Should these two dots be connected, and if so, how? After all, why would Microsoft reward Massachusetts for taking no action to curtail an IT policy that favored ODF and rejected Microsoft's own XML format, especially after Microsoft has by all accounts lobbied so aggressively to bring about a change? As it happens, the fact is that the game isn't over yet: I've learned that the IT policy language hasn't been permanently defeated — its just been shifted out of sight to an 'outside section' of the current budget bill."

Andy Updegrove writes "A big story in Massachusetts last week was the announcement by Microsoft that it would give $30 million in software to Bay State high schools and universities. Less noticed was the fact that an important economic stimulus bill adopted by the legislature lacked the amendment that sought to gut the power of the State CIO to set any new IT policies that might require compliance with certain standards (like ODF) or favor open source software. Should these two dots be connected, and if so, how? After all, why would Microsoft reward Massachusetts for taking no action to curtail an IT policy that favored ODF and rejected Microsoft's own XML format, especially after Microsoft has by all accounts lobbied so aggressively to bring about a change? As it happens, the fact is that the game isn't over yet: I've learned that the IT policy language hasn't been permanently defeated — its just been shifted out of sight to an 'outside section' of the current budget bill."

Andy Updegrove writes "In this third interview in a continuing series, I interview Sun's Erwin Tenhumberg, in order to compare StarOffice 2.0 with the other leading software productivity suites that support ODF (previous interviews have focused on KOffice and OpenOffice). As in the previous interviews, Tenhumberg answers questions intended to showcase the strong (and the weak) points of his product in comparison to its competitors, and in order to showcase the rich and varied ecosystem of products that is growing up to support ODF. He also answers a second set of questions tailored to bring out what's unique about Sun's development efforts, and how StarOffice relates to OpenOffice. This interview is particularly informative on accessibility issues."

Andy Updegrove writes "In this third interview in a continuing series, I interview Sun's Erwin Tenhumberg, in order to compare StarOffice 2.0 with the other leading software productivity suites that support ODF (previous interviews have focused on KOffice and OpenOffice). As in the previous interviews, Tenhumberg answers questions intended to showcase the strong (and the weak) points of his product in comparison to its competitors, and in order to showcase the rich and varied ecosystem of products that is growing up to support ODF. He also answers a second set of questions tailored to bring out what's unique about Sun's development efforts, and how StarOffice relates to OpenOffice. This interview is particularly informative on accessibility issues."

Andy Updegrove writes "Recently, spokespersons for Microsoft's standards group have been promoting 'design, collaboration and licensing' as alternatives, rather than supplements to, open standards. There's an important difference between an open standard and any of these ad hoc arrangements among companies, however, and that is the fact that with a standard, everybody knows that they can get what everybody else can get, and on substantially the same terms. With a de facto standard, that's not the case - as Microsoft itself found out last week when Adobe refused to offer the same deal on saving files in PDF form that Apple and OpenOffice enjoy."

Andy Updegrove writes "Recently, spokespersons for Microsoft's standards group have been promoting 'design, collaboration and licensing' as alternatives, rather than supplements to, open standards. There's an important difference between an open standard and any of these ad hoc arrangements among companies, however, and that is the fact that with a standard, everybody knows that they can get what everybody else can get, and on substantially the same terms. With a de facto standard, that's not the case - as Microsoft itself found out last week when Adobe refused to offer the same deal on saving files in PDF form that Apple and OpenOffice enjoy."

Andy Updegrove writes "Before there was Linux, before there was open source, there was of course (and still is) an operating system called Unix that was robust, stable and widely admired. It was also available under license to anyone that wanted to use it, and partly for that reason many variants grew up and lost interoperability - and the Unix wars began. Those wars helped Microsoft displace Unix with Windows NT, which steadily gained market share until Linux, a Unix clone, in turn began to supplant NT. Unfortunately, one of the very things that makes Linux powerful also makes it vulnerable to the same type of fragmentation that helped to doom Unix - the open source licenses under which Linux distributions are created and made available. Happily, there is a remedy to avoid the end that befell Unix, and that remedy is open standards - specifically, the Linux Standards Base (LSB). The LSB is now an ISO/IEC standard, and was created by the Free Standards Group. In a recent interview, the FSG's Executive Director, Jim Zemlin, and CTO, Ian Murdock, creator of Debian GNU/Linux, tell how the FSG works collaboratively with the open source community to support the continued progress of Linux and other key open source software, and ensure that end users do not suffer the same type of lock in that traps licensees of proprietary software products."

Andy Updegrove writes "Before there was Linux, before there was open source, there was of course (and still is) an operating system called Unix that was robust, stable and widely admired. It was also available under license to anyone that wanted to use it, and partly for that reason many variants grew up and lost interoperability - and the Unix wars began. Those wars helped Microsoft displace Unix with Windows NT, which steadily gained market share until Linux, a Unix clone, in turn began to supplant NT. Unfortunately, one of the very things that makes Linux powerful also makes it vulnerable to the same type of fragmentation that helped to doom Unix - the open source licenses under which Linux distributions are created and made available. Happily, there is a remedy to avoid the end that befell Unix, and that remedy is open standards - specifically, the Linux Standards Base (LSB). The LSB is now an ISO/IEC standard, and was created by the Free Standards Group. In a recent interview, the FSG's Executive Director, Jim Zemlin, and CTO, Ian Murdock, creator of Debian GNU/Linux, tell how the FSG works collaboratively with the open source community to support the continued progress of Linux and other key open source software, and ensure that end users do not suffer the same type of lock in that traps licensees of proprietary software products."