[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ltru] extlang & deprecation (was draft updated



> From: Phillips, Addison [mailto:addison at amazon.com]

> > A possible concern is that "Preferred-Value" is not only used in
> > canonicalization *for matching purposes*, but it is also what
> > people SHOULD be using to tag all their content and interchange: as
> > the opening sentence of 4.5 says,
>
> I agree that this applies. But I think it is important that we
> establish a general trend in tag choice. Multiple choices in language
> tags are bad news.

OK, so you're saying we need to move the trend in tag choice either toward everyone tagging things as "zh-cmn"/"zh-yue"/etc., or toward everyone tagging things as "cmn"/"yue"/etc. We've got different opinions on which way this should go. Some here *strongly* favour the former; I've got some people telling me they *strongly* favour the latter. How will we reach a consensus?

The main intent of what I've proposed is to say that we don't push one over the other. (Kind of like Latin precomposed/decomposed representations in Unicode: the Standard doesn't try to push either over the other.)



> > Again, the main concern I'm trying to address anticipated
> > difficulty in agreeing on whether content should get tagged "zh-
> > cmn" or "cmn".
> >
>
> If the solution were obvious, we'd have been done months ago. The
> current compromise is that both camps are "satisfied" (you can use both
> forms), but one form is less preferred going forward. Most important,
> we describe what results to expect and what issues arise from a user's
> tag choices.

Well, are both camps "satisfied"? We're not just saying you can use both forms; we'd be saying, "You can use either, but we really want you to use this one."



Peter
_______________________________________________
Ltru mailing list
Ltru at ietf.org
https://www.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.