Continuing Education on New Data Standards & Technologies

Search thousands of Continuing Education resources for metadata professionals


Advanced Search

Open standard - Wikipedia, the free encyclopedia

Go to the resource directly at https://en.wikipedia.org/wiki/Open_standard

Linked Data

Subject

Creator

Dublin Core

Title

Open standard - Wikipedia, the free encyclopedia

Description

An open standard is a standard that is publicly available and has various rights to use associated with it, and may also have various properties of how it was designed (e.g. open process). There is no single definition and interpretations vary with usage.

The terms open and standard have a wide range of meanings associated with their usage. There are a number of definitions of open standards which emphasize different aspects of openness, including the openness of the resulting specification, the openness of the drafting process, and the ownership of rights in the standard. 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 do the New Zealand, South African and the Venezuelan governments. On the standard organisation side, the World Wide Web Consortium (W3C) ensures that its specifications can be implemented on a royalty-free basis.

Many definitions of the term standard permit patent holders to impose "reasonable and non-discriminatory licensing" royalty fees and other licensing terms on implementers or users of the standard. For example, the rules for standards published by the major internationally recognized standards bodies such as the Internet Engineering Task Force (IETF), International Organization for Standardization (ISO), International Electrotechnical Commission (IEC), and ITU-T permit their standards to contain specifications whose implementation will require payment of patent licensing fees. Among these organizations, only the IETF and ITU-T explicitly refer to their standards as "open standards", while the others refer only to producing "standards". The IETF and ITU-T use definitions of "open standard" that allow "reasonable and non-discriminatory" patent licensing fee requirements.

There are those in the open-source software community who hold that an "open standard" is only open if it can be freely adopted, implemented and extended.[1] While open standards or architectures are considered non-proprietary in the sense that the standard is either unowned or owned by a collective body, it can still be publicly shared and not tightly guarded.[2] The typical example of “open source” that has become a standard is the personal computer originated by IBM and now referred to as Wintel, the combination of the Microsoft operating system and Intel microprocessor. There are three others that are most widely accepted as “open” which include the GSM phones (adopted as a government standard), Open Group which promotes UNIX and the like, and the Internet Engineering Task Force (IETF) which created the first standards of SMTP and TCP/IP. Buyers tend to prefer open standards which they believe offer them cheaper products and more choice for access due to network effects and increased competition between vendors.[3]

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. Joel West has argued that "open" standards are not black and white but have many different levels of "openness". Ultimately a standard needs[according to whom?] to be open enough that it will become adopted and accepted in the market, but still closed enough that firms can get a return on their investment in developing the technology around the standard. A more open standard tends to occur when the knowledge of the technology becomes dispersed enough that competition is increased and others are able to start copying the technology as they implement it. This occurred with the Wintel architecture as others were able to start imitating the software. Less open standards exist when a particular firm has much power (not ownership) over the standard, which can occur when a firm’s platform “wins” in standard setting or the market makes one platform most popular.[4]

On August 12, 2012, the Institute for Electrical and Electronics Engineers (IEEE), Internet Society (ISOC), World Wide Web Consortium (W3C), Internet Engineering Task Force (IETF) and Internet Architecture Board (IAB), jointly affirmed a set of principles which have contributed to the exponential growth of the Internet and related technologies. The “OpenStand Principles” define open standards and establish the building blocks for innovation. Standards developed using the OpenStand principles are developed through an open, participatory process, support interoperability, foster global competition, are voluntarily adopted on a global level and serve as building blocks for products and services targeted to meet the needs of markets and consumers. This drives innovation which, in turn, contributes to the creation of new markets and the growth and expansion of existing markets.

There are five, key OpenStand Principles, as outlined below:

1. Cooperation Respectful cooperation between standards organizations, whereby each respects the autonomy, integrity, processes, and intellectual property rules of the others.

2. Adherence to Principles Adherence to the five fundamental principles of standards development:

Due process. Decisions are made with equity and fairness among participants. No one party dominates or guides standards development. Standards processes are transparent and opportunities exist to appeal decisions. Processes for periodic standards review and updating are well defined. Broad consensus. Processes allow for all views to be considered and addressed, such that agreement can be found across a range of interests. Transparency. Standards organizations provide advance public notice of proposed standards development activities, the scope of work to be undertaken, and conditions for participation. Easily accessible records of decisions and the materials used in reaching those decisions are provided. Public comment periods are provided before final standards approval and adoption. Balance. Standards activities are not exclusively dominated by any particular person, company or interest group. Openness. Standards processes are open to all interested and informed parties.

3. Collective Empowerment Commitment by affirming standards organizations and their participants to collective empowerment by striving for standards that:

4. Availability Standards specifications are made accessible to all for implementation and deployment. Affirming standards organizations have defined procedures to develop specifications that can be implemented under fair terms. Given market diversity, fair terms may vary from royalty-free to fair, reasonable, and non-discriminatory terms (FRAND).

5. Voluntary Adoption Standards are voluntarily adopted and success is determined by the market.

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:[6]

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

In section 7 of its RFC 2026, the IETF classifies specifications that have been developed in a manner similar to that of the IETF itself as being "open standards," and lists the standards produced by ANSI, ISO, IEEE, and ITU-T as examples. As the IETF standardization processes and IPR policies have the characteristics listed above by ITU-T, the IETF standards fulfill the ITU-T definition of "open standards."

