- From: Harald Alvestrand <harald@alvestrand.no>
- Date: Thu, 11 Jun 2015 21:40:33 +0200
- To: public-media-capture@w3.org
Den 10. juni 2015 18:17, skrev Martin Thomson: > On 10 June 2015 at 07:54, Cullen Jennings (fluffy) <fluffy@cisco.com> wrote: >> even if no major browser intended to implement them > > That goes to the crux of the matter for me. What constituency does > the W3C serve? > > If we consider the web to be the primary consumer of the work here, I > see little value in having API features defined, but not available to > the web. The typical cycle for new Web features is: - Someone proposes it (enthusiastically) - at least one person/group/company whatever implements it in some fashion (including JS overlays, plugins, demo browsers, whathaveyou) - the implementors and users clamor for inclusion in other platforms - the feature is accepted, withers, or remains a bone of contention Publication (stable reference) needs to happen at the first/second stage. Standardization usually occurs somewhere between the first and last stage, but the place it happens varies a lot from feature to feature. The time from first to last stage can take months, years or decades (SMIL 2 was a standard in 2005; now, 10 years later, it is still chuning through stage 4). > > That said, I think that we could stand to have a lower bar for entry > than what it seems like we currently have. Not that I'd advocate for > a complete abdication of responsibility on our part either, just > stewardship. > Yep, the issues to be addressed include: - What's the bar? - Who administers the bar this week? - Who administers the bar 10 years from now (if we still need it)? - Where do the decisions on what passed the bar get recorded this week? - Where do the decisions get recorded 10 years from now? I think I've said something like this before...
Received on Thursday, 11 June 2015 19:41:09 UTC