open standard

Sniki Wiki> About Sniki Wiki: Your Social Networking Wiki > Social Media > categories > Glossary >

Jump to: navigation, search

An open standard is a standard that is publicly available and has various rights to use associated with it.

The terms "open" and "standard" have a wide range of meanings associated with their usage. The term "open" is usually restricted to royalty-free technologies while the term "standard" is sometimes restricted to technologies approved by formalized committees that are open to participation by all interested parties and operate on a consensus basis.

The definitions of the term "open standard" used by academics, the European Union and some of its member governments or parliaments such as Denmark, France, and Spain preclude open standards requiring fees for use, as does the Venezuelan Government. On the standard organisation side, the W3C ensures that its specifications can be implemented on a Royalty-Free (RF) basis.

Many definitions of the term "standard" permit patent holders to impose "reasonable and non-discriminatory" royalty fees and other licensing terms on implementers and/or users of the standard. For example, the rules for standards published by the major internationally recognized standards bodies such as the IETF[1], ISO, and IEC permit their Standards to contain specifications whose implementation will require payment of patent licensing fees (none of these organizations states that they grant "open standards", but only "standards"). ITU-T, the telecommunications branch of ITU, has a definition of "open standard" that allows "reasonable and non-discriminatory" licensing.

The term "open standard" is sometimes coupled with "open source" with the idea that a standard is not truly open if it does not have a complete free/open source reference implementation available. [2]

Open standards which specify formats are sometimes referred to as open formats.

Many specifications that are sometimes referred to as standards are proprietary and only available under restrictive contract terms (if they can be obtained at all) from the organization that owns the copyright on the specification. As such these specifications are not considered to be fully Open.
Contents
[hide]

* 1 Specific definitions of an open standard
o 1.1 ITU-T definition
o 1.2 European Union definition
o 1.3 Danish government definition
o 1.4 French law definition
o 1.5 Spanish law definition
o 1.6 Venezuelan law definition
o 1.7 Bruce Perens' definition
o 1.8 Open Source Initiative's definition
o 1.9 Ken Krechmer's definition
o 1.10 World Wide Web Consortium's definition
o 1.11 Digital Standards Organization definition
* 2 Examples of open standards
o 2.1 System
o 2.2 Hardware
o 2.3 File formats
o 2.4 Protocols
o 2.5 Programming languages
o 2.6 Other
* 3 Patents
* 4 Quotes
* 5 See also
* 6 References
* 7 External links

[edit] Specific definitions of an open standard

[edit] ITU-T definition

The ITU-T is a standards development organization (SDO) that is one of the three sectors of the International Telecommunications Union (a specialized agency of the United Nations). The ITU-T has a Telecommunication Standardization Bureau director's Ad Hoc group on IPR that produced the following definition in March 2005, which the ITU-T as a whole has endorsed for its purposes since November 2005 [3]:

The ITU-T has a long history of open standards development. However, recently some different external sources have attempted to define the term "Open Standard" in a variety of different ways. In order to avoid confusion, the ITU-T uses for its purpose the term "Open Standards" per the following definition:
"Open Standards" are standards made available to the general public and are developed (or approved) and maintained via a collaborative and consensus driven process. "Open Standards" facilitate interoperability and data exchange among different products or services and are intended for widespread adoption.
Other elements of "Open Standards" include, but are not limited to:

* Collaborative process – voluntary and market driven development (or approval) following a transparent consensus driven process that is reasonably open to all interested parties.
* Reasonably balanced – ensures that the process is not dominated by any one interest group.
* Due process - includes consideration of and response to comments by interested parties.
* Intellectual property rights (IPRs) – IPRs essential to implement the standard to be licensed to all applicants on a worldwide, non-discriminatory basis, either (1) for free and under other reasonable terms and conditions or (2) on reasonable terms and conditions (which may include monetary compensation). Negotiations are left to the parties concerned and are performed outside the SDO.
* Quality and level of detail – sufficient to permit the development of a variety of competing implementations of interoperable products or services. Standardized interfaces are not hidden, or controlled other than by the SDO promulgating the standard.
* Publicly available – easily available for implementation and use, at a reasonable price. Publication of the text of a standard by others is permitted only with the prior approval of the SDO.
* On-going support – maintained and supported over a long period of time.

