Open Definition

= synomymous with the Open Knowledge Definition: The Open Knowledge Definition is based on the OSI Open Source Software Definition No restrictions on field of endeavour - non-commercial-use licenses are not open as in the OKD.

URL = http://www.opendefinition.org/okd/

Description

Mike Linksvayer:

"Open Defintion (OD) is one of the first projects that the the Open Knowledge Foundation created. Its purpose has been to provide, promote — and protect — a meaningful Open in Open Data and Open Content.

It does this primarily through curating the Open Knowledge Definition (OKD), working with license stewards to ensure new licenses intending to be open are clearly so, and keeping lists of licenses that conform to the OKD, and those that do not — providing any entity intending to create an open project, or mandate “open” in policy, with a clear reference as to which licenses will achieve their aims.

If you’re a legal or policy expert, software freedom advocate, linked data hacker, translator, designer, communications maven — and want to go “meta” about openness, we could use your help! Join the od-discuss mailing list and pitch into the discussion, start a new one, or lurk until you’re ready.

Final decisions about license conformance and definition updates are made by the Open Definition Advisory Council. This is not a big time commitment, but it is a big responsibility. If you’d like to join the AC someday, join od-discuss today." (http://opendefinition.org/2012/12/17/open-definition-forges-ahead-get-involved/)

Status

Mike Linksvayer:

"With the growth in “open” and especially of open data initiatives in the last few years there has been an increasing amount for the project to do especially in terms of reviewing and evaluating licenses. For 2013 we see several important areas of work:

OKD v1.2 — we’ve seen license conditions cropping up that are certainly contrary to the spirit of the definition and implicitly non-conformant. It ought be possible for anyone with some understanding of public licenses to do a quick read of the definition and understand its meaning for a particular license without having to know all of the history of open definitions and licenses.

Review important new licenses and license versions for OKD compliance, e.g. Open Government License Canada, and version 4.0 of CC-BY and CC-BY-SA.

Moving linguistic translations into a git repository for better review and updating.

Improve explanations and graphics available on the OD site for anyone who wants to learn about open knowledge and services, and proudly announce to the world that their projects are open.

Extend our work on license APIs that provide information about open licenses at licenses.opendefinition.org and integrate with the main OD site; also look to cooperate with other projects providing Linked Open Data about licenses.

Provide regular updates about OD work to the broader OKFN network, open communities, and general public.

Develop a version git-based repository of license texts so they can be tracked over time

Growing out of discussions in 2006 and 2007, the OD project developed the Open Software Service Definition (OSSD), recognizing the complementarity of open content and data (knowledge) and open source web platforms and other network services that open knowledge is created, curated, and distributed on. The OSSD hasn’t been touched in a long time, but software services (some of them called “the cloud”) have become more important than ever, including in domains nearest to the OKFN community’s most active work, such as platforms used by and for open government. Shall we update the OSSD and revitalize evangelism for open services, or declare not a core competency, and look to other groups to take leadership?" (http://opendefinition.org/2012/12/17/open-definition-forges-ahead-get-involved/)

Text

An Open Knowledge Foundation Project , Version 1.1 [1]

Terminology

The term knowledge is taken to include:

  1. Content such as music, films, books
  2. Data be it scientific, historical, geographic or otherwise
  3. Government and other administrative information

Software is excluded despite its obvious centrality because it is already adequately addressed by previous work.

The term work will be used to denote the item or piece of knowledge which is being transferred.

The term package may also be used to denote a collection of works. Of course such a package may be considered a work in itself.

The term license refers to the legal license under which the work is made available. Where no license has been made this should be interpreted as referring to the resulting default legal conditions under which the work is available (for example copyright).

The Definition

A work is open if its manner of distribution satisfies the following conditions:

1. Access

The work shall be available as a whole and at no more than a reasonable reproduction cost, preferably downloading via the Internet without charge. The work must also be available in a convenient and modifiable form.

Comment: This can be summarized as ‘social’ openness – not only are you allowed to get the work but you can get it. ‘As a whole’ prevents the limitation of access by indirect means, for example by only allowing access to a few items of a database at a time.

2. Redistribution

The license shall not restrict any party from selling or giving away the work either on its own or as part of a package made from works from many different sources. The license shall not require a royalty or other fee for such sale or distribution.

3. Reuse

The license must allow for modifications and derivative works and must allow them to be distributed under the terms of the original work.

Comment: Note that this clause does not prevent the use of ‘viral’ or share-alike licenses that require redistribution of modifications under the same terms as the original.

4. Absence of Technological Restriction

The work must be provided in such a form that there are no technological obstacles to the performance of the above activities. This can be achieved by the provision of the work in an open data format, i.e. one whose specification is publicly and freely available and which places no restrictions monetary or otherwise upon its use.

5. Attribution

The license may require as a condition for redistribution and re-use the attribution of the contributors and creators to the work. If this condition is imposed it must not be onerous. For example if attribution is required a list of those requiring attribution should accompany the work.

6. Integrity

The license may require as a condition for the work being distributed in modified form that the resulting work carry a different name or version number from the original work.

7. No Discrimination Against Persons or Groups

The license must not discriminate against any person or group of persons.

Comment: In order to get the maximum benefit from the process, the maximum diversity of persons and groups should be equally eligible to contribute to open knowledge. Therefore we forbid any open-knowledge license from locking anybody out of the process.

Comment: this is taken directly from item 5 of the OSD.

8. No Discrimination Against Fields of Endeavor

The license must not restrict anyone from making use of the work in a specific field of endeavor. For example, it may not restrict the work from being used in a business, or from being used for genetic research.

Comment: The major intention of this clause is to prohibit license traps that prevent open source from being used commercially. We want commercial users to join our community, not feel excluded from it.

Comment: this is taken directly from item 6 of the OSD.

9. Distribution of License

The rights attached to the work must apply to all to whom the program is redistributed without the need for execution of an additional license by those parties.

Comment: This clause is intended to forbid closing up knowledge by indirect means such as requiring a non-disclosure agreement.

Comment: this is taken directly from item 7 of the OSD.

10. License Must Not Be Specific to a Package

The rights attached to the work must not depend on the work being part of a particular package. If the work is extracted from that package and used or distributed within the terms of the work’s license, all parties to whom the work is redistributed should have the same rights as those that are granted in conjunction with the original package.

Comment: this is taken directly from item 8 of the OSD.

11. License Must Not Restrict the Distribution of Other Works

The license must not place restrictions on other works that are distributed along with the licensed work. For example, the license must not insist that all other works distributed on the same medium are open.

Comment: Distributors of open knowledge have the right to make their own choices. Note that ‘share-alike’ licenses are conformant since those provisions only apply if the whole forms a single work.

Comment: this is taken directly from item 9 of the OSD.

More Information

• The Open Data Commons is run by Jordan Hatcher, who started work on the Open Database License with support from Talis, later extensive negotiation with the OpenStreetmap community. ODbL is a ShareAlike license for data, that obviates the problems of inapplicability of copyright to facts.

• Open Data Grid: a project in early incubation; based on the Tahoe distributed filesystem. It’s in need of development effort on Tahoe to really get going. Provide secure storage for open datasets around the edges of infrastructure that people are already running.