> > My interpretation of deprecated in computing is "this is obsolete > and replaced by something newer". Presumably it still works, but I > think in a code review you'd typically get dinged for using > deprecated APIs when newer behavior was available. Not quite a > burning at the stake, but still not good to use. > Yes, but we are not talking about code here. We're talking about value. Deprecated values are still legal values, part of the domain of values one's code MUST deal with to be a conforming implementation. "art-lojban" and "i-hak" are also deprecated, but code must still deal with those values. So too one must deal with the deprecation of either "X-Y" forms or "Y" forms. The deprecation of one in favor of the other suggests that an implementation should replace one with the other (when not otherwise obligated). In fact, my argument in favor of a particular form of deprecation partially rests on the observation that some mappings are easier to work with than others. Addison _______________________________________________ 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.