Open Source Daily Journal

1. Free Redistribution

2. Source Code

3. Derived Works

4. Integrity of the Author’s Source Code

5. No Discrimination against Person or Groups

6. No Discriminations on Fields of Endeavour

7.  The Distribution of License

8.  It Must not be specific to a Product

9.   It Must not restrict other Software

10.  It Must be Technology Neutral

(Source: Opensource.org)

A. Compliance Levels

To support governments and other bodies in acknowledging and selecting
standards that conform to this Requirement, the OSI defines two levels
of compliance:

1. OSR Compatible

This indicates that the owner of the standard has self-certified
that their standard conforms with this Requirement, and all Compliance
Criteria. Anyone may ask the OSI to review an OSR Compatible standard;
if the OSI finds that the standard is incompatible, the owner must either
modify the standard or stop using the OSR Compatible mark.

2. OSR Conformant

This indicates the OSI has reviewed a standard, as submitted by the owner,
and certified that it fully conforms to the OSR. The OSI may charge a fee
to balance the costs of this certification.

3. Versioning

The OSI may, at its sole discretion, update the Criteria from time to
time to ensure they continue to fulfill the intent of the Requirement.
These updates will include an explicit version number, and the most
current version will always be available from

(Source:Opensource.org)

The License Review Process:

The ultimate goal of the OSI License Review Process is to guarantee that licenses and software labeled as “open source” adapts to existing community norms and expectations. For that reason, all licenses must go through a public review process described below. The OSI Board is glad to consult with entities in advance to help them navigate the process and improve their license, but formal approval requires going through license-review.

Purpose of the Process:

• Guarantee approved licenses compliesto the Open Source Definition
• Identify appropriate License Proliferation Category
• Disapprove vanity and duplicative Licenses
• Ensure a thorough, transparent, and timely review (e.g., within 60 days)
• Provide current status of license review request.

(Source:Opensource.org)

Criteria:

1. No Intentional Secrets

2. Availability

3. Patents

4. No Agreements

5. No OSR Incompatible Dependencies

(Source:Opensource.org)

The ultimate purpose of an open standard is to increase the market for a technology by having potential consumers or suppliers of that technology to spend in it without having to either pay monopoly rent or fear litigation on trade secret, copyright, patent, or trademark causes of action. No such standard can properly be described as “open” except to the extent it achieves these goals. The industry has learned by previous experiences that the only software-related standards to fully meet these goals are those which not only permit but encourage open-source implementations. Open-source implementations are a quality and honesty check for any open standard that might be applied in software; whether an application programming interface, a hardware interface, a file format, a communication protocol, a specification of user interactions, or any other form of data interchange and program control. To support industry participants (suppliers, consumers, and regulators) identify and specify standards that permit open source implementations, the OSI has specified a minimal Open Standards Requirement (OSR). The OSI has also made a set of Criteria that can be used to judge whether a standard fully abides with that Requirement.

(Source:Opensource.org)

1. Fedora 9

2. Phoronix Test Suite 0.3.0

3. Ubuntu 8.04

4. Picasa 2.7

(Source:Lxer.com)