Web features, Baseline status, and standardization signals

• Past
• Confirmed
• Breakout Sessions

How do web developers talk about web features? What names do they use? How do these features map to specifications, fine-grained API functions and tests? What does a developer view tell us about the interoperability of the web platform?

The web-features project, envisioned in 2022 and launched in 2023, explores the set of interoperable features of the web platform by:

• Creating feature definitions, which identify and describe capabilities of web browsers.
• Generating Baseline support data, which summarizes the availability of web features across key browsers and releases.
• Publishing the web-features npm package, which bundles feature identifiers with Baseline statuses.

Developed by the WebDX Community Group and contributors, web-features data leverages compatibility data from the browser-compat-data project, is already integrated in MDN, Can I Use, Web Platform Tests, and is starting to reach additional authors of JavaScript libraries and dashboards.

Looking forward, feature identifiers at the "right" level make it possible to tag signals from the web community in surveys, browser standard positions, bug trackers, polyfills and usage counters. It also makes it easier to combine these signals with other projects that generate data out of specifications such as browser-specs and webref.

Features are also used in standardization groups, informally to organize discussions, but also formally to address transition requirements set forth by the W3C Process Document for advancing specifications on the Recommendation track. Within the Process, new features are defined as substantive changes that add new functionality, and used to assess implementation experience, document functionality that is considered at risk, and scope changes that may be incorporated in a specification depending on its maturity stage. This raises questions on the intersection between web-features and W3C’s standardization process, including:

• Can web-features provide useful information to working groups?
• Can it also inform the standardization process, e.g., to detect the need to transition a feature implemented by more than one browser out of incubation?
• What additional data or tooling would make web-features a powerful tool for standards bodies?
• How would you like to see web-features data presented in standards work?

Agenda

Chairs:
François Daoust, Patrick Brosset, Kadir Topal

Description:
How do web developers talk about web features? What names do they use? How do these features map to specifications, fine-grained API functions and tests? What does a developer view tell us about the interoperability of the web platform?

The web-features project, envisioned in 2022 and launched in 2023, explores the set of interoperable features of the web platform by:

• Creating feature definitions, which identify and describe capabilities of web browsers.
• Generating Baseline support data, which summarizes the availability of web features across key browsers and releases.
• Publishing the web-features npm package, which bundles feature identifiers with Baseline statuses.

Developed by the WebDX Community Group and contributors, web-features data leverages compatibility data from the browser-compat-data project, is already integrated in MDN, Can I Use, Web Platform Tests, and is starting to reach additional authors of JavaScript libraries and dashboards.

Looking forward, feature identifiers at the "right" level make it possible to tag signals from the web community in surveys, browser standard positions, bug trackers, polyfills and usage counters. It also makes it easier to combine these signals with other projects that generate data out of specifications such as browser-specs and webref.

Features are also used in standardization groups, informally to organize discussions, but also formally to address transition requirements set forth by the W3C Process Document for advancing specifications on the Recommendation track. Within the Process, new features are defined as substantive changes that add new functionality, and used to assess implementation experience, document functionality that is considered at risk, and scope changes that may be incorporated in a specification depending on its maturity stage. This raises questions on the intersection between web-features and W3C’s standardization process, including:

• Can web-features provide useful information to working groups?
• Can it also inform the standardization process, e.g., to detect the need to transition a feature implemented by more than one browser out of incubation?
• What additional data or tooling would make web-features a powerful tool for standards bodies?
• How would you like to see web-features data presented in standards work?

Goal(s):
Share updates on the web-features project, its use to inform the standardization process, and additional data, tooling and visualizations to make web-features a powerful tool for standards bodies.

Agenda:

• Presentation (20mn - see slides)
  • Web developers and web features
  • Web features and standardization
  • First stab at gathering signals to inform standardization process
    • Late incubations
    • Late Working Drafts
    • Not-so-well supported Recommendations
• Discussion (30mn)

Materials:

• minutes
• Session proposal on GitHub

Minutes

 Read minutes

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.

• Download as ics