The ITU-T, ITU-R, ISO, and IEC have harmonized on a common patent policy [4] under the banner of the WSC. Anyway, the above ITU-T definition cannot be considered also applicable in ITU-R, ISO and IEC contexts, since the Common Patent Policy [5] does not make any reference to "open standards" but only to "standards".

[edit] European Union definition

The European Union adopted the following definition in its European Interoperability Framework[6]:

USE OF OPEN STANDARDS To attain interoperability in the context of pan-European eGovernment services, guidance needs to focus on open standards. The following are the minimal characteristics that a specification and its attendant documents must have in order to be considered an open standard:

* The standard is adopted and will be maintained by a not-for-profit organization, and its ongoing development occurs on the basis of an open decision-making procedure available to all interested parties (consensus or majority decision etc.).
* The standard has been published and the standard specification document is available either freely or at a nominal charge. It must be permissible to all to copy, distribute and use it for no fee or at a nominal fee.
* The intellectual property - i.e. patents possibly present - of (parts of) the standard is made irrevocably available on a royalty-free basis.
* There are no constraints on the re-use of the standard.

[edit] Danish government definition

The Danish government has attempted to make a definition of open standards [7], which also is used in pan-European software development projects. It states:

* An open standard is accessible to everyone free of charge (i.e. there is no discrimination between users, and no payment or other considerations are required as a condition of use of the standard)
* An open standard of necessity remains accessible and free of charge (i.e. owners renounce their options, if indeed such exist, to limit access to the standard at a later date, for example, by committing themselves to openness during the remainder of a possible patent's life)
* An open standard is accessible free of charge and documented in all its details (i.e. all aspects of the standard are transparent and documented, and both access to and use of the documentation is free)

[edit] French law definition

The French Parliament approved a definition of "open standard" in its "Law for Confidence in the Digital Economy".[8] The definition is:[9]

* By open standard is understood any communication, interconnection or interchange protocol, and any interoperable data format whose specifications are public and without any restriction in their access or implementation.

[edit] Spanish law definition

A Law passed by the Spanish Parliament [10] requires that all electronic services provided by the Spanish public administration must be based on open standards. It defines an open standard as royalty free, according to the following definition:[11]

An open standard fulfills the following conditions:

* it is public, and its use is available on a free [gratis] basis, or at a cost that does not imply a difficulty for the user.
* its use is not subject to the payment of any intellectual or industrial property right.

[edit] Venezuelan law definition

The Venezuelan Government approved a "free software and open standards law".[12] The decree includes the requirement that the Venezuelan public sector must use free software based on open standards, and includes a definition of open standard:[13]

Article 2: for the purposes of this Decree, it shall be understood as

k) Open standards: technical specifications, published and controlled by an organization in charge of their development, that have been accepted by the industry, available to everybody for their implementation in free software or other [type of software], promoting competitivity, interoperability and flexibility.

[edit] Bruce Perens' definition

One of the most popular definitions of the term "open standard", as measured by Google ranking, is the one developed by Bruce Perens. [14] His definition lists a set of principles that he believes must be met by an open standard:

1. Availability: Open Standards are available for all to read and implement.
2. Maximize End-User Choice: Open Standards create a fair, competitive market for implementations of the standard. They do not lock the customer in to a particular vendor or group.
3. No Royalty: Open Standards are free for all to implement, with no royalty or fee. Certification of compliance by the standards organization may involve a fee.
4. No Discrimination: Open Standards and the organizations that administer them do not favor one implementor over another for any reason other than the technical standards compliance of a vendor’s implementation. Certification organizations must provide a path for low and zero-cost implementations to be validated, but may also provide enhanced certification services.
5. Extension or Subset: Implementations of Open Standards may be extended, or offered in subset form. However, certification organizations may decline to certify subset implementations, and may place requirements upon extensions (see Predatory Practices).
6. Predatory Practices: Open Standards may employ license terms that protect against subversion of the standard by embrace-and-extend tactics. The licenses attached to the standard may require the publication of reference information for extensions, and a license for all others to create, distribute, and sell software that is compatible with the extensions. An Open Standard may not otherwise prohibit extensions.

