3 ms·
w3c is completely irrelevant. https://whatwg.org/ https://whatwg.org/ is the functional keeper of the standard.
by bryanlarsen 3y ago
w3c is completely irrelevant. https://whatwg.org/ https://whatwg.org/ is the functional keeper of the standard.
- Eduard 3y agohttps://news.ycombinator.com/context?id=36882166 https://news.ycombinator.com/context?id=36882166 W3C is not only about HTML, JavaScript, and CSS. https://en.m.wikipedia.org/wiki/World_Wide_Web_Consortium#Standards https://en.m.wikipedia.org/wiki/World_Wide_Web_Consortium#St... E.g., I don't see WHATWG contributing anything of relevance regarding web accessibility, whereas W3C takes care of accessibility with WAI-ARIA and WCAG.
- tw061023 3y agoMy understanding is that WHATWG doesn't govern standards at all - it basically documents what browsers are doing at the moment. So when Google rolls WEI in a Chrome update, it will become a WHATWG "standard" automatically. Is that correct?
- notatoad 3y agono, to become a standard at least one other browser vendor would have to at least signal an intent to implement it.
- troupo 3y agoNo. To actually become a standard it needs at least two inependent implementations. But it's interesting that you wrote what you wrote. Because that's exactly what Chrome is doing: it's announcing an intent to implement, and then enables whatever they intend by default. Oh, they do pretend to ask other vendors about their position, but ship anyway. And then use web.dev to pretend it's a standard.
- seabass-labrax 3y agoThe W3C is relevant in multiple critical areas of the Web. Just to name a few topics where W3C is the primary venue for all standardisation efforts: - Accessibility - Authentication - CSS - Self-Sovereign Identity - Virtual Reality - Linked Data - XML I wrote a comment about the W3C's relationship with WHATWG a few days ago: https://news.ycombinator.com/item?id=37052428 https://news.ycombinator.com/item?id=37052428 If you do nothing else, please pass your eyes over the list of W3C Recommendations and other publications on standards track: https://www.w3.org/TR/ https://www.w3.org/TR/
- 1letterunixname 3y agoExactly. They were the original resource as far back as the mid-90's. They originated SGML, HTML <3.0 .. 4.01, CSS, XML (XPath, XSLT), and so forth. And yes, even VRML :) https://www.w3.org/MarkUp/html-spec/ https://www.w3.org/MarkUp/html-spec/ HTML 2 (the wild west) https://www.w3.org/MarkUp/Wilbur/ https://www.w3.org/MarkUp/Wilbur/ HTML 3.2 https://www.w3.org/TR/WD-html40-970708/appendix/changes.html https://www.w3.org/TR/WD-html40-970708/appendix/changes.html Diffs of HTML 3.2 -> 4 https://www.w3.org/People/Raggett/book4/ch02.html https://www.w3.org/People/Raggett/book4/ch02.html History of HTML until 3.2 https://www.w3.org/TR/html401/ https://www.w3.org/TR/html401/ HTML 4 https://www.w3.org/TR/html5-diff/ https://www.w3.org/TR/html5-diff/ Diffs of HTML 4 -> 5 https://www.w3.org/TR/2021/NOTE-html53-20210128/ https://www.w3.org/TR/2021/NOTE-html53-20210128/ HTML 5.3 (last version on W3C) https://html.spec.whatwg.org/multipage/ https://html.spec.whatwg.org/multipage/ HTML5.3+ (moved to whatwg) https://www.w3.org/MarkUp/VRML/ https://www.w3.org/MarkUp/VRML/ Virtual Reality Markup Language