Showing posts with label gnu gpl. Show all posts
Showing posts with label gnu gpl. Show all posts

16 September 2009

From the GNU GPL to GISAID's EpiFlu

A few months ago, I wrote about GISAID, which takes a rather interesting and - to readers of this blog, at least - familiar approach to sharing genomic data:

Registered users can upload data relating to sequences, clinical manifestations in humans, epidemiology, observations in poultry and other animals, etc. These data will be accessible to all other registered users, but not to others unless they have agreed to the same terms of use. This maintains confidentiality of the data.

This is, of course, the same as the GNU GPL: do as you would be done by - if you want to use the GPL'd code, you can, but you must share with everyone the results of your work if you decide to share it with anyone.

The GNU GPL was radical in its time, and the GISAID approach with its EpiFlu database, containing flu virus sequences, is also challenging - and meeting its own obstacles:

Today, the GISAID database (which is called EpiFlu) features both genomic and epidemiological data on tens of thousands of virus samples. At least until recently, the project seemed to be working. During the H1N1 outbreak, so many sequences were being submitted so quickly that researchers were literally watching clusters of outbreaks in real time.

Then, in July of 2009, the Swiss Institute of Bioinformatics (SIB) in Geneva, which has managed the database since 2006, removed EpiFlu from the GISAID Web site, making it available only to users redirected to SIB's Web site. SIB claims that GISAID had breached contract by failing to pay its bills on time, thereby relinquishing its rights to the database.

Let's hope that the SIB comes to its senses before it loses more of its credibility as a modern scientific organisation. Its high-handed claiming of "rights" to a commons created by others is simply not acceptable in the 21st century - which, if it has a future, will be one based around precisely the kind of sharing practised by GISAID.

Follow me @glynmoody on Twitter or identi.ca.

15 September 2009

Nonplussed by Non-Commercial

One of the vexed issues in the world of Creative Commons licensing is what, exactly, is meant by "non-commercial" use. In an attempt to clarify things, the Creative Commons people have commissioned a study, which has now appeared. Here are some of the highlights according to the press release:

Creative Commons noncommercial licenses preclude use of a work “in any manner that is primarily intended for or directed toward commercial advantage or private monetary compensation.” The majority of respondents (87% of creators, 85% of users) replied that the definition was “essentially the same as” (43% of creators, 42% of users) or “different from but still compatible with” (44% of creators, 43% of users) theirs. Only 7% of creators and 11% of users replied that the term was “different from and incompatible with” their definition.

Other highlights from the study include the rating by content creators and users of different uses of online content as either “commercial” or “noncommercial” on a scale of 1-100, where 1 is “definitely noncommercial” and 100 is “definitely commercial.” On this scale, creators and users (84.6 and 82.6, respectively) both rate uses in connection with online advertising generally as “commercial.” However, more specific use cases revealed that many interpretations are fact-specific. For example, creators and users gave the specific use case “not-for-profit organization uses work on its site, organization makes enough money from ads to cover hosting costs” ratings of 59.2 and 71.7, respectively.

On the same scale, creators and users (89.4 and 91.7, respectively) both rate uses in which money is made as being commercial, yet again those ratings are lower in use cases specifying cost recovery or use by not-for-profits. Finally, both groups rate “personal or private” use as noncommercial, though creators did so less strongly than users (24.3 and 16.0, respectively, on the same scale).

In open access polls, CC’s global network of “friends and family” rate some uses differently from the U.S. online population—although direct empirical comparisons may not be drawn from these data. For example, creators and users in these polls rate uses by not-for-profit organizations with advertisements as a means of cost recovery at 35.7 and 40.3, respectively—somewhat more noncommercial. They also rate “personal or private” use as strongly noncommercial—8.2 and 7.8, respectively—again on a scale of 1-100 where 1 is “definitely noncommercial” and 100 is “definitely commercial.”

I hope you got all that, for I certainly didn't. All that comes across to me from these figures is that "non-commercial" is so fluid a concept as to be useless.

The Creative Commons people rather created a rod for their own backs when they allowed this particular licence, which was bound to problematic. Indeed, it's striking that the GNU GPL, which doesn't allow this restriction, avoids all these issues entirely. Probably too late now to do anything about it...other than commissioning surveys, of course.

Follow me @glynmoody on Twitter or identi.ca.

