Revision as of 19:36, 14 February 2014

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. W3C Members and W3C Staff use this wiki to identify some potential directions for W3C (technical, organizational, etc.).

These are proposals for discussion. Do not assume that W3C endorses these ideas or has allocated any resources to pursuing them beyond initial discussion.

Contents

Schedule

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

Feb - May 2014: Idea Development

June 2014: AC meeting discussion

June-July 2014: further development

July 2014: W3M evaluation of proposals and assignment of resources

Projects

Webizen Program

Led by: Jeff Jaffe

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 of
comparable value. This project will explore whether such a program is
viable and want 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.

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

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

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 groups to write articles about how to read the specs, and
to translate these articles into other languages if necessary. By
these kind of introduction, more developers will get involved in the
process, which will help increase the consistency of our
specification, and allow us to develop new technologies for more
people.

Data-backed Operations

Led by: Alan Bird

This project will be primarily internal to the W3C Team. The project
goal is to identify data we have available and and to determine how we
ma analyze it to better serve our Members and other parts of
community.

Please contact Alan Bird <abird@w3.org> with any questions.

HTTP2

The IETF is defining HTTP2. Proponents point out that the improved
architecture will have far greater performance, and we can build
stronger security requirements into it. We need to explore further the
impact: What aspects of Web architecture need to be made more
efficient to leverage HTTP2? How do we build security into the Web
layer? What new applications will be developed?