Showing posts with label software patents. Show all posts
Showing posts with label software patents. Show all posts

Friday, July 27, 2007

Liberate your documents

odf

from: http://www.redhatmagazine.com/2007/07/25/odf-the-inevitable-format/

ODF: The inevitable format
by T. Colin Dodd

In 1999, a scientist wanted to look at some data from soil samples collected on Mars in 1975 by the Viking lander. He wanted to test a theory about detecting the existence of Martian bacteria and microbes–in other words, finding life on Mars. The scientist thought he would find what he needed on a NASA website somewhere, but it wasn’t that easy. The original data had been misplaced, and when the huge magnetic tapes that stored the data were found, they were “in a format so old that the programmers who knew it had died.” Someone finally found a ream of paper printouts propping a door open and humanity’s understanding of the universe expanded a bit more. The tragic sense that would have accompanied the loss of this knowledge is echoed in accounts of the destruction of the Library at Alexandria, and probably why book-burnings are seen as a sure sign that a society is unhealthy

Of course, not all lost or inaccessible data holds clues to life on Mars, and not every shred of information needs to outlive its creator. Many unreadable documents will never be missed, but responsible public policy demands that government documents–contracts, deeds, or court records that remain in force for decades or even centuries–must be archived and accessible. Whatever the case, when data is stored and shared on legacy or defunct proprietary formats, over time it will either become expensive to access or disappear entirely.

When it comes to digitally creating, sharing, and storing documents, the technology to prevent format-based decay already exists and is in wide (and growing) use. It’s called the Open Document Format (ODF) and if you’re not currently using it, someday you will.

The ODF, an XML-based document markup language, was first developed in 1999 by Stardivision and then by Sun Microsystem’s Openoffice.org project. Conceived as an open alternative to the proprietary document handling software, which then dominated the world, the driving force behind the ODF was the need for a vendor-neutral document format independent of any single application, readable and writable for all, without any royalty of licensing “encumbrances.” It was promoted on the basis that business and taxpayers would save money. An open format would create competition in the document application sphere. All documents could be read and shared by everyone. Nothing could be lost to time or changes in proprietary code or licensing requirements. Matters of great public interest - census data, weather data, public health statistics, investigative reports, court records and basic scientific research, all paid for by taxpayers, would no longer be encoded on a single, proprietary closed-standard format, requiring citizens to pay twice for access to their own information. Using ODF, proponents said, would keep public documents public.

The Organization for the Advancement of Structured Information Standards (OASIS) was formed in 2002 to standardize the format, which was recognized by the International Organization for Standardization (ISO) in 2006. The Open Document Format Alliance was formed in March of 2006 to promote the format, making the public, legal and political case for the adoption of open technology standards to governments and public institutions.

“Red Hat was a founding member of the ODF Alliance and Tom Rabon [Vice President of Corporate Affairs] serves on the executive committee,” says Stephanie McGarrah, outgoing Red Hat Public Policy Manager. “Red Hat works with other executive committee members to coordinate efforts to talk with governments around the world about ODF.”

Although the ODF was launched with a great gust of common sense blowing at its back, the momentum of widespread adoption has been hindered by bureaucratic inertia, local politics, persistent misconceptions (reinforced by opponents) about ODF’s viability and the “dangers” of adoption. Most of the fear, uncertainty and doubt has emanated from one source, on whose proprietary formats most of the world’s documents currently reside.

Opponents of the ODF do not concede its inevitable adoption, and actively lobby against it. It’s not that anyone is against the ODF in and of itself, or finds any real reason to question its necessity. The logic behind the ODF and the transparency of its creation is fairly unassailable. Rather, it is the open standards on which the ODF is based that are most attacked. From the detractors’ point of view, things are just fine the way they are now. The “standard” is theirs. They own the document “market,” and think of it as “territory” they “won” fair and square. They can’t foresee a future without them (that’s not in their business plan), and as long as everybody is already using their applications and formats, why change? Opponents of the ODF devote considerable resources to lobbying legislatures and executive branch IT advisory boards in an attempt to convince them that the adoption of the ODF actually limits choice and harms market-driven efficiency by “locking out” vendors like them. They say migration is expensive, and even argue that adoption of the ODF will limit public access by cluttering the environment with too many “incompatible” formats. And who really trusts all this “free stuff,” anyway?

But proponents like the ODF Alliance have arguments of their own, and most of them come from “Actually, the opposite is true…” school of refutation.

The ODF Alliance contends that open standards actually promote choice and vendor competition by leveling the playing field. The standard is open and freely available for anyone to implement. There is no competition over the format, just the application used to handle it. In this universe, the best applications win. The ODF alliance also points out that implementing or migrating to ODF is no more complicated or costly than periodically upgrading from one version of a proprietary application to the next, and by obviating the need for future upgrades, real money is saved over time. As for accessibility, Open Office (and other ODF-compliant applications) are freely down-loadable and ready to use now. There are no actual compatibility issues, they say, only non-cooperation issues.

“I think that some governments either aren’t aware of ODF or don’t have the technical staff in place who understand the value of ODF,” McGarrah explains. “So, it’s the alliance’s job to spread that message to the people in government who make those decisions.”

But the unshakable argument in favor of using ODF for public documents is the fact that it’s a better deal for citizens and taxpayers in the long run. Using closed-standard, proprietary software for public documents is like buying the proverbial $10,000 toilet seat, or prohibiting the federal government from negotiating better drug prices with pharmaceutical companies on behalf of Medicaid and Medicare patients, or trying to feed an army and rebuild a warzone by awarding secret, non-competitive, no-bid contracts. It’s non-competitive in the worst sense.

