BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20230919T113604Z
BEGIN:VTIMEZONE
TZID:Europe/Madrid
BEGIN:STANDARD
DTSTART:20221030T010000
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
END:STANDARD
BEGIN:STANDARD
DTSTART:20231029T010000
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20230326T010000
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:4fd28161-058b-4daa-9618-d1893be9c39c
DTSTAMP:20230919T113604Z
SUMMARY:DOM Localization
DTSTART;TZID=Europe/Madrid:20230913T093000
DTEND;TZID=Europe/Madrid:20230913T103000
DESCRIPTION:https://www.w3.org/events/meetings/4fd28161-058b-4daa-9618-d189
 3be9c39c/\n\nThe base requirements for message formatting and localization
  are experiencing some significant advancements as the [MessageFormat 2 sp
 ec](https://github.com/unicode-org/message-format-wg/tree/main/spec) is be
 ing defined in the Unicode Consortium\, and the [Intl.MessageFormat](https
 ://github.com/tc39/proposal-intl-messageformat) API is being defined in TC
 -39 for JavaScript.\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nBuilding on these\, wor
 k should start on defining a localization system for HTML that's _reactive
 _ rather than _imperative_\, and which allows for localization without any
  JS dependency. At Mozilla\, we've been using a similar system based on [F
 luent](https://projectfluent.org/) to localize Firefox and our other proje
 cts\, and have learned much about what works and what doesn't. Some of our
  ideas have been [collected as a draft](https://nordzilla.github.io/dom-l1
 0n-draft-spec/) of what this could look like in practice.\n\nAgenda\n\n**C
 hairs:**\nEemeli Aro\n\n**Description:**\nThe base requirements for messag
 e formatting and localization are experiencing some significant advancemen
 ts as the [MessageFormat 2 spec](https://github.com/unicode-org/message-fo
 rmat-wg/tree/main/spec) is being defined in the Unicode Consortium\, and t
 he [Intl.MessageFormat](https://github.com/tc39/proposal-intl-messageforma
 t) API is being defined in TC-39 for JavaScript.\n\n\n\n\n\n\n\n\n\n\n\n\n
 \n\n\nBuilding on these\, work should start on defining a localization sys
 tem for HTML that's _reactive_ rather than _imperative_\, and which allows
  for localization without any JS dependency. At Mozilla\, we've been using
  a similar system based on [Fluent](https://projectfluent.org/) to localiz
 e Firefox and our other projects\, and have learned much about what works 
 and what doesn't. Some of our ideas have been [collected as a draft](https
 ://nordzilla.github.io/dom-l10n-draft-spec/) of what this could look like 
 in practice.\n\n**Goal(s):**\n1. Collect comments on the proposal.\n\n\n\n
 2. Recruit interests to work on the standards development.\n\n\n\n3. Discu
 ss the most appropriate forum for further work.\n\n\n**Materials:**\n- [sl
 ides](https://docs.google.com/presentation/d/1cvvNcC2jMKztYKFIAg1Q5JPWrMCd
 0q8Ac2m7P1RYhOc/edit?usp=sharing)\n- [minutes](https://www.w3.org/2023/09/
 13-dom-localization-minutes.html)\n- [Session proposal on GitHub](https://
 github.com/w3c/tpac2023-breakouts/issues/52)
STATUS:CONFIRMED
CREATED:20230905T053959Z
LAST-MODIFIED:20230919T113604Z
SEQUENCE:1
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
LOCATION:Triana - Level -1
CATEGORIES:TPAC 2023,Breakout Sessions
END:VEVENT
END:VCALENDAR