4 ms·
> So what is the Web? Well we can agree the Web is a conglomerate of standards proposed by the W3C. No, I can’t agree with that because it hasn’t ever been tru
by chrismorgan 6y ago
> So what is the Web? Well we can agree the Web is a conglomerate of standards proposed by the W3C.
No, I can’t agree with that because it hasn’t ever been true. For its first decade, it was the place where most relevant standards were proposed, but that still didn’t define the web; you had to look at what browsers did rather than what specs said, especially in such days as IE’s domination, because it varied quite substantially from the “standards”, and more importantly people depended on these variations and extensions to the “standards”.
But then W3C tried to take the web further in a direction that the actual people with power (browser manufacturers) didn’t like—more XML everywhere, and little to no activity on HTML itself—and so they split and formed WHATWG which has since taken over progressively more and more of the actual important standards (e.g. HTML, DOM, URL, Fetch, Encoding), so that W3C itself is increasingly irrelevant, though there are still important things that are done through W3C, e.g. the CSS Working Group (CSSWG); and if you’re willing to stretch it, you could count the Web Incubator Community Group (WICG), but that’s more hosted by W3C than part of W3C.
Nowadays, if you say, “what is the web?”, you must include specifications from at least IETF (e.g. HTTP), WHATWG (e.g. HTML), W3C (e.g. CSS) and Ecma (e.g. JavaScript); but actual browser behaviour (an extremely vague concept) must also be considered too, because it has a big impact on what the web is.
- totallymike 6y agoDecent point. If my recollection is accurate, a number of browsers or other implementations must already implement something before it can become standard.
- fergie 6y agoI have to confess that I didnt know anything about WHATWG until I read this comment- I always assumed that HTML was defined by W3C.
- chrisseaton 6y ago> I always assumed that HTML was defined by W3C Yes I think that's the impression they try to create.
- acoard 6y agoTo be clear, initially HTML was defined by the W3C. Then when they tried to replace HTML with XML and the browser vendors revolted, the W3C essentially lost control over this. Basically the W3C over-played it's hand. It thought by re-writing standards from HTML to XML it could force Apple/Opera/Mozilla to re-write. In the end, the browser vendors got together and created a new body that would be responsible for HTML. They've skirmished for control, but there's no question WHATWG and browser vendors are in ascendency. From 2007-2019 they both had competing standards of HTML, but since the browser vendors were on WHATWG they would just implement their own version making it the de-facto standard. So, in 2019 W3C announced they'd just use the WHATWG HTML.[0] I expect if the W3C pushes anything the vendors consider too arduous (eg a re-write of CSS into constraints), then WHATWG would create a CSS working group and the process would repeat. This reminds me a lot of the power of the Supreme Court, specifically President Johnson's quote about it when they made a ruling he didn't like. "[The Chief Justice on the court] has made his decision; now let him enforce it"[1] The stakeholders of WHATWG have an army (of browser coders), whereas W3C needs to rule by consent of the ruled like the Supreme Court does. ---- [0] https://en.wikipedia.org/wiki/WHATWG https://en.wikipedia.org/wiki/WHATWG [1] https://en.wikipedia.org/wiki/Worcester_v._Georgia#Enforcement https://en.wikipedia.org/wiki/Worcester_v._Georgia#Enforceme...
- pgt 6y agoStandards are just out-of-date documentation.
- mandelbrotwurst 6y agoThey're more like a proposed specification.
- pgt 6y agoStandards are usually written after the implementation.