19 June 2009

Opening up: New York Senate's Doing It *Now*

Vancouver may have promised that it will do it, the New York Senate is actually opening up completely now:

Welcome to the Open NYSenate

To pursue its commitment to transparency and openness the New York State Senate is undertaking a cutting-edge program to not only release data, but help empower citizens and give back to the community. Under this program the New York Senate will, for the first time ever, give developers and other users direct access to its data through APIs and release its original software to the public. By placing the data and technological developments generated by the Senate in the public domain, the New York Senate hopes to invigorate, empower and engage citizens in policy creation and dialogue.

...

Original Software

As a user of Open-Source software the New York Senate wants to help give back to the community that has given it so much - including this website. To meet its needs the Senate is constantly devleoping new code and fixing existing bugs. Not only does the Senate recognize that it has a responsibility to give back to the Open Source community, but public developments, made with public money should be public.

...

Data Sets

The New York Senate's Open Data page is the official repository of all government data. There you can browse through data produced by and considered by the Senate in their original forms as well as various other file types created for your convenience; including but not limited to: Excel spreadsheets, .csv, text files and PDFs. To supplement the source data it is making available, the Senate has also created the Plain Language Initiative designed to help explain complex data sets and legal terms in plain language.

...

Open-Source Software & Software Licenses

In order to make the Senate's information and software as public as possible, it is has adopted unique system using two types of licenses - GNU General Public License as well as the BSD License. This system is meant to ensure the most public license is used in each specific case such that:

(i) Any Software released containing components with preexisting GPL copyrights must be released pursuant to a GPL v3 copyright restriction.

(ii) Any Software created independently by the Senate without any preexisting licensing restrictions on any of its components shall be released under dual licensing and take one of two forms: (a) a BSD license, or (b) a GPL v3 license. The ultimate user of such Software shall choose which form of licensing makes the most sense for his or her project.

This is getting too easy: I want more of a challenge to opening up government.

Anyway, kudos to all involved - great move.

Follow me @glynmoody on Twitter or identi.ca.

21 May 2009

Cisco Becomes Infected by the GNU GPL

When it was first announced that the FSF had filed a copyright infringement lawsuit against Cisco, some were predicting that this was going to be the definitive test of the power and legality of the GNU GPL. I was more sceptical...

On Open Enterprise blog.

08 April 2009

Second Life + Moodle = Sloodle

Moodle is one of open source's greatest success stories. It's variously described as an e-learning or course management system. Now, given that education is also one of the most popular applications of Second Life, it would be a natural fit somehow to meld Moodle and Second Life. Enter Sloodle, whose latest version has just been released:

