I can't help feeling that a lot of people are missing the point here. It really isn't anything to do with us developers whether to use XHTML2 or HTML5 - that will be governed by which specifications are supported by IE and Safari in the future. It may be that they disagree, and then we will be stuck on HTML4 for ever and ever!
As with XHTML1.1 there is no point in producing stuff, no matter how 'well formed' if nothing can read it. Mike > -----Original Message----- > From: [email protected] > [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Ingram > Sent: Friday, February 16, 2007 4:44 PM > To: [email protected] > Subject: Re: [WSG] Living With Legacy > There seems to be a lot of > argument about how > the two will be going head-to-head and only one will win, I > think this > is the wrong approach. I think it'll be more like having a choice of > programming languages, there's a range of choices but you > pick the one > most suited to the job. I agree with your assessment that > this applies > to current HTML/XHTML too. > > What I normally do is develop in XHTML so that I benefit from > the much > stricter validation, then I switch to HTML at the end. > Probably a weird > approach but I agree with the opinion that XHTML should be > served with > the correct MIME type or not at all. > > > - Andrew Ingram > > > ******************************************************************* > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [EMAIL PROTECTED] > ******************************************************************* > > ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
