|
I have to agree that this is rather unnecessary. XHTML as a spec might be dead, but using a valid XML serialization of HTML 5 is perfectly fine and supports evolving web standards perfectly. This is what happens in practice today anyway. Anything you can do in HTML 5 works fine when the HTML 5 is serialized as valid XML.
Forcing EPUB software developers to support HTML 5 parsing is just creating unnecessary busy work for no good reason.
The *only* advantage I can see for the HTML 5 serialization over the XML serialization is that the former is easier to write by hand. I dont think that is an advantage that justifies the cost. Most EPUB editing tools already have some kind of functionality to either flag or auto-correct invalid XML making writing it not that hard.
And I agree with KevinH that this disruptive of a change should be in EPUB 4 otherwise it will just end up getting ignored and un-used like the yoyo-ing that was done with EPUB metadata.
|