Difference between revisions of "Headlights2013"

From W3C Wiki
Jump to: navigation, search
(Proposals)
(Proposals)
Line 22: Line 22:
 
==== Payments ====
 
==== Payments ====
  
Led by Dave Raggett <dsr@w3.org>
+
'''Led by Dave Raggett <dsr@w3.org>'''
  
 
Web application developers want to monetise their work, particularly
 
Web application developers want to monetise their work, particularly
Line 36: Line 36:
 
point where we need to revisit the question as a community.
 
point where we need to revisit the question as a community.
  
=== Brand and Communications ====
+
==== HTML5 Performance ====
 +
'''Led by Philippe Le Hégaret <plh@w3.org>'''
 +
 
 +
W3C works on individual components of the web architecture, driven by
 +
the functional needs of our Members. This particular focus may lead us
 +
to miss system-level considerations such as the overall performance of
 +
typical implementations. While performance suffers for a variety of
 +
reasons, web standards could be part of the problem. In the past,
 +
when we looked at performance we instrumented the architecture to
 +
allow performance to be measured. This is quite different from a
 +
system level focus on addressing and improving performance.
 +
 
 +
As we mature to take a platform level view of our work, we should
 +
address performance issues to grow the acceptance of our standards.
 +
 
 +
=== Brand and Communications ===
  
 
=== Productivity ===
 
=== Productivity ===

Revision as of 14:41, 31 January 2013

To bring the Web to its Full potential W3C needs to be constantly thinking about the next major areas of focus. W3C management reviews 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 2013 W3C staff identified some potential directions for W3C. Some relate to the technical agenda, others to organizational development, and others to community-building or business development. In January W3C management launched ten task forces to develop proposals with community participation. This page lists the proposals the task forces are developing according to this calendar:

  • 31 January: Announcement to public and Membership and invitations to participate
  • 19 February: Formal "launch dates" for task forces
  • 20 February - June: Idea Development
  • 9-11 June: Discussion at AC Meeting 2013
  • June - July: Further refinement
  • July: W3M will prioritize mature proposals and (re)allocate resources to pursuing some of them.

Please note that these topics are in development; W3C has not allocated resources to them other than to develop proposals.

See also Headlights2012.

Proposals

Open Web Platform

Payments

Led by Dave Raggett <dsr@w3.org>

Web application developers want to monetise their work, particularly on mobile where ads are not as effective as on desktop. The Open Web Platform does not yet offer standard ways to transfer money, demonstrate proof-of-purchase, and meet other payment needs. Without a standard, developers are forced to turn to native platforms, or use solutions that work for one service provide but not another.

There was a headlights project on this last year, as well as a Community Group looking at a particular approach. The staff believes that the platform and industry have evolved in the past year to the point where we need to revisit the question as a community.

HTML5 Performance

Led by Philippe Le Hégaret <plh@w3.org>

W3C works on individual components of the web architecture, driven by the functional needs of our Members. This particular focus may lead us to miss system-level considerations such as the overall performance of typical implementations. While performance suffers for a variety of reasons, web standards could be part of the problem. In the past, when we looked at performance we instrumented the architecture to allow performance to be measured. This is quite different from a system level focus on addressing and improving performance.

As we mature to take a platform level view of our work, we should address performance issues to grow the acceptance of our standards.

Brand and Communications

Productivity