[20] WICG (Web Incubator Community Group) は、新技術の仕様書を開発している W3C の CG です。
[21] Webブラウザー業界各社で協力して開発されている仕様書もあれば、 とても実装される見込みが無さそうなものもあり、 玉石混淆状態です。
[1] WICG ( 著, 版) <http://discourse.wicg.io/>
[2] WICG/admin - Gitter ( 版) <https://gitter.im/WICG/admin>
[3] WICG/admin · GitHub ( 版) <https://github.com/WICG/admin>
[4] Web Incubator CG · GitHub ( 版) <https://github.com/WICG>
The Web Incubator Community Group (WICG) provides a lightweight venue for proposing and discussing new web platform features. Each proposal will be discussed in its own repository within the group's Github account. Membership of the group is open to everybody but all participants will have signed the W3C Community Contributor License Agreement.
[6] IRC logs: freenode / #whatwg / 20150724 ( 版) <http://krijnhoetmer.nl/irc-logs/whatwg/20150724>
[7] Web Incubator CG ( 版) <https://github.com/wicg>
But then, we should not use "incubation" as a euphemism for "no one is going to implement this and we don't want it" as it demeans the work of groups like the WIGC - that actually do incubation. At least, I will strongly object to the use of that word if your intention is to kill the spec.
So, what then is the real reason for WP terminating work on the spec? Can we see the minutes from the rationale given to the AC?
At the AC meeting in March 2016 the WP co-chairs indicated that the
following two specifications would benefit from further incubation before
continuing along the Recommendation track:
Quota Management API [1]
Input Method Editor API [2]
This is a proposal and may change without any notices. Interested parties should bring discussions to the Web Platform Incubator Community Group.
This is a proposal and may change without any notices. Interested parties should bring discussions to the Web Platform Incubator Community Group.
This is a proposal and may change without any notices. Interested parties should bring discussions to the Web Platform Incubator Community Group.
This document was moved to the Web Platform Incubator Community Group.
This document was moved to the Web Platform Incubator Community Group.
[15] EventListenerOptions and passive event listeners - move to WICG? - APIs - WICG () <https://discourse.wicg.io/t/eventlisteneroptions-and-passive-event-listeners-move-to-wicg/1386/5>
[16] Tombstone this and point to WICG. (tabatkins著, ) <https://github.com/w3c/css-houdini-drafts/commit/bac793d1eb5690cf41464ff179e613522c13c2df>
[17] Animation Worklet moved to WICG (Rick Byers著, ) <https://lists.w3.org/Archives/Public/public-houdini/2016Sep/0006.html>
It is being incubated here as part of the CSS Houdini task force, and if successful will be transferred to that task force for full standardization.
[19] Google's incubation-first standards process (Rick Byers著, ) <https://lists.w3.org/Archives/Public/www-style/2016Dec/0011.html>
[23] Changed spec headers to match move from WICG to webperf (plehegar著, ) <https://github.com/w3c/server-timing/commit/7f97a2bf259af7a15e737daf724f5fb186de0859>
[24] SVG 2 Status () <http://tavmjong.free.fr/svg2_status.html>