HTML to Lose the Version Number

CommanderFrank

Cat Can't Scratch It
Joined
May 9, 2000
Messages
75,399
Number 5 is alive. Sorry Number 5, but your life has been cut short. I bet this came as a surprise to the guys over at the World Wide Web Consortium….I wonder what they will do with all of those hats, shirts and bumper stickers. :p

The decision to remove the version number is little more than a move to strip away a small bit of unnecessary bureaucracy and acknowledge how the HTML standards ecosystem actually functions.
 
Whatever works, I guess. Ideally, a goal of rolling spec updates for "full HTML compliance" across all browsers would be great instead of major releases once in a blue moon. Let's see how that actually pans out with end users who don't care about the intricacies of revisions (IOW, "why should I upgrade, I have a HTML browser!"). ;)
 
How does removing a number reduce the amount of bureaucracy?

Things are definitely getting weird over at the W3C.
 
I'm not sure how that changes much. But hopefully it does help a lot. The only thing I can think of is: while browser standards change, you can just rate browsers on how HTML compliant they are rather than mention what HTML 5 features they have. Seems like a political word game to get the browser devs to wake up to adopt new standards.
 
Stupid idea. Call something what it is.

Not really. Either it works, or it doesn't. Desgining a half compliant POS browser isn't going to cut it, even if it's "100% HTML5 compliant," only to break everything HTML 3.2 and down.
 
Well you don't hear version numbers with ASP and .Net and everything else. You might see something like "to execute this web code, you must have framework version X installed on the server", but that's it. It's HTML, plain and simple.

We know there's differences between HTML versions but when it comes to the average Joe and Jane, they'll bother us with questions like "what's the difference? Is HTML5 better than HTML4?" etc. It should just work. If they're running older browser or lack the proper framework or Flash or Java versions, they'd be notified of it in their browser just like they've always been with proper links to remedies.
 
Makes sense to me. No browser has ever supported 100% of one version without supporting at least part of the next version, so the version numbers are meaningless in practice.
 
Then again, I kind of wish everything would move to a continuous improvement model rather than releasing discrete versions that always seem to come right after everyone gets used to the previous version.
 
Well you don't hear version numbers with ASP and .Net and everything else.

.NET has usually been pretty active about displaying the 2,3,4. However I will lump myself in with the average Joe & Jane, cause I couldn't tell you anything about the differences between HTML versions...the only guess I would make is somewhere along the way Cascade Style Sheets was added. Oh and HTML4 must have been when they added Adsense to every website.
 
Well you don't hear version numbers with ASP and .Net and everything else. You might see something like "to execute this web code, you must have framework version X installed on the server", but that's it. It's HTML, plain and simple.

im not sure about ASP but for PHP i and many others designate between PHP4 and PHP5
version numbers are very important for compatibility sake
 
Back
Top