Interoperability and open standards
Interoperability concerns whether products or systems can work together. For software, that can involve exchanging data, interpreting it consistently and coordinating work across organizations. Wikipedia’s interoperability overview distinguishes communication through shared formats and protocols from the meaningful interpretation of the information exchanged. A connection that moves data and a shared understanding of that data are related, but different, achievements.
The distinction helps explain why interoperability policy extends beyond selecting an application. A system can recognize the structure of a message without interpreting its contents as another system does. Organizations can also have different processes or legal responsibilities even when the technical exchange works. The source describes cross-domain interoperability in terms of social, organizational, political and legal entities working together.
What makes a standard open?
Wikipedia’s account of open standards states that there is no single definition of the term. Some definitions emphasize access to the published specification. Others emphasize participation in drafting it, the process for reaching decisions, or the rights needed to implement it. Calling a standard open consequently does not state all the relevant conditions without identifying the definition being used.
The same article describes definitions that accept reasonable and non-discriminatory patent royalties, alongside definitions that require implementation without such fees. These differ on rights to use the specified technology, rather than merely on whether a document is publicly available. Access to a specification, access to the development process and the cost of exercising essential rights are separate dimensions of openness.
The UK government's criteria
The UK criteria recorded in Wikipedia’s open-standard reference concern collaboration, transparent decision-making, a defined review process, fair access, maturity and independence from a platform, application or supplier. They also address essential implementation rights, requiring a royalty-free basis compatible with open-source and proprietary solutions. This definition connects governance of a standard to practical access for its implementers.
The official GOV.UK policy publication identifies software interoperability, data and document formats as its scope. It describes the principles as government policy intended to make public IT more open and better connected. Its stated aims belong to that policy; they do not prove that every standard called open produces the same outcome. The publication also describes standards profiles as guidance for implementation.
Patent commitments and royalty-free use
Wikipedia’s explanation of RAND and FRAND licensing describes voluntary commitments requested by standards organizations from holders of rights essential to implementing a standard. RAND means reasonable and non-discriminatory; FRAND adds fair. These commitments concern the terms offered to implementers. The article describes their role in reconciling patent holders' rights with adoption of a common specification.
The source records different rationales for that arrangement. Commentators described the commitments as limiting licensing abuse associated with essential rights; others emphasized compensation for a technology's contribution to a standard. These are attributed explanations of the model. They do not settle which terms are reasonable in an individual agreement or establish that a royalty is absent.
Wikipedia’s royalty-free explanation distinguishes recurring charges for implementation from obtaining the specification itself. A royalty-free standard can still have a copyrighted specification sold by a standards body. Royalty-free thus addresses the use of relevant rights; it is not a statement that every associated cost, service or document must be free of charge.
Wikipedia's open-standard article states that the World Wide Web Consortium’s specifications can be implemented on a royalty-free basis. The separate W3C reference article describes its work developing technical standards for the Web. These descriptions concern a standards body's work and implementation rights, rather than an assessment of any particular browser or other software product.
Standards organizations and committees
The International Organization for Standardization reference describes ISO as an independent international standards organization with national standards bodies represented in it. Wikipedia’s ISO/IEC JTC 1 article describes the joint information-technology committee of ISO and the International Electrotechnical Commission. Its stated purpose is to develop, maintain and promote standards in information and communications technology.
Other bodies also develop specifications. Wikipedia’s Ecma International article describes a nonprofit organization for information and communication systems, while its OASIS Open article describes a consortium developing technical IT standards. The roles of a consortium, a technical committee and a national standards body are not identical. The body named on a standard indicates its development setting, not every licensing or implementation condition.
Interoperable public services
The Interoperable Europe Portal’s account of the European Interoperability Framework describes guidance for interoperable digital public services. It organizes its account around principles, interoperability layers and a conceptual model for integrated services. The listed layers include legal, organizational, semantic and technical interoperability, making the framework broader than agreement on a file format alone.
Wikipedia’s EIF article describes recommendations for communication among administrations, businesses and citizens within the European Union and across borders. The Europe policy page places the framework in its policy setting. The document-formats page examines specifications for stored records, and the health information technology page covers interoperability in a specific public-service field.