Comments on: XHTML2 vs. HTML5 http://tech.navarr.me/2008/01/xhtml2-vs-html5.html The Technical Side of my Life Tue, 07 Feb 2012 22:49:00 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: The Buzz Saw http://tech.navarr.me/2008/01/xhtml2-vs-html5.html/comment-page-1#comment-33 The Buzz Saw Fri, 29 Feb 2008 21:07:00 +0000 http://temptech.gtaero.net/?p=4#comment-33 I completely agree with this. Once I began researching XHTML2 and CSS3 in great detail, I wanted them both very badly. I do not understand why the current browser industry is so fickle when it comes to implementing standards. Is it REALLY that difficult to implement? Shouldn't having a concrete specifications document make it easy to design and test?<br/><br/>Also, I agree on the HTML5 issue. Why is that system being updated? Let XHTML shine! We do not want to promote the old way of web programming! I completely agree with this. Once I began researching XHTML2 and CSS3 in great detail, I wanted them both very badly. I do not understand why the current browser industry is so fickle when it comes to implementing standards. Is it REALLY that difficult to implement? Shouldn’t having a concrete specifications document make it easy to design and test?

Also, I agree on the HTML5 issue. Why is that system being updated? Let XHTML shine! We do not want to promote the old way of web programming!

]]> By: Hixie http://tech.navarr.me/2008/01/xhtml2-vs-html5.html/comment-page-1#comment-2 Hixie Fri, 04 Jan 2008 03:47:00 +0000 http://temptech.gtaero.net/?p=4#comment-2 Actually the HTML5 spec doesn't take a position on HTML vs XHTML, the WHATWG HTML5 spec extends both at the same time and so leaves the choice of which to use up to the Web author.<br/><br/>You say that XHTML was started and controlled by the W3C group, making sure it gets properly implemented, but in fact XHTML1 was only implemented by Apple, Opera and Mozilla, the same companies that initially started the WHATWG, and XHTML2 was not implemented by anyone, and some of the browser vendors have even said they'll likely never implement it, so it's not clear that the W3C actually are making sure it's getting implemented.<br/><br/>With HTML5, I (as the editor) am talking to the browser vendors on a regular basis to make sure that they will implement it, and am making sure that it isn't wild and unordered.<br/><br/>We're also making very sure that HTML5 is just a backwards-compatible extension to HTML, so that browsers don't have to implement yet another set of standards, as you put it. In fact, we're defining the legacy HTML in HTML5 in extreme detail so that new browser vendors can write new browsers without having to reverse-engineer the other browsers (in the past, the specs were very incomplete and it was basically impossible to write a new browser without referring to the other ones).<br/><br/>Web Forms 2.0 is a part of HTML5. We actually started HTML5, starting with Web Forms 2, specifically because we didn't think XForms, XML Events, and XHTML2 were going to be improving the Web.<br/><br/>However, we actually are working with the W3C now. There's an HTML5 working group in the W3C that is chartered to work with the WHATWG.<br/><br/>If you would like to take part in this work, please do feel free to do so. You need but join the whatwg@whatwg.org mailing list, which you can find at: http://whatwg.org/mailing-list#specs<br/><br/>If you have any feedback and don't want to join the list you can also just e-mail me directly at: ian@hixie.ch<br/><br/>We do want your feedback! Actually the HTML5 spec doesn’t take a position on HTML vs XHTML, the WHATWG HTML5 spec extends both at the same time and so leaves the choice of which to use up to the Web author.

You say that XHTML was started and controlled by the W3C group, making sure it gets properly implemented, but in fact XHTML1 was only implemented by Apple, Opera and Mozilla, the same companies that initially started the WHATWG, and XHTML2 was not implemented by anyone, and some of the browser vendors have even said they’ll likely never implement it, so it’s not clear that the W3C actually are making sure it’s getting implemented.

With HTML5, I (as the editor) am talking to the browser vendors on a regular basis to make sure that they will implement it, and am making sure that it isn’t wild and unordered.

We’re also making very sure that HTML5 is just a backwards-compatible extension to HTML, so that browsers don’t have to implement yet another set of standards, as you put it. In fact, we’re defining the legacy HTML in HTML5 in extreme detail so that new browser vendors can write new browsers without having to reverse-engineer the other browsers (in the past, the specs were very incomplete and it was basically impossible to write a new browser without referring to the other ones).

Web Forms 2.0 is a part of HTML5. We actually started HTML5, starting with Web Forms 2, specifically because we didn’t think XForms, XML Events, and XHTML2 were going to be improving the Web.

However, we actually are working with the W3C now. There’s an HTML5 working group in the W3C that is chartered to work with the WHATWG.

If you would like to take part in this work, please do feel free to do so. You need but join the whatwg@whatwg.org mailing list, which you can find at: http://whatwg.org/mailing-list#specs

If you have any feedback and don’t want to join the list you can also just e-mail me directly at: ian@hixie.ch

We do want your feedback!

]]>