HTML

HTML

1. HTML5 is done
2. HTML WG focusing on:
   • Media Extensions: MSE, EME, (transcript)
   • Canvas accessibility: Hit regions
   • Getting DOM to REC: last interop issues
   • Core part of HTML isn't getting the needed attention:
     No wide review

What's up with HTML?

1. We need proper maintenance of HTML, in a functional Group
2. Web Components is happening in Web Applications Working Group
3. Community has some ideas (app oriented markup, transcripts, etc.)
4. Implementors aren't eager to develop new features
5. Working Group Charter runs out on June 30, and letting it lapse has some issues (media task force)

Gathering feedback

1. Robin Berjon proposed an HTML Plan to the AB and the WG
2. Met with browser vendors
3. Talked with several AC representatives
4. Discussions with HTML Chairs
5. No consensus or clear proposal yet

Challenges of Standardization

1. Incubating new ideas
2. Efficient standards work
3. Interoperability and W3C Standard
4. Maintenance (aka actual interoperability)

Incubating new ideas:
Web Platform Incubator

1. Facilitate submitting ideas to the community with inviting place, open, and no early process burden
2. CG operating with consensus to help future standardization
3. Let the idea come: github repositories
4. Track contributions through better tooling
5. Doesn't preclude other Groups to get ideas

From an idea to a Standard

• Once an idea is mature, it needs to move to the WG
• CG and WG Leadership, with W3C Team, to manage transitions
• Request to Transition templates
• Ensure continuity in participation between the CG and the WG

WG: Data-driven and priority-focus

1. Use data: usage, metrics, implementation status, tests
2. Strong leadership to avoid derailments
3. Refocus the participation in the Working Group

WG: Interoperability

1. Use development and stable branches to encourage convergence while evolving the platform
2. Demonstrate interoperability to move to W3C Recommendation
3. But also make judgement call based on implementation status and real world usage

WG: Maintenance

1. Achieve actual long term interoperability
2. Specs and vendors issues should be triaged and prioritized
3. Again, use real world data-driven usage for prioritarization

Organization

1. Licensing: W3C Software and Document license
2. Regular activity summaries to keep track
3. Need agreement on structure before answering leadership
4. Use Modern tooling

Browser vendors

Quarterly meetings with consumer browser engines:

• Why? Gather feedback on implementation priorities and W3C Group priorities
• Who? Those with authority over what gets committed to a consumer browser engine codebase
• How? Public communication: Scheduling, Agenda, Summaries

What's next?

• CG: can be launched in the upcoming weeks
  1. Refine Web Platform Incubator CG, including work mode
  2. Leadership and Team
• WG: will need a transition period
  1. Scope of the Working Group(s)?
  2. Work mode
  3. Leadership

… while getting wider review from AC and Community on the HTML plan

Questions?

• Is there enough HTML Innovation vs Maintenance out there?
• What Working Group: Separation between WebApps and HTML is artificial
  see also Application Foundations and Group boundaries
• Implementors: Will they come?
• Leadership?