W3C management reviews W3C priorities and resources on an ongoing basis, and annually (typically mid-year) explores major re-allocations of resources to align with important trends. In early 2014 W3C staff identified some potential directions for W3C (technical, organizational, etc.). We have launched six task forces to develop proposals with community participation.
If you are interested in participating in a task force, please contact the lead(s). Note that these topics are in development; W3C has not allocated resources to them other than to develop proposals.
See also Headlights2013.
- October 2013 - January 2014: Proposals from W3C Members and Staff added to this page
- Jan 2014: W3C management prioritization of headlights ideas
- Feb 2014: Announcement of topics selected for further development and start of task forces
- 7 March: People are encouraged to join the task forces by this date.
- 10 March - June: Task forces develop ideas
- 8-10 June 2014: AC meeting discussion
- June-July 2014: Further development
- July 2014: W3M evaluation of proposals and assignment of resources
Led by: Jeff Jaffe <email@example.com>
It was proposed during TPAC 2013 that we should have an Individual Membership program at W3C. W3C management concluded that we did not need a program which conferred the participation rights of Membership to individuals, since we already have Invited Experts.
Instead, we are looking to explore a "Webizen" program. For a nominal fee (e.g. $100 US per annum), the individual would get some benefits. This project will explore whether such a program is viable and what the benefits should be.
Sample benefits could include: user groups, user conferences, T-shirts, ID-cards, a path to provide user input to Working Groups, recognition as a Webizen for participants in W3C Working Groups and Community Groups.
W3C Community On-Boarding
Led by: Dominique Hazaël-Massieux <firstname.lastname@example.org>
As the scope of Web technologies increases, and as the communities impacted by the Web grows, it becomes critical that a wider variety of people can come on board of the W3C train and become effective participants in W3C groups. This headlight will explore the various existing and new approaches that would let W3C newcomers get integrated in our community better and faster.
Security and Privacy Internal Consulting
Led by: Wendy Seltzer <email@example.com>
To improve the quality of of W3C recommendations with regards to privacy and security, we want to provide internal consultation on security and privacy issues at the request of a Working Group. The aim is to help WGs throughout all phases of their work to identify, discuss and resolve specific privacy and security questions. Along with review of finalized specs, this service will focus on collaborative work earlier in the WG's progress.
Easy Access to W3C Specifications
Led by: Xiaoqian (Cindy) Wu <firstname.lastname@example.org>
Many developers have strong willingness to understand W3C's standards, to comment on the drafts or participant in our other activities, but quite a few of them might give up at the very beginning because the specs are not easy to read. To make it easier for the developers to get access to our specs, we hope to invite editors or other experts in each working group to write articles about how to read the specs, and to translate these articles into other languages if necessary. Through these introductions, more developers will feel welcome to get involved in the process, which will help increase the consistency of our specifications, and allow us to develop new technologies for more people.
Led by: Alan Bird <email@example.com>
The project goal is to identify data we have available and to determine how we may analyze it to better serve our Members and other parts of community.
This project will be primarily internal to the W3C Team. Please contact Alan with any questions.
Led by: Yves Lafon <firstname.lastname@example.org>
IETF is currently working on an improved version of HTTP called HTTP2, while keeping the same semantic as the original HTTP/1.1 specification (also reworked lately), it provides, on top of performance improvements, new features that may have impact on other specifications and have security implication. We need to explore further those potential impacts: What aspects of the Web architecture need refinement to leverage HTTP2? How its security features impact the Web layer?
To join: Contact Yves Lafon; discussion will take place on www-tag (the TAG's public mailing list).