3 ms·
> you need this level of exacting precision to achieve actual interoperability. That’s then writing a dictionary, and it’s fine, but it’s not defining a standa
by kuschku 10y ago
> you need this level of exacting precision to achieve actual interoperability.
That’s then writing a dictionary, and it’s fine, but it’s not defining a standard.
As said, the one most important property of a standard is that it simplifies the existing situation, and is stricter than what came before.
The W3C once produced standards, now not anymore. The WHATWG never produced standards.
I mean, we can fucking standardize languages and adapt the way people spell something or the way they use grammatical constructs by law within of only a few years.
If we can do it with natural language, doing it with the web is completely doable. Because languages ARE infinite monkeys with infinite typewriters.
- om2 10y agoWHATWG HTML and W3C HTML both define a valid syntax for content, as well as parsing rules that cover everything, even error cases. Postel's Law states: "Be conservative in what you do, be liberal in what you accept from others.". Modern HTML standards codify this rule in a serious and detailed way. I think Jon Postel knows more about real standards than you do. People with your attitude are a big part of why the W3C HTML Working Group failed. It's easy to expound on what Real True Standards should be when you have no real skin in the game. Those with a real stake in the result care about what actually works instead, and have no time for this kind of philosophizing.