Mark Davis wrote: > here is my suggested language: >| For each collection of records of a particular 'Type' (excluding >| records with a Deprecated field), each of the values that appears >| in a 'Description' field MUST be unique. ACK so far, that just makes sense. It doesn't catch the fine print of a shared namespace for language and extlang (JFTR, I'm not saying that it should) >| The description values MUST also be unique even after removing >| parentheticals [...] I'm not sure about this parenthical bit, see below, [...] >| and inverting any string containing commas. [...] That's again clear, and I like it. [...] >| Outside of parentheticals, commas MUST only be used for inverted >| strings. If you insist on this new comma-rule we're forced to patch several redundant and grandfathered descriptions, as noted before in another article - for the six 1901/1996 cases it would be simple. >| For example, suppose that the following description is in a >| language subtag record: > <pre>Description: Gibrus Xishu</pre> My preferred style would be what we get from the "inverted name" column in the table derived from the 639-3 draft: Xishu, Gibrus How does your parenthical rule handle Ainu (China) vs. Ainu (Japan), or similar Aja (Sudan) vs. Aja (Benin) ? Frank _______________________________________________ Ltru mailing list Ltru at ietf.org https://www1.ietf.org/mailman/listinfo/ltru
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.