That aside, the debate format makes it great fun for the audience, as well as the participants.

Sounds like it would make a good discussion panel

Following this years Web Directions North conference held in Vancouver, BC some of the main points of discussion involved html vs. xhtml and many users/developers said that they were trying to avoid xhtml as a dead horse. As for standards being incorporated across the board, it is nice to see all applications trying to resolve differences between browser types and MS did try and tell us that their new browser IE Whatever would be css capable...fully The fact that this issue was raised repeatedly by industry heavyweights and W3C & World Standards Group members (Molly Holzshlag, Andy Clarke and Dave Shea) with MS reps sort of set the tone for css being accepted fully by all in attendance. I would be hard pressed to not see css being fully integrated with special style sheets for 3 or 4 different types of display media being developed by developers in the future. That way folks using screen readers, users with handheld appliances and those using either regular or wide screen monitors will all be looked after. Sure it makes more work for the developers/designers in the long run...but having everyone being able to see your site via all the different media types will be an absolute bonus for our customers or employers.

While we're at it, how about talking about what percentage of browsers is a good breakoff point for no support...for instance, if less than 1% of browsers hitting my site are Mac XYZ or IE 5.5, should I worry about supporting them? How does one set the limit? 90% of the work for 10% of the users?

I am looking forward to hearing differing opinions on when and why hacking is O.K., and when and why CSS "needs" to validate. Getting differing opinions on "Is avoiding the occasional non-validating hack worth the extra HTTP request of pulling in an extra style sheet?" would be interesting.