Comments follow. Mostly I think I've fixed this in draft-02. Mark Davis wrote:
I agree that the language needs a bit of cleanup, but not quite what you suggestion.
I agree. "Well-formed" and "valid" have quite specific meaning. "Irregular" has the meaning Mark suggests.
The draft seems inconsistent in its use of "well-formed" and "regular". We find: > grandfathered = langtag ; well-formed grandfathered tags > / irregular ; tags that are not well-formed (I would say that irregular is the opposite of regular, not of well-formed.)
Irregular grandfathered tags are well-formed by definition. They are irregular in terms of the langtag production. Changed the note to say:
'grandfathered tags that don't match langtag'
> Some grandfathered tags are "well-formed" in that they match the > 'langtag' production in Figure 1. And, a few lines later: > An implementation that claims to check for well-formed language tags > MUST: > > o Check that the tag and all of its subtags, including extension and > private use subtags, conform to the ABNF or that the tag is on the > list of grandfathered tags.
Fixed. 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.