why html5? why not xhtml2?aitc.jp/events/20101202-ria/data/html5-xhtml2.key.pdf · 2010-12-06 ·...
TRANSCRIPT
![Page 1: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/1.jpg)
Why HTML5?Why not XHTML2?
Learning from history how to drive the future of the Web
![Page 3: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/3.jpg)
• HTML Working Group• Web Applications Working Group• CSS Working Group• SVG Working Group• more...
W3C Interaction domain
![Page 4: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/4.jpg)
From 1997 through the end of 2006, work on HTML within the W3C
focused exclusively on the XHTML dialect.
![Page 5: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/5.jpg)
A government in exile...
![Page 6: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/6.jpg)
From June 2004 to March 2007, work on the
(non-XHTML) HTML language took place outside of the W3C.
![Page 7: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/7.jpg)
About HTML5 (and HTML forms)...
![Page 8: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/8.jpg)
HTML5 in the words of the W3C HTML WG...
![Page 9: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/9.jpg)
HTML design principles
http://w3.org/TR/html-design-principles/
![Page 10: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/10.jpg)
HTML design principles
• Support existing content
• Ensure interoperability
• Precisely define UA behavior
•Handle errors (non-draconically)
• Evolution not revolution
![Page 11: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/11.jpg)
“Draconically”= “Draconian”=
“catch fire and fail”
![Page 12: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/12.jpg)
About XHTML2 (and XForms)...
![Page 13: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/13.jpg)
XHTML2 in the words of the W3C XHTML WG...
![Page 14: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/14.jpg)
XHTML2 Design Aims
http://w3.org/TR/xhtml2/introduction.html#aims
![Page 15: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/15.jpg)
XHTML2 Design Aims
• Use existing XML facilities rather than duplicating them (implies namespace support)
• Less scripting (vs declarative approach)
• Integration with Semantic Web
![Page 16: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/16.jpg)
What does“declarative” mean?
![Page 17: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/17.jpg)
Declarative programmingsuccess story: SVG
(XSLT also? XForms?)
![Page 18: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/18.jpg)
HTML5 and XHTML2in contrast...
![Page 19: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/19.jpg)
Things HTML5 doesn’t do
•Does not favor XML facilities
•Does not avoid scripting
•Does not consider integration with the SemWeb a priority
•No arbitrary namespaces
![Page 20: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/20.jpg)
Things XHTML2 did not do
• Does not support existing content in the same way that HTML5 does
• Does not precisely define UA behavior
• Does not handle errors non-draconically (uses “catch fire and fail” error handling)
![Page 21: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/21.jpg)
Important point: XHTML2 was a
different language than XHTML1
![Page 22: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/22.jpg)
...“different language” in that XHTML2 does not fully support existing XHTML1 content (not backward compatible)
![Page 23: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/23.jpg)
A representative statement about the difference in philosophy:
“HTML is the assemblylanguage of the Web.”
![Page 24: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/24.jpg)
Important point: In some cases HTML5 offers a
choice of both declarative and scripting
approaches.
![Page 25: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/25.jpg)
About error handling...
![Page 26: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/26.jpg)
• Well-formed XML: <input disabled="disabled"> • Empty attribute: <input disabled> • Without quotes: <input value=yes> • Single quotes: <input type='checkbox'> • Double quotes: <input name="be evil">
Which of these are errors?
![Page 27: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/27.jpg)
<i><b>misnested tags</i></b>
This is a real error
![Page 28: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/28.jpg)
HTML5 parsers can handle real errors interoperably
and gracefully.
![Page 29: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/29.jpg)
Why is it important to handle errors?
![Page 30: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/30.jpg)
More than 93% of Alexa Top 500 sites
contain HTML conformance errors.
![Page 31: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/31.jpg)
A little history...
![Page 32: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/32.jpg)
(About draconian error handling in XML)
I think users and application builders should have a choice with what they do with invalid data... I therefore plan to continue to provide it even if the
spec says that this is non-conforming.
April 1997 ◦ I think users and application builders should have a choice with what they do with invalid data. I cannot see
how a user or application builder can be disadvantaged by being provided with this choice, and I therefore plan to continue to provide it even if the spec says that this
![Page 33: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/33.jpg)
After careful consideration, the HTML Working Group has decided
that the goals for the next generation of forms are incompatible with
preserving backwards compatibility with browsers designed for earlier
versions of HTML.
August 1999
![Page 34: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/34.jpg)
W3C has no intention to extend HTML 4 as such. Instead, further
work is focusing on a reformulation of HTML in XML
November 1999
![Page 35: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/35.jpg)
...while the ancestry of XHTML 2 comes from HTML 4, XHTML 1.0,
and XHTML 1.1, it is not intended to be backward compatible with its
earlier versions
August 2002
![Page 36: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/36.jpg)
XHTML 2.0 seems to me the live proof that something is going wrong
at W3C... I strongly suggest dropping all XHTML 2.0 efforts in
favor of a new “xHTML 5.0” language. Clearly a successor to
HTML 4, feature-oriented, made for the web.
December 2002
![Page 37: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/37.jpg)
The W3C had so far failed to address a need in the Web
community: There is no language for Web applications... I intend to do something about this (hopefully
within a W3C context, although that will depend on the politics
of the situation).
January 2004
![Page 38: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/38.jpg)
The dream of a new web, based on XHTML+SVG+SMIL+XForms, is just
that — a dream... The best way to help the Web is to incrementally
improve the existing web standards... so that web content authors can actually deploy new
formats interoperably.
June 2004
![Page 39: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/39.jpg)
We need to specify error handling behavior to ensure interoperability
“even in the face of documents that do not comply to the letter of the
specifications”.
![Page 40: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/40.jpg)
Authors will write invalid content regardless of what we spec. So the spec states “what authors must not
do, and then tells implementors what they must do when an author
does it anyway”.
![Page 41: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/41.jpg)
It is necessary to evolve HTML incrementally. The attempt to get the
world to switch to XML, including quotes around attribute values and
slashes in empty tags and namespaces all at once didn’t work...
October 2006
![Page 42: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/42.jpg)
more HTML history
http://w3.org/html/wg/wiki/History
![Page 43: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/43.jpg)
HTML5 has a major focus on facilitating use of a browser as a Web application platform (or Web application runtime environment).
![Page 44: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/44.jpg)
XHTML2 had a major focus on providing a general-purpose document language with declarative mechanisms to enable interactive features.
![Page 45: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/45.jpg)
HTML5 support
• specific native browser support being implemented by all major browser vendors
• spec remains in active development
![Page 46: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/46.jpg)
XHTML2 support• no specific client-side native
browser support from any major browser vendor
• … but was intended to be possible to “bolt on” some level of support using CSS+JS
• last WD: 2006
![Page 47: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/47.jpg)
The bottom line...
![Page 48: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/48.jpg)
HTML5 is the only HTML dialect that will be natively supported in browsers on the client side.
![Page 49: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/49.jpg)
Some HTML5 differences...
![Page 50: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/50.jpg)
HTML5 defines HTML as an abstract language with two standard syntaxes supported by browsers:
• a text/html syntax, with parsing rules defined by the HTML5 spec
• an XML syntax, with parsing rules defined by the XML spec
![Page 51: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/51.jpg)
Similarly, applications can potentially represent HTML in
memory in any number of ways.
![Page 52: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/52.jpg)
http://software.hixie.ch/utilities/js/live-dom-viewer/
![Page 53: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/53.jpg)
However, there’s only one standard in-memory representation supported
by browsers: The W3C DOM.
The HTML5 spec precisely defines the DOM representation that
browsers must use to represent HTML content in memory.
![Page 54: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/54.jpg)
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
![Page 55: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/55.jpg)
<!DOCTYPE html>
![Page 56: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/56.jpg)
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
![Page 57: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/57.jpg)
<meta charset="utf-8">
![Page 58: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/58.jpg)
Important point:HTML5 includes XHTML
(but not XHTML2...)
![Page 59: Why HTML5? Why not XHTML2?aitc.jp/events/20101202-RIA/data/html5-xhtml2.key.pdf · 2010-12-06 · Why HTML5? Why not XHTML2? Learning from history how to drive the future of the Web](https://reader035.vdocument.in/reader035/viewer/2022062922/5f09b3737e708231d4281989/html5/thumbnails/59.jpg)
Frequently Asked Questions (FAQ) about the future of XHTML
http://www.w3.org/2009/06/xhtml-faq.html