1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> 2<html> 3<head> 4 5 6 7 8 9 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> 10 11 12 13 14 15 <meta http-equiv="Content-Language" content="en-us"> 16 17 18 19 20 21 <meta name="VI60_defaultClientScript" content="JavaScript"> 22 23 24 25 26 27 <meta name="GENERATOR" content="Microsoft FrontPage 6.0"> 28 29 30 31 32 33 <meta name="keywords" content="Unicode, common locale data repository"> 34 35 36 37 38 39 <meta name="ProgId" content="FrontPage.Editor.Document"> 40 41 42 43 44 45 46 47 48 <title>Unicode CLDR Process</title> 49 <link rel="stylesheet" type="text/css" href="http://www.unicode.org/webscripts/standard_styles.css"> 50</head> 51 52 53<body style="color: rgb(51, 0, 0);"> 54 55 56 57<table border="0" cellpadding="0" cellspacing="0" width="100%"> 58 59 60 61 <tbody> 62 63 64 65 <tr> 66 67 68 69 <td colspan="2"> 70 71 72 <table border="0" cellpadding="0" cellspacing="0" width="100%"> 73 74 75 76 <tbody> 77 78 79 80 <tr> 81 82 83 84 <td class="icon"><a href="http://www.unicode.org/"> <img src="http://www.unicode.org/webscripts/logo60s2.gif" alt="[Unicode]" align="middle" border="0" height="33" width="34"></a> 85 <a class="bar" href="index.html"><font size="3">Common Locale Data Repository</font></a></td> 86 87 88 89 <td class="bar"><a href="http://www.unicode.org" class="bar">Home</a> 90| <a href="http://www.unicode.org/sitemap/" class="bar">Site 91Map</a> | <a href="http://www.unicode.org/search/" class="bar">Search</a></td> 92 93 94 95 </tr> 96 97 98 99 100 101 </tbody> 102 103 104 </table> 105 106 107 108 </td> 109 110 111 112 </tr> 113 114 115 116 <tr> 117 118 119 120 <td colspan="2" class="gray"> </td> 121 122 123 124 </tr> 125 126 127 128 <tr> 129 130 131 132 <td class="navCol" valign="top" width="25%"> 133 134 135 <table class="navColTable" border="0" cellpadding="0" cellspacing="4" width="100%"> 136 137 138 139 <tbody> 140 141 142 143 <tr> 144 145 146 147 <td class="navColTitle" colspan="2">Contents</td> 148 149 150 151 </tr> 152 153 154 155 <tr> 156 157 158 159 <td class="navColCell" colspan="2" valign="top"><a href="#introduction">Introduction</a></td> 160 161 162 163 </tr> 164 165 166 167 <tr> 168 169 170 171 <td class="navColCell" colspan="2" valign="top"><a href="#specification_changes">Specification 172Changes</a></td> 173 174 175 176 </tr> 177 178 179 180 <tr> 181 182 183 184 <td class="navColCell" colspan="2" valign="top"><a href="#data_vetting_process">Data 185Submission and Vetting Process</a></td> 186 187 188 189 </tr> 190 191 192 193 <tr> 194 195 196 197 <td class="navColCell" valign="top" width="1em"> </td> 198 199 200 201 <td class="navColCell" valign="top"><a href="#resolution_procedure">Resolution Procedure</a></td> 202 203 204 205 </tr> 206 207 208 209 <tr> 210 211 212 213 <td class="navColCell" valign="top"> </td> 214 215 216 217 <td class="navColCell" valign="top"><a href="#Voting_Process">Voting Process</a></td> 218 219 220 221 </tr> 222 223 224 225 <tr> 226 227 228 229 <td class="navColCell" valign="top"> </td> 230 231 232 233 <td class="navColCell" valign="top"><a href="#prioritization">Prioritization</a></td> 234 235 236 237 </tr> 238 239 240 241 <tr> 242 243 244 245 <td class="navColCell" valign="top"> </td> 246 247 248 249 <td class="navColCell" valign="top"><a href="#Dot-Dot_Releases">Dot-Dot Releases</a></td> 250 251 252 253 </tr> 254 255 256 257 <tr> 258 259 260 261 <td class="navColCell" colspan="2" valign="top"><a href="#public_feedback">Public 262Feedback</a></td> 263 264 265 266 </tr> 267 268 269 270 <tr> 271 272 273 274 <td class="navColCell" colspan="2" valign="top"><a href="#data_release_process">Data 275Release Process</a></td> 276 277 278 279 </tr> 280 281 282 283 <tr> 284 285 286 287 <td class="navColCell" valign="top"> </td> 288 289 290 291 <td class="navColCell" valign="top"><a href="#version_numbering">Version Numbering</a></td> 292 293 294 295 </tr> 296 297 298 299 <tr> 300 301 302 303 <td class="navColCell" valign="top"> </td> 304 305 306 307 <td class="navColCell" valign="top"><a href="#release_schedule">Release Schedule</a></td> 308 309 310 311 </tr> 312 313 314 315 <tr> 316 317 318 319 <td class="navColCell" colspan="2" valign="top"><a href="#meetings">Meetings and 320Communication</a></td> 321 322 323 324 </tr> 325 326 327 328 <tr> 329 330 331 332 <td class="navColCell" colspan="2" valign="top"><a href="#officers">Officers</a></td> 333 334 335 336 </tr> 337 338 339 340 <tr> 341 342 343 344 <td class="navColTitle" colspan="2">Unicode 345CLDR</td> 346 347 348 349 </tr> 350 351 352 353 <tr> 354 355 356 357 <td class="navColCell" colspan="2" valign="top"><a href="index.html">CLDR Project</a></td> 358 359 360 361 </tr> 362 363 364 365 <tr> 366 367 368 369 <td class="navColCell" colspan="2" valign="top"><a href="repository_access.html">CLDR 370Releases (Downloads)</a></td> 371 372 373 374 </tr> 375 376 377 378 <tr> 379 380 381 382 <td class="navColCell" colspan="2" valign="top"><a href="survey_tool.html">CLDR 383Survey Tool</a></td> 384 385 386 387 </tr> 388 389 390 391 <tr> 392 393 394 395 <td class="navColCell" colspan="2" valign="top"><a href="filing_bug_reports.html">CLDR 396Bug Reports</a></td> 397 398 399 400 </tr> 401 402 403 404 <tr> 405 406 407 408 <td class="navColCell" colspan="2" valign="top"><a href="comparison_charts.html">CLDR 409Charts</a></td> 410 411 412 413 </tr> 414 415 416 417 <tr> 418 419 420 421 <td class="navColCell" colspan="2" valign="top"><a href="process.html">CLDR Process</a></td> 422 423 424 425 </tr> 426 427 428 429 <tr> 430 431 432 433 <td class="navColCell" colspan="2" valign="top"><a href="http://www.unicode.org/reports/tr35/">UTS #35: Locale 434Data Markup Language (LDML)</a></td> 435 436 437 438 </tr> 439 440 441 442 <tr> 443 444 445 446 <td class="navColTitle" colspan="2">Related 447Links</td> 448 449 450 451 </tr> 452 453 454 455 <tr> 456 457 458 459 <td class="navColCell" colspan="2" valign="top">Join the <a href="http://www.unicode.org/consortium/consort.html">Unicode 460Consortium</a></td> 461 462 463 464 </tr> 465 466 467 468 <tr> 469 470 471 472 <td class="navColCell" colspan="2" valign="top"><a href="http://www.unicode.org/reports/">Unicode 473Technical Reports</a></td> 474 475 476 477 </tr> 478 479 480 481 <tr> 482 483 484 485 <td class="navColCell" colspan="2" valign="top"><a href="http://www.unicode.org/faq/reports_process.html">Technical 486Reports Development and Maintenance Process</a></td> 487 488 489 490 </tr> 491 492 493 494 <tr> 495 496 497 498 <td class="navColCell" colspan="2" valign="top"><a href="http://www.unicode.org/consortium/utc.html">Unicode 499Technical Committee</a></td> 500 501 502 503 </tr> 504 505 506 507 <tr> 508 509 510 511 <td class="navColCell" colspan="2" valign="top"><a href="http://www.unicode.org/versions/">Versions 512of the Unicode Standard</a></td> 513 514 515 516 </tr> 517 518 519 520 <tr> 521 522 523 524 <td class="navColTitle" colspan="2">Other 525Publications</td> 526 527 528 529 </tr> 530 531 532 533 <tr> 534 535 536 537 <td class="navColCell" colspan="2" valign="top"><a href="http://www.unicode.org/standard/standard.html">The 538Unicode Standard</a></td> 539 540 541 542 </tr> 543 544 545 546 <tr> 547 548 549 550 <td class="navColCell" colspan="2" valign="top"><a href="http://www.unicode.org/notes/">Unicode 551Technical Notes</a></td> 552 553 554 555 </tr> 556 557 558 559 560 561 </tbody> 562 563 564 </table> 565 566 567 568<!-- BEGIN CONTENTS --></td> 569 570 571 572 <td> 573 574 575 <table> 576 577 578 579 <tbody> 580 581 582 583 <tr> 584 585 586 587 <td class="contents" valign="top"> 588 589 590 <div class="body"> 591 592 593 <h1>Unicode CLDR Technical Committee Process</h1> 594 595 596 597 598 599 <h2><a name="introduction"></a>1. 600Introduction</h2> 601 602 603 604 605 606 <p>This document describes the Unicode CLDR Technical 607Committee, and its process for data collection, resolution, public 608feedback and release. The process is designed to be light-weight: in 609particular, the meetings are frequent, short, and informal. Most of the 610work is by email or phone, with a database recording requested changes 611in data.</p> 612 613 614 615 616 617 <p>When gathering data for a region and language, it 618is important to have multiple sources for that data to produce the most 619widely acceptable data. Initial versions of data were based on the best 620available sources, but CLDR data will be modified and improved, in 621successive versions, by more input from the contributors inside and 622outside of the Unicode Consortium.</p> 623 624 625 626 627 628 <p>It is important to note that CLDR is a Repository, 629not a Registration. That is, contributors should not expect that their 630contributions will simply be adopted into the repository; instead, it 631will be vetted against the best available information.</p> 632 633 634 635 636 637 <p>All inputs are open, and gathered via the <a href="survey_tool.html">CLDR Survey Tool</a> or 638recorded in a bug/feature request database (<a href="filing_bug_reports.html">CLDR Bug Reports</a>). 639Changes in response to requests in the database may be entered into the 640repository snapshot over time by the maintainers of the repository, but 641the final approval of the release of any version of CLDR is up to the 642decision of the CLDR Technical Committee.</p> 643 644 645 646 647 648 <p>For more information on the formal procedures for 649the Unicode CLDR Technical Committee, see the <a href="http://www.unicode.org/consortium/tc-procedures.html">Technical 650Committee Procedures for the Unicode Consortium</a>.</p> 651 652 653 654 655 656 <h2><a name="specification_changes"></a>2. 657Specification Changes</h2> 658 659 660 661 662 663 <p>The <a href="http://www.unicode.org/reports/tr35/">UTS #35: Locale 664Data Markup Language (LDML)</a> specification may be changed to 665add structure for new kinds of data or other features. Requests for 666changes are entered in the bug/feature request database (<a href="filing_bug_reports.html">CLDR Bug Reports</a>).</p> 667 668 669 670 671 672 <p>Structural changes are always 673backwards-compatible. That is, previous files will continue to work. 674Deprecated elements remain and can be used, although their usage is 675strongly discouraged.</p> 676 677 678 679 680 681 <p>There is a standing policy for structural changes 682that require non-trivial code for proper implementation, such as time 683zone fallback or alias mechanisms. These require the existence of at 684least a prototype implementation that demonstrates correct function 685according to the proposed specification.</p> 686 687 688 689 690 691 <h2><a name="data_vetting_process"></a>3. 692Data Submission and Vetting Process</h2> 693 694 695 696 697 698 <p>Once data for a country and language has been 699received, the data from the different sources will be compared to show 700agreements and differences. Initial data contributions are normally 701marked as draft; this may be changed once the data is 702vetted.</p> 703 704 705 706 707 708 <p>Note that there are two types of data in the 709repository:</p> 710 711 712 713 714 715 <ol> 716 717 <li><b>Common Data: </b>The contents 718is decided upon by the CLDR Technical Committee, following its 719procedures and this process.</li> 720 721 <li><b>Comparison data: </b>The 722contributor can be an individual or an organization. Data is normally 723gathered by calling public APIs, to ensure that the data matches what 724is actually in use. The data is only for comparison, and will not be 725changed except where necessary to update the data to match the external 726source. The only requirement is that all changed data be versioned, and 727the Version Numbering Scheme be used.</li> 728 729 730 </ol> 731 732 733 734 735 736 <p>Contributors are encouraged to use local language 737and country contacts, inside and outside their organization, to help 738vet current common data and any new proposals for addition or amendment 739of common data. In particular, national standards organizations are 740encouraged to be involved in the data vetting process.</p> 741 742 743 744 745 746 <p>For CLDR to add a new language just requires that 747the proposer to commit to providing at least the minimal localization 748(exemplar characters, months, days, date/time formats, translations for 749a few countries, languages, currencies, etc.). <span style="font-style: italic;">The exemplar characters, 750however, are required before the new locale can be added: see also <a href="filing_bug_reports.html#Exemplar_Characters">Exemplar 751Character Sources</a>. </span>The new locale then becomes 752available for additional translations and vetting during the next 753review cycle.</p> 754 755 756 757 758 759 <h3>3.1 <a name="resolution_procedure">Resolution 760Procedure</a></h3> 761 762 763 764 765 766 <p>The following procedure is used when resolving 767differences in submitted data. At the end, for each field a single 768value will be chosen as optimal, while the others will have an <i>alt=proposed</i> 769attribute. The <i>draft</i> attribute on all the values 770will be set to one of 4 states:</p> 771 772 773 774 775 776 <ul> 777 778 779 780 <li><i><span style="font-weight: 700;">unconfirmed</span></i></li> 781 782 783 784 <li><b><i>provisional</i></b></li> 785 786 787 788 <li><b><i>contributed (= minimally approved)</i></b></li> 789 790 791 792 <li><i><b>approved</b> 793(equivalent to an absent draft attribute)</i></li> 794 795 796 797 798 799 </ul> 800 801 802 803 804 805 <p>Implementations may choose the level at which they 806wish to accept data. They may choose to accept even <b>unconfirmed</b> 807data, especially if there is no translated alternative. Approved data 808is approved by the Technical Committee, as described by the resolution 809process below. This does not mean that the data is guaranteed to be 810error-free -- this is simply the best judgment of the committee 811according to the process.</p> 812 813 814 815 816 817 <h4>User Levels</h4> 818 819 820 821 822 823 <p>There are multiple levels of access and control:</p> 824 825 826 <table style="text-align: left;" border="1" cellpadding="1" cellspacing="0"> 827 828 829 830 <tbody> 831 832 833 834 <tr> 835 836 837 838 <th style="font-weight: bold;">Vetter Level</th> 839 840 841 842 <td style="font-weight: bold; text-align: center;">Vote</td> 843 844 <th style="text-align: left; font-weight: bold;">Description</th> 845 846 847 848 </tr> 849 850 851 852 <tr> 853 854 855 856 <td style="font-style: italic;"><i>Committee Vetters</i></td> 857 858 859 860 <td style="text-align: center;">8</td> 861 862 <td style="text-align: left;"> 863 864 <ul> 865 866 <li>Can vet and submit data for all locales </li> 867 868 <li>Can manage users in their organization</li> 869 870 <li>Can see the email addresses for all vetters</li> 871 872 <li><i>Technical Committee 873(TC) members</i></li> 874 875 876 </ul> 877 878 </td> 879 880 881 882 </tr> 883 884 885 886 <tr> 887 888 889 890 <td style="font-style: italic;"><i>Expert Vetters</i></td> 891 892 893 894 <td style="text-align: center;">8</td> 895 896 <td style="text-align: left;"> 897 898 <ul> 899 900 <li>Can vet and submit data for a particular set of 901locales</li> 902 903 <li>Cannot manage other users.</li> 904 905 <li>Can see the email addresses for submitted data 906in their locales.</li> 907 908 909 </ul> 910 911 </td> 912 913 914 915 </tr> 916 917 918 919 <tr> 920 921 <td><i>Regular Vetters </i></td> 922 923 <td style="text-align: center;">4</td> 924 925 <td> 926 927 <ul> 928 929 <li>Can vet and submit data for a particular set of 930locales</li> 931 932 <li>Cannot manage other users.</li> 933 934 <li>Can see the email addresses for submitted data 935in their locales.</li> 936 937 938 </ul> 939 940 </td> 941 942 </tr> 943 944 <tr> 945 946 947 948 <td style="font-style: italic;"><i>Guest Vetters</i></td> 949 950 951 952 <td style="text-align: center;">1</td> 953 954 <td style="text-align: left;"> 955 956 <ul> 957 958 <li>Can vet and submit data for a particular set of 959locales</li> 960 961 <li>Cannot manage other users. </li> 962 963 <li>Cannot see email addresses.</li> 964 965 966 </ul> 967 968 </td> 969 970 971 972 </tr> 973 974 <tr> 975 976 <td><span style="font-style: italic;">Locked Vetters</span></td> 977 978 <td style="text-align: center;">0</td> 979 980 <td> 981 982 <ul> 983 984 <li>If a user is locked or removed, then his/er 985vote is zero.</li> 986 987 988 </ul> 989 990 </td> 991 992 </tr> 993 994 995 996 997 998 999 1000 </tbody> 1001 1002 1003 </table> 1004 1005 <i> </i> 1006 1007 1008 1009 <ul> 1010 1011 1012 </ul> 1013 1014 1015 1016 1017 1018 1019 1020 <ul> 1021 1022 1023 </ul> 1024 1025 1026 1027 1028 1029 1030 1031 <ul> 1032 1033 1034 </ul> 1035 1036 1037 1038 1039 1040 <p>These levels are decided by the technical committee and the TC representative 1041for the respective organizations. </p> 1042 1043 1044 1045 1046 1047 <ul> 1048 1049 1050 1051 <li>Unicode TC members (full/institutional/supporting) 1052can assign its users to Regular or Guest level, and with approval of the TC, users at the Expert level. </li> 1053 1054 1055 1056 <li>Liaison or associate members can assign to Guest, or to other levels with approval of the TC. 1057 1058 1059 <ul> 1060 1061 1062 1063 <li>The liaison/associate member him/erself 1064gets TC status in order to manage users, but gets a Guest status in 1065terms of voting, unless the committee approves a higher level.</li> 1066 1067 1068 1069 1070 1071 </ul> 1072 1073 1074 1075 </li> 1076 1077 1078 1079 <li>Users assigned to "<a href="http://unicode.org">unicode.org</a>" are 1080normally assigned as Guest, but the committee can assign a different 1081level.</li> 1082 1083 1084 1085 1086 1087 </ul> 1088 1089 1090 1091 1092 1093 <h4><a name="Voting_Process"></a>Voting Process</h4> 1094 1095 1096 1097 1098 1099 <ul> 1100 1101 1102 1103 <li>Each user gets one vote on each value, but the <i>strength</i> 1104of the vote varies according to the user level according to the table above. 1105 1106 1107 </li> 1108 1109 1110 1111 <li>All values with survey tool errors get <span style="font-style: italic;">zero</span> votes 1112 1113 1114 <ul> 1115 1116 1117 1118 <li>For example, a date pattern of "14. 1119september" instead of "dd MMM".</li> 1120 1121 1122 1123 <li>They cannot be voted for, and show a 1124visible error.</li> 1125 1126 1127 1128 <li>Collision errors are an exception. They get normal votes, but are handled below.</li> 1129 1130 1131 1132 1133 1134 </ul> 1135 1136 1137 1138 </li> 1139 1140 1141 1142 <li>For each value, each organization gets a vote 1143based on the <i>maximum</i> (not cumulative) strength of 1144the votes of its users who voted on that item. 1145 1146 1147 <ul> 1148 1149 1150 1151 <li>That is, even if an organization has 10 1152Vetters voting for an value, if the highest level is regular vetter, then the vote count attributed to the 1153organization as a whole is 4.</li> 1154 1155 1156 1157 1158 1159 </ul> 1160 1161 1162 1163 </li> 1164 1165 1166 1167 <li>If there is a dispute (votes for different 1168values) within an organization, then the majority vote for that 1169organization is chosen. If there is a tie, then no vote is counted for 1170the organization.</li> 1171 1172 1173 1174 <li>Batch data (marked with x999, for example) gets 1175a status based on committee decision.</li> 1176 1177 1178 1179 1180 1181 </ul> 1182 1183 1184 1185 1186 1187 <p style="font-style: italic;">All fields are then assessed as follows:</p> 1188 1189 1190 1191 1192 1193 <h4><span style="font-weight: bold;">Optimal 1194Field Value</span></h4> 1195 1196 1197 1198 1199 1200 <p>For each release, there is one optimal field value 1201determined by the following:</p> 1202 1203 1204 1205 1206 1207 <ul> 1208 1209 1210 1211 <li>Add up the votes for each value from each 1212organization.</li> 1213 1214 1215 1216 <li>Out of all the possible alternative values for 1217a given field, pick the one with the most votes, the <span style="font-style: italic;">optimal value</span>.</li> 1218 1219 1220 1221 <li>If there was a tie, pick the least one (in UCA 1222order).</li> 1223 1224 1225 1226 1227 1228 </ul> 1229 1230 1231 1232 1233 1234 <h4><span style="font-weight: bold;">Draft 1235Status of Optimal Field Value</span></h4> 1236 1237 1238 1239 1240 1241 <ul> 1242 1243 1244 1245 1246 1247 </ul> 1248 1249 1250 1251 1252 1253 <ol> 1254 1255 1256 1257 <li>Let <span style="font-weight: bold;">O</span> 1258be the optimal value's vote<span style="font-weight: bold;"></span>, 1259 <span style="font-weight: bold;">N</span> 1260be the vote of the next best value, and <font size="3"><span style="font-weight: bold;">G</span> be the number of 1261organizations that voted for the optimal value</font>.</li> 1262 1263 1264 1265 <li>Assign the draft status according to the first 1266of the conditions below that applies:<font size="3"><br> 1267 1268 1269 1270 </font> 1271 1272 1273 <table style="text-align: left;" border="1" cellpadding="1" cellspacing="0"> 1274 1275 1276 1277 <tbody> 1278 1279 1280 1281 <tr> 1282 1283 1284 1285 <th>Resulting Draft Status</th> 1286 1287 1288 1289 <th style="text-align: center;">Condition</th> 1290 1291 1292 1293 </tr> 1294 1295 1296 1297 <tr> 1298 1299 1300 1301 <td style="font-style: italic;"><span style="font-weight: 400;"></span>approved</td> 1302 1303 1304 1305 <td style="text-align: center;"><span style="font-weight: 400;">O <font face="Times New Roman">≥</font> 13068 and </span><span style="font-weight: 400;">O 1307 <font face="Times New Roman">≥</font> 13082<font face="Arial">×</font>N </span></td> 1309 1310 1311 1312 </tr> 1313 1314 1315 1316 <tr> 1317 1318 1319 1320 <td style="font-style: italic;">contributed</td> 1321 1322 1323 1324 <td style="text-align: center;"><span style="color: black;">O ≥ 13254 and O > N</span><br style="color: black;"> 1326 1327 1328 1329 <span style="font-weight: bold; font-style: italic; color: black;">OR</span><br> 1330 1331 1332 1333O ≥ 2 and O > N and G ≥ 2</td> 1334 1335 1336 1337 </tr> 1338 1339 1340 1341 <tr> 1342 1343 1344 1345 <td style="font-style: italic;">provisional</td> 1346 1347 1348 1349 <td style="text-align: center;">O <font face="Times New Roman">≥</font> 2 and O <span style="font-weight: 400;"> <font face="Times New Roman">≥</font></span> 1350N </td> 1351 1352 1353 1354 </tr> 1355 1356 1357 1358 <tr> 1359 1360 1361 1362 <td style="font-style: italic;">unconfirmed</td> 1363 1364 1365 1366 <td style="text-align: center;"><span style="font-style: italic;">otherwise</span></td> 1367 1368 1369 1370 </tr> 1371 1372 1373 1374 1375 1376 </tbody> 1377 1378 1379 </table> 1380 1381 1382 1383 </li> 1384 1385 1386 1387 <li style="color: black;">If the draft status of the previously released 1388value is better than the new draft status, then no change is made. 1389Otherwise, the optimal value and its draft status are made part of the 1390new release.</li> 1391 1392 1393 1394 1395 1396 <ul> 1397 1398 1399 1400 <li>For example, if the new optimal value does 1401not have the status of <b>approved</b>, and the previous 1402release had an <span style="font-weight: bold;">approved </span>value 1403(one that does not have an error and is not a fallback), then that 1404previously-released value stays <b>approved</b> and 1405replaces the optimal value in the following steps.</li> 1406 1407 1408 1409 1410 1411 </ul> 1412 1413 1414 1415 <li>If there was an <i>alt=proposed</i> 1416on the optimal value, the <i>alt=proposed</i> is removed.</li> 1417 1418 1419 1420 1421 1422 </ol> 1423 1424 1425 1426 1427 1428 <ul> 1429 1430 1431 1432 1433 1434 </ul> 1435 1436 1437 1438 1439 1440 <h4>Further Processing</h4> 1441 1442 <br> 1443 1444 1445 <p>After the optimal value is chosen:</p> 1446 1447 1448 1449 1450 1451 <ul> 1452 1453 1454 1455 <li>Collisions errors are resolved by retaining one of the values and 1456removing the other(s).</li> 1457 1458 1459 <ul> 1460 1461 <li>The choice is based 1462on the judgment of the committee, typically according to which field is most commonly used. 1463When an item is removed, an alternate may then become the new optimal 1464value.</li> 1465 1466 1467 </ul> 1468 1469 <li>All other values with errors are removed.</li> 1470 1471 1472 1473 <li>Non-optimal values are handled as follows:</li> 1474 1475 1476 <ul> 1477 1478 <li>Those with no votes are removed.</li> 1479 1480 <li>Those with votes are marked with <i>alt=proposed 1481 </i>and given the draft status:<span style="font-weight: bold;"> unconfirmed</span></li> 1482 1483 1484 </ul> 1485 1486 1487 1488 1489 1490 </ul> 1491 1492 1493 1494 1495 1496 <p>If a locale does not have minimal data (at least 1497at a provisional level), then it may be excluded from the release. 1498Where this is done, it may be restored to the repository for the next 1499submission cycle.</p> 1500 1501 1502 <p><span style="font-weight: bold;">Note: </span>Starting 1503with CLDR 1.7, we are planning to save votes across releases, for any 1504active (unlocked) voters. However, where there are English changes, old 1505votes will be discarded.</p> 1506 1507 1508 1509 1510 1511 <p>This process can be fine-tuned by the Technical 1512Committee as needed, to resolve any problems that turn up. A committee 1513decision can also override any of the above process for any specific 1514values.</p> 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 <p>For 1525more information see the key links in <a href="survey_tool.html">CLDR Survey Tool</a> (especially the Vetting Phase).<br> 1526 1527 <span style="font-weight: 700;"></span></p> 1528 1529 1530 <p><span style="font-weight: 700;">Notes:</span></p> 1531 1532 1533 1534 1535 1536 <ul> 1537 1538 1539 1540 <li>If data has a formal problem, it can be fixed 1541directly (in CVS) without going through the above process. Examples 1542include: 1543 1544 1545 <ul> 1546 1547 1548 1549 <li>syntactic problems in pattern, extra 1550trailing spaces, inconsistent decimals, mechanical sweeps to change 1551attributes, translatable characters not quoted in patterns, changing ' 1552(punctuation mark) to curly apostrophe or s-cedilla to s-comma-below, 1553removing disallowed exemplar characters (non-letter, number, mark, 1554uppercase when there is a lowercase).</li> 1555 1556 1557 1558 <li>These are changed in-place, without 1559changing the draft status.</li> 1560 1561 1562 1563 1564 1565 </ul> 1566 1567 1568 1569 </li> 1570 1571 1572 1573 <li>Linguistically-sensitive data should always go 1574through the survey tool. Examples include: 1575 1576 1577 <ul> 1578 1579 1580 1581 <li>names of months, territories, number 1582formats, changing ASCII apostrophe to U+02BC modifier letter apostrophe 1583or U+02BB modifier letter turned comma, or U+02BD modifier letter 1584reversed comma, adding/removing normal exemplar characters.</li> 1585 1586 1587 1588 1589 1590 </ul> 1591 1592 1593 1594 </li> 1595 1596 1597 1598 <li>The TC committee can authorize bulk submissions 1599of new data directly (CVS), with all new data marked 1600draft="unconfirmed" (or other status decided by the committee), but 1601only where the data passes the CheckCLDR console tests.</li> 1602 1603 1604 1605 <li>The survey tool does not currently handle all 1606CLDR data. For data it doesn't cover, the regular bug system is used to 1607submit new data or ask for revisions of this data. In particular: 1608 1609 1610 <ul> 1611 1612 1613 1614 <li>Collation, transforms, or text 1615segmentation, which are more complex. 1616 1617 1618 <ul> 1619 1620 1621 1622 <li>For collation data, see the comparison 1623charts at <a href="http://www.unicode.org/cldr/comparison_charts.html">http://www.unicode.org/cldr/comparison_charts.html</a> 1624or the XML data at <a href="http://unicode.org/cldr/data/common/collation/">http://unicode.org/cldr/data/common/collation/</a> 1625 </li> 1626 1627 1628 1629 <li>For transforms, see the XML data at <a href="http://unicode.org/cldr/data/common/transforms/">http://unicode.org/cldr/data/common/transforms/</a> 1630 </li> 1631 1632 1633 1634 1635 1636 </ul> 1637 1638 1639 1640 </li> 1641 1642 1643 1644 <li>Non-linguistic locale data: 1645 1646 1647 <ul> 1648 1649 1650 1651 <li>XML data: <a href="http://unicode.org/cldr/data/common/supplemental/">http://unicode.org/cldr/data/common/supplemental/</a> 1652 </li> 1653 1654 1655 1656 <li>HTML view: <a href="http://www.unicode.org/cldr/data/diff/supplemental/supplemental.html">http://www.unicode.org/cldr/data/diff/supplemental/supplemental.html</a> 1657 </li> 1658 1659 1660 1661 1662 1663 </ul> 1664 1665 1666 1667 </li> 1668 1669 1670 1671 1672 1673 </ul> 1674 1675 1676 1677 </li> 1678 1679 1680 1681 1682 1683 </ul> 1684 1685 1686 <h3>3.3 <a name="prioritization">Prioritization</a></h3> 1687 1688 1689 1690 1691 1692 <p>There may be conflicting common practices or 1693standards for a given country and language. Thus LDML provides keyword 1694variants to reflect the different practices. For example, for German it 1695allows the distinction between PHONEBOOK and DICTIONARY collation.</p> 1696 1697 1698 1699 1700 1701 <p>When there is an existing national standard for a 1702country that is widely accepted in practice, the goal is to follow that 1703standard as much as possible. Where the common practice in the country 1704deviates from the national standard, or if there are multiple 1705conflicting common practices, or options in conforming to the national 1706standard, or conflicting national standards, multiple variants may be 1707entered into the CLDR, distinguished by keyword variants or variant 1708locale identifiers.</p> 1709 1710 1711 1712 1713 1714 <p>Where a data value is identified as following a 1715particular national standard (or other reference), the goal is to keep 1716that data aligned with that standard. There is, however, no guarantee 1717that data will be tagged with any or all of the national standards that 1718it follows.</p> 1719 1720 1721 1722 1723 1724 <h3>3.4 <a name="Dot-Dot_Releases">Dot-Dot 1725Releases</a></h3> 1726 1727 1728 1729 1730 1731 <p>Dot-dot releases, such as 1.4.1, are issued 1732whenever the standard identifiers change (that is, BCP 47 identifiers, 1733Time zone identifiers, or ISO 4217 Currency identifiers). 1734Updates to identifiers will also mean updating the English names for 1735those identifiers.</p> 1736 1737 1738 1739 1740 1741 <p>Corrigenda may also be included in dot-dot 1742releases. Dot-dot releases may also be issued if there are substantive 1743changes to supplemental (non-language) data. An example of supplemental 1744data additions would be adding more transforms, or adding more 1745script-language info.<br> 1746 1747 1748 1749 <br> 1750 1751 1752 1753Normally there are no dot-dot releases for language data, but the 1754committee may decide to issue one if the situation warrants. Normally 1755there are no major changes in the specification. </p> 1756 1757 1758 1759 1760 1761 <p>The structure and DTD may change, but except for 1762additions or for small bug fixes, data will not be changed in a way 1763that would affect the content of resolved data.</p> 1764 1765 1766 1767 1768 1769 <h2>4. <a name="public_feedback">Public 1770Feedback Process</a></h2> 1771 1772 1773 1774 1775 1776 <p>The public can supply formal feedback into CLDR 1777via the <a href="http://unicode.org/cldr/apps/survey/">Survey 1778Tool</a> or by filing a <a href="filing_bug_reports.html">Bug 1779Report or Feature Request</a>. There is also a public forum for 1780questions at <a href="http://www.unicode.org/consortium/distlist.html#cldr_list">CLDR 1781Mailing List</a> (details on archives are found there).</p> 1782 1783 1784 1785 1786 1787 <p>Anyone can also asked to be added to a list that 1788will receive notification of new CLDR bugs, so they can track issues if 1789they want. Anyone can also to reply to any bug report to add comments 1790or questions.</p> 1791 1792 1793 1794 1795 1796 <ul> 1797 1798 1799 1800 <li>To subscribe, send a note to 1801"ecartis+unicode.org" (use an <i>at sign</i> instead of 1802the +) and put "subscribe cldr-bugrfe" in the subject line.</li> 1803 1804 1805 1806 <li>To unsubscribe, put "unsubscribe cldr-bugrfe" 1807in the subject line instead.</li> 1808 1809 1810 1811 1812 1813 </ul> 1814 1815 1816 1817 1818 1819 <p>There is also a members-only <a href="http://www.unicode.org/members/index.html#cldr"> CLDR 1820mailing list</a> for members of the CLDR Technical Committee.</p> 1821 1822 1823 1824 1825 1826 <p><a href="http://www.unicode.org/review/">Public 1827Review Issues</a> may be posted in cases where broader public 1828feedback is desired on a particular issue.</p> 1829 1830 1831 1832 1833 1834 <p>Be aware that changes and updates to CLDR will 1835only be taken in response to information entered in the <a href="http://unicode.org/cldr/apps/survey/">Survey Tool</a> 1836or by filing a <a href="filing_bug_reports.html">Bug 1837Report or Feature Request</a>. Discussion on public mailing lists 1838is <i>not</i> monitored; no actions will be taken in 1839response to such discussion -- only in response to filed bugs. The 1840process of checking and entering data takes time and effort; so even 1841when bugs/feature requests are accepted, it may take some time before 1842they are in a release of CLDR.</p> 1843 1844 1845 1846 1847 1848 <h2><a name="data_release_process"></a>5. 1849Data Release Process</h2> 1850 1851 1852 1853 1854 1855 <h3>5.1 <a name="version_numbering">Version 1856Numbering</a></h3> 1857 1858 1859 1860 1861 1862 <p>The locale data is frozen per version. Once a 1863version is released, it is never modified. Any changes, however minor, 1864will mean a newer version of the locale data being released. The 1865versioning scheme is x.y.z, where z is incremented for bug fixes, y is 1866incremented for any additions (such as new locale data or LDML 1867elements), and x is incremented for any major changes in format.</p> 1868 1869 1870 1871 1872 1873 <h3>5.2 <a name="release_schedule">Release 1874Schedule</a></h3> 1875 1876 1877 1878 1879 1880 <p>Early releases of a version of the common locale 1881data will be issued as either alpha or beta releases, available for 1882public feedback. The dates for the next scheduled release will be on <a href="index.html">CLDR Project</a>.</p> 1883 1884 1885 1886 1887 1888 <p>The schedule milestones are:</p> 1889 1890 1891 1892 1893 1894 <table style="border-collapse: collapse;" id="AutoNumber1" border="1" bordercolor="#111111" cellpadding="2" cellspacing="0"> 1895 1896 1897 1898 <tbody> 1899 1900 1901 1902 <tr> 1903 1904 1905 1906 <td><b>Design (p1)</b></td> 1907 1908 1909 1910 <td>All the proposed design changes have been 1911accepted in place for changes in structure, and tools. All the DTD and specification changes are 1912made according to proposed design. The tools are updated to support the 1913new structure, including the survey tool for displaying, collecting, 1914and vetting data.</td> 1915 1916 1917 1918 </tr> 1919 1920 1921 1922 <tr> 1923 1924 1925 1926 <td style="white-space: nowrap;"><b>Survey Tool Beta (p2)</b></td> 1927 1928 1929 1930 <td>Users can try out the survey tool and supply feedback</td> 1931 1932 1933 1934 </tr> 1935 1936 1937 1938 <tr> 1939 1940 <td><span style="font-weight: bold;">Data Submission</span></td> 1941 1942 <td>Users can add data and vet (vote for) for data</td> 1943 1944 </tr> 1945 1946 <tr> 1947 1948 1949 1950 <td><b>Data Vetting</b></td> 1951 1952 1953 1954 <td>Users can vet (vote for) data, and can add in certain disputed cases</td> 1955 1956 1957 1958 </tr> 1959 1960 1961 1962 <tr> 1963 1964 1965 1966 <td><span style="font-weight: bold;">Data Resolution</span></td> 1967 1968 1969 1970 <td>Data resolution, data/structure verification and correction by the committee.</td> 1971 1972 1973 1974 </tr> 1975 1976 1977 1978 <tr> 1979 1980 <td><span style="font-weight: bold;">Final Candidate</span></td> 1981 1982 <td>Final Candidate available for testing. Only showstoppers fixed.</td> 1983 1984 </tr> 1985 1986 <tr> 1987 1988 1989 1990 <td><b>Release</b></td> 1991 1992 1993 1994 <td>Released, stable, referenceable version.</td> 1995 1996 1997 1998 </tr> 1999 2000 2001 2002 2003 2004 </tbody> 2005 2006 2007 </table> 2008 2009 2010 <p>Each phase ends at 24:00 (midnight) on the day in question.</p> 2011 2012 2013 2014 2015 2016 <h2><a name="meetings"></a>6. 2017Meetings and Communication</h2> 2018 2019 2020 2021 2022 2023 <p>The currently-scheduled meetings are listed on the 2024 <a href="http://www.unicode.org/timesens/calendar.html">Unicode 2025Calendar</a>. Meetings are held by phone, every week at 8:00 2026Pacific Time (-08:00 GMT in winter, -07:00 GMT in summer). Some 2027meetings may be skipped if they conflict with holidays or other Unicode 2028meetings.</p> 2029 2030 2031 2032 2033 2034 <p>There is an internal email list for the Unicode 2035CLDR Technical Committee, open to Unicode members and invited experts. 2036All national standards bodies who are interested in locale data are 2037also invited to become involved by establishing a <a href="http://www.unicode.org/consortium/join.html">Liaison 2038membership</a> in the Unicode Consortium, to gain access to this 2039list.</p> 2040 2041 2042 2043 2044 2045 <p>Notification of the telephone numbers and 2046passcode, and agenda, and any change in schedule are sent out on the 2047this email list.</p> 2048 2049 2050 2051 2052 2053 <h2><a name="officers"></a>7. 2054Officers</h2> 2055 2056 2057 2058 2059 2060 <p>The current Technical Committee Officers are:</p> 2061 2062 2063 2064 2065 2066 <ul> 2067 2068 2069 2070 <li>Chair: Mark Davis (Google)</li> 2071 2072 2073 2074 <li>Vice-Chair: John Emmons (IBM)</li> 2075 2076 2077 2078 2079 2080 </ul> 2081 2082 2083 2084 2085 2086 <blockquote> </blockquote> 2087 2088 2089 2090 </div> 2091 2092 2093 2094 </td> 2095 2096 2097 2098 </tr> 2099 2100 2101 2102 2103 2104 </tbody> 2105 2106 2107 </table> 2108 2109 2110 2111 2112 2113 <hr width="50%"> 2114 2115 2116 <div align="center"> 2117 2118 2119 <center> 2120 2121 2122 <table border="0" cellpadding="0" cellspacing="0"> 2123 2124 2125 2126 <tbody> 2127 2128 2129 2130 <tr> 2131 2132 2133 2134 <td><a href="http://www.unicode.org/copyright.html"> 2135 <img src="http://www.unicode.org/img/hb_notice.gif" alt="Access to Copyright and terms of use" border="0" height="50" width="216"></a></td> 2136 2137 2138 2139 </tr> 2140 2141 2142 2143 2144 2145 </tbody> 2146 2147 2148 </table> 2149 2150 2151 2152 2153 2154 <script language="Javascript" type="text/javascript" src="http://www.unicode.org/webscripts/lastModified.js"> 2155 </script> 2156 </center> 2157 2158 2159 2160 </div> 2161 2162 2163 2164 </td> 2165 2166 2167 2168 </tr> 2169 2170 2171 2172 2173 2174 </tbody> 2175</table> 2176 2177 2178 2179</body> 2180</html> 2181