Version 0.4 integrates Second Life 3D classrooms with Moodle, the world’s most popular open source e-learning system with over 30 million users (http://www.moodle.org). This latest release allows teachers and students to prepare materials in an easy-to-use, web-based environment and then log into Second Life to put on lectures and student presentations using their avatars.

The new tools also let students send images from inside Second Life directly to their classroom blog. Students are finding this very useful during scavenger hunt exercises where teachers send them to find interesting content and bring it back to report to their classmates.

Tools that cross the web/3D divide are becoming more popular as institutions want to focus on the learning content rather than the technical overhead involved in orienting students into 3D settings and avatars.

As an open-source platform SLOODLE is both freely available and easily enhanced and adapted to suit the needs of diverse student populations. And web hosts are lining up to support the platform. A number of third-party web hosts now offer Moodle hosting with SLOODLE installed either on request or as standard, making easier than ever to get started with SLOODLE.

SLOODLE is funded and supported by Eduserv - http://www.eduserv.ac.uk/ and is completely free for use under the GNU GPL license.

The project was founded by Jeremy Kemp of San José State University, California, and Dr. Daniel Livingstone of the University of the West of Scotland, UK.

Follow me on Twitter @glynmoody

29 March 2009

Building on Richard Stallman's Greatest Achievement

What was Richard Stallman's greatest achievement? Some might say it's Emacs, one of the most powerful and adaptable pieces of software ever written. Others might plump for gcc, an indispensable tool used by probably millions of hackers to write yet more free software. And then there is the entire GNU project, astonishing in its ambition to create a Unix-like operating system from scratch. But for me, his single most important hack was the creation of the GNU General Public Licence....

On Linux Journal.

Follow me on Twitter @glynmoody

01 January 2009

Laying Down the Law

Ever since RMS drew up the GNU GPL, code and law have been inextricably linked. Mark Radcliffe provides a good summary of the last year from a legal viewpoint:

Last year was the one of the most active years for legal developments in the history of free and open source (“FOSS”). http://lawandlifesiliconvalley.com/blog/?p=27 This year, 2008, has seen a continuation of important legal developments for FOSS. My list of the top ten FOSS legal developments in 2008 follows...

12 December 2008

GPL Violations: Is Cisco the Big One?

Many sceptics were convinced that as free software spread out beyond hackers into the general computing sector the rigorous GNU GPL licence would gradually be replaced by more accommodating – meaning weaker – forms, since it was “obvious” that its unbending rules were too strict for widespread use. In fact, the GPL has grown in importance, until today it is probably fair to say that it underpins most of the free software world, including enterprise applications. This makes any violation of its terms particularly worrying, because if left unchallenged, it threatens to undermine the entire ecosystem.

On Linux Journal.

01 December 2008

Saving the Intellectual Commons with Open Source

Regular readers of this blog will know that I am not a fan of the term “intellectual property”, and that I prefer the more technically correct term “intellectual monopolies”. Despite that, I strongly recommend a new book from someone who not only approves of the term “intellectual property”, but of its fundamental ideas. I do so, however, because this avowed fan also has serious reservations....

On Open Enterprise blog.

18 November 2008

Thingiverse: SourceForge for Objects

I wrote below about the distinction between digital and analogue objects, but that was just a crude statement of the situation, which is in a state of flux. The distinction between digital and analogue is blurring thanks to rapid prototyping machines that can take digital representations of objects and turn them into physical things.

Once that happens, it becomes possible to apply all the usual open source methodology to analogue stuff - sharing designs, improving on them etc. One thing you need to do this is a repository of open designs; enter the wonderfully-named Thingiverse:

Thingiverse is a place for you to share your digital designs with the world. We believe that just as computing shifted away from the mainframe into the personal computer that you use today, digital fabrication will share the same path. Infact, it is already happening: laser cutters, cnc machines, 3D printers, and even automated paper cutters are all getting cheaper by the day. These machines are useful for a huge variety of things, but you need to supply them with a digital design in order to get anything useful out of them. We're hoping that together we can create a community of people who create and share designs freely, so that all can benefit from them.

Creative Commons has some useful further info:

Thingiverse is an “object sharing” site that enables anyone to upload the schematics, designs, and images for their projects. Users can then download and reuse the work in their projects using their own laser cutters, 3D printers, and analog tools. Think of it as a Flickr for the Maker set.

Besides implementing our licenses, Bre and Zach [Thingiverse's creators] have also gone the distance and allowed users to license works under the GNU GPL, LGPL, and BSD licenses, as well as allowing them to release works into the public domain.

25 September 2008

Want to Open Flash? Ask Sun How

I'm not the world's biggest fan of Flash, but there's no denying an open version would at least be better than a closed one. Here's why that's not happening:

Now whether we would publish the entire Flash Player as open source is something that first of all would be somewhat challenging in that there are some codices in Flash that we don't have the rights to all the source to. That's one challenge with that. The other is that I think in terms of what's best here for consistency of Flash on the web, having multiple implementations and having forking and splintering of that code would be a big loss for the web in terms of that consistency. So we're really working to be a good steward of Flash and making sure that it runs across operating systems on the web. And we really want to make sure that we don't end up in a situation where it's fragmented and loses the value that it has brought to the web so far. That's really what we're working to do is to maintain the consistency, but we're very inclusive of open source and involved in open source to enable that innovation of the open source community to be part of the success story with Flash.

Now replace the word "Flash" with "Java", and you have *precisely* the argument that Sun used to give for not open-sourcing Java. Which is now available under the GNU GPL.

Adobe, are you listening...? (Via Aral Balkan.)

30 July 2008

Why Open Access for Textbooks is Inevitable

Nice summary here:


With high up front costs and (relatively) low marginal costs, textbook publishing is like other media: the big winners are obscenely profitable and the losers have no hope of turning a profit. Thus, textbook publishers are exactly like record labels: they grew accustomed to high profit margins on winners both to cover their losers, but also to transfer wealth to shareholders and executives.

Without practical or legal protection, that business model will be as extinct as the dodo bird. It happened to CDs, it’s happening to textbooks, and movies are next. The publishers’ anti-piracy czar said “It is troubling that there is a culture of infringement out there.” No duh.

Unfortunately the author then goes on with a complete non-sequitur:

I’m really furious at both the publishers and these student self-appointed Robin Hoods, because together they are creating a generation of information pirates. To all these students studying organic chemistry: would you really prefer a world without IP — that instead of having a job producing information, you will instead have a job making things, delivering personal services or digging ditches? Is that really your nirvana?

A "world without IP" does not imply that everyone ends up digging ditches: it simply implies that business models are not based on exploiting one-sided intellectual monopolies.

I (and many others - hello, Mike) have written much about the alternatives to the "eye-pea" mentality, but if you want a single counter-example you could do worse than consider how open source companies make money. Hint: it's not by locking up their code. Although the GNU GPL *does* depend on copyright law to function, that's simply - if paradoxically - to make it available for all, not to forbid such re-use, which lies at the heart of the traditional copyright system.

11 May 2008

In Praise of the Public Domain

I write a lot about licensing here. Indeed, licensing arguably lies at the heart of free software. But there's another important way of looking at things, which is essentially licence-less, as John Wilbanks reminds us:

It is a damn shame that we no longer think of the public domain as an option that is attractive. It’s a sign of the victory of the content holders that the free licensing movements work against that something without a license – something that is truly free, not just just free “as in” – is somehow thought to be worse. We’ve bought into their games if we allow the public domain to be defined as the BSD. The idea of the public domain has been subjected to continuous erosion thanks to both the big content companies and our own movements, to the point where we think freedom only comes in a contract.

The public domain is not contractually constructed. It just is. It cannot be made more free, only less free. And if we start a culture of licensing and enclosing the public domain (stuff that is actually already free, like the human genome) in the name of “freedom” we’re playing a dangerous game.

How true. Which means that those of us in the free software world must be careful that we don't play into the hands of those who want *everything* to be licensed.

27 January 2008

GNU GPL: It's Irrevocable

I know by now you've seen the notice by the guy claiming to "revoke" the GPL license on his code, because I'm getting email about it.

Here's the answer to your question:

No. One can't retroactively revoke licenses previously granted, unless the license terms allow you to do so. The most you can do is stop granting new licenses.

Obvious, innit?

17 December 2007

Open Access Data - A Question of Protocol

Something calling itself a “Protocol for Implementing Open Access Data” sounds about as exciting as a list of ingredients for paint. But this memo from the Science Commons is one of the most important documents in this field to date. Its scope is explained in the opening paragraph:

This memo provides information for the Internet community interested in distributing data or databases under an “open access” structure. There are several definitions of “open” and “open access” on the Internet, including the Open Knowledge Definition and the Budapest Declaration on Open Access; the protocol laid out herein is intended to conform to the Open Knowledge Definition and extend the ideas of the Budapest Declaration to data and databases.

Again, that may not sound very exciting, but trying to come up with definitions of “open data” or “open access data” have proved extraordinarily hard, and in the course of the memo we learn why:
3. Principles of open access data
Legal tools for an open access data sharing protocol must be developed with three key principles in mind:
3.1 The protocol must promote legal predictability and certainty.
3.2 The protocol must be easy to use and understand.
3.3 The protocol must impose the lowest possible transaction costs on users.


These principles are motivated by Science Commons’ experience in distributing a database licensing Frequently Asked Questions (FAQ) file. Scientists are uncomfortable applying the FAQ because they find it hard to apply the distinction between what is copyrightable and what is not copyrightable, among other elements. A lack of simplicity restricts usage and as such restricts the open access flow of data. Thus any usage system must both be legally accurate while simultaneously very simple for scientists, reducing or eliminating the need to make the distinction between copyrightable and non-copyrightable elements.

The terms also need to satisfy the norms and expectations of the disciplines providing the database. This makes a single license approach difficult – archaeology data norms for citation will differ from those in physics, and yet again from those in biology, and yet again from those in the cultural or educational spaces. But those norms must be attached in a form that imposes the lowest possible costs on users (now and in the future).

The solution is at once obvious and radical:

4. Implementing the Science Commons Database Protocol for open access data
4.1 Converge on the public domain by waiving all rights based on intellectual property

The conflict between simplicity and legal certainty can be best resolved by a twofold measure: 1) a reconstruction of the public domain and 2) the use of scientific norms to express the wishes of the data provider.

