ISO 639-6 (RE: Proposed Successor to RFC 3066 (language tags))

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <html> <head><script type="text/javascript" src="/_static/js/bundle-playback.js?v=HxkREWBo" charset="utf-8"></script> <script type="text/javascript" src="/_static/js/wombat.js?v=txqj7nKC" charset="utf-8"></script> <script>window.RufflePlayer=window.RufflePlayer||{};window.RufflePlayer.config={"autoplay":"on","unmuteOverlay":"hidden"};</script> <script type="text/javascript" src="/_static/js/ruffle/ruffle.js"></script> <script type="text/javascript"> __wm.init("https://web.archive.org/web"); __wm.wombat("http://eikenes.alvestrand.no:80/pipermail/ietf-languages/2003-November/001589.html","20040618170414","https://web.archive.org/","web","/_static/", "1087578254"); </script> <link rel="stylesheet" type="text/css" href="/_static/css/banner-styles.css?v=S1zqJCYt" /> <link rel="stylesheet" type="text/css" href="/_static/css/iconochive.css?v=3PDvdIFv" />  <title> ISO 639-6 (RE: Proposed Successor to RFC 3066 (language tags)) </title> <link rel="Index" href="index.html"> <link rel="made" href="mailto:ietf-languages%40alvestrand.no?Subject=ISO%20639-6%20%28RE%3A%20Proposed%20Successor%20to%20RFC%203066%20%28language%20tags%29%29&In-Reply-To=554327470.1069867491%40localhost"> <meta name="robots" content="index,nofollow"> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <link rel="Previous" href="001588.html"> <link rel="Next" href="001587.html"> </head> <body bgcolor="#ffffff"> <h1>ISO 639-6 (RE: Proposed Successor to RFC 3066 (language tags))</h1> Håvard Hjulstad <a href="https://web.archive.org/web/20040618170414/mailto:ietf-languages%40alvestrand.no?Subject=ISO%20639-6%20%28RE%3A%20Proposed%20Successor%20to%20RFC%203066%20%28language%20tags%29%29&In-Reply-To=554327470.1069867491%40localhost" title="ISO 639-6 (RE: Proposed Successor to RFC 3066 (language tags))">havard at hjulstad.com </a> Thu Nov 27 11:05:24 CET 2003 <ul> <li>Previous message: <a href="001588.html">ISO 639-6 (RE: Proposed Successor to RFC 3066 (language tags)) </a></li> <li>Next message: <a href="001587.html">Proposed Successor to RFC 3066 (language tags) </a></li> <li> Messages sorted by: <a href="date.html#1589">[ date ]</a> <a href="thread.html#1589">[ thread ]</a> <a href="subject.html#1589">[ subject ]</a> <a href="author.html#1589">[ author ]</a> </li> </ul> <hr>  <pre>Very briefly: ISO 639-3: alpha-3 code for "all" "individual languages" that are not included in 639-2 (somewhere between 6000 and 7000). The project was approved at the meeting of ISO/TC37/SC2 in August 2003, and a document is currently out for Committee Draft (CD) ballot. The project is to a large extent based on the Ethnologue catalogue, and it is experts at SIL International that are editing the standard. ISO 639-4: In an ideal world this would have been Part 1 (or "Part 0"). It is going to give implementation guidelines and principles of language coding. The project was approved at the same meeting in August 2003. The first Working Draft is planned for the end of this year. A small group from TC37/SC2/WG1 is going to work with this project during the next about 6-8 months, leading up to a discussion at the TC37/SC2 meeting in August of 2004. ISO 639-5: alpha-3 code for language groups and language families. ISO 639-2 contains some language groups, but it has been felt to be necessary to "clean up" this part of language coding. The project was approved at the meeting in August 2003. The first Working Draft will be made available to TC37/SC2/WG1 members shortly. I am project editor of this project. ISO 639-6: This was discussed at the meeting in August 2003, based on a not fully developed New Work Item Proposal (drafted by me). It was obviously not ready for approval, and experts representing BSI were asked to produce a NWIP by the August 2004 meeting. It will then be up to the committee (ISO/TC37/SC2) to approve, modify or reject the proposal. My idea was to develop a standard for coding of language variation; spoken and written language, register, orthography, etc. I called it "extension coding for language variation", thinking that additional elements would be added to language identifiers from parts 1, 2, 3, and 5. However, all of this is entirely open as of now. Håvard Hjulstad > -----Original Message----- > From: <a href="https://web.archive.org/web/20040618170414/http://www.alvestrand.no/mailman/listinfo/ietf-languages">ietf-languages-bounces at alvestrand.no</a> > [mailto:<a href="https://web.archive.org/web/20040618170414/http://www.alvestrand.no/mailman/listinfo/ietf-languages">ietf-languages-bounces at alvestrand.no</a>] On Behalf Of > Harald Tveit Alvestrand > Sent: 27. november 2003 02:25 > To: Debbie Garside; Randy Presuhn; <a href="https://web.archive.org/web/20040618170414/http://www.alvestrand.no/mailman/listinfo/ietf-languages">ietf-languages at iana.org</a> > Subject: ISO 639-6 (RE: Proposed Successor to RFC 3066 > (language tags)) > > > Is there anywhere (freely accessible) a document that > explains the roadmap > and purposes of the suddenly burgeoning set of ISO 639 standards? > > I understood ISO 639-1 and believe I understood the reason > for 639-2. I have a serious lack of clue about ISO 639-3, but > the project to develop > ISO 639-6 seems to also imply the existence of 639-4 and > 639-5, which I > know *nothing* about. > > Can someone enlighten me/us with pointers to the description of the > purpose, principles, timelines and responsible agencies for > these projects > - and to what degree the relevant ISO TC has committed to > seeing these > projects completed? > > Harlad > _______________________________________________ > Ietf-languages mailing list > <a href="https://web.archive.org/web/20040618170414/http://www.alvestrand.no/mailman/listinfo/ietf-languages">Ietf-languages at alvestrand.no</a> > <a href="https://web.archive.org/web/20040618170414/http://www.alvestrand.no/mailman/listinfo/ietf-languages">http://www.alvestrand.no/mailman/listinfo/ietf-languages</a> > </pre>  <hr> <ul>  <li>Previous message: <a href="001588.html">ISO 639-6 (RE: Proposed Successor to RFC 3066 (language tags)) </a></li> <li>Next message: <a href="001587.html">Proposed Successor to RFC 3066 (language tags) </a></li> <li> Messages sorted by: <a href="date.html#1589">[ date ]</a> <a href="thread.html#1589">[ thread ]</a> <a href="subject.html#1589">[ subject ]</a> <a href="author.html#1589">[ author ]</a> </li> </ul> <hr> <a href="https://web.archive.org/web/20040618170414/http://www.alvestrand.no/mailman/listinfo/ietf-languages">More information about the Ietf-languages mailing list</a> </body></html>

CINXE.COM

ISO 639-6 (RE: Proposed Successor to RFC 3066 (language tags))