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  January 2004

ISOJAC January 2004

Subject:

Fw: issues to resolve in ISO 639 parts 1 and 2

From:

Peter Constable <[log in to unmask]>

Reply-To:

ISO 639 Joint Advisory Committee <[log in to unmask]>

Date:

Mon, 5 Jan 2004 21:50:16 -0800

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)


I have completed a document enumerating individual issues that need to be
resolved in ISO 639-1 and ISO 639-2 in order to prepare the way for ISO
639-3. For the most part, this is a matter of nailing down precisely what
the meaning of each entry in ISO 639-1/-2 is. In some cases, resolving
these issues may involve some changes; for instance, there are entries in
ISO 639-1/-2 that have names like individual-language entries, but they
probably should be collections; so, a change of the name associated with
the identifier to “… languages” may be needed.

It is essential that these things get resolved as I can’t determine what
needs to be listed in ISO 639-3 until I know exactly what each thing in ISO
639 part 1 or part 2 is supposed to be, and how it relates to the things
that are to be listed in part 3. It’s important that various stakeholders
give their input into these decisions so that we can ensure that the
standard reasonably meets the needs of all of the different sectors and
user communities that use these standards. (This includes the Internet,
WWW, software industry, linguists and other academic researchers, and other
users in addition to terminologists and bibliographers.) Also, it’s
important that this document be processed and the issues resolved
reasonably soon as it is in the critical path of progress on ISO 639-3. (It
is also in the critical path of preparation of the 15th edition of the
Ethnologue, which has a publication goal for this year.)

I tried to upload this to the TC Server, but I couldn’t figure out how to
do that. Havard, would you please post this as a TC 37/SC 2/WG 1 doc. For
those that don’t have access to TC 37’s area on the TC Server, I have
posted a copy at
http://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&item_id=PCUnicodeDocs
(it's the last link at the bottom of the page, under "Other standards
documents"

The decisions to be made pertain to ISO 639-1 and ISO 639-2, and so fall
under the jurisdiction of the ISO 639/RA Joint Advisory Committee. The
appropriate place for working discussions, then, would be the ISO 639 JAC
list. On the other hand, that is a closed-membership list, and there are
other parties not currently on that list who must be party to those
discussions as they will be involved in some capacity in the development
and future maintenance of ISO 639-3. These people are: Gary Simons (
[log in to unmask]); Paul Lewis ([log in to unmask]), who will be assuming
the role of Ethnologue Editor after the 15th edition is published; and
Anthony Aristar ([log in to unmask]), who maintains for The Linguist
List and in cooperation with SIL and the Open Language Archive Community
the catalog of historic, ancient and invented languages that will, in
complement to the Ethnologue, provide the basis for the inventory of
languages in ISO 639-3. In discussions of these issues, it will be helpful
if JAC members be sure to copy these three people. (Unfortunately, those
three will not be able to reply to the JAC list, but I can forward their
comments to the JAC list as needed.)

It may be useful for others beyond the JAC to review the doc and provide
input. There isn't one email address that can bring all the appropriate
parties together. I suggest that those of you on the JAC list with contacts
whom you think should have a chance to provide input invite your contacts
to provide feedback to you, and that you then incorporate that feedback
into your own comments on the JAC list.

For those attending the JAC meeting in D.C. next week, it will be most
helpful if you have taken time to review this document so that (hopefully)
consensus can be obtained at that time on some of the core issues. In
particular, one of the more radical innovations in ISO 639-3 is the
introduction of an addition type of identifier, which I have called (for
lack of any better term) a “macro-language identifier”. (Those who have
reviewed the CD for ISO 639-3 will have seen this notion described
already.) It is essential that we establish immediately whether the JAC
members find this innovation acceptable. (Of course, there will also be
input on this matter from TC 37 P-member bodies who submitted their
response to the ballot on the CD, the results of which have been coming
in.) The doc I have made available now explains the meaning and intent of
this notion, and enumerates the instances in which I suspect it should be
applied. Ultimately, I will be needing consensus both on the decision to
use this notion, and on the specific cases in which it is to be applied. I
would like to see both resolved as soon as possible, but it would be
especially helpful to have the former resolved by the end of that meeting.
JAC members not attending should, of course, have an opportunity to provide
input; I hope this week and next will be sufficient time in which to
consider at least the first of those two matters.


Peter Constable

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