However, the IETF has not adopted a specific definition of "open standard"; both RFC 2026 and the IETF's mission statement (RFC 3935) talks about "open process," but RFC 2026 does not define "open standard" except for the purpose of defining what documents IETF standards can link to.

RFC 2026 belongs to a set of RFCs collectively known as BCP 9 (Best Common Practice, an IETF policy).[9] RFC 2026 was later updated by BCP 78 and 79 (among others). As of 2011 BCP 78 is RFC 5378 (Rights Contributors Provide to the IETF Trust),[10] and BCP 79 consists of RFC 3979 (Intellectual Property Rights in IETF Technology) and a clarification in RFC 4879.[11] The changes are intended to be compatible with the "Simplified BSD License" as stated in the IETF Trust Legal Provisions and Copyright FAQ based on RFC 5377.[12]

In August 2012, the IETF combined with the W3C and IEEE to launch OpenStand [13] and to publish The Modern Paradigm for Standards. This captures "the effective and efficient standardization processes that have made the Internet and Web the premiere platforms for innovation and borderless commerce". The declaration is then published in the form of RFC 6852 in January 2013.

The European Union defined the term for use within its European Interoperability Framework for Pan-European eGovernment Services, Version 1.0[14] although it does not claim to be a universal definition for all European Union use and documentation.

The word "open" is here meant in the sense of fulfilling the following requirements:

The Network Centric Operations Industry Consortium (NCOIC) defines open standard as the following:

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

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

A clear Royalty Free stance and far reaching requirements case is the one for India's Government [20]

Italy has a general rule for the entire public sector dealing with Open Standards, although concentrating on data formats, in Art. 68 of the Code of the Digital Administration (Codice dell'Amministrazione Digitale)[21]

A Law passed by the Spanish Parliament [22] 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:[19]

The Venezuelan Government approved a "free software and open standards law."[23] 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:[19]

The South African Government approved a definition in the "Minimum Interoperability Operating Standards Handbook" (MIOS).[24]

For the purposes of the MIOS, a standard shall be considered open if it meets all of these criteria. There are standards which we are obliged to adopt for pragmatic reasons which do not necessarily fully conform to being open in all respects. In such cases, where an open standard does not yet exist, the degree of openness will be taken into account when selecting an appropriate standard:

The E-Government Interoperability Framework (e-GIF) [25] defines open standard as royalty free according to the following text:

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

Vijay Kapoor, national technology officer, Microsoft, defines what open standards are as follows:[27]

Overall, Microsoft's relationship to open standards is, at best, mixed. While Microsoft participates in the most significant standard-setting organizations that establish open standards, it is often seen as oppositional to their adoption.[28] The model started to shift, however, in 2006 and since the XML standard Microsoft has been earning a better reputation within the open-source and open-standards community.[28]

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

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

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.

As an important provider 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.[31]

Looking at the end result, the spec alone, up for adoption, is not enough. The participative/inclusive process leading to a particular design, and the supporting resources available with it should be accounted when we talk about Open Standards:

In August 2012, the W3C combined with the IETF and IEEE to launch OpenStand [13] and to publish The Modern Paradigm for Standards. This captures "the effective and efficient standardization processes that have made the Internet and Web the premiere platforms for innovation and borderless commerce".

The Digital Standards Organization (DIGISTAN) states that "an open standard must be aimed at creating unrestricted competition between vendors and unrestricted choice for users."[32] 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:

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."[32]

The Free Software Foundation Europe (FSFE) uses a definition which is based on the European Interoperability Framework v.1, and was extended after consultation with industry and community stakeholders. FSFE's standard has been adopted by groups such as the SELF EU Project, the 2008 Geneva Declaration on Standards and the Future of the Internet, and international Document Freedom Day teams.

According to this definition an Open Standard is a format or protocol that is:

The Foundation for a Free Information Infrastructure's definition is said[by whom?] to coincide with the definition issued in the European Interoperability Framework released in 2004.

Note that because the various definitions of "open standard" differ in their requirements, the standards listed below may not be open by every definition.

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.

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]

Examples of patent claims brought against standards previously thought to be open include JPEG and the Rambus case over DDR SDRAM. The H.264 video codec is an example of a standards organization producing a standard that has known, non-royalty-free required patents.

Often the scope of the standard itself determines how likely it is that a firm will be able to use a standard as patent-like protection. Richard Langlois argues that standards with a wide scope may offer a firm some level of protection from competitors but it is likely that Schumpeterian creative destruction will ultimately leave the firm open to being "invented around" regardless of the standard a firm may benefit from.[2]

Rights

Copyright to metadata belongs to Continuing Education Metadata Project.

Format

text/html; charset=utf-8 140.46 KB

Language

en

Identifier

https://en.wikipedia.org/wiki/Open_standard

Hyperlink Item Type Metadata

Files

Citation

En staff, “Open standard - Wikipedia, the free encyclopedia,” Continuing Education on New Data Standards & Technologies, accessed March 4, 2021, http://metadatace.cci.drexel.edu/omeka/items/show/34643.