Having one unified term makes popularizing the technology so much easier. How to label books (etc.) which deal with HTML5 and HTML5 only is honestly an edge case and the editors of those books can certainly come up with creative solutions. That’s a compromise (not a very bad one, either) you will have to live with.
Umbrella terms have existed in the past (like “Web 2.0”, …) and they were usually distinct from the actual names of the standards (I think because the standards had names that sounded very technical) but that is just not the case with HTML5. That’s the status quo. Thinking up a different umbrella term now, in isolation from actual usage, seems counterproductive.
It may not be the most elegant solution but that’s where we are. It’s not as though the W3C can decide how people will use the term. W3C picked the realistic common sense solution.
Having one unified term makes popularizing the technology so much easier. How to label books (etc.) which deal with HTML5 and HTML5 only is honestly an edge case and the editors of those books can certainly come up with creative solutions. That’s a compromise (not a very bad one, either) you will have to live with.
Umbrella terms have existed in the past (like “Web 2.0”, …) and they were usually distinct from the actual names of the standards (I think because the standards had names that sounded very technical) but that is just not the case with HTML5. That’s the status quo. Thinking up a different umbrella term now, in isolation from actual usage, seems counterproductive.
It may not be the most elegant solution but that’s where we are. It’s not as though the W3C can decide how people will use the term. W3C picked the realistic common sense solution.