index.html
371 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
2848
2849
2850
2851
2852
2853
2854
2855
2856
2857
2858
2859
2860
2861
2862
2863
2864
2865
2866
2867
2868
2869
2870
2871
2872
2873
2874
2875
2876
2877
2878
2879
2880
2881
2882
2883
2884
2885
2886
2887
2888
2889
2890
2891
2892
2893
2894
2895
2896
2897
2898
2899
2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2923
2924
2925
2926
2927
2928
2929
2930
2931
2932
2933
2934
2935
2936
2937
2938
2939
2940
2941
2942
2943
2944
2945
2946
2947
2948
2949
2950
2951
2952
2953
2954
2955
2956
2957
2958
2959
2960
2961
2962
2963
2964
2965
2966
2967
2968
2969
2970
2971
2972
2973
2974
2975
2976
2977
2978
2979
2980
2981
2982
2983
2984
2985
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
2998
2999
3000
3001
3002
3003
3004
3005
3006
3007
3008
3009
3010
3011
3012
3013
3014
3015
3016
3017
3018
3019
3020
3021
3022
3023
3024
3025
3026
3027
3028
3029
3030
3031
3032
3033
3034
3035
3036
3037
3038
3039
3040
3041
3042
3043
3044
3045
3046
3047
3048
3049
3050
3051
3052
3053
3054
3055
3056
3057
3058
3059
3060
3061
3062
3063
3064
3065
3066
3067
3068
3069
3070
3071
3072
3073
3074
3075
3076
3077
3078
3079
3080
3081
3082
3083
3084
3085
3086
3087
3088
3089
3090
3091
3092
3093
3094
3095
3096
3097
3098
3099
3100
3101
3102
3103
3104
3105
3106
3107
3108
3109
3110
3111
3112
3113
3114
3115
3116
3117
3118
3119
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3130
3131
3132
3133
3134
3135
3136
3137
3138
3139
3140
3141
3142
3143
3144
3145
3146
3147
3148
3149
3150
3151
3152
3153
3154
3155
3156
3157
3158
3159
3160
3161
3162
3163
3164
3165
3166
3167
3168
3169
3170
3171
3172
3173
3174
3175
3176
3177
3178
3179
3180
3181
3182
3183
3184
3185
3186
3187
3188
3189
3190
3191
3192
3193
3194
3195
3196
3197
3198
3199
3200
3201
3202
3203
3204
3205
3206
3207
3208
3209
3210
3211
3212
3213
3214
3215
3216
3217
3218
3219
3220
3221
3222
3223
3224
3225
3226
3227
3228
3229
3230
3231
3232
3233
3234
3235
3236
3237
3238
3239
3240
3241
3242
3243
3244
3245
3246
3247
3248
3249
3250
3251
3252
3253
3254
3255
3256
3257
3258
3259
3260
3261
3262
3263
3264
3265
3266
3267
3268
3269
3270
3271
3272
3273
3274
3275
3276
3277
3278
3279
3280
3281
3282
3283
3284
3285
3286
3287
3288
3289
3290
3291
3292
3293
3294
3295
3296
3297
3298
3299
3300
3301
3302
3303
3304
3305
3306
3307
3308
3309
3310
3311
3312
3313
3314
3315
3316
3317
3318
3319
3320
3321
3322
3323
3324
3325
3326
3327
3328
3329
3330
3331
3332
3333
3334
3335
3336
3337
3338
3339
3340
3341
3342
3343
3344
3345
3346
3347
3348
3349
3350
3351
3352
3353
3354
3355
3356
3357
3358
3359
3360
3361
3362
3363
3364
3365
3366
3367
3368
3369
3370
3371
3372
3373
3374
3375
3376
3377
3378
3379
3380
3381
3382
3383
3384
3385
3386
3387
3388
3389
3390
3391
3392
3393
3394
3395
3396
3397
3398
3399
3400
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3412
3413
3414
3415
3416
3417
3418
3419
3420
3421
3422
3423
3424
3425
3426
3427
3428
3429
3430
3431
3432
3433
3434
3435
3436
3437
3438
3439
3440
3441
3442
3443
3444
3445
3446
3447
3448
3449
3450
3451
3452
3453
3454
3455
3456
3457
3458
3459
3460
3461
3462
3463
3464
3465
3466
3467
3468
3469
3470
3471
3472
3473
3474
3475
3476
3477
3478
3479
3480
3481
3482
3483
3484
3485
3486
3487
3488
3489
3490
3491
3492
3493
3494
3495
3496
3497
3498
3499
3500
3501
3502
3503
3504
3505
3506
3507
3508
3509
3510
3511
3512
3513
3514
3515
3516
3517
3518
3519
3520
3521
3522
3523
3524
3525
3526
3527
3528
3529
3530
3531
3532
3533
3534
3535
3536
3537
3538
3539
3540
3541
3542
3543
3544
3545
3546
3547
3548
3549
3550
3551
3552
3553
3554
3555
3556
3557
3558
3559
3560
3561
3562
3563
3564
3565
3566
3567
3568
3569
3570
3571
3572
3573
3574
3575
3576
3577
3578
3579
3580
3581
3582
3583
3584
3585
3586
3587
3588
3589
3590
3591
3592
3593
3594
3595
3596
3597
3598
3599
3600
3601
3602
3603
3604
3605
3606
3607
3608
3609
3610
3611
3612
3613
3614
3615
3616
3617
3618
3619
3620
3621
3622
3623
3624
3625
3626
3627
3628
3629
3630
3631
3632
3633
3634
3635
3636
3637
3638
3639
3640
3641
3642
3643
3644
3645
3646
3647
3648
3649
3650
3651
3652
3653
3654
3655
3656
3657
3658
3659
3660
3661
3662
3663
3664
3665
3666
3667
3668
3669
3670
3671
3672
3673
3674
3675
3676
3677
3678
3679
3680
3681
3682
3683
3684
3685
3686
3687
3688
3689
3690
3691
3692
3693
3694
3695
3696
3697
3698
3699
3700
3701
3702
3703
3704
3705
3706
3707
3708
3709
3710
3711
3712
3713
3714
3715
3716
3717
3718
3719
3720
3721
3722
3723
3724
3725
3726
3727
3728
3729
3730
3731
3732
3733
3734
3735
3736
3737
3738
3739
3740
3741
3742
3743
3744
3745
3746
3747
3748
3749
3750
3751
3752
3753
3754
3755
3756
3757
3758
3759
3760
3761
3762
3763
3764
3765
3766
3767
3768
3769
3770
3771
3772
3773
3774
3775
3776
3777
3778
3779
3780
3781
3782
3783
3784
3785
3786
3787
3788
3789
3790
3791
3792
3793
3794
3795
3796
3797
3798
3799
3800
3801
3802
3803
3804
3805
3806
3807
3808
3809
3810
3811
3812
3813
3814
3815
3816
3817
3818
3819
3820
3821
3822
3823
3824
3825
3826
3827
3828
3829
3830
3831
3832
3833
3834
3835
3836
3837
3838
3839
3840
3841
3842
3843
3844
3845
3846
3847
3848
3849
3850
3851
3852
3853
3854
3855
3856
3857
3858
3859
3860
3861
3862
3863
3864
3865
3866
3867
3868
3869
3870
3871
3872
3873
3874
3875
3876
3877
3878
3879
3880
3881
3882
3883
3884
3885
3886
3887
3888
3889
3890
3891
3892
3893
3894
3895
3896
3897
3898
3899
3900
3901
3902
3903
3904
3905
3906
3907
3908
3909
3910
3911
3912
3913
3914
3915
3916
3917
3918
3919
3920
3921
3922
3923
3924
3925
3926
3927
3928
3929
3930
3931
3932
3933
3934
3935
3936
3937
3938
3939
3940
3941
3942
3943
3944
3945
3946
3947
3948
3949
3950
3951
3952
3953
3954
3955
3956
3957
3958
3959
3960
3961
3962
3963
3964
3965
3966
3967
3968
3969
3970
3971
3972
3973
3974
3975
3976
3977
3978
3979
3980
3981
3982
3983
3984
3985
3986
3987
3988
3989
3990
3991
3992
3993
3994
3995
3996
3997
3998
3999
4000
4001
4002
4003
4004
4005
4006
4007
4008
4009
4010
4011
4012
4013
4014
4015
4016
4017
4018
4019
4020
4021
4022
4023
4024
4025
4026
4027
4028
4029
4030
4031
4032
4033
4034
4035
4036
4037
4038
4039
4040
4041
4042
4043
4044
4045
4046
4047
4048
4049
4050
4051
4052
4053
4054
4055
4056
4057
4058
4059
4060
4061
4062
4063
4064
4065
4066
4067
4068
4069
4070
4071
4072
4073
4074
4075
4076
4077
4078
4079
4080
4081
4082
4083
4084
4085
4086
4087
4088
4089
4090
4091
4092
4093
4094
4095
4096
4097
4098
4099
4100
4101
4102
4103
4104
4105
4106
4107
4108
4109
4110
4111
4112
4113
4114
4115
4116
4117
4118
4119
4120
4121
4122
4123
4124
4125
4126
4127
4128
4129
4130
4131
4132
4133
4134
4135
4136
4137
4138
4139
4140
4141
4142
4143
4144
4145
4146
4147
4148
4149
4150
4151
4152
4153
4154
4155
4156
4157
4158
4159
4160
4161
4162
4163
4164
4165
4166
4167
4168
4169
4170
4171
4172
4173
4174
4175
4176
4177
4178
4179
4180
4181
4182
4183
4184
4185
4186
4187
4188
4189
4190
4191
4192
4193
4194
4195
4196
4197
4198
4199
4200
4201
4202
4203
4204
4205
4206
4207
4208
4209
4210
4211
4212
4213
4214
4215
4216
4217
4218
4219
4220
4221
4222
4223
4224
4225
4226
4227
4228
4229
4230
4231
4232
4233
4234
4235
4236
4237
4238
4239
4240
4241
4242
4243
4244
4245
4246
4247
4248
4249
4250
4251
4252
4253
4254
4255
4256
4257
4258
4259
4260
4261
4262
4263
4264
4265
4266
4267
4268
4269
4270
4271
4272
4273
4274
4275
4276
4277
4278
4279
4280
4281
4282
4283
4284
4285
4286
4287
4288
4289
4290
4291
4292
4293
4294
4295
4296
4297
4298
4299
4300
4301
4302
4303
4304
4305
4306
4307
4308
4309
4310
4311
4312
4313
4314
4315
4316
4317
4318
4319
4320
4321
4322
4323
4324
4325
4326
4327
4328
4329
4330
4331
4332
4333
4334
4335
4336
4337
4338
4339
4340
4341
4342
4343
4344
4345
4346
4347
4348
4349
4350
4351
4352
4353
4354
4355
4356
4357
4358
4359
4360
4361
4362
4363
4364
4365
4366
4367
4368
4369
4370
4371
4372
4373
4374
4375
4376
4377
4378
4379
4380
4381
4382
4383
4384
4385
4386
4387
4388
4389
4390
4391
4392
4393
4394
4395
4396
4397
4398
4399
4400
4401
4402
4403
4404
4405
4406
4407
4408
4409
4410
4411
4412
4413
4414
4415
4416
4417
4418
4419
4420
4421
4422
4423
4424
4425
4426
4427
4428
4429
4430
4431
4432
4433
4434
4435
4436
4437
4438
4439
4440
4441
4442
4443
4444
4445
4446
4447
4448
4449
4450
4451
4452
4453
4454
4455
4456
4457
4458
4459
4460
4461
4462
4463
4464
4465
4466
4467
4468
4469
4470
4471
4472
4473
4474
4475
4476
4477
4478
4479
4480
4481
4482
4483
4484
4485
4486
4487
4488
4489
4490
4491
4492
4493
4494
4495
4496
4497
4498
4499
4500
4501
4502
4503
4504
4505
4506
4507
4508
4509
4510
4511
4512
4513
4514
4515
4516
4517
4518
4519
4520
4521
4522
4523
4524
4525
4526
4527
4528
4529
4530
4531
4532
4533
4534
4535
4536
4537
4538
4539
4540
4541
4542
4543
4544
4545
4546
4547
4548
4549
4550
4551
4552
4553
4554
4555
4556
4557
4558
4559
4560
4561
4562
4563
4564
4565
4566
4567
4568
4569
4570
4571
4572
4573
4574
4575
4576
4577
4578
4579
4580
4581
4582
4583
4584
4585
4586
4587
4588
4589
4590
4591
4592
4593
4594
4595
4596
4597
4598
4599
4600
4601
4602
4603
4604
4605
4606
4607
4608
4609
4610
4611
4612
4613
4614
4615
4616
4617
4618
4619
4620
4621
4622
4623
4624
4625
4626
4627
4628
4629
4630
4631
4632
4633
4634
4635
4636
4637
4638
4639
4640
4641
4642
4643
4644
4645
4646
4647
4648
4649
4650
4651
4652
4653
4654
4655
4656
4657
4658
4659
4660
4661
4662
4663
4664
4665
4666
4667
4668
4669
4670
4671
4672
4673
4674
4675
4676
4677
4678
4679
4680
4681
4682
4683
4684
4685
4686
4687
4688
4689
4690
4691
4692
4693
4694
4695
4696
4697
4698
4699
4700
4701
4702
4703
4704
4705
4706
4707
4708
4709
4710
4711
4712
4713
4714
4715
4716
4717
4718
4719
4720
4721
4722
4723
4724
4725
4726
4727
4728
4729
4730
4731
4732
4733
4734
4735
4736
4737
4738
4739
4740
4741
4742
4743
4744
4745
4746
4747
4748
4749
4750
4751
4752
4753
4754
4755
4756
4757
4758
4759
4760
4761
4762
4763
4764
4765
4766
4767
4768
4769
4770
4771
4772
4773
4774
4775
4776
4777
4778
4779
4780
4781
4782
4783
4784
4785
4786
4787
4788
4789
4790
4791
4792
4793
4794
4795
4796
4797
4798
4799
4800
4801
4802
4803
4804
4805
4806
4807
4808
4809
4810
4811
4812
4813
4814
4815
4816
4817
4818
4819
4820
4821
4822
4823
4824
4825
4826
4827
4828
4829
4830
4831
4832
4833
4834
4835
4836
4837
4838
4839
4840
4841
4842
4843
4844
4845
4846
4847
4848
4849
4850
4851
4852
4853
4854
4855
4856
4857
4858
4859
4860
4861
4862
4863
4864
4865
4866
4867
4868
4869
4870
4871
4872
4873
4874
4875
4876
4877
4878
4879
4880
4881
4882
4883
4884
4885
4886
4887
4888
4889
4890
4891
4892
4893
4894
4895
4896
4897
4898
4899
4900
4901
4902
4903
4904
4905
4906
4907
4908
4909
4910
4911
4912
4913
4914
4915
4916
4917
4918
4919
4920
4921
4922
4923
4924
4925
4926
4927
4928
4929
4930
4931
4932
4933
4934
4935
4936
4937
4938
4939
4940
4941
4942
4943
4944
4945
4946
4947
4948
4949
4950
4951
4952
4953
4954
4955
4956
4957
4958
4959
4960
4961
4962
4963
4964
4965
4966
4967
4968
4969
4970
4971
4972
4973
4974
4975
4976
4977
4978
4979
4980
4981
4982
4983
4984
4985
4986
4987
4988
4989
4990
4991
4992
4993
4994
4995
4996
4997
4998
4999
5000
5001
5002
5003
5004
5005
5006
5007
5008
5009
5010
5011
5012
5013
5014
5015
5016
5017
5018
5019
5020
5021
5022
5023
5024
5025
5026
5027
5028
5029
5030
5031
5032
5033
5034
5035
5036
5037
5038
5039
5040
5041
5042
5043
5044
5045
5046
5047
5048
5049
5050
5051
5052
5053
5054
5055
5056
5057
5058
5059
5060
5061
5062
5063
5064
5065
5066
5067
5068
5069
5070
5071
5072
5073
5074
5075
5076
5077
5078
5079
5080
5081
5082
5083
5084
5085
5086
5087
5088
5089
5090
5091
5092
5093
5094
5095
5096
5097
5098
5099
5100
5101
5102
5103
5104
5105
5106
5107
5108
5109
5110
5111
5112
5113
5114
5115
5116
5117
5118
5119
5120
5121
5122
5123
5124
5125
5126
5127
5128
5129
5130
5131
5132
5133
5134
5135
5136
5137
5138
5139
5140
5141
5142
5143
5144
5145
5146
5147
5148
5149
5150
5151
5152
5153
5154
5155
5156
5157
5158
5159
5160
5161
5162
5163
5164
5165
5166
5167
5168
5169
5170
5171
5172
5173
5174
5175
5176
5177
5178
5179
5180
5181
5182
5183
5184
5185
5186
5187
5188
5189
5190
5191
5192
5193
5194
5195
5196
5197
5198
5199
5200
5201
5202
5203
5204
5205
5206
5207
5208
5209
5210
5211
5212
5213
5214
5215
5216
5217
5218
5219
5220
5221
5222
5223
5224
5225
5226
5227
5228
5229
5230
5231
5232
5233
5234
5235
5236
5237
5238
5239
5240
5241
5242
5243
5244
5245
5246
5247
5248
5249
5250
5251
5252
5253
5254
5255
5256
5257
5258
5259
5260
5261
5262
5263
5264
5265
5266
5267
5268
5269
5270
5271
5272
5273
5274
5275
5276
5277
5278
5279
5280
5281
5282
5283
5284
5285
5286
5287
5288
5289
5290
5291
5292
5293
5294
5295
5296
5297
5298
5299
5300
5301
5302
5303
5304
5305
5306
5307
5308
5309
5310
5311
5312
5313
5314
5315
5316
5317
5318
5319
5320
5321
5322
5323
5324
5325
5326
5327
5328
5329
5330
5331
5332
5333
5334
5335
5336
5337
5338
5339
5340
5341
5342
5343
5344
5345
5346
5347
5348
5349
5350
5351
5352
5353
5354
5355
5356
5357
5358
5359
5360
5361
5362
5363
5364
5365
5366
5367
5368
5369
5370
5371
5372
5373
5374
5375
5376
5377
5378
5379
5380
5381
5382
5383
5384
5385
5386
5387
5388
5389
5390
5391
5392
5393
5394
5395
5396
5397
5398
5399
5400
5401
5402
5403
5404
5405
5406
5407
5408
5409
5410
5411
5412
5413
5414
5415
5416
5417
5418
5419
5420
5421
5422
5423
5424
5425
5426
5427
5428
5429
5430
5431
5432
5433
5434
5435
5436
5437
5438
5439
5440
5441
5442
5443
5444
5445
5446
5447
5448
5449
5450
5451
5452
5453
5454
5455
5456
5457
5458
5459
5460
5461
5462
5463
5464
5465
5466
5467
5468
5469
5470
5471
5472
5473
5474
5475
5476
5477
5478
5479
5480
5481
5482
5483
5484
5485
5486
5487
5488
5489
5490
5491
5492
5493
5494
5495
5496
5497
5498
5499
5500
5501
5502
5503
5504
5505
5506
5507
5508
5509
5510
5511
5512
5513
5514
5515
5516
5517
5518
5519
5520
5521
5522
5523
5524
5525
5526
5527
5528
5529
5530
5531
5532
5533
5534
5535
5536
5537
5538
5539
5540
5541
5542
5543
5544
5545
5546
5547
5548
5549
5550
5551
5552
5553
5554
5555
5556
5557
5558
5559
5560
5561
5562
5563
5564
5565
5566
5567
5568
5569
5570
5571
5572
5573
5574
5575
5576
5577
5578
5579
5580
5581
5582
5583
5584
5585
5586
5587
5588
5589
5590
5591
5592
5593
5594
5595
5596
5597
5598
5599
5600
5601
5602
5603
5604
5605
5606
5607
5608
5609
5610
5611
5612
5613
5614
5615
5616
5617
5618
5619
5620
5621
5622
5623
5624
5625
5626
5627
5628
5629
5630
5631
5632
5633
5634
5635
5636
5637
5638
5639
5640
5641
5642
5643
5644
5645
5646
5647
5648
5649
5650
5651
5652
5653
5654
5655
5656
5657
5658
5659
5660
5661
5662
5663
5664
5665
5666
5667
5668
5669
5670
5671
5672
5673
5674
5675
5676
5677
5678
5679
5680
5681
5682
5683
5684
5685
5686
5687
5688
5689
5690
5691
5692
5693
5694
5695
5696
5697
5698
5699
5700
5701
5702
5703
5704
5705
5706
5707
5708
5709
5710
5711
5712
5713
5714
5715
5716
5717
5718
5719
5720
5721
5722
5723
5724
5725
5726
5727
5728
5729
5730
5731
5732
5733
5734
5735
5736
5737
5738
5739
5740
5741
5742
5743
5744
5745
5746
5747
5748
5749
5750
5751
5752
5753
5754
5755
5756
5757
5758
5759
5760
5761
5762
5763
5764
5765
5766
5767
5768
5769
5770
5771
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-US" lang="en-US">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>Internationalization Tag Set (ITS) Version 1.0</title><style type="text/css" xml:space="preserve">
</style><link rel="stylesheet" href="local.css" type="text/css" />
<link rel="stylesheet" type="text/css" href="http://www.w3.org/StyleSheets/TR/W3C-REC.css" />
</head>
<body>
<div style="text-align:center;">
<p>[ <a href="#contents" shape="rect">contents</a> ]
</p>
</div>
<div class="head">
<p><a href="http://www.w3.org/" shape="rect"><img src="http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width="72" /></a></p>
<h1><a name="title" id="title" shape="rect"></a>Internationalization Tag Set (ITS) Version 1.0
</h1>
<h2><a name="w3c-doctype" id="w3c-doctype" shape="rect"></a>W3C Recommendation 03 April 2007
</h2>
<dl>
<dt>This version:</dt>
<dd>
<a href="http://www.w3.org/TR/2007/REC-its-20070403/" shape="rect">
http://www.w3.org/TR/2007/REC-its-20070403/</a>
</dd>
<dt>Latest version:</dt>
<dd>
<a href="http://www.w3.org/TR/its/" shape="rect">http://www.w3.org/TR/its/</a>
</dd>
<dt>Previous version:</dt>
<dd><a href="http://www.w3.org/TR/2007/PR-its-20070226/" shape="rect">
http://www.w3.org/TR/2007/PR-its-20070226/</a></dd>
<dt>Editors:</dt>
<dd>Christian Lieske, SAP AG</dd>
<dd>Felix Sasaki, W3C</dd>
</dl>
<p>Please refer to the <a href="http://www.w3.org/International/its/itstagset/its-errata.html" shape="rect"><strong>errata</strong></a> for this document, which may include some normative corrections.
</p>
<p>See also <a href="http://www.w3.org/2003/03/Translations/byTechnology?technology=its" shape="rect"><strong>translations</strong></a>.
</p>
<p>This document is also available in these non-normative formats: <a href="itstagset.xml" shape="rect">ODD/XML document</a>, <a href="itstagset.zip" shape="rect">self-contained zipped archive</a>, and <a href="itstagset-diff-20070226.html" shape="rect">XHTML Diff markup to publication from 26 February 2007</a>.
</p>
<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright" shape="rect">Copyright</a> © 2007 <a href="http://www.w3.org/" shape="rect"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/" shape="rect"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/" shape="rect"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/" shape="rect">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer" shape="rect">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks" shape="rect">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents" shape="rect">document use</a> rules apply.
</p>
</div>
<hr />
<div>
<h2><a name="abstract" id="abstract" shape="rect"></a>Abstract
</h2>
<p>This document defines data categories and their
implementation as a set of elements and attributes called the
<em>Internationalization Tag Set (ITS)</em>. ITS is designed
to be used with schemas to support the internationalization and
localization of schemas and documents. An implementation is
provided for three schema languages: XML DTD, XML Schema and
RELAX NG.
</p>
</div>
<div>
<h2><a name="status" id="status" shape="rect"></a>Status of this Document
</h2>
<p>
<em>This section describes the status of this document at
the time of its publication. Other documents may supersede
this document. A list of current W3C publications and the
latest revision of this technical report can be found in the
<a href="http://www.w3.org/TR/" shape="rect">W3C technical reports
index</a> at http://www.w3.org/TR/.</em>
</p>
<p>This document defines data categories and their implementation as a set of elements and attributes called the Internationalization
Tag Set (ITS). ITS is designed to be used with schemas to support the internationalization and localization of schemas and
documents. An implementation is provided for three schema languages: XML DTD, XML Schema and RELAX NG.
</p>
<p>This is a <a href="http://www.w3.org/2004/02/Process-20040205/tr.html#RecsW3C" shape="rect">Recommendation</a>
of the W3C. It has been
developed by the W3C <a href="http://www.w3.org/International/its/" shape="rect">Internationalization Tag Set (ITS) Working Group</a>, which is part of the <a href="http://www.w3.org/International/" shape="rect">Internationalization
Activity</a>.
</p>
<p>This document has been reviewed by W3C Members, by software
developers, and by other W3C groups and interested parties, and is
endorsed by the Director as a W3C Recommendation. It is a stable
document and may be used as reference material or cited from
another document. W3C's role in making the Recommendation is to
draw attention to the specification and to promote its widespread
deployment. This enhances the functionality and interoperability of
the Web.
</p>
<p>Please make comments about this document using
W3C's <a href="http://www.w3.org/Bugs/Public/" shape="rect">public Bugzilla
system</a>. We recommend using Bugzilla for making comments
(instructions can be found at <a href="http://www.w3.org/International/its/its-bugzilla" shape="rect">How to
use the Issues Tracking System for the ITS Tagset Working
Draft</a>). If this is not feasible, comments may also be sent
to <a href="mailto:www-i18n-comments@w3.org?subject=[Comment on ITS WD]" shape="rect">www-i18n-comments@w3.org</a>. Use
"[Comment on ITS WD]" in the subject line of your
email. A list of <a href="http://www.w3.org/Bugs/Public/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ITS&component=ITS+tagset&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=" shape="rect">
ITS tagset related comments and issues in Bugzilla</a> and
the <a href="http://lists.w3.org/Archives/Public/www-i18n-comments/" shape="rect">www-
i18n-comments archives</a> are publicly available.
</p>
<p>This document incorporates minor changes made against the Proposed Recommendation of 21 November 2006; please see the <a href="#changelog-since-20070226" shape="rect">Revision Log</a> for details. The <a href="http://www.w3.org/International/its/itstagset/ImpReport.html" shape="rect">implementation report</a> and <a href="http://www.w3.org/International/its/tests/" shape="rect">test suite</a> provide further implementation information.
</p>
<p> This document was produced by a group operating under the
<a href="http://www.w3.org/Consortium/Patent-Policy-20040205/" shape="rect">5
February 2004 W3C Patent Policy</a>. W3C maintains a <a href="http://www.w3.org/2004/01/pp-impl/37139/status" shape="rect">public
list of any patent disclosures</a> made in connection with the
deliverables of the group; that page also includes instructions
for disclosing a patent. An individual who has actual knowledge
of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential" shape="rect">Essential
Claim(s)</a> must disclose the information in accordance with
<a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure" shape="rect">section
6 of the W3C Patent Policy</a>.
</p>
</div>
<div class="toc">
<h2><a name="contents" id="contents" shape="rect"></a>Table of Contents
</h2>
<div class="toc">
<div class="toc1">1 <a href="#introduction" shape="rect">Introduction</a><div class="toc2">1.1 <a href="#motivation-its" shape="rect">Motivation for ITS</a><div class="toc3">1.1.1 <a href="#motivation-its-issues" shape="rect">Typical Problems</a></div>
</div>
<div class="toc2">1.2 <a href="#users-usage" shape="rect">Users and Usages of ITS</a><div class="toc3">1.2.1 <a href="#potential-users" shape="rect">Potential Users of ITS</a></div>
<div class="toc3">1.2.2 <a href="#ways-to-use-its" shape="rect">Ways to Use ITS</a></div>
</div>
<div class="toc2">1.3 <a href="#out-of-scope" shape="rect">Out of Scope</a></div>
<div class="toc2">1.4 <a href="#design-decisions" shape="rect">Important Design Principles</a></div>
<div class="toc2">1.5 <a href="#spec-development" shape="rect">Development of this Specification</a></div>
</div>
<div class="toc1">2 <a href="#basic-concepts" shape="rect">Basic Concepts</a><div class="toc2">2.1 <a href="#basic-concepts-selection" shape="rect">Selection</a><div class="toc3">2.1.1 <a href="#basic-concepts-selection-local" shape="rect">Local Approach</a></div>
<div class="toc3">2.1.2 <a href="#basic-concepts-selection-global" shape="rect">Global Approach</a></div>
</div>
<div class="toc2">2.2 <a href="#basic-concepts-overinher" shape="rect">Overriding and Inheritance</a></div>
<div class="toc2">2.3 <a href="#basic-concepts-addingpointing" shape="rect">Adding Information or Pointing to Existing Information</a></div>
</div>
<div class="toc1">3 <a href="#notation-terminology" shape="rect">Notation and Terminology</a><div class="toc2">3.1 <a href="#notation" shape="rect">Notation</a></div>
<div class="toc2">3.2 <a href="#def-schemalanguage" shape="rect">Schema Language</a></div>
<div class="toc2">3.3 <a href="#def-datacat" shape="rect">Data category</a></div>
<div class="toc2">3.4 <a href="#def-selection" shape="rect">Selection</a></div>
<div class="toc2">3.5 <a href="#iri-usage" shape="rect">Usage of Internationalized Resource Identifiers in ITS</a></div>
</div>
<div class="toc1">4 <a href="#conformance" shape="rect">Conformance</a><div class="toc2">4.1 <a href="#conformance-product-schema" shape="rect">Conformance Type 1: ITS Markup Declarations</a></div>
<div class="toc2">4.2 <a href="#conformance-product-processing-expectations" shape="rect">Conformance Type 2: The Processing Expectations for ITS Markup</a></div>
</div>
<div class="toc1">5 <a href="#its-processing" shape="rect">Processing of ITS information</a><div class="toc2">5.1 <a href="#its-version-attribute" shape="rect">Indicating the Version of ITS</a></div>
<div class="toc2">5.2 <a href="#datacategory-locations" shape="rect">Locations of Data Categories</a><div class="toc3">5.2.1 <a href="#selection-global" shape="rect">Global, Rule-based Selection</a></div>
<div class="toc3">5.2.2 <a href="#selection-local" shape="rect">Local Selection in an XML Document</a></div>
</div>
<div class="toc2">5.3 <a href="#link-external-rules" shape="rect">Link to External Rules</a></div>
<div class="toc2">5.4 <a href="#selection-precedence" shape="rect">Precedence between Selections</a></div>
<div class="toc2">5.5 <a href="#associating-its-with-existing-markup" shape="rect">Associating ITS Data Categories with Existing Markup</a></div>
</div>
<div class="toc1">6 <a href="#datacategory-description" shape="rect">Description of Data Categories</a><div class="toc2">6.1 <a href="#datacategories-defaults-etc" shape="rect">Position, Defaults, Inheritance and Overriding of Data Categories</a></div>
<div class="toc2">6.2 <a href="#trans-datacat" shape="rect">Translate</a><div class="toc3">6.2.1 <a href="#translatability-definition" shape="rect">Definition</a></div>
<div class="toc3">6.2.2 <a href="#translatability-implementation" shape="rect">Implementation</a></div>
<div class="toc3">6.2.3 <a href="#translatability-markup" shape="rect">Markup Declarations for Translate</a></div>
</div>
<div class="toc2">6.3 <a href="#locNote-datacat" shape="rect">Localization Note</a><div class="toc3">6.3.1 <a href="#locNote-definition" shape="rect">Definition</a></div>
<div class="toc3">6.3.2 <a href="#locNote-implementation" shape="rect">Implementation</a></div>
<div class="toc3">6.3.3 <a href="#locNote-markup" shape="rect">Markup Declarations for Localization Note</a></div>
</div>
<div class="toc2">6.4 <a href="#terminology" shape="rect">Terminology</a><div class="toc3">6.4.1 <a href="#terminology-definition" shape="rect">Definition</a></div>
<div class="toc3">6.4.2 <a href="#terminology-implementation" shape="rect">Implementation</a></div>
<div class="toc3">6.4.3 <a href="#terminology-markup" shape="rect">Markup Declarations for Terminology</a></div>
</div>
<div class="toc2">6.5 <a href="#directionality" shape="rect">Directionality</a><div class="toc3">6.5.1 <a href="#directionality-definition" shape="rect">Definition</a></div>
<div class="toc3">6.5.2 <a href="#directionality-implementation" shape="rect">Implementation</a></div>
<div class="toc3">6.5.3 <a href="#directionality-markup" shape="rect">Markup Declarations for Directionality</a></div>
</div>
<div class="toc2">6.6 <a href="#ruby-annotation" shape="rect">Ruby</a><div class="toc3">6.6.1 <a href="#ruby-definition" shape="rect">Definition</a></div>
<div class="toc3">6.6.2 <a href="#ruby-implementation" shape="rect">Implementation</a></div>
<div class="toc3">6.6.3 <a href="#ruby-markup" shape="rect">Markup Declarations for Ruby</a></div>
</div>
<div class="toc2">6.7 <a href="#language-information" shape="rect">Language Information</a><div class="toc3">6.7.1 <a href="#langinfo-definition" shape="rect">Definition</a></div>
<div class="toc3">6.7.2 <a href="#langinfo-implementation" shape="rect">Implementation</a></div>
<div class="toc3">6.7.3 <a href="#langinfo-markup" shape="rect">Markup Declarations for Language Information</a></div>
</div>
<div class="toc2">6.8 <a href="#elements-within-text" shape="rect">Elements Within Text</a><div class="toc3">6.8.1 <a href="#within-text-definition" shape="rect">Definition</a></div>
<div class="toc3">6.8.2 <a href="#within-text-implementation" shape="rect">Implementation</a></div>
<div class="toc3">6.8.3 <a href="#within-text-markup" shape="rect">Markup Declarations for Elements Within Text</a></div>
</div>
</div>
</div>
<h3><a name="appendices" id="appendices" shape="rect"></a>Appendices
</h3>
<div class="toc1">A <a href="#normative-references" shape="rect">References</a></div>
<div class="toc1">B <a href="#informative-references" shape="rect">References</a> (Non-Normative)
</div>
<div class="toc1">C <a href="#its-markup-summary" shape="rect">Summary of ITS Markup</a> (Non-Normative)
</div>
<div class="toc1">D <a href="#its-schemas" shape="rect">Schemas for ITS</a> (Non-Normative)
</div>
<div class="toc1">E <a href="#its-schematron-constraints" shape="rect">Checking ITS Markup Constraints With Schematron</a> (Non-Normative)
</div>
<div class="toc1">F <a href="#its-nvdl-schema" shape="rect">Checking ITS Markup with NVDL</a> (Non-Normative)
</div>
<div class="toc1">G <a href="#revisionlog" shape="rect">Revision Log</a> (Non-Normative)
</div>
<div class="toc1">H <a href="#acknowledgements" shape="rect">Acknowledgements</a> (Non-Normative)
</div>
</div>
<hr />
<div class="body">
<div class="div1">
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="introduction" id="introduction" shape="rect"></a>1 Introduction
</h2>
<p>
<em>This section is informative.</em>
</p>
<p>ITS is a technology to easily create XML which is internationalized and can be localized effectively. On the one hand, the
ITS specification identifies concepts (such as "directionality") which are important for
internationalization and localization. On the other hand, the ITS specification defines implementations of these concepts
(termed "ITS data categories") as a set of elements and attributes called the Internationalization Tag Set (ITS). The document
provides implementations for three schema languages: XML DTD <a title="Extensible Markup Language (XML) 1.0 (Fourth Edition)" href="#xml10spec" shape="rect">[XML 1.0]</a>, XML Schema <a title="XML Schema Part 1:
 Structures Second Edition" href="#xmlschema1" shape="rect">[XML Schema]</a> and RELAX NG <a title="Regular-grammar-based validation -- RELAX NG" href="#relaxng" shape="rect">[RELAX NG]</a>.
