Which one should I use: HTML5 or XHTML5?

In most cases, the answer is HTML5. XHTML5 doesn’t work in IE. (Just like technical XHTML has never worked in IE. Only the marketing kind of XHTML has worked in IE.)

Sauf que HTML 5 en syntaxe HTML5 ne marche (et ne marchera) pas plus dans IE que dans la sérialisation pseudo-XML de HTML 5 abusivement appelée XHTML5. Encore de la bonne grosse désinformation de la part de la WTF.

And may be the spec doesn't need to be optimised for HTML guide authors either. They can treat HTML 5 as a black box too, and just read HTML 4 etc for the things that are obviously lacking in HTML 5. And in general. Authors can dig.

Mais c'est bien ce qui est demandé, HTML 5 est le nouveau XAML :-D

The HTML5 specification is political manifesto, cleverly disguised as a specification.

Cleverly ? De l'intelligence qui fait inventer l'eau chaude alors.

For the "Status" section to be changed to "Accepted", the proposed keyword must either have been through the Microformats process, and been approved by the Microformats community;

Oui oui, on est bien en train de parler de HTML 5 là.

# [14:27] <Philip> (Is it safe to assume that "the global market" speaks English?) # [14:27] <hsivonen> Philip: for software developers, yeah (except perhaps for Japan, I guess)

Le village global qui ne voit pas plus loin que le bout de son nez.

Henri: it’s hard to keep track of all the places where you post the same old arguments while refusing to take into account the responses you’ve already seen multiple times on the HTML5 list.

Henri passe-t-il le test de Turing ?

HTML5, however, exposes the varying state of the tree throughout; an application may examine a new element's parent pointer at one point, find one value, and then examine it after new events have been processed and find a different value. The very nature of SAX events prohibits that degree of flexibility.

Implémenter le modèle de parsing de HTML5 dans libxml est-il possible sans bouleverser la structure interne de libxml ?

Validator.nu does offer file upload and pasting file contents in its complex generic facet

WebKit had a number of minor parsing bugs that Acid 3 targeted. [...] We have updated our parser to be much closer to the HTML5-specified parsing rules.

For all these reasons, HTML 5 looks to me as a big step backward and XHTML 2.0 seems to be a much better alternative.