Justin Grant

> At a minimum, it seems like there should be stable BCP47 IDs for all non-canonical IANA zones, and that ICU4X should not canonicalize by default. So users would have...

I also agree with @robertbastian in much of above, although there may be a few areas where we haven't yet reached agreement. I'll try to enumerate the parts where I...

> > Mitigate the risk by removing canonicalization behavior from APIs, so that ECMAScript will never replace user-inputted IDs with a canonical ID. If a user provides Europe/Kiev or Europe/Kyiv...

A few questions and feedback about the proposed API: ### General questions: Is there a different type that will provide an enumeration of all IANA IDs (both canonical and non-canonical)?...

> The proposed `.parse_normalize()` function returns the two things an ECMAScript implementations needs: a `TimeZone` for formatting, based on the CLDR equivalence class, and a `&'data str`, an interned, normalized...

FYI, @sffc @robertbastian and I had an impromptu chat last week about the questions above and I think we made good progress. Do you guys want to post a summary?...

> IanaParserExtended also has two functions returning iterators, both returning an iterator of data strings: > * iter_all() > * iter_canonical() Should we also have an iterator for "struct containing...

> We could potentially change `iter_all()` to iterate over the 3-tuples. This seems like a good idea. Having all three fields unlocks more use cases, and converting from the 3-typles...

Here's a Temporal-only solution. Was this what you're looking for? ```js Temporal.Instant.from('2024-05-16T01:30:00.000Z') .toZonedDateTimeISO(Temporal.Now.timeZoneId()) .toPlainDate(); // => 2024-05-15 ```

For anyone reading this issue in the future wondering why there's an `ISO` suffix on the `toZonedDateTimeISO` and `plainDateISO` functions above, it's referring to the ISO 8601 calendar (or "ISO...