</p>
<p>This document aims to realize many of the ideas formulated in <a title="Requirements for Localizable DTD Design" href="#reqlocdtd" shape="rect">[Localizable DTDs]</a>.
</p>
<p>Requirements for this document are formulated in <a title="Internationalization and
 Localization Markup Requirements" href="#itsreq" shape="rect">[ITS REQ]</a>. Not all requirements listed there
are addressed in this document. Those which are not addressed here
are either covered in <a title="Best Practices for XML Internationalization" href="#xml-i18n-bp" shape="rect">[XML i18n BP]</a> or may be addressed in a future
version of this specification.
</p>
<p>This document covers the following requirements:</p>
<ul>
<li>
<p><a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/#span" shape="rect">R002 -
span-like element</a>, see <a href="#span" shape="rect">span</a></p>
</li>
<li>
<p><a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/#langlocale" shape="rect">R006 -
identifying language/locale</a>, see <a class="section-ref" href="#language-information" shape="rect">Section 6.7: Language Information</a></p>
</li>
<li>
<p><a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/#termid" shape="rect">R007 -
identifying Terms</a>, see <a class="section-ref" href="#terminology" shape="rect">Section 6.4: Terminology</a></p>
</li>
<li>
<p><a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/#mapping " shape="rect">R008 -
purpose specification/mapping</a>, see <a class="section-ref" href="#associating-its-with-existing-markup" shape="rect">Section 5.5: Associating ITS Data Categories with Existing Markup</a></p>
</li>
<li>
<p><a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/#bidi " shape="rect">R011 -
bidirectional text support</a>, see <a class="section-ref" href="#directionality" shape="rect">Section 6.5: Directionality</a></p>
</li>
<li>
<p><a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/#transinfo " shape="rect">R012 -
indicator of translatability</a>, see <a class="section-ref" href="#trans-datacat" shape="rect">Section 6.2: Translate</a></p>
</li>
<li>
<p><a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/#impact " shape="rect">R014 -
limited impact</a>, see <a class="section-ref" href="#associating-its-with-existing-markup" shape="rect">Section 5.5: Associating ITS Data Categories with Existing Markup</a></p>
</li>
<li>
<p><a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/#locnotes " shape="rect">R017 -
localization notes</a>, see <a class="section-ref" href="#locNote-datacat" shape="rect">Section 6.3: Localization Note</a></p>
</li>
<li>
<p><a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/#annomark " shape="rect">R020 -
annotation markup</a>, see <a class="section-ref" href="#ruby-annotation" shape="rect">Section 6.6: Ruby</a></p>
</li>
<li>
<p><a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/#elemseg " shape="rect">R025 -
elements and segmentation</a>, see <a class="section-ref" href="#elements-within-text" shape="rect">Section 6.8: Elements Within Text</a></p>
</li>
</ul>
<p>The following requirements will be addressed in <a title="Best Practices for XML Internationalization" href="#xml-i18n-bp" shape="rect">[XML i18n BP]</a>:
</p>
<ul>
<li>
<p><a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/#cdata" shape="rect">R003 -
CDATA Section</a></p>
</li>
<li>
<p><a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/#uid" shape="rect">R004 - Unique
Identifier</a></p>
</li>
<li>
<p><a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/#entities" shape="rect">R005 -
Handling of Entities</a></p>
</li>
<li>
<p><a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/#transattr" shape="rect">R015 -
Attributes and Translatable Text</a></p>
</li>
<li>
<p><a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/#naming" shape="rect">R016 -
Naming Scheme</a></p>
</li>
<li>
<p><a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/#multilang" shape="rect">R019 -
Multilingual Documents</a></p>
</li>
<li>
<p><a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/#nestedelems" shape="rect">R022
- Nested Elements</a></p>
</li>
</ul>
<p> The Working Group decided not to cover the following
requirements
at this time to be able to focus on the most important ones.
</p>
<ul>
<li>
<p><a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/#constraints" shape="rect">R001
- Indicator of Constraints</a></p>
</li>
<li>
<p><a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/#contstyle" shape="rect">R009
- Content Style</a></p>
</li>
<li>
<p><a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/#linkedtext" shape="rect">R010
- Link to Internal/External Text</a></p>
</li>
<li>
<p><a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/#metrics" shape="rect">R013 -
Metrics Count</a></p>
</li>
<li>
<p><a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/#whitespaces" shape="rect">R018
- Handling of White-Spaces</a></p>
</li>
<li>
<p><a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/#datetime" shape="rect">R021
- Identifying Date and Time</a></p>
</li>
<li>
<p><a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/#lingml" shape="rect">R023
- Linguistic Markup
</a></p>
</li>
<li>
<p><a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/#variables" shape="rect">R024 -
Variables</a></p>
</li>
<li>
<p><a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/#objects" shape="rect">R026 -
Associated
Objects</a></p>
</li>
</ul>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="motivation-its" id="motivation-its" shape="rect"></a>1.1 Motivation for ITS
</h3>
<p>Content or software that is authored in one language
(so-called source language) is often made available in
additional languages or adapted with regard to other
cultural aspects. This is done through a process called
localization, where the original material is translated and
adapted to the target audience.
</p>
<p>In addition, document formats expressed by schemas may be
used by people in different parts of the world, and these
people may need special markup to support the local language
or script. For example, people authoring in languages such
as Arabic, Hebrew, Persian or Urdu need special markup to
specify directionality in mixed direction text.
</p>
<p>From the viewpoints of feasibility, cost, and efficiency,
it is important that the original material should be
suitable for localization. This is achieved by appropriate
design and development, and the corresponding process is
referred to as internationalization. For a detailed
explanation of the terms "localization" and
"internationalization", see <a title="" href="#geo-i18n-l10n" shape="rect">[l10n i18n]</a>.
</p>
<p>The increasing usage of XML as a medium for
documentation-related content (e.g. DocBook and DITA as
formats for writing structured documentation, well suited to
computer hardware and software manuals) and software-related
content (e.g. the eXtensible User Interface Language <a title="exTensible User Interface Language" href="#xul" shape="rect">[XUL]</a>) creates challenges and
opportunities in the domain of XML internationalization and
localization.
</p>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="motivation-its-issues" id="motivation-its-issues" shape="rect"></a>1.1.1 Typical Problems
</h4>
<p>The following examples sketch one of the issues that
currently hinder efficient XML-related localization: the
lack of a standard, declarative mechanism which identifies
which parts of an XML document need to be translated. Tools often cannot automatically do this identification.
</p>
<div class="exampleOuter"><a name="d3e317" id="d3e317">Example 1: Document with partially translatable content</a><p>In this document it is difficult to make distinction between the <code>string</code> elements that are translatable and the ones that are not. Only the addition of flags could resolve the issue.
</p>
<div class="exampleInner"><pre xml:space="preserve">
<resources>
<section id="Homepage">
<arguments>
<string>page</string>
<string>childlist</string>
</arguments>
<variables>
<string>POLICY</string>
<string>Corporate Policy</string>
</variables>
<keyvalue_pairs>
<string>Page</string>
<string>ABC Corporation - Policy Repository</string>
<string>Footer_Last</string>
<string>Pages</string>
<string>bgColor</string>
<string>NavajoWhite</string>
<string>title</string>
<string>List of Available Policies</string>
</keyvalue_pairs>
</section>
</resources></pre></div>
<p>[Source file: <a href="EX-motivation-its-1.xml" shape="rect">EX-motivation-its-1.xml</a>]
</p>
</div>
<div class="exampleOuter"><a name="d3e332" id="d3e332">Example 2: Document with partially translatable content</a><p>Even when metadata are available to identify non-translatable text, the conditions may be quite complex and not directly indicated
with a simple flag. Here, for instance, only the text in the nodes matching the expression <code>//component[@type!='image']/data[@type='text']</code> is translatable.
</p>
<div class="exampleInner"><pre xml:space="preserve">
<dialogue xml:lang="en-gb">
<rsrc id="123">
<component id="456" type="image">
<data type="text">images/cancel.gif</data>
<data type="coordinates">12,20,50,14</data>
</component>
<component id="789" type="caption">
<data type="text">Cancel</data>
<data type="coordinates">12,34,50,14</data>
</component>
<component id="792" type="string">
<data type="text">Number of files: </data>
</component>
</rsrc>
</dialogue></pre></div>
<p>[Source file: <a href="EX-motivation-its-2.xml" shape="rect">EX-motivation-its-2.xml</a>]
</p>
</div>
</div>
</div>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="users-usage" id="users-usage" shape="rect"></a>1.2 Users and Usages of ITS
</h3>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="potential-users" id="potential-users" shape="rect"></a>1.2.1 Potential Users of ITS
</h4>
<p>The ITS specification aims to provide different types
of users with information about what markup should be
supported to enable worldwide use and effective
internationalization and localization of content. The following paragraphs sketch
these different types of users, and their usage of
ITS.
</p>
<ul>
<li>
<p>Schema developers who start a schema from ground up </p>
<p>This type of user will find proposals for attribute
and element names to be included in their new schema
(also called "host vocabulary"). Using the attribute and
element names proposed in the ITS specification may be
helpful because it leads to easier recognition of the
concepts represented by both schema users and
processors. It is perfectly possible, however, for a
schema developer to develop his own set of attribute and
element names. The specification sets out, first and
foremost, to ensure that the required markup is available,
and that the behavior of that markup meets established
needs.
</p>
</li>
<li>
<p>Schema developers who work with an existing schema</p>
<p>This type of user will be
working with schemas such as DocBook, DITA, or perhaps a proprietary
schema. The ITS Working Group has sought input from experts developing
widely used formats such as the ones mentioned.
</p>
<div class="note">
<p class="prefix"><b>Note:</b></p>
<p>The question
"How to use ITS with existing popular markup schemes?"
is covered in more details (including examples) in a separate document: <a title="Best Practices for XML Internationalization" href="#xml-i18n-bp" shape="rect">[XML i18n BP]</a>.
</p>
</div>
<p>Developers working on existing schemas
should check whether their schemas support the
markup proposed in this specification, and, where
appropriate, add the markup proposed here to their
schema.
</p>
<p>In some cases, an existing schema may
already contain markup equivalent to that
recommended in ITS. In this case it is not necessary
to add duplicate markup since ITS provides
mechanisms for associating ITS
markup with markup in the host vocabulary which
serves a similar purpose (see <a class="section-ref" href="#associating-its-with-existing-markup" shape="rect">Section 5.5: Associating ITS Data Categories with Existing Markup</a>). The developer should, however,
check that the behavior associated with the markup
in their own schema is fully compatible with the
expectations described in this specification.
</p>
</li>
<li>
<p>Vendors of content-related tools</p>
<p>This type of
user includes companies which provide tools for
authoring, translation or other flavors of
content-related software solutions. It is important to
ensure that such tools enable worldwide use and
effective localization of content. For example,
translation tools should prevent content marked up as
not for translation from being changed or translated. It
is hoped that the ITS specification will make the job of
vendors easier by standardizing the format and
processing expectations of certain relevant markup
items, and allowing them to more effectively identify
how content should be handled.
</p>
</li>
<li>
<p>Content producers</p>
<p>This type of user comprises
authors, translators and other types of content
author. The markup proposed in this specification may
be used by them to mark up specific bits of
content. Aside: The burden of inserting markup can be
removed from content producers by relating the ITS
information to relevant bits of content in a global
manner (see <a href="#selection-global" shape="rect">global,
rule-based approach</a>). This global work, however,
may fall to information architects, rather than the
content producers themselves.
</p>
</li>
</ul>
<p>In order to support all of these users, the information
about what markup should be supported to enable worldwide
use and effective localization of content is provided in
this specification in two ways:
</p>
<ul>
<li>
<p>abstractly in the data category descriptions: <a class="section-ref" href="#datacategory-description" shape="rect">Section 6: Description of Data Categories</a></p>
</li>
<li>
<p>concretely in the ITS schemas: <a class="section-ref" href="#its-schemas" shape="rect">Appendix D: Schemas for ITS</a></p>
</li>
</ul>
</div>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="ways-to-use-its" id="ways-to-use-its" shape="rect"></a>1.2.2 Ways to Use ITS
</h4>
<p>The ITS specification proposes several mechanisms for
supporting worldwide use and effective internationalization and localization of
content. We will sketch them below by looking at them from the
perspectives of certain user types. For the purpose of
illustration, we will demonstrate how ITS can
indicate that certain parts of content should or should
not be translated.
</p>
<ul>
<li>
<p>A content author uses an attribute on a particular
element to say that the text in the element should not
be translated.
</p>
</li>
</ul>
<div class="exampleOuter"><a name="EX-ways-to-use-its-1" id="EX-ways-to-use-its-1">Example 3: Use of ITS by content author</a><p>The <code>its:translate="no"</code> attributes indicate that the <code>path</code> and the <code>cmd</code> elements should not be translated.
</p>
<div class="exampleInner"><pre xml:space="preserve">
<help
xmlns:its="http://www.w3.org/2005/11/its"
its:version="1.0">
<head>
<title>Building the Zebulon Toolkit</title>
</head>
<body>
<p>To re-compile all the modules of the Zebulon toolkit you need to go in the
<path
its:translate="no">\Zebulon\Current Source\binary</path> directory.
Then from there, run batch file <cmd
its:translate="no">Build.bat</cmd>.</p>
</body>
</help></pre></div>
<p>[Source file: <a href="EX-ways-to-use-its-1.xml" shape="rect">EX-ways-to-use-its-1.xml</a>]
</p>
</div>
<ul>
<li>
<p>A content author or information architect uses
markup at the top of the document to identify a
particular type of element or context in which the
content should not be translated.
</p>
</li>
</ul>
<div class="exampleOuter"><a name="d3e435" id="d3e435">Example 4: Use of ITS by information architect</a><p>The <a class="itsmarkup" href="#translateRule" shape="rect">translateRule</a> element is used in the header of the document to indicate that none of the <code>path</code> or <code>cmd</code> elements should be translated.
</p>
<div class="exampleInner"><pre xml:space="preserve">
<help
xmlns:its="http://www.w3.org/2005/11/its"
its:version="1.0">
<head>
<title>Building the Zebulon Toolkit</title>
<its:rules version="1.0">
<its:translateRule selector="//path | //cmd" translate="no"/>
</its:rules>
</head>
<body>
<p>To re-compile all the modules of the Zebulon toolkit you need to go in the
<path>\Zebulon\Current Source\binary</path> directory.
Then from there, run batch file <cmd>Build.bat</cmd>.</p>
</body>
</help></pre></div>
<p>[Source file: <a href="EX-ways-to-use-its-2.xml" shape="rect">EX-ways-to-use-its-2.xml</a>]
</p>
</div>
<ul>
<li>
<p>A processor may insert markup at the top of the
document which links to ITS information outside of the
document.
</p>
</li>
</ul>
<div class="exampleOuter"><a name="d3e460" id="d3e460">Example 5: Use of ITS by processor</a><p>A <a class="itsmarkup" href="#rules" shape="rect">rules</a> element is inserted in the header of the document. It has a XLink <a class="itsmarkup" href="#rules.attributes" shape="rect">href</a> attribute used to link to an <a href="#link-external-rules" shape="rect">ITS external rule</a> document.
</p>
<div class="exampleInner"><pre xml:space="preserve">
<help
xmlns:its="http://www.w3.org/2005/11/its"
xmlns:xlink="http://www.w3.org/1999/xlink"
its:version="1.0">
<head>
<title>Building the Zebulon Toolkit</title>
<its:rules version="1.0" xlink:href="EX-ways-to-use-its-4.xml" xlink:type="simple"/>
</head>
<body>
<p>To re-compile all the modules of the Zebulon toolkit you need to go in the
<path>\Zebulon\Current Source\binary</path> directory.
Then from there, run batch file <cmd>Build.bat</cmd>.</p>
</body>
</help></pre></div>
<p>[Source file: <a href="EX-ways-to-use-its-3.xml" shape="rect">EX-ways-to-use-its-3.xml</a>]
</p>
</div>
<div class="exampleOuter"><a name="d3e481" id="d3e481">Example 6: ITS rule file shared by different documents</a><p>The <a class="itsmarkup" href="#rules" shape="rect">rules</a> element contains several ITS rules that are common to different documents. One of them is a <a class="itsmarkup" href="#translateRule" shape="rect">translateRule</a> element that indicates that no <code>path</code> or <code>cmd</code> element should be translated.
</p>
<div class="exampleInner"><pre xml:space="preserve">
<its:rules
xmlns:its="http://www.w3.org/2005/11/its" version="1.0">
<its:translateRule selector="//path | //cmd" translate="no"/>
</its:rules></pre></div>
<p>[Source file: <a href="EX-ways-to-use-its-4.xml" shape="rect">EX-ways-to-use-its-4.xml</a>]
</p>
</div>
<ul>
<li>
<p>A schema developer integrates ITS markup
declarations in his schema to allow users to indicate
that specific parts of the content should not be
translated.
</p>
</li>
</ul>
<div class="exampleOuter"><a name="d3e509" id="d3e509">Example 7: An XSD schema with ITS declaration</a><p>The declarations for the <a class="itsmarkup" href="#att.local.no-ns.attribute.translate" shape="rect">translate</a> attribute is added to a group of common attributes <code>commonAtts</code>. This allows to use the <a class="itsmarkup" href="#att.local.no-ns.attribute.translate" shape="rect">translate</a> attribute within the documents like in <a href="#EX-ways-to-use-its-1" shape="rect">Example 3</a>.
</p>
<div class="exampleInner"><pre xml:space="preserve">
<xs:schema
xmlns:its="http://www.w3.org/2005/11/its"
xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
<xs:import namespace="http://www.w3.org/2005/11/its" schemaLocation="its.xsd"/>
<xs:attributeGroup name="commonAtts">
<xs:attributeGroup ref="its:att.local.with-ns.attribute.translate"/>
<xs:attribute name="id" type="xs:ID" use="optional"/>
</xs:attributeGroup>
<xs:element name="help">
<xs:complexType>
<xs:sequence>
<xs:element name="head">
<xs:complexType>
<xs:sequence>
<xs:element name="title" type="xs:string"/>
</xs:sequence>
<xs:attributeGroup ref="commonAtts"/>
</xs:complexType>
</xs:element>
<xs:element name="body">
<xs:complexType>
<xs:choice minOccurs="1" maxOccurs="unbounded">
<xs:element name="p">
<xs:complexType mixed="true">
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element ref="path"/>
<xs:element ref="cmd"/>
</xs:choice>
<xs:attributeGroup ref="commonAtts"/>
</xs:complexType>
</xs:element>
</xs:choice>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attributeGroup ref="its:att.version.attribute.version"/>
</xs:complexType>
</xs:element>
<xs:element name="path">
<xs:complexType mixed="true">
<xs:attributeGroup ref="commonAtts"/>
</xs:complexType>
</xs:element>
<xs:element name="cmd">
<xs:complexType mixed="true">
<xs:attributeGroup ref="commonAtts"/>
</xs:complexType>
</xs:element>
</xs:schema></pre></div>
<p>[Source file: <a href="EX-ways-to-use-its-5.xsd" shape="rect">EX-ways-to-use-its-5.xsd</a>]
</p>
</div>
<p>The first two approaches above can be likened to the
use of CSS in <a title="XHTML™ 1.0 The Extensible
 HyperText Markup Language (Second Edition)" href="#xhtml10" shape="rect">[XHTML 1.0]</a>. Using a <code>style</code> attribute,
an XHTML content author may assign a color to a
particular paragraph. That author could also have used the
<code>style</code> element at the top of the page to say that
all paragraphs of a particular class or in a particular
context would be colored red.
</p>
</div>
</div>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="out-of-scope" id="out-of-scope" shape="rect"></a>1.3 Out of Scope
</h3>
<p>This standard does not cover all mechanisms and data formats (sometimes called <span class="new-term">Localization Properties</span>), which might be needed for configuring localization workflows or tools to process a specific format. However, these mechanisms
and data formats may be implemented using the framework described in this standard.
</p>
<div class="note">
<p class="prefix"><b>Note:</b></p>
<p>"XML localization properties" is a generic term to
name the mechanisms and data formats that allow
localization tools to be configured in order to process a
specific XML format. Examples of "XML localization
properties" are the Trados "DTD Settings" file, and the
SDLX "Analysis" file.
</p>
</div>
</div>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="design-decisions" id="design-decisions" shape="rect"></a>1.4 Important Design Principles
</h3>
<p>Abstraction via <em>data categories</em>: ITS defines
data categories as an abstract notion for information for
internationalization and localization of XML schemas and
documents. This abstraction is helpful in realizing
independence from a particular implementation using for example an
element or attribute. See <a class="section-ref" href="#def-datacat" shape="rect">Section 3.3: Data category</a> for a definition of the term data
categories, <a class="section-ref" href="#datacategory-description" shape="rect">Section 6: Description of Data Categories</a> for the definition of the various ITS data
categories, and subsections in <a class="section-ref" href="#datacategory-description" shape="rect">Section 6: Description of Data Categories</a> for the data
category implementations.
</p>
<p> Powerful <em>selection mechanism:</em> For ITS
markup which appears in an XML instance, it has to be
clearly defined to which XML nodes the ITS-related
information pertains. Thus, ITS defines
<a href="#termdef-selection" shape="rect">selection</a> mechanisms to specify to what parts
of an XML document an ITS data category and its values
should be applied. Selection relies on the information which is
given in the XML Information Set <a title="XML Information Set
 (Second Edition)" href="#xmlinfoset" shape="rect">[XML Infoset]</a>. ITS applications may implement inclusion mechanisms
