Mark Davis wrote:
I'm ok with the direction. I think it needs a bit more qualification, so I suggest the text below.
Additional edits were needed, notably for the "For a records" typo. I ended up with:
--<t>For each collection of records of a particular 'Type', each of the values that appears in a 'Description' field MUST be unique. For records taken from a source standard (such as ISO 639 or ISO 3166), the 'Description' value(s) SHOULD be taken from the source standard. Multiple descriptions in the source standard MUST be split into separate 'Description' fields. The source standard's descriptions MAY also be edited prior to insertion. Duplicate, redundant, conflicting, or otherwise problematic descriptions MUST either be corrected or omitted. Parenthetical comments, inverted names, and other formatting quirks SHOULD be regularized according to the guidelines used to update the registry in <xref target="registry-update"></xref>.</t>
-- Addison -- Addison Phillips Globalization Architect -- Yahoo! Inc. Internationalization is an architecture. It is not a feature. _______________________________________________ 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.