Then why are they making standards in the first place?
They're already deeply involved in the operation of browsers; they are practically morally obliged to object to things which could harm the Web.
I'm not arguing if the OP is right or not but I don't think the OED example is correct.
A better example would be a language academy, however English has never had a language academy, unlike French or Spanish, resulting in it being a stubbornly descriptivist, rather than prescriptivist phenomenon.
I had to give a chuckle at that, but seriously, the way in which words are spelt (ahem) in the OED is genuinely interesting! They use both -ize and -ise, for instance, choosing one or the other based on each individual word's etymology.
The OED, in my experience, covers the varieties of English spelling quite well, and if you want no distractions as an American but can deal with less extravagantly complete coveraged, you can always use the OAD.
Oxford seems to know how to spell quite well.
The OED includes American spellings for all of its entries.
Source: I have an OED subscription and look at it regularly.
For one thing, membership in W3C is loaded with representatives from those browser vendors. Which is a good thing, since W3C would be absolutely useless if browser vendors weren't there.
For another, standards aren't the place for rants about who sucks shit and who doesn't. It would be a fun read, but a bad standard. A standard is for saying what you must do, not for saying who sucks shit.
You should too.
https://www.ftc.gov/about-ftc/bureaus-offices/bureau-competi...
for the FTC's contact information
I agree we shouldn't let a single web browser dominate. I'm just saying that the W3C doesn't have any power to do so nor have they shown themselves capable of pulling it off.
Who would grant them such a authority and how would it be enforced?
Most blocs have their own standards. Commonwealth countries follow one standard, EU countries another, North American engineering standards are not the same as Japanese ones.
> Aim to reduce centralization in Web architecture, minimizing single points of failure and single points of control.
IMO it is entirely in scope for, and part of the responsibility of, the W3C to introduce a specification that explicitly forbids user agents from implementing Web Environment Integrity or any similar system as currently drafted.
One might say that the members' conflicts of interest make it likely that they will abdicate this responsibility, but that doesn't make it any less their role!
Maybe Google cares, maybe not, but there's no sense in having a spineless standards body that just turns around and says that the spec is whatever Google implements in Chrome.
It's not W3C's (or WhatWG's) role to "oppose" random things browser vendors decide to do.