Earlier quoted context omitted.
> Copyright © 2017 WHATWG (Apple, Google, Mozilla, Microsoft). This work is licensed under a Creative Commons Attribution 4.0 International License. See https://creativecommons.org/licenses/by/4.0/ > You are free to: > Share — copy and redistribute the material in any medium or format > Adapt — remix, transform, and build upon the material for any purpose, even commercially.
I think the point here is not about the legality but more about the ethics of doing so, in this case.
HTML 5.2 Recommendation
31–40 of 188 posts
Re: HTML 5.2 Recommendation
#32Re: HTML 5.2 Recommendation
#33Re: HTML 5.2 Recommendation
#34Earlier quoted context omitted.
For those who have not been paying attention for a decade, what's the relationship between this revision and WHATWG?
Full story here: https://www.reddit.com/r/javascript/comments/5swe9b/what_is_... tl;dr: Ignore w3c's HTML "standards" as they are (often poor) copies of WHATWG's standards.
I my opinion one cannot call something a "standard" that changes every few days.
EDIT: In this sense W3C's HTML 5.x can be considered a rather badly authored (cf. other comments here) standard, while what the WHATWG releases is not something that even measures up to a standard, but it is the daily version of how HTML is supposed to be today.
Re: HTML 5.2 Recommendation
#35Re: HTML 5.2 Recommendation
#36Earlier quoted context omitted.
> Copyright © 2017 WHATWG (Apple, Google, Mozilla, Microsoft). This work is licensed under a Creative Commons Attribution 4.0 International License. See https://creativecommons.org/licenses/by/4.0/ > You are free to: > Share — copy and redistribute the material in any medium or format > Adapt — remix, transform, and build upon the material for any purpose, even commercially.
I think the point here is not about the legality but more about the ethics of doing so, in this case.
Re: HTML 5.2 Recommendation
#37it's a document markup language and shouldn't be used for apps.
Re: HTML 5.2 Recommendation
#38Earlier quoted context omitted.
It is. W3C HTML5 standards are merely following/copying what WHATWG and the browser makers are doing, with little actual relevance.
The relevance it that W3C HTML5 standards are supposed to already be stable everywhere, while WHATWG and the browser is a guessing game of what actually works and behaves the same way everywhere.
For the question "is this supported widely enough", caniuse.com + your local traffic stats is in most cases more relevant than inclusion in some spec or not.
Re: HTML 5.2 Recommendation
#39Regardless of the state of W3C, if I built an embedded renderer based on their specs, I could at least say, "this renderer is based on and link to the recommended spec version. Whereas if I did that with the living standard href, I'd be out of date any time they decided to rename an attribute.
Re: HTML 5.2 Recommendation
#40"Although we have asked them to stop doing so, the W3C also republishes some parts of this specification as separate documents."
> Copyright © 2017 WHATWG (Apple, Google, Mozilla, Microsoft). This work is licensed under a Creative Commons Attribution 4.0 International License. See https://creativecommons.org/licenses/by/4.0/ > You are free to: > Share — copy and redistribute the material in any medium or format > Adapt — remix, transform, and build upon the material for any purpose, even commercially.
If that isn't the world you want to live in, let's get rid of this idea that just because I have no interest in the government stopping you from doing a thing by threatening violence (and that's all a license is - a statement that the following activities are not copyright infringement), I'm totally fine with you doing the thing.