Addison Phillips

I agree with adding "left behind" options. We should test drive the process described in #634 to do this. Currency (and unit) is tricky. I tend to agree that not...

> Could you share some example message in some locale that varies based on the plural category of a currency or unit value? It is admittedly the case that unit...

I think the #634 process should be our next stop. Specifically missing from #634 at the moment is a template for "registry entries". We can use the held-back options from...

TLDR: I think we should create `:currency` and `:unit` (or `:measure`, we can bikeshed this later) in the RGI registry and we should encourage good I18N hygiene by not providing...

@macchiati I'm not saying that we should avoid doing the right thing. I'm saying we should provide ways for different users to accomplish the right thing. For example, I was...

Waiting to merge #922, which will close this issue.

Normalization can be tricky here. I think we want to avoid requiring that a _message_ be in a specific normalization form. That would prevent patterns from using a denormalized sequence....

Names and namespaces, yes. Literals we might need to put SHOULD on. The only place where literal matching takes place in our syntax is between `keys` and selectors, where we...

> I think a message with two selection keys that are canonical equivalents would be a serious mistake, and also break interoperability. Totally--a mistake on the part of the message...

We have to be careful about identity here. Two keys can evaluate to the "same value" for a given selector, even without string normalization. I agree that it would be...