PUBLIC MARKS with tag xhtml

i.e. it took me less than 3 minutes to change my site from being exclusively written in HTML5 to being written in both HTML5 and XML: what's called a polyglot document.

This means you should always, and I mean ALWAYS, find yourself escaping for XHTML context, escaping for including a string in a URL, and escaping for a javascript context. Any time you output the contents of a variable, escape it.

Of course, then they decided to "continue evolving the specification" outside the W3C, which I strongly disagree with (browser vendors are not the custodians of the Web, and WHATWG should really be dismantled having now served its purpose: the destruction of XHTML and the advancement to HTML5).

Support any valid form of XHTML

XHTML 1.1 was obviously a mistake, as it’s used (as far as I know) nowhere else, and is a dead-end as far as web technologies go. Few automated HTML tools generate it, and the changes from XHTML 1.0 are simply annoying rather than useful.

I’d prefer that ePub support XHTML 1.0, which is simply HTML 4.01 with an XML vocabulary. HTML 4 is the dominant form of HTML on the web (and will remain so for some time) and common automated tools like Tidy can clean up “street” HTML 4 into XHTML 1.0 quite well. Tidy won’t, however, produce XHTML 1.1.

I also don’t want to put an upper bound on the XHTML supported: XHTML 5 should also be okay, and the rules for a reading system which don’t support later tags should be the same “ignore and move on” that has worked well on the web.

De mon point de vue, la tablette n'est pas intéressante pour cause d'absence d'encre électronique et d'une plateforme qui risque d'être la même que celle de l'iPhone, avec tous les niveaux de fermeture que cela comporte. Pourtant, elle fera sans doute un carton. Si c'est le cas, WebKit a de grande chance de devenir le moteur de rendu par défaut du XHTML des documents EPUB.