The Open Definition (formerly Open Knowledge Definition) is published by the Open Knowledge Foundation (OKF) to define openness for any type of data, content, or other knowledge. The definition's stated purpose is to "[make] precise the meaning of ‘open’ with respect to knowledge". Although it draws philosophically from both the open-source and free software movements, the Open Definition prioritizes license compatibility over copyleft principles requiring derivative works to be released under a free license. The Open Definition contains requirements for content licenses to be considered open licenses, and the OKF maintains a list of compatible licenses. The definition also requires open access, machine readability, and the use of open formats. The OKF's Open Software Service Definition is derived from the Open Definition.
The Open Knowledge Foundation (OKF) is a United-Kingdom-based NGO that began work on the definition in 2006. According to the OKF, the Open Definition is "substantially derivative" of Bruce Perens' Open Source Definition and intends to continue Richard Stallman’s "ideals of software freedom". The Open Source Definition, which is the most widely used criteria for determining if a license is open source, is itself is derived from the Debian Free Software Guidelines. Although it is similar to David Wiley's defunct Open Content License (which allows retaining, revising, remixing, reusing, and redistributing open content works), the Open Definition is more specific. It is concerned with freedom of access and reuse, rather than open governance. The definition's stated purpose is to "[make] precise the meaning of ‘open’ with respect to knowledge".
The definition (version 2.1) contains the following summary: "Knowledge is open if anyone is free to access, use, modify, and share it—subject, at most, to measures that preserve provenance and openness". The previous version (1.0) stated that "A piece of content or data is open if anyone is free to use, reuse, and redistribute it — subject only, at most, to the requirement to attribute and/or share-alike." The new version makes it clear that using digital rights management (DRM) technology to reduce openness is not allowed.
The definition contains detailed criteria for open knowledge. In terms of open data, the definition covers the four main aspects:
As such, the requirements of the Open Definition extend beyond open licensing by also requiring the elimination or reduction of technological barriers and pricing.
See also: Open license. The definition lists nine areas in which the license must be open and seven restrictions that may be placed on the content. The OKF maintains lists of compatible and incompatible licenses that can be applied to knowledge., it was recommending, in particular, six licenses. It would be possible to draft a bespoke license that met the definition, but this practice would likely lead to compatibility issues in the event of reuse. With the Open Definition, copyleft provisions—requiring reuse of content to be available under a free license—are allowed but not encouraged. The focus is more on license compatibility. Licenses that are noncommercial-only (prohibiting use of content for financial gain) or do not allow derivative works do not meet the Open Definition.
Most of the community involved in open data supports the Open Definition over competing ones, such as that offered by the technology firm Gartner—which only covers use and redistribution. The value that the Open Definition provides as a standard is maintaining license compatibility and preventing the openness of data from being reduced by data sharing and reuse policies.
In contrast to some other definitions of open knowledge, the Open Definition requires freedom of reuse as well as freedom of access. Thus, many open access scientific publications do not meet the Open Definition.
The OKF's Open Software Service Definition requires that the software service's code be free and open-source software and any non-personal data be available under the Open Definition. Lawyer Andrew Katz criticizes this definition for not doing enough to guarantee transparency and prevent vendor lock-in, which occurs when a company makes it deliberately difficult for users to switch to another service. He suggests that adding requirements for a fully documented and freely available API and bulk data export could mitigate lock-in.