r&d afrac <rd at afrac dot org> wrote: >> A person who knows not a single word of Shona and knows nothing of >> the culture of the Shona-speaking people can still work to develop a >> tagging mechanism by which Shona text can be indicated by use of the >> string "sn". > > This, I believe, describes perfectly why the Draft doctrine adds to > the basic error of RFC 3066 attenuated by its lose application (that > IETF has the capacity to correlate non protocol parameters). Jon > Postel had clearly established it: this is none of the IANA business. > Not only it seems that cultural empowerment is ignored by the author > of this text. But, since the topic here is ISO 3166, it shows a > remakable confusion between Senegal and Zimbabwe which precisely > document my point and the difficulty to establish general rules in a > world made of particulars. RFC 1766 and 3066 and the current draft use two-letter strings as both language identifiers and country identifiers. There are strict contextual rules for their use: a country code can never appear by itself in a language tag. If you are attempting to show that the draft introduces "remarkable confusion" because the two-letter string "sn" could be either a language subtag for Shona or a region subtag for Senegal, you have failed utterly. You have only proven that it is possible to confuse people by referring to things out of context. I am finished with this thread. -- Doug Ewell Fullerton, California http://users.adelphia.net/~dewell/ _______________________________________________ Ltru mailing list Ltru at lists.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.