1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> 2<html lang="en"><head><title>BCP 47 Extension U</title> 3<meta http-equiv="Content-Type" content="text/html; charset=utf-8"> 4<meta name="description" content="BCP 47 Extension U"> 5<meta name="keywords" content="locale, bcp 47"> 6<meta name="generator" content="xml2rfc v1.35pre1 (http://xml.resource.org/)"> 7<style type='text/css'><!-- 8 body { 9 font-family: verdana, charcoal, helvetica, arial, sans-serif; 10 font-size: small; color: #000; background-color: #FFF; 11 margin: 2em; 12 } 13 h1, h2, h3, h4, h5, h6 { 14 font-family: helvetica, monaco, "MS Sans Serif", arial, sans-serif; 15 font-weight: bold; font-style: normal; 16 } 17 h1 { color: #900; background-color: transparent; text-align: right; } 18 h3 { color: #333; background-color: transparent; } 19 20 td.RFCbug { 21 font-size: x-small; text-decoration: none; 22 width: 30px; height: 30px; padding-top: 2px; 23 text-align: justify; vertical-align: middle; 24 background-color: #000; 25 } 26 td.RFCbug span.RFC { 27 font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, verdana, sans-serif; 28 font-weight: bold; color: #666; 29 } 30 td.RFCbug span.hotText { 31 font-family: charcoal, monaco, geneva, "MS Sans Serif", helvetica, verdana, sans-serif; 32 font-weight: normal; text-align: center; color: #FFF; 33 } 34 35 table.TOCbug { width: 30px; height: 15px; } 36 td.TOCbug { 37 text-align: center; width: 30px; height: 15px; 38 color: #FFF; background-color: #900; 39 } 40 td.TOCbug a { 41 font-family: monaco, charcoal, geneva, "MS Sans Serif", helvetica, sans-serif; 42 font-weight: bold; font-size: x-small; text-decoration: none; 43 color: #FFF; background-color: transparent; 44 } 45 46 td.header { 47 font-family: arial, helvetica, sans-serif; font-size: x-small; 48 vertical-align: top; width: 33%; 49 color: #FFF; background-color: #666; 50 } 51 td.author { font-weight: bold; font-size: x-small; margin-left: 4em; } 52 td.author-text { font-size: x-small; } 53 54 /* info code from SantaKlauss at http://www.madaboutstyle.com/tooltip2.html */ 55 a.info { 56 /* This is the key. */ 57 position: relative; 58 z-index: 24; 59 text-decoration: none; 60 } 61 a.info:hover { 62 z-index: 25; 63 color: #FFF; background-color: #900; 64 } 65 a.info span { display: none; } 66 a.info:hover span.info { 67 /* The span will display just on :hover state. */ 68 display: block; 69 position: absolute; 70 font-size: smaller; 71 top: 2em; left: -5em; width: 15em; 72 padding: 2px; border: 1px solid #333; 73 color: #900; background-color: #EEE; 74 text-align: left; 75 } 76 77 a { font-weight: bold; } 78 a:link { color: #900; background-color: transparent; } 79 a:visited { color: #633; background-color: transparent; } 80 a:active { color: #633; background-color: transparent; } 81 82 p { margin-left: 2em; margin-right: 2em; } 83 p.copyright { font-size: x-small; } 84 p.toc { font-size: small; font-weight: bold; margin-left: 3em; } 85 table.toc { margin: 0 0 0 3em; padding: 0; border: 0; vertical-align: text-top; } 86 td.toc { font-size: small; font-weight: bold; vertical-align: text-top; } 87 88 ol.text { margin-left: 2em; margin-right: 2em; } 89 ul.text { margin-left: 2em; margin-right: 2em; } 90 li { margin-left: 3em; } 91 92 /* RFC-2629 <spanx>s and <artwork>s. */ 93 em { font-style: italic; } 94 strong { font-weight: bold; } 95 dfn { font-weight: bold; font-style: normal; } 96 cite { font-weight: normal; font-style: normal; } 97 tt { color: #036; } 98 tt, pre, pre dfn, pre em, pre cite, pre span { 99 font-family: "Courier New", Courier, monospace; font-size: small; 100 } 101 pre { 102 text-align: left; padding: 4px; 103 color: #000; background-color: #CCC; 104 } 105 pre dfn { color: #900; } 106 pre em { color: #66F; background-color: #FFC; font-weight: normal; } 107 pre .key { color: #33C; font-weight: bold; } 108 pre .id { color: #900; } 109 pre .str { color: #000; background-color: #CFF; } 110 pre .val { color: #066; } 111 pre .rep { color: #909; } 112 pre .oth { color: #000; background-color: #FCF; } 113 pre .err { background-color: #FCC; } 114 115 /* RFC-2629 <texttable>s. */ 116 table.all, table.full, table.headers, table.none { 117 font-size: small; text-align: center; border-width: 2px; 118 vertical-align: top; border-collapse: collapse; 119 } 120 table.all, table.full { border-style: solid; border-color: black; } 121 table.headers, table.none { border-style: none; } 122 th { 123 font-weight: bold; border-color: black; 124 border-width: 2px 2px 3px 2px; 125 } 126 table.all th, table.full th { border-style: solid; } 127 table.headers th { border-style: none none solid none; } 128 table.none th { border-style: none; } 129 table.all td { 130 border-style: solid; border-color: #333; 131 border-width: 1px 2px; 132 } 133 table.full td, table.headers td, table.none td { border-style: none; } 134 135 hr { height: 1px; } 136 hr.insert { 137 width: 80%; border-style: none; border-width: 0; 138 color: #CCC; background-color: #CCC; 139 } 140--></style> 141</head> 142<body> 143<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 144<table summary="layout" width="66%" border="0" cellpadding="0" cellspacing="0"><tr><td><table summary="layout" width="100%" border="0" cellpadding="2" cellspacing="1"> 145<tr><td class="header">Internet Engineering Task Force</td><td class="header">M. Davis</td></tr> 146<tr><td class="header">Internet-Draft</td><td class="header">Google</td></tr> 147<tr><td class="header">Intended status: BCP</td><td class="header">A. Phillips</td></tr> 148<tr><td class="header">Expires: July 17, 2010</td><td class="header">Lab126</td></tr> 149<tr><td class="header"> </td><td class="header">Y. Umaoka</td></tr> 150<tr><td class="header"> </td><td class="header">IBM</td></tr> 151<tr><td class="header"> </td><td class="header">January 13, 2010</td></tr> 152</table></td></tr></table> 153<h1><br />BCP 47 Extension U<br />draft-davis-u-langtag-ext-00</h1> 154 155<h3>Abstract</h3> 156 157<p>This document specifies an Extension to BCP 47 158 which provides subtags that specify language and/or locale-based behavior or refinements to language tags, according 159 to work done by the Unicode Consortium. 160</p> 161<h3>Status of this Memo</h3> 162<p> 163This Internet-Draft is submitted to IETF in full 164conformance with the provisions of BCP 78 and BCP 79.</p> 165<p> 166Internet-Drafts are working documents of the Internet Engineering 167Task Force (IETF), its areas, and its working groups. 168Note that other groups may also distribute working documents as 169Internet-Drafts.</p> 170<p> 171Internet-Drafts are draft documents valid for a maximum of six months 172and may be updated, replaced, or obsoleted by other documents at any time. 173It is inappropriate to use Internet-Drafts as reference material or to cite 174them other than as “work in progress.”</p> 175<p> 176The list of current Internet-Drafts can be accessed at 177<a href='http://www.ietf.org/ietf/1id-abstracts.txt'>http://www.ietf.org/ietf/1id-abstracts.txt</a>.</p> 178<p> 179The list of Internet-Draft Shadow Directories can be accessed at 180<a href='http://www.ietf.org/shadow.html'>http://www.ietf.org/shadow.html</a>.</p> 181<p> 182This Internet-Draft will expire on July 17, 2010.</p> 183 184<h3>Copyright Notice</h3> 185<p> 186Copyright (c) 2010 IETF Trust and the persons identified as the 187document authors. All rights reserved.</p> 188<p> 189This document is subject to BCP 78 and the IETF Trust's Legal 190Provisions Relating to IETF Documents 191(http://trustee.ietf.org/license-info) in effect on the date of 192publication of this document. Please review these documents 193carefully, as they describe your rights and restrictions with respect 194to this document. Code Components extracted from this document must 195include Simplified BSD License text as described in Section 4.e of 196the Trust Legal Provisions and are provided without warranty as 197described in the BSD License.</p> 198<a name="toc"></a><br /><hr /> 199<h3>Table of Contents</h3> 200<p class="toc"> 201<a href="#anchor1">1.</a> 202Introduction<br /> 203 <a href="#anchor2">1.1.</a> 204Requirements Language<br /> 205<a href="#anchor3">2.</a> 206BCP47 Required Information<br /> 207 <a href="#anchor4">2.1.</a> 208Summary<br /> 209 <a href="#canonicalization">2.1.1.</a> 210Canonicalization<br /> 211 <a href="#regform">2.2.</a> 212Registration Form<br /> 213<a href="#Acknowledgements">3.</a> 214Acknowledgements<br /> 215<a href="#IANA">4.</a> 216IANA Considerations<br /> 217<a href="#Security">5.</a> 218Security Considerations<br /> 219<a href="#rfc.references1">6.</a> 220References<br /> 221 <a href="#rfc.references1">6.1.</a> 222Normative References<br /> 223 <a href="#rfc.references2">6.2.</a> 224Informative References<br /> 225<a href="#rfc.authors">§</a> 226Authors' Addresses<br /> 227</p> 228<br clear="all" /> 229 230<a name="anchor1"></a><br /><hr /> 231<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 232<a name="rfc.section.1"></a><h3>1. 233Introduction</h3> 234 235<p> <a class='info' href='#BCP47'>[BCP47]<span> (</span><span class='info'>Davis, M., Ed., “Tags for the Identification of Language (BCP47),” September 2009.</span><span>)</span></a> permits the definition and registration of language tag extensions "that 236 contain a language component and are compatible with applications that 237 understand language tags". This document defines an extension for identifying Unicode locale-based variations using language tags. The "singleton" identifier for this extension is 'u'. 238</p> 239<a name="anchor2"></a><br /><hr /> 240<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 241<a name="rfc.section.1.1"></a><h3>1.1. 242Requirements Language</h3> 243 244<p>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 245 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 246 document are to be interpreted as described in RFC 2119. 247</p> 248<a name="anchor3"></a><br /><hr /> 249<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 250<a name="rfc.section.2"></a><h3>2. 251BCP47 Required Information</h3> 252 253<p>Language tags, as defined by <a class='info' href='#BCP47'>[BCP47]<span> (</span><span class='info'>Davis, M., Ed., “Tags for the Identification of Language (BCP47),” September 2009.</span><span>)</span></a>, are useful for identifying the language of content. They are also used as locale identifiers (or can be mapped to locales) in many operating environments and APIs. However, most such locale identifiers also provide additional "tailorings" or options for specific values within a language, culture, region, or other variation. This extension provides a mechanism for using these additional tailorings within language tags for general interchange. 254</p> 255<p> The maintaining authority for this extension's registry is the Unicode 256 Consortium. Unicode defines common locale data and identifiers for this data: 257</p><table class="full" align="center" border="0" cellpadding="2" cellspacing="2"> 258<col align="left"><col align="left"> 259<tr><th align="left">Item</th><th align="left">Value</th></tr> 260<tr> 261<td align="left">Name</td> 262<td align="left">Unicode Consortium</td> 263</tr> 264<tr> 265<td align="left">Contact Email</td> 266<td align="left">cldr@unicode.org</td> 267</tr> 268<tr> 269<td align="left">Discussion List Email</td> 270<td align="left">cldr-users@unicode.org</td> 271</tr> 272<tr> 273<td align="left">URL Location</td> 274<td align="left">cldr.unicode.org</td> 275</tr> 276<tr> 277<td align="left">Specification</td> 278<td align="left">Unicode Technical Standard #35 Unicode Locale Data Markup Language 279 (LDML), http://unicode.org/reports/tr35/</td> 280</tr> 281<tr> 282<td align="left">Section</td> 283<td align="left">Section 3.2 BCP 47 Tag Conversion</td> 284</tr> 285</table> 286<br clear="all" /> 287 288<p>The specification of extension subtags is provided by Section 3 of <a class='info' href='#LDML'>Unicode 289 Technical Standard #35 Unicode Locale Data Markup Language<span> (</span><span class='info'>Davis, M., “Unicode Technical Standard #35: Locale Data Markup Language (LDML),” December 2007.</span><span>)</span></a> [LDML]. As required by BCP 47, subtags follow the language tag ABNF and 290 other rules for the formation of language tags and subtags, are restricted to the ASCII letters and digits, are not case sensitive, and do not exceed eight characters in length. 291</p> 292<p><a class='info' href='#LDML'>[LDML]<span> (</span><span class='info'>Davis, M., “Unicode Technical Standard #35: Locale Data Markup Language (LDML),” December 2007.</span><span>)</span></a> specifies a canonical 293 representation. LDML is available over the Internet and at no cost, and 294 is available via a royalty-free license at 295 http://unicode.org/copyright.html. LDML is versioned, and each 296 version of LDML is numbered, dated, and stable. Extension subtags, once 297 defined by LDML, are never retracted or change in meaning in a 298 substantial way. 299</p> 300<a name="anchor4"></a><br /><hr /> 301<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 302<a name="rfc.section.2.1"></a><h3>2.1. 303Summary</h3> 304 305<p>The subtags available for use in the 'u' extension consist of a set of attributes, keys, and types. Attributes, keys, types, and their respective meanings are defined in Section 3 (Unicode Language and Locale Identifiers) of <a class='info' href='#LDML'>[LDML]<span> (</span><span class='info'>Davis, M., “Unicode Technical Standard #35: Locale Data Markup Language (LDML),” December 2007.</span><span>)</span></a>. The following is a summary of that definition (for details see Section 3):</p> 306<ul class="text"> 307<li>An 'attribute' is a subtag with a length of three or more characters following the singleton and preceding any 'keyword' sequences. No attributes were defined at the time of this document's publication. 308</li> 309<li>A 'keyword' is a sequence of subtags consisting of a 'key' subtag, followed by zero or more 'type' subtags. Each 'key' MUST be unique within the extension. The order of the 'type' subtags within a 'keyword' is sometimes significant to their interpretation. Note that 'keys' can appear without a subsequent 'type' subtag. 310<blockquote class="text"><dl> 311<dt>A.</dt> 312<dd>A 'key' is a subtag with a length of exactly two characters. Each 'key' is followed by zero or more 'type' subtags. 313</dd> 314<dt>B.</dt> 315<dd>A 'type' is a subtag with a length of three or more characters following a key. 'Type' subtags are specific to a particular 'key' and the order of the 'type' subtags MAY be significant to the interpretation of the 'keyword'. 316</dd> 317</dl></blockquote> 318</li> 319</ul> 320 321<p>For example, the language tag "de-DE-u-attr-co-phonebk" consists of:</p> 322<ul class="text"> 323<li>The base language tag "de-DE" (German as used in Germany), exactly as defined by <a class='info' href='#BCP47'>[BCP47]<span> (</span><span class='info'>Davis, M., Ed., “Tags for the Identification of Language (BCP47),” September 2009.</span><span>)</span></a> using subtags from the IANA Language Subtag Registry. 324</li> 325<li>The singleton 'u', identifying this extension. 326</li> 327<li>The attribute 'attr', which is an example for illustration (no attributes were defined at the time this document was published). 328</li> 329<li>The keyword 'co-phonebk', consisting to the key 'co' (Collation) and the type 'phonebk' (Phonebook collation order). 330</li> 331</ul> 332 333<p>With successive versions of <a class='info' href='#LDML'>[LDML]<span> (</span><span class='info'>Davis, M., “Unicode Technical Standard #35: Locale Data Markup Language (LDML),” December 2007.</span><span>)</span></a>, additional attributes, keys, and types MAY be defined. Once defined, attributes, keys, and types will never be removed. Machine-readable files listing the valid attributes, keys, and types are available in the CLDR repository for each version. For example, for version 1.7.2, the files are located at <a href='http://unicode.org/repos/cldr/tags/release-1-7-2/common/bcp47/'>http://unicode.org/repos/cldr/tags/release-1-7-2/common/bcp47/</a>. These also can contain aliases which were used in previous versions of <a class='info' href='#LDML'>[LDML]<span> (</span><span class='info'>Davis, M., “Unicode Technical Standard #35: Locale Data Markup Language (LDML),” December 2007.</span><span>)</span></a>. 334</p> 335<a name="canonicalization"></a><br /><hr /> 336<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 337<a name="rfc.section.2.1.1"></a><h3>2.1.1. 338Canonicalization</h3> 339 340<p>As required by <a class='info' href='#BCP47'>[BCP47]<span> (</span><span class='info'>Davis, M., Ed., “Tags for the Identification of Language (BCP47),” September 2009.</span><span>)</span></a>, case is not significant. The canonical form for all subtags in the extension is lowercase. The canonical order of attributes is in <a class='info' href='#US-ASCII'>[US‑ASCII]<span> (</span><span class='info'>International Organization for Standardization, “ISO/IEC 646:1991, Information technology -- ISO 7-bit coded character set for information interchange.,” 1991.</span><span>)</span></a> order (that is, numbers before letters, with letters sorted as lowercase US-ASCII code points). The canonical order of keywords is in <a class='info' href='#US-ASCII'>[US‑ASCII]<span> (</span><span class='info'>International Organization for Standardization, “ISO/IEC 646:1991, Information technology -- ISO 7-bit coded character set for information interchange.,” 1991.</span><span>)</span></a> order by key. The order of subtags within a keyword is significant; the meaning of this extension is altered if those subtags are rearranged. Thus, the canonical form of the extension never reorders the subtags within a keyword. 341</p> 342<a name="regform"></a><br /><hr /> 343<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 344<a name="rfc.section.2.2"></a><h3>2.2. 345Registration Form</h3> 346 347<p>Per <a class='info' href='#RFC5646'>[RFC5646]<span> (</span><span class='info'>Phillips, A. and M. Davis, “Tags for Identifying Languages,” September 2009.</span><span>)</span></a>, Section 3.7: 348</p><div style='display: table; width: 0; margin-left: 3em; margin-right: auto'><pre>%% 349Identifier: u 350Description: Unicode Locale 351Comments: Subtags for the identification of language and cultural 352 variations. Used to set behavior in locale APIs. 353Added: 2009-mm-dd 354RFC: [TBD] 355Authority: Unicode Consortium 356Contact_Email: cldr@unicode.org 357Mailing_List: cldr-users@unicode.org 358URL: http://cldr.unicode.org 359%%</pre></div> 360<a name="Acknowledgements"></a><br /><hr /> 361<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 362<a name="rfc.section.3"></a><h3>3. 363Acknowledgements</h3> 364 365<p>Thanks to John Emmons and the rest of the Unicode 366 CLDR Technical Committee for their work in developing the BCP 47 subtags 367 for LDML. 368</p> 369<a name="IANA"></a><br /><hr /> 370<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 371<a name="rfc.section.4"></a><h3>4. 372IANA Considerations</h3> 373 374<p>This document will require IANA to insert the record in <a class='info' href='#regform'>Section 2.2<span> (</span><span class='info'>Registration Form</span><span>)</span></a> into the Language Extensions Registry, according to 375 Section 3.7. Extensions and the Extensions Registry of "Tags for 376 Identifying Languages" in <a class='info' href='#BCP47'>[BCP47]<span> (</span><span class='info'>Davis, M., Ed., “Tags for the Identification of Language (BCP47),” September 2009.</span><span>)</span></a>. There might be occasional maintenance of this record. This document does not require IANA to create or maintain a new registry or otherwise impact IANA. 377</p> 378<a name="Security"></a><br /><hr /> 379<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 380<a name="rfc.section.5"></a><h3>5. 381Security Considerations</h3> 382 383<p>The security considerations for this extension are the same as those 384 for <a class='info' href='#RFC5646'>[RFC5646]<span> (</span><span class='info'>Phillips, A. and M. Davis, “Tags for Identifying Languages,” September 2009.</span><span>)</span></a> (or its successors). See Section 6. Security Considerations 385 of <a class='info' href='#RFC5646'>[RFC5646]<span> (</span><span class='info'>Phillips, A. and M. Davis, “Tags for Identifying Languages,” September 2009.</span><span>)</span></a>. 386</p> 387<a name="rfc.references"></a><br /><hr /> 388<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 389<a name="rfc.section.6"></a><h3>6. 390References</h3> 391 392<a name="rfc.references1"></a><br /><hr /> 393<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 394<h3>6.1. Normative References</h3> 395<table width="99%" border="0"> 396<tr><td class="author-text" valign="top"><a name="BCP47">[BCP47]</a></td> 397<td class="author-text">Davis, M., Ed., “Tags for the Identification of Language (BCP47),” September 2009.</td></tr> 398<tr><td class="author-text" valign="top"><a name="LDML">[LDML]</a></td> 399<td class="author-text">Davis, M., “<a href="http://www.unicode.org/reports/tr35/">Unicode Technical Standard #35: Locale Data Markup Language (LDML)</a>,” December 2007.</td></tr> 400<tr><td class="author-text" valign="top"><a name="RFC5646">[RFC5646]</a></td> 401<td class="author-text">Phillips, A. and M. Davis, “<a href="http://tools.ietf.org/html/rfc5646">Tags for Identifying Languages</a>,” BCP 47, RFC 5646, September 2009 (<a href="ftp://ftp.isi.edu/in-notes/rfc5646.txt">TXT</a>).</td></tr> 402<tr><td class="author-text" valign="top"><a name="US-ASCII">[US-ASCII]</a></td> 403<td class="author-text">International Organization for Standardization, “ISO/IEC 646:1991, Information technology -- ISO 7-bit coded character set for information interchange.,” 1991.</td></tr> 404</table> 405 406<a name="rfc.references2"></a><br /><hr /> 407<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 408<h3>6.2. Informative References</h3> 409<table width="99%" border="0"> 410<tr><td class="author-text" valign="top"><a name="ldml-registry">[ldml-registry]</a></td> 411<td class="author-text">“Registry for Common Locale Data Repository tag elements,” September 2009.</td></tr> 412</table> 413 414<a name="rfc.authors"></a><br /><hr /> 415<table summary="layout" cellpadding="0" cellspacing="2" class="TOCbug" align="right"><tr><td class="TOCbug"><a href="#toc"> TOC </a></td></tr></table> 416<h3>Authors' Addresses</h3> 417<table width="99%" border="0" cellpadding="0" cellspacing="0"> 418<tr><td class="author-text"> </td> 419<td class="author-text">Mark Davis</td></tr> 420<tr><td class="author-text"> </td> 421<td class="author-text">Google</td></tr> 422<tr><td class="author" align="right">Email: </td> 423<td class="author-text"><a href="mailto:mark@macchiato.com">mark@macchiato.com</a></td></tr> 424<tr cellpadding="3"><td> </td><td> </td></tr> 425<tr><td class="author-text"> </td> 426<td class="author-text">Addison Phillips</td></tr> 427<tr><td class="author-text"> </td> 428<td class="author-text">Lab126</td></tr> 429<tr><td class="author" align="right">Email: </td> 430<td class="author-text"><a href="mailto:addison@inter-locale.com">addison@inter-locale.com</a></td></tr> 431<tr cellpadding="3"><td> </td><td> </td></tr> 432<tr><td class="author-text"> </td> 433<td class="author-text">Yoshito Umaoka</td></tr> 434<tr><td class="author-text"> </td> 435<td class="author-text">IBM</td></tr> 436<tr><td class="author" align="right">Email: </td> 437<td class="author-text"><a href="mailto:yoshito_umaoka@us.ibm.com">yoshito_umaoka@us.ibm.com</a></td></tr> 438</table> 439</body></html> 440 441