Reconstructing the public domain can be achieved through the use of a legal tool (waiving the relevant rights on data and asserting that the provider makes no claims on the data).

Requesting behavior, such as citation, through norms and terms of use rather than as a legal requirement based on copyright or contracts, allows for different scientific disciplines to develop different norms for citation. This allows for legal certainty without constraining one community to the norms of another.

Thus, to facilitate data integration and open access data sharing, any implementation of this protocol MUST waive all rights necessary for data extraction and re-use (including copyright, sui generis database rights, claims of unfair competition, implied contracts, and other legal rights), and MUST NOT apply any obligations on the user of the data or database such as “copyleft” or “share alike”, or even the legal requirement to provide attribution. Any implementation SHOULD define a non-legally binding set of citation norms in clear, lay-readable language.

The solution is obvious because the public domain is the zero state of copyright (in fact, the new Creative Commons public domain licence is called simply CCZero.) It is radical because previous attempts have tried to build on the evident success of the GNU GPL by taking a kind of copyleft approach: using copyright to limit copyright. But the new protocol explicitly negates the use of both GPL's copyleft and the Creative Commons Sharealike licences because, minimal as they are, they are still too restrictive – even though they are both predicated on maximising sharing.

One knock-on consequence of this is that attribution requirements are out. This is not just a matter of belief or principle, but of practicality:

