Comment by assimpleaspossi
9 hours ago
It's not a technical term. Nowhere in the current HTML standard will you find a versioning of HTML. That's why it's now called a "living standard". You will never find a HTML6 or higher. That note you found is to help with any confusion.
> You will never find a HTML6 or higher
You might be right, but we don't know yet. Microsoft said that for Windows 10.
You might also be right that the current Living Standard specification doesn't really call it HTML5, but you'll find many people writing HTML for a living say HTML5 to refer to it, and telling them that HTML5 doesn't exist doesn't really help and is a bit wrong too if you have a descriptive approach to languages.
I'm still hopeful.
The next version of html should be able to do all the http verbs -- get, put, patch, post, delete online, reactively without having to use a form.
There has to be a way to figure this out, even if it requires a transition period. The best time to plant a tree was twenty years ago, the second best time is now. These things belong in the core HTML standards, not a js library you need to include in your code.
Oh that and better controls and better defaults but I guess that is something individual web browsers can implement on their own?
> that is something individual web browsers can implement on their own?
Yes, they could, but you want a standard that makes them all implement stuff in a compatible way… :-)
Telling them HTML5 does exist does even more harm cause it doesn't exist. Telling them it does exist is entirely wrong and is even a false statement, is misleading and causes confusion.
Ok, I'll bite.
Assuming you are right and HTML5 doesn't exist. What would be the actual bad outcomes of the following?
- believing HTML5 exists
- silently choosing to understand what someone mentioning HTML5 obviously meant
25 replies →
One of the annoying things about having a living standard is that it is difficult to implement a conforming version as additional updates means that you are no longer conforming.
Versioned standards allow you to know that you are compliant to that version of the specification, and track the changes between versions -- i.e. what additional functionality do I need to implement.
With "living standards" you need to track the date/commit you last checked and do a manual diff to work out what has changed.