Careful with Postel&#x27;s Law: it brought us a lot the mess we have with web standards.<p>Quoting wikipedia <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Robustness_principle" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;Robustness_principle</a>:<p>&gt; 
In RFC 3117, Marshall Rose characterized several deployment problems when applying Postel&#x27;s principle in the design of a new application protocol.[3] For example, a defective implementation that sends non-conforming messages might be used only with implementations that tolerate those deviations from the specification until, possibly several years later, it is connected with a less tolerant application that rejects its messages. In such a situation, identifying the problem is often difficult, and deploying a solution can be costly. Rose therefore recommended &quot;explicit consistency checks in a protocol ... even if they impose implementation overhead&quot;.