such as XInclude or DITA's <a title="OASIS Darwin Information Typing
Architecture (DITA) Language Specification v1.0" href="#dita10" shape="rect">[DITA 1.0]</a> conref.
</p>
<p>Content authors need, for example, a simple way to work
with the <a href="#trans-datacat" shape="rect">Translate</a> data category in order to express whether the content of an
element or attribute should be translated or
not. Localization coordinators, on the other hand, need an
efficient way of managing translations of large document
sets based on the same schema. This could by realized by a
specification of defaults for the <a href="#trans-datacat" shape="rect">Translate</a> data category and exceptions
from the defaults (e.g. all <code>p</code> elements should be
translated, but not <code>p</code> elements inside of an
<code>index</code> element).
</p>
<p>To meet these requirements this specification introduces mechanisms that add ITS information to XML documents, see <a class="section-ref" href="#its-processing" shape="rect">Section 5: Processing of ITS information</a>. These mechanisms also provide a means for specifying ITS
information for attributes (a task for which no standard
means yet exists).
</p>
<p>The ITS selection mechanisms allows you to provide information about content <a href="#selection-local" shape="rect">locally</a> (specified at the XML node to which it pertains) or <a href="#selection-global" shape="rect">globally</a> (specified in another part of the document). Global selection mechanisms can be in the same document, or in a separate file.
</p>
<p>
<em>No dedicated extensibility</em>: It may be useful
or necessary to extend the set of information available
for internationalization or localization purposes beyond
what is provided by ITS. This specification does not
define a dedicated extension mechanism, since ordinary XML
mechanisms (e.g. XML Namespaces <a title="Namespaces in
 XML (Second Edition)" href="#xmlns" shape="rect">[XML Names]</a>) may be used.
</p>
<p>
<em>Ease of integration</em>:
</p>
<ul>
<li>
<p> ITS follows the example from <a href="http://www.w3.org/TR/2001/REC-xlink-20010627/#att-method" shape="rect">section
4</a> of <a title="XML Linking Language
 1.0" href="#xlink1" shape="rect">[XLink 1.0]</a>, by
providing mostly global attributes for the implementation
of ITS data categories. Avoiding elements for ITS purposes
as much as possible ensures ease of integration into
existing markup schemes, see <a href="http://www.w3.org/TR/itsreq/#impact" shape="rect">section
3.14</a> in <a title="Internationalization and
 Localization Markup Requirements" href="#itsreq" shape="rect">[ITS REQ]</a>. Only
for some requirements do additional child elements have to be
used, see for example <a class="section-ref" href="#ruby-annotation" shape="rect">Section 6.6: Ruby</a>.
</p>
</li>
<li>
<p>ITS has no dependency on technologies which are
still under development
</p>
</li>
<li>
<p>ITS fits with existing work in the W3C architecture
(e.g. use of <a title="XML Path Language (XPath) Version 1.0" href="#xpath" shape="rect">[XPath 1.0]</a> for the selection mechanism)
</p>
</li>
</ul>
</div>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="spec-development" id="spec-development" shape="rect"></a>1.5 Development of this Specification
</h3>
<p>This specification has been developed using the ODD (<em>One Document Does it
all</em>) language of the Text Encoding Initiative (<a title="Text Encoding Initiative Guidelines development
 version (P5)" href="#tei" shape="rect">[TEI]</a>). This is a literate programming language for writing XML schemas, with three characteristics:
</p>
<ol class="depth1">
<li>
<p>The element and attribute set is specified using an XML vocabulary which includes support for macros (like DTD entities, or
schema patterns), a hierarchical class system for attributes and elements, and creation of modules.
</p>
</li>
<li>
<p>The content models for elements and attributes are written using embedded RELAX NG XML notation.</p>
</li>
<li>
<p>Documentation for elements, attributes, value lists etc. is written inline, along with examples and other supporting material.</p>
</li>
</ol>
<p>XSLT transformations are provided by the TEI to create documentation into HTML, XSL FO or LaTeX forms, and to generate RELAX
NG documents and DTD. From the RELAX NG documents, James Clark's <a href="http://www.thaiopensource.com/relaxng/trang.html" shape="rect">trang</a> can be used to create XML Schema documents.
</p>
</div>
</div>
<div class="div1">
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="basic-concepts" id="basic-concepts" shape="rect"></a>2 Basic Concepts
</h2>
<p>
<em>This section is informative.</em>
</p>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="basic-concepts-selection" id="basic-concepts-selection" shape="rect"></a>2.1 Selection
</h3>
<p>Information (e.g. "translate this") captured by ITS markup
(e.g. <code>its:translate='yes'</code>) always pertains to
one or more XML nodes (mainly element and attribute nodes). In
a sense, ITS markup "selects" the XML node(s). Selection may
be explicit or implicit. ITS distinguishes two approaches to
selection: local, and with global rules.
</p>
<p>The mechanisms defined for ITS selection resemble those
defined in <a title="Cascading Style Sheets,
 level 2 revision 1
CSS 2.1 Specification" href="#css2-1" shape="rect">[CSS 2.1]</a>. The local
approach can be compared to the <code>style</code> attribute in
HTML/XHTML, and the approach with global rules is similar to the
<code>style</code> element in HTML/XHTML. In contrast to CSS, ITS uses
XPath for identifying nodes. Thus,
</p>
<ul>
<li>
<p>the local approach puts ITS markup in the relevant
element of the host vocabulary (e.g. the <code>author</code>
element in DocBook)
</p>
</li>
<li>
<p>the <a href="#selection-global" shape="rect">rule-based, global
approach</a> puts the ITS markup in elements defined by
ITS itself (namely the <a class="itsmarkup" href="#rules" shape="rect">rules</a> element)
</p>
</li>
</ul>
<p>ITS markup can be used with XML documents (e.g. a DocBook
article), or schemas (e.g. an XML Schema document for a proprietary document
format). Since each usage defines some specific requirements,
ITS markup may take different shapes.
</p>
<p>The following two examples sketch the distinction between
the local and global approaches.
</p>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="basic-concepts-selection-local" id="basic-concepts-selection-local" shape="rect"></a>2.1.1 Local Approach
</h4>
<p>The document in <a href="#EX-basic-concepts-1" shape="rect">Example 8</a> shows how a content author may use the
ITS <a class="itsmarkup" href="#att.local.no-ns.attribute.translate" shape="rect">translate</a> attribute to indicate
that all content inside the <code>author</code> element should be protected from
translation. Translation tools that are aware of the meaning
of this attribute can then screen the relevant content from
the translation process.
</p>
<div class="exampleOuter"><a name="EX-basic-concepts-1" id="EX-basic-concepts-1">Example 8: ITS markup on elements in an XML document (local approach) </a><div class="exampleInner"><pre xml:space="preserve">
<dbk:article
xmlns:its="http://www.w3.org/2005/11/its"
xmlns:dbk="http://docbook.org/ns/docbook"
its:version="1.0" version="5.0" xml:lang="en">
<dbk:info>
<dbk:title>An example article</dbk:title>
<dbk:author
its:translate="no">
<dbk:personname>
<dbk:firstname>John</dbk:firstname>
<dbk:surname>Doe</dbk:surname>
</dbk:personname>
<dbk:affiliation>
<dbk:address>
<dbk:email>foo@example.com</dbk:email>
</dbk:address>
</dbk:affiliation>
</dbk:author>
</dbk:info>
<dbk:para>This is a short article.</dbk:para>
</dbk:article></pre></div>
<p>[Source file: <a href="EX-basic-concepts-1.xml" shape="rect">EX-basic-concepts-1.xml</a>]
</p>
</div>
<p>For this to work, the schema developer will need to add the
<a class="itsmarkup" href="#att.local.no-ns.attribute.translate" shape="rect">translate</a> attribute to the schema as a common
attribute or on all the relevant element definitions. Note
how there is an expectation in this case that inheritance
plays a part in identifying which content does have to be
translated and which does not. Tools that process this content
for translation will need to implement the expected
inheritance.
</p>
</div>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="basic-concepts-selection-global" id="basic-concepts-selection-global" shape="rect"></a>2.1.2 Global Approach
</h4>
<p>The document in <a href="#EX-basic-concepts-2" shape="rect">Example 9</a> shows a different approach to identifying
non-translatable content, similar to that used with a
<code>style</code> element in <a title="XHTML™ 1.0 The Extensible
 HyperText Markup Language (Second Edition)" href="#xhtml10" shape="rect">[XHTML 1.0]</a>, but using an ITS-defined
element called <a class="itsmarkup" href="#rules" shape="rect">rules</a>. It works as follows: A document
can contain a <a class="itsmarkup" href="#rules" shape="rect">rules</a> element (placed where it does not impact the
structure of the document, like in a "head" section). It contains one or more
ITS rule elements (for example
<a class="itsmarkup" href="#translateRule" shape="rect">translateRule</a>). Each of these specific elements
contains a <a class="itsmarkup" href="#att.selector.attribute.selector" shape="rect">selector</a> attribute. As its name
suggests, this attribute selects the XML node
or nodes to which a corresponding ITS information
pertains. The values of ITS selector attributes are XPath
absolute location paths. Information for the handling of
namespaces in these path expressions is taken from namespace
declarations <a title="Namespaces in
 XML (Second Edition)" href="#xmlns" shape="rect">[XML Names]</a> at the current rules element.
</p>
<div class="note">
<p class="prefix"><b>Note:</b></p>
<p>Caveat Related to XSLT-based Processing of ITS Selector Attributes</p>
<p>
The values of ITS <a class="itsmarkup" href="#att.selector.attribute.selector" shape="rect">selector</a> attributes are XPath absolute location paths.
Accordingly, the following is a legitimate value:
</p>
<p>myElement/descendant-or-self::*/@*</p>
<p>Unfortunately, values like this cause trouble when they are used in
XSLT-based processing of ITS where the values of the ITS <a class="itsmarkup" href="#att.selector.attribute.selector" shape="rect">selector</a> attributes are used as values
of <code>match</code> attributes of XSLT templates. The reason for this is the following: <code>match</code> attributes
may only contain a restriction/subset of XPath expressions, so-called
<a href="http://www.w3.org/TR/xslt#patterns" shape="rect">patterns</a>.
</p>
<p>Basically the following restrictions hold for patterns: </p>
<ul>
<li>
<p>only axes "child" or "attribute" allowed</p>
</li>
<li>
<p>"//" or "/" possible</p>
</li>
<li>
<p>id() or key() function possible</p>
</li>
<li>
<p>predicates possible</p>
</li>
</ul>
<p>Using only XSLT patterns in ITS <a class="itsmarkup" href="#att.selector.attribute.selector" shape="rect">selector</a> attributes helps to avoid this
issue. In many cases, this is possible by using patterns with predicates. The value above
may for example be rewritten as follows:
</p>
<p>*[self::myElement]/@* | myElement//*/@*</p>
</div>
<div class="exampleOuter"><a name="EX-basic-concepts-2" id="EX-basic-concepts-2">Example 9: ITS global markup in an XML document (rule-based approach) </a><div class="exampleInner"><pre xml:space="preserve">
<myTopic
xmlns:its="http://www.w3.org/2005/11/its"
xmlns="myNamescapeURI" id="topic01" xml:lang="en-us">
<prolog>
<title>Using ITS</title>
<its:rules version="1.0">
<its:translateRule selector="//n:term" translate="no"/>
</its:rules>
</prolog>
<body>
<p>ITS defines <term>data category</term> as an abstract
concept for a particular type of information for
internationalization and localization of XML schemas and
documents.</p>
</body>
</myTopic></pre></div>
<p>[Source file: <a href="EX-basic-concepts-2.xml" shape="rect">EX-basic-concepts-2.xml</a>]
</p>
</div>
<p>For this approach to work, the schema developer needs to add the
<a class="itsmarkup" href="#rules" shape="rect">rules</a> element and associated markup to the schema.
</p>
<p>In some cases this may allow the schema developer to avoid adding
other ITS markup (such as an <a class="itsmarkup" href="#att.local.no-ns.attribute.translate" shape="rect">translate</a> attribute)
to the elements in the schema. However, it is likely that
authors will want to use attributes on markup from time to
time to override the general rule.
</p>
<p>For specification of the
<a href="#trans-datacat" shape="rect">Translate</a> data category information, the contents of the
<a class="itsmarkup" href="#rules" shape="rect">rules</a> element would normally be designed by an
information architect familiar with the document format and
familiar with, or working with someone familiar with, the
needs of the localization group.
</p>
<p>The global, rule-based approach has the following
benefits:
</p>
<ul>
<li>
<p>Content authors do not have to concern themselves with
creating additional markup or verifying that the markup was
applied correctly. ITS data categories are associated with
sets of XML nodes (for example all <code>p</code> elements in an
XML instance)
</p>
</li>
<li>
<p>Changes can be done in a single location, rather than
by searching and modifying the markup throughout a document
(or documents, if the <a class="itsmarkup" href="#rules" shape="rect">rules</a> element is stored as an
external entity)
</p>
</li>
<li>
<p>ITS data categories can designate attribute values as
well as elements.
</p>
</li>
<li>
<p>It is possible to associate ITS markup with existing
markup (for example the <code>term</code> element in DITA)
</p>
</li>
</ul>
<p>The commonality in both examples above is the markup
<code>translate='no'</code>. This piece of ITS markup can
be interpreted as follows:
</p>
<ul>
<li>
<p>it pertains to the <a href="#trans-datacat" shape="rect">Translate</a> data category
</p>
</li>
<li>
<p>the attribute <a class="itsmarkup" href="#att.local.no-ns.attribute.translate" shape="rect">translate</a> holds a value of "no"
</p>
</li>
</ul>
<p>The ITS <a class="itsmarkup" href="#att.selector.attribute.selector" shape="rect">selector</a> attribute allows:
</p>
<ul>
<li>
<p>ITS data category attributes to appear in global rules
(even outside of an XML document or schema)
</p>
</li>
<li>
<p>ITS data categories attributes to pertain to sets of
XML nodes (for example all <code>p</code> elements in an XML
document)
</p>
</li>
<li>
<p>ITS markup to pertain to attributes</p>
</li>
<li>
<p>ITS markup to <a href="#associating-its-with-existing-markup" shape="rect">
associate with existing markup</a> (for example the <code>term</code> element in DITA)
</p>
</li>
</ul>
</div>
</div>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="basic-concepts-overinher" id="basic-concepts-overinher" shape="rect"></a>2.2 Overriding and Inheritance
</h3>
<p>The power of the ITS selection mechanisms comes at
a price: rules related to <a href="#selection-precedence" shape="rect">overriding/precedence</a>,
and <a href="#datacategories-defaults-etc" shape="rect">inheritance</a>,
have to be established.
</p>
<p>The document in <a href="#EX-basic-concepts-3" shape="rect">Example 10</a> shows how inheritance and overriding work for the
<a href="#trans-datacat" shape="rect">Translate</a> data category. By default elements are translatable. Here, the <a class="itsmarkup" href="#translateRule" shape="rect">translateRule</a> element declared in the header overrides the default for the <code>head</code> element inside <code>text</code> and for all its children. Because the <code>title</code> element is actually translatable, the global rule needs to be overridden by a local <code>its:translate="yes"</code>. Note that the global rule is processed first, regardless of its position inside the document. In the main body of the document,
the default applies, and here it is <code>its:translate="no"</code> that is used to set "faux pas" as non-translatable.
</p>
<div class="exampleOuter"><a name="EX-basic-concepts-3" id="EX-basic-concepts-3">Example 10: Overriding and Inheritance</a><div class="exampleInner"><pre xml:space="preserve">
<text
xmlns:its="http://www.w3.org/2005/11/its" >
<head>
<revision>Sep-10-2006 v5</revision>
<author>Ealasaidh McIan</author>
<contact>ealasaidh@hogw.ac.uk</contact>
<title
its:translate="yes">The Origins of Modern Novel</title>
<its:rules version="1.0">
<its:translateRule translate="no" selector="/text/head"/>
</its:rules>
</head>
<body>
<div xml:id="intro">
<head>Introduction</head>
<p>It would certainly be quite a <span
its:translate="no">faux pas</span>
to start a dissertation on the origin of modern novel without
mentioning the <tl>Epic of Gilgamesh</tl>...</p>
</div>
</body>
</text></pre></div>
<p>[Source file: <a href="EX-basic-concepts-3.xml" shape="rect">EX-basic-concepts-3.xml</a>]
</p>
</div>
</div>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="basic-concepts-addingpointing" id="basic-concepts-addingpointing" shape="rect"></a>2.3 Adding Information or Pointing to Existing Information
</h3>
<p>For some data categories, special attributes add or point to information about the selected nodes. For example, the <a href="#locNote-datacat" shape="rect">Localization Note</a> data category can add information to selected nodes (using a <a class="itsmarkup" href="#locNote" shape="rect">locNote</a> element), or point at existing information elsewhere in the document (using a <a class="itsmarkup" href="#locNoteRule.attributes" shape="rect">locNotePointer</a> attribute).
</p>
<p>The functionality of adding information to the selected
nodes is available for each data category except <a href="#language-information" shape="rect">Language Information</a>. Pointing to
existing information is not possible for data categories that
express <em>a closed set of values</em>; that is: <a href="#trans-datacat" shape="rect">Translate</a>, <a href="#directionality" shape="rect">Directionality</a> and <a href="#elements-within-text" shape="rect">Elements Within Text</a>.
</p>
<p>The functionalities of adding information and pointing to
existing information are <em>mutually exclusive</em>. That
is to say, attributes for pointing and adding must not appear
at the same rule element.
</p>
</div>
</div>
<div class="div1">
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="notation-terminology" id="notation-terminology" shape="rect"></a>3 Notation and Terminology
</h2>
<p>
<em>This section is normative.</em>
</p>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="notation" id="notation" shape="rect"></a>3.1 Notation
</h3>
<p id="rfc-keywords">The keywords "MUST", "MUST NOT",
"REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
"RECOMMENDED", "MAY", and "OPTIONAL" in this document are to
be interpreted as described in <a title="" href="#rfc2119" shape="rect">[RFC 2119]</a>.
</p>
<p>The namespace URI that <a href="#rfc-keywords" shape="rect">MUST</a>
be used by implementations of this specification is:
</p>
<div class="exampleInner"><pre xml:space="preserve">http://www.w3.org/2005/11/its</pre></div>
<p>The namespace prefix used in this specification for this
URI is "its". It is recommended that implementations of this
specification use this prefix.
</p>
<p>In addition, the following namespaces are used in this
document:
</p>
<ul>
<li>
<p><code>http://www.w3.org/2001/XMLSchema</code> for
the XML Schema namespace, here used with the prefix
"xs"
</p>
</li>
<li>
<p><code>http://relaxng.org/ns/structure/1.0</code> for
the RELAX NG namespace, here used with the prefix
"rng"
</p>
</li>
<li>
<p><code>http://www.w3.org/1999/xlink</code> for the XLink namespace, here used with the prefix "xlink"
</p>
</li>
</ul>
</div>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="def-schemalanguage" id="def-schemalanguage" shape="rect"></a>3.2 Schema Language
</h3>
<p>
[<a name="t001" id="t001" title="schema" shape="rect">Definition</a>:
<span class="new-term">Schema language</span> refers in this
specification to an XML-related modeling or validation
language such as XML DTD, XML Schema or RELAX
NG.]
</p>
<div class="note">
<p class="prefix"><b>Note:</b></p>
<p>This specification provides schemas in the format of
XML DTD, XML Schema or RELAX NG. However, these schemas
are only non-normative; <a href="#conformance-product-schema" shape="rect">conformance for ITS
markup declarations</a> defines only mandatory positions
of ITS declarations in schemas. This makes it possible to
use ITS with any schema language that allows for using
these positions.
</p>
</div>
</div>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="def-datacat" id="def-datacat" shape="rect"></a>3.3 Data category
</h3>
<p>
[<a name="t002" id="t002" title="data category" shape="rect">Definition</a>: ITS
defines <span class="new-term">data category</span> as an abstract concept
for a particular type of information for
internationalization and localization of XML schemas and
documents.] The concept of a data category is
independent of its implementation in an XML environment
(e.g. using an element or attribute).
</p>
<p>For each data category, ITS distinguishes between the
following:
</p>
<ul>
<li>
<p>the prose description, see <a class="section-ref" href="#datacategory-description" shape="rect">Section 6: Description of Data Categories</a></p>
</li>
<li>
<p>schema language independent formalization, see the
"markup declarations" subsections in <a class="section-ref" href="#datacategory-description" shape="rect">Section 6: Description of Data Categories</a></p>
</li>
<li>
<p>schema language specific implementations, see <a class="section-ref" href="#its-schemas" shape="rect">Appendix D: Schemas for ITS</a></p>
</li>
</ul>
<div class="exampleOuter"><a name="d3e1090" id="d3e1090">Example 11: A data category and its implementation</a><p>The <a href="#trans-datacat" shape="rect">Translate</a> data category conveys
information as to whether a piece of content should be
translated or not.
</p>
<p>The simplest formalization of this prose description on
a schema language independent level is a
<a class="itsmarkup" href="#att.local.no-ns.attribute.translate" shape="rect">translate</a> attribute with two possible values:
"yes" and "no". An implementation on a
schema language specific level would be the declaration of
the <a class="itsmarkup" href="#att.local.no-ns.attribute.translate" shape="rect">translate</a> attribute in, for example, an XML DTD, an
XML Schema document or an RELAX NG document. A different implementation would be a <a class="itsmarkup" href="#translateRule" shape="rect">translateRule</a> element that allows for specifying <a href="#selection-global" shape="rect">global rules</a> about the <a href="#trans-datacat" shape="rect">Translate</a> data category.
</p>
</div>
</div>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="def-selection" id="def-selection" shape="rect"></a>3.4 Selection
</h3>
<p>
[<a name="termdef-selection" id="termdef-selection" title="Selection" shape="rect">Definition</a>:
<span class="new-term">selection</span> encompasses
mechanisms to specify to what parts of an XML document an
ITS data category and its values should be applied
to.] Selection is discussed in detail in <a class="section-ref" href="#its-processing" shape="rect">Section 5: Processing of ITS information</a>. Selection can be
applied globally, see <a class="section-ref" href="#selection-global" shape="rect">Section 5.2.1: Global, Rule-based Selection</a>, and locally, see <a class="section-ref" href="#selection-local" shape="rect">Section 5.2.2: Local Selection in an XML Document</a>. As for global
selection, ITS information can be <a href="#def-adding-pointing" shape="rect">added</a> to the selected
nodes, or it can <a href="#def-adding-pointing" shape="rect">point to
existing information</a> which is related to selected
nodes.
</p>
<p id="selection-and-inclusion-mechanisms">Selection relies on the information that is
given in the XML Information Set <a title="XML Information Set
 (Second Edition)" href="#xmlinfoset" shape="rect">[XML Infoset]</a>. ITS applications <a href="#rfc-keywords" shape="rect">MAY</a> implement inclusion mechanisms
such as XInclude or DITA's <a title="OASIS Darwin Information Typing
Architecture (DITA) Language Specification v1.0" href="#dita10" shape="rect">[DITA 1.0]</a> conref.
</p>
<div class="note">
<p class="prefix"><b>Note:</b></p>
<p id="note-object-selection">The selection of the ITS data categories applies to textual values contained within element or attribute nodes. In
some cases these nodes form pointers to other resources; a well-known
example is the <code>src</code> attribute on the <code>img</code> element in
HTML. The ITS <a href="#trans-datacat" shape="rect">Translate</a> data category applies to the
text of the pointer itself, not the object to which it points. Thus in
the following example, the translation information specified via the <a class="itsmarkup" href="#translateRule" shape="rect">translateRule</a> element applies to the filename
"instructions.jpg", and is not an instruction to open the
graphic and change the words therein.
</p>
<div class="exampleOuter"><a name="d3e1173" id="d3e1173">Example 12: Selecting the text of a pointer to an external object</a><div class="exampleInner"><pre xml:space="preserve">
<text
xmlns:its="http://www.w3.org/2005/11/its" >
<its:rules version="1.0">
<its:translateRule translate="yes" selector="//p/img/@src"/>
</its:rules> ...
<p>As you can see in
<img src="instructions.jpg"/>,
the truth is not always out there.</p>
</text></pre></div>
<p>[Source file: <a href="EX-notation-terminology-1.xml" shape="rect">EX-notation-terminology-1.xml</a>]
</p>
</div>
</div>
</div>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="iri-usage" id="iri-usage" shape="rect"></a>3.5 Usage of Internationalized Resource Identifiers in ITS
</h3>
<p>The
attributes <a class="itsmarkup" href="#rules.attributes" shape="rect">href</a>, <a class="itsmarkup" href="#locNoteRule.attributes" shape="rect">locNoteRef</a> and <a class="itsmarkup" href="#termRule.attributes" shape="rect">termInfoRef</a> which contain resource identifiers <a href="#rfc-keywords" shape="rect">MUST</a> allow the usage of Internationalized Resource Identifiers (IRIs, <a title="Internationalized Resource Identifiers (IRIs)" href="#rfc3987" shape="rect">[RFC 3987]</a> or its successor) to ease the adoption of ITS
in international application scenarios.
</p>
<div class="note">
<p class="prefix"><b>Note:</b></p>
<p>The ITS schemas in <a class="section-ref" href="#its-schemas" shape="rect">Appendix D: Schemas for ITS</a> are not
normative. Hence this specification defines no validation requirements for IRI values in ITS markup. For processing of these
values, relying on IRIs imposes no specific
requirements. The reason is that the processing happens on the info set level <a title="XML Information Set
 (Second Edition)" href="#xmlinfoset" shape="rect">[XML Infoset]</a>, where no difference between IRIs and URIs exists.
</p>
</div>
</div>
</div>
<div class="div1">
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="conformance" id="conformance" shape="rect"></a>4 Conformance
</h2>
<p>
<em>This section is normative.</em>
</p>
<p>The usage of the term <em>conformance clause</em> in
this section is in compliance with <a title="QA Framework:
 Specification Guidelines" href="#qa-framework" shape="rect">[QAFRAMEWORK]</a>.
</p>
<p>This specification defines two types of conformance:
conformance of <a href="#conformance-product-schema" shape="rect">1)
ITS markup declarations</a> , and conformance of <a href="#conformance-product-processing-expectations" shape="rect">2)
processing expectations for ITS Markup</a>. These
conformance types complement each other. An implementation of
this specification <a href="#rfc2119" shape="rect">MAY</a> use them
separately or together.
</p>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="conformance-product-schema" id="conformance-product-schema" shape="rect"></a>4.1 Conformance Type 1: ITS Markup Declarations
</h3>
<p>
<em>Description:</em> ITS markup declarations
encompass all declarations that are part of the
Internationalization Tag Set. They do not concern the
<em>usage</em> of the markup in XML documents. Such
markup is subject to the conformance clauses in <a class="section-ref" href="#conformance-product-processing-expectations" shape="rect">Section 4.2: Conformance Type 2: The Processing Expectations for ITS Markup</a>.
</p>
<p>
<em>Definitions related to this conformance
type:</em> ITS markup declarations are defined in various
subsections in <a class="section-ref" href="#its-processing" shape="rect">Section 5: Processing of ITS information</a> and
<a class="section-ref" href="#datacategory-description" shape="rect">Section 6: Description of Data Categories</a>
(e.g. <a class="section-ref" href="#locNote-markup" shape="rect">Section 6.3.3: Markup Declarations for Localization Note</a>) in a
schema language independent manner, relying on the ODD
language. Their occurrence in other sections of this
document is typographically marked via bold face and
color.
</p>
<p>
<em>Who uses this conformance type:</em> Schema
designers integrating ITS markup declarations into a
schema. All conformance clauses for this conformance type
concern the position of ITS markup declarations in that
schema, and their status as mandatory or optional.
</p>
<p>
<em>Conformance clauses:</em>
</p>
<ul>
<li>
<p id="its-conformance-1-1">
<em>1-1:</em> At least one of the following <a href="#rfc-keywords" shape="rect">MUST</a>
be in the schema:
</p>
<ul>
<li>
<p><a class="itsmarkup" href="#rules" shape="rect">rules</a> element
</p>
</li>
<li>
<p>one of the <a href="#span.attributes" shape="rect">local
ITS attributes</a></p>
</li>
<li>
<p><a class="itsmarkup" href="#span" shape="rect">span</a> element
</p>
</li>
<li>
<p><a class="itsmarkup" href="#ruby" shape="rect">ruby</a> element
</p>
</li>
</ul>
</li>
<li>
<p id="its-conformance-1-2">
<em>1-2:</em> If the <a class="itsmarkup" href="#rules" shape="rect">rules</a> element is
used, it <a href="#rfc-keywords" shape="rect">MUST</a> be part of the
content model of at least one element declared in the
schema. It <a href="#rfc-keywords" shape="rect">SHOULD</a> be in a
content model for meta information, if this is available
in that schema (e.g. the <code>head</code> element in
<a title="XHTML™ 1.0 The Extensible
 HyperText Markup Language (Second Edition)" href="#xhtml10" shape="rect">[XHTML 1.0]</a>).
</p>
</li>
<li>
<p id="its-conformance-1-3">
<em>1-3:</em> If the <a class="itsmarkup" href="#ruby" shape="rect">ruby</a> element is
used, it <a href="#rfc-keywords" shape="rect">SHOULD</a> be declared
as an inline element.
</p>
</li>
<li>
<p id="its-conformance-1-4">
<em>1-4:</em> If the <a class="itsmarkup" href="#span" shape="rect">span</a> element is
used, it <a href="#rfc-keywords" shape="rect">SHOULD</a> be declared
as an inline element.
</p>
</li>
</ul>
<p id="its-markup-conformance-claims">Full
implementations of this conformance type will implement all
markup declarations for ITS. Statements related to this
conformance type <a href="#rfc-keywords" shape="rect">MUST</a> list all
markup declarations they implement.
</p>
<p>
<em>Examples: </em> Examples of the usage of ITS
markup declarations in various existing schemas are given in
a separate document <a title="Best Practices for XML Internationalization" href="#xml-i18n-bp" shape="rect">[XML i18n BP]</a>.
</p>
<div class="note">
<p class="prefix"><b>Note:</b></p>
<p>Since the ITS markup declarations are schema language
independent, each schema language can use its own,
possibly multiple, mechanisms to implement the conformance
clauses for ITS markup declarations. For example, an XML
DTD can use parameter entities to encapsulate the <a href="#span.attributes" shape="rect">ITS local attributes</a>, or
declare them directly for each element. The appropriate
steps to integrate ITS into a schema depend on the design
of this schema (e.g. whether it already has a
customization layer that uses parameter entities). The
ITS schemas in the format of XML DTD, XML Schema and RELAX
NG in <a class="section-ref" href="#its-schemas" shape="rect">Appendix D: Schemas for ITS</a> are only
informative examples.
</p>
</div>
</div>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="conformance-product-processing-expectations" id="conformance-product-processing-expectations" shape="rect"></a>4.2 Conformance Type 2: The Processing Expectations for ITS Markup
</h3>
<p>
<em>Description:</em> Processors need to compute the
ITS information that pertains to a node in an XML
document. The ITS processing expectations define how the
computation has to be carried out. Correct computation
involves support for <a href="#def-selection" shape="rect">selection
mechanism</a>, <a href="#datacategories-defaults-etc" shape="rect">defaults / inheritance / overriding characteristics</a>, and <a href="#selection-precedence" shape="rect">precedence</a>. The markup
<a href="#rfc-keywords" shape="rect">MAY</a> be valid against a schema
which conforms to the clauses in <a class="section-ref" href="#conformance-product-schema" shape="rect">Section 4.1: Conformance Type 1: ITS Markup Declarations</a>.
</p>
<p>
<em>Definitions related to this conformance
type:</em> The processing expectations for ITS markup make
use of selection mechanisms defined in <a class="section-ref" href="#its-processing" shape="rect">Section 5: Processing of ITS information</a>. The individual data
categories defined in <a class="section-ref" href="#datacategory-description" shape="rect">Section 6: Description of Data Categories</a> have <a href="#datacategories-defaults-etc" shape="rect">defaults / inheritance / overriding characteristics</a>,
and allow for using ITS markup in various positions (<a href="#selection-global" shape="rect">global</a> and <a href="#selection-local" shape="rect">local</a>).
</p>
<p>
<em>Who uses this conformance type:</em> Applications
that need to process for internationalization or
localization the nodes captured by a data category. Examples
of this type of application are: ITS markup-aware editors,
or translation tools that make use of ITS markup to filter
translatable text as an input to the localization
process.
</p>
<div class="note">
<p class="prefix"><b>Note:</b></p>
<p> Application-specific processing (that is processing
that goes beyond the computation of ITS information for a
node) such as automated filtering of translatable content
based on the <a href="#trans-datacat" shape="rect">Translate</a> data category is not covered by the conformance clauses
below.
</p>
</div>
<div class="note">
<p class="prefix"><b>Note:</b></p>
<p>
The ITS Working group provides a
<a href="http://www.w3.org/International/its/tests/" shape="rect">
test suite
</a>
to help implementers to write applications that
support the ITS specifications. The test suite
provides pairs of input and output files.
</p>
</div>
<p>
<em>Conformance clauses:</em>
</p>
<ul>
<li>
<p id="its-conformance-2-1">
<em>2-1:</em> A processor <a href="#rfc-keywords" shape="rect">
MUST</a> implement at least one <a href="#def-datacat" shape="rect">data category</a>.
For each implemented <a href="#def-datacat" shape="rect">data category</a>, the following
<a href="#rfc-keywords" shape="rect">MUST</a> be taken into account:
</p>
<ul>
<li>
<p id="its-conformance-2-1-1">
<em>2-1-1:</em>
processing of at least one selection mechanism (<a href="#selection-global" shape="rect">global</a> or <a href="#selection-local" shape="rect">local</a>).
</p>
</li>
<li>
<p id="its-conformance-2-1-2">
<em>2-1-2:</em> the
<a href="#datacategories-defaults-etc" shape="rect">default
selections for the data category</a>.
</p>
</li>
<li>
<p id="its-conformance-2-1-3">
<em>2-1-3:</em> the
precedence definitions for selections defined in <a class="section-ref" href="#selection-precedence" shape="rect">Section 5.4: Precedence between Selections</a>, for
the type of selections it processes.
</p>
</li>
</ul>
</li>
<li>
<p id="its-conformance-2-2">
<em>2-2:</em> If an application claims to
process ITS markup for the global selection mechanism, it
<a href="#rfc-keywords" shape="rect">MUST</a> process an XLink
<a class="itsmarkup" href="#rules.attributes" shape="rect">href</a> attribute found on a <a class="itsmarkup" href="#rules" shape="rect">rules</a>
elements.
</p>
</li>
</ul>
<p id="its-processing-conformance-claims">Statements
related to this conformance type <a href="#rfc-keywords" shape="rect">MUST</a> list all <a href="#def-datacat" shape="rect">data categories</a> they implement,
and for each <a href="#def-datacat" shape="rect">data category</a>
which type of selection they support.
</p>
</div>
</div>
<div class="div1">
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="its-processing" id="its-processing" shape="rect"></a>5 Processing of ITS information
</h2>
<p>
<em>This section is normative.</em>
</p>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="its-version-attribute" id="its-version-attribute" shape="rect"></a>5.1 Indicating the Version of ITS
</h3>
<p>The version of the ITS schema defined in this specification is
"1.0". The version is indicated by the ITS
<a class="itsmarkup" href="#att.version.attribute.version" shape="rect">version</a> attribute. This attribute is mandatory for the
<a class="itsmarkup" href="#rules" shape="rect">rules</a> element, where it <a href="#rfc-keywords" shape="rect">MUST</a> be in no namespace. If there is no <a class="itsmarkup" href="#rules" shape="rect">rules</a> element in an
XML document, a prefixed ITS <a class="itsmarkup" href="#att.version.attribute.version" shape="rect">version</a> attribute
(e.g. <code>its:version</code>) <a href="#rfc-keywords" shape="rect">MUST</a> be provided at the
root element of the document. If there is both a <a class="itsmarkup" href="#att.version.attribute.version" shape="rect">version</a>
attribute at the root element and a <a class="itsmarkup" href="#rules" shape="rect">rules</a> element in a
document, they <a href="#rfc-keywords" shape="rect">MUST NOT</a> specify
different versions.
</p>
<p>Each XML document can have a different
version. That is: if external rules are linked via an XLink
<a class="itsmarkup" href="#rules.attributes" shape="rect">href</a> attribute on the <a class="itsmarkup" href="#rules" shape="rect">rules</a> element, they can
specify a different version than the <a class="itsmarkup" href="#rules" shape="rect">rules</a> element.
</p>
</div>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="datacategory-locations" id="datacategory-locations" shape="rect"></a>5.2 Locations of Data Categories
</h3>
<p>ITS data categories can appear in two places:</p>
<ul>
<li>
<p><a href="#selection-global" shape="rect">Global rules</a>:
the selection is realized within a <a class="itsmarkup" href="#rules" shape="rect">rules</a>
element. It contains <a href="#rules.content" shape="rect">rule
elements</a> for each data category. Each rule element
has a <a class="itsmarkup" href="#att.selector.attribute.selector" shape="rect">selector</a> attribute and possibly other
attributes. The <a class="itsmarkup" href="#att.selector.attribute.selector" shape="rect">selector</a> attribute contains an<a href="http://www.w3.org/TR/xpath#NT-AbsoluteLocationPath" shape="rect">
AbsoluteLocationPath</a> as described in <a href="#xpath" shape="rect">XPath 1.0</a> or its successor.
</p>
</li>
<li>
<p><a href="#selection-local" shape="rect">Locally in a
document</a>: the selection is realized using <a href="#span.attributes" shape="rect">ITS local attributes</a>,
which are attached to an element node, or the <a class="itsmarkup" href="#span" shape="rect">span</a> or <a class="itsmarkup" href="#ruby" shape="rect">ruby</a> element. There is no
additional <a class="itsmarkup" href="#att.selector.attribute.selector" shape="rect">selector</a> attribute. The default
selection for each data category defines whether the
selection covers attributes and child elements. See <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 6.1: Position, Defaults, Inheritance and Overriding of Data Categories</a>.
</p>
</li>
</ul>
<p>The two locations are described in detail below.</p>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="selection-global" id="selection-global" shape="rect"></a>5.2.1 Global, Rule-based Selection
</h4>
<p>Global, rule-based selection is implemented using the
<a class="itsmarkup" href="#rules" shape="rect">rules</a> element. It contains zero or more <a href="#rules.content" shape="rect">rule elements</a>. Each <a href="#rules.content" shape="rect">rule element</a> has a mandatory
<a class="itsmarkup" href="#att.selector.attribute.selector" shape="rect">selector</a> attribute. This attribute and all other possible attributes on <a href="#rules.content" shape="rect">rule elements</a> are in the empty namespace and used without a prefix.
</p>
<p>If there is more than one <a class="itsmarkup" href="#rules" shape="rect">rules</a> element in an XML document, the rules from each section are to be processed at the same precedence level. The <a class="itsmarkup" href="#rules" shape="rect">rules</a> sections are to be read in document order, and the ITS rules with them processed sequentially. The versions of these <a class="itsmarkup" href="#rules" shape="rect">rules</a> elements <a href="#rfc-keywords" shape="rect">MUST NOT</a> be different.
</p>
<p id="def-adding-pointing">Depending on the data
category and its usage, there are additional attributes
for adding information to the selected nodes, or for
pointing to existing information in the document. For
example, the <a href="#locNote-datacat" shape="rect">Localization Note</a> data category can be used for adding notes to
selected nodes, or for pointing to existing notes in
the document. For the former purpose, a <a class="itsmarkup" href="#locNote" shape="rect">locNote</a>
element can be used. For the latter purpose, a
<a class="itsmarkup" href="#locNoteRule.attributes" shape="rect">locNotePointer</a> attribute can be used.
</p>
<p>Each data category allows you to add information to the
selected nodes except for <a href="#language-information" shape="rect">language
information</a>. Pointing to existing information is not
possible for data categories that express <em>a closed
set of values</em>, that is: <a href="#trans-datacat" shape="rect">Translate</a>, <a href="#directionality" shape="rect">Directionality</a> and <a href="#elements-within-text" shape="rect">Elements Within Text</a>.
</p>
<p>The functionalities of adding information and pointing
to existing information are <em>mutually
exclusive</em>. That is: markup for pointing and adding
<a href="#rfc-keywords" shape="rect">MUST NOT</a> appear in the same
rule element.
</p>
<p>
Another difference between adding and
pointing is the usage of XPath:
</p>
<ul>
<li>
<p>The value of the <a class="itsmarkup" href="#att.selector.attribute.selector" shape="rect">selector</a> attribute <a href="#rfc-keywords" shape="rect">MUST</a> be an XPath expression
which starts with "<code>/</code>". That is, it must
be an <a href="http://www.w3.org/TR/xpath#NT-AbsoluteLocationPath" shape="rect">
AbsoluteLocationPath</a> as described in <a href="#xpath" shape="rect">XPath 1.0</a> or its successor. This ensures that
the selection is not relative to a specific
location. The resulting nodes <a href="#rfc-keywords" shape="rect">MUST</a> be either element or
attribute nodes.
</p>
</li>
<li>
<p>Attributes that point to existing information in the document, i.e. attributes whose name ends in <code>...Pointer</code>, <a href="#rfc-keywords" shape="rect">MUST</a> use a RelativeLocationPath as described in <a href="#xpath" shape="rect">XPath 1.0</a> or its successor. The XPath expression is evaluated relative to the nodes selected by the selector attribute. The following
attributes point to existing information: <a class="itsmarkup" href="#locNoteRule.attributes" shape="rect">locNotePointer</a>, <a class="itsmarkup" href="#locNoteRule.attributes" shape="rect">locNoteRefPointer</a>, <a class="itsmarkup" href="#termRule.attributes" shape="rect">termInfoPointer</a>, <a class="itsmarkup" href="#termRule.attributes" shape="rect">termInfoRefPointer</a>, <a class="itsmarkup" href="#rubyRule.attributes" shape="rect">rubyPointer</a>, <a class="itsmarkup" href="#rubyRule.attributes" shape="rect">rtPointer</a>, <a class="itsmarkup" href="#rubyRule.attributes" shape="rect">rpPointer</a>, <a class="itsmarkup" href="#rubyRule.attributes" shape="rect">rbcPointer</a>, <a class="itsmarkup" href="#rubyRule.attributes" shape="rect">rtcPointer</a>, <a class="itsmarkup" href="#rubyRule.attributes" shape="rect">rbspanPointer</a>, <a class="itsmarkup" href="#langRule.attributes" shape="rect">langPointer</a>.
</p>
</li>
</ul>
<p>If namespaces <a title="Namespaces in
 XML (Second Edition)" href="#xmlns" shape="rect">[XML Names]</a> are
used in XPath expressions in the <a class="itsmarkup" href="#att.selector.attribute.selector" shape="rect">selector</a>
attribute or the pointing attributes, the following rules
<a href="#rfc-keywords" shape="rect">MUST</a> be applied while
processing XPath:
</p>
<ol class="depth1">
<li>
<p>For each prefix, there <a href="#rfc-keywords" shape="rect">MUST</a> be an <a class="itsmarkup" href="#rules.attributes" shape="rect">xmlns</a> attribute at the same rule element which allows to resolve the namespace URI of the prefix.
</p>
</li>
<li>
<p>Element and attribute names without a prefix are
interpreted as having no namespace.
</p>
</li>
<li>
<p>To avoid a conflict with rule 2., default
namespaces <a href="#rfc-keywords" shape="rect">MUST NOT</a> be
used in the XPath expressions.
</p>
</li>
</ol>
<div class="exampleOuter"><a name="d3e1784" id="d3e1784">Example 13: XPath expressions with namespaces</a><p>The <code>term</code> element from the TEI is in a
namespace <code>http://www.tei-c.org/ns/1.0</code>.
</p>
<div class="exampleInner"><pre xml:space="preserve">
<its:rules
xmlns:its="http://www.w3.org/2005/11/its"
xmlns:tei="http://www.tei-c.org/ns/1.0" version="1.0">
<its:termRule selector="//tei:term" term="yes"/>
</its:rules></pre></div>
<p>[Source file: <a href="EX-selection-global-1.xml" shape="rect">EX-selection-global-1.xml</a>]
</p>
</div>
<div class="exampleOuter"><a name="d3e1803" id="d3e1803">Example 14: XPath expressions without namespaces</a><p>The <code>qterm</code> element from DocBook is in no
namespace.
</p>
<div class="exampleInner"><pre xml:space="preserve">
<its:rules
xmlns:its="http://www.w3.org/2005/11/its" version="1.0">
<its:termRule selector="//qterm" term="yes"/>
</its:rules></pre></div>
<p>[Source file: <a href="EX-selection-global-2.xml" shape="rect">EX-selection-global-2.xml</a>]
</p>
</div>
<p>Global rules can appear in the XML document they will
be applied to, or in a separate XML document. The
precedence of their processing depends on these
variations. See also <a class="section-ref" href="#selection-precedence" shape="rect">Section 5.4: Precedence between Selections</a>.
</p>
<p>Markup for global, rule-based selection is defined as
follows.
</p>
<dl>
<dt class="label">rules</dt>
<dd>
<table class="scrap" summary="Scrap">
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="rules" id="rules" shape="rect"></a>[1]
</td>
<td rowspan="1" colspan="1"><code>rules</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> element its:rules { rules.content, <a href="#rules.attributes" shape="rect">rules.attributes</a> }</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="rules.content" id="rules.content" shape="rect"></a>[2]
</td>
<td rowspan="1" colspan="1"><code>rules.content</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
(
<a href="#translateRule" shape="rect">translateRule</a>
| <a href="#locNoteRule" shape="rect">locNoteRule</a>
| <a href="#termRule" shape="rect">termRule</a>
| <a href="#dirRule" shape="rect">dirRule</a>
| <a href="#rubyRule" shape="rect">rubyRule</a>
| <a href="#langRule" shape="rect">langRule</a>
| <a href="#withinTextRule" shape="rect">withinTextRule</a>
)*</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="rules.attributes" id="rules.attributes" shape="rect"></a>[3]
</td>
<td rowspan="1" colspan="1"><code>rules.attributes</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
attribute version { xsd:float },
attribute xlink:href { xsd:anyURI }?,
attribute xlink:type { "simple" }?</code></td>
</tr>
</tbody>
</table>
</dd>
<dt class="label"><a name="att.selector" id="att.selector" shape="rect"></a>att.selector
</dt>
<dd>
<table class="scrap" summary="Scrap">
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.selector.attributes" id="att.selector.attributes" shape="rect"></a>[4]
</td>
<td rowspan="1" colspan="1"><code>att.selector.attributes</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#att.selector.attribute.selector" shape="rect">att.selector.attribute.selector</a>
</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.selector.attribute.selector" id="att.selector.attribute.selector" shape="rect"></a>[5]
</td>
<td rowspan="1" colspan="1"><code>att.selector.attribute.selector</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> attribute selector { string }</code></td>
</tr>
</tbody>
</table>
</dd>
<dt class="label"><a name="att.version" id="att.version" shape="rect"></a>att.version
</dt>
<dd>
<table class="scrap" summary="Scrap">
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.version.attributes" id="att.version.attributes" shape="rect"></a>[6]
</td>
<td rowspan="1" colspan="1"><code>att.version.attributes</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#att.version.attribute.version" shape="rect">att.version.attribute.version</a>
</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.version.attribute.version" id="att.version.attribute.version" shape="rect"></a>[7]
</td>
<td rowspan="1" colspan="1"><code>att.version.attribute.version</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> attribute its:version { xsd:float }</code></td>
</tr>
</tbody>
</table>
</dd>
</dl>
</div>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="selection-local" id="selection-local" shape="rect"></a>5.2.2 Local Selection in an XML Document
</h4>
<p>Local selection in XML documents is realized with <a href="#att.local.with-ns.attributes" shape="rect">local ITS attributes</a>, the
<a class="itsmarkup" href="#ruby" shape="rect">ruby</a> element, or the <a class="itsmarkup" href="#span" shape="rect">span</a>
element. <a class="itsmarkup" href="#span" shape="rect">span</a> serves just as a carrier for the
local ITS attributes and a container for <a class="itsmarkup" href="#ruby" shape="rect">ruby</a>.
</p>
<p>The content model of <a class="itsmarkup" href="#span" shape="rect">span</a> permits arbitrary nesting of ruby markup, since the <a class="itsmarkup" href="#rb" shape="rect">rb</a> and <a class="itsmarkup" href="#rt" shape="rect">rt</a> elements themselves can contain <a class="itsmarkup" href="#span" shape="rect">span</a>. An application of ruby <a href="#rfc-keywords" shape="rect">MUST</a> not use such arbitrary nesting.
</p>
<p>The data category determines what is being selected.
The necessary data category specific defaults
are described in <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 6.1: Position, Defaults, Inheritance and Overriding of Data Categories</a>.
</p>
<div class="exampleOuter"><a name="EX-selection-local-1" id="EX-selection-local-1">Example 15: Defaults for various data categories</a><p>By default the content of all elements in a document is translatable. The attribute <code>its:translate="no"</code> in the <code>head</code> element means that the content of this element, including child elements, should not be translated. The attribute <code>its:translate="yes"</code> in the <code>title</code> element means that the content of this element, should be translated (overriding the <code>its:translate="no"</code> in <code>head</code>). Attribute values of the selected elements or their children are not affected by local <a class="itsmarkup" href="#att.local.no-ns.attribute.translate" shape="rect">translate</a> attributes. By default they are not translatable.
</p>
<p>The default directionality of a document is left-to-right. The <code>its:dir="rtl"</code> in
the <code>quote</code> element means that the directionality of the content of this element, including child elements and attributes, is right-to-left.
Note that <code>xml:lang</code> indicates only the language, not the directionality.
</p>
<div class="exampleInner"><pre xml:space="preserve">
<text
xmlns:its="http://www.w3.org/2005/11/its"
its:version="1.0" xml:lang="en">
<head
its:translate="no">
<author>Sven Corneliusson</author>
<date>2006-09-26T17:34:04Z</date>
<title
its:translate="yes" role="header">Bidirectional Text</title>
</head>
<body>
<par>In Arabic, the title <quote xml:lang="ar"
its:dir="rtl"><span dir="rtl">نشاط التدويل، W3C</span></quote>
means <quote>Internationalization Activity, W3C</quote>.</par>
</body>
</text></pre></div>
<p>[Source file: <a href="EX-selection-local-1.xml" shape="rect">EX-selection-local-1.xml</a>]
</p>
</div>
<p>Markup for local selection is defined as follows. The attribute group <a href="#att.local.no-ns.attributes" shape="rect">att.local.no-ns.attributes</a> contains ITS attributes in no namespace and is used with the ITS elements <a class="itsmarkup" href="#span" shape="rect">span</a>, <a class="itsmarkup" href="#locNote" shape="rect">locNote</a>, <a class="itsmarkup" href="#ruby" shape="rect">ruby</a>, <a class="itsmarkup" href="#rb" shape="rect">rb</a>, <a class="itsmarkup" href="#rt" shape="rect">rt</a>, <a class="itsmarkup" href="#rbc" shape="rect">rbc</a>, <a class="itsmarkup" href="#rtc" shape="rect">rtc</a> and <a class="itsmarkup" href="#rp" shape="rect">rp</a>. The attribute group <a href="#att.local.with-ns.attributes" shape="rect">att.local.with-ns.attributes</a> contains namespace qualified ITS attributes and is used with elements from different namespaces.
</p>
<dl>
<dt class="label"><a name="att.local.no-ns" id="att.local.no-ns" shape="rect"></a>att.local.no-ns
</dt>
<dd>
<table class="scrap" summary="Scrap">
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.local.no-ns.attributes" id="att.local.no-ns.attributes" shape="rect"></a>[8]
</td>
<td rowspan="1" colspan="1"><code>att.local.no-ns.attributes</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#att.local.no-ns.attribute.translate" shape="rect">att.local.no-ns.attribute.translate</a>,
<a href="#att.local.no-ns.attribute.locNote" shape="rect">att.local.no-ns.attribute.locNote</a>,
<a href="#att.local.no-ns.attribute.locNoteType" shape="rect">att.local.no-ns.attribute.locNoteType</a>,
<a href="#att.local.no-ns.attribute.locNoteRef" shape="rect">att.local.no-ns.attribute.locNoteRef</a>,
<a href="#att.local.no-ns.attribute.termInfoRef" shape="rect">att.local.no-ns.attribute.termInfoRef</a>,
<a href="#att.local.no-ns.attribute.term" shape="rect">att.local.no-ns.attribute.term</a>,
<a href="#att.local.no-ns.attribute.dir" shape="rect">att.local.no-ns.attribute.dir</a>
</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.local.no-ns.attribute.translate" id="att.local.no-ns.attribute.translate" shape="rect"></a>[9]
</td>
<td rowspan="1" colspan="1"><code>att.local.no-ns.attribute.translate</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> attribute translate { "yes" | "no" }?</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.local.no-ns.attribute.locNote" id="att.local.no-ns.attribute.locNote" shape="rect"></a>[10]
</td>
<td rowspan="1" colspan="1"><code>att.local.no-ns.attribute.locNote</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> attribute locNote { string }?</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.local.no-ns.attribute.locNoteType" id="att.local.no-ns.attribute.locNoteType" shape="rect"></a>[11]
</td>
<td rowspan="1" colspan="1"><code>att.local.no-ns.attribute.locNoteType</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
attribute locNoteType { "alert" | "description" }?</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.local.no-ns.attribute.locNoteRef" id="att.local.no-ns.attribute.locNoteRef" shape="rect"></a>[12]
</td>
<td rowspan="1" colspan="1"><code>att.local.no-ns.attribute.locNoteRef</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> attribute locNoteRef { xsd:anyURI }?</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.local.no-ns.attribute.termInfoRef" id="att.local.no-ns.attribute.termInfoRef" shape="rect"></a>[13]
</td>
<td rowspan="1" colspan="1"><code>att.local.no-ns.attribute.termInfoRef</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> attribute termInfoRef { xsd:anyURI }?</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.local.no-ns.attribute.term" id="att.local.no-ns.attribute.term" shape="rect"></a>[14]
</td>
<td rowspan="1" colspan="1"><code>att.local.no-ns.attribute.term</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> attribute term { "yes" | "no" }?</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.local.no-ns.attribute.dir" id="att.local.no-ns.attribute.dir" shape="rect"></a>[15]
</td>
<td rowspan="1" colspan="1"><code>att.local.no-ns.attribute.dir</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> attribute dir { "ltr" | "rtl" | "lro" | "rlo" }?</code></td>
</tr>
</tbody>
</table>
</dd>
<dt class="label"><a name="att.local.with-ns" id="att.local.with-ns" shape="rect"></a>att.local.with-ns
</dt>
<dd>
<table class="scrap" summary="Scrap">
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.local.with-ns.attributes" id="att.local.with-ns.attributes" shape="rect"></a>[16]
</td>
<td rowspan="1" colspan="1"><code>att.local.with-ns.attributes</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#att.local.with-ns.attribute.translate" shape="rect">att.local.with-ns.attribute.translate</a>,
<a href="#att.local.with-ns.attribute.locNote" shape="rect">att.local.with-ns.attribute.locNote</a>,
<a href="#att.local.with-ns.attribute.locNoteType" shape="rect">att.local.with-ns.attribute.locNoteType</a>,
<a href="#att.local.with-ns.attribute.locNoteRef" shape="rect">att.local.with-ns.attribute.locNoteRef</a>,
<a href="#att.local.with-ns.attribute.termInfoRef" shape="rect">att.local.with-ns.attribute.termInfoRef</a>,
<a href="#att.local.with-ns.attribute.term" shape="rect">att.local.with-ns.attribute.term</a>,
<a href="#att.local.with-ns.attribute.dir" shape="rect">att.local.with-ns.attribute.dir</a>
</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.local.with-ns.attribute.translate" id="att.local.with-ns.attribute.translate" shape="rect"></a>[17]
</td>
<td rowspan="1" colspan="1"><code>att.local.with-ns.attribute.translate</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> attribute its:translate { "yes" | "no" }?</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.local.with-ns.attribute.locNote" id="att.local.with-ns.attribute.locNote" shape="rect"></a>[18]
</td>
<td rowspan="1" colspan="1"><code>att.local.with-ns.attribute.locNote</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> attribute its:locNote { string }?</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.local.with-ns.attribute.locNoteType" id="att.local.with-ns.attribute.locNoteType" shape="rect"></a>[19]
</td>
<td rowspan="1" colspan="1"><code>att.local.with-ns.attribute.locNoteType</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
attribute its:locNoteType { "alert" | "description" }?</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.local.with-ns.attribute.locNoteRef" id="att.local.with-ns.attribute.locNoteRef" shape="rect"></a>[20]
</td>
<td rowspan="1" colspan="1"><code>att.local.with-ns.attribute.locNoteRef</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> attribute its:locNoteRef { xsd:anyURI }?</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.local.with-ns.attribute.termInfoRef" id="att.local.with-ns.attribute.termInfoRef" shape="rect"></a>[21]
</td>
<td rowspan="1" colspan="1"><code>att.local.with-ns.attribute.termInfoRef</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
attribute its:termInfoRef { xsd:anyURI }?</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.local.with-ns.attribute.term" id="att.local.with-ns.attribute.term" shape="rect"></a>[22]
</td>
<td rowspan="1" colspan="1"><code>att.local.with-ns.attribute.term</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> attribute its:term { "yes" | "no" }?</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.local.with-ns.attribute.dir" id="att.local.with-ns.attribute.dir" shape="rect"></a>[23]
</td>
<td rowspan="1" colspan="1"><code>att.local.with-ns.attribute.dir</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
attribute its:dir { "ltr" | "rtl" | "lro" | "rlo" }?</code></td>
</tr>
</tbody>
</table>
</dd>
<dt class="label">span</dt>
<dd>
<table class="scrap" summary="Scrap">
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="span" id="span" shape="rect"></a>[24]
</td>
<td rowspan="1" colspan="1"><code>span</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> element its:span { span.content, <a href="#span.attributes" shape="rect">span.attributes</a> }</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="span.content" id="span.content" shape="rect"></a>[25]
</td>
<td rowspan="1" colspan="1"><code>span.content</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> ( text | <a href="#ruby" shape="rect">ruby</a> | <a href="#span" shape="rect">span</a> )*</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="span.attributes" id="span.attributes" shape="rect"></a>[26]
</td>
<td rowspan="1" colspan="1"><code>span.attributes</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#att.local.no-ns.attributes" shape="rect">att.local.no-ns.attributes</a>
</code></td>
</tr>
</tbody>
</table>
</dd>
</dl>
</div>
</div>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="link-external-rules" id="link-external-rules" shape="rect"></a>5.3 Link to External Rules
</h3>
<p>One way to associate a document with a set of external
ITS rules is to use the optional XLink <a title="XML Linking Language
 1.0" href="#xlink1" shape="rect">[XLink 1.0]</a>
<a class="itsmarkup" href="#rules.attributes" shape="rect">href</a> attribute in the
<a class="itsmarkup" href="#rules" shape="rect">rules</a> element, accompanied by the XLink <a class="itsmarkup" href="#rules.attributes" shape="rect">type</a> attribute with the value "simple". The referenced document must be a
valid XML document containing at most one <a class="itsmarkup" href="#rules" shape="rect">rules</a>
element. That <a class="itsmarkup" href="#rules" shape="rect">rules</a> element can be the root element
or anywhere within the document tree (for example, the
document could be an XML Schema).
</p>
<p>The rules contained in the referenced document <a href="#rfc-keywords" shape="rect">MUST</a> be processed as if they were
at the top of the <a class="itsmarkup" href="#rules" shape="rect">rules</a> element with the XLink
<a class="itsmarkup" href="#rules.attributes" shape="rect">href</a> attribute.
</p>
<div class="exampleOuter"><a name="EX-link-external-rules-1" id="EX-link-external-rules-1">Example 16: External file EX-link-external-rules-1.xml with global rules:</a><p>The example demonstrates how metadata can be added to
ITS rules.
</p>
<div class="exampleInner"><pre xml:space="preserve">
<myFormatInfo
xmlns:its="http://www.w3.org/2005/11/its" >
<desc>ITS rules used by the Open University</desc>
<hostVoc>http://www.tei-c.org/ns/1.0</hostVoc>
<rulesId>98ECED99DF63D511B1250008C784EFB1</rulesId>
<rulesVersion>v 1.81 2006/03/28 07:43:21</rulesVersion> ...
<its:rules version="1.0">
<its:translateRule selector="//header" translate="no"/>
<its:translateRule selector="//term" translate="no"/>
<its:termRule selector="//term" term="yes"/>
<its:withinTextRule withinText="yes" selector="//term | //b"/>
</its:rules>
</myFormatInfo></pre></div>
<p>[Source file: <a href="EX-link-external-rules-1.xml" shape="rect">EX-link-external-rules-1.xml</a>]
</p>
</div>
<div class="exampleOuter"><a name="d3e2256" id="d3e2256">Example 17: Document with a link to EX-link-external-rules-1.xml</a><div class="exampleInner"><pre xml:space="preserve">
<myDoc
xmlns:its="http://www.w3.org/2005/11/its"
xmlns:xlink="http://www.w3.org/1999/xlink" >
<header>
<its:rules version="1.0" xlink:href="EX-link-external-rules-1.xml" xlink:type="simple">
<its:translateRule selector="//term" translate="yes"/>
</its:rules>
<author>Theo Brumble</author>
<lastUpdate>Apr-01-2006</lastUpdate>
</header>
<body>
<p>A <term>Palouse horse</term> has a spotted coat.</p>
</body>
</myDoc></pre></div>
<p>[Source file: <a href="EX-link-external-rules-2.xml" shape="rect">EX-link-external-rules-2.xml</a>]
</p>
</div>
<p>The result of processing the two documents above is the
same as processing the following document.
</p>
<div class="exampleOuter"><a name="d3e2268" id="d3e2268">Example 18: Document with identical rules as in the case of included rules</a><div class="exampleInner"><pre xml:space="preserve">
<myDoc
xmlns:its="http://www.w3.org/2005/11/its" >
<header>
<its:rules version="1.0">
<its:translateRule selector="//header" translate="no"/>
<its:translateRule selector="//term" translate="no"/>
<its:termRule selector="//term" term="yes"/>
<its:withinTextRule withinText="yes" selector="//term | //b"/>
<its:translateRule selector="//term" translate="yes"/>
</its:rules>
<author>Theo Brumble</author>
<lastUpdate>Apr-01-2006</lastUpdate>
</header>
<body>
<p>A <term>Palouse horse</term> has a spotted coat.</p>
</body>
</myDoc></pre></div>
<p>[Source file: <a href="EX-link-external-rules-3.xml" shape="rect">EX-link-external-rules-3.xml</a>]
</p>
</div>
<p>Applications processing global ITS markup <a href="#rfc-keywords" shape="rect">MUST</a> recognize the XLink
<a class="itsmarkup" href="#rules.attributes" shape="rect">href</a> attribute in the <a class="itsmarkup" href="#rules" shape="rect">rules</a> element;
they <a href="#rfc-keywords" shape="rect">MUST</a> load the
corresponding referenced document and process its rules
element before processing the content of the <a class="itsmarkup" href="#rules" shape="rect">rules</a>
element where the original XLink <a class="itsmarkup" href="#rules.attributes" shape="rect">href</a> attribute
is.
</p>
<p>External rules may also have links to other external
rules. The linking mechanism is recursive, the deepest rules
being overridden by the top-most rules, if any.
</p>
</div>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="selection-precedence" id="selection-precedence" shape="rect"></a>5.4 Precedence between Selections
</h3>
<p>The following precedence order is defined for selections
of ITS information in various positions (the first item in
the list has the highest precedence):
</p>
<ol class="depth1">
<li>
<p>Implicit local selection
in documents (<a href="#span.attributes" shape="rect">ITS local
attributes</a> on a specific element)
</p>
</li>
<li>
<p>Global selections
in documents (using a <a class="itsmarkup" href="#rules" shape="rect">rules</a> element)
</p>
<p>Inside each <a class="itsmarkup" href="#rules" shape="rect">rules</a> element the precedence order is:
</p>
<ol class="depth2">
<li>
<p>Any rules inside the rules element</p>
</li>
<li>
<p>Any rules linked via the XLink <a class="itsmarkup" href="#rules.attributes" shape="rect">href</a> attribute
</p>
</li>
</ol>
<p>
</p>
<div class="note">
<p class="prefix"><b>Note:</b></p>
<p>If identical selections are defined in different rules elements
within one document, the selection defined by the last takes
precedence.
</p>
</div>
<div class="note">
<p class="prefix"><b>Note:</b></p>
<p>ITS doesn't define precedence related to rules defined or linked
based on non-ITS mechanisms (such as processing instructions for linking
rules).
</p>
</div>
</li>
<li>
<p>Selections via defaults
for data categories, see <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 6.1: Position, Defaults, Inheritance and Overriding of Data Categories</a></p>
</li>
</ol>
<p>In case of conflicts between global selections via
multiple <a href="#selection-global" shape="rect">rule</a>
elements, the last selector has higher precedence.
</p>
<div class="note">
<p class="prefix"><b>Note:</b></p>
<p>The precedence order fulfills the same purpose as the
built-in template rules of <a title="XSL Transformations (XSLT)
 Version 1.0" href="#xslt10" shape="rect">[XSLT 1.0]</a>.
</p>
</div>
<div class="exampleOuter"><a name="d3e2355" id="d3e2355">Example 19: Conflicts between selections of ITS information which are resolved using the
precedence order</a><p>The two elements <code>title</code> and <code>author</code> of this document should be treated as separate content when inside a <code>prolog</code> element, but as part of the content of their parent element otherwise. In order to make this distinction two <a class="itsmarkup" href="#withinTextRule" shape="rect">withinTextRule</a> elements are used:
</p>
<p>The first rule specifies that <code>title</code> and <code>author</code> in general should be treated as an element within text. This overrides the default.
</p>
<p>The second rule indicates that when <code>title</code> or <code>author</code> are found in a <code>prolog</code> element their content should be treated separately. This is normally the default, but the rule is needed to override the
first rule.
</p>
<div class="exampleInner"><pre xml:space="preserve">
<text
xmlns:its="http://www.w3.org/2005/11/its" >
<prolog>
<its:rules version="1.0">
<its:withinTextRule withinText="yes" selector="//title|//author"/>
<its:withinTextRule withinText="no" selector="//prolog/title|//prolog/author"/>
</its:rules>
<title>Designing User Interfaces</title>
<author>Janice Prakash</author>
<keywords>user interface, ui, software interface</keywords>
</prolog>
<body>
<p>The book <title>Of Mice and Screens</title> by <author>Aldus
Brandywine</author> is one of the best introductions to the vast
topic of designing user interfaces.</p>
</body>
</text></pre></div>
<p>[Source file: <a href="EX-selection-precedence-1.xml" shape="rect">EX-selection-precedence-1.xml</a>]
</p>
</div>
</div>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="associating-its-with-existing-markup" id="associating-its-with-existing-markup" shape="rect"></a>5.5 Associating ITS Data Categories with Existing Markup
</h3>
<p>Some markup schemes provide markup which can be used to
express ITS data categories. ITS data categories can be associated with such existing markup, using
the global selection mechanism described in <a class="section-ref" href="#selection-global" shape="rect">Section 5.2.1: Global, Rule-based Selection</a>.
</p>
<p>Associating existing markup with ITS data
categories can be done only if the processing expectations of the host markup
are the same as, or greater than, those of ITS.
</p>
<div class="exampleOuter"><a name="EX-associating-its-with-existing-markup-1" id="EX-associating-its-with-existing-markup-1">Example 20: Association of the ITS data categories
Translate and Terminology with DITA 1.0 markup</a><div class="exampleInner"><pre xml:space="preserve">
<topic
xmlns:its="http://www.w3.org/2005/11/its" id="myTopic">
<title>The ITS Topic</title>
<prolog>
<its:rules version="1.0">
<its:translateRule selector="//*[@translate='no']" translate="no"/>
<its:translateRule selector="//*[@translate='yes']" translate="yes"/>
<its:termRule selector="//term | //dt" term="yes"/>
</its:rules>
</prolog>
<body>
<dl>
<dlentry id="tDataCat">
<dt>Data category</dt>
<dd>ITS defines <term>data category</term> as an abstract concept for
a particular type of information related to internationalization and
localization of XML schemas and documents.</dd>
</dlentry>
</dl>
<p>For the implementation of ITS, apply the rules in the order:</p>
<ul>
<li>Defaults</li>
<li>Rules in external files</li>
<li>Rules in the document</li>
<li>Local attributes</li>
</ul>
<p>
<ph translate="no" xml:lang="fr">Et voilà !</ph>.</p>
</body>
</topic></pre></div>
<p>[Source file: <a href="EX-associating-its-with-existing-markup-1.xml" shape="rect">EX-associating-its-with-existing-markup-1.xml</a>]
</p>
</div>
<p>Global rules can be associated with a given XML document using different means:</p>
<ul>
<li>
<p>By using an <a class="itsmarkup" href="#rules" shape="rect">rules</a> element in the document itself:
</p>
<ul>
<li>
<p>with the rules directly inside the document, as shown in <a href="#EX-associating-its-with-existing-markup-1" shape="rect">Example 20</a></p>
</li>
<li>
<p>with a link to an external rules file using the XLink <a class="itsmarkup" href="#rules.attributes" shape="rect">href</a> attribute, as shown in <a href="#EX-link-external-rules-1" shape="rect">Example 16</a></p>
</li>
</ul>
</li>
<li>
<p>By associating the rules and the document through a tool-specific mechanism. For example, for a command-line tool: providing
the paths of both the XML document to process and its corresponding external rules file.
</p>
</li>
</ul>
</div>
</div>
<div class="div1">
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="datacategory-description" id="datacategory-description" shape="rect"></a>6 Description of Data Categories
</h2>
<p>
<em>This section is normative.</em>
</p>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="datacategories-defaults-etc" id="datacategories-defaults-etc" shape="rect"></a>6.1 Position, Defaults, Inheritance and Overriding of Data Categories
</h3>
<p>The following table summarizes for each data category which selection, default value, and inheritance and overriding behavior
applies.
</p>
<ul>
<li>
<p><em>Default values</em> apply if both local or global selection are absent.
The default value for the <a href="#trans-datacat" shape="rect">Translate</a> data category for example mandates that elements are translatable, and attributes are not translatable if there is no <a class="itsmarkup" href="#translateRule" shape="rect">translateRule</a> element and no <a class="itsmarkup" href="#att.local.no-ns.attribute.translate" shape="rect">translate</a> attribute available.
</p>
</li>
<li>
<p><em>Inheritance</em> describes whether ITS information is applicable to child elements of nodes and attributes related to these nodes or their
child notes. The inheritance for the <a href="#trans-datacat" shape="rect">Translate</a> data category for example mandates that all child elements of nodes are translatable whereas all attributes related to these
the nodes or their child notes are not translatable.
</p>
</li>
<li>
<p><em>Overriding</em> describes whether ITS information can be overridden or not. Overriding is only applicable for data categories with inheritance.
Overriding thus is not applicable for the <a href="#terminology" shape="rect">Terminology</a> and the <a href="#ruby-annotation" shape="rect">Ruby</a> data category.
</p>
</li>
</ul>
<table border="1" width="100%">
<thead>
<tr>
<td rowspan="1" colspan="1">Data category</td>
<td rowspan="1" colspan="1">Local Usage</td>
<td rowspan="1" colspan="1">Global, rule-based selection</td>
<td rowspan="1" colspan="1">Global adding of information</td>
<td rowspan="1" colspan="1">Global pointing to existing information</td>
<td rowspan="1" colspan="1">Default Values</td>
<td rowspan="1" colspan="1">Inheritance</td>
<td rowspan="1" colspan="1">Overriding</td>
</tr>
</thead>
<tbody>
<tr>
<td rowspan="1" colspan="1">
<a href="#trans-datacat" shape="rect">Translate</a>
</td>
<td rowspan="1" colspan="1">Yes</td>
<td rowspan="1" colspan="1">Yes</td>
<td rowspan="1" colspan="1">Yes</td>
<td rowspan="1" colspan="1">No</td>
<td rowspan="1" colspan="1">
<code>translate="yes"</code> for elements, and <code>translate="no"</code> for attributes
</td>
<td rowspan="1" colspan="1">Textual content of element, <em>including</em> content of child elements,
but <em>excluding</em> attributes
</td>
<td rowspan="1" colspan="1">Yes</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<a href="#locNote-datacat" shape="rect">Localization Note</a>
</td>
<td rowspan="1" colspan="1">Yes</td>
<td rowspan="1" colspan="1">Yes</td>
<td rowspan="1" colspan="1">Yes</td>
<td rowspan="1" colspan="1">Yes</td>
<td rowspan="1" colspan="1">None</td>
<td rowspan="1" colspan="1">Textual content of element, <em>including</em> content of child elements,
but <em>excluding</em> attributes
</td>
<td rowspan="1" colspan="1">Yes</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<a href="#terminology" shape="rect">Terminology</a>
</td>
<td rowspan="1" colspan="1">Yes</td>
<td rowspan="1" colspan="1">Yes</td>
<td rowspan="1" colspan="1">Yes</td>
<td rowspan="1" colspan="1">Yes</td>
<td rowspan="1" colspan="1">
<code>term="no"</code>
</td>
<td rowspan="1" colspan="1">None</td>
<td rowspan="1" colspan="1">Not applicable</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<a href="#directionality" shape="rect">Directionality</a>
</td>
<td rowspan="1" colspan="1">Yes</td>
<td rowspan="1" colspan="1">Yes</td>
<td rowspan="1" colspan="1">Yes</td>
<td rowspan="1" colspan="1">No</td>
<td rowspan="1" colspan="1">
<code>dir="ltr"</code>
</td>
<td rowspan="1" colspan="1">Textual content of element, <em>including</em> attributes and child
elements
</td>
<td rowspan="1" colspan="1">Yes</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<a href="#ruby-annotation" shape="rect">Ruby</a>
</td>
<td rowspan="1" colspan="1">Yes</td>
<td rowspan="1" colspan="1">Yes</td>
<td rowspan="1" colspan="1">Yes</td>
<td rowspan="1" colspan="1">Yes</td>
<td rowspan="1" colspan="1">None</td>
<td rowspan="1" colspan="1">None</td>
<td rowspan="1" colspan="1">Not applicable</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<a href="#language-information" shape="rect">Language Information</a>
</td>
<td rowspan="1" colspan="1">No</td>
<td rowspan="1" colspan="1">Yes</td>
<td rowspan="1" colspan="1">No</td>
<td rowspan="1" colspan="1">Yes</td>
<td rowspan="1" colspan="1">None</td>
<td rowspan="1" colspan="1">Textual content of element, <em>including</em> attributes and child
elements
</td>
<td rowspan="1" colspan="1">Yes</td>
</tr>
<tr>
<td rowspan="1" colspan="1">
<a href="#elements-within-text" shape="rect">Elements Within Text</a>
</td>
<td rowspan="1" colspan="1">No</td>
<td rowspan="1" colspan="1">Yes</td>
<td rowspan="1" colspan="1">Yes</td>
<td rowspan="1" colspan="1">No</td>
<td rowspan="1" colspan="1">
<code>withinText="no"</code>
</td>
<td rowspan="1" colspan="1">None</td>
<td rowspan="1" colspan="1">Not applicable</td>
</tr>
</tbody>
</table>
<div class="exampleOuter"><a name="d3e2689" id="d3e2689">Example 21: Defaults, inheritance and overriding behavior of data categories</a><p>In this example, the content of all the <code>data</code> elements is translatable because the default for
the <a href="#trans-datacat" shape="rect">Translate</a> data category in elements is "yes". The content of <code>revision</code> and <a class="itsmarkup" href="#locNote" shape="rect">locNote</a> is not translatable because the default is overridden by the local <code>its:translate="no"</code> attribute in the <code>prolog</code> element, and that value is inherited by all the children of <code>prolog</code>.
</p>
<p>The localization note for the two first <code>data</code> elements is the text defined globally with the
<a class="itsmarkup" href="#locNoteRule" shape="rect">locNoteRule</a> element. And this note is overridden for the last <code>data</code> element by the local
<code>its:locNote</code> attribute.
</p>
<div class="exampleInner"><pre xml:space="preserve">
<Res
xmlns:its="http://www.w3.org/2005/11/its"
its:version="1.0">
<prolog
its:translate="no">
<revision>Sep-07-2006</revision>
<its:rules version="1.0">
<its:translateRule selector="//msg/notes" translate="no"/>
<its:locNoteRule locNoteType="description" selector="//msg/data">
<its:locNote>The variable {0} is the name of the host.</its:locNote>
</its:locNoteRule>
</its:rules>
</prolog>
<body>
<msg id="HostNotFound">
<data>Host {0} cannot be found.</data>
</msg>
<msg id="HostDisconnected">
<data>The connection with {0} has been lost.</data>
</msg>
<msg id="FileNotFound">
<data
its:locNote="{0} is a filename">{0} not found.</data>
</msg>
</body>
</Res></pre></div>
<p>[Source file: <a href="EX-datacat-behavior-1.xml" shape="rect">EX-datacat-behavior-1.xml</a>]
</p>
</div>
<div class="note">
<p class="prefix"><b>Note:</b></p>
<p>The data categories differ with respect to defaults. This is due to existing standards and practices. It is common practice
for example that information about translation refers only to textual content of an element. Thus, the default selection for
the <a href="#trans-datacat" shape="rect">Translate</a> data category is the textual content.
</p>
</div>
</div>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="trans-datacat" id="trans-datacat" shape="rect"></a>6.2 Translate
</h3>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="translatability-definition" id="translatability-definition" shape="rect"></a>6.2.1 Definition
</h4>
<p>The <a href="#trans-datacat" shape="rect">Translate</a> data category expresses information
about whether the content of an element or attribute
should be translated or not. The values of this data
category are "yes" (translatable) or
"no" (not translatable).
</p>
</div>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="translatability-implementation" id="translatability-implementation" shape="rect"></a>6.2.2 Implementation
</h4>
<p>The <a href="#trans-datacat" shape="rect">Translate</a> data category can be expressed with global rules, or locally on an individual element. The information applies to the textual
content of the element, <em>including</em> child elements, but <em>excluding</em> attributes. The default is that elements are translatable and attributes are not.
</p>
<p>GLOBAL: The <a class="itsmarkup" href="#translateRule" shape="rect">translateRule</a> element contains the following:
</p>
<ul>
<li>
<p>A required <a class="itsmarkup" href="#att.selector.attribute.selector" shape="rect">selector</a> attribute. It contains an XPath expression which selects the nodes to which this rule applies.
</p>
</li>
<li>
<p>A required <a class="itsmarkup" href="#translateRule.attributes" shape="rect">translate</a> attribute with the value "yes" or "no".
</p>
</li>
</ul>
<div class="exampleOuter"><a name="EX-translate-selector-1" id="EX-translate-selector-1">Example 22: The Translate data category expressed globally</a><p>The <a class="itsmarkup" href="#translateRule" shape="rect">translateRule</a> element specifies that the elements <code>code</code> must not be translated.
</p>
<div class="exampleInner"><pre xml:space="preserve">
<its:rules
xmlns:its="http://www.w3.org/2005/11/its" version="1.0">
<its:translateRule translate="no" selector="//code"/>
</its:rules></pre></div>
<p>[Source file: <a href="EX-translate-selector-1.xml" shape="rect">EX-translate-selector-1.xml</a>]
</p>
</div>
<p>LOCAL: The following local markup is available for the <a href="#trans-datacat" shape="rect">Translate</a> data category:
</p>
<ul>
<li>
<p>A <a class="itsmarkup" href="#att.local.no-ns.attribute.translate" shape="rect">translate</a> attribute with the value "yes" or "no".
</p>
</li>
</ul>
<div class="note">
<p class="prefix"><b>Note:</b></p>
<p>It is not possible to override the <a href="#trans-datacat" shape="rect">Translate</a> data category settings of attributes using local markup. This limitation is consistent with the advised practice of not using
translatable attributes.
</p>
</div>
<div class="exampleOuter"><a name="EX-translate-selector-2" id="EX-translate-selector-2">Example 23: The Translate data category expressed locally</a><p>The local <code>its:translate="no"</code> specifies that the content of <code>panelmsg</code> must not be translated.
</p>
<div class="exampleInner"><pre xml:space="preserve">
<messages
xmlns:its="http://www.w3.org/2005/11/its"
its:version="1.0">
<msg num="123">Click Resume Button on Status Display or
<panelmsg
its:translate="no">CONTINUE</panelmsg> Button
on printer panel</msg>
</messages></pre></div>
<p>[Source file: <a href="EX-translate-selector-2.xml" shape="rect">EX-translate-selector-2.xml</a>]
</p>
</div>
</div>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="translatability-markup" id="translatability-markup" shape="rect"></a>6.2.3 Markup Declarations for Translate
</h4>
<dl>
<dt class="label">translateRule</dt>
<dd>
<table class="scrap" summary="Scrap">
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="translateRule" id="translateRule" shape="rect"></a>[27]
</td>
<td rowspan="1" colspan="1"><code>translateRule</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
element its:translateRule
{
translateRule.content,
<a href="#translateRule.attributes" shape="rect">translateRule.attributes</a>
}</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="translateRule.content" id="translateRule.content" shape="rect"></a>[28]
</td>
<td rowspan="1" colspan="1"><code>translateRule.content</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> empty</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="translateRule.attributes" id="translateRule.attributes" shape="rect"></a>[29]
</td>
<td rowspan="1" colspan="1"><code>translateRule.attributes</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#att.selector.attributes" shape="rect">att.selector.attributes</a>,
attribute translate { "yes" | "no" }</code></td>
</tr>
</tbody>
</table>
</dd>
<dt class="label"><a name="att.translate" id="att.translate" shape="rect"></a>att.translate
</dt>
<dd>
<table class="scrap" summary="Scrap">
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.translate.attributes" id="att.translate.attributes" shape="rect"></a>[30]
</td>
<td rowspan="1" colspan="1"><code>att.translate.attributes</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#att.translate.attribute.translate" shape="rect">att.translate.attribute.translate</a>
</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.translate.attribute.translate" id="att.translate.attribute.translate" shape="rect"></a>[31]
</td>
<td rowspan="1" colspan="1"><code>att.translate.attribute.translate</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> attribute its:translate { "yes" | "no" }?</code></td>
</tr>
</tbody>
</table>
</dd>
</dl>
</div>
</div>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="locNote-datacat" id="locNote-datacat" shape="rect"></a>6.3 Localization Note
</h3>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="locNote-definition" id="locNote-definition" shape="rect"></a>6.3.1 Definition
</h4>
<p>The <a href="#locNote-datacat" shape="rect">Localization Note</a> data category is used to
communicate notes to localizers about a particular
item of content.
</p>
<p>This data category can be used for several purposes, including, but
not limited to:
</p>
<ul>
<li>
<p>Tell the translator how to translate parts of the
content
</p>
</li>
<li>
<p>Expand on the meaning or contextual usage of a
specific element, such as what a variable refers to or
how a string will be used on the user interface
</p>
</li>
<li>
<p>Clarify ambiguity and show relationships between
items sufficiently to allow correct translation (e.g. in
many languages it is impossible to translate the word "<span class="quote">enabled</span>" in isolation without knowing the
gender, number and case of the thing it refers
to.)
</p>
</li>
<li>
<p>Indicate why a piece of text is emphasized
(important, sarcastic, etc.)
</p>
</li>
</ul>
<p>Two types of informative notes are needed:</p>
<ul>
<li>
<p>An alert contains information that the translator
must read before translating a piece of text. Example:
an instruction to the translator to leave parts of the
text in the source language.
</p>
</li>
<li>
<p>A description provides useful background
information that the translator will refer to only if
they wish. Example: a clarification of ambiguity in the
source text.
</p>
</li>
</ul>
<p>Editing tools may offer an easy way to create this type of information.
Translation tools can be made to recognize the difference between these two
types of localization notes, and present the information to translators
in different ways.
</p>
</div>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="locNote-implementation" id="locNote-implementation" shape="rect"></a>6.3.2 Implementation
</h4>
<p>The <a href="#locNote-datacat" shape="rect">Localization Note</a> data category can be expressed with global
rules, or locally on an individual element. The information applies to the textual
content of the element, <em>including</em> child elements,
but <em>excluding</em> attributes.
</p>
<p id="locNote-global">GLOBAL: The <a class="itsmarkup" href="#locNoteRule" shape="rect">locNoteRule</a> element contains the following:
</p>
<ul>
<li>
<p>A required <a class="itsmarkup" href="#att.selector.attribute.selector" shape="rect">selector</a> attribute. It contains an XPath expression which selects the nodes to which this rule applies.
</p>
</li>
<li>
<p>A required <a class="itsmarkup" href="#locNoteRule.attributes" shape="rect">locNoteType</a> attribute with the value "description" or "alert".
</p>
</li>
<li>
<p>Exactly one of the following:</p>
<ul>
<li>
<p>A <a class="itsmarkup" href="#locNote" shape="rect">locNote</a> element that contains the note itself and allows for <a href="#selection-local" shape="rect">local ITS markup</a>.
</p>
</li>
<li>
<p>A <a class="itsmarkup" href="#locNoteRule.attributes" shape="rect">locNotePointer</a> attribute that contains a relative XPath expression pointing to a node that holds the localization note.
</p>
</li>
<li>
<p>A <a class="itsmarkup" href="#att.local.no-ns.attribute.locNoteRef" shape="rect">locNoteRef</a> attribute that contains a URI referring to the location of the localization note.
</p>
</li>
<li>
<p>A <a class="itsmarkup" href="#locNoteRule.attributes" shape="rect">locNoteRefPointer</a> attribute that contains a relative XPath expression pointing to a node that holds the URI referring to the location of the
localization note.
</p>
</li>
</ul>
</li>
</ul>
<div class="exampleOuter"><a name="EX-locNote-element-1" id="EX-locNote-element-1">Example 24: The locNote element</a><p>The <a class="itsmarkup" href="#locNoteRule" shape="rect">locNoteRule</a> element associates the content of the <a class="itsmarkup" href="#locNote" shape="rect">locNote</a> element with the message with the identifier 'DisableInfo' and flags it as important. This would also work if the rule was
in an external file, allowing to provide notes without modifying the source document.
</p>
<div class="exampleInner"><pre xml:space="preserve">
<myRes
xmlns:its="http://www.w3.org/2005/11/its" >
<head>
<its:rules version="1.0"
its:translate="no">
<its:locNoteRule locNoteType="alert" selector="//msg[@id='DisableInfo']">
<its:locNote>The variable {0} has three possible values: 'printer',
'stacker' and 'stapler options'.</its:locNote>
</its:locNoteRule>
</its:rules>
</head>
<body>
<msg id="DisableInfo">The {0} has been disabled.</msg>
</body>
</myRes></pre></div>
<p>[Source file: <a href="EX-locNote-element-1.xml" shape="rect">EX-locNote-element-1.xml</a>]
</p>
</div>
<div class="exampleOuter"><a name="EX-locNotePointer-attribute-1" id="EX-locNotePointer-attribute-1">Example 25: The locNotePointer attribute</a><p>The <a class="itsmarkup" href="#locNoteRule.attributes" shape="rect">locNotePointer</a> attribute is a relative XPath expression pointing to a node that holds the note.
</p>
<div class="exampleInner"><pre xml:space="preserve">
<Res
xmlns:its="http://www.w3.org/2005/11/its" >
<prolog>
<its:rules version="1.0">
<its:translateRule selector="//msg/notes" translate="no"/>
<its:locNoteRule locNoteType="description" selector="//msg/data" locNotePointer="../notes"/>
</its:rules>
</prolog>
<body>
<msg id="FileNotFound">
<notes>Indicates that the resource file {0} could not be loaded.</notes>
<data>Cannot find the file {0}.</data>
</msg>
<msg id="DivByZero">
<notes>A division by 0 was going to be computed.</notes>
<data>Invalid parameter.</data>
</msg>
</body>
</Res></pre></div>
<p>[Source file: <a href="EX-locNotePointer-attribute-1.xml" shape="rect">EX-locNotePointer-attribute-1.xml</a>]
</p>
</div>
<div class="exampleOuter"><a name="EX-locNoteRef-attribute-1" id="EX-locNoteRef-attribute-1">Example 26: The locNoteRef attribute</a><p>The <a class="itsmarkup" href="#locNoteRule" shape="rect">locNoteRule</a> element specifies that the message with the identifier 'NotFound' has a corresponding explanation note in an
external file. The URI for the exact location of the note is stored in the <a class="itsmarkup" href="#locNoteRule.attributes" shape="rect">locNoteRef</a> attribute.
</p>
<div class="exampleInner"><pre xml:space="preserve">
<myRes
xmlns:its="http://www.w3.org/2005/11/its" >
<head>
<its:rules version="1.0">
<its:locNoteRule locNoteType="description" selector="//msg[@id='NotFound']" locNoteRef="ErrorsInfo.html#NotFound"/>
</its:rules>
</head>
<body>
<msg id="NotFound">Cannot find {0} on {1}.</msg>
</body>
</myRes></pre></div>
<p>[Source file: <a href="EX-locNoteRef-attribute-1.xml" shape="rect">EX-locNoteRef-attribute-1.xml</a>]
</p>
</div>
<div class="exampleOuter"><a name="d3e3088" id="d3e3088">Example 27: The locNoteRefPointer attribute</a><p>The <a class="itsmarkup" href="#locNoteRule.attributes" shape="rect">locNoteRefPointer</a> attribute contains a relative XPath expression pointing to a node that holds the URI referring to the location of the note.
</p>
<div class="exampleInner"><pre xml:space="preserve">
<dataFile
xmlns:its="http://www.w3.org/2005/11/its" >
<prolog>
<its:rules version="1.0">
<its:locNoteRule locNoteType="description" selector="//data" locNoteRefPointer="../@noteFile"/>
</its:rules>
</prolog>
<body>
<string id="FileNotFound" noteFile="Comments.html#FileNotFound">
<data>Cannot find the file {0}.</data>
</string>
<string id="DivByZero" noteFile="Comments.html#DivByZero">
<data>Invalid parameter.</data>
</string>
</body>
</dataFile></pre></div>
<p>[Source file: <a href="EX-locNoteRefPointer-attribute-1.xml" shape="rect">EX-locNoteRefPointer-attribute-1.xml</a>]
</p>
</div>
<p>LOCAL: The following local markup is available for the <a href="#locNote-datacat" shape="rect">Localization Note</a> data category:
</p>
<ul>
<li>
<p>One of the following:</p>
<ul>
<li>
<p>A <a class="itsmarkup" href="#att.local.no-ns.attribute.locNote" shape="rect">locNote</a> attribute that contains the note itself.
</p>
</li>
<li>
<p>A <a class="itsmarkup" href="#att.local.no-ns.attribute.locNoteRef" shape="rect">locNoteRef</a> attribute that contains a URI referring to the location of the localization note.
</p>
</li>
</ul>
</li>
<li>
<p>An optional <a class="itsmarkup" href="#att.local.no-ns.attribute.locNoteType" shape="rect">locNoteType</a> attribute with the value "description" or "alert". If the <a class="itsmarkup" href="#att.local.no-ns.attribute.locNoteType" shape="rect">locNoteType</a> attribute is not present, the type of localization note will be assumed to be "description".
</p>
</li>
</ul>
<div class="exampleOuter"><a name="d3e3146" id="d3e3146">Example 28: The Localization Note data category expressed locally</a><div class="exampleInner"><pre xml:space="preserve">
<msgList
xmlns:its="http://www.w3.org/2005/11/its" xml:space="preserve"
its:version="1.0">
<data name="LISTFILTERS_VARIANT"
its:locNote="Keep the leading space!"
its:locNoteType="alert">
<value> Variant {0} = {1} ({2})</value>
</data>
<data
its:locNote="%1\$s is the original text's date in the format YYYY-MM-DD HH:MM always in GMT">
<value>Translated from English content dated <span id="version-info">%1\$s</span> GMT.</value>
</data>
</msgList></pre></div>
<p>[Source file: <a href="EX-locNote-selector-2.xml" shape="rect">EX-locNote-selector-2.xml</a>]
</p>
</div>
<div class="note">
<p class="prefix"><b>Note:</b></p>
<p>It is generally recommended to avoid using attributes to store text, however, in this specific case, the need to provide the
notes without interfering with
the structure of the host document is outweighing the drawbacks of using an
attribute.
</p>
</div>
</div>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="locNote-markup" id="locNote-markup" shape="rect"></a>6.3.3 Markup Declarations for Localization Note
</h4>
<dl>
<dt class="label">locNoteRule</dt>
<dd>
<table class="scrap" summary="Scrap">
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="locNoteRule" id="locNoteRule" shape="rect"></a>[32]
</td>
<td rowspan="1" colspan="1"><code>locNoteRule</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
element its:locNoteRule { locNoteRule.content, <a href="#locNoteRule.attributes" shape="rect">locNoteRule.attributes</a> }</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="locNoteRule.content" id="locNoteRule.content" shape="rect"></a>[33]
</td>
<td rowspan="1" colspan="1"><code>locNoteRule.content</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#locNote" shape="rect">locNote</a>?</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="locNoteRule.attributes" id="locNoteRule.attributes" shape="rect"></a>[34]
</td>
<td rowspan="1" colspan="1"><code>locNoteRule.attributes</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#att.selector.attributes" shape="rect">att.selector.attributes</a>,
attribute locNotePointer { string }?,
attribute locNoteType { "alert" | "description" },
attribute locNoteRef { xsd:anyURI }?,
attribute locNoteRefPointer { string }?</code></td>
</tr>
</tbody>
</table>
</dd>
<dt class="label">locNote</dt>
<dd>
<table class="scrap" summary="Scrap">
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="locNote" id="locNote" shape="rect"></a>[35]
</td>
<td rowspan="1" colspan="1"><code>locNote</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> element its:locNote { locNote.content, <a href="#locNote.attributes" shape="rect">locNote.attributes</a> }</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="locNote.content" id="locNote.content" shape="rect"></a>[36]
</td>
<td rowspan="1" colspan="1"><code>locNote.content</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> ( text | <a href="#ruby" shape="rect">ruby</a> | <a href="#span" shape="rect">span</a> )*</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="locNote.attributes" id="locNote.attributes" shape="rect"></a>[37]
</td>
<td rowspan="1" colspan="1"><code>locNote.attributes</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#att.local.no-ns.attributes" shape="rect">att.local.no-ns.attributes</a>
</code></td>
</tr>
</tbody>
</table>
</dd>
<dt class="label"><a name="att.locNote" id="att.locNote" shape="rect"></a>att.locNote
</dt>
<dd>
<table class="scrap" summary="Scrap">
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.locNote.attributes" id="att.locNote.attributes" shape="rect"></a>[38]
</td>
<td rowspan="1" colspan="1"><code>att.locNote.attributes</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#att.locNote.attribute.locNote" shape="rect">att.locNote.attribute.locNote</a>,
<a href="#att.locNote.attribute.locNoteType" shape="rect">att.locNote.attribute.locNoteType</a>,
<a href="#att.locNote.attribute.locNoteRef" shape="rect">att.locNote.attribute.locNoteRef</a>
</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.locNote.attribute.locNote" id="att.locNote.attribute.locNote" shape="rect"></a>[39]
</td>
<td rowspan="1" colspan="1"><code>att.locNote.attribute.locNote</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> attribute its:locNote { string }?</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.locNote.attribute.locNoteType" id="att.locNote.attribute.locNoteType" shape="rect"></a>[40]
</td>
<td rowspan="1" colspan="1"><code>att.locNote.attribute.locNoteType</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
attribute its:locNoteType { "alert" | "description" }?</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.locNote.attribute.locNoteRef" id="att.locNote.attribute.locNoteRef" shape="rect"></a>[41]
</td>
<td rowspan="1" colspan="1"><code>att.locNote.attribute.locNoteRef</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> attribute its:locNoteRef { xsd:anyURI }?</code></td>
</tr>
</tbody>
</table>
</dd>
</dl>
</div>
</div>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="terminology" id="terminology" shape="rect"></a>6.4 Terminology
</h3>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="terminology-definition" id="terminology-definition" shape="rect"></a>6.4.1 Definition
</h4>
<p>The <a href="#terminology" shape="rect">Terminology</a> data category is used to mark terms and optionally
associate them with information, such as definitions. This helps to increase consistency across different
parts of the documentation. It is also helpful for translation.
</p>
<div class="note">
<p class="prefix"><b>Note:</b></p>
<p>Existing terminology standards such as <a title="Machine-readable terminology interchange format (MARTIF) -- Negotiated interchange" href="#iso12200" shape="rect">[ISO 12200]</a> and its derived formats are about coding terminology data, while the ITS <a href="#terminology" shape="rect">Terminology</a> data category simply allows to identify terms in XML documents and optionally to point to corresponding information.
</p>
</div>
</div>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="terminology-implementation" id="terminology-implementation" shape="rect"></a>6.4.2 Implementation
</h4>
<p>The <a href="#terminology" shape="rect">Terminology</a> data category can be expressed with global
rules, or locally on an individual element. There is no inheritance. The default is that neither elements nor attributes are
terms.
</p>
<p>GLOBAL: The <a class="itsmarkup" href="#termRule" shape="rect">termRule</a> element contains the following:
</p>
<ul>
<li>
<p>A required <a class="itsmarkup" href="#att.selector.attribute.selector" shape="rect">selector</a> attribute. It contains an XPath expression which selects the nodes to which this rule applies.
</p>
</li>
<li>
<p>A required <a class="itsmarkup" href="#termRule.attributes" shape="rect">term</a> attribute with the value "yes" or "no".
</p>
</li>
<li>
<p>Exactly one of the following:</p>
<ul>
<li>
<p>A <a class="itsmarkup" href="#termRule.attributes" shape="rect">termInfoPointer</a> attribute that contains a relative XPath expression pointing to a node that holds the terminology information.
</p>
</li>
<li>
<p>A <a class="itsmarkup" href="#att.local.no-ns.attribute.termInfoRef" shape="rect">termInfoRef</a> attribute that contains a URI referring to the resource providing information about the term.
</p>
</li>
<li>
<p>A <a class="itsmarkup" href="#termRule.attributes" shape="rect">termInfoRefPointer</a> attribute that contains a relative XPath expression pointing to a node that holds the URI referring to the location of the
terminology information.
</p>
</li>
</ul>
</li>
</ul>
<div class="exampleOuter"><a name="d3e3341" id="d3e3341">Example 29: Usage of the termInfoPointer attribute</a><div class="exampleInner"><pre xml:space="preserve">
<text
xmlns:its="http://www.w3.org/2005/11/its" >
<its:rules version="1.0">
<its:termRule selector="//term" term="yes" termInfoPointer="id(@def)"/>
</its:rules>
<p>We may define <term def="TDPV">discoursal point of view</term>
as <gloss xml:id="TDPV">the relationship, expressed through discourse
structure, between the implied author or some other addresser,
and the fiction.</gloss>
</p>
</text></pre></div>
<p>[Source file: <a href="EX-terms-selector-1.xml" shape="rect">EX-terms-selector-1.xml</a>]
</p>
</div>
<div class="exampleOuter"><a name="d3e3354" id="d3e3354">Example 30: Usage of the termInfoRef attribute</a><div class="exampleInner"><pre xml:space="preserve">
<text
xmlns:its="http://www.w3.org/2005/11/its" >
<its:rules version="1.0">
<its:termRule selector="//term[1]" term="yes" termInfoRef="#TDPV"/>
</its:rules>
<p>We may define <term>discoursal point of view</term>
as <gloss xml:id="TDPV">the relationship, expressed through discourse
structure, between the implied author or some other addresser,
and the fiction.</gloss>
</p>
</text></pre></div>
<p>[Source file: <a href="EX-terms-selector-2.xml" shape="rect">EX-terms-selector-2.xml</a>]
</p>
</div>
<div class="exampleOuter"><a name="d3e3367" id="d3e3367">Example 31: Usage of the termInfoRefPointer attribute</a><div class="exampleInner"><pre xml:space="preserve">
<text
xmlns:its="http://www.w3.org/2005/11/its" >
<its:rules version="1.0">
<its:termRule selector="//term" term="yes" termInfoRefPointer="@target"/>
</its:rules>
<p>We may define <term target="#TDPV">discoursal point of view</term>
as <gloss xml:id="TDPV">the relationship, expressed through discourse
structure, between the implied author or some other addresser,
and the fiction.</gloss>
</p>
</text></pre></div>
<p>[Source file: <a href="EX-terms-selector-3.xml" shape="rect">EX-terms-selector-3.xml</a>]
</p>
</div>
<p>LOCAL: The following local markup is available for the <a href="#terminology" shape="rect">Terminology</a> data category:
</p>
<ul>
<li>
<p>A <a class="itsmarkup" href="#att.local.no-ns.attribute.term" shape="rect">term</a> attribute with the value "yes" or "no".
</p>
</li>
<li>
<p>An optional <a class="itsmarkup" href="#att.local.no-ns.attribute.termInfoRef" shape="rect">termInfoRef</a> attribute that contains a URI referring to the resource providing information about the term.
</p>
</li>
</ul>
<div class="exampleOuter"><a name="d3e3404" id="d3e3404">Example 32: The Terminology data category expressed locally</a><div class="exampleInner"><pre xml:space="preserve">
<book
xmlns:its="http://www.w3.org/2005/11/its"
its:version="1.0">
<head>...</head>
<body> ... <p>And he said: you need a
new <quote
its:term="yes">motherboard</quote>
</p> ...
</body>
</book></pre></div>
<p>[Source file: <a href="EX-terms-selector-4.xml" shape="rect">EX-terms-selector-4.xml</a>]
</p>
</div>
</div>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="terminology-markup" id="terminology-markup" shape="rect"></a>6.4.3 Markup Declarations for Terminology
</h4>
<dl>
<dt class="label">termRule</dt>
<dd>
<table class="scrap" summary="Scrap">
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="termRule" id="termRule" shape="rect"></a>[42]
</td>
<td rowspan="1" colspan="1"><code>termRule</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> element its:termRule { termRule.content, <a href="#termRule.attributes" shape="rect">termRule.attributes</a> }</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="termRule.content" id="termRule.content" shape="rect"></a>[43]
</td>
<td rowspan="1" colspan="1"><code>termRule.content</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> empty</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="termRule.attributes" id="termRule.attributes" shape="rect"></a>[44]
</td>
<td rowspan="1" colspan="1"><code>termRule.attributes</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#att.selector.attributes" shape="rect">att.selector.attributes</a>,
attribute term { "yes" | "no" },
attribute termInfoRef { xsd:anyURI }?,
attribute termInfoRefPointer { string }?,
attribute termInfoPointer { string }?</code></td>
</tr>
</tbody>
</table>
</dd>
<dt class="label"><a name="att.term" id="att.term" shape="rect"></a>att.term
</dt>
<dd>
<table class="scrap" summary="Scrap">
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.term.attributes" id="att.term.attributes" shape="rect"></a>[45]
</td>
<td rowspan="1" colspan="1"><code>att.term.attributes</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#att.term.attribute.termInfoRef" shape="rect">att.term.attribute.termInfoRef</a>, <a href="#att.term.attribute.term" shape="rect">att.term.attribute.term</a>
</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.term.attribute.termInfoRef" id="att.term.attribute.termInfoRef" shape="rect"></a>[46]
</td>
<td rowspan="1" colspan="1"><code>att.term.attribute.termInfoRef</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> attribute its:termInfoRef { xsd:anyURI }?</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.term.attribute.term" id="att.term.attribute.term" shape="rect"></a>[47]
</td>
<td rowspan="1" colspan="1"><code>att.term.attribute.term</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> attribute its:term { "yes" | "no" }?</code></td>
</tr>
</tbody>
</table>
</dd>
</dl>
</div>
</div>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="directionality" id="directionality" shape="rect"></a>6.5 Directionality
</h3>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="directionality-definition" id="directionality-definition" shape="rect"></a>6.5.1 Definition
</h4>
<p>The <a href="#directionality" shape="rect">Directionality</a> data category allows the user to specify the base writing direction of blocks, embeddings and overrides for the Unicode bidirectional
algorithm. It has four values: "ltr", "rtl", "lro" and "rlo".
</p>
<div class="note">
<p class="prefix"><b>Note:</b></p>
<p>ITS defines only the values of the <a href="#directionality" shape="rect">Directionality</a> data category and their inheritance. The behavior of text labeled in this way may vary, according
to the implementation. Implementers are encouraged, however, to model the
behavior on that described in the CSS 2.1 specification or its successor. In
such a case, the effect of the data category's values would correspond to
the following CSS rules:
</p>
<ul>
<li>
<p>Data category value: "ltr" (left-to-right text)</p>
<p>CSS rule: <code>*[dir="ltr"] { unicode-bidi: embed; direction: ltr}</code>
</p>
</li>
<li>
<p>Data category value: "rtl" (right-to-left text)</p>
<p>CSS rule: <code>*[dir="rtl"] { unicode-bidi: embed; direction: rtl}</code>
</p>
</li>
<li>
<p>Data category value: "rlo" (left-to-right override)</p>
<p>CSS rule: <code>*[dir="lro"] { unicode-bidi: bidi-override; direction: ltr}</code>
</p>
</li>
<li>
<p>Data category value: "rlo" (right-to-left text)</p>
<p>CSS rule: <code>*[dir="rlo"] { unicode-bidi: bidi-override; direction: rtl}</code>
</p>
</li>
</ul>
<p>More information about how to use this data category is provided by <a title="What you need to know about the bidi algorithm and inline markup" href="#bidiarticle" shape="rect">[Bidi Article]</a>.
</p>
</div>
</div>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="directionality-implementation" id="directionality-implementation" shape="rect"></a>6.5.2 Implementation
</h4>
<p>The <a href="#directionality" shape="rect">Directionality</a> data category can be expressed with global rules, or locally on an individual element. The information applies to the textual
content of the element, <em>including</em> child elements and attributes. The default is that both elements and attributes have the directionality of left-to-right.
</p>
<p>GLOBAL: The <a class="itsmarkup" href="#dirRule" shape="rect">dirRule</a> element contains the following:
</p>
<ul>
<li>
<p>A required <a class="itsmarkup" href="#att.selector.attribute.selector" shape="rect">selector</a> attribute. It contains an XPath expression which selects the nodes to which this rule applies.
</p>
</li>
<li>
<p>A required <a class="itsmarkup" href="#dirRule.attributes" shape="rect">dir</a> attribute with the value "ltr", "rtl", "lro" or "rlo".
</p>
</li>
</ul>
<div class="exampleOuter"><a name="EX-dir-selector-1.xml" id="EX-dir-selector-1.xml">Example 33: Document which needs global rules for directionality</a><p>In this document the right-to-left directionality is marked using a <code>direction</code> attribute with a value "rtlText".
</p>
<div class="exampleInner"><pre xml:space="preserve">
<text xml:lang="en">
<body>
<par>In Hebrew, the title <quote xml:lang="he" direction="rtlText"><span dir="rtl">פעילות הבינאום, W3C</span></quote>
means <quote>Internationalization Activity, W3C</quote>.</par>
</body>
</text></pre></div>
<p>[Source file: <a href="EX-dir-selector-1.xml" shape="rect">EX-dir-selector-1.xml</a>]
</p>
</div>
<div class="exampleOuter"><a name="EX-dir-selector-2.xml" id="EX-dir-selector-2.xml">Example 34: The Directionality data category expressed with global rules</a><p>The <a class="itsmarkup" href="#dirRule" shape="rect">dirRule</a> element indicates that all elements with an attribute <code>direction="rtlText"</code> have right-to-left content.
</p>
<div class="exampleInner"><pre xml:space="preserve">
<its:rules
xmlns:its="http://www.w3.org/2005/11/its" version="1.0">
<its:dirRule dir="rtl" selector="//*[@direction='rtlText']"/>
</its:rules></pre></div>
<p>[Source file: <a href="EX-dir-selector-2.xml" shape="rect">EX-dir-selector-2.xml</a>]
</p>
</div>
<p>LOCAL: The following local markup is available for the <a href="#directionality" shape="rect">Directionality</a> data category:
</p>
<ul>
<li>
<p>A <a class="itsmarkup" href="#att.local.no-ns.attribute.dir" shape="rect">dir</a> attribute with the value "ltr", "rtl", "lro" or "rlo".
</p>
</li>
</ul>
<div class="exampleOuter"><a name="d3e3662" id="d3e3662">Example 35: The Directionality data category expressed locally</a><p>On the first <code>quote</code> element, the <code>its:dir="rtl"</code> attribute indicates a right-to-left content.
</p>
<div class="exampleInner"><pre xml:space="preserve">
<text
xmlns:its="http://www.w3.org/2005/11/its" xml:lang="en"
its:version="1.0">
<body>
<par>In Arabic, the title <quote xml:lang="ar"
its:dir="rtl"><span dir="rtl">نشاط التدويل، W3C</span></quote>
means <quote>Internationalization Activity, W3C</quote>.</par>
</body>
</text></pre></div>
<p>[Source file: <a href="EX-dir-selector-3.xml" shape="rect">EX-dir-selector-3.xml</a>]
</p>
</div>
</div>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="directionality-markup" id="directionality-markup" shape="rect"></a>6.5.3 Markup Declarations for Directionality
</h4>
<dl>
<dt class="label">dirRule</dt>
<dd>
<table class="scrap" summary="Scrap">
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="dirRule" id="dirRule" shape="rect"></a>[48]
</td>
<td rowspan="1" colspan="1"><code>dirRule</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> element its:dirRule { dirRule.content, <a href="#dirRule.attributes" shape="rect">dirRule.attributes</a> }</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="dirRule.content" id="dirRule.content" shape="rect"></a>[49]
</td>
<td rowspan="1" colspan="1"><code>dirRule.content</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> empty</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="dirRule.attributes" id="dirRule.attributes" shape="rect"></a>[50]
</td>
<td rowspan="1" colspan="1"><code>dirRule.attributes</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#att.selector.attributes" shape="rect">att.selector.attributes</a>,
attribute dir { "ltr" | "rtl" | "lro" | "rlo" }</code></td>
</tr>
</tbody>
</table>
</dd>
<dt class="label"><a name="att.dir" id="att.dir" shape="rect"></a>att.dir
</dt>
<dd>
<table class="scrap" summary="Scrap">
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.dir.attributes" id="att.dir.attributes" shape="rect"></a>[51]
</td>
<td rowspan="1" colspan="1"><code>att.dir.attributes</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#att.dir.attribute.dir" shape="rect">att.dir.attribute.dir</a>
</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="att.dir.attribute.dir" id="att.dir.attribute.dir" shape="rect"></a>[52]
</td>
<td rowspan="1" colspan="1"><code>att.dir.attribute.dir</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> attribute its:dir { "ltr" | "rtl" | "lro" | "rlo" }?</code></td>
</tr>
</tbody>
</table>
</dd>
</dl>
</div>
</div>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="ruby-annotation" id="ruby-annotation" shape="rect"></a>6.6 Ruby
</h3>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="ruby-definition" id="ruby-definition" shape="rect"></a>6.6.1 Definition
</h4>
<p>The <a href="#ruby-annotation" shape="rect">Ruby</a> data category is used for a run of text that
is associated with another run of text, referred to as the
base text. Ruby text is used to provide a short annotation
of the associated base text. It is most often used to
provide a reading (pronunciation) guide.
</p>
</div>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="ruby-implementation" id="ruby-implementation" shape="rect"></a>6.6.2 Implementation
</h4>
<p>The <a href="#ruby-annotation" shape="rect">Ruby</a> data category can be expressed with global rules, or locally. There is no inheritance.
</p>
<p>GLOBAL: The <a class="itsmarkup" href="#rubyRule" shape="rect">rubyRule</a> element contains the following:
</p>
<ul>
<li>
<p>A required <a class="itsmarkup" href="#att.selector.attribute.selector" shape="rect">selector</a> attribute. It contains an XPath expression which selects the nodes to which this rule applies. This is the ruby base text.
</p>
</li>
<li>
<p>An optional <a class="itsmarkup" href="#rubyRule.attributes" shape="rect">rubyPointer</a> attribute that contains a relative XPath expression pointing to a node that corresponds to the ruby element.
</p>
</li>
<li>
<p>An optional <a class="itsmarkup" href="#rubyRule.attributes" shape="rect">rpPointer</a> attribute that contains a relative XPath expression pointing to a node that corresponds to the ruby parenthesis.
</p>
</li>
<li>
<p>An optional <a class="itsmarkup" href="#rubyRule.attributes" shape="rect">rbcPointer</a> attribute that contains a relative XPath expression pointing to a node that corresponds to the ruby base container.
</p>
</li>
<li>
<p>An optional <a class="itsmarkup" href="#rubyRule.attributes" shape="rect">rtcPointer</a> attribute that contains a relative XPath expression pointing to a node that corresponds to the ruby text container.
</p>
</li>
<li>
<p>An optional <a class="itsmarkup" href="#rubyRule.attributes" shape="rect">rbspanPointer</a> attribute that contains a relative XPath expression pointing to a node that corresponds to the <a class="itsmarkup" href="#rubyText.attributes" shape="rect">rbspan</a> attribute.
</p>
</li>
<li>
<p>An optional <a class="itsmarkup" href="#rubyText" shape="rect">rubyText</a> element that contains the ruby
text.
</p>
</li>
<li>
<p>An optional <a class="itsmarkup" href="#rubyRule.attributes" shape="rect">rtPointer</a> attribute that contains a relative XPath expression pointing to a node that corresponds to the ruby text.
</p>
</li>
</ul>
<div class="note">
<p class="prefix"><b>Note:</b></p>
<p>Where legacy formats do not contain ruby markup, it is still possible to associate ruby text with a specified range of document
content using the <a class="itsmarkup" href="#rubyRule" shape="rect">rubyRule</a> element.
</p>
</div>
<div class="exampleOuter"><a name="EX-ruby-legacy-1" id="EX-ruby-legacy-1">Example 36: Adding ruby text with a rubyRule element</a><div class="exampleInner"><pre xml:space="preserve">
<text
xmlns:its="http://www.w3.org/2005/11/its" >
<head> ...
<its:rules version="1.0">
<its:rubyRule selector="/text/body/img[1]/@alt">
<its:rubyText>World Wide Web Consortium</its:rubyText>
</its:rubyRule>
</its:rules>
</head>
<body>
<img src="w3c_home.png" alt="W3C"/> ...
</body>
</text></pre></div>
<p>[Source file: <a href="EX-ruby-legacy-1.xml" shape="rect">EX-ruby-legacy-1.xml</a>]
</p>
</div>
<p>LOCAL: In a document, the <a href="#ruby-annotation" shape="rect">Ruby</a> data category is realized with a
<a class="itsmarkup" href="#ruby" shape="rect">ruby</a> element. It contains the following:
</p>
<ul>
<li>
<p>An <a class="itsmarkup" href="#rb" shape="rect">rb</a> element that contains the ruby base text and allows for <a href="#selection-local" shape="rect">local ITS markup</a>.
</p>
</li>
<li>
<p>An <a class="itsmarkup" href="#rp" shape="rect">rp</a> element that contains the ruby parenthesis. It is used in case of simple markup to specify characters that can denote the
beginning and end of ruby text when user agents do not have other ways to present ruby text distinctively from the base text.
</p>
</li>
<li>
<p>An <a class="itsmarkup" href="#rt" shape="rect">rt</a> element that contains the ruby text and allows for <a href="#selection-local" shape="rect">local ITS markup</a>. It has an optional <a class="itsmarkup" href="#rubyText.attributes" shape="rect">rbspan</a> attribute. The <a class="itsmarkup" href="#rubyText.attributes" shape="rect">rbspan</a> attribute allows an <a class="itsmarkup" href="#rt" shape="rect">rt</a> element to span multiple <a class="itsmarkup" href="#rb" shape="rect">rb</a> elements.
</p>
</li>
<li>
<p>An <a class="itsmarkup" href="#rbc" shape="rect">rbc</a> element that contains the ruby base container.
</p>
</li>
<li>
<p>An <a class="itsmarkup" href="#rtc" shape="rect">rtc</a> element that contains the ruby text container.
</p>
</li>
</ul>
<p>All these elements share the attributes of the <a class="itsmarkup" href="#span" shape="rect">span</a> element.
</p>
<div class="exampleOuter"><a name="EX-ruby-implementation-1" id="EX-ruby-implementation-1">Example 37: The Ruby data category expressed locally</a><div class="exampleInner"><pre xml:space="preserve">
<text
xmlns:its="http://www.w3.org/2005/11/its"
its:version="1.0">
<head> ... </head>
<body>
<p>この本は <its:ruby>
<its:rb>慶応義塾大学</its:rb>
<its:rp>(</its:rp>
<its:rt>けいおうぎじゅくだいがく</its:rt>
<its:rp>)</its:rp>
</its:ruby>の歴史を説明するものです。</p>
</body>
</text></pre></div>
<p>[Source file: <a href="EX-ruby-implementation-1.xml" shape="rect">EX-ruby-implementation-1.xml</a>]
</p>
</div>
<div class="note">
<p class="prefix"><b>Note:</b></p>
<p>The structure of the content model for the
<a class="itsmarkup" href="#ruby" shape="rect">ruby</a> element is identical with the structure of
ruby markup as defined in <a title="Ruby Annotation" href="#ruby-tr" shape="rect">[Ruby-TR]</a>. An implementation of the <a href="#ruby-annotation" shape="rect">Ruby</a> data category is encouraged, but not mandated follow the <a href="http://www.w3.org/TR/ruby/#conformance" shape="rect">conformance criteria for ruby</a> defined in that specification.
</p>
<p>The structure of ruby defined in section 5.4 of <a title="OASIS
 Open Document Format for Office Applications (OpenDocument)." href="#opendocument" shape="rect">[OpenDocument]</a> is also compliant with
ruby defined in this specification.
</p>
</div>
</div>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="ruby-markup" id="ruby-markup" shape="rect"></a>6.6.3 Markup Declarations for Ruby
</h4>
<dl>
<dt class="label">rubyRule</dt>
<dd>
<table class="scrap" summary="Scrap">
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="rubyRule" id="rubyRule" shape="rect"></a>[53]
</td>
<td rowspan="1" colspan="1"><code>rubyRule</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> element its:rubyRule { rubyRule.content, <a href="#rubyRule.attributes" shape="rect">rubyRule.attributes</a> }</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="rubyRule.content" id="rubyRule.content" shape="rect"></a>[54]
</td>
<td rowspan="1" colspan="1"><code>rubyRule.content</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#rubyText" shape="rect">rubyText</a>?</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="rubyRule.attributes" id="rubyRule.attributes" shape="rect"></a>[55]
</td>
<td rowspan="1" colspan="1"><code>rubyRule.attributes</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#att.selector.attributes" shape="rect">att.selector.attributes</a>,
attribute rubyPointer { string }?,
attribute rtPointer { string }?,
attribute rpPointer { string }?,
attribute rbcPointer { string }?,
attribute rtcPointer { string }?,
attribute rbspanPointer { string }?</code></td>
</tr>
</tbody>
</table>
</dd>
<dt class="label">rubyText</dt>
<dd>
<table class="scrap" summary="Scrap">
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="rubyText" id="rubyText" shape="rect"></a>[56]
</td>
<td rowspan="1" colspan="1"><code>rubyText</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> element its:rubyText { rubyText.content, <a href="#rubyText.attributes" shape="rect">rubyText.attributes</a> }</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="rubyText.content" id="rubyText.content" shape="rect"></a>[57]
</td>
<td rowspan="1" colspan="1"><code>rubyText.content</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> text</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="rubyText.attributes" id="rubyText.attributes" shape="rect"></a>[58]
</td>
<td rowspan="1" colspan="1"><code>rubyText.attributes</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#att.local.no-ns.attributes" shape="rect">att.local.no-ns.attributes</a>, attribute rbspan { string }?</code></td>
</tr>
</tbody>
</table>
</dd>
<dt class="label">ruby</dt>
<dd>
<table class="scrap" summary="Scrap">
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="ruby" id="ruby" shape="rect"></a>[59]
</td>
<td rowspan="1" colspan="1"><code>ruby</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> element its:ruby { ruby.content, <a href="#ruby.attributes" shape="rect">ruby.attributes</a> }</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="ruby.content" id="ruby.content" shape="rect"></a>[60]
</td>
<td rowspan="1" colspan="1"><code>ruby.content</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> ( <a href="#rb" shape="rect">rb</a>, ( <a href="#rt" shape="rect">rt</a> | ( <a href="#rp" shape="rect">rp</a>, <a href="#rt" shape="rect">rt</a>, <a href="#rp" shape="rect">rp</a> ) ) ) | ( <a href="#rbc" shape="rect">rbc</a>, <a href="#rtc" shape="rect">rtc</a>, <a href="#rtc" shape="rect">rtc</a>? )</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="ruby.attributes" id="ruby.attributes" shape="rect"></a>[61]
</td>
<td rowspan="1" colspan="1"><code>ruby.attributes</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#att.local.no-ns.attributes" shape="rect">att.local.no-ns.attributes</a>
</code></td>
</tr>
</tbody>
</table>
</dd>
<dt class="label">rb</dt>
<dd>
<table class="scrap" summary="Scrap">
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="rb" id="rb" shape="rect"></a>[62]
</td>
<td rowspan="1" colspan="1"><code>rb</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> element its:rb { rb.content, <a href="#rb.attributes" shape="rect">rb.attributes</a> }</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="rb.content" id="rb.content" shape="rect"></a>[63]
</td>
<td rowspan="1" colspan="1"><code>rb.content</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> ( text | <a href="#span" shape="rect">span</a> )*</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="rb.attributes" id="rb.attributes" shape="rect"></a>[64]
</td>
<td rowspan="1" colspan="1"><code>rb.attributes</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#att.local.no-ns.attributes" shape="rect">att.local.no-ns.attributes</a>
</code></td>
</tr>
</tbody>
</table>
</dd>
<dt class="label">rt</dt>
<dd>
<table class="scrap" summary="Scrap">
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="rt" id="rt" shape="rect"></a>[65]
</td>
<td rowspan="1" colspan="1"><code>rt</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> element its:rt { rt.content, <a href="#rt.attributes" shape="rect">rt.attributes</a> }</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="rt.content" id="rt.content" shape="rect"></a>[66]
</td>
<td rowspan="1" colspan="1"><code>rt.content</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> ( text | <a href="#span" shape="rect">span</a> )*</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="rt.attributes" id="rt.attributes" shape="rect"></a>[67]
</td>
<td rowspan="1" colspan="1"><code>rt.attributes</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#att.local.no-ns.attributes" shape="rect">att.local.no-ns.attributes</a>, attribute rbspan { string }?</code></td>
</tr>
</tbody>
</table>
</dd>
<dt class="label">rbc</dt>
<dd>
<table class="scrap" summary="Scrap">
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="rbc" id="rbc" shape="rect"></a>[68]
</td>
<td rowspan="1" colspan="1"><code>rbc</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> element its:rbc { rbc.content, <a href="#rbc.attributes" shape="rect">rbc.attributes</a> }</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="rbc.content" id="rbc.content" shape="rect"></a>[69]
</td>
<td rowspan="1" colspan="1"><code>rbc.content</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#rb" shape="rect">rb</a>+</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="rbc.attributes" id="rbc.attributes" shape="rect"></a>[70]
</td>
<td rowspan="1" colspan="1"><code>rbc.attributes</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#att.local.no-ns.attributes" shape="rect">att.local.no-ns.attributes</a>
</code></td>
</tr>
</tbody>
</table>
</dd>
<dt class="label">rtc</dt>
<dd>
<table class="scrap" summary="Scrap">
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="rtc" id="rtc" shape="rect"></a>[71]
</td>
<td rowspan="1" colspan="1"><code>rtc</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> element its:rtc { rtc.content, <a href="#rtc.attributes" shape="rect">rtc.attributes</a> }</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="rtc.content" id="rtc.content" shape="rect"></a>[72]
</td>
<td rowspan="1" colspan="1"><code>rtc.content</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#rt" shape="rect">rt</a>+</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="rtc.attributes" id="rtc.attributes" shape="rect"></a>[73]
</td>
<td rowspan="1" colspan="1"><code>rtc.attributes</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#att.local.no-ns.attributes" shape="rect">att.local.no-ns.attributes</a>
</code></td>
</tr>
</tbody>
</table>
</dd>
<dt class="label">rp</dt>
<dd>
<table class="scrap" summary="Scrap">
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="rp" id="rp" shape="rect"></a>[74]
</td>
<td rowspan="1" colspan="1"><code>rp</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> element its:rp { rp.content, <a href="#rp.attributes" shape="rect">rp.attributes</a> }</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="rp.content" id="rp.content" shape="rect"></a>[75]
</td>
<td rowspan="1" colspan="1"><code>rp.content</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> text</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="rp.attributes" id="rp.attributes" shape="rect"></a>[76]
</td>
<td rowspan="1" colspan="1"><code>rp.attributes</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#att.local.no-ns.attributes" shape="rect">att.local.no-ns.attributes</a>
</code></td>
</tr>
</tbody>
</table>
</dd>
</dl>
</div>
</div>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="language-information" id="language-information" shape="rect"></a>6.7 Language Information
</h3>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="langinfo-definition" id="langinfo-definition" shape="rect"></a>6.7.1 Definition
</h4>
<p>The element <a class="itsmarkup" href="#langRule" shape="rect">langRule</a> is used to express the language of a given piece of
content. The <a class="itsmarkup" href="#langRule.attributes" shape="rect">langPointer</a> attribute points to the markup which expresses the
language of the text selected by the selector attribute. This markup <a href="#rfc-keywords" shape="rect">MUST</a> use
values that conform to <a title="Tags for Identifying Languages" href="#bcp47" shape="rect">[BCP47]</a>. The recommended way to specify language identification is to use <code>xml:lang</code>. The <a class="itsmarkup" href="#langRule" shape="rect">langRule</a> element is intended only as a fall-back
mechanism for documents where language is identified with another construct.
</p>
<div class="exampleOuter"><a name="EX-lang-definition-1" id="EX-lang-definition-1">Example 38: Pointing to language information via langRule
</a><p>The following <a class="itsmarkup" href="#langRule" shape="rect">langRule</a> element expresses that
the content of all <code>p</code> elements (including attribute values and
textual content of child elements) are in the language indicated
by <code>mylangattribute</code>, which is attached to the <code>p</code> elements,
and expresses language using values conformant to <a title="Tags for Identifying Languages" href="#bcp47" shape="rect">[BCP47]</a>.
</p>
<div class="exampleInner"><pre xml:space="preserve">
<its:rules
xmlns:its="http://www.w3.org/2005/11/its" version="1.0">
<its:langRule selector="//p" langPointer="@mylangattribute"/>
</its:rules></pre></div>
<p>[Source file: <a href="EX-lang-definition-1.xml" shape="rect">EX-lang-definition-1.xml</a>]
</p>
</div>
<div class="note">
<p class="prefix"><b>Note:</b></p>
<p>The <a href="#language-information" shape="rect">Language Information</a> data category only provides for rules to be
expressed at a global level. Locally users are able to use <code>xml:lang</code> (which is defined by XML) or an attribute
specific to the format in question (as in <a href="#EX-lang-definition-1" shape="rect">Example 38</a>).
</p>
<p>
<code>xml:lang</code> is the preferable means of language identification. To ease the
usage of <code>xml:lang</code>, a declaration for this attribute is part of the
non-normative XML DTD and XML Schema document for ITS markup
declarations. There is no declaration of <code>xml:lang</code> in the non-normative
RELAX NG document for ITS, since in RELAX NG it is not necessary to
declare attributes from the XML namespace.
</p>
<p>Applying the <a href="#language-information" shape="rect">Language Information</a> data category to <code>xml:lang</code> attributes using global rules is not necessary, since <code>xml:lang</code> is the standard way to specify language information in XML. <code>xml:lang</code> is defined in terms of <a href="http://www.w3.org/TR/2006/REC-xml-20060816/#sec-lang-tag" shape="rect">RFC 3066 or its successor</a> (<a title="Tags for Identifying Languages" href="#bcp47" shape="rect">[BCP47]</a> is the "Best Common Practice" for language identification and encompasses <a title="Tags for the Identification of Languages" href="#rfc3066" shape="rect">[RFC 3066]</a> and its successors.)
</p>
</div>
</div>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="langinfo-implementation" id="langinfo-implementation" shape="rect"></a>6.7.2 Implementation
</h4>
<p>The <a href="#language-information" shape="rect">Language Information</a> data category can be expressed only with global rules. The information applies to the textual content of the element, <em>including</em> child elements and attributes. There is no default.
</p>
<p>GLOBAL: The <a class="itsmarkup" href="#langRule" shape="rect">langRule</a> element contains the following:
</p>
<ul>
<li>
<p>A required <a class="itsmarkup" href="#att.selector.attribute.selector" shape="rect">selector</a> attribute. It contains an XPath expression which selects the nodes to which this rule applies.
</p>
</li>
<li>
<p>A required <a class="itsmarkup" href="#langRule.attributes" shape="rect">langPointer</a> attribute that contains a relative XPath expression pointing to a node that contains language information.
</p>
</li>
</ul>
</div>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="langinfo-markup" id="langinfo-markup" shape="rect"></a>6.7.3 Markup Declarations for Language Information
</h4>
<dl>
<dt class="label">langRule</dt>
<dd>
<table class="scrap" summary="Scrap">
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="langRule" id="langRule" shape="rect"></a>[77]
</td>
<td rowspan="1" colspan="1"><code>langRule</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> element its:langRule { langRule.content, <a href="#langRule.attributes" shape="rect">langRule.attributes</a> }</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="langRule.content" id="langRule.content" shape="rect"></a>[78]
</td>
<td rowspan="1" colspan="1"><code>langRule.content</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> empty</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="langRule.attributes" id="langRule.attributes" shape="rect"></a>[79]
</td>
<td rowspan="1" colspan="1"><code>langRule.attributes</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#att.selector.attributes" shape="rect">att.selector.attributes</a>, attribute langPointer { string }</code></td>
</tr>
</tbody>
</table>
</dd>
</dl>
</div>
</div>
<div class="div2">
<h3><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="elements-within-text" id="elements-within-text" shape="rect"></a>6.8 Elements Within Text
</h3>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="within-text-definition" id="within-text-definition" shape="rect"></a>6.8.1 Definition
</h4>
<p>The <a href="#elements-within-text" shape="rect">Elements Within Text</a> data category reveals if and how an element affects the way text content behaves from a linguistic viewpoint. This information
is for example relevant to provide basic text segmentation hints for tools such as translation memory systems. The values
associated with this data category are:
</p>
<ul>
<li>
<p>
"yes" : The element and its content are part of the flow of its parent element. For example the element <code>strong</code> in <a title="XHTML™ 1.0 The Extensible
 HyperText Markup Language (Second Edition)" href="#xhtml10" shape="rect">[XHTML 1.0]</a>:
</p>
<p>
<code><strong>Appaloosa horses</strong> have spotted coats.</code>
</p>
</li>
<li>
<p>
"nested" : The element is part of the flow of its parent element, its content is an independent flow. For example the element
<code>fn</code> in <a title="OASIS Darwin Information Typing
Architecture (DITA) Language Specification v1.0" href="#dita10" shape="rect">[DITA 1.0]</a>:
</p>
<p>
<code>Palouse horses<fn>A Palouse horse is the same as an Appaloosa.</fn> have
spotted coats.</code>
</p>
</li>
<li>
<p>
"no" : The element splits the text flow of its parent element and its content is an independent text flow. For example the
element <code>p</code> when inside the element <code>li</code> in DITA or XHTML:
</p>
<p>
<code><li>Palouse horses:
<p>They have spotted coats.</p>
<p>They have been bred by the Nez Perce.</p>
</li></code>
</p>
</li>
</ul>
</div>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="within-text-implementation" id="within-text-implementation" shape="rect"></a>6.8.2 Implementation
</h4>
<p>The <a href="#elements-within-text" shape="rect">Elements Within Text</a> data category can be expressed only with global rules. There is no inheritance. The default is that elements are not within
text.
</p>
<p>GLOBAL: The <a class="itsmarkup" href="#withinTextRule" shape="rect">withinTextRule</a> element contains the following:
</p>
<ul>
<li>
<p>A required <a class="itsmarkup" href="#att.selector.attribute.selector" shape="rect">selector</a> attribute. It contains an XPath expression which selects the nodes to which this rule applies.
</p>
</li>
<li>
<p>A required <a class="itsmarkup" href="#withinTextRule.attributes" shape="rect">withinText</a> attribute with the value "yes", "no" or "nested".
</p>
</li>
</ul>
<div class="exampleOuter"><a name="d3e4452" id="d3e4452">Example 39: Specifying elements within text with a withinTextRule element</a><div class="exampleInner"><pre xml:space="preserve">
<its:rules
xmlns:its="http://www.w3.org/2005/11/its" version="1.0">
<its:withinTextRule withinText="yes" selector="//b | //em | //i"/>
</its:rules></pre></div>
<p>[Source file: <a href="EX-within-text-implementation-1.xml" shape="rect">EX-within-text-implementation-1.xml</a>]
</p>
</div>
</div>
<div class="div3">
<h4><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="within-text-markup" id="within-text-markup" shape="rect"></a>6.8.3 Markup Declarations for Elements Within Text
</h4>
<dl>
<dt class="label">withinTextRule</dt>
<dd>
<table class="scrap" summary="Scrap">
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="withinTextRule" id="withinTextRule" shape="rect"></a>[80]
</td>
<td rowspan="1" colspan="1"><code>withinTextRule</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
element its:withinTextRule
{
withinTextRule.content,
<a href="#withinTextRule.attributes" shape="rect">withinTextRule.attributes</a>
}</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="withinTextRule.content" id="withinTextRule.content" shape="rect"></a>[81]
</td>
<td rowspan="1" colspan="1"><code>withinTextRule.content</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code> empty</code></td>
</tr>
</tbody>
<tbody>
<tr valign="baseline">
<td rowspan="1" colspan="1"><a name="withinTextRule.attributes" id="withinTextRule.attributes" shape="rect"></a>[82]
</td>
<td rowspan="1" colspan="1"><code>withinTextRule.attributes</code></td>
<td rowspan="1" colspan="1"> ::= </td>
<td rowspan="1" colspan="1"><code>
<a href="#att.selector.attributes" shape="rect">att.selector.attributes</a>,
attribute withinText { "yes" | "no" | "nested" }</code></td>
</tr>
</tbody>
</table>
</dd>
</dl>
</div>
</div>
</div>
</div>
<div class="back">
<div class="div1">
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="normative-references" id="normative-references" shape="rect"></a>A References
</h2>
<dl>
<dt class="label"><a name="bcp47" id="bcp47" shape="rect"></a>BCP47
</dt>
<dd>Addison Phillips, Mark Davis. <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt" shape="rect"><cite>Tags for Identifying Languages</cite></a>, September 2006. Available at <a href="http://www.rfc-editor.org/rfc/bcp/bcp47.txt" shape="rect">
http://www.rfc-editor.org/rfc/bcp/bcp47.txt</a>.
</dd>
<dt class="label"><a name="qa-framework" id="qa-framework" shape="rect"></a>QAFRAMEWORK
</dt>
<dd>Karl Dubost, Lynne Rosental, Dominique
Hazaël-Massieux, Lofton Henderson. <a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/" shape="rect"><cite>QA Framework:
Specification Guidelines</cite></a>. W3C Recommendation 17 August 2005. Available at <a href="http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/" shape="rect">
http://www.w3.org/TR/2005/REC-qaframe-spec-20050817/</a>. The latest version of
<a href="http://www.w3.org/TR/qaframe-spec/" shape="rect">QAFRAMEWORK</a> is available at
http://www.w3.org/TR/qaframe-spec/.
</dd>
<dt class="label"><a name="relaxng" id="relaxng" shape="rect"></a>RELAX NG
</dt>
<dd>Information technology -- Document Schema Definition Language (DSDL) -- Part 2: <cite>Regular-grammar-based validation -- RELAX NG</cite>. International Organization for Standardization (ISO) ISO/IEC 19757-2:2003.
</dd>
<dt class="label"><a name="rfc2119" id="rfc2119" shape="rect"></a>RFC 2119
</dt>
<dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt" shape="rect">Key Words for use in RFCs to Indicate
Requirement Levels</a>. IETF RFC 2119, March 1997. Available at <a href="http://www.ietf.org/rfc/rfc2119.txt" shape="rect">
http://www.ietf.org/rfc/rfc2119.txt</a>.
</dd>
<dt class="label"><a name="rfc3987" id="rfc3987" shape="rect"></a>RFC 3987
</dt>
<dd>Martin Dürst, Michel Suignard. <a href="http://www.ietf.org/rfc/rfc3987.txt" shape="rect"><cite>Internationalized Resource Identifiers (IRIs)</cite></a>. RFC 3987, January 2005. See <a href="http://www.ietf.org/rfc/rfc3987.txt" shape="rect">http://www.ietf.org/rfc/rfc3987.txt</a>.
</dd>
<dt class="label"><a name="xlink1" id="xlink1" shape="rect"></a>XLink 1.0
</dt>
<dd>Steve DeRose, Eve Maler, David Orchard. <a href="http://www.w3.org/TR/2001/REC-xlink-20010627/" shape="rect"><cite>XML Linking Language
1.0</cite></a>. W3C Recommendation 27 June 2001. Available at <a href="http://www.w3.org/TR/2001/REC-xlink-20010627/" shape="rect">
http://www.w3.org/TR/2001/REC-xlink-20010627/</a>. The latest version of <a href="http://www.w3.org/TR/xlink/" shape="rect">XLink 1.0</a> is available at
http://www.w3.org/TR/xlink/.
</dd>
<dt class="label"><a name="xml10spec" id="xml10spec" shape="rect"></a>XML 1.0
</dt>
<dd>Tim Bray, Jean Paoli, C.M. Sperberg-McQueen, et al., editors. <a href="http://www.w3.org/TR/2006/REC-xml-20060816/" shape="rect"><cite>Extensible Markup Language (XML) 1.0 (Fourth Edition)</cite></a>, W3C Recommendation 16 August 2006. Available at <a href="http://www.w3.org/TR/2006/REC-xml-20060816/" shape="rect">
http://www.w3.org/TR/2006/REC-xml-20060816/</a>. The latest version of <a href="http://www.w3.org/TR/REC-xml/" shape="rect">XML 1.0</a> is available at http://www.w3.org/TR/REC-xml/.
</dd>
<dt class="label"><a name="xmlinfoset" id="xmlinfoset" shape="rect"></a>XML Infoset
</dt>
<dd>John Cowan, Richard Tobin. <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/" shape="rect"><cite>XML Information Set
(Second Edition)</cite></a>. W3C Recommendation 4 February 2004. Available at <a href="http://www.w3.org/TR/2004/REC-xml-infoset-20040204/" shape="rect">
http://www.w3.org/TR/2004/REC-xml-infoset-20040204/</a>. The latest version of <a href="http://www.w3.org/TR/xml-infoset/" shape="rect">XML Infoset</a> is available at
http://www.w3.org/TR/xml-infoset/.
</dd>
<dt class="label"><a name="xmlns" id="xmlns" shape="rect"></a>XML Names
</dt>
<dd>Tim Bray, Dave Hollander, Andrew Layman, Richard Tobin. <a href="http://www.w3.org/TR/2006/REC-xml-names-20060816/" shape="rect"><cite>Namespaces in
XML (Second Edition)</cite></a>. W3C Recommendation 16 August 2006. Available at <a href="http://www.w3.org/TR/2006/REC-xml-names-20060816/" shape="rect">
http://www.w3.org/TR/2006/REC-xml-names-20060816/</a>. The latest version of <a href="http://www.w3.org/TR/REC-xml-names/" shape="rect">XML Names</a> is available at
http://www.w3.org/TR/REC-xml-names/.
</dd>
<dt class="label"><a name="xmlschema1" id="xmlschema1" shape="rect"></a>XML Schema
</dt>
<dd>Henry S. Thompson, David Beech, Murray Maloney,
Noah Mendelsohn. <a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/" shape="rect"><cite>XML Schema Part 1:
Structures Second Edition</cite></a>. W3C Recommendation 28 October 2004. Available at <a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/" shape="rect">
http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/</a>. The latest version of <a href="http://www.w3.org/TR/xmlschema-1/" shape="rect">XML Schema</a> is
available at http://www.w3.org/TR/xmlschema-1/.
</dd>
<dt class="label"><a name="xpath" id="xpath" shape="rect"></a>XPath 1.0
</dt>
<dd>James Clark. <a href="http://www.w3.org/TR/1999/REC-xpath-19991116" shape="rect"><cite>XML Path Language (XPath) Version 1.0</cite></a>. W3C Recommendation 16 November 1999. Available at <a href="http://www.w3.org/TR/1999/REC-xpath-19991116" shape="rect">
http://www.w3.org/TR/1999/REC-xpath-19991116</a>. The latest version of <a href="http://www.w3.org/TR/xpath" shape="rect">XPath 1.0</a> is available at
http://www.w3.org/TR/xpath.
</dd>
</dl>
</div>
<div class="div1">
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="informative-references" id="informative-references" shape="rect"></a>B References (Non-Normative)
</h2>
<dl>
<dt class="label"><a name="bidiarticle" id="bidiarticle" shape="rect"></a>Bidi Article
</dt>
<dd>Richard Ishida.
<a href="http://www.w3.org/International/articles/inline-bidi-markup/" shape="rect"><cite>What you need to know about the bidi algorithm and inline markup</cite></a>. Article of the <a href="http://www.w3.org/International/" shape="rect">W3C Internationalization Activity</a>,
June 2005.
</dd>
<dt class="label"><a name="css2-1" id="css2-1" shape="rect"></a>CSS 2.1
</dt>
<dd> Bert Bos, Tantek Çelik, Ian Hickson Håkon Wium Lie.
<a href="http://www.w3.org/TR/2006/WD-CSS21-20060411/" shape="rect"><cite>Cascading Style Sheets,
level 2 revision 1
CSS 2.1 Specification</cite></a>. W3C Working Draft 11 April 2006. Available at <a href="http://www.w3.org/TR/2006/WD-CSS21-20060411/" shape="rect">
http://www.w3.org/TR/2006/WD-CSS21-20060411/</a>. The latest version of <a href="http://www.w3.org/TR/CSS21/" shape="rect">CSS2</a> is available at
http://www.w3.org/TR/CSS21/.
</dd>
<dt class="label"><a name="dita10" id="dita10" shape="rect"></a>DITA 1.0
</dt>
<dd>Michael Priestley, JoAnn Hackos, et. al., editors. <a href="http://www.oasis-open.org/committees/download.php/15316/dita10.zip" shape="rect"><cite>OASIS Darwin Information Typing
Architecture (DITA) Language Specification v1.0</cite></a>. OASIS Standard 9 May 2005. Available at <a href="http://www.oasis-open.org/committees/download.php/15316/dita10.zip" shape="rect">http://www.oasis-open.org/committees/download.php/15316/dita10.zip</a>.
</dd>
<dt class="label"><a name="docbook" id="docbook" shape="rect"></a>DocBook
</dt>
<dd>Norman Walsh and Leonard Muellner. <a href="http://www.docbook.org/" shape="rect"><cite>DocBook: The Definitive Guide</cite></a>. Available at <a href="http://www.docbook.org/" shape="rect">
http://www.docbook.org/</a>.
</dd>
<dt class="label"><a name="geo-i18n-l10n" id="geo-i18n-l10n" shape="rect"></a>l10n i18n
</dt>
<dd>Richard Ishida, Susan Miller. <a href="http://www.w3.org/International/questions/qa-i18n" shape="rect">Localization vs.
Internationalization</a>. Article of the <a href="http://www.w3.org/International/" shape="rect">W3C Internationalization Activity</a>,
January 2006.
</dd>
<dt class="label"><a name="iso12200" id="iso12200" shape="rect"></a>ISO 12200
</dt>
<dd>(International Organization for Standardization). <cite>Machine-readable terminology interchange format (MARTIF) -- Negotiated interchange</cite>. [Geneva]: International Organization for Standardization, 1999.
</dd>
<dt class="label"><a name="itsreq" id="itsreq" shape="rect"></a>ITS REQ
</dt>
<dd>Yves Savourel. <a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/" shape="rect"><cite>Internationalization and
Localization Markup Requirements</cite></a>. W3C Working Draft 18 May 2006. Available at <a href="http://www.w3.org/TR/2006/WD-itsreq-20060518/" shape="rect">
http://www.w3.org/TR/2006/WD-itsreq-20060518/</a>. The latest version of <a href="http://www.w3.org/TR/itsreq/" shape="rect">ITS REQ</a> is available at
http://www.w3.org/TR/itsreq/.
</dd>
<dt class="label"><a name="reqlocdtd" id="reqlocdtd" shape="rect"></a>Localizable DTDs
</dt>
<dd>Richard Ishida, Yves Savourel
<a href="http://people.w3.org/rishida/localizable-dtds/" shape="rect"><cite>Requirements for Localizable DTD Design</cite></a>.
Working Draft 7 July 2003. Available at
<a href="http://people.w3.org/rishida/localizable-dtds/" shape="rect">http://people.w3.org/rishida/localizable-dtds/</a>.
</dd>
<dt class="label"><a name="nvdl" id="nvdl" shape="rect"></a>NVDL
</dt>
<dd>Information technology -- Document Schema Definition Languages (DSDL) -- Part 4: <cite>Namespace-based Validation Dispatching Language (NVDL)</cite>. International Organization for Standardization (ISO) ISO/IEC 19757-4:2003.
</dd>
<dt class="label"><a name="opendocument" id="opendocument" shape="rect"></a>OpenDocument
</dt>
<dd>Michael Brauer et al. <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office" shape="rect"><cite>OASIS
Open Document Format for Office Applications (OpenDocument).</cite></a>. Oasis Standard 1 May 2005. Available at <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office" shape="rect">
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office</a>. The latest
version of <a href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office" shape="rect">
OpenDocument</a> is available at
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office.
</dd>
<dt class="label"><a name="rfc3066" id="rfc3066" shape="rect"></a>RFC 3066
</dt>
<dd>Harald Alvestrand. <a href="http://www.ietf.org/rfc/rfc3066.txt" shape="rect"><cite>Tags for the Identification of Languages</cite></a>. RFC 3066, January 2001. Available at <a href="http://www.ietf.org/rfc/rfc3066.txt" shape="rect">http://www.ietf.org/rfc/rfc3066.txt</a>.
</dd>
<dt class="label"><a name="ruby-tr" id="ruby-tr" shape="rect"></a>Ruby-TR
</dt>
<dd>Marcin Sawicki (until 10 October, 1999), Michel
Suignard, Masayasu Ishikawa (石川 雅康), Martin Dürst, Tex Texin, <a href="http://www.w3.org/TR/ruby/" shape="rect"><cite>Ruby Annotation</cite></a>. W3C Recommendation 31 May 2001. Available at <a href="http://www.w3.org/TR/2001/REC-ruby-20010531/" shape="rect">
http://www.w3.org/TR/2001/REC-ruby-20010531/ </a>. The latest version of <a href="http://www.w3.org/TR/ruby/" shape="rect">Ruby Annotation</a> is available at
http://www.w3.org/TR/ruby/.
</dd>
<dt class="label"><a name="schematron" id="schematron" shape="rect"></a>Schematron
</dt>
<dd>Information technology -- Document Schema Definition Languages (DSDL) -- Part 3: <cite>Rule-based validation -- Schematron</cite>. International Organization for Standardization (ISO) ISO/IEC 19757-3:2003.
</dd>
<dt class="label"><a name="tei" id="tei" shape="rect"></a>TEI
</dt>
<dd>Lou Burnard and Syd Bauman (eds). <a href="http://www.tei-c.org/P5/" shape="rect"><cite>Text Encoding Initiative Guidelines development
version (P5)</cite></a>. TEI Consortium, Charlottesville, Virginia, USA, Text Encoding Initiative.
</dd>
<dt class="label"><a name="xhtml10" id="xhtml10" shape="rect"></a>XHTML 1.0
</dt>
<dd>Steven Pemberton et al. <a href="http://www.w3.org/TR/2002/REC-xhtml1-20020801/" shape="rect"><cite>XHTML™ 1.0 The Extensible
HyperText Markup Language (Second Edition)</cite></a>. W3C Recommendation 26 January 2000, revised 1 August 2002. Available at <a href="http://www.w3.org/TR/2002/REC-xhtml1-20020801/" shape="rect">
http://www.w3.org/TR/2002/REC-xhtml1-20020801/</a>. The latest version of <a href="http://www.w3.org/TR/xhtml1/" shape="rect">XHTML 1.0</a> is available at
http://www.w3.org/TR/xhtml1/.
</dd>
<dt class="label"><a name="xml-i18n-bp" id="xml-i18n-bp" shape="rect"></a>XML i18n BP
</dt>
<dd>Yves Savourel, Diane Stoick. <a href="http://www.w3.org/TR/2006/WD-xml-i18n-bp-20060518/" shape="rect"><cite>Best Practices for XML Internationalization</cite></a>. Available at <a href="http://www.w3.org/TR/2006/WD-xml-i18n-bp-20060518/" shape="rect">http://www.w3.org/TR/2006/WD-xml-i18n-bp-20060518/</a>. The latest version of <a href="http://www.w3.org/TR/xml-i18n-bp/" shape="rect">xml-i18n-bp</a> is available at http://www.w3.org/TR/xml-i18n-bp/.
</dd>
<dt class="label"><a name="xmlspecbib" id="xmlspecbib" shape="rect"></a>XMLSPEC
</dt>
<dd>
<a href="http://www.w3.org/2002/xmlspec/" shape="rect"><cite>The XML Spec Schema and
Stylesheets</cite></a>. Available at <a href="http://www.w3.org/2002/xmlspec/" shape="rect">
http://www.w3.org/2002/xmlspec/</a>.
</dd>
<dt class="label"><a name="xslt10" id="xslt10" shape="rect"></a>XSLT 1.0
</dt>
<dd> James Clark. <a href="http://www.w3.org/TR/1999/REC-xslt-19991116" shape="rect"><cite>XSL Transformations (XSLT)
Version 1.0</cite></a>. W3C Recommendation 16 November 1999. Available at <a href="http://www.w3.org/TR/1999/REC-xslt-19991116" shape="rect">
http://www.w3.org/TR/1999/REC-xslt-19991116</a>. The latest version of <a href="http://www.w3.org/TR/xslt" shape="rect">XSLT 1.0</a> is available at
http://www.w3.org/TR/xslt.
</dd>
<dt class="label"><a name="xul" id="xul" shape="rect"></a>XUL
</dt>
<dd>
<a href="http://www.xulplanet.com/" shape="rect"><cite>exTensible User Interface Language</cite></a>. Available at <a href="http://www.xulplanet.com/" shape="rect">
http://www.xulplanet.com/</a>.
</dd>
</dl>
</div>
<div class="div1">
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="its-markup-summary" id="its-markup-summary" shape="rect"></a>C Summary of ITS Markup (Non-Normative)
</h2>
<p>
<em>This section is informative.</em>
</p>
<p>The following list summarizes elements relating to global rules and their attributes:</p>
<ul>
<li>
<p>
<span class="new-term"><rules></span> Container for global rules.
</p>
<ul>
<li>
<p>
<span class="new-term">href</span>
</p>
<p>Pointer to external rules files.</p>
</li>
<li>
<p>
<span class="new-term">type</span>
</p>
<p>Type of pointer to external rules files.</p>
<p>Legal values are:</p>
<ul>
<li>
<p>
<em>simple</em>
</p>
</li>
</ul>
</li>
</ul>
<p></p>
<ul>
<li>
<p>
<span class="new-term">version</span>
</p>
<p>Version of the ITS schema.</p>
</li>
</ul>
<p></p>
</li>
<li>
<p>
<span class="new-term"><dirRule> </span>Rule about the Directionality data category.
</p>
<ul>
<li>
<p>
<span class="new-term">dir</span>
</p>
<p>The text direction for the selection.</p>
<p>Legal values are:</p>
<ul>
<li>
<p>
<em>ltr</em>
</p>
</li>
<li>
<p>
<em>rtl</em>
</p>
</li>
<li>
<p>
<em>lro</em>
</p>
</li>
<li>
<p>
<em>rlo</em>
</p>
</li>
</ul>
</li>
</ul>
<p></p>
<ul>
<li>
<p>
<span class="new-term">selector</span>
</p>
<p>XPath expression identifying the nodes to be selected.</p>
</li>
</ul>
<p></p>
</li>
<li>
<p>
<span class="new-term"><langRule> </span>Rule about the Language Information data category.
</p>
<ul>
<li>
<p>
<span class="new-term">langPointer</span>
</p>
<p>Relative XPath expression pointing to a node that contains language information.</p>
</li>
</ul>
<p></p>
<ul>
<li>
<p>
<span class="new-term">selector</span>
</p>
<p>XPath expression identifying the nodes to be selected.</p>
</li>
</ul>
<p></p>
</li>
<li>
<p>
<span class="new-term"><locNote> </span>Contains a localization note.
</p>
<ul>
<li>
<p>
<span class="new-term">translate</span>
</p>
<p>The Translate data category information to be attached to
the current node.
</p>
</li>
</ul>
<p></p>
<ul>
<li>
<p>
<span class="new-term">locNote</span>
</p>
<p>Localization note.</p>
</li>
<li>
<p>
<span class="new-term">locNoteType</span>
</p>
<p>The type of localization note.</p>
</li>
<li>
<p>
<span class="new-term">locNoteRef</span>
</p>
<p>URI referring to the location of the localization note.</p>
</li>
</ul>
<p></p>
<ul>
<li>
<p>
<span class="new-term">termInfoRef</span>
</p>
<p>Pointer to a resource containing
information about the term.
</p>
</li>
<li>
<p>
<span class="new-term">term</span>
</p>
<p>Indicates a term locally.</p>
</li>
</ul>
<p></p>
<ul>
<li>
<p>
<span class="new-term">dir</span>
</p>
<p>The text direction for the context.</p>
</li>
</ul>
<p></p>
</li>
<li>
<p>
<span class="new-term"><locNoteRule> </span>Rule about the Localization Note data category.
</p>
<ul>
<li>
<p>
<span class="new-term">locNotePointer</span>>
</p>
<p>Relative XPath expression pointing to a node that holds the localization note.</p>
</li>
<li>
<p>
<span class="new-term">locNoteType</span>
</p>
<p>The type of localization note.</p>
<p>Legal values are:</p>
<ul>
<li>
<p>
<em>alert</em>
</p>
</li>
<li>
<p>
<em>description</em>
</p>
</li>
</ul>
</li>
<li>
<p>
<span class="new-term">locNoteRef</span>
</p>
<p>URI referring to the location of the localization note.</p>
</li>
<li>
<p>
<span class="new-term">locNoteRefPointer</span>
</p>
<p>Relative XPath expression pointing to a node that holds the URI referring to the location of the localization note.</p>
</li>
</ul>
<p></p>
<ul>
<li>
<p>
<span class="new-term">selector</span>
</p>
<p>XPath expression identifying the nodes to be selected.</p>
</li>
</ul>
<p></p>
</li>
<li>
<p>
<span class="new-term"><termRule> </span>Rule about the Terminology data category.
</p>
<ul>
<li>
<p>
<span class="new-term">term</span>
</p>
<p>Indicates whether the selection is a term or not.</p>
<p>Legal values are:</p>
<ul>
<li>
<p>
<em>yes</em>
</p>
</li>
<li>
<p>
<em>no</em>
</p>
</li>
</ul>
</li>
<li>
<p>
<span class="new-term">termInfoRef</span>
</p>
<p>URI referring to the resource providing information about the term.</p>
</li>
<li>
<p>
<span class="new-term">termInfoRefPointer</span>
</p>
<p>Relative XPath expression pointing to a node containing a URI referring to the resource providing information about the term.</p>
</li>
<li>
<p>
<span class="new-term">termInfoPointer</span>
</p>
<p>Relative XPath expression pointing to a node containing
information about the term.
</p>
</li>
</ul>
<p></p>
<ul>
<li>
<p>
<span class="new-term">selector</span>
</p>
<p>XPath expression identifying the nodes to be selected.</p>
</li>
</ul>
<p></p>
</li>
<li>
<p>
<span class="new-term"><translateRule> </span>Rule about the Translate data category.
</p>
<ul>
<li>
<p>
<span class="new-term">translate</span>
</p>
<p>The Translate data category information to be
applied to selected nodes.
</p>
<p>Legal values are:</p>
<ul>
<li>
<p>
<em>yes</em>
</p>
</li>
<li>
<p>
<em>no</em>
</p>
</li>
</ul>
</li>
</ul>
<p></p>
<ul>
<li>
<p>
<span class="new-term">selector</span>
</p>
<p>XPath expression identifying the nodes to be selected.</p>
</li>
</ul>
<p></p>
</li>
<li>
<p>
<span class="new-term"><withinTextRule> </span>Rule about the Elements Within Text data category.
</p>
<ul>
<li>
<p>
<span class="new-term">withinText</span>
</p>
<p>States whether current context is regarded as
"within text".
</p>
<p>Legal values are:</p>
<ul>
<li>
<p>
<em>yes</em>
</p>
<p>
<em>no</em>
</p>
<p>
<em>nested</em>
</p>
</li>
</ul>
</li>
</ul>
<p></p>
<ul>
<li>
<p>
<span class="new-term">selector</span>
</p>
<p>XPath expression identifying the nodes to be selected.</p>
</li>
</ul>
<p></p>
</li>
<li>
<p>
<span class="new-term"><rubyRule> </span>Rule about the Ruby data category.
</p>
<ul>
<li>
<p>
<span class="new-term">rubyPointer</span>
</p>
<p>Relative XPath expression pointing to a node that corresponds to a <code>ruby</code> element
</p>
</li>
<li>
<p>
<span class="new-term">rtPointer</span>
</p>
<p>Relative XPath expression pointing to a node that
corresponds to a <code>rt</code> element
</p>
</li>
<li>
<p>
<span class="new-term">rpPointer</span>
</p>
<p>Relative XPath expression pointing to a node that
corresponds to a <code>rp</code> element
</p>
</li>
<li>
<p>
<span class="new-term">rbcPointer</span>
</p>
<p>Relative XPath expression pointing to a node that
corresponds to a <code>rbc</code> element
</p>
</li>
<li>
<p>
<span class="new-term">rtcPointer</span>
</p>
<p>Relative XPath expression pointing to a node that
corresponds to a <code>rtc</code> element
</p>
</li>
<li>
<p>
<span class="new-term">rbspanPointer</span>
</p>
<p>Relative XPath expression pointing to a node that corresponds to a rbspan attribute.</p>
</li>
</ul>
<p></p>
<ul>
<li>
<p>
<span class="new-term">selector</span>
</p>
<p>XPath expression identifying the nodes to be selected.</p>
</li>
</ul>
<p></p>
</li>
</ul>
<p>The following list summarizes elements that are available for local use:</p>
<ul>
<li>
<p>
<span class="new-term"><span> </span>Inline element to contain ITS information.
</p>
</li>
<li>
<p>
<span class="new-term"><rb> </span>Ruby base text.
</p>
</li>
<li>
<p>
<span class="new-term"><rbc> </span>Container for rb elements in the case of complex ruby markup.
</p>
</li>
<li>
<p>
<span class="new-term"><rp> </span>Used in the case of simple ruby markup to specify characters that can denote the beginning and end of ruby text when user
agents do not have other ways to present ruby text distinctively from the base text.
</p>
</li>
<li>
<p>
<span class="new-term"><rt> </span>Ruby text.
</p>
</li>
<li>
<p>
<span class="new-term"><rtc> </span>Container for rt elements in the case of complex ruby markup.
</p>
</li>
<li>
<p>
<span class="new-term"><ruby> </span>Ruby markup.
</p>
</li>
</ul>
<p>The following list summarizes attributes that are available for local use, with the local elements mentioned above, or with
other elements in a host schema:
</p>
<ul>
<li>
<p>
<span class="new-term">translate</span>
</p>
<p>The Translate data category information to be attached to
the current node.
</p>
</li>
</ul>
<p></p>
<ul>
<li>
<p>
<span class="new-term">locNote</span>
</p>
<p>Localization note.</p>
</li>
<li>
<p>
<span class="new-term">locNoteType</span>
</p>
<p>The type of localization note.</p>
</li>
<li>
<p>
<span class="new-term">locNoteRef</span>
</p>
<p>URI referring to the location of the localization note.</p>
</li>
</ul>
<p></p>
<ul>
<li>
<p>
<span class="new-term">termInfoRef</span>
</p>
<p>Pointer to a resource containing
information about the term.
</p>
</li>
<li>
<p>
<span class="new-term">term</span>
</p>
<p>Indicates a term locally.</p>
</li>
</ul>
<p></p>
<ul>
<li>
<p>
<span class="new-term">dir</span>
</p>
<p>The text direction for the context.</p>
</li>
</ul>
</div>
<div class="div1">
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="its-schemas" id="its-schemas" shape="rect"></a>D Schemas for ITS (Non-Normative)
</h2>
<p>
<em>This section is informative.</em>
</p>
<p>The following schemas define ITS elements and attributes and could be
used as building blocks when you want to integrate ITS markup into your
own XML vocabulary. You can see examples of such integration in <a href="http://www.w3.org/TR/2006/WD-xml-i18n-bp-20060518/" shape="rect">Best Practices for XML Internationalization</a>.
The schemas are not intended to be used alone for validation of
documents with ITS markup.
</p>
<p>The following schemas are provided:</p>
<ul>
<li>
<p>
<a href="its.dtd" shape="rect">DTD for ITS</a>
</p>
</li>
<li>
<p>
<a href="its.xsd" shape="rect">XML Schema document for ITS</a>
</p>
</li>
<li>
<p>
<a href="its.rnc" shape="rect">RELAX NG compact syntax document
for ITS</a>
</p>
</li>
<li>
<p>
<a href="its.rng" shape="rect">RELAX NG XML syntax document for
ITS</a>
</p>
</li>
</ul>
</div>
<div class="div1">
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="its-schematron-constraints" id="its-schematron-constraints" shape="rect"></a>E Checking ITS Markup Constraints With Schematron (Non-Normative)
</h2>
<p>
<em>This section is informative.</em>
</p>
<p>Several constraints of ITS markup cannot be validated with ITS schemas. The following <a title="Rule-based validation -- Schematron" href="#schematron" shape="rect">[Schematron]</a> document allows for validating some of these constraints.
</p>
<div class="exampleOuter"><a name="d3e5437" id="d3e5437">Example 40: Testing constraints in ITS markup</a><div class="exampleInner"><pre xml:space="preserve">
<sch:schema
xmlns:sch="http://www.ascc.net/xml/schematron" >
<!-- Schematron document to test constraints for global and local ITS markup.
For ITS markup definitions, see http://www.w3.org/TR/its/ . -->
<sch:ns prefix="its" uri="http://www.w3.org/2005/11/its"/>
<sch:pattern
name="Check ITS Global Rules and Local Constraints, and Version Constraints">
<sch:rule context="*">
<!-- Tests for locNoteRule -->
<sch:report
test="self::its:locNoteRule and child::its:locNote and @its:locNotePointer">
locNoteRule error: A locNoteRule element must not have both a locNote child element
and a locNotePointer attribute.</sch:report>
<sch:report
test="self::its:locNoteRule and @its:locNoteRef and @its:locNoteRefPointer">
locNoteRule error: A locNoteRule element must not have both a locNoteRef attribute
and a locNoteRefPointer attribute.</sch:report>
<sch:report
test="self::its:locNoteRule and child::its:locNote and @its:locNoteRef">
locNoteRule error: A locNoteRule element must not have both a locNote child element
and a locNoteRef attribute.</sch:report>
<!-- Test for termRule -->
<sch:report
test="self::its:termRule and @its:termInfoRef and @its:termInfoRefPointer">
termRule error: A termRule element must not have both a termInfoRef attribute and a
termInfoRefPointer attribute.</sch:report>
<sch:report
test="self::its:termRule and @its:termInfo and @its:termInfoPointer">
termRule error: A termRule element must not have both a termInfo attribute and a
termInfoPointer attribute.</sch:report>
<sch:report
test="self::its:termRule and @its:termInfoRef and @its:termInfoPointer">
termRule error: A termRule element must not have both a termInfoRef attribute and a
termInfoPointer attribute.</sch:report>
<!-- Test for rubyRule -->
<sch:report
test="self::its:rubyRule and child::its:rubyText and @its:rtPointer">
rubyRule error: A rubyRule element must not have both a rubyText child element and
a rtPointer attribute.</sch:report>
<!-- Test for locNote (local) -->
<sch:report test="@its:locNote and @its:locNoteRef">
Local ITS usage error: The locNote attribute and the locNoteRef attribute
must not be used together.</sch:report>
<!-- Test for term (local) -->
<sch:report
test="@its:termInfoRef and not(its:term) and not(self::its:termRule)">
Local ITS usage error: A termInfoRef attribute must not appear locally without
a term attribute.</sch:report>
<!-- Version attribute test -->
<sch:report test="/*/@its:version != @its:version">
The version attribute at the root element and at the rules element
must not specify different versions of ITS.</sch:report>
</sch:rule>
</sch:pattern>
</sch:schema></pre></div>
<p>[Source file: <a href="its-constraints-check-schematron.xml" shape="rect">its-constraints-check-schematron.xml</a>]
</p>
</div>
</div>
<div class="div1">
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="its-nvdl-schema" id="its-nvdl-schema" shape="rect"></a>F Checking ITS Markup with NVDL (Non-Normative)
</h2>
<p>
<em>This section is informative.</em>
</p>
<p>The following <a title="Namespace-based Validation Dispatching Language (NVDL)" href="#nvdl" shape="rect">[NVDL]</a> document allows validation of ITS
markup which has been added to a host vocabulary. Only ITS elements and attributes are checked.
Elements and attributes of host language are ignored during validation
against this NVDL document/schema.
</p>
<div class="exampleOuter"><a name="d3e5459" id="d3e5459">Example 41: NVDL schema for ITS</a><div class="exampleInner"><pre xml:space="preserve"><rules xmlns="http://purl.oclc.org/dsdl/nvdl/ns/structure/1.0">
<namespace ns="http://www.w3.org/2005/11/its">
<validate schema="its-elements.rng"/>
</namespace>
<namespace ns="http://www.w3.org/2005/11/its" match="attributes">
<validate schema="its-attributes.rng"/>
</namespace>
<anyNamespace>
<allow/>
</anyNamespace>
</rules></pre></div>
<p>
[Source file: <a href="its.nvdl" shape="rect">its.nvdl</a>]
</p>
</div>
<p>The NVDL schema depends on the following two schemas:</p>
<ul>
<li>
<p>
<a href="its-elements.rng" shape="rect">RELAX NG schema for ITS elements</a>
</p>
</li>
<li>
<p>
<a href="its-attributes.rng" shape="rect">RELAX NG schema for ITS
attributes</a>
</p>
</li>
</ul>
</div>
<div class="div1">
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="revisionlog" id="revisionlog" shape="rect"></a>G Revision Log (Non-Normative)
</h2>
<p id="changelog-since-20051122">The following log records
major changes that have been made to this document between the
<a href="http://www.w3.org/TR/2005/WD-its-20051122/" shape="rect">
publication in November 2005</a> and the <a href="http://www.w3.org/TR/2006/WD-its-20060222/" shape="rect">
publication in February 2006</a>.
</p>
<ol class="depth1">
<li>
<p>A section about <a href="#basic-concepts" shape="rect">basic
concepts</a> of ITS has been created.
</p>
</li>
<li>
<p>Terminology has been modified: the terms for position
of ITS information <a href="http://www.w3.org/TR/2005/WD-its-20051122/#design-decisions" shape="rect">in
situ versus dislocated</a> have been replaced by <a href="#selection-local" shape="rect">selection in an instance
document</a> versus <a href="#selection-global" shape="rect">global, rule-based
selection</a>.
</p>
</li>
<li>
<p>The definition of the <a href="#directionality" shape="rect">Directionality</a> data category has
been changed, to be compliant to various other
specifications. See the <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=2551" shape="rect">comment
on bidirectionality</a> for further information.
</p>
</li>
<li>
<p>Terminology within the text of this document and
within the markup declarations has been modified: <a href="http://www.w3.org/TR/2005/WD-its-20051122/#scope" shape="rect">scope
of ITS information</a> has been replaced with <a href="#its-processing" shape="rect">selection of ITS
information</a>.
</p>
</li>
<li>
<p>The <a href="http://www.w3.org/TR/2005/WD-its-20051122/#schemaRules" shape="rect">
schemaRules</a> element has been removed. For ITS
information as schema annotation, where is now only a<code>schemaRule</code> element.
</p>
</li>
<li>
<p>All ITS attributes are now defined as qualified
attributes. This leads to changes in the <a href="#its-schemas" shape="rect">generated ITS schemas</a>, for
example the generation of parameter entities for prefixes in
the XML DTD. This allows for easy changing of prefixes in
element or attribute names.
</p>
</li>
<li>
<p>The possibility of selector attributes in instance
documents (in the previous draft this was called <a href="http://www.w3.org/TR/2005/WD-its-20051122/#scope-instance" shape="rect">
scope in an instance document</a>) has been removed. <a href="#selection-local" shape="rect">Local selection in an instance
document</a> now relies only on <a href="#datacategories-defaults-etc" shape="rect">default selections of data
categories</a>. Due to this change, the definition of <a href="#selection-precedence" shape="rect">precedence between
selections</a> and <a href="#conformance" shape="rect">conformance
criteria</a> have been simplified, and the <a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=2719" shape="rect">
issue on namespace requirements and selector values</a>
could be resolved.
</p>
</li>
<li>
<p>Definitions of <a href="#datacategories-defaults-etc" shape="rect">default selections of data
categories</a> have been modified.
</p>
</li>
<li>
<p>An <code>ns</code> element has been added to the <a class="itsmarkup" href="#rules" shape="rect">rules</a> element to allow for specifying namespace
bindings.
</p>
</li>
<li>
<p>The implementation of the <a href="#ruby-annotation" shape="rect">Ruby</a>
data category has been modified, to reflect the removal of selector attributes in instance documents.
</p>
</li>
<li>
<p>A section on <a href="#associating-its-with-existing-markup" shape="rect">mapping of
ITS data categories to existing markup</a> has been
created.
</p>
</li>
<li>
<p>Examples of integrating ITS markup into a TEI schema
and into XML Spec have been created.
</p>
</li>
<li>
<p>A <a class="itsmarkup" href="#span" shape="rect">span</a> element has been created.
</p>
</li>
<li>
<p>The examples have been modified to reflect changes
mentioned above.
</p>
</li>
<li>
<p>For clarity, various sections have been reworded and
re-structured, and the visualization of ITS markup within
the text of this document has been modified.
</p>
</li>
<li>
<p>Tracking of issues is now handled via Bugzilla.</p>
</li>
<li>
<p>A revision log has been added.</p>
</li>
</ol>
<p id="changelog-since-20060222">The following log records
major changes that have been made to this document between the
<a href="http://www.w3.org/TR/2006/WD-its-20060222/" shape="rect">publication in February 2006</a> and the <a href="http://www.w3.org/TR/2006/WD-its-20060414/" shape="rect">publication in April 2006</a>.
</p>
<ol class="depth1">
<li>
<p>The <code>schemaRule</code> element, and the notion of
schema annotation which was connected to it, have been
abandoned.
</p>
</li>
<li>
<p>The section on conformance has been rewritten and
placed at the beginning of the document.
</p>
</li>
<li>
<p>In global rules, the <code>documentRule</code> element has
been replaced with elements which have data category
specific names. This eases the creation and validation of
global rules.
</p>
</li>
<li>
<p>In global rules, instead of rule specific attributes
for selection, there is now just one <a class="itsmarkup" href="#att.selector.attribute.selector" shape="rect">selector</a>
attribute.
</p>
</li>
<li>
<p>In global rules, the <code>documentRules</code> element
has been renamed to <a class="itsmarkup" href="#rules" shape="rect">rules</a>.
</p>
</li>
<li>
<p>In global rules, in addition to the existing
functionality of <a href="#def-adding-pointing" shape="rect">adding</a> ITS information
to selected nodes, a new functionality of <a href="#def-adding-pointing" shape="rect">pointing</a> to information
in an XML document has been created.
</p>
</li>
<li>
<p>An XLink <a class="itsmarkup" href="#rules.attributes" shape="rect">href</a> attribute has been added to
the <a class="itsmarkup" href="#rules" shape="rect">rules</a> element to allow for <a href="#link-external-rules" shape="rect">links to external
rules</a>. The <a href="#selection-precedence" shape="rect">precedence between
selections</a> has been modified to reflect this
change.
</p>
</li>
<li>
<p>Two new data categories <a href="#language-information" shape="rect">Language Information</a> and <a href="#elements-within-text" shape="rect">Elements Within Text</a>
have been defined.
</p>
</li>
<li>
<p>The data category <a href="#ruby-annotation" shape="rect">Ruby</a>
has been redefined, to be conforming to <a title="Ruby Annotation" href="#ruby-tr" shape="rect">[Ruby-TR]</a>.
</p>
</li>
<li>
<p>The declarations for ITS markup have been rewritten,
to adopt the changes mentioned above.
</p>
</li>
<li>
<p>The declarations for ITS markup (formally all
assembled in a single section) have been separated and
placed in the sections there they are described.
</p>
</li>
<li>
<p>A modularization of ITS and XHTML 1.0 has been
created.
</p>
</li>
<li>
<p>The informative <a class="section-ref" href="#introduction" shape="rect">Section 1: Introduction</a> and <a class="section-ref" href="#basic-concepts" shape="rect">Section 2: Basic Concepts</a> have been rewritten.
</p>
</li>
<li>
<p>Examples and the modularizations of ITS with existing
markup schemes have been changed to reflect the modifications
mentioned above.
</p>
</li>
</ol>
<p id="changelog-since-20060414">The following
log records major changes that have been made to this document
between the <a href="http://www.w3.org/TR/2006/WD-its-20060414/" shape="rect">publication
in April 2006</a> and the <a href="http://www.w3.org/TR/2006/WD-its-20060518/" shape="rect">publication in May 2006</a>.
</p>
<ol class="depth1">
<li>
<p>The <a href="#conformance" shape="rect">conformance
section</a> has been rewritten.
</p>
</li>
<li>
<p>The terminology of mapping ITS data categories with
existing markup has been changed to <a href="#associating-its-with-existing-markup" shape="rect">associating
ITS Data Categories with existing markup</a>.
</p>
</li>
<li>
<p>The global rule elements have been rewritten to
have attributes in the empty namespace.
</p>
</li>
<li>
<p>The examples have been validated, partially modified and extended.</p>
</li>
<li>
<p>Documentation strings have been added to elements
and attributes.
</p>
</li>
<li>
<p>The <a href="#elements-within-text" shape="rect">Elements Within Text</a> data category has been redefined.
</p>
</li>
<li>
<p>Clarifications about <a href="#selection-and-inclusion-mechanisms" shape="rect">ITS and inclusion mechanisms</a> and <a href="#note-object-selection" shape="rect">selections of pointers to external (possibly non-textual) objects</a> have been made.
</p>
</li>
<li>
<p>The <a href="#span.attributes" shape="rect">local attributes</a> have been reorganized into various data category specific groups.
</p>
</li>
<li>
<p>A <a href="#its-version-attribute" shape="rect">versioning mechanism</a> has been introduced
</p>
</li>
<li>
<p>A <a href="#its-markup-summary" shape="rect">summary of ITS markup</a> has been created.
</p>
</li>
<li>
<p>The automatically generated <a href="#its-schemas" shape="rect">ITS schemas</a> have been augmented with element and attribute documentations.
</p>
</li>
<li>
<p>A description of <a href="#its-schematron-constraints" shape="rect">ITS markup constraints</a> not covered by the ITS schemas has been created.
</p>
</li>
<li>
<p>The attributes <a href="http://www.w3.org/TR/2006/WD-its-20060414/#att.termRef.attribute.termRef" shape="rect">termRef</a> and <a href="http://www.w3.org/TR/2006/WD-its-20060414/#att.termRefPointer.attribute.termRefPointer" shape="rect">termRefPointer</a> have been renamed to <a class="itsmarkup" href="#att.local.no-ns.attribute.termInfoRef" shape="rect">termInfoRef</a> and <a class="itsmarkup" href="#termRule.attributes" shape="rect">termInfoRefPointer</a>.
</p>
</li>
<li>
<p>A list of requirements which are formulated in <a title="Internationalization and
 Localization Markup Requirements" href="#itsreq" shape="rect">[ITS REQ]</a>, but not covered in this document, has been created. See <a class="section-ref" href="#introduction" shape="rect">Section 1: Introduction</a>.
</p>
</li>
</ol>
<p id="changelog-since-20060518">The following log records major changes that have been made to this document between the <a href="http://www.w3.org/TR/2006/WD-its-20060518/" shape="rect">publication in May 2006</a> and the <a href="http://www.w3.org/TR/2006/CR-its-20061102/" shape="rect">
publication in November 2006</a>.
</p>
<ol class="depth1">
<li>
<p>In response to issue 3290 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3290" shape="rect">Introduction too "positive" and not enough informative</a>) <a class="section-ref" href="#introduction" shape="rect">Section 1: Introduction</a> has been modified.
</p>
</li>
<li>
<p>In response to issue 3293 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3293" shape="rect">Conformance/Compliance</a>) <a class="section-ref" href="#conformance" shape="rect">Section 4: Conformance</a> has been changed.
</p>
</li>
<li>
<p>In response to issue 3318 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3318" shape="rect">Clarify "within text" data category</a>) the <a href="#within-text-definition" shape="rect">definition of the Elements Within Text</a> data category has been clarified and illustrated with examples.
</p>
</li>
<li>
<p>In response to issue 3321 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3321" shape="rect">Relation of terminology data category to existing standards for terminology</a>) the relation has been described in <a class="section-ref" href="#terminology-definition" shape="rect">Section 6.4.1: Definition</a>.
</p>
</li>
<li>
<p>In response to issue 3323 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3323" shape="rect">Version of XPath: Write "XPath 1.0 or its successor"</a>) the reference to <a title="XML Path Language (XPath) Version 1.0" href="#xpath" shape="rect">[XPath 1.0]</a> has been replaced by a reference to "<a title="XML Path Language (XPath) Version 1.0" href="#xpath" shape="rect">[XPath 1.0]</a> or its successor".
</p>
</li>
<li>
<p>In response to issue 3330 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3330" shape="rect">lro and rlo explanation</a>) explanations have been modified in <a class="section-ref" href="#directionality-definition" shape="rect">Section 6.5.1: Definition</a>.
</p>
</li>
<li>
<p>In response to issue 3456 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3456" shape="rect">Attribute used for locInfo</a>) a note has been added at the end of <a class="section-ref" href="#locNote-implementation" shape="rect">Section 6.3.2: Implementation</a>.
</p>
</li>
<li>
<p>In response to issue 3457 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3457" shape="rect">RFC 3066bis</a>) the references to "RFC 3066bis" been replaced by a reference to "RFC4646 or its successor".
</p>
</li>
<li>
<p>In response to issue 3458 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3458" shape="rect">Default translate value</a>) default values have been made explicit in <a class="section-ref" href="#translatability-implementation" shape="rect">Section 6.2.2: Implementation</a>.
</p>
</li>
<li>
<p>In response to issue 3459 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3459" shape="rect">Use of elements</a>) ITS markup is now explicitly allowed inside other ITS markup.
</p>
</li>
<li>
<p>In response to issue 3460 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3460" shape="rect">Loc Info or Loc Note</a>) all attributes and elements starting with <code>locInfo...</code> have been renamed <code>locNote...</code>.
</p>
</li>
<li>
<p>In response to issue 3461 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3461" shape="rect">Role of termInfo</a>) <a class="section-ref" href="#terminology-definition" shape="rect">Section 6.4.1: Definition</a> has been clarified.
</p>
</li>
<li>
<p>In response to issue 3462 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3462" shape="rect">Pointing to terms</a>) <a class="section-ref" href="#terminology-implementation" shape="rect">Section 6.4.2: Implementation</a> has been clarified.
</p>
</li>
<li>
<p>In response to issue 3463 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3463" shape="rect">termInfoRef should allow for id strings</a>) the <a class="itsmarkup" href="#termRule.attributes" shape="rect">termInfoPointer</a> attribute has been added.
</p>
</li>
<li>
<p>In response to issue 3464 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3464" shape="rect">Allowing for XPath expressions to point to term definitions</a>) the <a class="itsmarkup" href="#termRule.attributes" shape="rect">termInfoPointer</a> attribute has been added.
</p>
</li>
<li>
<p>In response to issue 3465 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3465" shape="rect">Default is ltr</a>) <a class="section-ref" href="#directionality-implementation" shape="rect">Section 6.5.2: Implementation</a> has been clarified.
</p>
</li>
<li>
<p>In response to issue 3466 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3466" shape="rect">Existing ruby markup</a>) <a class="section-ref" href="#iri-usage" shape="rect">Section 3.5: Usage of Internationalized Resource Identifiers in ITS</a> has been added, the <a href="http://www.w3.org/TR/2006/WD-its-20060518/#its-conformance-2-2" shape="rect">conformance clause 2-2</a> has been removed, the reference to <a title="Ruby Annotation" href="#ruby-tr" shape="rect">[Ruby-TR]</a> has been clarified and moved to <a class="section-ref" href="#ruby-implementation" shape="rect">Section 6.6.2: Implementation</a>, and the definition of the <a href="#directionality" shape="rect">Directionality</a> data category has been clarified in <a class="section-ref" href="#directionality-definition" shape="rect">Section 6.5.1: Definition</a>.
</p>
</li>
<li>
<p>In response to issue 3467 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3467" shape="rect">rubyText is an attribute</a>) the <code>rubyText</code> attribute has been changed to the <a class="itsmarkup" href="#rubyText" shape="rect">rubyText</a> element.
</p>
</li>
<li>
<p>In response to issue 3468 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3468" shape="rect">xml:lang missing</a>) a note at the end of <a class="section-ref" href="#langinfo-definition" shape="rect">Section 6.7.1: Definition</a> has been added.
</p>
</li>
<li>
<p>In response to issue 3469 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3469" shape="rect">Example 19 xml:lang</a>) the role of <code>xml:lang</code> for the <a href="#language-information" shape="rect">language information</a> data category has been clarified in <a class="section-ref" href="#langinfo-definition" shape="rect">Section 6.7.1: Definition</a>.
</p>
</li>
<li>
<p>In response to issue 3473 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3473" shape="rect">Language information data category overview</a>) the role of the <a class="itsmarkup" href="#langRule" shape="rect">langRule</a> element has been clarified in <a class="section-ref" href="#langinfo-definition" shape="rect">Section 6.7.1: Definition</a>.
</p>
</li>
<li>
<p>In response to issue 3479 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3479" shape="rect">Example 33</a>) <a href="#EX-lang-definition-1" shape="rect">Example 38</a> (which was Example 33) has been modified.
</p>
</li>
<li>
<p>In response to issue 3480 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3480" shape="rect">Language information data category overview</a>) the role of <code>xml:lang</code> for the <a href="#language-information" shape="rect">language information</a> data category has been clarified in <a class="section-ref" href="#langinfo-definition" shape="rect">Section 6.7.1: Definition</a>.
</p>
</li>
<li>
<p>In response to issue 3481 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3481" shape="rect">Translatability</a>) the data category "Translatability" has been renamed to <a href="#trans-datacat" shape="rect">Translate</a>.
</p>
</li>
<li>
<p>In response to issue 3482 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3482" shape="rect">Inheritance of translation information</a>) the role of inheritance of translation information within global rules has been made more explicit in <a class="section-ref" href="#translatability-implementation" shape="rect">Section 6.2.2: Implementation</a>.
</p>
</li>
<li>
<p>In response to issue 3487 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3487" shape="rect">Invert translate examples</a>) <a href="#EX-translate-selector-2" shape="rect">Example 23</a> has been modified.
</p>
</li>
<li>
<p>In response to issue 3488 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3488" shape="rect">6.3 ed 1</a>) <a class="section-ref" href="#locNote-definition" shape="rect">Section 6.3.1: Definition</a> has been modified.
</p>
</li>
<li>
<p>In response to issue 3489 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3489" shape="rect">Mention translation tools</a>) a reference to translation tools has been added in <a class="section-ref" href="#locNote-definition" shape="rect">Section 6.3.1: Definition</a>.
</p>
</li>
<li>
<p>In response to issue 3490 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3490" shape="rect">Examples 22 and 23</a>) <a href="#EX-locNote-element-1" shape="rect">Example 24</a> (which was Example 22) and <a href="#EX-locNotePointer-attribute-1" shape="rect">Example 25</a> (which was example 23) have been modified.
</p>
</li>
<li>
<p>In response to issue 3491 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3491" shape="rect">Explanations for examples</a>) the examples in <a class="section-ref" href="#locNote-implementation" shape="rect">Section 6.3.2: Implementation</a> have been clarified.
</p>
</li>
<li>
<p>In response to issue 3492 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3492" shape="rect">Examples 24</a>) <a href="#EX-locNoteRef-attribute-1" shape="rect">Example 26</a> (which was Example 24) has been modified.
</p>
</li>
<li>
<p>In response to issue 3493 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3493" shape="rect">Marks terms and meanings</a>) the purpose of the <a href="#terminology" shape="rect">terminology</a> data category has been clarified in <a class="section-ref" href="#terminology-definition" shape="rect">Section 6.4.1: Definition</a>.
</p>
</li>
<li>
<p>In response to issue 3494 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3494" shape="rect">termInfoRefPointer referent's data</a>) the explanation of the termInfoRefPointer attribute has been clarified in <a class="section-ref" href="#terminology-implementation" shape="rect">Section 6.4.2: Implementation</a>.
</p>
</li>
<li>
<p>In response to issue 3495 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3495" shape="rect">Hard to know what this is about</a>) <a class="section-ref" href="#elements-within-text" shape="rect">Section 6.8: Elements Within Text</a> has been clarified.
</p>
</li>
<li>
<p>In response to issue 3496 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3496" shape="rect">Standardized wording</a>) all subsections in <a class="section-ref" href="#datacategory-description" shape="rect">Section 6: Description of Data Categories</a> have been reworded to be consistent.
</p>
</li>
<li>
<p>In response to issue 3497 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3497" shape="rect">No implementation section</a>) an implementation section (<a class="section-ref" href="#langinfo-implementation" shape="rect">Section 6.7.2: Implementation</a>) has been added for the <a href="#language-information" shape="rect">language information</a> data category.
</p>
</li>
<li>
<p>In response to issue 3498 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3498" shape="rect">Repetition</a>) <a class="section-ref" href="#directionality-definition" shape="rect">Section 6.5.1: Definition</a> has been modified.
</p>
</li>
<li>
<p>In response to issue 3499 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3499" shape="rect">Is dir mandatory?</a>) it has been made explicit that the <a class="itsmarkup" href="#att.local.no-ns.attribute.dir" shape="rect">dir</a> attribute is mandatory at the <a class="itsmarkup" href="#dirRule" shape="rect">dirRule</a> element (see <a class="section-ref" href="#directionality-implementation" shape="rect">Section 6.5.2: Implementation</a>).
</p>
</li>
<li>
<p>In response to issue 3500 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3500" shape="rect">Avoid xml:lang='he'</a>) <a class="section-ref" href="#selection-local" shape="rect">Section 5.2.2: Local Selection in an XML Document</a> (especially <a href="#EX-selection-local-1" shape="rect">Example 15</a>) has been modified.
</p>
</li>
<li>
<p>In response to issue 3501 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3501" shape="rect">Some Hebrew quotation</a>) <a class="section-ref" href="#directionality-implementation" shape="rect">Section 6.5.2: Implementation</a> has been modified.
</p>
</li>
<li>
<p>In response to issue 3502 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3502" shape="rect">Example 30</a>) <a href="#EX-dir-selector-1.xml" shape="rect">Example 33</a> (which was Example 30) has been modified.
</p>
</li>
<li>
<p>In response to issue 3503 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3503" shape="rect">Refer to bidi article</a>) a reference to <a title="What you need to know about the bidi algorithm and inline markup" href="#bidiarticle" shape="rect">[Bidi Article]</a> in <a class="section-ref" href="#directionality-definition" shape="rect">Section 6.5.1: Definition</a> has been added.
</p>
</li>
<li>
<p>In response to issue 3504 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3504" shape="rect">Example 31 lacks rp</a>) <a href="#EX-ruby-implementation-1" shape="rect">Example 37</a> (which was Example 31) has been modified.
</p>
</li>
<li>
<p>In response to issue 3505 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3505" shape="rect">Use Japanese in Example 31</a>) <a href="#EX-ruby-implementation-1" shape="rect">Example 37</a> (which was Example 31) has been modified.
</p>
</li>
<li>
<p>In response to issue 3506 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3506" shape="rect">Make the application of legacy ruby clearer</a>) <a class="section-ref" href="#ruby-implementation" shape="rect">Section 6.6.2: Implementation</a> has been modified.
</p>
</li>
<li>
<p>In response to issue 3507 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3507" shape="rect">In the case of no selection</a>) <a class="section-ref" href="#ruby-implementation" shape="rect">Section 6.6.2: Implementation</a> has been modified.
</p>
</li>
<li>
<p>In response to issue 3508 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3508" shape="rect">Example 32 head</a>) <a href="#EX-ruby-legacy-1" shape="rect">Example 36</a> (which was Example 32) has been modified.
</p>
</li>
<li>
<p>In response to issue 3509 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3509" shape="rect">Too many places to look</a>) the section <a href="http://www.w3.org/TR/2006/WD-its-20060518/#its-markup-summary" shape="rect">5.1 Summary of ITS Markup</a> has been changed to <a class="section-ref" href="#its-markup-summary" shape="rect">Appendix C: Summary of ITS Markup</a>, and <a class="section-ref" href="#datacategory-description" shape="rect">Section 6: Description of Data Categories</a> has been reworded.
</p>
</li>
<li>
<p>In response to issue 3510 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3510" shape="rect">Spell out the attributes</a>) <a class="section-ref" href="#selection-global" shape="rect">Section 5.2.1: Global, Rule-based Selection</a> has been modified to list relevant attributes.
</p>
</li>
<li>
<p>In response to issue 3511 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3511" shape="rect">Example 14 translate</a>) <a href="#EX-selection-local-1" shape="rect">Example 15</a> (which was Example 14) has been modified.
</p>
</li>
<li>
<p>In response to issue 3512 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3512" shape="rect">Example 14 dir</a>) <a href="#EX-selection-local-1" shape="rect">Example 15</a> (which was Example 14) has been modified.
</p>
</li>
<li>
<p>In response to issue 3513 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3513" shape="rect">ITS markup must be integrated</a>) the optionality of ITS markup in the targeted XML file(s) has been made explicit in <a class="section-ref" href="#associating-its-with-existing-markup" shape="rect">Section 5.5: Associating ITS Data Categories with Existing Markup</a>.
</p>
</li>
<li>
<p>In response to issue 3514 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3514" shape="rect">Attributes missing?</a>) the attributes that are available for local use have been spelled out in <a class="section-ref" href="#its-markup-summary" shape="rect">Appendix C: Summary of ITS Markup</a>.
</p>
</li>
<li>
<p>In response to issue 3515 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3515" shape="rect">xml:lang = language info, please</a>) the role of <code>xml:lang</code> has been clarified in <a class="section-ref" href="#langinfo-definition" shape="rect">Section 6.7.1: Definition</a>.
</p>
</li>
<li>
<p>In response to issue 3516 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3516" shape="rect">Editorial comments on ITS</a>) <a class="section-ref" href="#introduction" shape="rect">Section 1: Introduction</a>, <a class="section-ref" href="#basic-concepts" shape="rect">Section 2: Basic Concepts</a>, <a class="section-ref" href="#notation-terminology" shape="rect">Section 3: Notation and Terminology</a>, and <a class="section-ref" href="#datacategory-description" shape="rect">Section 6: Description of Data Categories</a> have been modified.
</p>
</li>
<li>
<p>In response to issue 3612 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3612" shape="rect">Missing term="yes|no" in termRule element</a>) the value "no" has been reinstated for the <a class="itsmarkup" href="#att.local.no-ns.attribute.term" shape="rect">term</a> attribute.
</p>
</li>
<li>
<p>In response to issue 3640 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3640" shape="rect">Need to handle inheritance for terminology</a>) the description of the inheritance / default / overriding behavior of the data categories has been clarified in <a class="section-ref" href="#datacategories-defaults-etc" shape="rect">Section 6.1: Position, Defaults, Inheritance and Overriding of Data Categories</a>.
</p>
</li>
<li>
<p>In response to issue 3803 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3803" shape="rect">Both selector and the rbPointer attributes are base text in rubyRule</a>) the <code>rbPointer</code> has been removed.
</p>
</li>
</ol>
<p id="changelog-since-20061102">The following log records
major changes that have been made to this document between the
<a href="http://www.w3.org/TR/2006/CR-its-20061102/" shape="rect">
publication in November 2006</a> and January 2007.
</p>
<ol class="depth1">
<li>
<p>
In response to issue 3319 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=3319" shape="rect">Namespace binding mechanism</a>
) removed the <a href="http://www.w3.org/TR/2006/CR-its-20061102/#ns" shape="rect">ns</a>
element.
</p>
</li>
<li>
<p>
In response to issue 4096 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4096" shape="rect">Inheritance and overriding needs to be made clearer</a>) changed wording.
</p>
</li>
<li>
<p>
In response to issue 4098 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4098" shape="rect">Need to make more explicit: what is possible with XSLT patterns realizing ITS selectors?</a>) added a note about the subset of XPath in XSLT to <a class="section-ref" href="#basic-concepts-selection-global" shape="rect">Section 2.1.2: Global Approach</a>.
</p>
</li>
<li>
<p>
In response to issue 4099 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4099" shape="rect">Format for implementation output needs to be clear</a>) added note on the <a href="http://www.w3.org/International/its/tests/" shape="rect">Internationalization Tag Set (ITS) Version 1.0 testsuite</a> processing to <a class="section-ref" href="#conformance-product-processing-expectations" shape="rect">Section 4.2: Conformance Type 2: The Processing Expectations for ITS Markup</a>.
</p>
</li>
<li>
<p>
In response to issue 4152 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4152" shape="rect">Need to make explicit that ITS attributes at its:span are not namespace qualified</a>) created two groups of ITS attributes, <a href="#att.local.with-ns.attributes" shape="rect">namespace qualified</a> and <a href="#att.local.no-ns.attributes" shape="rect">not namespace qualified</a>, the latter used at ITS <a class="itsmarkup" href="#span" shape="rect">span</a>, the former for use at elements not from the ITS namespace.
</p>
</li>
<li>
<p>
In response to issue 4289 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4289" shape="rect">Various mainly editorial changes</a>) made the editorial changes described in the issue.
</p>
</li>
<li>
<p>
In response to issue 4290 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4290" shape="rect">Create appendix about NVDL</a>) introduced <a class="section-ref" href="#its-nvdl-schema" shape="rect">Appendix F: Checking ITS Markup with NVDL</a>.
</p>
</li>
<li>
<p>
In response to issue 4291 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4291" shape="rect">Have version attribute at its:rules element in no namespace</a>) put the ITS <a href="#its-version-attribute" shape="rect">version</a> attribute at the <a class="itsmarkup" href="#rules" shape="rect">rules</a> element in no namespace.
</p>
</li>
<li>
<p>
In response to issue 4293 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4293" shape="rect">Editorial fix in sec. 6.6.2</a>) removed bullet point.
</p>
</li>
<li>
<p>
In response to issue 4294 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4294" shape="rect">Add xlink:type to its:rules element</a>) added the XLink <a class="itsmarkup" href="#rules.attributes" shape="rect">type</a> attribute to the <a class="itsmarkup" href="#rules" shape="rect">rules</a> element.
</p>
</li>
<li>
<p>In response to issue 4295 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4295" shape="rect">Change of XPath expressions in Schematron example</a>) updated <a class="section-ref" href="#its-schematron-constraints" shape="rect">Appendix E: Checking ITS Markup Constraints With Schematron</a>.
</p>
</li>
<li>
<p>
In response to issue 4322 (<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=4322" shape="rect">Editors to go to the draft and check that there are no "CSS style elements" or the like</a>) removed wording related to CSS style elements.
</p>
</li>
</ol>
<p id="changelog-since-20070226">The following log records
major changes that have been made to this document between the
<a href="http://www.w3.org/TR/2007/PR-its-20070226/" shape="rect">
publication in February 2007</a> and March 2007.
</p>
<ol class="depth1">
<li>
<p>In response to <a href="http://lists.w3.org/Archives/Member/member-i18n-its/2007JanMar/0138.html" shape="rect">comments received during the AC review</a> made the following changes: replaced the examples 3 (<a href="EX-ways-to-use-its-1.xml" shape="rect">EX-ways-to-use-its-1.xml</a>), 4 (<a href="EX-ways-to-use-its-2.xml" shape="rect">EX-ways-to-use-its-2.xml</a>), 5 (<a href="EX-ways-to-use-its-3.xml" shape="rect">EX-ways-to-use-its-3.xml</a>), 6 (<a href="EX-ways-to-use-its-4.xml" shape="rect">EX-ways-to-use-its-4.xml</a>) and 7 (<a href="EX-ways-to-use-its-5.xsd" shape="rect">EX-ways-to-use-its-5.xsd</a>) with other examples; updated the bibliography.
</p>
</li>
<li>
<p>Fixed various (spelling etc.) errors in examples.</p>
</li>
<li>
<p>General spell check.</p>
</li>
<li>
<p>Updated reference for language identification in <a class="section-ref" href="#language-information" shape="rect">Section 6.7: Language Information</a>.
</p>
</li>
</ol>
</div>
<div class="div1">
<h2><a href="#contents" shape="rect"><img src="images/topOfPage.gif" align="right" height="26" width="26" title="Go to the table of contents." alt="Go to the table of contents." /></a><a name="acknowledgements" id="acknowledgements" shape="rect"></a>H Acknowledgements (Non-Normative)
</h2>
<p>This document has been developed with contributions by the
ITS Working Group: Damien Donlon (Sun Microsystems, Inc.), Martin Dürst (W3C Invited Expert), Poonam Gupta (Centre for Development
of Advanced Computing (CDAC)), Richard Ishida (W3C/ERCIM), Jirka Kosek (W3C Invited Expert), Christian Lieske (SAP AG), Sebastian
Rahtz (W3C Invited Expert), Francois Richard (HP), Goutam Saha (Centre for Development of Advanced Computing (CDAC)), Felix
Sasaki (W3C/Keio), Yves Savourel (ENLASO Corporation), Diane Stoick (The Boeing Company), Najib Tounsi (Ecole Mohammadia d'Ingenieurs
Rabat (EMI)), Andrzej Zydron (W3C Invited Expert).
</p>
<p>A special thanks goes to Sebastian Rahtz who introduced us
to the ODD language, which was used to create this document,
and who provided the stylesheets to generate schemas and the
XHTML version out of an ODD document. The generation of XHTML
from ODD takes an intermediate step through the
xmlspec-i18n.dtd.
</p>
</div>
</div>
</body>
</html>