A standard is an agreed specification that lets independent products work together: a protocol, a file format, a language. Standards are written by committees and open groups, and their value is interoperability. Reading one is a skill in itself, because the text is precise, formal and written for implementers.
Key concepts
- Interoperability: two independent implementations of the same text can talk to each other.
- Normative and informative text: what you must do, versus notes and examples.
- Requirement keywords: MUST, SHOULD and MAY have defined strengths in many specifications.
- Process: drafts, public review, comments, consensus and revision.
- Conformance and testing: test suites and profiles show whether an implementation follows the text.
Vocabulary
- RFC: request for comments, the document series used for internet protocols.
- Specification: a precise description of behaviour or format.
- De facto standard: a practice widely used without a formal body behind it.
- Errata: published corrections to a standard.
What to study, in order
- Read a short specification, such as a simple protocol, marking every MUST.
- Implement a small piece of it and write tests straight from its examples.
- Compare two implementations and find where they disagree and why.
- Follow a draft through public discussion and note what changed.
- Learn the difference between an open, royalty-free text and one with restrictions.