Nauduotuos:Zordsdavini/isokuods/irašėmė i Ethnologue.com

ISO639-3@sil.org

kam: man

Dear Arns Udovīčė,

Our info-sil staff forwarded your message to me, as the registrar for ISO/FDIS 639-3, for which SIL International is the registration authority. I have been aware of correspondence between you and Håvard Hjulstad of the Joint Advisory Committee for ISO 639, in reference to an application for an identifier for Samogitian in ISO 639-2.

I regret that your request for a code element for Samogitian has been caught in the delays surrounding the voting on and approval of the new ISO 639-3, which is currently in Final Draft International Standard status. We anticipate the end of the voting period very shortly. In the meantime, the Joint Advisory Committee for ISO 639 found it most appropriate to defer this application, recommending that it be submitted to the 639-3 change process for consideration.

So, in anticipation of full adoption of ISO/FDIS 639-3 soon, I invite you to submit your request for an identifier for Samogitian in the form of a Change Proposal for ISO 639-3. The following instructions and attached forms will direct you in the requirements. With regard to an entry in the Ethnologue, the editors of the Ethnologue will be very glad to correspond with you on the data that they collect and maintain, after a new code element for Samogitian has been adopted. Since they are also users of the ISO 639-3 code set, they are not able to independently assign new identifiers or make any other changes in the code set without going through the same public review process as any other submitter.

The starting point for all Change Proposals is to complete a "Change Request" form. This form is used for changes to reference information, for proposing additions of heretofore unidentified languages, and for proposing merges, splits, or retirements of existing code elements. Please submit the forms according to the following scenarios:

1. For an entirely new language (not previously considered a dialect or subvariety of a language already having a code element), submit a Change Request form and a New Code request form.
2. For a split of one language code element into two or more code elements, please submit one Change Request for the existing code element and a New Code Request for each of the new languages into which the existing element would be split.
3. For a merge of two or more language code elements into a single (existing) element, please submit one Change Request form identified according to the language code element into which all other varieties would be merged.
4. For a code element retirement for a reason other than a split or a merge (e.g., no evidence for the language exists), please submit one Change request form identified according to that code element.
5. Changes involving language name, scope, type, and/or macrolanguage mapping for a single identifier may be combined on a single Change Request form.

I hope that the forms are sufficiently clear with regard to how they should be completed. The whole process is further described on the final page of the Change Request form. These are MS Word document forms, meaning that text can only be entered into the gray fields of the forms. Please do not hesitate to ask about anything that is unclear or problematic with regard to the forms. Alternate formats are available.

It may that the Change Request will require some modification or clarification with regard to the proposed actions. Such questions will be discussed privately between the submitter and the Registrar to arrive at a fully documented Change Proposal. At the time the Change Proposal is accepted, it will be assigned a number and the submitter will be notified prior to making the Change Proposal public.

In completing each form (as many instances as are needed), please name each document as follows (omit the braces { } in an actual filename): ISO639-3_ChangeRequest_{three letter identifier under consideration, or language name for a completely new language}.doc ISO639-3_NewCode_{new language name}.doc

Once completed, these forms will be part of a Change Proposal that will be open to public review. The Registration Agency will invite reviewers from scholarly organizations, universities and national bodies to give comment (which will also become a part of the public record of the Change Proposal), as well notify the linguistic community of new proposals via the LinguistList discussion list. All Change Proposal documentation will also be posted on the 639-3/RA website at http://www.sil.org/iso639%2D3/default.asp where it may be downloaded. Comments on proposals should be submitted to the ISO 639-3 Registrar at ISO639-3@sil.org.

Thank you for your interest in the ISO/FDIS 639-3, Codes for the Identification of Languages, Part 3.

Best regards,

Joan Spanne
ISO 639-3/RA
SIL International
7500 W Camp Wisdom Rd
Dallas, TX 75236
ISO639-3@sil.org