[edit] Open Source Initiative's definition

The Open Source Initiative defines the requirements and criteria for open standards as follows:[15]

The Requirement

An "open standard" must not prohibit conforming implementations in open source software.

The Criteria

To comply with the Open Standards Requirement, an "open standard" must satisfy the following criteria. If an "open standard" does not meet these criteria, it will be discriminating against open source developers.

1. No Intentional Secrets: The standard MUST NOT withhold any detail necessary for interoperable implementation. As flaws are inevitable, the standard MUST define a process for fixing flaws identified during implementation and interoperability testing and to incorporate said changes into a revised version or superseding version of the standard to be released under terms that do not violate the OSR.
2. Availability: The standard MUST be freely and publicly available (e.g., from a stable web site) under royalty-free terms at reasonable and non-discriminatory cost.
3. Patents: All patents essential to implementation of the standard MUST:
* be licensed under royalty-free terms for unrestricted use, or
* be covered by a promise of non-assertion when practiced by open source software
4. No Agreements: There MUST NOT be any requirement for execution of a license agreement, NDA, grant, click-through, or any other form of paperwork to deploy conforming implementations of the standard.
5. No OSR-Incompatible Dependencies: Implementation of the standard MUST NOT require any other technology that fails to meet the criteria of this Requirement.

[edit] Ken Krechmer's definition

Ken Krechmer[16] identifies ten "rights":

1. Open Meeting
2. Consensus
3. Due Process
4. Open IPR
5. One World
6. Open Change
7. Open Documents
8. Open Interface
9. Open Use
10. On-going Support

[edit] World Wide Web Consortium's definition

As one of the important providers of Web technology ICT Standards, notably XML, http, HTML, CSS and WAI, the World Wide Web Consortium (W3C) follows a process that promotes the development of high-quality standards.

The W3C process defines the following set of requirements that the provider of a technical specification must follow for that specification to qualify as an Open Standard.[17]

* transparency (due process is public, and all technical discussions, meeting minutes, are archived and referencable in decision making)
* relevance (new standardization is started upon due analysis of the market needs, including requirements phase, e.g. accessibility, multi-linguism)
* openness (anybody can participate, and everybody does: industry, individual, public, government bodies, academia, on a worldwide scale)
* impartiality and consensus (guaranteed fairness by the process and the neutral hosting of the W3C organization, with equal weight for each participant)
* availability (free access to the standard text, both during development and at final stage, translations, and clear IPR rules for implementation, allowing open source development in the case of Web technologies)
* maintenance (ongoing process for testing, errata, revision, permanent access)

[edit] Digital Standards Organization definition

The Digital Standards Organization (DIGISTAN) states that "an open standard must be aimed at creating unrestricted competition between vendors and unrestricted choice for users".[18] Its brief definition of "open standard" (or "free and open standard") is "a published specification that is immune to vendor capture at all stages in its life-cycle". Its more complete definition as follows:

* "The standard is adopted and will be maintained by a not-for-profit organization, and its ongoing development occurs on the basis of an open decision-making procedure available to all interested parties.
* The standard has been published and the standard specification document is available freely. It must be permissible to all to copy, distribute, and use it freely.
* The patents possibly present on (parts of) the standard are made irrevocably available on a royalty-free basis.
* There are no constraints on the re-use of the standard.

A key defining property is that an open standard is immune to vendor capture at all stages in its life-cycle. Immunity from vendor capture makes it possible to improve upon, trust, and extend an open standard over time."[19]

This definition is based on the EU's EIF v1 definition of "open standard", but with changes to address what it terms as "vendor capture". They believe that "Many groups and individuals have provided definitions for 'open standard' that reflect their economic interests in the standards process. We see that the fundamental conflict is between vendors who seek to capture markets and raise costs, and the market at large, which seeks freedom and lower costs… Vendors work hard to turn open standards into franchise standards. They work to change the statutory language so they can cloak franchise standards in the sheep's clothing of 'open standard'. A robust definition of "free and open standard" must thus take into account the direct economic conflict between vendors and the market at large."[20]

[edit] Examples of open standards

[edit] System

* World Wide Web architecture specified by W3C[21]

[edit] Hardware
This section does not cite any references or sources.
Please help improve this section by adding citations to reliable sources. Unverifiable material may be challenged and removed. (June 2008)

See also: Open source hardware.

* Industry Standard Architecture (ISA) (a specification by IBM for plug-in boards to IBM-architecture PCs, later standardized by the IEEE)
* Peripheral Component Interconnect (PCI) (a specification by Intel Corporation for plug-in boards to IBM-architecture PCs)
* Accelerated Graphics Port (AGP) (a specification by Intel Corporation for plug-in boards to IBM-architecture PCs)

[edit] File formats

See also: Open format.

* Computer Graphics Metafile (CGM) (file format for 2D vector graphics, raster graphics, and text defined by ISO/IEC 8632[22])
* Hypertext Markup Language (HTML) and Extensible HTML (XHTML) (specifications of the W3C for structured hyperlinked document formatting)
* Portable Document Format (PDF/X) (a specification by Adobe Systems Incorporated for formatted documents, later approved by ISO as ISO 15930-1:2001 [23])
* OpenDocument Format (ODF) (a specification by OASIS for office document formats, approved by ISO as ISO/IEC 26300)
* Portable Network Graphics (PNG) (a bitmapped image format that employs lossless data compression, approved by ISO as ISO/IEC 15948:2004)
* Ogg (a container for Vorbis, FLAC, Speex (audio formats) & Theora (a video format), by the Xiph.Org Foundation)

[edit] Protocols

* Internet Protocol (IP) (a specification of the IETF for transmitting packets of data on a network - specifically, IETF RFC 791)
* Transmission Control Protocol (TCP) (a specification of the IETF for implementing streams of data on top of IP - specifically, IETF RFC 793)
* OMA Data Synchronization and Device Management (a platform-independent data synchronization protocol, specified by The SyncML Initiative/Open Mobile Alliance)

[edit] Programming languages

* Ada (a multi-paradigm programming language, defined by joint ISO/ANSI standard (ISO-8652:1995), combined with major Amendment ISO/IEC 8652:1995/Amd 1:2007)
* MUMPS (a dynamically typed programming language, originally designed for database-driven applications in the healthcare industry approved by ISO as ISO/IEC 11756:1992 and ISO/IEC 11756:1999)
* C# (a general-purpose programming language, approved by ISO as ISO/IEC 23270 and ECMA as ECMA-334)

[edit] Other

* Common Information Model (CIM) (a specification by DMTF for defining how managed elements in an IT environment are represented as a common set of objects and relationships between them)
* CD-ROM (Yellow Book) (a specification for data interchange on read-only 120 mm optical data disks, approved by ISO as ISO/IEC 10149 and ECMA as ECMA-130)
* Attention Profiling Markup Language (APML)

[edit] Patents

In 2002 and 2003 the controversy about using reasonable and non-discriminatory (RAND) licensing for the use of patented technology in web standards increased. Bruce Perens, important associations as FSF or FFII and others have argued that the use of patents restricts who can implement a standard to those able or willing to pay for the use of the patented technology. The requirement to pay some small amount per user, is often an insurmountable problem for free/open source software implementations which can be redistributed by anyone. Royalty free (RF) licensing is generally the only possible license for free/open source software implementations. Version 3 of the GNU General Public License includes a section that enjoins anyone who distributes a program released under the GPL from enforcing patents on subsequent users of the software or derivative works.

One result of this controversy was that many governments (including the Danish, French and Spanish governments singly and the EU collectively) specifically affirmed that "open standards" required royalty-free licenses. Some standards organizations, such as the W3C, modified their processes to essentially only permit royalty-free licensing. Oasis-Open allows committees to operate either on a RAND basis or a royalty-free basis, but OASIS does say to grant "open standards" when they are not royalty-free.

Patents for software, formulas and algorithms are currently enforceable in the US but not in the EU. The European Patent Convention Article 52 paragraph (2)(c) expressly prohibits algorithms, business methods and software from being covered by patents. The US has only allowed them since 1989 and there has been growing controversy in recent years as to either the benefit or feasibility.

