BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20241002T122523Z
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-MICROSOFT-CDO-TZID:13
BEGIN:STANDARD
DTSTART:20231105T090000
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
END:STANDARD
BEGIN:STANDARD
DTSTART:20241103T090000
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20240310T100000
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:49ecab51-dbf7-4351-b2a9-314d169d0b77
DTSTAMP:20241002T122523Z
SUMMARY:Web Features: Building an index for the web platform
DTSTART;TZID=America/Los_Angeles:20240925T100000
DTEND;TZID=America/Los_Angeles:20240925T110000
DESCRIPTION:https://www.w3.org/events/meetings/49ecab51-dbf7-4351-b2a9-314d
 169d0b77/\n\n[Web features](https://github.com/web-platform-dx/web-feature
 s/) is an initiative of the [WebDX Community Group](https://www.w3.org/com
 munity/webdx/)\, to build a list of features on the web platform\, organis
 ed in a way that's useful to developers. It is currently used for providin
 g "baseline" statuses\, indicating feature availability\, to be presented 
 on documentation sites such as [MDN](https://developer.mozilla.org/en-US/d
 ocs/Glossary/Baseline/Compatibility).\n\nSo far the work has mainly been f
 ocused on grouping the already-existing platform APIs into features that c
 an be assigned a baseline status. However the purpose of this session is t
 o understand the opportunities and requirements to use web-features earlie
 r in the proposal lifecycle\, as part of the ongoing standardisation proce
 ss. For example\, in a world where standards-positions and intent emails c
 onsistently use well-defined feature names\, it may be possibly to build t
 ooling that informs developers\, and other interested parties\, about whic
 h proposals are just waiting for implementation\, or where there are more 
 fundamental challenges at the standards level. This data could then be use
 d to inform other projects such as Interop.\n\nAgenda\n\n**Chairs:**\nJame
 s Graham\n\n**Description:**\n[Web features](https://github.com/web-platfo
 rm-dx/web-features/) is an initiative of the [WebDX Community Group](https
 ://www.w3.org/community/webdx/)\, to build a list of features on the web p
 latform\, 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](https://developer.mo
 zilla.org/en-US/docs/Glossary/Baseline/Compatibility).\n\nSo far the work 
 has mainly been focused on grouping the already-existing platform APIs int
 o features that can be assigned a baseline status. However the purpose of 
 this session is to understand the opportunities and requirements to use we
 b-features earlier in the proposal lifecycle\, as part of the ongoing stan
 dardisation process. For example\, in a world where standards-positions an
 d intent emails consistently use well-defined feature names\, it may be po
 ssibly to build tooling that informs developers\, and other interested par
 ties\, about which proposals are just waiting for implementation\, or wher
 e there are more fundamental challenges at the standards level. This data 
 could then be used to inform other projects such as Interop.\n\n**Goal(s):
 **\nUnderstand the requirements / challenges of integrating web-features e
 arly into the standards development process\n\n\n\n**Materials:**\n- [minu
 tes](https://www.w3.org/2024/09/25-webdx-minutes.html)\n- [Session proposa
 l on GitHub](https://github.com/w3c/tpac2024-breakouts/issues/99)\n\n**Tra
 ck(s):**\n- Feature lifecycle
STATUS:CONFIRMED
CREATED:20240916T220403Z
LAST-MODIFIED:20241002T122523Z
SEQUENCE:5
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:-1 Lower Level - Catalina 1
CATEGORIES:TPAC 2024,Breakout Sessions
END:VEVENT
END:VCALENDAR