Open standards
In shortA format is open when more than one implementation exists — anything else is documentation.
At a glance
- Four characteristics
- Public specification, several independent implementations, open development, no licensing barriers
- The decisive test
- Are there at least two independent implementations that interoperate?
- Examples
- IMAP and SMTP, CalDAV and CardDAV, ODF, PDF/A, S3-compatible object storage interfaces, Matrix
- Common confusion
- A documented format from a single vendor is not open, it is described
- Regulatory support
- The Interoperable Europe Act and the European Interoperability Framework for the public sector
- Practical benefit
- Lowers switching cost at the format layer — the only layer that can be solved technically
Open standards are the only part of the sovereignty discussion that can be settled purely technically. Everything else — ownership, law, operations — hangs on contracts and organisations. A format either works or it does not.
That makes it worth taking the term precisely.
The four characteristics
The specification is publicly available, without a contract and without asking.
Several independent implementations exist and interoperate. That is the test that counts.
Development happens in an open body rather than in one vendor's product planning.
And use is not tied to licensing barriers that make an implementation impractical.
Why the second condition decides
A vendor can document its format completely and still remain the only party that masters it. The specification then describes what the product does, and changes when the product changes.
Only a second, independent implementation turns the description into an agreement. From that point a switch costs time rather than data — and that is exactly what Vendor lock-in is about.
Where it pays off most in practice
Four areas cover most everyday dependence: email over IMAP and SMTP, calendars and contacts over CalDAV and CardDAV, documents in ODF plus PDF/A for archiving, and object storage over an S3-compatible interface.
For chat, Matrix is the only widely used open approach. For line-of-business applications there is usually no standard at all — there only the export question remains, which belongs to every Exit strategy.
The regulatory tailwind
The Interoperable Europe Act and the European Interoperability Framework bind the public sector above all. For companies they work indirectly: anyone supplying public administration is increasingly asked about interoperability — and anyone already using open formats can answer without starting a project.
Common questions
- Is a documented format automatically open?
- No. Documentation is necessary but not sufficient. Only when several independent implementations exist and interoperate does switching become practical. Otherwise the specification merely describes what one vendor does.
- Which open standards pay off most day to day?
- Email over IMAP and SMTP, calendars and contacts over CalDAV and CardDAV, documents in ODF or PDF/A for archiving, object storage over an S3-compatible interface. Those four cover most everyday dependence.
- Do open standards solve lock-in?
- Only the format layer. Processes, in-house knowledge and contracts still bind. A heavily customised system on an open format can be more expensive to leave than a subscription product with a clean export.
- How do I spot marketing?
- By the answer to a single question: name two independent products that fully read and write this format. Anyone evading it is selling documentation as a standard.