Addison Phillips

In the 2024-07-15 call we agreed to default to medium. Removing agenda+. Adding action-item for @eemeli to update the PR

The use of XMLSchema was semi-arbitrary on my part. We could use [RFC3339](https://www.rfc-editor.org/rfc/rfc3339.html#section-5.6) instead. The definitions there might be `date-time` and `full-date`. We might make `full-time` and `partial-time` optional (as...

Yes, the variability sucks. I disagree with just saying "ISO 8601" (which is far more expansive than just date/time values). And I disagree with being "permissive". We want messages to...

Fair enough. That works for me, although I'm leery of the "my message worked in X but not on Y" problem.

Keeping this issue alive for further discussion of date/time/datetime literals.

Moving to v48 because this function is draft in 47

If something is done here, it should draw on I18N support and that should be consistent with at least Intl.DateTimeFormat (and its options). These will also be the options used...

@sffc Thanks for the update. Please note that the document you linked is a design document. There is specification text in the `registry.md` document that also uses these various options....

> Please note with semantic skeleta that not all field sets are well-defined. If you request a field set [year, hour], that is considered a syntax error. Is "well-defined" a...

I am tagging this as "Future" because it will not meet the cutoff for LDML46. It will still be considered prior to exiting Tech Preview, which is expected in the...