- From: Philippe Le Hegaret <plh@w3.org>
- Date: Fri, 05 Aug 2011 08:50:35 -0400
- To: Arthur Barstow <art.barstow@nokia.com>
- Cc: public-webapps <public-webapps@w3.org>
On Fri, 2011-08-05 at 08:22 -0400, Arthur Barstow wrote: > On 8/4/11 11:47 AM, ext Philippe Le Hegaret wrote: > > Several documents in the WebApps Working Group are linking to HTML, more > > specifically to the WHATWG HTML specification. An example of those is > > Progress Events. This is done for no reason than political as far as I > > can tell. This undermines and is disrespectful the work of the HTML > > Working Group. Unless the WebApps comes up with a set of good reasons of > > why this is done and convince the HTML Working Group, those references > > must be changed in order to publish the documents properly and respect > > the work of the HTML Working Group, > > Philippe, > > Re the specific case of the Progress Events spec - when it was last > published it included non-normative references to both version of HTML: > > http://www.w3.org/TR/progress-events/#references > > May we do that again? (I interpret that to mean the W3C has a fixed > version of HTML and the WHATWG has a tip-of-the-tree version of HTML and > as such, I don't think it 'disses the HTMLWG nor the W3C.) Again, what are the reasons to link to the WHATWG HTML version? What does it mean for the work of the HTML Working Group? There are features in the WHATWG version that got rejected in the HTML Working Group. See http://www.whatwg.org/specs/web-apps/current-work/multipage/introduction.html#how-do-the-whatwg-and-w3c-specifications-differ? This list keeps growing. I don't think it's appropriate for one Working Group to ditch the work of an other. Philippe
Received on Friday, 5 August 2011 12:50:48 UTC