Randy Presuhn wrote: > .... There are currently two proposals for text: > > (1) "Private-use subtags require private agreement between the parties > that intend to use or exchange language tags that use them and they > MUST NOT be used in content or protocols intended for general use > unless it can be guaranteed that they will not inadvertently show up > in parsing agents used by other parties with private-use agreements > that coincedentally employ the same alphanumeric sequence." > > (2) "Private-use subtags require private agreement between the parties > that intend to use or exchange language tags that use them. Great > caution SHOULD be used in employing them in content or protocols > intended for general use. Private-use subtags SHOULD respect the > general format contraints. Even used in a private context, general > libraries are legitimate in only using the part of each subtag which > matches the general ABNF [or in disregarding the subtags wich > does not match the general ABNF]. Private-use subtags are > simply useless for information exchange without prior arrangement." > > (2[a]) "Private-use subtags require private agreement between parties > intending to use them. Use great caution if employing them in > content or protocols intended for general use. Private-use subtags > MUST conform to the format contraints specified in the ABNF. > Private-use subtags are useless for information exchange without > prior arrangement." > > Randy How about a non-ridiculous middle ground?(3) "Private-use subtags require private agreement between parties intending to use them. They MUST NOT be designed for distribution outside of the private agreements for which they are intended. Tags intended for wider distribution SHOULD be registered instead as extensions with the [registration authority]. There MUST NOT be consequences for any application which chooses to ignore private use tags. Developers of private use tags should use great caution in ensuring that their applications are aware of, and can handle, the possibility of a conflicting private use tag from an external private agreement which appears similar to one of their own."
If we can't get rid of them, after all, the least we can do is ensure that the poor working hacks like me receive a heads-up in unambiguous language. Programmers /do/ read these things, but we can't always assume they think through the implications well. No harm in throwing them a rope.
--Dylan _______________________________________________ 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.