RFC 2119¶
Bradner, S. (1997). RFC 2119.
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Mechanisms¶
- Codec Specification
- The classic misuse is writing the spec after the implementation and treating whatever the code emits as the contract, which produces documentation, not specification.
This sourceWriting a codec contract in those terms is what makes "conforming implementation" a testable claim rather than a matter of interpretation.
- The classic misuse is writing the spec after the implementation and treating whatever the code emits as the contract, which produces documentation, not specification.
Verification¶
This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.
Registry ID ref:b2f326baad3e · see in the full table