[20] WICG (Web Incubator Community Group) は、新技術の仕様書を開発している W3C の CG です。

[21] Webブラウザー業界各社で協力して開発されている仕様書もあれば、 とても実装される見込みが無さそうなものもあり、 玉石混淆状態です。

成功事例

[22] WHATWG の仕様書に取り込まれたもの

歴史

[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

[5] Web Incubator Community Group ( 版) https://wicg.github.io/admin/charter.html

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

[8] Re: CFC ( (marcos@marcosc.com著, )) https://lists.w3.org/Archives/Public/public-webapps/2016AprJun/0088.html

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?

[9] CFC: Publish as W3C Notes ( (Léonie Watson著, )) https://lists.w3.org/Archives/Public/public-webapps/2016AprJun/0069.html

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]

[10] Network Error Logging ( ()) https://www.w3.org/TR/2016/NOTE-network-error-logging-20160524/

This is a proposal and may change without any notices. Interested parties should bring discussions to the Web Platform Incubator Community Group.

[11] Server Timing ( ()) https://www.w3.org/TR/2016/NOTE-server-timing-20160523/

This is a proposal and may change without any notices. Interested parties should bring discussions to the Web Platform Incubator Community Group.

[12] Reporting API 1 ( ()) https://www.w3.org/TR/2016/NOTE-reporting-1-20160607/

This is a proposal and may change without any notices. Interested parties should bring discussions to the Web Platform Incubator Community Group.

[13] Frame Timing () https://www.w3.org/TR/2016/NOTE-frame-timing-20160720/

This document was moved to the Web Platform Incubator Community Group.

[14] Network Error Logging () https://www.w3.org/TR/2016/NOTE-network-error-logging-20160720/

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

[18] WICG/animation-worklet: Proposal for a new primitive for creating scroll-linked and other high performance procedural animations on the web. () https://github.com/WICG/animation-worklet

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