> Mark, > I am sorry, Frank is right. You cannot be cannonical with tables you do > not > control. This is precisely the problem the charter wants us to address. > Stability is not in the ID but in the documented object. You have two > possibilities: to attach a date to the ID or to define your own canonical > table and relate it to the ID. > jfc Uh... The items in the registry all have dates attached to them. And they are in their own canonical table over which the registry draft has ironclad control. We are discussing rules for the maintenance of canonical values and stability of those values in that registry. The use of ISO 3166 to provide some of the values in that table does not mean that the registry cedes control to the ISO 3166 MA. Defining rules for how the registry tracks ISO 3166 is what we are about here, since creating separate standards for these things is unappealing. Addison Addison P. Phillips Globalization Architect, Quest Software Chair, W3C Internationalization Core Working Group Internationalization is not a feature. It is an architecture. _______________________________________________ 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.