LISTSERV mailing list manager LISTSERV 16.0

Help for ISOJAC Archives


ISOJAC Archives

ISOJAC Archives


ISOJAC@LISTSERV.LOC.GOV


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  March 2000

ISOJAC March 2000

Subject:

N2R and N3R

From:

"Rebecca S. Guenther" <[log in to unmask]>

Reply-To:

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

Date:

Fri, 10 Mar 2000 12:21:25 -0500

Content-Type:

MULTIPART/MIXED

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (21 lines) , iso639jac_n2r.html (1 lines) , iso639jac_n3r.html (1 lines)


To ISO 639 JAC:

Documents N2 and N3 have been revised according to our discussions and are
attached. I do not want to do any major revisions unless there are errors
or ambiguities.  If you have specific comments, please send them by the
middle of next week (15 March).

Are there any reasons not to make these public documents? When they were
in draft and not yet discussed, I considered them only for the committee,
but now that we have discussed them and will shortly finalize them, I
think they can probably be available to anyone.

In cases where we have drafts that we wish to discuss before making them
public, I do now have an area to put these in (password protected as is
the archives of the JAC list).

Rebecca




<HTML> <HEAD> <TITLE>ISO 639/JAC N2R: Rules for procedure for the conduct of meetings</TITLE> <base href="http://lcweb.loc.gov/standards/iso639-2/iso639jac_rules.html"> <meta name="keywords" content="Language Codes ISO 639 JAC rules procedure"> <meta name="description" content="Rules of procedure for the conduct of meetings and business by email by the ISO 639/Joint Advisory Committee."> </HEAD> <BODY BGCOLOR="ffffff"> <B>ISO 639/JAC N2R</B><CENTER><B><H1>ISO 639 Joint Advisory Committee</H1> <P> <H2>Rules of procedure for conducting business</H2> <P> </B>(10 March 2000) </CENTER> <P> <HR> The following documents rules of procedure for the conduct of meetings and email business by the ISO 639 Joint Advisory Committee. It repeats some information that is in ISO 639-2:1998 in the normative Annex A and elaborates where necessary for clarification of procedures. In particular it details how business is run in the absence of regular meetings. <P> <HR> <P> <B><H3>1. Composition of the Joint Advisory Committee</H3></B> <P> ISO 639/JAC is composed of: <P> <UL><LI>one representative of the International Information Centre for Terminology (Infoterm; representing ISO 639-1/RA) <LI>one representative of the Library of Congress (LC; representing ISO 639-2/RA) <LI>three representatives of ISO/TC 37 (nominated by ISO/TC 37) <LI>three representatives of ISO/TC 46 (nominated by ISO/TC46)</UL> <P> Both ISO/TCs may nominate substitute representatives for a meeting. <P> <H3><B>2. Membership of ISO 639/JAC</B></H3> <P> <UL><LI>Representatives of Infoterm and Library of Congress will hold the chair on a 2-year rotating basis. The first term begins at the first meeting in February 2000. <LI>Up to six technical experts may be asked to participate as non-voting observers. Each TC (TC37 and TC46) may appoint three observers based on the issues and topics being discussed. <li>Representatives may be reappointed or replaced if necessary by the appropriate TC. Observers may be replaced by the appropriate rotating chair.</ul><p> <H3><B>3. Procedures for conducting business at meetings</B></H3> <P><I>3.1. Agenda.</I> <P> <UL><LI>An agenda will be distributed at least two months prior to the meeting. It will be amended as needed when meeting is convened if there is agreement.</UL> <P> <I>3.2. Voting.</I> <P> <UL><LI>Each member of ISO 639/JAC has one vote. <LI>Voting is obligatory. <LI>A vote must be unanimous for approval of an item. If there are abstentions, it shall not be considered unanimous approval. <LI>If a unanimous vote cannot be reached on an item, a second vote will be conducted following discussion.<LI>At least five positive votes are required to pass on the second ballot.</UL> <P> <I>3.3. Role of observers</I> <P> <UL><LI>The designated observers may attend a JAC meeting. No more than three observers from each TC may attend. <LI>Observers shall function as experts concerning specific language issues, not for procedural issues. <LI>Observers will be asked to contribute as necessary. <LI>Observers may not vote.<li>Experts on specific topics may attend future meetings if appropriate as determined by the chair.</UL> <H3><B>4. Procedures for conducting business by electronic mail</B></H3> <I>4.1. Electronic communications</I> <UL><LI>An electronic distribution list will include all ISO 639/JAC members and appointed observers. <LI>Numbered documents are distributed by the chair. They may be distributed to the JAC list (JAC members and observers) or more widely depending upon the topic. <li>The two rotating chairs may wish to consult on the appropriate distribution for official committee documents. <LI>The more general list ([log in to unmask]) may be used for discussion about general or specific language issues. <li>Prior to voting on specific changes new proposals should be openly discussed on language-related lists. <li>The chair may ask specific experts about specific language issues as necessary.</UL> <p> <I>4.2. Electronic voting procedures</I> <P> <UL> <LI>Voting may take place electronically on the list initially and confirmed in writing. A printed record will be kept. <LI>Votes must be submitted within two weeks of the electronic distribution of the voting request. <li>In some circumstances the voting period may be extended if necessary because of complex issues; in these cases the deadline will be stated when the voting request is distributed. <LI>Failure to vote is considered an abstention (and thus a unanimous ballot cannot be reached with an abstention). <LI>If a JAC member does not vote after two consecutive times, the JAC chair will inform the appropriate TC subcommittee and request a replacement. </UL> <P><I>4.3. Role of observers</I> <UL><LI>Observers will be included in electronic mail distributions when specific language issues are discussed and their expertise is needed. <LI>Observers may be requested to perform research on specific language issues when needed.</UL> <P> <I>4.4. Deadlines for response</I> <UL><LI>When a request for a new, deleted, or changed code is submitted to the appropriate Registration Authority (Infoterm for 639-1 and Library of Congress for 639-2), the RA determines whether or not the request meets the relevant criteria. <li>The appropriate RA informs the requestor of the process generally within two weeks of the submission.<li>If the request meets the criteria, the RA determines an appropriate code and consults the ISO 639/JAC. <LI>ISO 639/JAC is obliged to respond within one month with a decision. This allows for a second round of voting if the first vote is not unanimous.<li>The original requestor shall be informed of the JAC decision in six weeks to two months from submission of the original request.<li>Results of the JAC decisions will be publicized in a newsletter available on the Web and distributed through distribution lists.</UL> <P> See also Working principles for ISO 639 maintenance (<A HREF="http://www.loc.gov/loc/standards/iso639-2/iso639jac_n3r.html">ISO 639/JAC N3R</A>). <P> <HR> <P> <center><a href="http://lcweb.loc.gov/standards/iso639-2/iso639jac.html">ISO 639 Joint Advisory Committee Home Page</a> - <a href="http://lcweb.loc.gov/standards/iso639-2/">ISO 639-2 Registration Authority Home Page</a> - <br> ISO 639-1 Registration Authority Home Page (not yet active)</center> <p> <!---LC Footer---> <HR> <IMG SRC="http://lcweb.loc.gov/homepage/lc2.gif" HEIGHT=46 WIDTH=91 ALT=""> <STRONG>Library of Congress</STRONG><BR> <ADDRESS>Comments: <A HREF="mailto:[log in to unmask]" TITLE="MARC Proposals">[log in to unmask]</A> (03/10/00)</ADDRESS> </BODY> </HTML>
<HTML> <HEAD> <TITLE>ISO 639/JAC N3 (Working Principles for ISO 639 Maintenance)</TITLE> <base href="http://lcweb.loc.gov/standards/iso639-2/iso639jac_n3r.html"> <meta name="keywords" content="Language Codes ISO 639 JAC principles"> <meta name="description" content="Working principles for the maintenance of language codes by the ISO 639/Joint Advisory Committee."> </HEAD> <BODY BGCOLOR="#ffffff"> <B>ISO 639/JAC N3R</B><CENTER><B><H1>ISO 639 Joint Advisory Committee</H1></b> <P> <H2>Working principles for ISO 639 maintenance</H2> <P>(8 March 2000) </CENTER> <P> <HR> The following documents working principles for the maintenance of language codes by the ISO 639 Joint Advisory Committee both in ISO 639-1 (Alpha-2 code) and ISO 639-2 (Alpha-3 code). It repeats some information that is in ISO 639-2:1998 in section 4 (Language codes) and the normative Annex A. In addition, it gives further details as to how language code changes that are submitted are considered and how the two parts of ISO 639 are related. <P> <HR> <P> <B><H3>1. Definition of new language codes</H3></B> <P><B>1.1. Procedures</B> <UL><LI>A <a href="http://lcweb.loc.gov/standards/iso639-2/iso639-2form.html">Registration form</a> is available on the Web for requesting new language codes, which is submitted to the appropriate ISO 639 Registration Authority for consideration.<LI>The Registration Authority will review applications, obtain additional information and/or justification from the submitter, and suggest the assignment of a code when the relevant criteria are met.</UL> <P> <B>1.2. Criteria for ISO 639-2</B> <P><UL> <LI><I>Number of documents. </I>The request for a new language code shall include evidence that one agency holds 50 different documents in the language or that five agencies hold a total of 50 different documents among them in the language. Documents include all forms of material and is not limited to text. <LI><I>Collective codes. </I>If the criteria above are not met the language may be assigned a new or existing collective language code. The words <I>languages</I> or <I>other</I> as part of a language name indicates that a language code is a collective one. <LI><I>Scripts.</I> A single language code is normally provided for a language even though the language is written in more than one script. A standard for script codes is under development by ISO/TC46/SC2, ISO DIS 15924: <I>Codes for the representation of names of scripts</I>. <LI><I>Dialects.</I>A dialect of a language is usually represented by the same language code as that used for the language. If the language is assigned to a collective language code, the dialect is assigned to the same collective language code. The difference between dialects and languages will be decided on a case-by-case basis.<li><i>Orthography.</i> A language using more than one orthography is not given multiple language codes. </UL> <p> <b>1.3. Criteria for ISO 639-1</b> <p> <ul><li><i>Relation to ISO 639-2.</i> Since ISO 639-1 is to remain a subset of ISO 639-2, it must first satisfy the requirements for ISO 639-2 and also satisfy the following. <li><i>Documentation.</i> <ul><li>a significant body of existing documents (specialized texts, such as college or university textbooks, technical documentation manuals, specialized journals, subject-field related books, etc.) written in specialized languages<li>a number of existing terminologies in various subject fields (e.g. technical dictionaries, specialized glossaries, vocabularies, etc. in printed or electronic form)</ul> <li><i>Recommendation.</i>A recommendation and support of a specialized authority (such as a standards organization, governmental body, linguistic institution, or cultural organization) <li><i>Other considerations</i><ul><li>the number of speakers of the language community<li>the recognized status of the language in one or more countries<li>the support of the request by one or more official bodies</ul><li><i>Collective codes.</i> ISO 639-1 does not use collective codes. If these are necessary the alpha-3 code shall be used.</ul> <p> <B><H3>2. Choice of new language codes</H3></B> <P><UL><LI>Language codes consist of the following 26 letters of the Latin alphabet in lower case with no diacritical marks or modified characters: a, b, c, d, e, f, g, h, i, j, k, l, m, n, o, p, q, r, s, t, u, v, w, x, y, z.<li>ISO 639-2 uses three alphabetic characters, and ISO 639-1 uses two alphabetic characters.<LI>Codes need not be abbreviations for the language as they are intended to serve as an arbitrary device to identify a given language or group of languages. Mnemonicity of codes is striven for, but this may not always be possible or appropriate.<LI>An effort is made to derive a language code from a language's name for itself, when possible. For historical reasons, some codes may be based on the name of a language in English. <LI>There are 23 language names in ISO 639-2 that have variant codes, one for bibliographic applications, the other for terminological applications. This was because of established usage in national and international bibliographic databases which employed codes based on English language forms of names. <LI>New language codes shall be based on the vernacular form of name unless <ul><li>another language code is requested by the country or countries using the language or the sponsor submitting the request; <li> if the vernacular cannot be determined; or <li>if a suitable code is not available</ul> In the latter two cases, an English form of name may be used for to derive the language code.<LI>A language code already in ISO 639-2/T which is based on the English form of the name shall not be changed even if the vernacular form is determined and/or added to ISO 639-1. This is to ensure continuity and stability and to prevent the proliferation of multiple or alternative codes. <LI>A prefix is not regarded as part of the language name for purposes of assigning a code (e.g. Swahili is language name, although "KiSwahili" is often used). </UL> <B><H3>3. Changes of existing language codes</H3></B> <P> <UL><LI>To ensure continuity and stability in support of online retrieval from large databases built over many years, codes shall not be changed. <LI>Where codes have been changed or discontinued in the past, the old codes shall not be reassigned. <LI>Language codes shall not be changed if the conventional name of a language is changed. However, language names associated with codes may be changed. <li> Variant forms of a language name may be included in the entry, separated by a semicolon in the future. No effort will be made by the Registration Authorities to collect those variants that were previously not included. <li>The <a href="http://lcweb.loc.gov/marc/languages/"><i>MARC Code List for Languages</i></a> maintains variant names of languages and may be used as a reference source.</UL> <P> <B><H3>4. Relationship between ISO 639-1 to ISO 639-2 </H3></B> <P> <UL><LI>In development of ISO 639-2 there was a principle that a code in the alpha-3 list would include the 2 characters from the alpha-2 where possible. An exception was the alternative codes, where longstanding and widespread existing usage of bibliographic codes did not permit this. <LI>New codes introduced in ISO 639-1 that are already included in ISO 639-2 should follow this principle. If the vernacular form had not been used in ISO 639-2/T, the ISO JAC will attempt establish an alpha-2 code with two letters in common with the alpha-3 code when possible. <LI>ISO 639-1 shall be a subset of ISO 639-2. <li>New codes will no longer be added to ISO 639-1 after the publication of a revised standard. <li>A language code already in ISO 639-2 at the point of freezing ISO 639-1 shall not later be added to ISO 639-1. This is to ensure consistency in usage over time, since users are directed in Internet applications to employ the alpha-3 code when an alpha-2 code for that language is not available.<LI>New language codes may be considered for inclusion in both parts or in ISO 639-2 only. If request is to add to ISO 639-1 it must also be added to ISO 639-2 and satisfy the stated criteria. </UL> <P> See also <a href="http://lcweb.loc.gov/standards/iso639-2/iso639jac_n2r.html">Rules of procedure for conducting business</a> (ISO 639/JAC N2R). <P> <HR> <P><center><a href="http://lcweb.loc.gov/standards/iso639-2/iso639jac.html">ISO 639 Joint Advisory Committee Home Page</a> - <a href="http://lcweb.loc.gov/standards/iso639-2/">ISO 639-2 Registration Authority Home Page</a> - <br> ISO 639-1 Registration Authority Home Page (not yet active)</center> <p> <P> <!---LC Footer---> <HR> <IMG SRC="http://lcweb.loc.gov/homepage/lc2.gif" HEIGHT=46 WIDTH=91 ALT=""> <STRONG>Library of Congress</STRONG><BR> <ADDRESS>Comments: <A HREF="mailto:[log in to unmask]" TITLE="MARC Proposals">[log in to unmask]</A> (2/10/00)</ADDRESS></BODY> </HTML>

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