- From: Dominique Hazael-Massieux <dom@w3.org>
- Date: Thu, 22 Mar 2012 14:48:49 +0100
- To: Marcos Caceres <w3c@marcosc.com>
- Cc: Jeff Jaffe <jeff@w3.org>, Anne van Kesteren <annevk@opera.com>, public-w3process <public-w3process@w3.org>, Daniel Glazman <daniel.glazman@disruptive-innovations.com>
Le jeudi 22 mars 2012 à 13:40 +0000, Marcos Caceres a écrit : > > Modularization for the sake of it is make work; modularization built > > around fast tracking features that are already deployed and > > interoperable seems to be a good investment (even if costly). > > We would need to ask Hixie how long it took him to write the script > that breaks the WHATWG spec up into the little specs (and cost of > maintenance of that code). That would give us a real cost estimate. Actually, I think any cost estimate we would get would be entirely dwarfed by the estimates we would get by asking microsoft, google, and apple about the cost they would associate with getting sued over a feature they're deploying in their browsers today. And I don't need to mention all the services and content providers that rely on these features to get their business done today. So I don't really think we need that particular data to determine that this would be a very good ROI. As I have mentioned, if we were to take that approach, I think we should find resources other than the lead editor to do the bulk of the work (even if it involves semi-manual work), since the lead editor is such a precious resource. > > I started to look into this the other day, and can share the CSV data > > that I extracted in that early work; but I stopped when it was obvious > > that I didn't have a specific theory to test for the existing data set, > > or not the right data for the theories I wanted to test. > > > > My theory is: specs that stick close to implementation deployment can > > fly through the Rec track. But I don't think that anyone has been > > tracking that particular characteristic. > > I think any start on this would be good. Even if it's a simple > question… how long does it take to go from A to B? Then we can look > more closely at the data. So wish I could find a little time to go > into this… it's super interesting. I'll try to finish the work I started there; but I don't think rough data will give us much clue here. Dom
Received on Thursday, 22 March 2012 13:49:17 UTC