Chris Wilson schreef: > All, > I need to detail an essay about compatibility and opt-in to explain the Microsoft viewpoint on this. I have a few things on my plate I must do today, so it will probably take a day or two. I'm going to likely be silent until then on this topic. I wonder how much merit it has to discuss/decide this now; isn’t the necessity of this depending on the output of this working group and the opinion of implementors on the feasibility to implement it without breaking current pages? Assuming on beforehand the spec will never be able to define HTML5 in a way that doesn’t break existing pages is I think premature. We should try our best to achieve this, and if in the end that turns out to be impossible, then we can introduce a version number after all. You mentioned HTML6; if HTML6 is not interoperable without breaking backwards compatibility, a version switch can be added in HTML6. Saying that HTML5 won’t have versioning information does I think not prevent future specifications from not having any. Plus that I (as stated earlier) don’t think that per-specification-versioning is very useful, what you would really need is per-user-agent versioning. ~Grauw -- Ushiko-san! Kimi wa doushite, Ushiko-san nan da!! ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Laurens Holst, student, university of Utrecht, the Netherlands. Website: www.grauw.nl. Backbase employee; www.backbase.com.
Received on Thursday, 12 April 2007 07:08:31 UTC