In a world of database integration and federation, attribution can easily cascade into a burden for scientists if a category error is made. Would a scientist need to attribute 40,000 data depositors in the event of a query across 40,000 data sets? How does this relate to the evolved norms of citation within a discipline, and does the attribution requirement indeed conflict with accepted norms in some disciplines? Indeed, failing to give attribution to all 40,000 sources could be the basis for a copyright infringement suit at worst, and at best, imposes a significant transaction cost on the scientist using the data.

It is this pragmatism, rooted in how science actually works, that makes the current protocol particularly important: it might actually be useful. It's also significant that it plugs in to previously existing work in related fields. For example, as the accompanying blog post explains:

We are also pleased to announce that the Open Knowledge Foundation has certified the Protocol as conforming to the Open Knowledge Definition. We think it’s important to avoid legal fragmentation at the early stages, and that one way to avoid that fragmentation is to work with the existing thought leaders like the OKF.

Moreover, the protocol has already been applied in drawing up another important text, the Open Data Commons Public Domain Dedication & Licence:

The Open Data Commons Public Domain Dedication & Licence is a document intended to allow you to freely share, modify, and use this work for any purpose and without any restrictions. This licence is intended for use on databases or their contents (”data”), either together or individually.

Many databases are covered by copyright. Some jurisdictions, mainly in Europe, have specific special rights that cover databases called the “sui generis” database right. Both of these sets of rights, as well as other legal rights used to protect databases and data, can create uncertainty or practical difficulty for those wishing to share databases and their underlying data but retain a limited amount of rights under a “some rights reserved” approach to licensing. As a result, this waiver and licence tries to the fullest extent possible to eliminate or fully license any rights that cover this database and data.

Again, however dry and legalistic this stuff may seem it's not: we're talking about the rigorous foundations of new kinds of sharing - and we all know how important and powerful that can be.

Update: John Wilbanks has pointed me to his post about the winnowing process that led to this protocol - fascinating stuff.

11 December 2007

*The* e-Primer on Open Content

Independently of the fact that it's probably the best single intro to open content currently available, how could anyone resist a publication that has a gnu and penguin sitting together on its front cover?

If you *do* need more, try this:


This e-Primer introduces the idea of Open Content by locating it within the larger historical context of copyright’s relation to the public domain. It examines the foundational premises of copyright and argues that a number of these premises have to be tested on the basis of the public interest that they purport to serve. It then looks at the ways in which content owners are increasingly using copyright as a tool to create monopolies, and how an alternative paradigm like Open Content can facilitate a democratization of knowledge and culture.This e-Primer focuses on some of the implications for policy makers thinking about information policies, and the advantages that the Open Content model may offer, especially for developing countries.

(Via Open Access News.)

Be Afraid, Verizon, Be Very Afraid

On Open Enterprise blog.