No, it doesn’t. The SC said “unless expressly defined”, and the RFC expressly defines it.
No, it doesn’t. The SC said “unless expressly defined”, and the RFC expressly defines it.
There's also no reason for legal contracts or laws to be written with archaic formulations, but common law countries have a fetish for this kind of thing.
Implementations should support the entire spec, and not produce something outside of spec, then every implementation can interact with every other implementation.
If the implementers can't agree what's within spec and what's not, it's a bug in the spec.
Law has a similar requirement, only slightly looser because it has a fallback of getting a human judge to decide in case of disagreement. Still, ambiguity in a law is a bug.
In both cases, you do use natural language, which can rely on context, so the real test is, or should be, whether a "reasonable person" would choose a different interpretation, not whether one is technically possible.
One example from my past was a contract that levied specific requirements for equipment operated autonomously with software, but "autonomous" wasn't explicitly defined. A contractor who didn't want to spend the money to meet the extra requirements argued the system couldn't be considered autonomous because it required a human to turn it on (despite being fully autonomous after that point).