Eemeli Aro

Updated to match corresponding changes made to PR #195.

My suspicion is that the exact shape of the output should be an implementation question, rather than one answered by the MF2 spec. For instance, the current JS Intl.MessageFormat proposal...

@romulocintra As I mentioned at today's meeting, would it be possible to get a slot at the next plenary to present my [XLIFF 2 module strawman proposal](https://docs.google.com/document/d/1D702OBAzT-Crb9XXUiZYJnFO9Yq5duRy4Zc3Br6JwRU/edit?usp=sharing)?

I've recently added a couple of features to the `mf2` branch that might be of interest: ### Automatic grammatical case/gender/plural detection & reporting If the key values of a selector...

To clarify the terms: - By "interface provided by the data model" I mean the representation provided directly by the data model. For example, it's what a MF1 -> MF2...

While we do need to determine the soundness/completeness/simplicity of the data model, we need to _first_ determine whether that ought to be directly linked with the interface that translators will...

> > 1. Tool X fails, because the data model cannot represent the message. > > 2. Tool Y fails, because the XLIFF 2 representation does not support this data...

A set of slides summarising the full document is now also available: https://docs.google.com/presentation/d/1QOJidlaymR5xqdimMjEqE-GJeoHwNJ2CZG5CfTygwBI/edit?usp=sharing

Would it be appropriate to ask remit from the CLDR-TC to start a separate subgroup to discuss the resource syntax?

> So again: what kind of format you envision that is not already expressible in the existing formats? One important aspect that is not currently expressible in existing resource formats...