A standards body and its associated processes cannot force a patent holder to give up its right to charge license fees, especially if the company concerned is not a member of the standards body and unconstrained by any rules that were set during the standards development process. In fact, this element discourages some standards bodies from adopting an "open" approach, fearing that they will lose out if their members are more constrained than non-members. Few bodies will carry out (or require their members to carry out) a full patent search. Ultimately, the only sanctions a standards body can apply on a non-member when patent licensing is demanded is to cancel the standard, try to rework around it, or work to invalidate the patent. Standards bodies such as W3C and OASIS require[citation needed] that the use of required patents be granted under a royalty-free license as a condition for joining the body or a particular working group, and this is generally considered enforceable.[citation needed]

[edit] Quotes

* EU Commissioner Erkki Liikanen: "Open standards are important to help create interoperable and affordable solutions for everybody. They also promote competition by setting up a technical playing field that is level to all market players. This means lower costs for enterprises and, ultimately, the consumer." (World Standards Day, 14 October 2003) [24]

* Jorma Ollila, Chairman of Nokia's Board of Directors: "… Open standards and platforms create a foundation for success. They enable interoperability of technologies and encourage innovativeness and healthy competition, which in turn increases consumer choice and opens entirely new markets," ([25], 2006)

* W3C Director Tim Berners-Lee: "The decision to make the Web an open system was necessary for it to be universal. You can't propose that something be a universal space and at the same time keep control of it." [26]

[edit] See also

* Open system (computing)
* Open specifications
* Conformity assessment
* Specification (technical standard)
* Vendor lock-in
* Network effect
* Free software

[edit] References

1. ^ RFC 2026, IETF
2. ^ Tim Simcoe: 'Chapter 8: Open Standards and Intellectual Property Rights', To appear in Open Innovation: Researching a New Paradigm
3. ^ ITU-T on Open Standards
4. ^ ITU-T on IPR
5. ^ ISO TC on Common Patent Policy
6. ^ European Interoperability Framework for pan-European eGovernment Services, page 17 (Version 1.0, 2004)
7. ^ "Definitions of Open Standards", 2004
8. ^ "Loi nº 2004-575" for the Confidence in the Digital Economy", June, 21nd 2004
9. ^ "Estándares Abiertos"
10. ^ "Ley 11/2007" of Public Electronic Access of the Citizens to the Public Services, June, 22nd 2007
11. ^ "Estándares Abiertos"
12. ^ "Decreto 3390" of Free Software and Open Standards, December, 23rd 2004
13. ^ "Estándares Abiertos"
14. ^ Is OpenDocument an Open Standard? Yes!
15. ^ Open Standards Requirement for Software
16. ^ Ken Krechmer, The Meaning of Open Standards
17. ^ World Wide Web Consortium Process Document
18. ^ Defining "Open Standard"
19. ^ What is an Open Standard?
20. ^ Defining "Open Standard"
21. ^ WWW architecture
22. ^ ISO/IEC 8632
23. ^ Portable Document File (PDF) format specification
24. ^ EU Commissioner Erkki Liikanen on Open Standards
25. ^ Nokia Foundation Award to Mårten Mickos
26. ^ Tim Berners-Lee's FAQ

[edit] External links

* Berkman Center for Internet & Society at Harvard Law School, Open ePolicy Group, Roadmap for Open ICT Ecosystems
* Bruce Perens: Open Standards: Principles and Practice
* Ken Krechmer: The Principles of Open Standards
* Bob Sutor: Open Standards vs. Open Source: How to think about software, standards, and Service Oriented Architecture at the beginning of the 21st century
* European Commission: Valoris report on Open Document Formats
* The New York Times: Steve Lohr: 'Plan by 13 Nations Urges Open Technology Standards'
* UNDP-APDIP International Open Source Network: Free/Open Source Software: Open Standards Primer
* OpenStandards.net: An Open Standards Portal
* Is OpenDocument an Open Standard? Yes! develops a unified definition of "open standard" from multiple sources, then applies it to a particular standard
* Open Source Initiative: Open Standard Requirement for Software
* Open Standards: Definitions of "Open Standards" from the Cover Pages
* Standard Categories and Definitions: Categories and definitions of the different types of standards - by FFII Open Standards Work Group

Retrieved from "http://en.wikipedia.org/wiki/Open_standard"
Categories: Standards

Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License