Despite opposition, adoption of the ODF is making slow but inexorable headway, and as a greater understanding of the issue is reached by policymakers, the ODF will challenge the standing ubiquity of proprietary formats. Moving the issue forward, Japan recently required that all its ministries contract with software vendors whose applications are built around open standards. Brazil, Poland, Malaysia, Italy, Korea, Norway, France, The Netherlands, Denmark, Belgium, The Commonwealth of Massachusetts, and the Dehli State Government in India have all made commitments in principle to adopting the ODF and, perhaps more importantly, recognizing the imperative of using open standards. The ODF Alliance continues to arm and enlighten policy-makers with the information and tools they need to make recommendations and change policy, but no one promoting the ODF think its widespread adoption is imminent. It will take time.

“These decision makers have a lot of other issues to deal with (i.e. Health care, education, transportation, poverty…) so technology decisions aren’t usually at the top of their lists,” says McGarrah. “Progress has been made on the wider adoption of ODF. Several governments have adopted ODF and are working to implement the standard, but there is a lot of work to do.”

More information
Spread the word, share this ODF artwork by Michael Pittman

This entry was posted by T. Colin Dodd on Wednesday, July 25th, 2007 at 2:01 pm

Monday, December 18, 2006

a letter from Knuth to the U.S. Patent Office in Sept. 2003.

Art_of_Computer_Programming_-_Cover


Letter to the Patent Office
From Professor Donald Knuth

Commissioner of Patents and Trademarks
Box 4
Patent and Trademark Office
Washington, DC 20231

Dear Commissioner:

Along with many other computer scientists, I would like to ask you to reconsider the current policy of giving patents for computational processes. I find a considerable anxiety throughout the community of practicing computer scientists that decisions by the patent courts and the Patent and Trademark Office are making life much more difficult for programmers.

In the period 1945-1980, it was generally believed that patent law did not pertain to software. However, it now appears that some people have received patents for algorithms of practical importance--e.g., Lempel-Ziv compression and RSA public key encryption--and are now legally preventing other programmers from using these algorithms.

This is a serious change from the previous policy under which the computer revolution became possible, and I fear this change will be harmful for society. It certainly would have had a profoundly negative effect on my own work: For example, I developed software called TeX that is now used to produce more than 90% of all books and journals in mathematics and physics and to produce hundreds of thousands of technical reports in all scientific disciplines. If software patents had been commonplace in 1980, I would not have been able to create such a system, nor would I probably have ever thought of doing it, nor can I imagine anyone else doing so.

I am told that the courts are trying to make a distinction between mathematical algorithms and nonmathematical algorithms. To a computer scientist, this makes no sense, because every algorithm is as mathematical as anything could be. An algorithm is an abstract concept unrelated to physical laws of the universe.

Nor is it possible to distinguish between "numerical" and "nonnumerical" algorithms, as if numbers were somehow different from other kinds of precise information. All data are numbers, and all numbers are data. Mathematicians work much more with symbolic entities than with numbers.

Therefore the idea of passing laws that say some kinds of algorithms belong to mathematics and some do not strikes me as absurd as the 19th century attempts of the Indiana legislature to pass a law that the ratio of a circle's circumference to its diameter is exactly 3, not approximately 3.1416. It's like the medieval church ruling that the sun revolves about the earth. Man-made laws can be significantly helpful but not when they contradict fundamental truths.

Congress wisely decided long ago that mathematical things cannot be patented. Surely nobody could apply mathematics if it were necessary to pay a license fee whenever the theorem of Pythagoras is employed. The basic algorithmic ideas that people are now rushing to patent are so fundamental, the result threatens to be like what would happen if we allowed authors to have patents on individual words and concepts. Novelists or journalists would be unable to write stories unless their publishers had permission from the owners of the words. Algorithms are exactly as basic to software as words are to writers, because they are the fundamental building blocks needed to make interesting products. What would happen if individual lawyers could patent their methods of defense, or if Supreme Court justices could patent their precedents?

I realize that the patent courts try their best to serve society when they formulate patent law. The Patent Office has fulfilled this mission admirably with respect to aspects of technology that involve concrete laws of physics rather than abstract laws of thought. I myself have a few patents on hardware devices. But I strongly believe that the recent trend to patenting algorithms is of benefit only to a very small number of attorneys and inventors, while it is seriously harmful to the vast majority of people who want to do useful things with computers.

When I think of the computer programs I require daily to get my own work done, I cannot help but realize that none of them would exist today if software patents had been prevalent in the 1960s and 1970s. Changing the rules now will have the effect of freezing progress at essentially its current level. If present trends continue, the only recourse available to the majority of America's brilliant software developers will be to give up software or to emigrate. The U.S.A. will soon lose its dominant position.

Please do what you can to reverse this alarming trend. There are far better ways to protect the intellectual property rights of software developers than to take away their right to use fundamental building blocks.

Sincerely,
Donald E. Knuth
Professor Emeritus

Links:

http://lpf.ai.mit.edu/Newsletter/programming.freedom.11.html

http://lpf.ai.mit.edu/Patents/knuth-to-pto.txt

http://www.pluto.it/files/meeting1999/atti/no-patents/brevetti/docs/knuth_letter_en.html

http://en.wikipedia.org/wiki/The_Art_of_Computer_Programming

http://en.wikipedia.org/wiki/Donald_Knuth

http://www-cs-staff.stanford.edu/~knuth/

http://www.digital-copyright.ca/discuss/1104

http://swpat.ffii.org/gasnu/knuth/swpatknuth.en.pdf

http://swpat.ffii.org/gasnu/knuth/index.en.html