All the next generation of Web pages would be made using HTML5, rather than a new markup language. HTML5 would incrementally change HTML, instead of completely overhauling it. It would be a forgiving syntax, one that anticipates that there will be deviation from standards. Instead of forcing compliance – it makes recommendations for how Web browsers should adapt. It also adds some new features.
XHTML1/1.1, a successor to HTML4, has been the most current version of HTML. XHTML1/1.1 leveraged the strengths of XML to create well-formed Web pages. These pages could be validated against a schema to test for compliance to a standard. Perhaps most importantly, it helped fix the issue of cross-browser incompatibility.
XHTML2 was going to be the successor to XHTML1/1.1; as the name suggests. However, this ended up not being the case. HTML5 is. Here’s why: XHTML2 was actually a different language; a new abstract approach to HTML. In at least the immediate future, making Web pages would’ve been made more difficult. It was a departure from the trajectory of many HTML traditions:
- IMG elements were being phased out in favor of OBJECT elements.
- The anchors, A elements, were being phased out because, “all elements may now play the role of a hyperlink.“