An open standard is a technical specification that is publicly available, developed through an open and consensus-based process, and implementable by anyone without discriminatory restrictions. In interoperability, open standards are what allow software from different vendors to exchange data and work together without one company controlling the rules.
Familiar examples include HTTP, HTML, TCP/IP, Unicode, JSON and PDF. There is no single legal definition of the term, and organizations disagree mainly on one point: whether a standard is still open when implementers must pay patent royalties. That disagreement shapes procurement rules, licensing and the design of file formats.
Criteria that make a standard open
A standard is judged open by how it is created, how it can be obtained and how it can be used. Definitions from governments, standards bodies and industry groups overlap on most criteria.
| Criterion | What it requires | What it prevents |
|---|---|---|
| Open development | Any interested party can participate and comment | Control by a single vendor |
| Consensus decisions | Changes approved through documented procedures | Unilateral changes to the rules |
| Public availability | Full text free or at a nominal cost | Hidden or partial documentation |
| Fair patent licensing | Royalty-free or FRAND terms for essential patents | Blocking competitors through patents |
| Complete specification | Enough detail to build an independent implementation | Dependence on one reference product |
| Stable maintenance | A neutral body responsible for versions and errata | Abandonment or arbitrary forks |
The completeness criterion is often underestimated. A format can be published yet still be impractical to implement if the specification omits behavior that only the original vendor’s product defines, which is why independent, interoperable implementations are the strongest evidence that a standard is truly open.
Royalty-free and FRAND licensing
Most technical standards touch patents, so the licensing policy of the standards body decides who can implement them. Two models dominate.
| Model | Terms | Typical bodies or fields | Effect on open source |
|---|---|---|---|
| Royalty-free | Essential patents licensed at no charge | W3C web standards, most IETF protocols | Fully compatible |
| FRAND | Fair, reasonable and non-discriminatory royalties | ISO, IEC, ITU, mobile and video codecs | Often difficult or impossible |
| Undeclared | No commitment from patent holders | Some industry consortia | Uncertain legal risk |
FRAND terms are open to all bidders but not free. Per-copy royalties are incompatible with software that anyone may copy and redistribute, so many open source projects cannot ship FRAND-encumbered features. Video coding illustrates the split: HEVC is licensed through several patent pools, while AV1 was designed to be royalty-free by the Alliance for Open Media.
Open standards compared with related concepts
The term is frequently confused with open source software, de facto standards and merely documented formats. Each describes something different.
| Concept | What it is | Example | Key difference |
|---|---|---|---|
| Open standard | A specification governed openly | HTML, ODF | Describes behavior, contains no code |
| Open source software | An implementation with an open license | A browser engine | Code, which may or may not follow standards |
| De facto standard | A widely used format controlled by one party | Many proprietary file formats | Popularity without open governance |
| Published proprietary format | Documentation released by the owner | A vendor’s documented binary format | Owner can change it unilaterally |
| De jure standard | A standard approved by a formal body | ISO 32000 for PDF | Formal status, not always open licensing |
These categories can change over time. PDF began as a proprietary Adobe format and became the open international standard ISO 32000 in 2008. Office document formats followed a similar path, with ODF standardized as ISO/IEC 26300 and Office Open XML as ISO/IEC 29500.
Why open standards matter for interoperability
Open standards are the main defense against vendor lock-in. When data is stored and exchanged in an openly specified format, an organization can change suppliers, run several products side by side and read its own archives decades later.
- Data portability: records can move between applications without lossy conversion.
- Competition: several vendors can implement the same standard, which keeps prices and quality in check.
- Long-term preservation: archives remain readable after the original product disappears.
- Public procurement: many governments require open standards so citizens are not forced to buy specific products.
An open standard does not guarantee perfect file compatibility, however. Implementations differ in completeness, defaults and bugs, so conformance testing and interoperability events remain necessary.
Limitations and common misconceptions
Openness is a spectrum rather than a yes-or-no property, and several common beliefs about open standards do not hold.
| Misconception | Reality |
|---|---|
| Published means open | Openness also needs fair governance and licensing |
| ISO approval means royalty-free | ISO accepts standards under FRAND terms |
| Open standards are always better | They can evolve slowly and lag behind proprietary features |
| One standard ends compatibility problems | Optional features and extensions still cause differences |
Standardization also takes time: formal processes can need several years from draft to approval. For fast-moving areas, a good practice is to adopt the open standard for storage and exchange, while accepting proprietary features inside individual tools.
A non-technical view
An open standard is a shared rulebook that anyone may read and follow. Think of electrical plugs in one country. Any manufacturer can build a lamp that fits the socket, and no single company decides who may do so.
Software works the same way. Because web pages follow open standards, any browser can display any website. The result is freedom of choice: you can switch products without losing access to your files or services.
A concrete example
A regional government publishes about 3,000 editable documents a year for citizens and businesses, such as forms and consultation drafts. Recipients complain that some files open incorrectly because they require one specific office application.
The government adopts a policy: editable documents are exchanged in ODF, documents meant only for reading are published as PDF/A, and data tables are released as CSV with UTF-8 encoding. Staff can still use any office suite, provided it saves in the required formats.
Within a year, complaints about unreadable files fall sharply, and the administration can tender office software competitively because no vendor holds its archives hostage. Documents stored today will remain readable after the products used to create them are retired.