Brett Patterson wrote:
From the few recent posts, I have become so far confused, as anyone would as to why, Gunlaug, you keep stating xHTML5 or as above you say XHTML5? HTML and xHTML/XHTML are different. xHTML is XHTML, albeit 1.0 or 1.1 or 2.0 etc. So, is it a typo?

No typo, but I understand the confusion.

We may call it 'HTML5', '(x)HTML5', 'xHTML5' or 'HTML5 + XML
serialization', as the 'HTML5' drafts in existence to date cover both
HTML and XHTML as two flavors, or rather "serializations", of the same
markup language.

See:
<http://www.w3.org/QA/2008/01/html5-is-html-and-xml.html>
<http://dev.w3.org/html5/html-author/>

Keep in mind that we're reading drafts, so nothing is set in stone, and
won't be for years to come. Gives us a good indication of how they're
continuing, and smoothing, the relationship between 'HTML' and XHTML
that began with 'HTML4' and 'XHTML1.0' though.


To exemplify: one can in most cases just change doctype and a meta, and
serve a valid and tested XHTML1.0 Strict document...
<http://www.gunlaug.no/html5-demo.html>
...as valid HTML5 (text/html)...
<http://html5.validator.nu/?doc=http%3A%2F%2Fwww.gunlaug.no%2Fhtml5-demo.html&showsource=yes>
...or as valid XHTML5 (application/xhtml+xml)...
<http://html5.validator.nu/?doc=http%3A%2F%2Fwww.gunlaug.no%2Fhtml5-demo.xhtml&showsource=yes>

Note which validator I use - <http://html5.validator.nu/>, as the
experimental W3C HTML5 validator won't play ball yet.
I can't judge which one is more correct on every detail than the other,
as both validators are new and experimental and will be tuned to spec in
time. Thus, I may have to make minor adjustments to how I modify my old
markup, once the dust settles around xHTML5 :-)


Unless they introduce major changes to the specs, the syntactic
differences are not creating any real problems for us who serve valid
XHTML1.0 as 'text/html' and/or 'application/xhtml+xml' today.
Only one or two HTML4/XHTML1.0 elements are "signaled to be" deprecated
in xHTML5, so that's not a problem.
Serving a document as 'text/html' vs. as 'application/xhtml+xml' does of
course introduce potential problems in other areas, but nothing really
new for the average document there either.

regards
        Georg
--
http://www.gunlaug.no


*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
*******************************************************************

Reply via email to