Information

Web Features: Building an index for the web platform
  • Past
  • Confirmed
  • Breakout Sessions

Meeting

Event details

Date:
Pacific Daylight Time
Status:
Confirmed
Location:
-1 Lower Level - Catalina 1
Participants:
Rachel Andrew, Panos Astithas, Tab Atkins Jr., Kevin Babbitt, Christos Bacharakis, Daniel Beck, Tantek Çelik, Ioana Chiorean, Yehonatan Daniv, Guohui Deng, Marie-Claire Forgue, James Graham, Dave Hunt, Pete LePage, Sandor Major, Romain Menke, Niklas Merz, John Riviello, Florian Scholz, Miriam Suzanne, Kadir Topal, Munira Tursunova
Big meeting:
TPAC 2024 (Calendar)

Web features is an initiative of the WebDX Community Group, to build a list of features on the web platform, organised in a way that's useful to developers. It is currently used for providing "baseline" statuses, indicating feature availability, to be presented on documentation sites such as MDN.

So far the work has mainly been focused on grouping the already-existing platform APIs into features that can be assigned a baseline status. However the purpose of this session is to understand the opportunities and requirements to use web-features earlier in the proposal lifecycle, as part of the ongoing standardisation process. For example, in a world where standards-positions and intent emails consistently use well-defined feature names, it may be possibly to build tooling that informs developers, and other interested parties, about which proposals are just waiting for implementation, or where there are more fundamental challenges at the standards level. This data could then be used to inform other projects such as Interop.

Agenda

Chairs:
James Graham

Description:
Web features is an initiative of the WebDX Community Group, to build a list of features on the web platform, organised in a way that's useful to developers. It is currently used for providing "baseline" statuses, indicating feature availability, to be presented on documentation sites such as MDN.

So far the work has mainly been focused on grouping the already-existing platform APIs into features that can be assigned a baseline status. However the purpose of this session is to understand the opportunities and requirements to use web-features earlier in the proposal lifecycle, as part of the ongoing standardisation process. For example, in a world where standards-positions and intent emails consistently use well-defined feature names, it may be possibly to build tooling that informs developers, and other interested parties, about which proposals are just waiting for implementation, or where there are more fundamental challenges at the standards level. This data could then be used to inform other projects such as Interop.

Goal(s):
Understand the requirements / challenges of integrating web-features early into the standards development process

Materials:

Track(s):

  • Feature lifecycle

Export options

Personal Links

Please log in to export this event with all the information you have access to.

Public Links

The following links do not contain any sensitive information and can be shared publicly.

Feedback

Report feedback and issues on GitHub.