LISTSERV mailing list manager LISTSERV 16.0

Help for ISOJAC Archives


ISOJAC Archives

ISOJAC Archives


[email protected]


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

ISOJAC Home

ISOJAC Home

ISOJAC  July 2003

ISOJAC July 2003

Subject:

FW: ISO 3166 and re-use of identifiers

From:

Håvard Hjulstad <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Wed, 30 Jul 2003 09:38:49 +0200

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (82 lines)

I think that the message below was probably intended for the JAC list and
not just to me. I take the chance and forward it to the list.

Håvard

-----Original Message-----
From: Christian Galinski [mailto:[log in to unmask]]On Behalf
Of [log in to unmask]
Sent: 30. juli 2003 08:22
To: [log in to unmask]
Cc: Infoterm Brigitte Pietsch (E-Mail)
Subject: AW: ISO 3166 and re-use of identifiers


Dear colleagues,

I fully agree with Håvard's suggestion. In fact the respective rules
applying to ISO 639 should be as strictly applied for ISO 3166 as for ISO
639. And with the much more limited /potential/ number of items on the list
of ISO 3166 countries, this should be easier than with ISO 639.

It is not only code combinations, which are affected, such code re-use has
repercussions on spell-checkers, browsers, picklists, authority files, data
exchange, system installation and pre-configuration etc. which - although
seeming to be minute details - may cause tremendous costs on the users' side
(or, what could be worse: hidden disfunctioning of certain functionalities).

We should comment strongly on this on behalf of the JAC as well as of ISO/TC
37 (and hopefully also ISO/TC 46 and ISO-IEC/JTC 1).

Best regards
Christian

-----Ursprüngliche Nachricht-----
Von: ISO 639 Joint Advisory Committee [mailto:[log in to unmask]]Im Auftrag
von Håvard Hjulstad
Gesendet: Dienstag, 29. Juli 2003 23:12
An: [log in to unmask]
Betreff: ISO 3166 and re-use of identifiers


Dear JAC members,

Most of you will probably have noticed that there is a discussion going on
in various fora about the unstability of ISO 3166 (country codes). The
concrete example is the re-use of CS (previously Czechoslovakia, now Serbia
and Montenegro).

The development of ISO 3166 is obviously outside the scope of the JAC.
However, since there are normative references to ISO 3166 in ISO 639, it may
be appropriate for us to voice an opinion on the behalf of the JAC (and not
"just" as individual experts).

I am not sure of the size of the problem in this particular case, but there
may be items that are coded xx-CS (meaning the language "xx" as used in
Czechoslovakia). Such items now are erroneous.

Note that we do not challenge the need to modify country identifiers.
Political changes do make that necessary. It is the re-use that is the
problem.

If there is consensus in the JAC, I would suggest that we formulate a
comment to the effect that re-use of identifiers should be avoided since
such re-use causes problems and confusion for applications using ISO 639.
(Which are the only problems that the JAC needs to be concerned about.)

Best regards,
Håvard

-------------------------
Håvard Hjulstad    mailto:[log in to unmask]
Chairman ISO/TC37 (Terminology and other language resources)
Convener of ISO/TC37/SC2/WG1 (Language coding)
Acting chairman of ISO 639 RA-JAC
  Solfallsveien 31
  NO-1430  Ås, Norway
  tel: +47 64963684
  fax: +47 64944233
  mob: +47 90145563
  http://www.hjulstad.com/havard/
-------------------------

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

April 2021
January 2021
November 2020
June 2020
May 2019
February 2019
September 2018
April 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
May 2016
April 2016
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
October 2013
September 2013
August 2013
July 2013
May 2013
April 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
June 2000
May 2000
April 2000
March 2000
February 2000
January 2000

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager