Открытые стандарты: Доступность, разработка и использование
Open standard
Открытые стандарты: что это такое? Доступные и расширяемые спецификации, как GSM, 4G, 5G, обеспечивающие совместимость и участие в разработке для всех.
Сравнивайте с английским: нажмите на абзац — оригинал откроется в окне. Кнопка EN под абзацем показывает его прямо в тексте.
Содержание
Введение
Стандарт, к которому легко могут получить доступ и который могут использовать все участники рынка. Открытый стандарт – это стандарт, который находится в открытом доступе и может быть использован любым желающим. Обычно открытые стандарты используют открытую лицензию, обеспечивающую возможность расширения и доработки. Благодаря своей природе, любой может участвовать в их разработке. Единого определения не существует, и интерпретации могут различаться в зависимости от контекста использования. Примерами открытых стандартов являются стандарты GSM, 4G и 5G, обеспечивающие работу большинства современных мобильных телефонов по всему миру.
Standard that can be easily accessed and used by all market participants
An open standard is a standard that is openly accessible and usable by anyone. It is also a common prerequisite that open standards use an open license that provides for extensibility. Typically, anybody can participate in their development due to their inherently open nature. There is no single definition, and interpretations vary with usage. Examples of open standards include the GSM, 4G, and 5G standards that allow most modern mobile phones to work world wide.
Определения
Термины "открытый" и "стандартный" имеют широкий спектр значений в зависимости от контекста их использования. Существует множество определений открытых стандартов, подчеркивающих различные аспекты открытости, включая открытость самой спецификации, открытость процесса разработки и права на стандарт. Термин "стандарт" иногда ограничивается технологиями, утвержденными формализованными комитетами, открытыми для участия всех заинтересованных сторон и работающими на основе консенсуса. Определения термина "открытый стандарт", используемые научными кругами, Европейским союзом и некоторыми государствами-членами или парламентами, такими как Дания, Франция и Испания, исключают открытые стандарты, требующие платы за использование, как и правительства Новой Зеландии, Южной Африки и Венесуэлы. Что касается организаций по стандартизации, Консорциум Всемирной паутины (W3C) гарантирует, что его спецификации могут быть реализованы без уплаты роялти. Многие определения термина "стандарт" разрешают владельцам патентов взимать "разумные и недискриминационные" лицензионные сборы и устанавливать другие условия лицензирования для тех, кто внедряет или использует стандарт. Например, правила стандартов, публикуемые крупными международными организациями по стандартизации, такими как Internet Engineering Task Force (IETF), Международная организация по стандартизации (ISO), Международная электротехническая комиссия (IEC) и ITU T, допускают включение в их стандарты спецификаций, реализация которых потребует выплаты лицензионных сборов за патенты. Среди этих организаций только IETF и ITU T явно называют свои стандарты "открытыми стандартами", в то время как остальные говорят лишь о производстве "стандартов". IETF и ITU T используют определения "открытого стандарта", которые допускают требования к "разумным и недискриминационным" лицензионным сборам за патенты. В сообществе разработчиков программного обеспечения с открытым исходным кодом существуют сторонники точки зрения, что "открытый стандарт" является по-настоящему открытым только в том случае, если его можно свободно использовать, внедрять и расширять. Хотя открытые стандарты или архитектуры считаются не проприетарными в том смысле, что стандарт либо не имеет владельца, либо принадлежит коллективному органу, он все равно может быть общедоступным и не подвергаться жесткому контролю. Типичным примером "открытого исходного кода", ставшего стандартом, является персональный компьютер, разработанный IBM и теперь известный как Wintel – комбинация операционной системы Microsoft и микропроцессора Intel. Существуют еще три широко признанных "открытых" стандарта: телефоны GSM (принятые в качестве государственного стандарта), Open Group, продвигающая UNIX, и Internet Engineering Task Force (IETF), создавшая первые стандарты SMTP и TCP/IP. Покупатели, как правило, предпочитают открытые стандарты, поскольку считают, что они предлагают более дешевые продукты и больший выбор благодаря сетевому эффекту и усилению конкуренции между поставщиками. Открытые стандарты, определяющие форматы, иногда называют открытыми форматами. Многие спецификации, которые иногда называют стандартами, являются проприетарными и доступны только (если вообще доступны) на условиях ограничительных договоров с организацией, владеющей авторскими правами на спецификацию. Следовательно, эти спецификации не считаются полностью открытыми. Джоэл Уэст утверждает, что "открытые" стандарты не бывают однозначными, а имеют множество уровней "открытости". Стандарт становится более открытым, когда знания о технологии достаточно распространяются, что приводит к усилению конкуренции и возможности для других копировать технологию при ее внедрении. Это произошло с архитектурой Wintel, поскольку другие смогли начать имитировать программное обеспечение.
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. 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. 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 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. 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 (if they can be obtained at all) under restrictive contract terms 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". 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.
Определение IETF
В разделе 7 RFC 2026 IETF классифицирует спецификации, разработанные аналогичным IETF образом, как «открытые стандарты» и приводит в качестве примеров стандарты, разработанные ANSI, ISO, IEEE и ITU T. Поскольку процессы стандартизации IETF и политики в отношении прав интеллектуальной собственности (ИС) обладают характеристиками, перечисленными ITU T, стандарты IETF соответствуют определению «открытых стандартов» ITU T. Однако IETF не приняло конкретного определения «открытого стандарта»; как RFC 2026, так и заявление о миссии IETF (RFC 3935) говорят об «открытом процессе», но RFC 2026 не определяет «открытый стандарт», за исключением цели определения документов, на которые могут ссылаться стандарты IETF. RFC 2026 входит в набор RFC, известных как BCP 9 (Best Common Practice – политика IETF). RFC 2026 впоследствии был обновлен BCP 78 и 79 (и другими). По состоянию на 2011 год BCP 78 – это RFC 5378 («Права, предоставляемые участниками IETF Trust»), а BCP 79 состоит из RFC 3979 («Права интеллектуальной собственности в технологиях IETF») и разъяснений в RFC 4879. Эти изменения призваны быть совместимыми с «Упрощенной BSD-лицензией», как указано в Legal Provisions IETF Trust и FAQ по авторскому праву на основе RFC 5377. В августе 2012 года IETF объединился с W3C и IEEE для запуска OpenStand и публикации The Modern Paradigm for Standards. Это отражает «эффективные процессы стандартизации, которые сделали Интернет и Web ведущими платформами для инноваций и безграничной торговли». Затем декларация была опубликована в форме RFC 6852 в январе 2013 года.
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). 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), and BCP 79 consists of RFC 3979 (Intellectual Property Rights in IETF Technology) and a clarification in RFC 4879. 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. In August 2012, the IETF combined with the W3C and IEEE to launch OpenStand 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.
Определение французского права
Французский парламент утвердил определение "открытого стандарта" в своем "Законе о доверии к цифровой экономике". Определение (статья 4): Открытым стандартом понимается любой протокол связи, взаимодействия или обмена данными, а также любой совместимый формат данных, спецификации которого находятся в открытом доступе и не имеют ограничений на доступ или реализацию.
The French Parliament approved a definition of "open standard" in its "Law for Confidence in the Digital Economy." The definition is (Article 4):
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.
Определение итальянского права
В Италии действует общее правило для всего государственного сектора в отношении открытых стандартов, хотя оно сосредоточено преимущественно на форматах данных, и закреплено в ст. 68 Кодекса о цифровом администрировании (Codice dell'Amministrazione Digitale).
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)
[Приложения должны] обеспечивать представление данных в различных форматах, как минимум один из которых должен быть открытым форматом данных.
[applications must] allow representation of data under different formats, at least one being an open data format. [ ]
[Определяется] открытый формат данных как формат данных, который является общедоступным, тщательно документированным и нейтральным по отношению к технологическим средствам, необходимым для его обработки.
[it is defined] an open data format, a data format which is made public, is thoroughly documented and neutral with regard to the technological tools needed to peruse the same data.
Определение правительства Великобритании
Определение открытых стандартов, данное правительством Великобритании, распространяется на совместимость программного обеспечения, данные и форматы документов. Критерии открытых стандартов опубликованы в документе "Принципы открытых стандартов" и следующие:
The UK government's definition of open standards applies to software interoperability, data and document formats. The criteria for open standards are published in the “Open Standards Principles” policy paper and are as follows. Collaboration the standard is maintained through a collaborative decision making process that is consensus based and independent of any individual supplier. Involvement in the development and maintenance of the standard is accessible to all interested parties. Transparency the decision making process is transparent, and a publicly accessible review by subject matter experts is part of the process. Due process the standard is adopted by a specification or standardisation organisation, or a forum or consortium with a feedback and ratification process to ensure quality. Fair access the standard is well documented, publicly available and free to use. Mature completely developed, unless they are in the context of creating innovative solutions. Independent of platform, application and vendor supported by the market with several implementations. Rights rights essential to implementation of the standard, and for interfacing with other implementations which have adopted that same standard, are licensed on a royalty free basis that is compatible with both open source and proprietary licensed solutions. These rights should be irrevocable unless there is a breach of licence conditions. The Cabinet Office in the UK recommends that government departments specify requirements using open standards when undertaking procurement exercises in order to promote interoperability and re use, and avoid technological lock in.
Сотрудничество – стандарт поддерживается посредством совместного процесса принятия решений, основанного на консенсусе и независимого от какого-либо отдельного поставщика. Участие в разработке и поддержании стандарта доступно всем заинтересованным сторонам.
The UK government's definition of open standards applies to software interoperability, data and document formats. The criteria for open standards are published in the “Open Standards Principles” policy paper and are as follows. Collaboration the standard is maintained through a collaborative decision making process that is consensus based and independent of any individual supplier. Involvement in the development and maintenance of the standard is accessible to all interested parties. Transparency the decision making process is transparent, and a publicly accessible review by subject matter experts is part of the process. Due process the standard is adopted by a specification or standardisation organisation, or a forum or consortium with a feedback and ratification process to ensure quality. Fair access the standard is well documented, publicly available and free to use. Mature completely developed, unless they are in the context of creating innovative solutions. Independent of platform, application and vendor supported by the market with several implementations. Rights rights essential to implementation of the standard, and for interfacing with other implementations which have adopted that same standard, are licensed on a royalty free basis that is compatible with both open source and proprietary licensed solutions. These rights should be irrevocable unless there is a breach of licence conditions. The Cabinet Office in the UK recommends that government departments specify requirements using open standards when undertaking procurement exercises in order to promote interoperability and re use, and avoid technological lock in.
Прозрачность – процесс принятия решений прозрачен, и общедоступный анализ экспертами в соответствующей области является его частью.
The UK government's definition of open standards applies to software interoperability, data and document formats. The criteria for open standards are published in the “Open Standards Principles” policy paper and are as follows. Collaboration the standard is maintained through a collaborative decision making process that is consensus based and independent of any individual supplier. Involvement in the development and maintenance of the standard is accessible to all interested parties. Transparency the decision making process is transparent, and a publicly accessible review by subject matter experts is part of the process. Due process the standard is adopted by a specification or standardisation organisation, or a forum or consortium with a feedback and ratification process to ensure quality. Fair access the standard is well documented, publicly available and free to use. Mature completely developed, unless they are in the context of creating innovative solutions. Independent of platform, application and vendor supported by the market with several implementations. Rights rights essential to implementation of the standard, and for interfacing with other implementations which have adopted that same standard, are licensed on a royalty free basis that is compatible with both open source and proprietary licensed solutions. These rights should be irrevocable unless there is a breach of licence conditions. The Cabinet Office in the UK recommends that government departments specify requirements using open standards when undertaking procurement exercises in order to promote interoperability and re use, and avoid technological lock in.
Процедура – стандарт принимается организацией по разработке спецификаций или стандартизации, либо форумом или консорциумом с механизмом обратной связи и ратификации для обеспечения качества.
The UK government's definition of open standards applies to software interoperability, data and document formats. The criteria for open standards are published in the “Open Standards Principles” policy paper and are as follows. Collaboration the standard is maintained through a collaborative decision making process that is consensus based and independent of any individual supplier. Involvement in the development and maintenance of the standard is accessible to all interested parties. Transparency the decision making process is transparent, and a publicly accessible review by subject matter experts is part of the process. Due process the standard is adopted by a specification or standardisation organisation, or a forum or consortium with a feedback and ratification process to ensure quality. Fair access the standard is well documented, publicly available and free to use. Mature completely developed, unless they are in the context of creating innovative solutions. Independent of platform, application and vendor supported by the market with several implementations. Rights rights essential to implementation of the standard, and for interfacing with other implementations which have adopted that same standard, are licensed on a royalty free basis that is compatible with both open source and proprietary licensed solutions. These rights should be irrevocable unless there is a breach of licence conditions. The Cabinet Office in the UK recommends that government departments specify requirements using open standards when undertaking procurement exercises in order to promote interoperability and re use, and avoid technological lock in.
Свободный доступ – стандарт хорошо документирован, находится в открытом доступе и свободен от платежей за использование.
The UK government's definition of open standards applies to software interoperability, data and document formats. The criteria for open standards are published in the “Open Standards Principles” policy paper and are as follows. Collaboration the standard is maintained through a collaborative decision making process that is consensus based and independent of any individual supplier. Involvement in the development and maintenance of the standard is accessible to all interested parties. Transparency the decision making process is transparent, and a publicly accessible review by subject matter experts is part of the process. Due process the standard is adopted by a specification or standardisation organisation, or a forum or consortium with a feedback and ratification process to ensure quality. Fair access the standard is well documented, publicly available and free to use. Mature completely developed, unless they are in the context of creating innovative solutions. Independent of platform, application and vendor supported by the market with several implementations. Rights rights essential to implementation of the standard, and for interfacing with other implementations which have adopted that same standard, are licensed on a royalty free basis that is compatible with both open source and proprietary licensed solutions. These rights should be irrevocable unless there is a breach of licence conditions. The Cabinet Office in the UK recommends that government departments specify requirements using open standards when undertaking procurement exercises in order to promote interoperability and re use, and avoid technological lock in.
Зрелость – полностью разработан, за исключением случаев, когда он используется для создания инновационных решений.
The UK government's definition of open standards applies to software interoperability, data and document formats. The criteria for open standards are published in the “Open Standards Principles” policy paper and are as follows. Collaboration the standard is maintained through a collaborative decision making process that is consensus based and independent of any individual supplier. Involvement in the development and maintenance of the standard is accessible to all interested parties. Transparency the decision making process is transparent, and a publicly accessible review by subject matter experts is part of the process. Due process the standard is adopted by a specification or standardisation organisation, or a forum or consortium with a feedback and ratification process to ensure quality. Fair access the standard is well documented, publicly available and free to use. Mature completely developed, unless they are in the context of creating innovative solutions. Independent of platform, application and vendor supported by the market with several implementations. Rights rights essential to implementation of the standard, and for interfacing with other implementations which have adopted that same standard, are licensed on a royalty free basis that is compatible with both open source and proprietary licensed solutions. These rights should be irrevocable unless there is a breach of licence conditions. The Cabinet Office in the UK recommends that government departments specify requirements using open standards when undertaking procurement exercises in order to promote interoperability and re use, and avoid technological lock in.
Независимость от платформы, приложения и поставщика – поддерживается рынком и имеет несколько реализаций.
The UK government's definition of open standards applies to software interoperability, data and document formats. The criteria for open standards are published in the “Open Standards Principles” policy paper and are as follows. Collaboration the standard is maintained through a collaborative decision making process that is consensus based and independent of any individual supplier. Involvement in the development and maintenance of the standard is accessible to all interested parties. Transparency the decision making process is transparent, and a publicly accessible review by subject matter experts is part of the process. Due process the standard is adopted by a specification or standardisation organisation, or a forum or consortium with a feedback and ratification process to ensure quality. Fair access the standard is well documented, publicly available and free to use. Mature completely developed, unless they are in the context of creating innovative solutions. Independent of platform, application and vendor supported by the market with several implementations. Rights rights essential to implementation of the standard, and for interfacing with other implementations which have adopted that same standard, are licensed on a royalty free basis that is compatible with both open source and proprietary licensed solutions. These rights should be irrevocable unless there is a breach of licence conditions. The Cabinet Office in the UK recommends that government departments specify requirements using open standards when undertaking procurement exercises in order to promote interoperability and re use, and avoid technological lock in.
Права – права, необходимые для реализации стандарта и взаимодействия с другими реализациями, использующими тот же стандарт, лицензируются на безвозмездной основе, совместимой как с решениями с открытым исходным кодом, так и с проприетарными решениями. Эти права должны быть безотзывными, за исключением случаев нарушения условий лицензии.
The UK government's definition of open standards applies to software interoperability, data and document formats. The criteria for open standards are published in the “Open Standards Principles” policy paper and are as follows. Collaboration the standard is maintained through a collaborative decision making process that is consensus based and independent of any individual supplier. Involvement in the development and maintenance of the standard is accessible to all interested parties. Transparency the decision making process is transparent, and a publicly accessible review by subject matter experts is part of the process. Due process the standard is adopted by a specification or standardisation organisation, or a forum or consortium with a feedback and ratification process to ensure quality. Fair access the standard is well documented, publicly available and free to use. Mature completely developed, unless they are in the context of creating innovative solutions. Independent of platform, application and vendor supported by the market with several implementations. Rights rights essential to implementation of the standard, and for interfacing with other implementations which have adopted that same standard, are licensed on a royalty free basis that is compatible with both open source and proprietary licensed solutions. These rights should be irrevocable unless there is a breach of licence conditions. The Cabinet Office in the UK recommends that government departments specify requirements using open standards when undertaking procurement exercises in order to promote interoperability and re use, and avoid technological lock in.
Кабинет министров Великобритании рекомендует государственным органам указывать требования к использованию открытых стандартов при проведении закупок для обеспечения совместимости, повторного использования и предотвращения технологической привязки.
The UK government's definition of open standards applies to software interoperability, data and document formats. The criteria for open standards are published in the “Open Standards Principles” policy paper and are as follows. Collaboration the standard is maintained through a collaborative decision making process that is consensus based and independent of any individual supplier. Involvement in the development and maintenance of the standard is accessible to all interested parties. Transparency the decision making process is transparent, and a publicly accessible review by subject matter experts is part of the process. Due process the standard is adopted by a specification or standardisation organisation, or a forum or consortium with a feedback and ratification process to ensure quality. Fair access the standard is well documented, publicly available and free to use. Mature completely developed, unless they are in the context of creating innovative solutions. Independent of platform, application and vendor supported by the market with several implementations. Rights rights essential to implementation of the standard, and for interfacing with other implementations which have adopted that same standard, are licensed on a royalty free basis that is compatible with both open source and proprietary licensed solutions. These rights should be irrevocable unless there is a breach of licence conditions. The Cabinet Office in the UK recommends that government departments specify requirements using open standards when undertaking procurement exercises in order to promote interoperability and re use, and avoid technological lock in.
Определение FFII
Считается, что определение Фонда свободной информационной инфраструктуры совпадает с определением, представленным в Европейской структуре обеспечения совместимости, опубликованной в 2004 году. Эта спецификация является публичной, стандарт – всеобъемлющим, и он разработан и поддерживается в рамках открытого процесса стандартизации. Любой может реализовать его без каких-либо ограничений, включая оплату или лицензирование прав интеллектуальной собственности (предоставляемых всем бесплатно и без каких-либо условий). Это минимальные условия лицензирования, требуемые организациями по стандартизации, такими как W3C. Разумеется, все остальные организации принимают открытые стандарты. Однако сама спецификация может стоить значительных средств (например, 100 400 евро за экземпляр, как в ISO, из-за авторских прав и публикации документа).
The Foundation for a Free Information Infrastructure's definition is said to coincide with the definition issued in the European Interoperability Framework released in 2004. A specification that is public, the standard is inclusive and it has been developed and is maintained in an open standardization process, everybody can implement it without any restriction, neither payment, to license the IPR (granted to everybody for free and without any condition). This is the minimum license terms asked by standardization bodies as W3C. Of course, all the other bodies accept open standards. But specification itself could cost a fair amount of money (i. e. 100 400 Eur per copy as in ISO because copyright and publication of the document itself).
Сравнение определений
Издатель Время публикации Доступность (Распространение спецификации) Права использования (Лицензирование основных патентов) Процесс (Процесс дальнейшей разработки) Полнота Бесплатно Условия FRAND Без роялти, безвозвратно Условия FRAND Открытое участие Открытый просмотр Требует реализации от нескольких поставщиков или открытой справки для зрелости Совместный IEEE, ISOC, W3C, IETF, IAB 2012 08 12 ITU T 2005 03 ✔ ✔ Pan European eGovernment 2004 0 или номинальная ✔ ✔ Правительство Дании 2004 ✔ Французское законодательство 2004 Правительство Индии 2014 0 или номинальная ✔ Итальянское законодательство 2005 03 07 Новая Зеландия e GIF 2007 06 22 ✔ Португальское законодательство 2011 06 21 ✔ ✔ ✔ Правительство Южной Африки 2007 ✔ ✔ ✔ ✔ Испанское законодательство 2007 06 22 0 или низкая Правительство Великобритании 2012 0 или низкая ✔ ✔ ✔ Венесуэльское законодательство 2004 12 23 Брюс Перенс до 2002 Предпочтительно ✔ Microsoft ок. 2006 ✔ ✔ Open Source Initiative 2006 09 ✔ ✔ Кен Крехмер 2005 01 ✔ ✔ ✔ W3C 2005 09 ✔ ✔ ✔ DIGISTAN ок. 2008 ✔ ✔ ✔ FSFE 2001 ✔ ✔ ✔ FFII до 2004 ✔
Publisher Time of publication Availability (Redistribution of Specification) Usage rights (Licensing of essential patents) Process (Process of further development) Completeness Free of charge FRAND terms Royalty free, irrevocably FRAND terms Open participation Open viewing Needs multiple vendorimplementations or openreference for maturity Joint IEEE, ISOC, W3C, IETF, IAB 2012 08 12 ITU T 2005 03 ✔ ✔ Pan European eGovernment 2004 0 or nominal ✔ ✔ Danish government 2004 ✔ French law 2004 Indian government 2014 0 or nominal ✔ Italian law 2005 03 07 New Zealand e GIF 2007 06 22 ✔ Portuguese law 2011 06 21 ✔ ✔ ✔ South African government 2007 ✔ ✔ ✔ ✔ Spanish law 2007 06 22 0 or low UK government 2012 0 or low ✔ ✔ ✔ Venezuelan law 2004 12 23 Bruce Perens before 2002 Preferred ✔ Microsoft c. 2006 ✔ ✔ Open Source Initiative 2006 09 ✔ ✔ Ken Krechmer 2005 01 ✔ ✔ ✔ W3C 2005 09 ✔ ✔ ✔ DIGISTAN c. 2008 ✔ ✔ ✔ FSFE 2001 ✔ ✔ ✔ FFII before 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.