BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20260316T160242Z
BEGIN:VTIMEZONE
TZID:Etc/UTC
BEGIN:STANDARD
DTSTART:20230318T140000
TZOFFSETFROM:+0000
TZOFFSETTO:+0000
TZNAME:UTC
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
UID:9e7690a7-cd77-4192-ab60-337243f9b70a
DTSTAMP:20260316T160242Z
SUMMARY:Web features\, Baseline status\, and standardization signals
DTSTART;TZID=Etc/UTC:20240312T140000
DTEND;TZID=Etc/UTC:20240312T150000
DESCRIPTION:https://www.w3.org/events/meetings/9e7690a7-cd77-4192-ab60-3372
 43f9b70a/\n\nHow do web developers talk about web features? What names do 
 they use? How do these features map to specifications\, fine-grained API f
 unctions and tests? What does a developer view tell us about the interoper
 ability of the web platform?\n\nThe [`web-features` project](https://githu
 b.com/web-platform-dx/web-features)\, [envisioned in 2022](https://www.w3.
 org/2022/09/TPAC/breakouts.html#webdx) and [launched in 2023](https://www.
 w3.org/2023/09/TPAC/demos/web-features.html)\, explores the set of interop
 erable features of the web platform by:\n\n- Creating feature definitions\
 , which identify and describe capabilities of web browsers.\n- Generating 
 [Baseline](https://github.com/web-platform-dx/web-features/blob/main/docs/
 baseline.md) support data\, which summarizes the availability of web featu
 res across key browsers and releases.\n- Publishing the `web-features` npm
  package\, which bundles feature identifiers with Baseline statuses.\n\nDe
 veloped by the WebDX Community Group and contributors\, web-features data 
 leverages compatibility data from the browser-compat-data project\, is alr
 eady [integrated in MDN](https://developer.mozilla.org/en-US/blog/baseline
 -evolution-on-mdn/)\, [Can I Use](https://caniuse.com/css-nesting)\, [Web 
 Platform Tests](https://github.com/web-platform-tests/wpt.fyi/blob/main/ap
 i/query/README.md#feature)\, and is starting to reach additional authors o
 f JavaScript libraries and dashboards.\n\nLooking forward\, feature identi
 fiers at the "right" level make it possible to tag signals from the web co
 mmunity 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`](https://github.com/w3c/browser-specs/) and [webref](https://githu
 b.com/w3c/webref).\n\nFeatures are also used in standardization groups\, i
 nformally to organize discussions\, but also formally to address transitio
 n requirements set forth by the W3C Process Document for advancing specifi
 cations on the Recommendation track. Within the Process\, [new features](h
 ttps://www.w3.org/2023/Process-20231103/#class-4) are defined as substanti
 ve changes that add new functionality\, and used to assess [implementation
  experience](https://www.w3.org/2023/Process-20231103/#implementation-expe
 rience)\, document functionality that is considered [at risk](https://www.
 w3.org/2023/Process-20231103/#at-risk)\, and scope changes that may be inc
 orporated in a specification depending on its maturity stage. This raises 
 questions on the intersection between web-features and W3C’s standardiza
 tion process\, including:\n\n- Can web-features provide useful information
  to working groups?\n- Can it also inform the standardization process\, e.
 g.\, to detect the need to transition a feature implemented by more than o
 ne browser out of incubation?\n- What additional data or tooling would mak
 e web-features a powerful tool for standards bodies?\n- How would **you** 
 like to see web-features data presented in standards work?\n\n**Goal(s):**
 \nShare updates on the web-features project\, its use to inform the standa
 rdization process\, and additional data\, tooling and visualizations to ma
 ke web-features a powerful tool for standards bodies.\n\nAgenda\n\n- Prese
 ntation (20mn - see [slides](https://docs.google.com/presentation/d/e/2PAC
 X-1vT5PiEfUCia_p-hIKu-LxQ90qwQks42FtsXTxI4wATYuG1OWEQlCnGcP7R_gENVnGUa82ZT
 GkQXQgRQ/pub))\n  - Web developers and web features\n  - Web features and 
 standardization\n  - First stab at gathering signals to inform standardiza
 tion process\n    - Late incubations\n    - Late Working Drafts\n    - Not
 -so-well supported Recommendations\n- Discussion (30mn)\n\n**Materials:**\
 n- [Session proposal on GitHub](https://github.com/w3c/breakouts-day-2024/
 issues/22)
STATUS:CONFIRMED
CREATED:20240302T115628Z
LAST-MODIFIED:20260316T160242Z
SEQUENCE:4
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Koto
CATEGORIES:W3C Breakouts Day 2024,Breakout Sessions
END:VEVENT
END:VCALENDAR