That may be true, but it is irrelevant. I don't know why you believe that the technologies under the W3C web standards need be open. The standards themselves ne

That may be true, but it is irrelevant. I don't know why you believe that the technologies under the W3C web standards need be open. The standards themselves need be open (they're published, after all), but the technologies underpinning them? Checking W3C's website, their guidelines for implementations appear to be "W3C issues a call for implementations as part of standardization and welcomes public participation" [https://www.w3.org/participate/implementation https://www.w3.org/participate/implementation]. Nothing in the formal standards process [https://www.w3.org/2005/10/Process-20051014/tr.html https://www.w3.org/2005/10/Process-20051014/tr.html] appears to require all implementations be "open," and that assumption flies in the face of previous legacy standards (<img> when .gif was an accepted file format but still encumbered by patent, the <object> and <embed> standards that specify closed-binary plugins to side-load). While it'd be nice if it worked the way you described, it seems that the standard as currently codified (including one specified "dummy" open reference implementation) is all that is needed.