Phillips, Addison 2008-10-01 17.47:
I'm not saying year numbers don't ever have their place, but it worries me when we expect them to be so common that we are thinking about compromising an important property of the Registry, uniqueness of subtag values within type, in anticipation that there will be tons of them.I don't think the problem will be common. The problem is that the potential for conflicts is relatively large if years end up being used commonly, since mostly we'll be registering either (a) new events that happen typically in the current or a recent year or (b) standards published in the relatively recent past fifty years or so (1694acad notwithstanding). I don't think it is a huge problem, but I think we should foreclose the possibility of a particular year being given two meanings.
For Norwegian Nynorsk, I could meaningfully register at the very least 3 years. Same for Norwegian Bokmål. And even more if I were to really register all the revisions. Most modern language norms are not more than 200 years old, I think. So year numbers for the last 200 years would be most at risk for being used.
There is a "clash" problem in the case of Macrolanguage subtags. For instance, both Bokmål and Nynorsk was revised in 1917. So if one wrote "no-1917", then it would not be clear what it meant. (However, that unclarity allready is built into the 'no' tag.) Whereas, if I wrote no-1907, then it could only refer to the Bokmål reform of 1907. (Interesting side effect that variation tags could make a macrolangauge tag more spesific.)
Otherwise, I am not sure what conflict you talk about. Used correctly, there should not be any conflict (except with Macrolanguage subtags). Of course, there will be different reforms linked to the same year, no doubt, if that was what you meant.
-- leif halvard silli _______________________________________________ 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.