W3C 'clarifies' HTML 5 v XHTML
|
|
|
Comments (5)
As a counterpoint:
Say you have some data. Your only problem is how to represent it.
You go with XML.
Now you have two problems.
Just sayin'.
Say you have some data. Your only problem is how to represent it.
You go with XML.
Now you have two problems.
Just sayin'.
1. HTML5 has a video element.
2. The HTML5 draft defines a parallel XML serialization for HTML5. The XML serialization is called XHTML5.
Quoting:The XML serialization is called XHTML5
Oh great. I love the confusion.
AFAIR they decided to work off HTML because they wanted evolution, not revolution. I think they're wrong, because it will waste a great chance to clean up this HTML mess, but at least I understand them...
Quoting:The XML serialization is called XHTML5
Sigh...
While HTML5 does have some nice features, it's stupid things like this that makes me prefer XHTML2 when it's out.
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help
Sign up and post (it is free) or Log in and post

The only reason I can think off why they would do this is because they "felt" like they couldn't also be working on XHTML2 since W3C was already working on it. And that's a pretty lousy reason to stick with SGML.