Shane F. Carr

> we've already had Metazone vs MetaZone Metazone wasn't a casing decision; we actually decided that "metazone" was one word. You might be thinking of "time zone", where we decided...

I talked this over with @echeran and @kartva today. I presented the following question: We have a type `icu::datetime::Formatter`. When `Foo` is a field set, what should it be in...

On the trait naming: the other example I almost forgot to mention but which we've definitely hit problems is in the data provider constellation. `BufferProvider` is a trait but `BlobDataProvider`...

So much activity! Thank you! Responding in chronological order > > For clients, the field set markers are the most important and unique part of the new API. The rest...

Exploration on ultra-abbreviated, based on the set of fields in the current spec draft: We are limited to the 26 letters. We could potentially use lowercase letters as modifiers on...

One _potential_ concern with `YMD` is that it might more strongly signify that there is an order involved, since I've seen UIs that have enumerations allowing you to select "YMD,...

Proposal: - Move forward with the field abbreviations proposed in the comment, like `YMD` and `HMS` - Put them in the namespace `icu::datetime::fieldsets` - A macro could be added later,...

We have alignment on the datetime field set type names. I'm leaving the issue open because there were other things in the OP which we don't have alignment on, yet.

Fieldsets are tracked in #1317 and #4991 tracks the data markers

The closest way to model the calendar like the other preferences would be to add a new data marker called something like `CalendarPreferenceV1`, which contains a single string equal to...