index.html
882 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
5772
5773
5774
5775
5776
5777
5778
5779
5780
5781
5782
5783
5784
5785
5786
5787
5788
5789
5790
5791
5792
5793
5794
5795
5796
5797
5798
5799
5800
5801
5802
5803
5804
5805
5806
5807
5808
5809
5810
5811
5812
5813
5814
5815
5816
5817
5818
5819
5820
5821
5822
5823
5824
5825
5826
5827
5828
5829
5830
5831
5832
5833
5834
5835
5836
5837
5838
5839
5840
5841
5842
5843
5844
5845
5846
5847
5848
5849
5850
5851
5852
5853
5854
5855
5856
5857
5858
5859
5860
5861
5862
5863
5864
5865
5866
5867
5868
5869
5870
5871
5872
5873
5874
5875
5876
5877
5878
5879
5880
5881
5882
5883
5884
5885
5886
5887
5888
5889
5890
5891
5892
5893
5894
5895
5896
5897
5898
5899
5900
5901
5902
5903
5904
5905
5906
5907
5908
5909
5910
5911
5912
5913
5914
5915
5916
5917
5918
5919
5920
5921
5922
5923
5924
5925
5926
5927
5928
5929
5930
5931
5932
5933
5934
5935
5936
5937
5938
5939
5940
5941
5942
5943
5944
5945
5946
5947
5948
5949
5950
5951
5952
5953
5954
5955
5956
5957
5958
5959
5960
5961
5962
5963
5964
5965
5966
5967
5968
5969
5970
5971
5972
5973
5974
5975
5976
5977
5978
5979
5980
5981
5982
5983
5984
5985
5986
5987
5988
5989
5990
5991
5992
5993
5994
5995
5996
5997
5998
5999
6000
6001
6002
6003
6004
6005
6006
6007
6008
6009
6010
6011
6012
6013
6014
6015
6016
6017
6018
6019
6020
6021
6022
6023
6024
6025
6026
6027
6028
6029
6030
6031
6032
6033
6034
6035
6036
6037
6038
6039
6040
6041
6042
6043
6044
6045
6046
6047
6048
6049
6050
6051
6052
6053
6054
6055
6056
6057
6058
6059
6060
6061
6062
6063
6064
6065
6066
6067
6068
6069
6070
6071
6072
6073
6074
6075
6076
6077
6078
6079
6080
6081
6082
6083
6084
6085
6086
6087
6088
6089
6090
6091
6092
6093
6094
6095
6096
6097
6098
6099
6100
6101
6102
6103
6104
6105
6106
6107
6108
6109
6110
6111
6112
6113
6114
6115
6116
6117
6118
6119
6120
6121
6122
6123
6124
6125
6126
6127
6128
6129
6130
6131
6132
6133
6134
6135
6136
6137
6138
6139
6140
6141
6142
6143
6144
6145
6146
6147
6148
6149
6150
6151
6152
6153
6154
6155
6156
6157
6158
6159
6160
6161
6162
6163
6164
6165
6166
6167
6168
6169
6170
6171
6172
6173
6174
6175
6176
6177
6178
6179
6180
6181
6182
6183
6184
6185
6186
6187
6188
6189
6190
6191
6192
6193
6194
6195
6196
6197
6198
6199
6200
6201
6202
6203
6204
6205
6206
6207
6208
6209
6210
6211
6212
6213
6214
6215
6216
6217
6218
6219
6220
6221
6222
6223
6224
6225
6226
6227
6228
6229
6230
6231
6232
6233
6234
6235
6236
6237
6238
6239
6240
6241
6242
6243
6244
6245
6246
6247
6248
6249
6250
6251
6252
6253
6254
6255
6256
6257
6258
6259
6260
6261
6262
6263
6264
6265
6266
6267
6268
6269
6270
6271
6272
6273
6274
6275
6276
6277
6278
6279
6280
6281
6282
6283
6284
6285
6286
6287
6288
6289
6290
6291
6292
6293
6294
6295
6296
6297
6298
6299
6300
6301
6302
6303
6304
6305
6306
6307
6308
6309
6310
6311
6312
6313
6314
6315
6316
6317
6318
6319
6320
6321
6322
6323
6324
6325
6326
6327
6328
6329
6330
6331
6332
6333
6334
6335
6336
6337
6338
6339
6340
6341
6342
6343
6344
6345
6346
6347
6348
6349
6350
6351
6352
6353
6354
6355
6356
6357
6358
6359
6360
6361
6362
6363
6364
6365
6366
6367
6368
6369
6370
6371
6372
6373
6374
6375
6376
6377
6378
6379
6380
6381
6382
6383
6384
6385
6386
6387
6388
6389
6390
6391
6392
6393
6394
6395
6396
6397
6398
6399
6400
6401
6402
6403
6404
6405
6406
6407
6408
6409
6410
6411
6412
6413
6414
6415
6416
6417
6418
6419
6420
6421
6422
6423
6424
6425
6426
6427
6428
6429
6430
6431
6432
6433
6434
6435
6436
6437
6438
6439
6440
6441
6442
6443
6444
6445
6446
6447
6448
6449
6450
6451
6452
6453
6454
6455
6456
6457
6458
6459
6460
6461
6462
6463
6464
6465
6466
6467
6468
6469
6470
6471
6472
6473
6474
6475
6476
6477
6478
6479
6480
6481
6482
6483
6484
6485
6486
6487
6488
6489
6490
6491
6492
6493
6494
6495
6496
6497
6498
6499
6500
6501
6502
6503
6504
6505
6506
6507
6508
6509
6510
6511
6512
6513
6514
6515
6516
6517
6518
6519
6520
6521
6522
6523
6524
6525
6526
6527
6528
6529
6530
6531
6532
6533
6534
6535
6536
6537
6538
6539
6540
6541
6542
6543
6544
6545
6546
6547
6548
6549
6550
6551
6552
6553
6554
6555
6556
6557
6558
6559
6560
6561
6562
6563
6564
6565
6566
6567
6568
6569
6570
6571
6572
6573
6574
6575
6576
6577
6578
6579
6580
6581
6582
6583
6584
6585
6586
6587
6588
6589
6590
6591
6592
6593
6594
6595
6596
6597
6598
6599
6600
6601
6602
6603
6604
6605
6606
6607
6608
6609
6610
6611
6612
6613
6614
6615
6616
6617
6618
6619
6620
6621
6622
6623
6624
6625
6626
6627
6628
6629
6630
6631
6632
6633
6634
6635
6636
6637
6638
6639
6640
6641
<?xml version="1.0" encoding="us-ascii"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="EN" xmlns="http://www.w3.org/1999/xhtml"><head><meta content="text/html; charset=utf-8" http-equiv="Content-Type"/><title>XML Schema Part 1: Structures Second Edition</title><style type="text/css">
table {text-indent: 0;}
code { font-family: monospace; }
div.constraint,
div.issue,
div.note,
div.notice { margin-left: 2em; }
ol.enumar { list-style-type: decimal; }
ol.enumla { list-style-type: lower-alpha; }
ol.enumlr { list-style-type: lower-roman; }
ol.enumua { list-style-type: upper-alpha; }
ol.enumur { list-style-type: upper-roman; }
div.exampleInner pre { margin-left: 1em;
margin-top: 0em; margin-bottom: 0em}
div.exampleOuter {border: 4px double gray;
margin: 0em; padding: 0em}
div.exampleInner { background-color: #d5dee3;
border-top-width: 4px;
border-top-style: double;
border-top-color: #d3d3d3;
border-bottom-width: 4px;
border-bottom-style: double;
border-bottom-color: #d3d3d3;
padding: 4px; margin: 0em }
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
margin: 4px}
img { color: white; border: none }
span.nav { float: right}
span.arrow { font-style: normal; font-weight: bold }
code { font-family: monospace; font-size: 100%}
span.propdef { font-weight: bold; font-family: monospace }
span.termdef {color: #850021}
a.termref:visited, a.termref:link {font-family: sans-serif;
font-style: normal;
color: black;
text-decoration: none }
a.eltref:visited, a.eltref:link { font-family: sans-serif;
color: black;
text-decoration: none }
a.propref:visited, a.xpropref:visited, a.propref:link, a.xpropref:link { color: black; text-decoration: none;
font-family: sans-serif }
dl.props, dl.psvi {margin-bottom: .5em; margin-top: 0em}
div.toc1 {margin-left: 5ex}
div.toc2 {margin-left: 2ex}
div.tocLine{margin: 0em; text-indent: -6ex}
h3.withToc {margin-bottom: 0em}
div.constraintnote { margin-top: 1em }
div.constraint {
margin-left: 1em; }
div.constraintlist {
margin-left: 1em; margin-bottom: 0em
}
div.clnumber {
text-indent: -1em;
margin-top: 0em; margin-bottom: 0em }
div.schemaComp { border: 4px double gray;
margin: 0em 1em; padding: 0em }
div.compHeader { margin: 4px;
font-weight: bold }
span.schemaComp { color: #A52A2A }
div.compBody {
border-top-width: 4px;
border-top-style: double;
border-top-color: #d3d3d3;
padding: 4px ; margin: 0em}
div.psviDef { border: 4px double gray;
margin: 1em 1em; padding: 0em }
div.psviHeader { margin: 4px;
font-weight: bold }
span.psviDef { color: #A52A2A }
div.psviBody { border-top-width: 4px;
border-top-style: double;
border-top-color: #d3d3d3;
padding: 4px ; margin: 0em}
div.reprdef { border: 4px double gray;
margin: 0em 1em; padding: 0em }
div.reprHeader { margin: 4px;
font-weight: bold }
span.reprdef { color: #A52A2A }
div.reprBody, div.reprcomp, div.reprdep {
border-top-width: 4px;
border-top-style: double;
border-top-color: #d3d3d3;
padding: 4px ; margin: 0em}
table.reprcomp { margin-bottom: -.5em}
p.element-syntax-1 { font-family: monospace;
margin-top: 0em; margin-bottom: .5em }
p.element-syntax { font-family: monospace;
border-top-width: 1px;
border-top-style: solid;
border-top-color: #d3d3d3;
padding: 4px ; margin: 0em}
div.exampleInner pre { margin-left: 1em;
margin-top: 0em; margin-bottom: 0em}
div.exampleOuter {border: 4px double gray;
margin: 0em; padding: 0em}
div.exampleInner { background-color: #d5dee3;
border-top-width: 4px;
border-top-style: double;
border-top-color: #d3d3d3;
border-bottom-width: 4px;
border-bottom-style: double;
border-bottom-color: #d3d3d3;
padding: 4px; margin: 0em }
div.exampleWrapper { margin: 4px }
div.exampleHeader { font-weight: bold;
margin: 4px}
span.edtext { color: red }
table.restricts { margin-top: 1em; margin-bottom: 1em; margin-left: -2em}
table.restricts th { margin-left: 0em }
table.ubc td, table.ubc th { font-size: smaller }
table.dtdemo th { text-align: center;
background-color: #d5dee3}
table.dtdemo pre { margin-left: 0em; margin-bottom: 0em}
table.dtdemo td {background-color: #bedce6}
table.scrap {background-color: #f5dcb3}
img { color: white; border: none }
span.nav { float: right}
span.arrow { font-style: normal; font-weight: bold }
</style><link href="http://www.w3.org/StyleSheets/TR/W3C-REC.css" type="text/css" rel="stylesheet"/></head><body><div class="head"><p><a href="http://www.w3.org/"><img width="72" height="48" alt="W3C" src="http://www.w3.org/Icons/w3c_home"/></a></p>
<h1><a id="title" name="title"/>XML Schema Part 1: Structures Second Edition</h1>
<h2><a id="w3c-doctype" name="w3c-doctype"/>W3C Recommendation 28 October 2004</h2>
<!--*
<h2><a id="w3c-doctype" name="w3c-doctype"/>W3C Recommendation 2 May 2001, Second Edition 28 October 2004</h2>
*-->
<dl><dt>This version:</dt><dd> <a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/</a> </dd><dt>Latest version:</dt><dd><a href="http://www.w3.org/TR/xmlschema-1/">http://www.w3.org/TR/xmlschema-1/</a>
</dd><dt>Previous version:</dt><dd>
<a href="http://www.w3.org/TR/2004/PER-xmlschema-1-20040318/">http://www.w3.org/TR/2004/PER-xmlschema-1-20040318/</a>
</dd><dt>Editors:</dt><dd>Henry S. Thompson, University of Edinburgh <a href="mailto:ht@cogsci.ed.ac.uk"><ht@cogsci.ed.ac.uk></a></dd><dd>David Beech, Oracle Corporation <a href="mailto:David.Beech@oracle.com"><David.Beech@oracle.com></a></dd><dd>Murray Maloney, for Commerce One <a href="mailto:murray@muzmo.com"><murray@muzmo.com></a></dd><dd>Noah Mendelsohn, Lotus Development Corporation <a href="mailto:Noah_Mendelsohn@lotus.com"><Noah_Mendelsohn@lotus.com></a></dd></dl>
<p>Please refer to the <a href="http://www.w3.org/2004/03/xmlschema-errata"
><strong>errata</strong></a>
for this document, which may include some normative corrections.</p>
<p>This document is also available in these non-normative formats: <a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/structures.xml">XML</a>, <a href="http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/structures-with-errata.html">XHTML with visible change markup</a>, <a href="http://www.w3.org/2001/XMLSchema.xsd">Independent copy of the schema for schema
documents</a>, and <a href="http://www.w3.org/2001/XMLSchema.dtd">Independent copy of the DTD for schema documents</a>.
See also <a
href="http://www.w3.org/2003/03/Translations/byTechnology?technology=xmlschema"
><strong>translations</strong></a>.</p>
<p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2004 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology">MIT</acronym></a>, <a href="http://www.ercim.org/"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a>
<!--*
and <a href="http://www.w3.org/Consortium/Legal/copyright-software">software licensing</a>
*-->
rules apply.</p></div><hr/><div>
<h2><a id="abstract" name="abstract"/>Abstract</h2><p><em>XML Schema: Structures</em> specifies the XML Schema definition language,
which offers facilities for describing the structure and constraining the contents
of XML 1.0 documents, including those which exploit the XML
Namespace facility. The schema language, which is itself represented in XML
1.0 and uses namespaces, substantially reconstructs and considerably extends the capabilities found in XML 1.0 document type
definitions (DTDs). This specification depends on <em>XML Schema Part 2:
Datatypes</em>.</p></div><div>
<h2><a id="status" name="status"/>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/">W3C technical reports index</a> at
http://www.w3.org/TR/.</em></p><p>This is a <a href="http://www.w3.org/2004/02/Process-20040205/tr.html#RecsW3C">W3C
Recommendation</a>, which forms part of the Second Edition of XML
Schema. This document has been reviewed by W3C Members and
other interested parties and has been endorsed by the Director as a
W3C Recommendation. It is a stable document and may be used as
reference material or cited as a normative reference
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>
This document has been produced by the <a href="http://www.w3.org/XML/Schema">W3C XML Schema Working Group</a>
as part of the W3C <a href="http://www.w3.org/XML/Activity">XML
Activity</a>. The goals of the XML Schema language are discussed in
the <a href="http://www.w3.org/TR/NOTE-xml-schema-req">XML Schema
Requirements</a> document. The authors of this document are the
members of the XML Schema Working Group. Different parts of this
specification have different editors.
</p><p>
This document was produced under the <a href="http://www.w3.org/TR/2002/NOTE-patent-practice-20020124">24
January 2002 Current Patent Practice (CPP)</a> as amended by the <a href="http://www.w3.org/2004/02/05-pp-transition">W3C Patent Policy
Transition Procedure</a>. The Working Group maintains a <a href="http://www.w3.org/2002/11/xml-schema-IPR-statements.html">public
list of patent disclosures</a> relevant to this document;
that page also includes instructions for disclosing a patent.
An individual who
has actual knowledge of a patent which the individual believes
contains Essential Claim(s) with respect to this specification should
disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section
6 of the W3C Patent Policy</a>.
</p><p>The English version of this specification is the only normative
version. Information about translations of this document is available
at <a href="http://www.w3.org/2001/05/xmlschema-translations">http://www.w3.org/2001/05/xmlschema-translations</a>.</p><p>This second edition is <em>not</em> a new version,
it merely incorporates the changes dictated by the corrections to
errors found in the <a href="http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/">first
edition</a> as agreed by the XML Schema Working Group, as a
convenience to readers. A separate list of all such corrections is
available at <a href="http://www.w3.org/2001/05/xmlschema-errata">http://www.w3.org/2001/05/xmlschema-errata</a>.
</p><p>The errata list for this second edition is available at <a href="http://www.w3.org/2004/03/xmlschema-errata">http://www.w3.org/2004/03/xmlschema-errata</a>.</p><p>
Please report errors in this document to <a href="mailto:www-xml-schema-comments@w3.org">www-xml-schema-comments@w3.org</a>
(<a href="http://lists.w3.org/Archives/Public/www-xml-schema-comments/">archive</a>).
</p><div class="note"><b>Note: </b>David Beech has retired since the publication of the first edition,
and can be reached at <a href="mailto:davidbeech@earthlink.net">davidbeech@earthlink.net</a>.<p/>Murray Maloney is no longer affiliated with Commerce One; his contact
details are unchanged.<p/>Noah Mendelsohn's affiliation has changed since the publication of the
first edition. He is now at IBM, and can be contacted at <a href="mailto:noah_mendelsohn@us.ibm.com">noah_mendelsohn@us.ibm.com</a></div></div><div class="toc">
<h2><a id="contents" name="contents"/>Table of Contents</h2><p class="toc">1 <a href="#intro">Introduction</a><br/>
    1.1 <a href="#intro-purpose">Purpose</a><br/>
    1.2 <a href="#intro-relatedWork">Dependencies on Other Specifications</a><br/>
    1.3 <a href="#intro-terminology">Documentation Conventions and Terminology</a><br/>
2 <a href="#concepts">Conceptual Framework</a><br/>
    2.1 <a href="#d0e504">Overview of XML Schema</a><br/>
    2.2 <a href="#concepts-data-model">XML Schema Abstract Data Model</a><br/>
    2.3 <a href="#concepts-schemaConstraints">Constraints and Validation Rules</a><br/>
    2.4 <a href="#concepts-conformance">Conformance</a><br/>
    2.5 <a href="#concepts-nameSymbolSpaces">Names and Symbol Spaces</a><br/>
    2.6 <a href="#Instance_Document_Constructions">Schema-Related Markup in
Documents Being Validated</a><br/>
    2.7 <a href="#web-representation">Representation of Schemas on the World Wide Web</a><br/>
3 <a href="#components">Schema Component Details</a><br/>
    3.1 <a href="#scIntro">Introduction</a><br/>
    3.2 <a href="#cAttribute_Declarations">Attribute Declarations</a><br/>
    3.3 <a href="#cElement_Declarations">Element Declarations</a><br/>
    3.4 <a href="#Complex_Type_Definitions">Complex Type Definitions</a><br/>
    3.5 <a href="#cAttributeUse">AttributeUses</a><br/>
    3.6 <a href="#cAttribute_Group_Definitions">Attribute Group Definitions</a><br/>
    3.7 <a href="#cModel_Group_Definitions">Model Group Definitions</a><br/>
    3.8 <a href="#Model_Groups">Model Groups</a><br/>
    3.9 <a href="#cParticles">Particles</a><br/>
    3.10 <a href="#Wildcards">Wildcards</a><br/>
    3.11 <a href="#cIdentity-constraint_Definitions">Identity-constraint Definitions</a><br/>
    3.12 <a href="#cNotation_Declarations">Notation Declarations</a><br/>
    3.13 <a href="#cAnnotations">Annotations</a><br/>
    3.14 <a href="#Simple_Type_Definitions">Simple Type Definitions</a><br/>
    3.15 <a href="#Schemas">Schemas as a Whole</a><br/>
4 <a href="#composition">Schemas and Namespaces: Access and Composition</a><br/>
    4.1 <a href="#layer1">Layer 1: Summary of the Schema-validity Assessment Core</a><br/>
    4.2 <a href="#layer2">Layer 2: Schema Documents, Namespaces and Composition</a><br/>
    4.3 <a href="#composition-instances">Layer 3: Schema Document Access and Web-interoperability</a><br/>
5 <a href="#conformance">Schemas and Schema-validity Assessment</a><br/>
    5.1 <a href="#conformance-schemaValidity">Errors in Schema Construction and Structure</a><br/>
    5.2 <a href="#validation_outcome">Assessing Schema-Validity</a><br/>
    5.3 <a href="#conformance-missing">Missing Sub-components</a><br/>
    5.4 <a href="#conformance-processorResponsibilities">Responsibilities of Schema-aware Processors</a><br/>
</p>
<h3><a id="appendices" name="appendices"/>Appendices</h3><p class="toc">A <a href="#normative-schemaSchema">Schema for Schemas (normative)</a><br/>
B <a href="#normative-references">References (normative)</a><br/>
C <a href="#outcomes">Outcome Tabulations (normative)</a><br/>
    C.1 <a href="#validation_failures">Validation Rules</a><br/>
    C.2 <a href="#PSVI_contributions">Contributions to the post-schema-validation infoset</a><br/>
    C.3 <a href="#outcome-src">Schema Representation Constraints</a><br/>
    C.4 <a href="#outcome-cos">Schema Component Constraints</a><br/>
D <a href="#infoset">Required Information Set Items and Properties (normative)</a><br/>
E <a href="#component-diagram">Schema Components Diagram (non-normative)</a><br/>
F <a href="#normative-glossary">Glossary (non-normative)</a><br/>
G <a href="#nonnormative-schemaDTD">DTD for Schemas (non-normative)</a><br/>
H <a href="#non-ambig">Analysis of the Unique Particle Attribution Constraint (non-normative)</a><br/>
I <a href="#nonnormative-references">References (non-normative)</a><br/>
J <a href="#acknowledgments">Acknowledgements (non-normative)</a><br/>
</p></div><hr/><div class="body"><div class="div1">
<h2><a id="intro" name="intro"/>1 Introduction</h2><p>This document sets out the structural part (<em>XML Schema: Structures</em>) of the XML Schema definition language.</p><p>Chapter 2 presents a <a href="#concepts">Conceptual Framework (§2)</a> for XML Schemas, including
an introduction to the nature of XML Schemas and an introduction
to the XML Schema abstract data model, along with
other terminology used throughout this document. </p><p>Chapter 3, <a href="#components">Schema Component Details (§3)</a>, specifies the precise
semantics of each component of the abstract model, the representation of each
component in XML, with reference to a DTD and XML Schema
for an XML Schema document type, along with a detailed mapping between the elements and
attribute vocabulary of this representation and the components and properties
of the abstract model.</p><p>Chapter 4 presents <a href="#composition">Schemas and Namespaces: Access and Composition (§4)</a>, including the
connection between documents and schemas, the import, inclusion and redefinition of declarations and definitions and
the foundations of schema-validity assessment.</p><p>Chapter 5 discusses <a href="#conformance">Schemas and Schema-validity Assessment (§5)</a>, including the
overall approach to schema-validity assessment of documents, and responsibilities of schema-aware
processors. </p><p>The normative appendices include a <a href="#normative-schemaSchema">Schema for Schemas (normative) (§A)</a> for the XML representation of schemas and
<a href="#normative-references">References (normative) (§B)</a>.</p><p>The non-normative appendices include the <a href="#nonnormative-schemaDTD">DTD for Schemas (non-normative) (§G)</a> and a <a href="#normative-glossary">Glossary (non-normative) (§F)</a>.</p><p>This document is primarily intended as a language definition reference.
As such, although it contains a few examples, it is <em>not</em> primarily designed
to serve as a motivating introduction to the design and its features, or as a
tutorial for new users.
Rather it presents a careful and fully explicit definition of that design, suitable
for guiding implementations. For those in search of a step-by-step
introduction to the design, the non-normative <a href="#bib-expo">[XML Schema: Primer]</a> is a much better
starting point than this document.</p><div class="div2">
<h3><span class="nav"> <a class="nav" href="#intro-relatedWork"><img src="next.jpg" alt="next sub-section"/></a></span><a id="intro-purpose" name="intro-purpose"/>1.1 Purpose</h3><p>The purpose of <em>XML Schema: Structures</em> is to define the nature of XML schemas
and their component parts,
provide an inventory of XML markup
constructs with which to represent schemas, and define the
application of schemas to XML documents. </p><p>The purpose of an <em>XML Schema: Structures</em> schema is to define and describe a class of
XML documents by using schema components to constrain and document the meaning,
usage and relationships of their constituent parts: datatypes, elements and
their content and attributes and their values. Schemas may also provide for the specification of additional
document information, such as normalization and defaulting of attribute
and element values. Schemas have
facilities for self-documentation. Thus, <em>XML Schema: Structures</em> can be used to define, describe and catalogue XML
vocabularies for classes of XML documents. </p><p>Any application that consumes well-formed XML can use the <em>XML Schema: Structures</em>
formalism to express syntactic, structural and value constraints applicable to
its document instances. The <em>XML Schema: Structures</em> formalism allows a useful level of
constraint checking to be described and implemented for a wide spectrum of XML
applications. However, the language defined by this specification does not attempt to provide
<em>all</em> the facilities that might be needed by <em>any</em>
application. Some applications may require constraint capabilities not
expressible in this language, and so may need to perform their own additional
validations.</p></div><div class="div2">
<h3><span class="nav"><a class="nav" href="#intro-purpose"><img src="previous.jpg" alt="previous sub-section"/></a> <a class="nav" href="#intro-terminology"><img src="next.jpg" alt="next sub-section"/></a></span><a id="intro-relatedWork" name="intro-relatedWork"/>1.2 Dependencies on Other Specifications</h3><p>The definition of <em>XML Schema: Structures</em> depends on the following specifications:
<a href="#ref-xmlinfo">[XML-Infoset]</a>,
<a href="#ref-xml-namespaces">[XML-Namespaces]</a>,
<a href="#bib-xpath">[XPath]</a>, and
<a href="#ref-xsp2">[XML Schemas: Datatypes]</a>.</p><p>See <a href="#infoset">Required Information Set Items and Properties (normative) (§D)</a> for a tabulation of the information items
and properties specified in <a href="#ref-xmlinfo">[XML-Infoset]</a> which this
specification requires as a precondition to schema-aware processing.</p></div><div class="div2">
<h3><span class="nav"><a class="nav" href="#intro-relatedWork"><img src="previous.jpg" alt="previous sub-section"/></a> </span><a id="intro-terminology" name="intro-terminology"/>1.3 Documentation Conventions and Terminology</h3><p>The section introduces the highlighting and typography as used in
this document to present technical material.</p><p>Special terms are defined at their point of
introduction in the text. For example <span class="termdef"><a id="key-sampledef" name="key-sampledef">[Definition:]  </a>a <b>term</b> is
something used with a special meaning</span>. The definition is
labeled as such and the term it defines is displayed in boldface. The end of the definition is not specially marked
in the displayed or printed text. Uses of defined terms are links to
their definitions, set off with middle dots, for instance <a class="termref" href="#key-sampledef"><span class="arrow">·</span>term<span class="arrow">·</span></a>.</p><p>Non-normative examples are set off in boxes and accompanied by a brief
explanation:</p><div class="exampleOuter"><div class="exampleHeader">Example</div><div class="exampleInner"><pre><schema targetNamespace="http://www.example.com/XMLSchema/1.0/mySchema"></pre></div><div class="exampleWrapper">And an explanation of the example.</div></div><p>The definition of each kind of schema component consists of a list of
its properties and their contents, followed by descriptions of the
semantics of the properties:</p><div class="schemaComp"><div class="compHeader"><span class="schemaComp">Schema Component</span>: <a href="#intro-terminology">Example</a></div><div class="compBody">
<dl class="props">
<dt><a name="xmpl-prop" id="xmpl-prop"><span class="propdef">{example property}</span></a></dt><dd>
Definition of the property.
</dd>
</dl>
</div></div><p>References to properties of schema components are links to
the relevant definition as exemplified above, set off with curly braces, for instance <a class="propref" href="#xmpl-prop">{example property}</a>.</p><p>The correspondence between an element information item which is part
of the XML representation of a schema and one or more schema components is presented in a tableau
which illustrates the element information item(s) involved.
This is followed by a tabulation of the correspondence between properties of the component
and properties of the information item. Where context may determine which of
several different components may arise, several tabulations, one per context,
are given. The property correspondences are normative,
as are the illustrations of the XML representation element information items.
</p><p>In the XML representation, bold-face
attribute names (e.g. <b>count</b> below) indicate a required
attribute information item, and the rest are
optional. Where an attribute information item has an enumerated type
definition, the values are shown separated by vertical bars, as for
<code>size</code> below; if there is a default value, it is shown
following a colon. Where an attribute information item has a built-in simple
type definition defined in <a href="#ref-xsp2">[XML Schemas: Datatypes]</a>, a hyperlink to its
definition therein is given.</p><p>The allowed content of the information item is
shown as a grammar fragment, using the Kleene operators <code>?</code>,
<code>*</code> and <code>+</code>. Each element name therein is a hyperlink to
its own illustration.</p><div class="note"><b>Note: </b>The illustrations are derived automatically from the <a href="#normative-schemaSchema">Schema for Schemas (normative) (§A)</a>. In the case of apparent conflict, the <a href="#normative-schemaSchema">Schema for Schemas (normative) (§A)</a> takes precedence, as it, together with the <a class="termref" href="#gloss-src"><span class="arrow">·</span>Schema Representation Constraints<span class="arrow">·</span></a>, provide the normative statement of
the form of XML representations.</div><div class="reprdef"><div class="reprHeader"><span class="reprdef">XML Representation Summary</span>: <code>example</code> Element Information Item</div><div class="reprBody">
<p class="element-syntax-1"><a name="element-example" id="element-example"><example</a><br/>  <b>count</b> = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#integer">integer</a><br/>  size = (<var>large</var> | <var>medium</var> | <var>small</var>) : medium><br/><em>  Content: </em>(<a class="eltref" href="#element-all">all</a> | <a class="eltref" href="#element-any">any</a>*)<br/></example></p>
<div class="reprcomp"><table class="reprcomp"><thead><tr><th><a href="#intro-terminology">Example</a><strong> Schema Component</strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Representation</th></tr></thead><tbody valign="top"><tr valign="top"><td><a class="propref" href="#xmpl-prop">{example property}</a></td><td>Description of what the property corresponds to, e.g. the value of the <code>size</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>
</td></tr></tbody></table></td></tr></tbody></table></div>
</div></div><p>References to elements in the text are links to
the relevant illustration as exemplified above, set off with angle brackets, for instance <a class="eltref" href="#element-example"><example></a>.</p><p>References to properties of information items as defined in <a href="#ref-xmlinfo">[XML-Infoset]</a> are notated as links to the relevant section thereof, set off with square brackets, for example <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>.</p><p>Properties which this specification defines for information items are
introduced as follows:</p><div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> example information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="ex-foo" id="ex-foo"><span class="propdef">[new property]</span></a></dt><dd>The value the property gets.</dd>
</dl></div></div><p>References to properties of information items defined in this specification
are notated as links to their introduction as exemplified above, set off with square brackets, for example <a class="propref" href="#ex-foo">[new property]</a>.</p><p>The following highlighting is used for non-normative commentary in
this document:</p><div class="note"><b>Note: </b>General comments directed to all readers. </div><p>Following <a href="#ref-xml">[XML 1.0 (Second Edition)]</a>, within normative prose in this specification, the words
<em>may</em> and <em>must</em> are defined as follows:</p><dl><dt class="label">may</dt><dd>Conforming documents and XML Schema-aware processors are permitted to but need not behave as described.</dd><dt class="label">must</dt><dd>Conforming documents and XML Schema-aware processors are required to behave as described; otherwise they are in error.</dd></dl><p>Note however that this specification provides a definition of error and of conformant processors'
responsibilities with respect to errors (see <a href="#conformance">Schemas and Schema-validity Assessment (§5)</a>) which is considerably
more complex than that of <a href="#ref-xml">[XML 1.0 (Second Edition)]</a>.</p></div></div><div class="div1">
<h2><a id="concepts" name="concepts"/>2 Conceptual Framework</h2><p>This chapter gives an overview of <em>XML Schema: Structures</em> at the level of its abstract data model. <a href="#components">Schema Component Details (§3)</a> provides details on this model, including
a normative representation in XML for the components of the model.
Readers interested primarily in learning to write schema documents may wish to
first read <a href="#bib-expo">[XML Schema: Primer]</a> for a tutorial introduction, and only then consult the sub-sections of
<a href="#components">Schema Component Details (§3)</a> named <em>XML Representation of ...</em> for
the details.</p><div class="div2">
<h3><span class="nav"> <a class="nav" href="#concepts-data-model"><img src="next.jpg" alt="next sub-section"/></a></span><a id="d0e504" name="d0e504"/>2.1 Overview of XML Schema</h3><p>An XML Schema
consists of components such as type definitions
and element declarations. These can be used to assess the validity of
well-formed element and attribute information items (as defined
in <a href="#ref-xmlinfo">[XML-Infoset]</a>), and furthermore
may specify augmentations to those items and their descendants. This augmentation makes explicit information which may have
been implicit in the original document, such as normalized and/or default values for
attributes and elements and
the types of element and attribute information items. <span class="termdef"><a id="key-psvi" name="key-psvi">[Definition:]  </a>We refer to the augmented infoset which results from conformant processing as defined in this specification as the <b>post-schema-validation infoset</b>, or PSVI</span>.</p><p>Schema-validity assessment has two aspects:
</p><div class="constraintlist"><div class="clnumber">1<a name="c-lsv" id="c-lsv"> </a>Determining local schema-validity, that is
whether an element or attribute information item satisfies the
constraints embodied in the relevant
components of an XML Schema;</div><div class="clnumber">2 Synthesizing an overall validation outcome for the item,
combining local schema-validity with the results of schema-validity
assessments of its descendants, if any, and
adding appropriate augmentations to the infoset to record this outcome.</div></div><p>Throughout this specification, <span class="termdef"><a id="key-vn" name="key-vn">[Definition:]  </a>the
word <b>valid</b> and its derivatives are used to refer to
clause <a href="#c-lsv">1</a> above, the determination of local
schema-validity</span>.</p><p>Throughout this specification, <span class="termdef"><a id="key-va" name="key-va">[Definition:]  </a> the word <b>assessment</b> is used to refer
to the overall process of
local validation, schema-validity assessment and infoset augmentation</span>.</p></div><div class="div2">
<h3 class="withToc"><span class="nav"><a class="nav" href="#"><img src="previous.jpg" alt="previous sub-section"/></a> <a class="nav" href="#concepts-schemaConstraints"><img src="next.jpg" alt="next sub-section"/></a></span><a id="concepts-data-model" name="concepts-data-model"/>2.2 XML Schema Abstract Data Model</h3><div class="localToc">        2.2.1 <a href="#Type_Definition_Summary">Type Definition Components</a><br/>
        2.2.2 <a href="#Declarations_Summary">Declaration Components</a><br/>
        2.2.3 <a href="#Model_Group_Summary">Model Group Components</a><br/>
        2.2.4 <a href="#Identity-constraint_Definition">Identity-constraint Definition Components</a><br/>
        2.2.5 <a href="#Group_Definitions">Group Definition Components</a><br/>
        2.2.6 <a href="#Annotation">Annotation Components</a><br/>
</div><p>This specification builds on <a href="#ref-xml">[XML 1.0 (Second Edition)]</a> and
<a href="#ref-xml-namespaces">[XML-Namespaces]</a>. The concepts and definitions used
herein regarding XML are framed at the abstract level of <a href="http://www.w3.org/TR/xml-infoset/#infoitem">information
items</a> as defined in <a href="#ref-xmlinfo">[XML-Infoset]</a>. By
definition, this use of the infoset provides <em>a priori</em> guarantees of <a href="http://www.w3.org/TR/REC-xml#sec-well-formed">well-formedness</a>
(as defined in <a href="#ref-xml">[XML 1.0 (Second Edition)]</a>) and <a href="http://www.w3.org/TR/REC-xml-names/#Conformance">namespace
conformance</a> (as defined in <a href="#ref-xml-namespaces">[XML-Namespaces]</a>) for
all candidates for <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> and for all <a class="termref" href="#key-schemaDoc"><span class="arrow">·</span>schema documents<span class="arrow">·</span></a>.</p><p>Just as <a href="#ref-xml">[XML 1.0 (Second Edition)]</a> and
<a href="#ref-xml-namespaces">[XML-Namespaces]</a> can be described in terms of
information items, XML Schemas can be described in terms of an
abstract data model. In defining XML Schemas in terms of an abstract
data model, this specification rigorously specifies the information which
must be available to a conforming XML Schema processor. The abstract
model for schemas is conceptual only, and does not mandate any
particular implementation or representation of this information. To
facilitate interoperation and sharing of schema information, a
normative XML interchange format for schemas is provided.</p><p><span class="termdef"><a id="key-component" name="key-component">[Definition:]  </a> <b>Schema component</b> is the generic term for the building blocks that comprise the abstract data model of the schema.
</span>
<span class="termdef"><a id="key-schema" name="key-schema">[Definition:]  </a>
An <b>XML Schema</b> is a
set of <a class="termref" href="#key-component"><span class="arrow">·</span>schema components<span class="arrow">·</span></a></span>. There are 13 kinds of
component in all, falling into three groups. The primary components, which may
(type definitions) or must (element and attribute declarations) have names
are as follows:</p><ul><li>Simple type definitions
</li><li>Complex type definitions</li><li>Attribute declarations</li><li>Element declarations</li></ul><p>The secondary components, which must have names, are as follows:</p><ul><li>Attribute group definitions</li><li>Identity-constraint definitions</li><li>Model group definitions</li><li>Notation declarations</li></ul><p>Finally, the "helper" components provide small parts of
other components; they are not independent of their context:</p><ul><li>Annotations</li><li>Model groups</li><li>Particles</li><li>Wildcards</li><li>Attribute Uses</li></ul><p>During <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a>, <span class="termdef"><a id="key-declaration" name="key-declaration">[Definition:]  </a><b>declaration</b> components are associated by
(qualified) name to information items being <a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a></span>.</p><p>On the other hand, <span class="termdef"><a id="key-definition" name="key-definition">[Definition:]  </a><b>definition</b> components define
internal schema components that can be used in other schema components</span>.
</p><p>
<span class="termdef"><a id="key-compName" name="key-compName">[Definition:]  </a>Declarations and
definitions may have and be identified by <b>name</b>s, which are NCNames as defined by <a href="#ref-xml-namespaces">[XML-Namespaces]</a></span>.</p><p> <span class="termdef"><a id="key-targetNS" name="key-targetNS">[Definition:]  </a>Several kinds
of component have a <b>target namespace</b>, which is either
<a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> or a namespace name, also as
defined by <a href="#ref-xml-namespaces">[XML-Namespaces]</a></span>. The <a class="termref" href="#key-targetNS"><span class="arrow">·</span>target
namespace<span class="arrow">·</span></a> serves to identify the namespace within which the
association between the component and its name exists. In the case of
declarations, this in turn determines the namespace name of, for example, the element
information items it may <a class="termref" href="#key-vn"><span class="arrow">·</span>validate<span class="arrow">·</span></a>.</p><div class="note"><b>Note: </b>At the abstract level, there is
no requirement that the components of a schema share a
<a class="termref" href="#key-targetNS"><span class="arrow">·</span>target namespace<span class="arrow">·</span></a>. Any schema for use in
<a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> of documents containing names from more than one namespace
will of necessity include components with different <a class="termref" href="#key-targetNS"><span class="arrow">·</span>target namespaces<span class="arrow">·</span></a>. This contrasts with
the situation at the level of the XML representation of components, in which each schema document contributes
definitions and declarations to a single target namespace.</div><p><a class="termref" href="#key-vn"><span class="arrow">·</span>Validation<span class="arrow">·</span></a>, defined in detail in <a href="#components">Schema Component Details (§3)</a>, is a
relation between information items and schema components. For example, an
attribute information item may <a class="termref" href="#key-vn"><span class="arrow">·</span>validate<span class="arrow">·</span></a> with respect to an attribute
declaration, a list of element information items may <a class="termref" href="#key-vn"><span class="arrow">·</span>validate<span class="arrow">·</span></a> with
respect to a content model, and so on. The following sections briefly
introduce the kinds of components in the
schema abstract data model, other major features of the abstract
model, and how they contribute to <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a>.</p><div class="div3">
<h4><a id="Type_Definition_Summary" name="Type_Definition_Summary"/>2.2.1 Type Definition Components</h4><p>The abstract model provides two kinds of type definition component: simple
and complex.</p><p><span class="termdef"><a id="key-typeDefn" name="key-typeDefn">[Definition:]  </a>This specification uses
the phrase <b>type definition</b> in cases where no distinction
need be made between simple and complex types</span>.</p><p>Type definitions form a hierarchy with a single root. The subsections below first describe characteristics of that
hierarchy, then provide an introduction to simple and complex type definitions themselves.</p><div class="div4">
<h5><a id="Type_Derivation" name="Type_Derivation"/>2.2.1.1 Type Definition Hierarchy</h5><p>
<span class="termdef"><a id="key-typeDefinitionHierarchy" name="key-typeDefinitionHierarchy">[Definition:]  </a>Except for a distinguished <a class="termref" href="#key-urType"><span class="arrow">·</span>ur-type definition<span class="arrow">·</span></a>, every <a class="termref" href="#key-typeDefn"><span class="arrow">·</span>type definition<span class="arrow">·</span></a> is, by construction, either a
<a class="termref" href="#key-typeRestriction"><span class="arrow">·</span>restriction<span class="arrow">·</span></a> or an <a class="termref" href="#key-typeExtension"><span class="arrow">·</span>extension<span class="arrow">·</span></a> of some other type definition. The graph of these relationships forms a tree known as the <b>Type Definition Hierarchy</b></span>.
</p><p><span class="termdef"><a id="key-typeRestriction" name="key-typeRestriction">[Definition:]  </a>A type
definition whose
declarations or facets are in a one-to-one relation with those of another
specified type
definition, with each in turn restricting the possibilities of the one it
corresponds to, is said to be a <b>restriction</b></span>.
The specific restrictions might include narrowed ranges or reduced
alternatives.
Members of a type, A, whose definition is a <a class="termref" href="#key-typeRestriction"><span class="arrow">·</span>restriction<span class="arrow">·</span></a> of the definition of another type, B, are always members of type B as well.</p><p><span class="termdef"><a id="key-typeExtension" name="key-typeExtension">[Definition:]  </a>A complex type definition
which allows element or attribute content in addition to that allowed by
another specified type
definition is said to be an <b>extension</b></span>.</p><p><span class="termdef"><a id="key-urType" name="key-urType">[Definition:]  </a>A distinguished complex
type definition, the <b>ur-type
definition</b>, whose
name is <i>anyType</i> in the XML Schema namespace, is present in each <a class="termref" href="#key-schema"><span class="arrow">·</span>XML Schema<span class="arrow">·</span></a>, serving as the root of the type
definition hierarchy for that schema</span>.
</p><p><span class="termdef"><a id="key-baseTypeDefinition" name="key-baseTypeDefinition">[Definition:]  </a>A type definition used as the
basis for an <a class="termref" href="#key-typeExtension"><span class="arrow">·</span>extension<span class="arrow">·</span></a> or
<a class="termref" href="#key-typeRestriction"><span class="arrow">·</span>restriction<span class="arrow">·</span></a> is known as
the <b>base type definition</b> of that definition</span>.
</p></div><div class="div4">
<h5><a id="Simple_Type_Definition" name="Simple_Type_Definition"/>2.2.1.2 Simple Type Definition</h5><p>A simple type definition is a set of constraints on strings and information about the values they encode, applicable to the <a class="termref" href="#key-nv"><span class="arrow">·</span>normalized value<span class="arrow">·</span></a> of an attribute
information item or of an element information item with no element children.
Informally, it applies to the values of attributes and the text-only content of elements.
</p><p>Each simple type definition, whether built-in (that is, defined in <a href="#ref-xsp2">[XML Schemas: Datatypes]</a>) or
user-defined, is a <a class="termref" href="#key-typeRestriction"><span class="arrow">·</span>restriction<span class="arrow">·</span></a> of some particular
simple <a class="termref" href="#key-baseTypeDefinition"><span class="arrow">·</span>base type
definition<span class="arrow">·</span></a>. For the built-in primitive type definitions, this is <span class="termdef"><a id="key-simpleUrType" name="key-simpleUrType">[Definition:]  </a>the <b>simple
ur-type definition</b>, a special restriction of the
<a class="termref" href="#key-urType"><span class="arrow">·</span>ur-type
definition<span class="arrow">·</span></a>, whose name is <b>anySimpleType</b> in the XML Schema namespace</span>. The <a class="termref" href="#key-simpleUrType"><span class="arrow">·</span>simple ur-type definition<span class="arrow">·</span></a> is considered to have an unconstrained lexical space, and a value space consisting of the union of the value spaces of all the built-in primitive datatypes and the set of all lists of all members of the value spaces of all the built-in primitive datatypes.</p><p>The mapping from lexical space to value space is
unspecified for items whose type definition is the
<a class="termref" href="#key-simpleUrType"><span class="arrow">·</span>simple ur-type definition<span class="arrow">·</span></a>.
Accordingly this specification does not constrain processors' behaviour in
areas where this mapping is implicated, for example checking such items against
enumerations, constructing default attributes or elements whose declared type
definition is the
<a class="termref" href="#key-simpleUrType"><span class="arrow">·</span>simple ur-type definition<span class="arrow">·</span></a>, checking
identity constraints involving such items.</p><div class="note"><b>Note: </b>The Working Group expects to return to this area in a future
version of this specification.</div><p>Simple types may
also be defined whose members are lists of items
themselves constrained by some other simple type definition, or whose
membership is the union of the memberships of some other simple type
definitions. Such list and union simple type definitions are also restrictions of the <a class="termref" href="#key-simpleUrType"><span class="arrow">·</span>simple ur-type
definition<span class="arrow">·</span></a>.</p><p>For detailed information on simple type definitions, see <a href="#Simple_Type_Definitions">Simple Type Definitions (§3.14)</a> and <a href="#ref-xsp2">[XML Schemas: Datatypes]</a>. The latter also defines an extensive inventory of
pre-defined simple types.</p></div><div class="div4">
<h5><a id="Complex_Type_Definition" name="Complex_Type_Definition"/>2.2.1.3 Complex Type Definition</h5><p>A complex type definition is a set of attribute declarations and a content type, applicable to the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> and
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> of an element information item respectively. The content type may
require the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> to contain neither element nor character information
items (that is, to be empty), to be a string which belongs to a particular simple
type or to contain a sequence of element information items which conforms to a particular model group, with or without character information items as well.</p><p>Each complex type definition other than the
<a class="termref" href="#key-urType"><span class="arrow">·</span>ur-type definition<span class="arrow">·</span></a> is either
</p><ul><li>a restriction of a complex <a class="termref" href="#key-baseTypeDefinition"><span class="arrow">·</span>base
type definition<span class="arrow">·</span></a></li></ul><p>
or
</p><ul><li>an <a class="termref" href="#key-typeExtension"><span class="arrow">·</span>extension<span class="arrow">·</span></a> of a simple or complex <a class="termref" href="#key-baseTypeDefinition"><span class="arrow">·</span>base
type definition<span class="arrow">·</span></a>.</li></ul><p>
</p><p>
</p><p> A
complex type which extends another does so by having additional content model
particles at the end of the other definition's content model,
or by having additional attribute declarations, or both.
</p><div class="note"><b>Note: </b>This specification allows only appending, and not other kinds of
extensions. This decision
simplifies application processing required to cast instances from derived to
base type. Future versions may allow more kinds of extension, requiring more
complex transformations to effect casting.</div><p>
For detailed information on complex type definitions, see <a href="#Complex_Type_Definitions">Complex Type Definitions (§3.4)</a>.</p></div></div><div class="div3">
<h4><a id="Declarations_Summary" name="Declarations_Summary"/>2.2.2 Declaration Components</h4><p>There are three kinds of declaration component: element, attribute, and
notation. Each is described in a section below. Also included is a discussion
of element substitution groups, which is a feature provided in conjunction with
element declarations.</p><div class="div4">
<h5><a id="Element_Declaration" name="Element_Declaration"/>2.2.2.1 Element Declaration</h5><p>An element declaration is an association of a name with a type definition, either simple or
complex, an (optional) default value and a (possibly empty) set of identity-constraint
definitions. The association is either global or scoped to a containing complex type definition. A
top-level element declaration with name 'A' is broadly comparable to a pair of
DTD declarations as follows, where the associated type definition
fills in the ellipses:</p><pre><!ELEMENT A . . .>
<!ATTLIST A . . .>
</pre><p>Element declarations contribute to
<a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> as part of model group <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a>, when their defaults and type components are checked against an element
information item with a matching name and namespace, and by triggering
identity-constraint definition <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a>.</p><p>
For detailed information on element declarations, see <a href="#cElement_Declarations">Element Declarations (§3.3)</a>.</p></div><div class="div4">
<h5><a id="Element_Equivalence_Class" name="Element_Equivalence_Class"/>2.2.2.2 Element Substitution Group</h5><p>In XML 1.0, the name and content of an element must correspond exactly to the element type referenced in the corresponding content model.</p><p><span class="termdef"><a id="key-equivalenceClass" name="key-equivalenceClass">[Definition:]  </a>Through
the new mechanism of <b>element substitution groups</b>, XML Schemas provides a more powerful model supporting substitution of one named element for another</span>.
Any top-level element declaration can serve as the defining member, or
head, for an element substitution group. Other top-level element declarations,
regardless of target namespace, can be designated as members of the
substitution group headed by this element. In a suitably enabled content
model, a reference to the head <a class="termref" href="#key-vn"><span class="arrow">·</span>validates<span class="arrow">·</span></a> not just the head itself, but elements
corresponding to any other member of the substitution group as well.
</p><p>All such members must have type definitions which are either the same as the
head's type definition or
restrictions or extensions of it.
Therefore, although the names of elements can vary widely as new
namespaces and members of the substitution group are defined, the
content of member elements is strictly limited according to the type
definition of the substitution group head.</p><p>Note that element substitution groups are not represented as separate components. They are
specified in the property values for element declarations (see <a href="#cElement_Declarations">Element Declarations (§3.3)</a>).</p></div><div class="div4">
<h5><a id="Attribute_Declaration" name="Attribute_Declaration"/>2.2.2.3 Attribute Declaration</h5><p>An attribute declaration is an association between a name and a simple type definition, together
with occurrence information and (optionally) a default value. The
association is either global, or local to its containing complex type definition. Attribute declarations contribute to
<a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> as part of complex type definition <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a>, when their
occurrence, defaults and type components are checked against an attribute
information item with a matching name and namespace.</p><p>
For detailed information on attribute declarations, see <a href="#cAttribute_Declarations">Attribute Declarations (§3.2)</a>.</p></div><div class="div4">
<h5><a id="Notation_Declaration" name="Notation_Declaration"/>2.2.2.4 Notation Declaration</h5><p>A notation declaration is an association between a name and an identifier for a
notation. For an attribute information item to be <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to a
<code>NOTATION</code> simple type definition, its value must have been declared
with a notation declaration.</p><p>
For detailed information on notation declarations, see <a href="#cNotation_Declarations">Notation Declarations (§3.12)</a>.</p></div></div><div class="div3">
<h4><a id="Model_Group_Summary" name="Model_Group_Summary"/>2.2.3 Model Group Components</h4><p>The model group, particle, and wildcard components contribute to
the portion of a complex type definition that controls an element
information item's content.</p><div class="div4">
<h5><a id="Model_Group" name="Model_Group"/>2.2.3.1 Model Group</h5><p>A model group is a constraint in the form of a grammar fragment that applies to
lists of element information items. It consists of a list of particles, i.e.
element declarations, wildcards and model groups. There are three varieties of
model group:</p><ul><li>Sequence (the element information items
match the particles in sequential order);</li><li>Conjunction (the element information items match the
particles, in any order);</li><li>Disjunction (the element information items match
one of the particles).</li></ul><p>
For detailed information on model groups, see <a href="#Model_Groups">Model Groups (§3.8)</a>.</p></div><div class="div4">
<h5><a id="Particle" name="Particle"/>2.2.3.2 Particle</h5><p>A particle is a term in the grammar for element content, consisting of either an element
declaration, a wildcard or a model group, together with
occurrence constraints. Particles contribute to
<a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> as part of complex type definition <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a>, when they allow anywhere
from zero to many element information items or sequences thereof, depending on
their contents and occurrence
constraints.</p><p><span class="termdef"><a id="key-contentModel" name="key-contentModel">[Definition:]  </a>A particle can
be used in a complex type definition to constrain the <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a>
of the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> of an element information item; such a particle is called
a <b>content model</b></span>.
</p><div class="note"><b>Note: </b><em>XML Schema: Structures</em> <a class="termref" href="#key-contentModel"><span class="arrow">·</span>content models<span class="arrow">·</span></a> are similar to but more expressive than
<a href="#ref-xml">[XML 1.0 (Second Edition)]</a> content models; unlike <a href="#ref-xml">[XML 1.0 (Second Edition)]</a>, <em>XML Schema: Structures</em> applies <a class="termref" href="#key-contentModel"><span class="arrow">·</span>content models<span class="arrow">·</span></a> to the <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> of both mixed and element-only content. </div><p>
For detailed information on particles, see <a href="#cParticles">Particles (§3.9)</a>.</p></div><div class="div4">
<h5><a id="Attribute_Use" name="Attribute_Use"/>2.2.3.3 Attribute Use</h5><p>An attribute use plays a role similar to that of a particle, but for
attribute declarations: an attribute declaration within a complex type definition
is embedded within an attribute use, which specifies whether the declaration
requires or merely allows its attribute, and whether it has a default or fixed value.</p></div><div class="div4">
<h5><a id="Wildcard" name="Wildcard"/>2.2.3.4 Wildcard</h5><p>A wildcard is a special kind of particle which matches element and attribute information items dependent on their namespace name, independently
of their local names.</p><p>
For detailed information on wildcards, see <a href="#Wildcards">Wildcards (§3.10)</a>.</p></div></div><div class="div3">
<h4><a id="Identity-constraint_Definition" name="Identity-constraint_Definition"/>2.2.4 Identity-constraint Definition Components</h4><p>An identity-constraint definition is an association between a name and one of
several varieties of
identity-constraint related to uniqueness and reference. All the
varieties use <a href="#bib-xpath">[XPath]</a> expressions to pick out sets of
information items relative to particular target element
information items which are unique, or a key, or a <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> reference, within
a specified scope. An element information item is only <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with
respect to an element declaration
with identity-constraint definitions if those definitions are all satisfied for all the descendants
of that element information item which they pick out.</p><p>
For detailed information on identity-constraint definitions, see <a href="#cIdentity-constraint_Definitions">Identity-constraint Definitions (§3.11)</a>.</p></div><div class="div3">
<h4><a id="Group_Definitions" name="Group_Definitions"/>2.2.5 Group Definition Components</h4><p>There are two kinds of convenience definitions provided to enable
the re-use of pieces of complex type definitions: model group definitions
and attribute group definitions.</p><div class="div4">
<h5><a id="Model_Group_Definition" name="Model_Group_Definition"/>2.2.5.1 Model Group Definition</h5><p>A model group definition is an association between a name and a model group,
enabling re-use of the same model group in several complex type
definitions.</p><p>
For detailed information on model group definitions, see <a href="#cModel_Group_Definitions">Model Group Definitions (§3.7)</a>.</p></div><div class="div4">
<h5><a id="Attribute_Group_Definition" name="Attribute_Group_Definition"/>2.2.5.2 Attribute Group Definition</h5><p>An attribute group definition is an association between a name and a set of attribute declarations,
enabling re-use of the same set in several complex type
definitions.</p><p>
For detailed information on attribute group definitions, see <a href="#cAttribute_Group_Definitions">Attribute Group Definitions (§3.6)</a>.</p></div></div><div class="div3">
<h4><a id="Annotation" name="Annotation"/>2.2.6 Annotation Components</h4><p>An annotation is information for human and/or mechanical
consumers. The interpretation of such information is
not defined in this specification.</p><p>
For detailed information on annotations, see <a href="#cAnnotations">Annotations (§3.13)</a>.</p></div></div><div class="div2">
<h3><span class="nav"><a class="nav" href="#concepts-data-model"><img src="previous.jpg" alt="previous sub-section"/></a> <a class="nav" href="#concepts-conformance"><img src="next.jpg" alt="next sub-section"/></a></span><a id="concepts-schemaConstraints" name="concepts-schemaConstraints"/>2.3 Constraints and Validation Rules</h3><p>The <a href="#ref-xml">[XML 1.0 (Second Edition)]</a> specification describes two kinds of
constraints on XML documents: <em>well-formedness</em> and
<em>validity</em> constraints. Informally, the well-formedness constraints
are those imposed by the definition of XML itself (such as the rules for the
use of the < and > characters and the rules for proper nesting of
elements), while validity constraints are the further constraints on document
structure provided by a particular DTD. </p><p>The preceding section focused on <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a>, that is
the constraints on information items which schema components supply. In fact
however this specification provides four different kinds of normative statements about schema
components, their representations in XML and their contribution to the
<a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> of information items:</p><dl><dt class="label">Schema Component Constraint</dt><dd><span class="termdef"><a id="gloss-cos" name="gloss-cos">[Definition:]  </a>Constraints on the schema components themselves, i.e.
conditions components must satisfy to be components at all. Located in the
sixth sub-section of the per-component sections of <a href="#components">Schema Component Details (§3)</a>
and tabulated in <a href="#outcome-cos">Schema Component Constraints (§C.4)</a></span>.</dd><dt class="label">Schema Representation Constraint</dt><dd><span class="termdef"><a id="gloss-src" name="gloss-src">[Definition:]  </a>Constraints on the
representation of schema components in XML beyond those which are expressed
in <a href="#normative-schemaSchema">Schema for Schemas (normative) (§A)</a>. Located in the
third sub-section of the per-component sections of <a href="#components">Schema Component Details (§3)</a>
and tabulated in <a href="#outcome-src">Schema Representation Constraints (§C.3)</a></span>.</dd><dt class="label">Validation Rules</dt><dd><span class="termdef"><a id="gloss-cvc" name="gloss-cvc">[Definition:]  </a>Contributions to <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> associated
with schema components. Located in the
fourth sub-section of the per-component sections of <a href="#components">Schema Component Details (§3)</a>
and tabulated in <a href="#validation_failures">Validation Rules (§C.1)</a></span>.</dd><dt class="label">Schema Information Set
Contribution</dt><dd><span class="termdef"><a id="gloss-sic" name="gloss-sic">[Definition:]  </a>Augmentations to <a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a>s
expressed by schema components, which follow
as a consequence of <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> and/or <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a>.
Located in the
fifth sub-section of the per-component sections of <a href="#components">Schema Component Details (§3)</a>
and tabulated in <a href="#PSVI_contributions">Contributions to the post-schema-validation infoset (§C.2)</a></span>.</dd></dl><p>The last of these, schema information set
contributions, are not as new as they might at first seem. XML 1.0
validation augments the XML 1.0 information set in similar ways,
for example by
providing values for attributes not present in instances, and by implicitly
exploiting type information for normalization or access.
(As an example of the latter case, consider the
effect of <code>NMTOKENS</code> on attribute white space, and the semantics of
<code>ID</code> and <code>IDREF</code>.) By including schema
information set contributions, this specification makes explicit some features
that XML 1.0 left implicit.</p></div><div class="div2">
<h3><span class="nav"><a class="nav" href="#concepts-schemaConstraints"><img src="previous.jpg" alt="previous sub-section"/></a> <a class="nav" href="#concepts-nameSymbolSpaces"><img src="next.jpg" alt="next sub-section"/></a></span><a id="concepts-conformance" name="concepts-conformance"/>2.4 Conformance</h3><p>This specification describes three levels of conformance for schema aware processors. The first is
required of all processors. Support for the other two will depend on the application environments
for which the processor is intended.</p><p><span class="termdef"><a id="key-minimallyConforming" name="key-minimallyConforming">[Definition:]  </a><b>Minimally conforming</b> processors must completely and
correctly implement the <a class="termref" href="#gloss-cos"><span class="arrow">·</span>Schema Component
Constraints<span class="arrow">·</span></a>, <a class="termref" href="#gloss-cvc"><span class="arrow">·</span>Validation Rules<span class="arrow">·</span></a>,
and <a class="termref" href="#gloss-sic"><span class="arrow">·</span>Schema Information
Set Contributions<span class="arrow">·</span></a> contained in this specification</span>.</p><p><span class="termdef"><a id="key-interchange" name="key-interchange">[Definition:]  </a><a class="termref" href="#key-minimallyConforming"><span class="arrow">·</span>Minimally conforming<span class="arrow">·</span></a> processors which accept
schemas represented in the form of XML documents as described in <a href="#layer2">Layer 2: Schema Documents, Namespaces and Composition (§4.2)</a> are
additionally said to provide <b>conformance to the XML Representation of Schemas</b>.
</span>
Such processors must, when processing schema documents, completely and
correctly implement all <a class="termref" href="#gloss-src"><span class="arrow">·</span>Schema Representation
Constraints<span class="arrow">·</span></a> in this specification, and must adhere exactly to the
specifications in <a href="#components">Schema Component Details (§3)</a> for mapping the contents of
such documents to <a class="termref" href="#key-component"><span class="arrow">·</span>schema
components<span class="arrow">·</span></a> for use in <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> and <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a>.</p><div class="note"><b>Note: </b>By separating the conformance requirements relating to the concrete syntax of XML schema
documents, this specification admits processors
which use schemas stored in optimized binary
representations, dynamically created schemas represented as programming language data structures, or implementations in which particular schemas are compiled into executable code
such as C or Java. Such processors can be said to be <a class="termref" href="#key-minimallyConforming"><span class="arrow">·</span>minimally conforming<span class="arrow">·</span></a> but not necessarily in <a class="termref" href="#key-interchange"><span class="arrow">·</span>conformance to the XML Representation of Schemas<span class="arrow">·</span></a>.</div><p><span class="termdef"><a id="key-fullyConforming" name="key-fullyConforming">[Definition:]  </a> <b>Fully conforming</b>
processors are network-enabled processors which are not only both <a class="termref" href="#key-minimallyConforming"><span class="arrow">·</span>minimally conforming<span class="arrow">·</span></a> and <a class="termref" href="#key-interchange"><span class="arrow">·</span>in conformance to the XML Representation of Schemas<span class="arrow">·</span></a>, but which additionally must be capable of accessing
schema documents from the World Wide Web according to <a href="#web-representation">Representation of Schemas on the World Wide Web (§2.7)</a> and <a href="#schema-loc">How schema definitions are located on the Web (§4.3.2)</a>.
</span>.
</p><div class="note"><b>Note: </b>Although this specification provides just these three standard levels of conformance, it is
anticipated that other conventions can be established in the future. For example, the World Wide
Web Consortium is considering conventions for packaging on the Web a variety of
resources relating to individual documents and namespaces. Should such
developments lead to new conventions for representing schemas, or for accessing them on the Web,
new levels of conformance can be established and named at that time. There is no need to modify
or republish this specification to define such additional levels of conformance.</div><p>See <a href="#composition">Schemas and Namespaces: Access and Composition (§4)</a> for a more detailed explanation of the
mechanisms supporting these levels of conformance.</p></div><div class="div2">
<h3><span class="nav"><a class="nav" href="#concepts-conformance"><img src="previous.jpg" alt="previous sub-section"/></a> <a class="nav" href="#Instance_Document_Constructions"><img src="next.jpg" alt="next sub-section"/></a></span><a id="concepts-nameSymbolSpaces" name="concepts-nameSymbolSpaces"/>2.5 Names and Symbol Spaces</h3><p>As discussed in <a href="#concepts-data-model">XML Schema Abstract Data Model (§2.2)</a>, most schema
components (may) have <a class="termref" href="#key-compName"><span class="arrow">·</span>names<span class="arrow">·</span></a>.
If all such names were assigned from the same "pool", then
it would be impossible to have, for example, a simple type definition and an element
declaration both with the name
"title" in a given <a class="termref" href="#key-targetNS"><span class="arrow">·</span>target namespace<span class="arrow">·</span></a>.</p><p>
Therefore <span class="termdef"><a id="key-symbolSpace" name="key-symbolSpace">[Definition:]  </a>this specification introduces the term
<b>symbol space</b> to denote a
collection of names, each of which is unique with respect to the others</span>. A symbol space is similar to the non-normative concept of <a href="http://www.w3.org/TR/REC-xml-names/#ns-breakdown">namespace partition</a> introduced in <a href="#ref-xml-namespaces">[XML-Namespaces]</a>.
There is a single distinct symbol space within a given <a class="termref" href="#key-targetNS"><span class="arrow">·</span>target
namespace<span class="arrow">·</span></a> for each kind of definition and declaration component
identified in <a href="#concepts-data-model">XML Schema Abstract Data Model (§2.2)</a>, except that within a target namespace, simple
type definitions and complex type definitions share a symbol space.
Within a given symbol space, names are unique, but the same name may appear in more than one symbol space without conflict. For example, the same name can appear in both a type definition and an element declaration, without conflict or necessary relation between the two.
</p><p>Locally scoped attribute and element
declarations are special with regard to symbol spaces.
Every complex type definition defines its own local attribute and element declaration symbol
spaces, where these symbol spaces are distinct from each other and from any of the other
symbol spaces. So, for example, two complex type definitions having
the same target namespace can contain
a local attribute declaration for the unqualified name "priority", or contain a local element declaration
for the name "address", without conflict or necessary relation between
the two.</p></div><div class="div2">
<h3 class="withToc"><span class="nav"><a class="nav" href="#concepts-nameSymbolSpaces"><img src="previous.jpg" alt="previous sub-section"/></a> <a class="nav" href="#web-representation"><img src="next.jpg" alt="next sub-section"/></a></span><a id="Instance_Document_Constructions" name="Instance_Document_Constructions"/>2.6 Schema-Related Markup in
Documents Being Validated</h3><div class="localToc">        2.6.1 <a href="#xsi_type">xsi:type</a><br/>
        2.6.2 <a href="#xsi_nil">xsi:nil</a><br/>
        2.6.3 <a href="#xsi_schemaLocation">xsi:schemaLocation, xsi:noNamespaceSchemaLocation</a><br/>
</div><p>The XML representation of schema components uses a vocabulary
identified by the namespace name <code>http://www.w3.org/2001/XMLSchema</code>. For brevity, the text and examples in this specification use the prefix
<code>xs:</code> to stand for this namespace; in practice,
any prefix can be used.</p><p><em>XML Schema: Structures</em> also defines several attributes for direct use in any XML documents. These attributes are in a different namespace,
which has the namespace name <code>http://www.w3.org/2001/XMLSchema-instance</code>.
For brevity, the text and examples in this specification use the prefix
<code>xsi:</code> to stand for this latter namespace; in practice,
any prefix can be used. All schema processors have appropriate attribute
declarations for these attributes built in, see <a href="#xsi.type">Attribute Declaration for the 'type' attribute (§3.2.7)</a>,
<a href="#xsi.nil">Attribute Declaration for the 'nil' attribute (§3.2.7)</a>, <a href="#xsi.schemaLocation">Attribute Declaration for the 'schemaLocation' attribute (§3.2.7)</a> and <a href="#xsi.noNamespaceSchemaLocation">Attribute Declaration for the 'noNamespaceSchemaLocation' attribute (§3.2.7)</a>.</p><div class="div3">
<h4><a id="xsi_type" name="xsi_type"/>2.6.1 xsi:type</h4><p>The <a href="#Simple_Type_Definition">Simple Type Definition (§2.2.1.2)</a> or <a href="#Complex_Type_Definition">Complex Type Definition (§2.2.1.3)</a> used in <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> of an element is usually
determined by reference to the appropriate schema components.
An element information item in an instance may, however,
explicitly assert its type using the attribute <code>xsi:type</code>.
The value of this attribute is a <a class="termref" href="#gloss-QName"><span class="arrow">·</span>QName<span class="arrow">·</span></a>; see <a href="#src-qname">QName Interpretation (§3.15.3)</a> for
the means by which the <a class="termref" href="#gloss-QName"><span class="arrow">·</span>QName<span class="arrow">·</span></a> is
associated with a type definition.
</p></div><div class="div3">
<h4><a id="xsi_nil" name="xsi_nil"/>2.6.2 xsi:nil</h4><p><em>XML Schema: Structures</em> introduces a mechanism for signaling that an element should
be accepted as <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> when it has no
content despite a content type which does not require or even necessarily allow empty content. An
element may be
<a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> without content if it has the attribute <code>xsi:nil</code> with
the value <code>true</code>. An element so labeled must be empty, but can
carry attributes if permitted by the corresponding complex type.</p></div><div class="div3">
<h4><a id="xsi_schemaLocation" name="xsi_schemaLocation"/>2.6.3 xsi:schemaLocation, xsi:noNamespaceSchemaLocation</h4><p>The <code>xsi:schemaLocation</code> and <code>xsi:noNamespaceSchemaLocation</code> attributes can be used in a document to provide
hints as to the physical location of schema documents which may be used for <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a>.
See <a href="#schema-loc">How schema definitions are located on the Web (§4.3.2)</a> for details on the use of these attributes.</p></div></div><div class="div2">
<h3><span class="nav"><a class="nav" href="#Instance_Document_Constructions"><img src="previous.jpg" alt="previous sub-section"/></a> </span><a id="web-representation" name="web-representation"/>2.7 Representation of Schemas on the World Wide Web</h3><p>On the World Wide Web, schemas are conventionally represented as XML
documents (preferably of MIME type
<code>application/xml</code> or <code>text/xml</code>, but see clause <a href="#c-vxd">1.1</a> of <a href="#src-include">Inclusion Constraints and Semantics (§4.2.1)</a>), conforming to the specifications in <a href="#layer2">Layer 2: Schema Documents, Namespaces and Composition (§4.2)</a>. For more information on
the representation and use of schema documents on the World Wide Web see <a href="#schema-repr">Standards for representation of schemas and retrieval of schema documents on the Web (§4.3.1)</a> and
<a href="#schema-loc">How schema definitions are located on the Web (§4.3.2)</a>. </p></div></div><div class="div1">
<h2><a id="components" name="components"/>3 Schema Component Details</h2><div class="div2">
<h3 class="withToc"><span class="nav"> <a class="nav" href="#cAttribute_Declarations"><img src="next.jpg" alt="next sub-section"/></a></span><a id="scIntro" name="scIntro"/>3.1 Introduction</h3><div class="localToc">        3.1.1 <a href="#d0e1531">Components and Properties</a><br/>
        3.1.2 <a href="#d0e1568">XML Representations of Components</a><br/>
        3.1.3 <a href="#d0e1610">The Mapping between XML Representations and Components</a><br/>
        3.1.4 <a href="#d0e1654">White Space Normalization during Validation</a><br/>
</div><p>The following sections provide full details on the composition of all schema components, together
with their XML representations and their contributions to <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a>. Each section is devoted to a single component, with separate subsections for
</p><ol class="enumar"><li>properties: their values and significance</li><li>XML representation and the mapping to properties</li><li>constraints on representation</li><li>validation rules</li><li><a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a> contributions</li><li>constraints on the components themselves</li></ol><p>
The sub-sections immediately below introduce conventions and terminology used throughout the component sections.</p><div class="div3">
<h4><a id="d0e1531" name="d0e1531"/>3.1.1 Components and Properties</h4><p>Components are defined in terms of their
properties, and each property in turn is defined by giving its range,
that is the values it may have. This can be understood as
defining a schema as a labeled directed graph, where the root is a schema,
every other vertex is a schema
component or a literal (string, boolean, number) and every labeled edge is a
property. The graph is <em>not</em> acyclic: multiple copies of
components with the same name in the same <a class="termref" href="#key-symbolSpace"><span class="arrow">·</span>symbol space<span class="arrow">·</span></a> may not exist, so in some cases re-entrant chains
of properties must exist. Equality of components for the purposes of this
specification is always defined as equality of names (including target
namespaces) within symbol spaces.</p><div class="note"><b>Note: </b>A schema and its components as defined in this chapter are an idealization of the information a schema-aware
processor requires: implementations are not constrained in how they provide
it. In particular, no implications about literal embedding versus indirection
follow from the use below of language such as "properties . . . having . . .
components as values".</div><p><span class="termdef"><a id="key-null" name="key-null">[Definition:]  </a>Throughout this specification, the
term <b>absent</b> is used as a distinguished property value denoting absence</span>.</p><p>Any property not
identified as optional is required to be present; optional properties which are
not present are taken to have <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> as their value. Any
property identified as a having a set, subset or list value may have an empty value unless this is explicitly
ruled out: this is <em>not</em> the same as <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>. Any property value identified as a superset or subset of some set may be equal to that set, unless a proper superset or subset is explicitly called for.
By 'string' in Part 1 of this specification is meant a
sequence of ISO 10646 characters identified as <a href="http://www.w3.org/TR/REC-xml#charsets">legal XML characters</a>
in <a href="#ref-xml">[XML 1.0 (Second Edition)]</a>.</p></div><div class="div3">
<h4><a id="d0e1568" name="d0e1568"/>3.1.2 XML Representations of Components</h4><p>The principal purpose of <em>XML Schema: Structures</em> is to define a set of
schema components that constrain the contents of instances and augment the
information sets thereof. Although no external representation
of schemas is required for this purpose, such representations will
obviously be widely used. To provide for this in an appropriate and
interoperable way, this specification provides a normative XML representation for schemas which
makes provision for every kind of schema
component. <span class="termdef"><a id="key-schemaDoc" name="key-schemaDoc">[Definition:]  </a>A document in
this form (i.e. a <a class="eltref" href="#element-schema"><schema></a> element information item) is a <b>schema document</b></span>. For the schema document as a whole, and
its constituents, the sections below define correspondences between element
information items (with declarations in
<a href="#normative-schemaSchema">Schema for Schemas (normative) (§A)</a> and <a href="#nonnormative-schemaDTD">DTD for Schemas (non-normative) (§G)</a>) and
schema components. All the element information items in the XML representation
of a schema must be in the XML Schema namespace, that is their <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[namespace name]</a> must be <code>http://www.w3.org/2001/XMLSchema</code>. Although a common way of creating the XML Infosets which are or contain <a class="termref" href="#key-schemaDoc"><span class="arrow">·</span>schema documents<span class="arrow">·</span></a> will be using an XML parser, this is not required: any mechanism which constructs conformant infosets as defined in <a href="#ref-xmlinfo">[XML-Infoset]</a> is a possible starting point.</p><p>Two aspects of the XML representations of components presented in the
following sections are constant across them all:
</p><ol class="enumar"><li>All of them allow attributes qualified with namespace names other than
the XML Schema namespace itself: these appear as annotations in the
corresponding schema component;</li><li>All of them allow an <a class="eltref" href="#element-annotation"><annotation></a> as their first child, for human-readable documentation and/or machine-targeted information.</li></ol><p>
</p></div><div class="div3">
<h4><a id="d0e1610" name="d0e1610"/>3.1.3 The Mapping between XML Representations and Components</h4><p>For each kind of schema component there is a corresponding normative XML representation.
The sections below describe the correspondences between the properties of each kind of
schema component on the one hand and the properties of information items in
that XML representation on the other, together
with constraints on that representation above and beyond those implicit in the
<a href="#normative-schemaSchema">Schema for Schemas (normative) (§A)</a>.</p><p>The language used is as if the correspondences were mappings from XML representation to
schema component, but the mapping in the other direction, and therefore the
correspondence in the abstract, can always be
constructed therefrom.</p><p>In discussing the mapping from XML representations to schema
components below, the value of a component property is often determined by the
value of an attribute information item, one of the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> of an element
information item. Since schema documents are constrained by the
<a href="#normative-schemaSchema">Schema for Schemas (normative) (§A)</a>, there is always a simple type
definition associated with any such attribute information item. <span class="termdef"><a id="key-vv" name="key-vv">[Definition:]  </a>The
phrase <b>actual value</b> is used to refer to the member of the value space of the
simple type definition associated with an attribute information item which corresponds to
its <a class="termref" href="#key-nv"><span class="arrow">·</span>normalized value<span class="arrow">·</span></a></span>. This will often be a string, but may also be an
integer, a boolean, a URI reference, etc. This term is also occasionally used with respect to element or attribute information items in a document being <a class="termref" href="#key-va"><span class="arrow">·</span>validated<span class="arrow">·</span></a>.</p><p>Many properties are identified below as having
other schema components or sets of components as values. For the purposes of exposition, the definitions in
this section assume that (unless the property is explicitly identified as
optional) all such values are in fact present. When schema
components are constructed from XML representations involving reference by name
to other components, this assumption may be violated if one or more references
cannot be resolved. This specification addresses the matter of missing
components in a uniform manner, described in <a href="#conformance-missing">Missing Sub-components (§5.3)</a>: no mention of
handling missing components will be found in the individual component
descriptions below.</p><p>Forward reference to named definitions and declarations <em>is</em>
allowed, both within and between <a class="termref" href="#key-schemaDoc"><span class="arrow">·</span>schema documents<span class="arrow">·</span></a>.
By the time the component corresponding to an XML representation which
contains a forward reference is actually needed for <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> an appropriately-named component may have become available to discharge the reference: see <a href="#composition">Schemas and Namespaces: Access and Composition (§4)</a> for details.</p></div><div class="div3">
<h4><a id="d0e1654" name="d0e1654"/>3.1.4 White Space Normalization during Validation</h4><p>Throughout this specification, <span class="termdef"><a id="key-iv" name="key-iv">[Definition:]  </a>the
<b>initial value</b> of some
attribute information item is the value of the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[normalized
value]</a> property of that item. Similarly, the <b>initial value</b> of an element information item is the string composed of, in order, the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.character">[character code]</a> of each character information item in the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> of that
element information item</span>.</p><p>The above definition means that comments and processing instructions,
even in the midst of text, are ignored for all <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> purposes.</p><p><span class="termdef"><a id="key-nv" name="key-nv">[Definition:]  </a>The
<b>normalized value</b> of an element or
attribute information item is an <a class="termref" href="#key-iv"><span class="arrow">·</span>initial value<span class="arrow">·</span></a> whose white space, if any, has been
normalized according to the value of the <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#rf-whiteSpace">whiteSpace facet</a> of the
simple type definition used in its <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a>:
</span>
</p><dl><dt class="label">preserve</dt><dd>No normalization is done, the value is the <a class="termref" href="#key-nv"><span class="arrow">·</span>normalized value<span class="arrow">·</span></a></dd><dt class="label">replace</dt><dd>All occurrences of <code>#x9</code> (tab), <code>#xA</code> (line feed) and
<code>#xD</code> (carriage return) are replaced with <code>#x20</code> (space).</dd><dt class="label">collapse</dt><dd>Subsequent to the replacements specified above under <b>replace</b>,
contiguous sequences of <code>#x20</code>s are collapsed to a single
<code>#x20</code>, and initial and/or final <code>#x20</code>s are deleted.</dd></dl><p>
</p><p>If the simple type definition used in an item's <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> is the <a class="termref" href="#key-simpleUrType"><span class="arrow">·</span>simple ur-type definition<span class="arrow">·</span></a>, the <a class="termref" href="#key-nv"><span class="arrow">·</span>normalized value<span class="arrow">·</span></a> must be determined as in the <b>preserve</b> case above.</p><p>There are three alternative validation rules which may supply the
necessary background for the above: <a href="#cvc-attribute">Attribute Locally Valid (§3.2.4)</a> (clause <a href="#c-sva">3</a>), <a href="#cvc-type">Element Locally Valid (Type) (§3.3.4)</a> (clause <a href="#c-sv1">3.1.3</a>) or <a href="#cvc-complex-type">Element Locally Valid (Complex Type) (§3.4.4)</a> (clause <a href="#c-sv2">2.2</a>).</p><p>These three levels of normalization correspond to the processing mandated
in XML 1.0 for element content, CDATA attribute content and tokenized
attributed content, respectively. See <a href="http://www.w3.org/TR/REC-xml#AVNormalize">Attribute Value Normalization</a> in <a href="#ref-xml">[XML 1.0 (Second Edition)]</a> for the precedent for <b>replace</b> and <b>collapse</b> for attributes. Extending this processing to element content is necessary to ensure a consistent <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> semantics for simple types, regardless of whether they are applied to attributes or elements. Performing it twice in the case of attributes whose <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[normalized
value]</a> has already been subject to replacement or collapse on the basis of
information in a DTD is necessary to ensure consistent treatment of attributes
regardless of the extent to which DTD-based information has been made use of
during infoset construction.</p><div class="note"><b>Note: </b>Even when DTD-based information <em>has</em> been appealed to, and
<a href="http://www.w3.org/TR/REC-xml#AVNormalize">Attribute Value
Normalization</a> has taken place, the above definition of <a class="termref" href="#key-nv"><span class="arrow">·</span>normalized value<span class="arrow">·</span></a> may
mean <em>further</em> normalization takes place, as for instance when
character entity references in attribute values result in white space characters
other than spaces in their <a class="termref" href="#key-iv"><span class="arrow">·</span>initial value<span class="arrow">·</span></a>s.</div></div></div><div class="div2">
<h3 class="withToc"><span class="nav"><a class="nav" href="#scIntro"><img src="previous.jpg" alt="previous sub-section"/></a> <a class="nav" href="#cElement_Declarations"><img src="next.jpg" alt="next sub-section"/></a></span><a id="cAttribute_Declarations" name="cAttribute_Declarations"/>3.2 Attribute Declarations</h3><div class="localToc">        3.2.1 <a href="#Attribute_Declaration_details">The Attribute Declaration Schema Component</a><br/>
        3.2.2 <a href="#declare-attribute">XML Representation of Attribute Declaration Schema Components</a><br/>
        3.2.3 <a href="#d0e2403">Constraints on XML Representations of Attribute Declarations</a><br/>
        3.2.4 <a href="#d0e2483">Attribute Declaration Validation Rules</a><br/>
        3.2.5 <a href="#d0e2622">Attribute Declaration Information Set Contributions</a><br/>
        3.2.6 <a href="#coss-attribute">Constraints on Attribute Declaration Schema Components</a><br/>
        3.2.7 <a href="#d0e3067">Built-in Attribute Declarations</a><br/>
</div><p>Attribute declarations provide for:</p><ul><li>Local <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> of attribute information item values using a simple type definition;</li><li>Specifying default or fixed values for attribute information items.</li></ul><div class="exampleOuter"><div class="exampleHeader">Example</div><div class="exampleInner"><pre><xs:attribute name="age" type="xs:positiveInteger" use="required"/>
</pre></div><div class="exampleWrapper">The XML representation of an attribute declaration.</div></div><div class="div3">
<h4><a id="Attribute_Declaration_details" name="Attribute_Declaration_details"/>3.2.1 The Attribute Declaration Schema Component</h4><p>The attribute declaration schema component has the following
properties:</p><div class="schemaComp"><div class="compHeader"><span class="schemaComp">Schema Component</span>: <a href="#Attribute_Declaration">Attribute Declaration</a></div><div class="compBody">
<dl class="props">
<dt><a name="a-name" id="a-name"><span class="propdef">{name}</span></a></dt><dd>An NCName as defined by
<a href="#ref-xml-namespaces">[XML-Namespaces]</a>.</dd>
<dt><a name="a-target_namespace" id="a-target_namespace"><span class="propdef">{target namespace}</span></a></dt><dd>Either <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> or
a namespace name, as defined in <a href="#ref-xml-namespaces">[XML-Namespaces]</a>.</dd>
<dt><a name="a-simple_type_definition" id="a-simple_type_definition"><span class="propdef">{type definition}</span></a></dt><dd>A
simple type definition.</dd>
<dt><a name="a-scope" id="a-scope"><span class="propdef">{scope}</span></a></dt><dd>Optional. Either <i>global</i> or a complex type
definition.</dd>
<dt><a name="a-value_constraint" id="a-value_constraint"><span class="propdef">{value constraint}</span></a></dt><dd>Optional. A pair
consisting of a value and one of <i>default</i>, <i>fixed</i>.</dd>
<dt><a name="a-annotation" id="a-annotation"><span class="propdef">{annotation}</span></a></dt><dd>Optional. An annotation.</dd>
</dl>
</div></div><p>The <a class="propref" href="#a-name">{name}</a> property must match the local part of the names of attributes being <a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a>.</p><p>The value of the attribute must conform to the supplied <a class="propref" href="#a-simple_type_definition">{type definition}</a>.</p><p>A non-<a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> value of the <a class="propref" href="#a-target_namespace">{target namespace}</a> property provides for <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> of
namespace-qualified attribute information items (which must be explicitly
prefixed in the character-level form of XML documents). <a class="termref" href="#key-null"><span class="arrow">·</span>Absent<span class="arrow">·</span></a> values of
<a class="propref" href="#a-target_namespace">{target namespace}</a> <a class="termref" href="#key-vn"><span class="arrow">·</span>validate<span class="arrow">·</span></a> unqualified (unprefixed) items.</p><p>A <a class="propref" href="#a-scope">{scope}</a> of <i>global</i> identifies attribute declarations
available for use in complex type definitions throughout the schema. Locally scoped declarations are available for use only within the
complex type definition identified by the <a class="propref" href="#a-scope">{scope}</a> property. This property is <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> in the case of declarations within attribute group definitions: their scope will be determined when they are used in the construction of complex type definitions.
</p><p><a class="propref" href="#a-value_constraint">{value constraint}</a> reproduces the functions of XML 1.0 default and <code>#FIXED</code>
attribute values. <i>default</i> specifies that the attribute is to appear unconditionally in
the <a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a>, with the supplied value used
whenever the attribute is not actually present; <i>fixed</i> indicates that the attribute value if present must equal the supplied
constraint value, and if absent receives the supplied value as for
<i>default</i>. Note that it is <em>values</em> that are supplied and/or
checked, not strings.</p><p>See <a href="#cAnnotations">Annotations (§3.13)</a> for information on the role of the
<a class="propref" href="#a-annotation">{annotation}</a> property.</p><div class="note"><b>Note: </b>A more complete and formal presentation of the semantics of <a class="propref" href="#a-name">{name}</a>, <a class="propref" href="#a-target_namespace">{target namespace}</a> and <a class="propref" href="#a-value_constraint">{value constraint}</a> is provided in
conjunction with other aspects of complex type <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> (see <a href="#cvc-complex-type">Element Locally Valid (Complex Type) (§3.4.4)</a>.)</div><p><a href="#ref-xmlinfo">[XML-Infoset]</a> distinguishes attributes with names such as <code>xmlns</code> or <code>xmlns:xsl</code> from
ordinary attributes, identifying them as <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[namespace attributes]</a>. Accordingly, it is unnecessary and in fact not possible for
schemas to contain attribute declarations corresponding to such
namespace declarations, see <a href="#no-xmlns">xmlns Not Allowed (§3.2.6)</a>. No means is provided in
this specification to supply a
default value for a namespace declaration.</p></div><div class="div3">
<h4><a id="declare-attribute" name="declare-attribute"/>3.2.2 XML Representation of Attribute Declaration Schema Components</h4><p>The XML representation for an attribute declaration schema component is an
<a class="eltref" href="#element-attribute"><attribute></a> element information item. It specifies a simple type
definition for an attribute either by reference or explicitly, and may provide default information. The correspondences between the
properties of the information item and
properties of the component are as follows:</p><div class="reprdef"><div class="reprHeader"><span class="reprdef">XML Representation Summary</span>: <code>attribute</code> Element Information Item</div><div class="reprBody">
<p class="element-syntax-1"><a name="element-attribute" id="element-attribute"><attribute</a><br/>  default = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#string">string</a><br/>  fixed = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#string">string</a><br/>  form = (<var>qualified</var> | <var>unqualified</var>)<br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  name = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#NCName">NCName</a><br/>  ref = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#QName">QName</a><br/>  type = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#QName">QName</a><br/>  use = (<var>optional</var> | <var>prohibited</var> | <var>required</var>) : optional<br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?, <a class="eltref" href="#element-simpleType">simpleType</a>?)<br/></attribute></p>
<div class="reprdep">If the <a class="eltref" href="#element-attribute"><attribute></a> element information item has <a class="eltref" href="#element-schema"><schema></a> as its parent, the corresponding schema component is as follows:</div>
<div class="reprcomp"><table class="reprcomp"><thead><tr><th><a href="#Attribute_Declaration_details">Attribute Declaration</a><strong> Schema Component</strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Representation</th></tr></thead><tbody valign="top"><tr valign="top"><td><a class="propref" href="#a-name">{name}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>name</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a></td></tr><tr valign="top"><td><a class="propref" href="#a-target_namespace">{target namespace}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the
<code>targetNamespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of the parent <a class="eltref" href="#element-schema"><schema></a>
element information item, or <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> if there is none.</td></tr><tr valign="top"><td><a class="propref" href="#a-simple_type_definition">{type definition}</a></td><td>The simple type definition
corresponding to the <a class="eltref" href="#element-simpleType"><simpleType></a> element information item in the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if present, otherwise the simple type definition <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to by
the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>type</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, if present, otherwise the
<a class="termref" href="#simple-ur-type-itself"><span class="arrow">·</span>simple ur-type definition<span class="arrow">·</span></a>.</td></tr><tr valign="top"><td><a class="propref" href="#a-scope">{scope}</a></td><td><i>global</i>.</td></tr><tr valign="top"><td><a class="propref" href="#a-value_constraint">{value constraint}</a></td><td>If there is a <code>default</code> or a <code>fixed</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, then a pair consisting of the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> (with respect to the
<a class="propref" href="#a-simple_type_definition">{type definition}</a>) of that <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> and
either <i>default</i> or <i>fixed</i>, as appropriate, otherwise <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</td></tr><tr valign="top"><td><a class="propref" href="#a-annotation">{annotation}</a></td><td>The annotation corresponding to the <a class="eltref" href="#element-annotation"><annotation></a> element information item in the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if present, otherwise <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</td></tr></tbody></table></td></tr></tbody></table></div>
<div class="reprdep">otherwise if the <a class="eltref" href="#element-attribute"><attribute></a> element information item has
<a class="eltref" href="#element-complexType"><complexType></a> or <a class="eltref" href="#element-attributeGroup"><attributeGroup></a> as an ancestor
and the <code>ref</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> is absent, it corresponds to an
attribute use with properties as follows (unless <code>use='prohibited'</code>, in which case the item
corresponds to nothing at all):</div>
<div class="reprcomp"><table class="reprcomp"><thead><tr><th><a href="#AU_details">Attribute Use</a><strong> Schema Component</strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Representation</th></tr></thead><tbody valign="top"><tr valign="top"><td><a class="propref" href="#required">{required}</a></td><td><i>true</i> if the <code>use</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> is present with <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> <code>required</code>, otherwise
<i>false</i>.</td></tr><tr valign="top"><td><a class="propref" href="#attribute">{attribute declaration}</a></td><td>See the Attribute Declaration mapping
immediately below.</td></tr><tr valign="top"><td><a class="propref" href="#au-value_constraint">{value constraint}</a></td><td>If there is a <code>default</code> or a <code>fixed</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, then a pair consisting of the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> (with respect to the
<a class="propref" href="#a-simple_type_definition">{type definition}</a> of the <a class="propref" href="#attribute">{attribute declaration}</a>) of that <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> and
either <i>default</i> or <i>fixed</i>, as appropriate, otherwise <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</td></tr></tbody></table></td></tr></tbody></table></div>
<div class="reprcomp"><table class="reprcomp"><thead><tr><th><a href="#Attribute_Declaration_details">Attribute Declaration</a><strong> Schema Component</strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Representation</th></tr></thead><tbody valign="top"><tr valign="top"><td><a class="propref" href="#a-name">{name}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>name</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a></td></tr><tr valign="top"><td><a class="propref" href="#a-target_namespace">{target namespace}</a></td><td>If <code>form</code> is present and its
<a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> is <code>qualified</code>, or if <code>form</code> is absent and the
<a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of <code>attributeFormDefault</code> on the <a class="eltref" href="#element-schema"><schema></a>
ancestor is <code>qualified</code>, then the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the
<code>targetNamespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of the parent <a class="eltref" href="#element-schema"><schema></a>
element information item, or <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> if there
is none, otherwise <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</td></tr><tr valign="top"><td><a class="propref" href="#a-simple_type_definition">{type definition}</a></td><td>The simple type definition
corresponding to the <a class="eltref" href="#element-simpleType"><simpleType></a> element information item in the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if present, otherwise the simple type definition <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to by
the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>type</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, if present, otherwise the
<a class="termref" href="#simple-ur-type-itself"><span class="arrow">·</span>simple ur-type definition<span class="arrow">·</span></a>.</td></tr><tr valign="top"><td><a class="propref" href="#a-scope">{scope}</a></td><td>If the <a class="eltref" href="#element-attribute"><attribute></a> element information item
has <a class="eltref" href="#element-complexType"><complexType></a> as an ancestor, the complex definition
corresponding to that item, otherwise (the <a class="eltref" href="#element-attribute"><attribute></a> element
information item is within an <a class="eltref" href="#element-attributeGroup"><attributeGroup></a> definition), <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</td></tr><tr valign="top"><td><a class="propref" href="#a-value_constraint">{value constraint}</a></td><td><a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</td></tr><tr valign="top"><td><a class="propref" href="#a-annotation">{annotation}</a></td><td>The annotation corresponding to the <a class="eltref" href="#element-annotation"><annotation></a> element information item in the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if present, otherwise <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</td></tr></tbody></table></td></tr></tbody></table></div>
<div class="reprdep">otherwise (the <a class="eltref" href="#element-attribute"><attribute></a> element information item has
<a class="eltref" href="#element-complexType"><complexType></a> or <a class="eltref" href="#element-attributeGroup"><attributeGroup></a> as an ancestor and the
<code>ref</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> is present), it corresponds to an
attribute use with properties as follows (unless <code>use='prohibited'</code>, in which case the item
corresponds to nothing at all):</div>
<div class="reprcomp"><table class="reprcomp"><thead><tr><th><a href="#AU_details">Attribute Use</a><strong> Schema Component</strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Representation</th></tr></thead><tbody valign="top"><tr valign="top"><td><a class="propref" href="#required">{required}</a></td><td><i>true</i> if the <code>use</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> is present with <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> <code>required</code>, otherwise
<i>false</i>.</td></tr><tr valign="top"><td><a class="propref" href="#attribute">{attribute declaration}</a></td><td>The (top-level) attribute declaration <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to by the
<a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>ref</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a></td></tr><tr valign="top"><td><a class="propref" href="#au-value_constraint">{value constraint}</a></td><td>If there is a <code>default</code> or a <code>fixed</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, then a pair consisting of the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> (with respect to the
<a class="propref" href="#a-simple_type_definition">{type definition}</a> of the <a class="propref" href="#attribute">{attribute declaration}</a>) of that <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> and
either <i>default</i> or <i>fixed</i>, as appropriate, otherwise <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</td></tr></tbody></table></td></tr></tbody></table></div>
</div></div><p>Attribute declarations can appear at the top level of a schema document, or within complex
type definitions, either as complete (local) declarations, or by reference to top-level
declarations, or within attribute group definitions. For complete declarations, top-level or local, the <code>type</code> attribute is used when the declaration can use a
built-in or pre-declared simple type definition. Otherwise an
anonymous <a class="eltref" href="#element-simpleType"><simpleType></a> is provided inline.</p><p>The default when no simple type definition is referenced or
provided is the <a class="termref" href="#key-simpleUrType"><span class="arrow">·</span>simple ur-type definition<span class="arrow">·</span></a>, which imposes no constraints at all.</p><p>Attribute information items <a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a> by a top-level declaration must be qualified with the
<a class="propref" href="#a-target_namespace">{target namespace}</a> of that declaration (if this is <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>, the item must be unqualified). Control over whether attribute information items
<a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a> by a local declaration must be similarly qualified or not
is provided by the <code>form</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, whose default is provided
by the <code>attributeFormDefault</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> on the enclosing <a class="eltref" href="#element-schema"><schema></a>, via its determination of <a class="propref" href="#a-target_namespace">{target namespace}</a>.</p><p>The names for top-level attribute declarations are in their own
<a class="termref" href="#key-symbolSpace"><span class="arrow">·</span>symbol space<span class="arrow">·</span></a>. The names of locally-scoped
attribute declarations reside in symbol spaces local to the type definition which contains
them.</p></div><div class="div3">
<h4><a id="d0e2403" name="d0e2403"/>3.2.3 Constraints on XML Representations of Attribute Declarations</h4><div class="constraintnote"><a name="src-attribute" id="src-attribute"/><b>Schema Representation Constraint: Attribute Declaration Representation OK</b><br/><div class="constraint">In addition to the conditions imposed on <a class="eltref" href="#element-attribute"><attribute></a> element
information items by the schema for schemas,
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 <code>default</code> and <code>fixed</code> must not both be present.</div><div class="clnumber">2 If <code>default</code> and <code>use</code> are both present,
<code>use</code> must have the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> <code>optional</code>.</div><div class="clnumber">3 If the item's parent is not <a class="eltref" href="#element-schema"><schema></a>, then
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">3.1 One of <code>ref</code> or <code>name</code> must be present, but not both.</div><div class="clnumber">3.2 If <code>ref</code> is present, then all of <a class="eltref" href="#element-simpleType"><simpleType></a>,
<code>form</code> and <code>type</code> must be absent.</div></div>
</div><div class="clnumber">4 <code>type</code> and <a class="eltref" href="#element-simpleType"><simpleType></a>
must not both be present.</div><div class="clnumber">5 The corresponding attribute
declaration must satisfy the conditions set out in
<a href="#coss-attribute">Constraints on Attribute Declaration Schema Components (§3.2.6)</a>.</div></div>
</div></div></div><div class="div3">
<h4><a id="d0e2483" name="d0e2483"/>3.2.4 Attribute Declaration Validation Rules</h4><div class="constraintnote"><a name="cvc-attribute" id="cvc-attribute"/><b>Validation Rule: Attribute Locally Valid</b><br/><div class="constraint">For an attribute information item to be locally <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to an
attribute declaration
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1<a name="c-a1" id="c-a1"> </a>The declaration must not be <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> (see <a href="#conformance-missing">Missing Sub-components (§5.3)</a> for
how this can fail to be the case).</div><div class="clnumber">2<a name="c-a2" id="c-a2"> </a>Its <a class="propref" href="#a-simple_type_definition">{type definition}</a> must not be absent.</div><div class="clnumber">3<a name="c-sva" id="c-sva"> </a>The item's <a class="termref" href="#key-nv"><span class="arrow">·</span>normalized value<span class="arrow">·</span></a> must be locally <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to that <a class="propref" href="#a-simple_type_definition">{type definition}</a> as per <a href="#cvc-simple-type">String Valid (§3.14.4)</a>.</div><div class="clnumber">4 The item's <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> must match the value of the <a class="propref" href="#a-value_constraint">{value constraint}</a>, if it is
present and <i>fixed</i>.</div></div>
</div></div><div class="constraintnote"><a name="cvc-assess-attr" id="cvc-assess-attr"/><b>Validation Rule: Schema-Validity Assessment (Attribute)</b><br/><div class="constraint">The schema-validity assessment of an attribute information item depends
on its <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> alone.<p/><span class="termdef"><a id="key-dd" name="key-dd">[Definition:]  </a>During <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a>, associations
between element and attribute information items among the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>
and <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> on the one hand, and element and attribute
declarations on the other, are established as a side-effect. Such
declarations are called the <b>context-determined declarations</b></span>.
See clause <a href="#c-ctma">3.1</a> (in <a href="#cvc-complex-type">Element Locally Valid (Complex Type) (§3.4.4)</a>) for
attribute declarations, clause <a href="#c-cdde">2</a> (in <a href="#cvc-particle">Element Sequence Locally Valid (Particle) (§3.9.4)</a>) for element
declarations.<p/>For an attribute information item's schema-validity to have been assessed
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 A non-<a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> attribute declaration
must be known for it, namely
<b>one</b> of the following:<div class="constraintlist"><div class="clnumber">1.1 A declaration which has been established as its <a class="termref" href="#key-dd"><span class="arrow">·</span>context-determined declaration<span class="arrow">·</span></a>;</div><div class="clnumber">1.2<a name="c-adbyr" id="c-adbyr"> </a>A declaration resolved to by its <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[local name]</a> and <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[namespace name]</a> as defined by <a href="#cvc-resolve-instance">QName resolution (Instance) (§3.15.4)</a>, provided its <a class="termref" href="#key-dd"><span class="arrow">·</span>context-determined declaration<span class="arrow">·</span></a> is
not <i>skip</i>.</div></div>
</div><div class="clnumber">2 Its <a class="termref" href="#key-vn"><span class="arrow">·</span>validity<span class="arrow">·</span></a> with respect to that
declaration must have been evaluated as per <a href="#cvc-attribute">Attribute Locally Valid (§3.2.4)</a>.</div><div class="clnumber">3 Both clause <a href="#c-a1">1</a> and clause <a href="#c-a2">2</a> of <a href="#cvc-attribute">Attribute Locally Valid (§3.2.4)</a> must be satisfied.</div></div>
<p/><span class="termdef"><a id="key-svaa" name="key-svaa">[Definition:]  </a>For attributes, there is no
difference between assessment and strict assessment, so if the above holds, the attribute information item has been <b>strictly assessed</b></span>.</div></div></div><div class="div3">
<h4><a id="d0e2622" name="d0e2622"/>3.2.5 Attribute Declaration Information Set Contributions</h4><div class="constraintnote"><a name="sic-a-outcome" id="sic-a-outcome"/><b>Schema Information Set Contribution: Assessment Outcome (Attribute)</b><br/><div class="constraint">If the schema-validity of an attribute information item has been assessed
as per <a href="#cvc-assess-attr">Schema-Validity Assessment (Attribute) (§3.2.4)</a>, then in the <a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a> it has properties as follows:<div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> attribute information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="a-validation_context" id="a-validation_context"><span class="propdef">[validation context]</span></a></dt><dd>The nearest ancestor element information
item with a <a class="propref" href="#e-schema_information">[schema information]</a> property.</dd>
<dt><a name="a-validity" id="a-validity"><span class="propdef">[validity]</span></a></dt><dd>
The appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">1 <b>If </b>it was <a class="termref" href="#key-svaa"><span class="arrow">·</span>strictly assessed<span class="arrow">·</span></a>, <b>then </b>
the appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">1.1 <b>If </b>it was
<a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> as defined by <a href="#cvc-attribute">Attribute Locally Valid (§3.2.4)</a>, <b>then </b><i>valid</i>;</div><div class="clnumber">1.2 <b>otherwise </b><i>invalid</i>.</div></div>
</div><div class="clnumber">2 <b>otherwise </b><i>notKnown</i>.</div></div>
</dd>
<dt><a name="a-validation_attempted" id="a-validation_attempted"><span class="propdef">[validation attempted]</span></a></dt><dd>
The appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">1 <b>If </b>it was <a class="termref" href="#key-svaa"><span class="arrow">·</span>strictly assessed<span class="arrow">·</span></a>, <b>then </b><i>full</i>;</div><div class="clnumber">2 <b>otherwise </b><i>none</i>.</div></div></dd>
<dt><a name="a-schema_specified" id="a-schema_specified"><span class="propdef">[schema specified]</span></a></dt><dd><i>infoset</i>. See <a href="#sic-attrDefault">Attribute Default Value (§3.4.5)</a> for the other possible value.</dd>
</dl></div></div></div></div><div class="constraintnote"><a name="sic-attr-error-code" id="sic-attr-error-code"/><b>Schema Information Set Contribution: Validation Failure (Attribute)</b><br/><div class="constraint">If the local <a class="termref" href="#key-vn"><span class="arrow">·</span>validity<span class="arrow">·</span></a>, as defined by <a href="#cvc-attribute">Attribute Locally Valid (§3.2.4)</a>
above, of an attribute information item has been assessed,
in the <a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a> the item has a
property:<div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> attribute information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="a-schema_error_code" id="a-schema_error_code"><span class="propdef">[schema error code]</span></a></dt><dd>
The appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">1 <b>If </b>the item is not <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a>, <b>then </b>a list. Applications wishing to provide
information as to the reason(s) for the <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> failure are encouraged to record one or more
error codes (see <a href="#outcomes">Outcome Tabulations (normative) (§C)</a>) herein.</div><div class="clnumber">2 <b>otherwise </b><a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</div></div>
</dd>
</dl></div></div></div></div><div class="constraintnote"><a name="sic-attr-decl" id="sic-attr-decl"/><b>Schema Information Set Contribution: Attribute Declaration</b><br/><div class="constraint">If an attribute information item is <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to an attribute
declaration as per <a href="#cvc-attribute">Attribute Locally Valid (§3.2.4)</a> then in the <a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a> the attribute
information item may, at processor option, have a property:<div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> attribute information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="a-declaration" id="a-declaration"><span class="propdef">[attribute declaration]</span></a></dt><dd>
An <a class="termref" href="#key-iso"><span class="arrow">·</span>item isomorphic<span class="arrow">·</span></a> to the declaration component itself.
</dd>
</dl></div></div></div></div><div class="constraintnote"><a name="sic-attrType" id="sic-attrType"/><b>Schema Information Set Contribution: Attribute Validated by Type</b><br/><div class="constraint">If clause <a href="#c-sva">3</a> of <a href="#cvc-attribute">Attribute Locally Valid (§3.2.4)</a> applies with
respect to an attribute information item, in the <a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a> the attribute
information item has a property:<div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> attribute information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="a-schema_normalized_value" id="a-schema_normalized_value"><span class="propdef">[schema normalized value]</span></a></dt><dd>
The <a class="termref" href="#key-nv"><span class="arrow">·</span>normalized value<span class="arrow">·</span></a> of the item as <a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a>.
</dd>
</dl></div></div>Furthermore, the item has one of the following alternative sets of properties:<p/>Either<div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> attribute information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="a-type_definition" id="a-type_definition"><span class="propdef">[type definition]</span></a></dt><dd>An <a class="termref" href="#key-iso"><span class="arrow">·</span>item isomorphic<span class="arrow">·</span></a> to the relevant attribute declaration's
<a class="propref" href="#a-simple_type_definition">{type definition}</a> component.</dd>
<dt><a name="a-member_type_definition" id="a-member_type_definition"><span class="propdef">[member type definition]</span></a></dt><dd>If
and only if that type definition has <a class="propref" href="#variety">{variety}</a> <i>union</i>, then an
<a class="termref" href="#key-iso"><span class="arrow">·</span>item isomorphic<span class="arrow">·</span></a> to that member of its <a class="propref" href="#st-member_type_definitions">{member type definitions}</a> which actually <a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a> the attribute item's <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[normalized value]</a>.</dd>
</dl></div></div>or<div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> attribute information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="a-type_definition_type" id="a-type_definition_type"><span class="propdef">[type definition type]</span></a></dt><dd>
<i>simple</i>.</dd>
<dt><a name="a-type_definition_namespace" id="a-type_definition_namespace"><span class="propdef">[type definition namespace]</span></a></dt><dd>The <a class="propref" href="#st-target_namespace">{target namespace}</a> of the <a class="termref" href="#key-typeDefn"><span class="arrow">·</span>type definition<span class="arrow">·</span></a>.</dd>
<dt><a name="a-type_definition_anonymous" id="a-type_definition_anonymous"><span class="propdef">[type definition anonymous]</span></a></dt><dd><i>true</i> if the <a class="propref" href="#st-name">{name}</a> of the <a class="termref" href="#key-typeDefn"><span class="arrow">·</span>type definition<span class="arrow">·</span></a> is <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>, otherwise <i>false</i>.</dd>
<dt><a name="a-type_definition_name" id="a-type_definition_name"><span class="propdef">[type definition name]</span></a></dt><dd>The <a class="propref" href="#st-name">{name}</a> of the <a class="termref" href="#key-typeDefn"><span class="arrow">·</span>type definition<span class="arrow">·</span></a>, if it is not <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>. If it is
<a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>, schema processors may, but need not,
provide a value unique to the definition.</dd>
</dl></div></div>If the <a class="termref" href="#key-typeDefn"><span class="arrow">·</span>type definition<span class="arrow">·</span></a> has <a class="propref" href="#variety">{variety}</a> <i>union</i>, then calling
<span class="termdef"><a id="a-key-amt" name="a-key-amt">[Definition:]  </a> that
member of the <a class="propref" href="#st-member_type_definitions">{member type definitions}</a> which actually
<a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a> the attribute item's <a class="termref" href="#key-nv"><span class="arrow">·</span>normalized value<span class="arrow">·</span></a> the
<b>actual member type definition</b></span>, there are three additional properties:<div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> attribute information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="a-member_type_definition_namespace" id="a-member_type_definition_namespace"><span class="propdef">[member type definition namespace]</span></a></dt><dd>The <a class="propref" href="#st-target_namespace">{target namespace}</a> of the <a class="termref" href="#a-key-amt"><span class="arrow">·</span>actual
member type definition<span class="arrow">·</span></a>.</dd>
<dt><a name="a-member_type_definition_anonymous" id="a-member_type_definition_anonymous"><span class="propdef">[member type definition anonymous]</span></a></dt><dd><i>true</i> if the <a class="propref" href="#st-name">{name}</a> of the <a class="termref" href="#a-key-amt"><span class="arrow">·</span>actual member type definition<span class="arrow">·</span></a> is <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>, otherwise <i>false</i>.</dd>
<dt><a name="a-member_type_definition_name" id="a-member_type_definition_name"><span class="propdef">[member type definition name]</span></a></dt><dd>The <a class="propref" href="#st-name">{name}</a> of the <a class="termref" href="#a-key-amt"><span class="arrow">·</span>actual member type definition<span class="arrow">·</span></a>, if it is not <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>. If it is
<a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>, schema processors may, but need not,
provide a value unique to the definition.</dd>
</dl></div></div>The first (<a class="termref" href="#key-iso"><span class="arrow">·</span>item isomorphic<span class="arrow">·</span></a>) alternative above is provided for applications such as query
processors which need access to the full range of details about an item's
<a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a>, for example the type hierarchy; the second, for lighter-weight
processors for whom representing the significant parts of the type hierarchy as
information items might be a significant burden.<p/>Also, if the declaration has a <a class="propref" href="#a-value_constraint">{value constraint}</a>, the
item has a property:<div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> attribute information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="a-schema_default" id="a-schema_default"><span class="propdef">[schema default]</span></a></dt><dd>
The <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#dt-canonical-representation">canonical lexical representation</a> of
the declaration's <a class="propref" href="#a-value_constraint">{value constraint}</a> value.
</dd>
</dl></div></div>If the attribute information item was not <a class="termref" href="#key-svaa"><span class="arrow">·</span>strictly assessed<span class="arrow">·</span></a>, then instead of the values specified above,
<div class="constraintlist"><div class="clnumber">1 The item's <a class="propref" href="#a-schema_normalized_value">[schema normalized value]</a>
property has
the <a class="termref" href="#key-iv"><span class="arrow">·</span>initial value<span class="arrow">·</span></a> of the item as its value;</div><div class="clnumber">2 The <a class="propref" href="#a-type_definition">[type definition]</a> and
<a class="propref" href="#a-member_type_definition">[member type definition]</a> properties, or their
alternatives, are based on the <a class="termref" href="#simple-ur-type-itself"><span class="arrow">·</span>simple ur-type definition<span class="arrow">·</span></a>.</div></div>
</div></div></div><div class="div3">
<h4><a id="coss-attribute" name="coss-attribute"/>3.2.6 Constraints on Attribute Declaration Schema Components</h4><p>All attribute declarations (see <a href="#cAttribute_Declarations">Attribute Declarations (§3.2)</a>) must satisfy the following constraints.</p><div class="constraintnote"><a name="a-props-correct" id="a-props-correct"/><b>Schema Component Constraint: Attribute Declaration Properties Correct</b><br/><div class="constraint"><b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 The values of the properties of an attribute declaration must be as described in
the property tableau in
<a href="#Attribute_Declaration_details">The Attribute Declaration Schema Component (§3.2.1)</a>, modulo the impact of <a href="#conformance-missing">Missing Sub-components (§5.3)</a>.</div><div class="clnumber">2 if there is a <a class="propref" href="#a-value_constraint">{value constraint}</a>, the <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#dt-canonical-representation">canonical lexical representation</a> of its value must be
<a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to the <a class="propref" href="#a-simple_type_definition">{type definition}</a> as
defined in <a href="#cvc-simple-type">String Valid (§3.14.4)</a>.
</div><div class="clnumber">3 If the <a class="propref" href="#a-simple_type_definition">{type definition}</a> is or is derived from <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a> then there must not be a <a class="propref" href="#a-value_constraint">{value constraint}</a>.</div></div></div></div><div class="constraintnote"><a name="no-xmlns" id="no-xmlns"/><b>Schema Component Constraint: xmlns Not Allowed</b><br/><div class="constraint">The <a class="propref" href="#a-name">{name}</a> of an attribute declaration must not match <code>xmlns</code>.<div class="note"><b>Note: </b>The <a class="propref" href="#a-name">{name}</a> of an attribute is an <a class="termref" href="#gloss-NCName"><span class="arrow">·</span>NCName<span class="arrow">·</span></a>, which implicitly
prohibits attribute declarations of the form <code>xmlns:*</code>.</div></div></div><div class="constraintnote"><a name="no-xsi" id="no-xsi"/><b>Schema Component Constraint: xsi: Not Allowed</b><br/><div class="constraint">The <a class="propref" href="#a-target_namespace">{target namespace}</a> of an attribute declaration,
whether local or top-level, must not match <code>http://www.w3.org/2001/XMLSchema-instance</code>
(unless it is one of the four built-in declarations given in the next section).<div class="note"><b>Note: </b>This reinforces the special status of these attributes, so that they not
only <em>need</em> not be declared to be allowed in instances, but
<em>must</em> not be declared. It also removes any temptation to experiment with supplying global or fixed values
for e.g. <code>xsi:type</code> or <code>xsi:nil</code>, which would be
seriously misleading, as they would have no effect.</div></div></div></div><div class="div3">
<h4><a id="d0e3067" name="d0e3067"/>3.2.7 Built-in Attribute Declarations</h4><p>There are four attribute declarations present in every
schema by definition:</p><table border="1" class="schemaComp"><thead><tr><th><strong><a name="xsi.type" id="xsi.type">Attribute Declaration for the 'type' attribute</a></strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Value</th></tr></thead><tbody valign="top"><tr><td><a class="propref" href="#a-name">{name}</a></td><td><code>type</code></td></tr><tr><td><a class="propref" href="#a-target_namespace">{target namespace}</a></td><td><code>http://www.w3.org/2001/XMLSchema-instance</code></td></tr><tr><td><a class="propref" href="#type_definition">{type definition}</a></td><td>The built-in <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#QName">QName</a> simple
type definition</td></tr><tr><td><a class="propref" href="#a-scope">{scope}</a></td><td><i>global</i></td></tr><tr><td><a class="propref" href="#a-value_constraint">{value constraint}</a></td><td><a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a></td></tr><tr><td><a class="propref" href="#a-annotation">{annotation}</a></td><td><a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a></td></tr></tbody></table></td></tr></tbody></table><table border="1" class="schemaComp"><thead><tr><th><strong><a name="xsi.nil" id="xsi.nil">Attribute Declaration for the 'nil' attribute</a></strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Value</th></tr></thead><tbody valign="top"><tr><td><a class="propref" href="#a-name">{name}</a></td><td><code>nil</code></td></tr><tr><td><a class="propref" href="#a-target_namespace">{target namespace}</a></td><td><code>http://www.w3.org/2001/XMLSchema-instance</code></td></tr><tr><td><a class="propref" href="#type_definition">{type definition}</a></td><td>The built-in <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#boolean">boolean</a> simple
type definition</td></tr><tr><td><a class="propref" href="#a-scope">{scope}</a></td><td><i>global</i></td></tr><tr><td><a class="propref" href="#a-value_constraint">{value constraint}</a></td><td><a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a></td></tr><tr><td><a class="propref" href="#a-annotation">{annotation}</a></td><td><a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a></td></tr></tbody></table></td></tr></tbody></table><table border="1" class="schemaComp"><thead><tr><th><strong><a name="xsi.schemaLocation" id="xsi.schemaLocation">Attribute Declaration for the 'schemaLocation' attribute</a></strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Value</th></tr></thead><tbody valign="top"><tr><td><a class="propref" href="#a-name">{name}</a></td><td><code>schemaLocation</code></td></tr><tr><td><a class="propref" href="#a-target_namespace">{target namespace}</a></td><td><code>http://www.w3.org/2001/XMLSchema-instance</code></td></tr><tr><td><a class="propref" href="#type_definition">{type definition}</a></td><td>An anonymous simple type definition, as follows:
<table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Value</th></tr></thead><tbody valign="top"><tr><td><a class="propref" href="#st-name">{name}</a></td><td><a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a></td></tr><tr><td><a class="propref" href="#st-target_namespace">{target namespace}</a></td><td><code>http://www.w3.org/2001/XMLSchema-instance</code></td></tr><tr><td><a class="propref" href="#st-base_type_definition">{base type definition}</a></td><td>The built in <a class="termref" href="#simple-ur-type-itself"><span class="arrow">·</span>simple ur-type definition<span class="arrow">·</span></a></td></tr><tr><td><a class="propref" href="#facets">{facets}</a></td><td><a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a></td></tr><tr><td><a class="propref" href="#variety">{variety}</a></td><td><i>list</i></td></tr><tr><td><a class="propref" href="#st-item_type_definition">{item type definition}</a></td><td>The built-in <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#anyURI">anyURI</a> simple
type definition</td></tr><tr><td><a class="propref" href="#st-annotation">{annotation}</a></td><td><a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a></td></tr></tbody></table>
</td></tr><tr><td><a class="propref" href="#a-scope">{scope}</a></td><td><i>global</i></td></tr><tr><td><a class="propref" href="#a-value_constraint">{value constraint}</a></td><td><a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a></td></tr><tr><td><a class="propref" href="#a-annotation">{annotation}</a></td><td><a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a></td></tr></tbody></table></td></tr></tbody></table><table border="1" class="schemaComp"><thead><tr><th><strong><a name="xsi.noNamespaceSchemaLocation" id="xsi.noNamespaceSchemaLocation">Attribute Declaration for the 'noNamespaceSchemaLocation' attribute</a></strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Value</th></tr></thead><tbody valign="top"><tr><td><a class="propref" href="#a-name">{name}</a></td><td><code>noNamespaceSchemaLocation</code></td></tr><tr><td><a class="propref" href="#a-target_namespace">{target namespace}</a></td><td><code>http://www.w3.org/2001/XMLSchema-instance</code></td></tr><tr><td><a class="propref" href="#type_definition">{type definition}</a></td><td>The built-in <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#anyURI">anyURI</a> simple
type definition</td></tr><tr><td><a class="propref" href="#a-scope">{scope}</a></td><td><i>global</i></td></tr><tr><td><a class="propref" href="#a-value_constraint">{value constraint}</a></td><td><a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a></td></tr><tr><td><a class="propref" href="#a-annotation">{annotation}</a></td><td><a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a></td></tr></tbody></table></td></tr></tbody></table></div></div><div class="div2">
<h3 class="withToc"><span class="nav"><a class="nav" href="#cAttribute_Declarations"><img src="previous.jpg" alt="previous sub-section"/></a> <a class="nav" href="#Complex_Type_Definitions"><img src="next.jpg" alt="next sub-section"/></a></span><a id="cElement_Declarations" name="cElement_Declarations"/>3.3 Element Declarations</h3><div class="localToc">        3.3.1 <a href="#Element_Declaration_details">The Element Declaration Schema Component</a><br/>
        3.3.2 <a href="#declare-element">XML Representation of Element Declaration Schema Components</a><br/>
        3.3.3 <a href="#d0e4233">Constraints on XML Representations of Element Declarations</a><br/>
        3.3.4 <a href="#d0e4333">Element Declaration Validation Rules</a><br/>
        3.3.5 <a href="#d0e5070">Element Declaration Information Set Contributions</a><br/>
        3.3.6 <a href="#coss-element">Constraints on Element Declaration Schema Components</a><br/>
</div><p>Element declarations provide for:</p><ul><li>Local <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> of element information item values using a type definition;</li><li>Specifying default or fixed values for an element information items;</li><li>Establishing uniquenesses and reference constraint relationships among the values of related elements and
attributes;</li><li>Controlling the substitutability of elements through the
mechanism of <a class="termref" href="#key-equivalenceClass"><span class="arrow">·</span>element substitution groups<span class="arrow">·</span></a>.</li></ul><div class="exampleOuter"><div class="exampleHeader">Example</div><div class="exampleInner"><pre><xs:element name="PurchaseOrder" type="PurchaseOrderType"/>
<xs:element name="gift">
<xs:complexType>
<xs:sequence>
<xs:element name="birthday" type="xs:date"/>
<xs:element ref="PurchaseOrder"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</pre></div><div class="exampleWrapper">XML representations of several different types of element declaration</div></div><div class="div3">
<h4><a id="Element_Declaration_details" name="Element_Declaration_details"/>3.3.1 The Element Declaration Schema Component</h4><p>The element declaration schema component has the following
properties:</p><div class="schemaComp"><div class="compHeader"><span class="schemaComp">Schema Component</span>: <a href="#Element_Declaration">Element Declaration</a></div><div class="compBody">
<dl class="props">
<dt><a name="e-name" id="e-name"><span class="propdef">{name}</span></a></dt><dd>An NCName as defined by
<a href="#ref-xml-namespaces">[XML-Namespaces]</a>.</dd>
<dt><a name="e-target_namespace" id="e-target_namespace"><span class="propdef">{target namespace}</span></a></dt><dd>Either <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> or
a namespace name, as defined in <a href="#ref-xml-namespaces">[XML-Namespaces]</a>.</dd>
<dt><a name="type_definition" id="type_definition"><span class="propdef">{type definition}</span></a></dt><dd>Either a simple type
definition or a complex type definition.</dd>
<dt><a name="e-scope" id="e-scope"><span class="propdef">{scope}</span></a></dt><dd>Optional. Either <i>global</i> or a complex type
definition.</dd>
<dt><a name="e-value_constraint" id="e-value_constraint"><span class="propdef">{value constraint}</span></a></dt><dd>Optional. A
pair consisting of a value and one of <i>default</i>, <i>fixed</i>.</dd>
<dt><a name="nillable" id="nillable"><span class="propdef">{nillable}</span></a></dt><dd>A boolean.</dd>
<dt><a name="identity-constraint_definitions" id="identity-constraint_definitions"><span class="propdef">{identity-constraint definitions}</span></a></dt><dd>A set
of constraint definitions.</dd>
<dt><a name="class_exemplar" id="class_exemplar"><span class="propdef">{substitution group affiliation}</span></a></dt><dd>Optional. A top-level
element definition.</dd>
<dt><a name="e-final" id="e-final"><span class="propdef">{substitution group exclusions}</span></a></dt><dd>A subset of
{<i>extension</i>,
<i>restriction</i>}.</dd>
<dt><a name="e-exact" id="e-exact"><span class="propdef">{disallowed substitutions}</span></a></dt><dd>A subset of {<i>substitution</i>, <i>extension</i>,
<i>restriction</i>}.</dd>
<dt><a name="e-abstract" id="e-abstract"><span class="propdef">{abstract}</span></a></dt><dd>A boolean.</dd>
<dt><a name="e-annotation" id="e-annotation"><span class="propdef">{annotation}</span></a></dt><dd>Optional. An annotation.</dd>
</dl>
</div></div><p>The <a class="propref" href="#e-name">{name}</a> property must match the local part of the names
of element information items being <a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a>.</p><p>A <a class="propref" href="#e-scope">{scope}</a> of <i>global</i> identifies element declarations available for use in content
models throughout the schema. Locally scoped declarations are available for use only within the
complex type identified by the <a class="propref" href="#e-scope">{scope}</a> property. This property is <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> in the case of declarations within named model groups: their scope is determined when they are used in the construction of complex type definitions.</p><p>A non-<a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> value of the <a class="propref" href="#e-target_namespace">{target namespace}</a> property provides for <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> of
namespace-qualified element information items. <a class="termref" href="#key-null"><span class="arrow">·</span>Absent<span class="arrow">·</span></a> values of
<a class="propref" href="#e-target_namespace">{target namespace}</a> <a class="termref" href="#key-vn"><span class="arrow">·</span>validate<span class="arrow">·</span></a> unqualified items.</p><p>An element information item is <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a>
if it satisfies the <a class="propref" href="#type_definition">{type definition}</a>. For such an
item, schema information set contributions appropriate to the <a class="propref" href="#type_definition">{type definition}</a> are added to the
corresponding element information item in the <a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a>.
</p><p>If <a class="propref" href="#nillable">{nillable}</a> is <i>true</i>, then an element may
also be <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> if it
carries the namespace qualified attribute with <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[local name]</a> <code>nil</code> from namespace <code>http://www.w3.org/2001/XMLSchema-instance</code> and value <code>true</code> (see <a href="#xsi_nil">xsi:nil (§2.6.2)</a>) even if it has
no text or element content despite a <a class="propref" href="#content_type">{content type}</a> which would
otherwise require content. Formal details of element <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> are described in <a href="#cvc-elt">Element Locally Valid (Element) (§3.3.4)</a>.</p><p><a class="propref" href="#e-value_constraint">{value constraint}</a> establishes a default or fixed value for an element. If <i>default</i> is specified, and if the element
being <a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a> is empty, then the
canonical form of the supplied
constraint value becomes the <a class="propref" href="#e-schema_normalized_value">[schema normalized value]</a> of the <a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a> element in the <a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a>. If <i>fixed</i> is specified, then the element's content
must either be empty, in which case <i>fixed</i> behaves as <i>default</i>,
or its value must match the supplied constraint value.</p><div class="note"><b>Note: </b>The provision of defaults for elements goes beyond what is possible in
XML 1.0 DTDs, and does not exactly correspond to defaults for attributes. In
particular, an element with a non-empty <a class="propref" href="#e-value_constraint">{value constraint}</a> whose simple
type definition includes the empty string in its lexical space will
nonetheless never receive that value, because the <a class="propref" href="#e-value_constraint">{value constraint}</a> will override it.</div><p><a class="propref" href="#identity-constraint_definitions">{identity-constraint definitions}</a> express constraints establishing uniquenesses and reference relationships among the values of related elements and
attributes. See <a href="#cIdentity-constraint_Definitions">Identity-constraint Definitions (§3.11)</a>.</p><p>Element declarations are potential members of the substitution group, if any, identified
by <a class="propref" href="#class_exemplar">{substitution group affiliation}</a>. Potential membership is transitive but not symmetric; an element
declaration is a potential member of any group of which its <a class="propref" href="#class_exemplar">{substitution group affiliation}</a> is a potential member. Actual membership may be blocked by the effects of <a class="propref" href="#e-final">{substitution group exclusions}</a> or <a class="propref" href="#e-exact">{disallowed substitutions}</a>, see below.</p><p>An empty <a class="propref" href="#e-final">{substitution group exclusions}</a> allows a declaration to be nominated as
the <a class="propref" href="#class_exemplar">{substitution group affiliation}</a> of other element declarations having the same <a class="propref" href="#type_definition">{type definition}</a> or
types derived therefrom. The explicit
values of <a class="propref" href="#e-final">{substitution group exclusions}</a> rule out element declarations having types which
are <i>extension</i>s or <i>restriction</i>s respectively of <a class="propref" href="#type_definition">{type definition}</a>. If
both values are specified, then the declaration may not be nominated as the
<a class="propref" href="#class_exemplar">{substitution group affiliation}</a> of any other declaration.</p><p>The supplied values for <a class="propref" href="#e-exact">{disallowed substitutions}</a> determine
whether an element declaration appearing in a <a class="termref" href="#key-contentModel"><span class="arrow">·</span>content model<span class="arrow">·</span></a> will be prevented from additionally
<a class="termref" href="#key-vn"><span class="arrow">·</span>validating<span class="arrow">·</span></a> elements (a) with an <a href="#xsi_type">xsi:type (§2.6.1)</a> that identifies an
<i>extension</i> or <i>restriction</i> of the type of the declared element, and/or (b) from <a class="termref" href="#key-vn"><span class="arrow">·</span>validating<span class="arrow">·</span></a> elements which are in the
substitution group headed by the declared element.
If <a class="propref" href="#e-exact">{disallowed substitutions}</a> is empty, then all derived types and substitution group members are allowed.</p><p>Element declarations for which <a class="propref" href="#e-abstract">{abstract}</a> is <i>true</i> can appear in
content models only when substitution is allowed;
such declarations may not themselves ever be used to <a class="termref" href="#key-vn"><span class="arrow">·</span>validate<span class="arrow">·</span></a> element content.</p><p>See <a href="#cAnnotations">Annotations (§3.13)</a> for information on the role of the
<a class="propref" href="#e-annotation">{annotation}</a> property.</p></div><div class="div3">
<h4><a id="declare-element" name="declare-element"/>3.3.2 XML Representation of Element Declaration Schema Components</h4><p>The XML representation for an element declaration schema component is an
<a class="eltref" href="#element-element"><element></a> element information item. It specifies a type
definition for an element either by reference or explicitly, and may provide
occurrence and default information. The correspondences between the
properties of the information item and
properties of the component(s) it corresponds to are as follows:</p><div class="reprdef"><div class="reprHeader"><span class="reprdef">XML Representation Summary</span>: <code>element</code> Element Information Item</div><div class="reprBody">
<p class="element-syntax-1"><a name="element-element" id="element-element"><element</a><br/>  abstract = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#boolean">boolean</a> : false<br/>  block =
(<var>#all</var> | List of (<var>extension</var> | <var>restriction</var> | <var>substitution</var>))
<br/>  default = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#string">string</a><br/>  final =
(<var>#all</var> | List of (<var>extension</var> | <var>restriction</var>))
<br/>  fixed = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#string">string</a><br/>  form = (<var>qualified</var> | <var>unqualified</var>)<br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  maxOccurs =
(<a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#nonNegativeInteger">nonNegativeInteger</a> | <var>unbounded</var>)
 : 1<br/>  minOccurs = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#nonNegativeInteger">nonNegativeInteger</a> : 1<br/>  name = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#NCName">NCName</a><br/>  nillable = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#boolean">boolean</a> : false<br/>  ref = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#QName">QName</a><br/>  substitutionGroup = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#QName">QName</a><br/>  type = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#QName">QName</a><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?, ((<a class="eltref" href="#element-simpleType">simpleType</a> | <a class="eltref" href="#element-complexType">complexType</a>)?, (<a class="eltref" href="#element-unique">unique</a> | <a class="eltref" href="#element-key">key</a> | <a class="eltref" href="#element-keyref">keyref</a>)*))<br/></element></p>
<div class="reprdep">If the <a class="eltref" href="#element-element"><element></a> element information item has <a class="eltref" href="#element-schema"><schema></a> as its parent, the corresponding schema component is as follows:</div>
<div class="reprcomp"><table class="reprcomp"><thead><tr><th><a href="#Element_Declaration_details">Element Declaration</a><strong> Schema Component</strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Representation</th></tr></thead><tbody valign="top"><tr valign="top"><td><a class="propref" href="#e-name">{name}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>name</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>.</td></tr><tr valign="top"><td><a class="propref" href="#e-target_namespace">{target namespace}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the
<code>targetNamespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of the parent <a class="eltref" href="#element-schema"><schema></a>
element information item, or <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> if there is none.</td></tr><tr valign="top"><td><a class="propref" href="#e-scope">{scope}</a></td><td><i>global</i>.</td></tr><tr valign="top"><td><a class="propref" href="#type_definition">{type definition}</a></td><td>The type definition
corresponding to the <a class="eltref" href="#element-simpleType"><simpleType></a> or <a class="eltref" href="#element-complexType"><complexType></a> element information item in the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if either is present, otherwise the type definition <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to by
the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>type</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, otherwise the <a class="propref" href="#type_definition">{type definition}</a> of the element declaration <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to by the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>substitutionGroup</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, if present, otherwise the
<a class="termref" href="#ur-type-itself"><span class="arrow">·</span>ur-type definition<span class="arrow">·</span></a>.</td></tr><tr valign="top"><td><a class="propref" href="#nillable">{nillable}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>nillable</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, if present, otherwise <i>false</i>.</td></tr><tr valign="top"><td><a class="propref" href="#e-value_constraint">{value constraint}</a></td><td>If there is a <code>default</code> or a <code>fixed</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, then a pair consisting of the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> (with respect to the
<a class="propref" href="#type_definition">{type definition}</a>, if it is a simple type definition, or the
<a class="propref" href="#type_definition">{type definition}</a>'s <a class="propref" href="#content_type">{content type}</a>, if that is a
simple type definition, or else with respect to the built-in <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#string">string</a> simple type definition) of that <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> and
either <i>default</i> or <i>fixed</i>, as appropriate, otherwise <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</td></tr><tr valign="top"><td><a class="propref" href="#identity-constraint_definitions">{identity-constraint definitions}</a></td><td>A set consisting of the
identity-constraint-definitions corresponding to all the <a class="eltref" href="#element-key"><key></a>, <a class="eltref" href="#element-unique"><unique></a> and <a class="eltref" href="#element-keyref"><keyref></a> element information items in the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if any, otherwise the empty set.</td></tr><tr valign="top"><td><a class="propref" href="#class_exemplar">{substitution group affiliation}</a></td><td>The element declaration <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to by the
<a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the
<code>substitutionGroup</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, if present, otherwise <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</td></tr><tr valign="top"><td><a class="propref" href="#e-exact">{disallowed substitutions}</a></td><td>A set depending on the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the
<code>block</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, if present, otherwise on the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the
<code>blockDefault</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of the ancestor <a class="eltref" href="#element-schema"><schema></a> element
information item, if present, otherwise on the empty string. Call this the <b>EBV</b> (for effective block value). Then the value of this property is
the appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">1 <b>If </b>the <b>EBV</b> is the empty string, <b>then </b>the empty set;</div><div class="clnumber">2 <b>If </b>the <b>EBV</b> is <code>#all</code>, <b>then </b><code>{</code><i>extension</i>, <i>restriction</i>, <i>substitution</i><code>}</code>;</div><div class="clnumber">3 <b>otherwise </b>a set with members drawn from the set above, each being present or
absent depending on whether the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> (which is a list) contains an
equivalently named item.
<div class="note"><b>Note: </b>Although the <code>blockDefault</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of <a class="eltref" href="#element-schema"><schema></a> may include values other than <i>extension</i>, <i>restriction</i> or <i>substitution</i>, those values are ignored in the determination of <a class="propref" href="#e-exact">{disallowed substitutions}</a> for element declarations (they <em>are</em> used elsewhere).</div>
</div></div>
</td></tr><tr valign="top"><td><a class="propref" href="#e-final">{substitution group exclusions}</a></td><td>As for <a class="propref" href="#e-exact">{disallowed substitutions}</a> above, but using the
<code>final</code> and <code>finalDefault</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> in place of the
<code>block</code> and <code>blockDefault</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> and with the
relevant set being <code>{</code><i>extension</i>, <i>restriction</i><code>}</code>.</td></tr><tr valign="top"><td><a class="propref" href="#e-abstract">{abstract}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>abstract</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, if present, otherwise <i>false</i>.</td></tr><tr valign="top"><td><a class="propref" href="#e-annotation">{annotation}</a></td><td>The annotation corresponding to the <a class="eltref" href="#element-annotation"><annotation></a> element information item in the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if present, otherwise <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</td></tr></tbody></table></td></tr></tbody></table></div>
<div class="reprdep">otherwise if the <a class="eltref" href="#element-element"><element></a> element information item has
<a class="eltref" href="#element-complexType"><complexType></a> or <a class="eltref" href="#element-group"><group></a> as an ancestor and the
<code>ref</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> is absent, the corresponding schema components
are as follows (unless <code>minOccurs=maxOccurs=0</code>, in which case the item
corresponds to no component at all):</div>
<div class="reprcomp"><table class="reprcomp"><thead><tr><th><a href="#Particle_details">Particle</a><strong> Schema Component</strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Representation</th></tr></thead><tbody valign="top"><tr valign="top"><td><a class="propref" href="#p-min_occurs">{min occurs}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>minOccurs</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, if present, otherwise <code>1</code>.</td></tr><tr valign="top"><td><a class="propref" href="#p-max_occurs">{max occurs}</a></td><td><i>unbounded</i>, if the <code>maxOccurs</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> equals <i>unbounded</i>, otherwise the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>maxOccurs</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, if present, otherwise <code>1</code>.</td></tr><tr valign="top"><td><a class="propref" href="#term">{term}</a></td><td>A (local) element declaration as given below.</td></tr></tbody></table></td></tr></tbody></table></div>
<div class="reprdep">
An element declaration as in the first case above, with the exception of its <a class="propref" href="#e-target_namespace">{target namespace}</a> and <a class="propref" href="#e-scope">{scope}</a> properties, which are as below:</div>
<div class="reprcomp"><table class="reprcomp"><thead><tr><th><a href="#Element_Declaration_details">Element Declaration</a><strong> Schema Component</strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Representation</th></tr></thead><tbody valign="top"><tr valign="top"><td><a class="propref" href="#e-target_namespace">{target namespace}</a></td><td>If <code>form</code> is present and its
<a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> is <code>qualified</code>, or if <code>form</code> is absent and the
<a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of <code>elementFormDefault</code> on the <a class="eltref" href="#element-schema"><schema></a>
ancestor is <code>qualified</code>, then the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the
<code>targetNamespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of the parent <a class="eltref" href="#element-schema"><schema></a>
element information item, or <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> if there
is none, otherwise <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</td></tr><tr valign="top"><td><a class="propref" href="#e-scope">{scope}</a></td><td>If the <a class="eltref" href="#element-element"><element></a> element information item
has <a class="eltref" href="#element-complexType"><complexType></a> as an ancestor, the complex definition
corresponding to that item, otherwise (the <a class="eltref" href="#element-element"><element></a> element
information item is within a named <a class="eltref" href="#element-group"><group></a> definition), <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</td></tr></tbody></table></td></tr></tbody></table></div>
<div class="reprdep">otherwise (the <a class="eltref" href="#element-element"><element></a> element information item has
<a class="eltref" href="#element-complexType"><complexType></a> or <a class="eltref" href="#element-group"><group></a> as an ancestor and the
<code>ref</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> is present), the corresponding schema component is as
follows (unless <code>minOccurs=maxOccurs=0</code>, in which case the item
corresponds to no component at all):</div>
<div class="reprcomp"><table class="reprcomp"><thead><tr><th><a href="#Particle_details">Particle</a><strong> Schema Component</strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Representation</th></tr></thead><tbody valign="top"><tr valign="top"><td><a class="propref" href="#p-min_occurs">{min occurs}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>minOccurs</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, if present, otherwise <code>1</code>.</td></tr><tr valign="top"><td><a class="propref" href="#p-max_occurs">{max occurs}</a></td><td><i>unbounded</i>, if the <code>maxOccurs</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> equals <i>unbounded</i>, otherwise the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>maxOccurs</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, if present, otherwise <code>1</code>.</td></tr><tr valign="top"><td><a class="propref" href="#term">{term}</a></td><td>The (top-level) element declaration <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to by the
<a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>ref</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>.</td></tr></tbody></table></td></tr></tbody></table></div>
</div></div><p><a class="eltref" href="#element-element"><element></a> corresponds to an element declaration, and allows
the type definition of that declaration to be specified either by reference or
by explicit inclusion.</p><p><a class="eltref" href="#element-element"><element></a>s within <a class="eltref" href="#element-schema"><schema></a> produce
<i>global</i> element declarations; <a class="eltref" href="#element-element"><element></a>s within <a class="eltref" href="#element-group"><group></a> or <a class="eltref" href="#element-complexType"><complexType></a> produce either particles which contain <i>global</i> element declarations (if there's a <code>ref</code> attribute) or local declarations (otherwise). For complete declarations, top-level or local, the <code>type</code> attribute is used when the declaration can use a
built-in or pre-declared type definition. Otherwise an
anonymous <a class="eltref" href="#element-simpleType"><simpleType></a> or <a class="eltref" href="#element-complexType"><complexType></a> is provided inline.</p><p>Element information items <a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a> by a top-level declaration must be qualified with the
<a class="propref" href="#e-target_namespace">{target namespace}</a> of that declaration (if this is <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>, the item must be unqualified). Control over whether element information items <a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a> by a local declaration must be similarly qualified or not
is provided by the <code>form</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, whose default is provided
by the <code>elementFormDefault</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> on the enclosing <a class="eltref" href="#element-schema"><schema></a>, via its determination of <a class="propref" href="#e-target_namespace">{target namespace}</a>.</p><p>As noted above the names for top-level element declarations are in a separate
<a class="termref" href="#key-symbolSpace"><span class="arrow">·</span>symbol space<span class="arrow">·</span></a> from the symbol spaces for
the names of type definitions, so there can (but need
not be) a simple or complex type definition with the same name as a
top-level element. As with attribute names, the names of locally-scoped
element declarations with no <a class="propref" href="#e-target_namespace">{target namespace}</a> reside in symbol spaces local to the type definition which contains
them.</p><p>Note that the above allows for two levels of defaulting for unspecified
type definitions. An <a class="eltref" href="#element-element"><element></a> with no referenced or included type definition will
correspond to an element declaration which has the same type definition as the
head of its substitution group if it identifies one, otherwise the <a class="termref" href="#key-urType"><span class="arrow">·</span>ur-type definition<span class="arrow">·</span></a>. This has the important consequence that the minimum valid element declaration, that is, one with only a <code>name</code> attribute and no contents, is also (nearly) the most general, validating any combination of text and element content and allowing any attributes, and providing for recursive validation where possible.</p><p>See below at <a href="#declare-key">XML Representation of Identity-constraint Definition Schema Components (§3.11.2)</a> for <a class="eltref" href="#element-key"><key></a>, <a class="eltref" href="#element-unique"><unique></a> and <a class="eltref" href="#element-keyref"><keyref></a>.</p><div class="exampleOuter"><div class="exampleHeader">Example</div><div class="exampleInner"><pre><xs:element name="unconstrained"/>
<xs:element name="emptyElt">
<xs:complexType>
<xs:attribute ...>. . .</xs:attribute>
</xs:complexType>
</xs:element>
<xs:element name="contextOne">
<xs:complexType>
<xs:sequence>
<xs:element name="myLocalElement" type="myFirstType"/>
<xs:element ref="globalElement"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="contextTwo">
<xs:complexType>
<xs:sequence>
<xs:element name="myLocalElement" type="mySecondType"/>
<xs:element ref="globalElement"/>
</xs:sequence>
</xs:complexType>
</xs:element></pre></div><div class="exampleWrapper">The first example above declares an element whose type, by default, is the
<a class="termref" href="#key-urType"><span class="arrow">·</span>ur-type definition<span class="arrow">·</span></a>. The second uses an embedded anonymous complex
type definition.<p/>The last two examples illustrate the use of local element declarations. Instances of <code>myLocalElement</code> within
<code>contextOne</code> will be constrained by <code>myFirstType</code>,
while those within <code>contextTwo</code> will be constrained by
<code>mySecondType</code>. </div></div><div class="note"><b>Note: </b>The possibility that differing attribute declarations and/or content models
would apply to elements with the same name in different contexts is an
extension beyond the expressive power of a DTD in XML 1.0.</div><div class="exampleOuter"><div class="exampleHeader">Example</div><div class="exampleInner"><pre> <xs:complexType name="facet">
<xs:complexContent>
<xs:extension base="xs:annotated">
<xs:attribute name="value" use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="facet" type="xs:facet" abstract="true"/>
<xs:element name="encoding" substitutionGroup="xs:facet">
<xs:complexType>
<xs:complexContent>
<xs:restriction base="xs:facet">
<xs:sequence>
<xs:element ref="annotation" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="value" type="xs:encodings"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
</xs:element>
<xs:element name="period" substitutionGroup="xs:facet">
<xs:complexType>
<xs:complexContent>
<xs:restriction base="xs:facet">
<xs:sequence>
<xs:element ref="annotation" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="value" type="xs:duration"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
</xs:element>
<xs:complexType name="datatype">
<xs:sequence>
<xs:element ref="facet" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="name" type="xs:NCName" use="optional"/>
. . .
</xs:complexType>
</pre></div><div class="exampleWrapper">An example from a previous version of the schema for datatypes. The
<code>facet</code> type is defined
and the <code>facet</code> element is declared to use it. The <code>facet</code> element is abstract -- it's
<em>only</em> defined to stand as the head for a substitution group. Two further
elements are declared, each a member of the <code>facet</code> substitution group. Finally a type is defined which refers to <code>facet</code>, thereby
allowing <em>either</em> <code>period</code> or <code>encoding</code> (or
any other member of the group).</div></div></div><div class="div3">
<h4><a id="d0e4233" name="d0e4233"/>3.3.3 Constraints on XML Representations of Element Declarations</h4><div class="constraintnote"><a name="src-element" id="src-element"/><b>Schema Representation Constraint: Element Declaration Representation OK</b><br/><div class="constraint">In addition to the conditions imposed on <a class="eltref" href="#element-element"><element></a> element
information items by the schema for schemas:
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 <code>default</code> and <code>fixed</code> must not both be present.</div><div class="clnumber">2 If the item's parent is not <a class="eltref" href="#element-schema"><schema></a>, then
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.1 One of <code>ref</code> or <code>name</code> must be present, but not both.</div><div class="clnumber">2.2 If <code>ref</code> is present, then all of <a class="eltref" href="#element-complexType"><complexType></a>,
<a class="eltref" href="#element-simpleType"><simpleType></a>, <a class="eltref" href="#element-key"><key></a>, <a class="eltref" href="#element-keyref"><keyref></a>,
<a class="eltref" href="#element-unique"><unique></a>, <code>nillable</code>, <code>default</code>,
<code>fixed</code>, <code>form</code>, <code>block</code> and <code>type</code> must be absent,
i.e. only <code>minOccurs</code>, <code>maxOccurs</code>, <code>id</code> are
allowed in addition to <code>ref</code>, along with <a class="eltref" href="#element-annotation"><annotation></a>.</div></div>
</div><div class="clnumber">3 <code>type</code> and either <a class="eltref" href="#element-simpleType"><simpleType></a> or <a class="eltref" href="#element-complexType"><complexType></a> are mutually exclusive.</div><div class="clnumber">4 The corresponding particle and/or element declarations must satisfy the conditions set
out in <a href="#coss-element">Constraints on Element Declaration Schema Components (§3.3.6)</a> and <a href="#coss-particle">Constraints on Particle Schema Components (§3.9.6)</a>.</div></div>
</div></div></div><div class="div3">
<h4><a id="d0e4333" name="d0e4333"/>3.3.4 Element Declaration Validation Rules</h4><div class="constraintnote"><a name="cvc-elt" id="cvc-elt"/><b>Validation Rule: Element Locally Valid (Element)</b><br/><div class="constraint">For an element information item to be locally <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to an
element declaration
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1<a name="c-ea" id="c-ea"> </a>The declaration must not be <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</div><div class="clnumber">2 Its
<a class="propref" href="#e-abstract">{abstract}</a> must be <i>false</i>.</div><div class="clnumber">3 The appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">3.1 <b>If </b><a class="propref" href="#nillable">{nillable}</a> is <i>false</i>, <b>then </b>there must be no attribute information item among the element
information item's <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> whose <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[namespace name]</a> is identical to <code>http://www.w3.org/2001/XMLSchema-instance</code> and whose <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[local name]</a> is <code>nil</code>.</div><div class="clnumber">3.2<a name="c-nl" id="c-nl"> </a><b>If </b><a class="propref" href="#nillable">{nillable}</a> is <i>true</i> and there is such an attribute
information item and its <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> is <code>true</code>
, <b>then </b>
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">3.2.1 The element information item must have no character or element information item
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>.</div><div class="clnumber">3.2.2 There must be no <i>fixed</i> <a class="propref" href="#e-value_constraint">{value constraint}</a>.</div></div></div></div></div><div class="clnumber">4 If there is an attribute information item among the element
information item's <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> whose <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[namespace name]</a> is identical to <code>http://www.w3.org/2001/XMLSchema-instance</code> and whose <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[local name]</a> is <code>type</code>, then
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">4.1 The <a class="termref" href="#key-nv"><span class="arrow">·</span>normalized value<span class="arrow">·</span></a> of that attribute information item must be
<a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to the built-in <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#QName">QName</a> simple type, as defined by <a href="#cvc-simple-type">String Valid (§3.14.4)</a>;</div><div class="clnumber">4.2 The <a class="termref" href="#q-local"><span class="arrow">·</span>local name<span class="arrow">·</span></a> and <a class="termref" href="#q-uri"><span class="arrow">·</span>namespace name<span class="arrow">·</span></a> (as defined in <a href="#src-qname">QName Interpretation (§3.15.3)</a>), of the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of that attribute information item must resolve to a type definition, as defined in <a href="#cvc-resolve-instance">QName resolution (Instance) (§3.15.4)</a> -- <span class="termdef"><a id="key-ltd" name="key-ltd">[Definition:]  </a>call this type definition the <b>local type definition</b></span>;</div><div class="clnumber">4.3 The <a class="termref" href="#key-ltd"><span class="arrow">·</span>local type definition<span class="arrow">·</span></a> must be
validly derived from the <a class="propref" href="#type_definition">{type definition}</a> given the
union of the <a class="propref" href="#e-exact">{disallowed substitutions}</a> and the <a class="propref" href="#type_definition">{type definition}</a>'s <a class="propref" href="#ct-exact">{prohibited substitutions}</a>, as defined in <a href="#cos-ct-derived-ok">Type Derivation OK (Complex) (§3.4.6)</a> (if it is a complex type definition), or given <a class="propref" href="#e-exact">{disallowed substitutions}</a> as defined in <a href="#cos-st-derived-ok">Type Derivation OK (Simple) (§3.14.6)</a> (if it is a simple type definition).</div></div>
<span class="termdef"><a id="key-atd" name="key-atd">[Definition:]  </a>The phrase
<b>actual type definition</b> occurs below. If the above three clauses are satisfied, this
should be understood as referring to the <a class="termref" href="#key-ltd"><span class="arrow">·</span>local type
definition<span class="arrow">·</span></a>, otherwise to the <a class="propref" href="#type_definition">{type definition}</a></span>.
</div><div class="clnumber">5 The appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">5.1 <b>If </b>the declaration has a <a class="propref" href="#e-value_constraint">{value constraint}</a>, the item has neither element nor character <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> and clause <a href="#c-nl">3.2</a> has not applied, <b>then </b>
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">5.1.1 If the <a class="termref" href="#key-atd"><span class="arrow">·</span>actual type definition<span class="arrow">·</span></a> is a <a class="termref" href="#key-ltd"><span class="arrow">·</span>local type
definition<span class="arrow">·</span></a> then the <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#dt-canonical-representation">canonical lexical representation</a> of the <a class="propref" href="#e-value_constraint">{value constraint}</a> value must
be a valid default for the <a class="termref" href="#key-atd"><span class="arrow">·</span>actual
type definition<span class="arrow">·</span></a> as defined in <a href="#cos-valid-default">Element Default Valid (Immediate) (§3.3.6)</a>.
</div><div class="clnumber">5.1.2 The element information item with the <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#dt-canonical-representation">canonical lexical representation</a> of the <a class="propref" href="#e-value_constraint">{value constraint}</a> value used as its <a class="termref" href="#key-nv"><span class="arrow">·</span>normalized value<span class="arrow">·</span></a>
must be <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to the <a class="termref" href="#key-atd"><span class="arrow">·</span>actual type definition<span class="arrow">·</span></a> as defined by <a href="#cvc-type">Element Locally Valid (Type) (§3.3.4)</a>.</div></div>
</div><div class="clnumber">5.2 <b>If </b>the declaration has no <a class="propref" href="#e-value_constraint">{value constraint}</a> or the item has either element or character <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> or clause <a href="#c-nl">3.2</a> has applied, <b>then </b><b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">5.2.1 The element information item
must be <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to the <a class="termref" href="#key-atd"><span class="arrow">·</span>actual type definition<span class="arrow">·</span></a> as defined by <a href="#cvc-type">Element Locally Valid (Type) (§3.3.4)</a>.</div><div class="clnumber">5.2.2 If there is a <i>fixed</i> <a class="propref" href="#e-value_constraint">{value constraint}</a> and
clause <a href="#c-nl">3.2</a> has not applied,
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">5.2.2.1 The element information item must have no element information
item <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>.</div><div class="clnumber">5.2.2.2 The appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">5.2.2.2.1 <b>If </b>the <a class="propref" href="#content_type">{content type}</a> of the <a class="termref" href="#key-atd"><span class="arrow">·</span>actual type definition<span class="arrow">·</span></a> is <i>mixed</i>, <b>then </b>the <a class="termref" href="#key-iv"><span class="arrow">·</span>initial value<span class="arrow">·</span></a>
of the item must match the <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#dt-canonical-representation">canonical lexical representation</a> of the <a class="propref" href="#e-value_constraint">{value constraint}</a> value.</div><div class="clnumber">5.2.2.2.2 <b>If </b>the <a class="propref" href="#content_type">{content type}</a> of the <a class="termref" href="#key-atd"><span class="arrow">·</span>actual type definition<span class="arrow">·</span></a> is a simple type definition, <b>then </b>the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the item must match the <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#dt-canonical-representation">canonical lexical representation</a> of the <a class="propref" href="#e-value_constraint">{value constraint}</a> value.</div></div></div></div>
</div></div></div></div></div><div class="clnumber">6 The element information item must be <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to
each of the <a class="propref" href="#identity-constraint_definitions">{identity-constraint definitions}</a> as per <a href="#cvc-identity-constraint">Identity-constraint Satisfied (§3.11.4)</a>.</div><div class="clnumber">7 If the element information item is the <a class="termref" href="#key-vr"><span class="arrow">·</span>validation root<span class="arrow">·</span></a>, it must be <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> per <a href="#cvc-id">Validation Root Valid (ID/IDREF) (§3.3.4)</a>.</div></div>
</div></div><div class="constraintnote"><a name="cvc-type" id="cvc-type"/><b>Validation Rule: Element Locally Valid (Type)</b><br/><div class="constraint">For an element information item to be locally <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to a type definition
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1<a name="c-ct" id="c-ct"> </a>The type definition must not be <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>;</div><div class="clnumber">2
It must not have
<a class="propref" href="#ct-abstract">{abstract}</a> with value <i>true</i>.</div><div class="clnumber">3 The appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">3.1 <b>If </b>the type definition is a simple type
definition, <b>then </b>
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">3.1.1 The element information item's <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> must be empty,
excepting those whose <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[namespace name]</a> is identical to <code>http://www.w3.org/2001/XMLSchema-instance</code> and whose <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[local name]</a> is one of <code>type</code>, <code>nil</code>, <code>schemaLocation</code> or <code>noNamespaceSchemaLocation</code>.</div><div class="clnumber">3.1.2 The element information item must have no element information item <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>.</div><div class="clnumber">3.1.3<a name="c-sv1" id="c-sv1"> </a>If clause <a href="#c-nl">3.2</a> of <a href="#cvc-elt">Element Locally Valid (Element) (§3.3.4)</a> did not apply, then the <a class="termref" href="#key-nv"><span class="arrow">·</span>normalized value<span class="arrow">·</span></a> must be <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to the type definition as defined by <a href="#cvc-simple-type">String Valid (§3.14.4)</a>.</div></div>
</div><div class="clnumber">3.2 <b>If </b>the type definition is a complex type definition, <b>then </b>the element information item must be <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to the type definition as per <a href="#cvc-complex-type">Element Locally Valid (Complex Type) (§3.4.4)</a>;</div></div></div></div>
</div></div><div class="constraintnote"><a name="cvc-id" id="cvc-id"/><b>Validation Rule: Validation Root Valid (ID/IDREF)</b><br/><div class="constraint">For an element information item which is the <a class="termref" href="#key-vr"><span class="arrow">·</span>validation root<span class="arrow">·</span></a> to be <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a>
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 There must be no <b>ID/IDREF binding</b> in the item's
<a class="propref" href="#e-ii_table">[ID/IDREF table]</a> whose <a class="propref" href="#iib-binding">[binding]</a> is the
empty set.</div><div class="clnumber">2<a name="c-uba" id="c-uba"> </a>There must be no <b>ID/IDREF binding</b> in the item's <a class="propref" href="#e-ii_table">[ID/IDREF table]</a> whose <a class="propref" href="#iib-binding">[binding]</a> has more
than one member.</div></div>
<p/>See <a href="#sic-id">ID/IDREF Table (§3.15.5)</a> for the definition of <b>ID/IDREF binding</b>.<div class="note"><b>Note: </b>The first clause above applies when there is a reference to an
undefined ID. The second applies when there is a multiply-defined ID. They
are separated out to ensure that distinct error codes (see <a href="#outcomes">Outcome Tabulations (normative) (§C)</a>) are associated with these two cases.</div><div class="note"><b>Note: </b>Although this rule applies at the <a class="termref" href="#key-vr"><span class="arrow">·</span>validation
root<span class="arrow">·</span></a>, in practice processors, particularly streaming processors, may
wish to detect and signal the clause <a href="#c-uba">2</a> case as it arises.</div><div class="note"><b>Note: </b>This reconstruction of <a href="#ref-xml">[XML 1.0 (Second Edition)]</a>'s <code>ID/IDREF</code>
functionality is imperfect in that if the <a class="termref" href="#key-vr"><span class="arrow">·</span>validation
root<span class="arrow">·</span></a> is not the document element of an XML document, the results will
not necessarily be the same as those a validating parser would give were the
document to have a DTD with equivalent declarations.</div></div></div><div class="constraintnote"><a name="cvc-assess-elt" id="cvc-assess-elt"/><b>Validation Rule: Schema-Validity Assessment (Element)</b><br/><div class="constraint">The schema-validity assessment of an element information item depends
on its <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> and the <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> of its element information item
children and associated attribute information items, if any.<p/>So for an element information item's schema-validity to be assessed
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1<a name="c-xd" id="c-xd"> </a><b>One</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1.1<a name="c-ed" id="c-ed"> </a><b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1.1.1 A non-<a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> element declaration
must be known for it, because<b>one</b> of the following is true<div class="constraintlist"><div class="clnumber">1.1.1.1 A declaration was stipulated by the processor (see <a href="#validation_outcome">Assessing Schema-Validity (§5.2)</a>).</div><div class="clnumber">1.1.1.2 A declaration has been established as its <a class="termref" href="#key-dd"><span class="arrow">·</span>context-determined declaration<span class="arrow">·</span></a>.</div><div class="clnumber">1.1.1.3 <b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1.1.1.3.1 Its <a class="termref" href="#key-dd"><span class="arrow">·</span>context-determined declaration<span class="arrow">·</span></a> is
not <i>skip</i>.</div><div class="clnumber">1.1.1.3.2 Its <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[local name]</a> and <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[namespace name]</a> resolve to an element declaration as defined by <a href="#cvc-resolve-instance">QName resolution (Instance) (§3.15.4)</a>.</div></div></div></div></div><div class="clnumber">1.1.2 Its <a class="termref" href="#key-vn"><span class="arrow">·</span>validity<span class="arrow">·</span></a> with respect to that
declaration must have been evaluated as per <a href="#cvc-elt">Element Locally Valid (Element) (§3.3.4)</a>.</div><div class="clnumber">1.1.3 If that evaluation involved the evaluation of <a href="#cvc-type">Element Locally Valid (Type) (§3.3.4)</a>, clause <a href="#c-ct">1</a> thereof must be satisfied.</div></div></div><div class="clnumber">1.2<a name="c-td" id="c-td"> </a><b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1.2.1 A non-<a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> type definition is known for
it because
<b>one</b> of the following is true<div class="constraintlist"><div class="clnumber">1.2.1.1 A type definition was stipulated by the processor
(see <a href="#validation_outcome">Assessing Schema-Validity (§5.2)</a>).</div><div class="clnumber">1.2.1.2 <b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1.2.1.2.1 There is an attribute information item among the element
information item's <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> whose <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[namespace name]</a> is identical to <code>http://www.w3.org/2001/XMLSchema-instance</code> and whose <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[local name]</a> is <code>type</code>.</div><div class="clnumber">1.2.1.2.2 The <a class="termref" href="#key-nv"><span class="arrow">·</span>normalized value<span class="arrow">·</span></a> of that attribute information item is
<a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to the built-in <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#QName">QName</a> simple type, as defined by <a href="#cvc-simple-type">String Valid (§3.14.4)</a>.</div><div class="clnumber">1.2.1.2.3 The <a class="termref" href="#q-local"><span class="arrow">·</span>local name<span class="arrow">·</span></a> and <a class="termref" href="#q-uri"><span class="arrow">·</span>namespace name<span class="arrow">·</span></a> (as defined in <a href="#src-qname">QName Interpretation (§3.15.3)</a>), of the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of that attribute information item resolve to a type definition, as defined in <a href="#cvc-resolve-instance">QName resolution (Instance) (§3.15.4)</a> -- <span class="termdef"><a id="key-ltd1" name="key-ltd1">[Definition:]  </a>call this type definition the <b>local type definition</b></span>.</div><div class="clnumber">1.2.1.2.4 If there is also a processor-stipulated type definition, the <a class="termref" href="#key-ltd1"><span class="arrow">·</span>local type definition<span class="arrow">·</span></a> must be
validly derived from that type definition given its <a class="propref" href="#ct-exact">{prohibited substitutions}</a>,
as defined in <a href="#cos-ct-derived-ok">Type Derivation OK (Complex) (§3.4.6)</a> (if it is a complex type
definition), or given the empty set, as defined in <a href="#cos-st-derived-ok">Type Derivation OK (Simple) (§3.14.6)</a> (if it is a simple type definition).</div></div></div></div>
</div><div class="clnumber">1.2.2 The element information item's <a class="termref" href="#key-vn"><span class="arrow">·</span>validity<span class="arrow">·</span></a> with respect to the <a class="termref" href="#key-ltd1"><span class="arrow">·</span>local type definition<span class="arrow">·</span></a> (if present and validly derived)
or the processor-stipulated type definition (if no <a class="termref" href="#key-ltd1"><span class="arrow">·</span>local
type definition<span class="arrow">·</span></a> is present) has been evaluated as per <a href="#cvc-type">Element Locally Valid (Type) (§3.3.4)</a>.</div></div></div></div>
</div><div class="clnumber">2 The schema-validity of all the element information items among its
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> has been assessed as per <a href="#cvc-assess-elt">Schema-Validity Assessment (Element) (§3.3.4)</a>, and the
schema-validity of all the attribute information items among its
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> has been assessed as per <a href="#cvc-assess-attr">Schema-Validity Assessment (Attribute) (§3.2.4)</a>.</div></div>
<p/><span class="termdef"><a id="key-sva" name="key-sva">[Definition:]  </a>If either case of
clause <a href="#c-xd">1</a> above holds, the element information item has been <b>strictly assessed</b></span>.<p/>If the item cannot be <a class="termref" href="#key-sva"><span class="arrow">·</span>strictly
assessed<span class="arrow">·</span></a>, because neither clause <a href="#c-ed">1.1</a> nor clause <a href="#c-td">1.2</a> above are satisfied,
<span class="termdef"><a id="key-lva" name="key-lva">[Definition:]  </a>an element information item's
schema validity may be <b>laxly assessed</b> if its <a class="termref" href="#key-dd"><span class="arrow">·</span>context-determined declaration<span class="arrow">·</span></a> is not <i>skip</i> by <a class="termref" href="#key-vn"><span class="arrow">·</span>validating<span class="arrow">·</span></a> with respect to the <a class="termref" href="#ur-type-itself"><span class="arrow">·</span>ur-type definition<span class="arrow">·</span></a> as per <a href="#cvc-type">Element Locally Valid (Type) (§3.3.4)</a></span>.<div class="note"><b>Note: </b>In general if clause <a href="#c-ed">1.1</a> above holds
clause <a href="#c-td">1.2</a> does not, and vice versa. When an
<code>xsi:type</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> is involved, however, clause <a href="#c-td">1.2</a> takes precedence,
as is made clear in <a href="#cvc-elt">Element Locally Valid (Element) (§3.3.4)</a>.</div></div></div><div class="note"><b>Note: </b>The <a class="propref" href="#e-name">{name}</a> and <a class="propref" href="#e-target_namespace">{target namespace}</a> properties are not
mentioned above because they are checked during particle <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a>, as per
<a href="#cvc-particle">Element Sequence Locally Valid (Particle) (§3.9.4)</a>.</div></div><div class="div3">
<h4><a id="d0e5070" name="d0e5070"/>3.3.5 Element Declaration Information Set Contributions</h4><div class="constraintnote"><a name="sic-e-outcome" id="sic-e-outcome"/><b>Schema Information Set Contribution: Assessment Outcome (Element)</b><br/><div class="constraint">If the schema-validity of an element information item has been assessed
as per <a href="#cvc-assess-elt">Schema-Validity Assessment (Element) (§3.3.4)</a>, then in the <a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a> it has properties as follows:<div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> element information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="e-validation_context" id="e-validation_context"><span class="propdef">[validation context]</span></a></dt><dd>The nearest ancestor element information
item with a <a class="propref" href="#e-schema_information">[schema information]</a> property (or this element item itself if it has such a property).</dd>
<dt><a name="e-validity" id="e-validity"><span class="propdef">[validity]</span></a></dt><dd>
The appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">1 <b>If </b>it was <a class="termref" href="#key-sva"><span class="arrow">·</span>strictly
assessed<span class="arrow">·</span></a>, <b>then </b>
the appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">1.1 <b>If </b>
<b>all</b> of the following are true<div class="constraintlist"><div class="clnumber">1.1.1 <div class="constraintlist"><div class="clnumber">1.1.1.1 clause <a href="#c-ed">1.1</a> of <a href="#cvc-assess-elt">Schema-Validity Assessment (Element) (§3.3.4)</a>
applied and the item was
<a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> as defined by <a href="#cvc-elt">Element Locally Valid (Element) (§3.3.4)</a>;</div><div class="clnumber">1.1.1.2 clause <a href="#c-td">1.2</a> of <a href="#cvc-assess-elt">Schema-Validity Assessment (Element) (§3.3.4)</a>
applied and the item was
<a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> as defined by <a href="#cvc-type">Element Locally Valid (Type) (§3.3.4)</a>.</div></div></div><div class="clnumber">1.1.2 Neither its <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> nor its
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> contains an information item (element or attribute respectively) whose <span class="anonRef">[validity]</span> is <i>invalid</i>.</div><div class="clnumber">1.1.3 Neither its <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> nor its
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> contains an information item (element or attribute respectively) with a <a class="termref" href="#key-dd"><span class="arrow">·</span>context-determined declaration<span class="arrow">·</span></a> of
<i>mustFind</i> whose <span class="anonRef">[validity]</span>
is <i>notKnown</i>.</div></div>
, <b>then </b><i>valid</i>;</div><div class="clnumber">1.2 <b>otherwise </b><i>invalid.</i>.</div></div>
</div><div class="clnumber">2 <b>otherwise </b><i>notKnown</i>.</div></div>
</dd>
<dt><a name="e-validation_attempted" id="e-validation_attempted"><span class="propdef">[validation attempted]</span></a></dt><dd>
The appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">1 <b>If </b>it was <a class="termref" href="#key-sva"><span class="arrow">·</span>strictly assessed<span class="arrow">·</span></a> and neither its <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> nor its
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> contains an information item (element or attribute
respectively) whose <span class="anonRef">[validation attempted]</span> is not
<i>full</i>, <b>then </b><i>full</i>;</div><div class="clnumber">2 <b>If </b>it was not <a class="termref" href="#key-sva"><span class="arrow">·</span>strictly assessed<span class="arrow">·</span></a> and neither its <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> nor its
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> contains an information item (element or attribute
respectively) whose <span class="anonRef">[validation attempted]</span> is not
<i>none</i>, <b>then </b><i>none</i>;</div><div class="clnumber">3 <b>otherwise </b><i>partial</i>.</div></div></dd></dl></div></div></div></div><div class="constraintnote"><a name="sic-elt-error-code" id="sic-elt-error-code"/><b>Schema Information Set Contribution: Validation Failure (Element)</b><br/><div class="constraint">If the local <a class="termref" href="#key-vn"><span class="arrow">·</span>validity<span class="arrow">·</span></a>, as defined by
<a href="#cvc-elt">Element Locally Valid (Element) (§3.3.4)</a> above and/or <a href="#cvc-type">Element Locally Valid (Type) (§3.3.4)</a>
below, of an element information item has been assessed,
in the <a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a> the item has a
property:<div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> element information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="e-schema_error_code" id="e-schema_error_code"><span class="propdef">[schema error code]</span></a></dt><dd>
The appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">1 <b>If </b>the item is not <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a>, <b>then </b>a list. Applications wishing to provide
information as to the reason(s) for the <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> failure are encouraged to record one or more
error codes (see <a href="#outcomes">Outcome Tabulations (normative) (§C)</a>) herein.</div><div class="clnumber">2 <b>otherwise </b><a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</div></div>
</dd>
</dl></div></div></div></div><div class="constraintnote"><a name="sic-elt-decl" id="sic-elt-decl"/><b>Schema Information Set Contribution: Element Declaration</b><br/><div class="constraint">If an element information item is <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to an element
declaration as per <a href="#cvc-elt">Element Locally Valid (Element) (§3.3.4)</a> then in the <a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a>
the element
information item must, at processor option, have either:<div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> element information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="e-declaration" id="e-declaration"><span class="propdef">[element declaration]</span></a></dt><dd>
an <a class="termref" href="#key-iso"><span class="arrow">·</span>item isomorphic<span class="arrow">·</span></a> to the declaration component itself
</dd>
</dl></div></div>or<div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> element information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="e-nil" id="e-nil"><span class="propdef">[nil]</span></a></dt><dd><i>true</i> if clause <a href="#c-nl">3.2</a> of <a href="#cvc-elt">Element Locally Valid (Element) (§3.3.4)</a> above is satisfied,
otherwise <i>false</i>
</dd>
</dl></div></div></div></div><div class="constraintnote"><a name="sic-eltType" id="sic-eltType"/><b>Schema Information Set Contribution: Element Validated by Type</b><br/><div class="constraint">If an element information item is <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to a <a class="termref" href="#key-typeDefn"><span class="arrow">·</span>type definition<span class="arrow">·</span></a>
as per <a href="#cvc-type">Element Locally Valid (Type) (§3.3.4)</a>, in the <a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a> the item has a property:<div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> element information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="e-schema_normalized_value" id="e-schema_normalized_value"><span class="propdef">[schema normalized value]</span></a></dt><dd>
The appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">1 <b>If </b>clause <a href="#c-nl">3.2</a> of <a href="#cvc-elt">Element Locally Valid (Element) (§3.3.4)</a> and <a href="#sic-eltDefault">Element Default Value (§3.3.5)</a> above have
<em>not</em> applied and either the <a class="termref" href="#key-typeDefn"><span class="arrow">·</span>type definition<span class="arrow">·</span></a> is a simple type definition or its <a class="propref" href="#content_type">{content type}</a> is a simple type definition, <b>then </b>
the <a class="termref" href="#key-nv"><span class="arrow">·</span>normalized value<span class="arrow">·</span></a> of the item as <a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a>.</div><div class="clnumber">2 <b>otherwise </b><a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</div></div>
</dd>
</dl></div></div>Furthermore, the item has one of the following alternative sets of properties:<p/>Either<div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> element information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="e-type_definition" id="e-type_definition"><span class="propdef">[type definition]</span></a></dt><dd>An
<a class="termref" href="#key-iso"><span class="arrow">·</span>item isomorphic<span class="arrow">·</span></a> to the <a class="termref" href="#key-typeDefn"><span class="arrow">·</span>type definition<span class="arrow">·</span></a> component itself.</dd>
<dt><a name="e-member_type_definition" id="e-member_type_definition"><span class="propdef">[member type definition]</span></a></dt><dd>If
and only if that type definition is a
simple type definition with <a class="propref" href="#variety">{variety}</a> <i>union</i>, or
a complex type definition whose <a class="propref" href="#content_type">{content type}</a> is a
simple type
definition with <a class="propref" href="#variety">{variety}</a> <i>union</i>, then an
<a class="termref" href="#key-iso"><span class="arrow">·</span>item isomorphic<span class="arrow">·</span></a> to that member of the
union's <a class="propref" href="#st-member_type_definitions">{member type definitions}</a> which actually <a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a> the element item's <a class="termref" href="#key-nv"><span class="arrow">·</span>normalized value<span class="arrow">·</span></a>.</dd>
</dl></div></div>or<div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> element information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="e-type_definition_type" id="e-type_definition_type"><span class="propdef">[type definition type]</span></a></dt><dd>
<i>simple</i> or <i>complex</i>, depending on the <a class="termref" href="#key-typeDefn"><span class="arrow">·</span>type definition<span class="arrow">·</span></a>.</dd>
<dt><a name="e-type_definition_namespace" id="e-type_definition_namespace"><span class="propdef">[type definition namespace]</span></a></dt><dd>The <span class="anonRef">{target namespace}</span> of the <a class="termref" href="#key-typeDefn"><span class="arrow">·</span>type definition<span class="arrow">·</span></a>.</dd>
<dt><a name="e-type_definition_anonymous" id="e-type_definition_anonymous"><span class="propdef">[type definition anonymous]</span></a></dt><dd><i>true</i> if the <span class="anonRef">{name}</span> of the <a class="termref" href="#key-typeDefn"><span class="arrow">·</span>type definition<span class="arrow">·</span></a> is <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>, otherwise <i>false</i>.</dd>
<dt><a name="e-type_definition_name" id="e-type_definition_name"><span class="propdef">[type definition name]</span></a></dt><dd>The <span class="anonRef">{name}</span> of the <a class="termref" href="#key-typeDefn"><span class="arrow">·</span>type definition<span class="arrow">·</span></a>, if it is not <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>. If it is
<a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>, schema processors may, but need not,
provide a value unique to the definition.</dd>
</dl></div></div>If the <a class="termref" href="#key-typeDefn"><span class="arrow">·</span>type definition<span class="arrow">·</span></a> is a
simple type definition or its <a class="propref" href="#content_type">{content type}</a> is a
simple type definition, and that type
definition has <a class="propref" href="#variety">{variety}</a> <i>union</i>, then calling
<span class="termdef"><a id="key-amt" name="key-amt">[Definition:]  </a> that
member of the <a class="propref" href="#st-member_type_definitions">{member type definitions}</a> which actually
<a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a> the element item's <a class="termref" href="#key-nv"><span class="arrow">·</span>normalized value<span class="arrow">·</span></a> the
<b>actual member type definition</b></span>, there are three additional properties:<div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> element information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="e-member_type_definition_namespace" id="e-member_type_definition_namespace"><span class="propdef">[member type definition namespace]</span></a></dt><dd>The <a class="propref" href="#st-target_namespace">{target namespace}</a> of the <a class="termref" href="#key-amt"><span class="arrow">·</span>actual
member type definition<span class="arrow">·</span></a>.</dd>
<dt><a name="e-member_type_definition_anonymous" id="e-member_type_definition_anonymous"><span class="propdef">[member type definition anonymous]</span></a></dt><dd><i>true</i> if the <a class="propref" href="#st-name">{name}</a> of the <a class="termref" href="#key-amt"><span class="arrow">·</span>actual member type definition<span class="arrow">·</span></a> is <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>, otherwise <i>false</i>.</dd>
<dt><a name="e-member_type_definition_name" id="e-member_type_definition_name"><span class="propdef">[member type definition name]</span></a></dt><dd>The <a class="propref" href="#st-name">{name}</a> of the <a class="termref" href="#key-amt"><span class="arrow">·</span>actual member type definition<span class="arrow">·</span></a>, if it is not <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>. If it is
<a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>, schema processors may, but need not,
provide a value unique to the definition.</dd>
</dl></div></div>The first (<a class="termref" href="#key-iso"><span class="arrow">·</span>item isomorphic<span class="arrow">·</span></a>) alternative above is provided for applications such as query
processors which need access to the full range of details about an item's
<a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a>, for example the type hierarchy; the second, for lighter-weight
processors for whom representing the significant parts of the type hierarchy as
information items might be a significant burden.<p/>Also, if the declaration has a <a class="propref" href="#e-value_constraint">{value constraint}</a>, the item has a property:<div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> element information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="e-schema_default" id="e-schema_default"><span class="propdef">[schema default]</span></a></dt><dd>
The <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#dt-canonical-representation">canonical lexical representation</a> of
the declaration's <a class="propref" href="#e-value_constraint">{value constraint}</a> value.</dd>
</dl></div></div>Note that if an element is <a class="termref" href="#key-lva"><span class="arrow">·</span>laxly assessed<span class="arrow">·</span></a>, then the <a class="propref" href="#e-type_definition">[type definition]</a> and
<a class="propref" href="#e-member_type_definition">[member type definition]</a> properties, or their
alternatives, are based on the <a class="termref" href="#ur-type-itself"><span class="arrow">·</span>ur-type definition<span class="arrow">·</span></a>.</div></div><div class="constraintnote"><a name="sic-eltDefault" id="sic-eltDefault"/><b>Schema Information Set Contribution: Element Default Value</b><br/><div class="constraint">If the local <a class="termref" href="#key-vn"><span class="arrow">·</span>validity<span class="arrow">·</span></a>, as defined by <a href="#cvc-elt">Element Locally Valid (Element) (§3.3.4)</a>
above, of an element information item has been assessed,
in the <a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a> the item has a
property:<div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> element information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="e-schema_specified" id="e-schema_specified"><span class="propdef">[schema specified]</span></a></dt><dd>
The appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">1 <b>If </b>the item is <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to an element
declaration as per <a href="#cvc-elt">Element Locally Valid (Element) (§3.3.4)</a> and the <a class="propref" href="#e-value_constraint">{value constraint}</a> is present, but clause <a href="#c-nl">3.2</a>
of <a href="#cvc-elt">Element Locally Valid (Element) (§3.3.4)</a> above is not satisfied and the item has no element or character information item <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, <b>then </b>
<i>schema</i>. Furthermore, the
<a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a> has the <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#dt-canonical-representation">canonical lexical representation</a> of the <a class="propref" href="#e-value_constraint">{value constraint}</a> value as the
item's <a class="propref" href="#e-schema_normalized_value">[schema normalized value]</a>
property.</div><div class="clnumber">2 <b>otherwise </b><i>infoset</i>.</div></div></dd></dl></div></div></div></div></div><div class="div3">
<h4><a id="coss-element" name="coss-element"/>3.3.6 Constraints on Element Declaration Schema Components</h4><p>All element declarations (see <a href="#cElement_Declarations">Element Declarations (§3.3)</a>) must satisfy the following constraint.</p><div class="constraintnote"><a name="e-props-correct" id="e-props-correct"/><b>Schema Component Constraint: Element Declaration Properties Correct</b><br/><div class="constraint"><b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 The values of the properties of an element declaration must be as described in
the property tableau in
<a href="#Element_Declaration_details">The Element Declaration Schema Component (§3.3.1)</a>, modulo the impact of <a href="#conformance-missing">Missing Sub-components (§5.3)</a>.</div><div class="clnumber">2 If there is a <a class="propref" href="#e-value_constraint">{value constraint}</a>, the <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#dt-canonical-representation">canonical lexical representation</a> of its value must be
<a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to the <a class="propref" href="#type_definition">{type definition}</a> as defined in <a href="#cos-valid-default">Element Default Valid (Immediate) (§3.3.6)</a>.</div><div class="clnumber">3 If there is a non-<a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>
<a class="propref" href="#class_exemplar">{substitution group affiliation}</a>, then <a class="propref" href="#e-scope">{scope}</a> must be <i>global</i>.</div><div class="clnumber">4 If there is a <a class="propref" href="#class_exemplar">{substitution group affiliation}</a>, the <a class="propref" href="#type_definition">{type definition}</a> of the element declaration must
be validly derived from the <a class="propref" href="#type_definition">{type definition}</a> of the <a class="propref" href="#class_exemplar">{substitution group affiliation}</a>, given the value of the <a class="propref" href="#e-final">{substitution group exclusions}</a> of the <a class="propref" href="#class_exemplar">{substitution group affiliation}</a>, as defined in <a href="#cos-ct-derived-ok">Type Derivation OK (Complex) (§3.4.6)</a> (if the <a class="propref" href="#type_definition">{type definition}</a> is complex) or as defined in <a href="#cos-st-derived-ok">Type Derivation OK (Simple) (§3.14.6)</a> (if the <a class="propref" href="#type_definition">{type definition}</a> is simple).
</div><div class="clnumber">5 If the <a class="propref" href="#type_definition">{type definition}</a> or <a class="propref" href="#type_definition">{type definition}</a>'s <a class="propref" href="#content_type">{content type}</a> is or is derived from <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a> then there must not be a <a class="propref" href="#e-value_constraint">{value constraint}</a>.<div class="note"><b>Note: </b>The use of <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a> as a type
definition for elements goes beyond XML 1.0, and should be avoided if backwards
compatibility is desired.</div></div><div class="clnumber">6 Circular substitution groups are disallowed. That is, it
must not be possible to return to an element declaration by repeatedly following
the <a class="propref" href="#class_exemplar">{substitution group affiliation}</a> property.</div></div></div></div><p>The following constraints define relations appealed to elsewhere in this specification.</p><div class="constraintnote"><a name="cos-valid-default" id="cos-valid-default"/><b>Schema Component Constraint: Element Default Valid (Immediate)</b><br/><div class="constraint">For a string to be a valid default with respect to a type definition
the appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">1 <b>If </b>the type definition is a simple type definition, <b>then </b>the string must be
<a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to that definition as defined by <a href="#cvc-simple-type">String Valid (§3.14.4)</a>.</div><div class="clnumber">2 <b>If </b>the type definition is a complex type definition, <b>then </b>
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.1 its <a class="propref" href="#content_type">{content type}</a> must be a simple type definition
or <i>mixed</i>.</div><div class="clnumber">2.2 The appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">2.2.1 <b>If </b>the <a class="propref" href="#content_type">{content type}</a> is a simple type definition, <b>then </b>the string must be
<a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to that simple type definition as defined by <a href="#cvc-simple-type">String Valid (§3.14.4)</a>.</div><div class="clnumber">2.2.2 <b>If </b>the <a class="propref" href="#content_type">{content type}</a> is <i>mixed</i>, <b>then </b>the <a class="propref" href="#content_type">{content type}</a>'s particle must be <a class="termref" href="#cd-emptiable"><span class="arrow">·</span>emptiable<span class="arrow">·</span></a> as defined by <a href="#cos-group-emptiable">Particle Emptiable (§3.9.6)</a>.</div></div></div></div>
</div></div>
</div></div><div class="constraintnote"><a name="cos-equiv-derived-ok-rec" id="cos-equiv-derived-ok-rec"/><b>Schema Component Constraint: Substitution Group OK (Transitive)</b><br/><div class="constraint">For an element declaration (call it <b>D</b>) to be validly
substitutable for another element declaration (call it <b>C</b>)
subject to a blocking constraint (a subset of
{<i>substitution</i>, <i>extension</i>, <i>restriction</i>}, the value of
a <a class="propref" href="#e-exact">{disallowed substitutions}</a>)
<b>one</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 <b>D</b> and <b>C</b> are the same element declaration.</div><div class="clnumber">2 <b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.1 The blocking constraint does not contain <i>substitution</i>.</div><div class="clnumber">2.2 There is a chain of <a class="propref" href="#class_exemplar">{substitution group affiliation}</a>s from <b>D</b> to
<b>C</b>, that is, either <b>D</b>'s <a class="propref" href="#class_exemplar">{substitution group affiliation}</a> is
<b>C</b>, or <b>D</b>'s <a class="propref" href="#class_exemplar">{substitution group affiliation}</a>'s <a class="propref" href="#class_exemplar">{substitution group affiliation}</a> is <b>C</b>, or . . .</div><div class="clnumber">2.3 The set of all <a class="propref" href="#derivation_method">{derivation method}</a>s
involved in the derivation of <b>D</b>'s <a class="propref" href="#type_definition">{type definition}</a> from
<b>C</b>'s <a class="propref" href="#type_definition">{type definition}</a> does not intersect with the union
of the blocking constraint, <b>C</b>'s <a class="propref" href="#ct-exact">{prohibited substitutions}</a> (if <b>C</b>
is complex, otherwise the empty set) and the
<a class="propref" href="#ct-exact">{prohibited substitutions}</a> (respectively the empty set) of any intermediate <a class="propref" href="#type_definition">{type definition}</a>s
in the derivation of <b>D</b>'s <a class="propref" href="#type_definition">{type definition}</a> from
<b>C</b>'s <a class="propref" href="#type_definition">{type definition}</a>.</div></div></div></div>
</div></div><div class="constraintnote"><a name="cos-equiv-class" id="cos-equiv-class"/><b>Schema Component Constraint: Substitution Group</b><br/><div class="constraint"><span class="termdef"><a id="key-eq" name="key-eq">[Definition:]  </a>Every element
declaration (call this <b>HEAD</b>)
in the <a class="propref" href="#element_declarations">{element declarations}</a> of a schema defines a
<b>substitution group</b>, a subset of those <a class="propref" href="#element_declarations">{element declarations}</a>, as follows:</span><p/>Define <b>P</b>, the potential substitution group for <b>HEAD</b>, as follows:<div class="constraintlist"><div class="clnumber">1 The element declaration itself is in <b>P</b>;</div><div class="clnumber">2 <b>P</b> is closed with respect to <a class="propref" href="#class_exemplar">{substitution group affiliation}</a>, that
is, if any element declaration in the <a class="propref" href="#element_declarations">{element declarations}</a>
has a <a class="propref" href="#class_exemplar">{substitution group affiliation}</a> in <b>P</b>, then that element is also in <b>P</b> itself.</div></div><b>HEAD</b>'s actual <a class="termref" href="#key-eq"><span class="arrow">·</span>substitution
group<span class="arrow">·</span></a> is then the set consisting of each member of <b>P</b>
such that <b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 Its <a class="propref" href="#e-abstract">{abstract}</a> is <i>false</i>.</div><div class="clnumber">2 It is validly substitutable for <b>HEAD</b> subject to
<b>HEAD</b>'s <a class="propref" href="#e-exact">{disallowed substitutions}</a> as the
blocking constraint, as defined in <a href="#cos-equiv-derived-ok-rec">Substitution Group OK (Transitive) (§3.3.6)</a>.</div></div></div></div></div></div><div class="div2">
<h3 class="withToc"><span class="nav"><a class="nav" href="#cElement_Declarations"><img src="previous.jpg" alt="previous sub-section"/></a> <a class="nav" href="#cAttributeUse"><img src="next.jpg" alt="next sub-section"/></a></span><a id="Complex_Type_Definitions" name="Complex_Type_Definitions"/>3.4 Complex Type Definitions</h3><div class="localToc">        3.4.1 <a href="#Complex_Type_Definition_details">The Complex Type Definition Schema Component</a><br/>
        3.4.2 <a href="#declare-type">XML Representation of Complex Type Definitions</a><br/>
        3.4.3 <a href="#d0e7923">Constraints on XML Representations of Complex Type Definitions</a><br/>
        3.4.4 <a href="#formal-complex-type">Complex Type Definition Validation Rules</a><br/>
        3.4.5 <a href="#d0e8328">Complex Type Definition Information Set Contributions</a><br/>
        3.4.6 <a href="#coss-ct">Constraints on Complex Type Definition Schema Components</a><br/>
        3.4.7 <a href="#d0e9252">Built-in Complex Type Definition</a><br/>
</div><p>Complex Type Definitions provide for:</p><ul><li>Constraining element information items by providing <a href="#Attribute_Declaration">Attribute Declaration (§2.2.2.3)</a>s governing the appearance and content of
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a></li><li>Constraining element information item <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> to be empty,
or to conform to a specified element-only or mixed content model, or else
constraining the character information item <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> to conform to a
specified simple type definition.</li><li>Using the mechanisms of <a href="#Type_Derivation">Type Definition Hierarchy (§2.2.1.1)</a> to derive a complex type from another simple or complex type.</li><li>Specifying <a class="termref" href="#gloss-sic"><span class="arrow">·</span>post-schema-validation infoset contributions<span class="arrow">·</span></a> for elements. </li><li>Limiting the ability to derive additional types from a given complex type.</li><li>Controlling the permission to substitute, in an instance, elements of a derived
type for elements declared in a content model to be of a given complex type.</li></ul><div class="exampleOuter"><div class="exampleHeader">Example</div><div class="exampleInner"><pre><xs:complexType name="PurchaseOrderType">
<xs:sequence>
<xs:element name="shipTo" type="USAddress"/>
<xs:element name="billTo" type="USAddress"/>
<xs:element ref="comment" minOccurs="0"/>
<xs:element name="items" type="Items"/>
</xs:sequence>
<xs:attribute name="orderDate" type="xs:date"/>
</xs:complexType>
</pre></div><div class="exampleWrapper">The XML representation of a complex type definition.</div></div><div class="div3">
<h4><a id="Complex_Type_Definition_details" name="Complex_Type_Definition_details"/>3.4.1 The Complex Type Definition Schema Component</h4><p>A complex type definition schema component has the following
properties:</p><div class="schemaComp"><div class="compHeader"><span class="schemaComp">Schema Component</span>: <a href="#Complex_Type_Definition">Complex Type Definition</a></div><div class="compBody">
<dl class="props">
<dt><a name="ct-name" id="ct-name"><span class="propdef">{name}</span></a></dt><dd>
Optional. An NCName as defined by <a href="#ref-xml-namespaces">[XML-Namespaces]</a>.
</dd>
<dt><a name="ct-target_namespace" id="ct-target_namespace"><span class="propdef">{target namespace}</span></a></dt><dd>
Either <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> or a namespace name, as defined in <a href="#ref-xml-namespaces">[XML-Namespaces]</a>.
</dd>
<dt><a name="ct-base_type_definition" id="ct-base_type_definition"><span class="propdef">{base type definition}</span></a></dt><dd>
Either a simple type definition or a complex type definition.
</dd>
<dt><a name="derivation_method" id="derivation_method"><span class="propdef">{derivation method}</span></a></dt><dd>
Either <i>extension</i> or <i>restriction</i>.
</dd>
<dt><a name="ct-final" id="ct-final"><span class="propdef">{final}</span></a></dt><dd>
A subset of {<i>extension</i>, <i>restriction</i>}.
</dd>
<dt><a name="ct-abstract" id="ct-abstract"><span class="propdef">{abstract}</span></a></dt><dd>
A boolean
</dd>
<dt><a name="ct-attribute_declarations" id="ct-attribute_declarations"><span class="propdef">{attribute uses}</span></a></dt><dd>
A set of attribute uses.
</dd>
<dt><a name="ct-attribute_wildcard" id="ct-attribute_wildcard"><span class="propdef">{attribute wildcard}</span></a></dt><dd>
Optional. A wildcard.
</dd>
<dt><a name="content_type" id="content_type"><span class="propdef">{content type}</span></a></dt><dd>One of <i>empty</i>, a simple type definition or a pair
consisting of a <a class="termref" href="#key-contentModel"><span class="arrow">·</span>content model<span class="arrow">·</span></a> (I.e. a <a href="#Particle">Particle (§2.2.3.2)</a>) and one of <i>mixed</i>, <i>element-only</i>.
</dd>
<dt><a name="ct-exact" id="ct-exact"><span class="propdef">{prohibited substitutions}</span></a></dt><dd>
A subset of {<i>extension</i>, <i>restriction</i>}.
</dd>
<dt><a name="ct-annotations" id="ct-annotations"><span class="propdef">{annotations}</span></a></dt><dd>A set of annotations.</dd>
</dl>
</div></div><p>Complex types definitions are identified by their <a class="propref" href="#ct-name">{name}</a> and <a class="propref" href="#ct-target_namespace">{target namespace}</a>. Except
for anonymous complex type definitions (those with no <a class="propref" href="#ct-name">{name}</a>), since
type definitions (i.e. both simple and complex type definitions taken together) must be uniquely identified within an <a class="termref" href="#key-schema"><span class="arrow">·</span>XML
Schema<span class="arrow">·</span></a>, no complex type definition can have the same name as another
simple or complex type definition. Complex type <a class="propref" href="#ct-name">{name}</a>s and <a class="propref" href="#ct-target_namespace">{target namespace}</a>s
are provided for reference from
instances (see <a href="#xsi_type">xsi:type (§2.6.1)</a>), and for use in the XML
representation of schema components
(specifically in <a class="eltref" href="#element-element"><element></a>). See <a href="#composition-schemaImport">References to schema components across namespaces (§4.2.3)</a> for the use of component
identifiers when importing one schema into another.</p><div class="note"><b>Note: </b>The <a class="propref" href="#ct-name">{name}</a> of a complex type is not <em>ipso
facto</em> the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[(local) name]</a> of the
element information items <a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a> by that definition. The connection between a
name and a type definition is described in <a href="#cElement_Declarations">Element Declarations (§3.3)</a>. </div><p>As described in <a href="#Type_Derivation">Type Definition Hierarchy (§2.2.1.1)</a>, each complex type is derived from a
<a class="propref" href="#ct-base_type_definition">{base type definition}</a> which is itself either a <a href="#Simple_Type_Definition">Simple Type Definition (§2.2.1.2)</a> or a <a href="#Complex_Type_Definition">Complex Type Definition (§2.2.1.3)</a>. <a class="propref" href="#derivation_method">{derivation method}</a> specifies the means of derivation as either <i>extension</i> or <i>restriction</i> (see <a href="#Type_Derivation">Type Definition Hierarchy (§2.2.1.1)</a>).</p><p>A complex type with an empty specification for <a class="propref" href="#ct-final">{final}</a> can be used as a
<a class="propref" href="#ct-base_type_definition">{base type definition}</a> for other types derived by either of
extension or restriction; the explicit values <i>extension</i>, and <i>restriction</i> prevent further
derivations by extension and restriction respectively. If all values are specified, then <span class="termdef"><a id="key-ct-final" name="key-ct-final">[Definition:]  </a>the complex type is said to be
<b>final</b>, because no
further derivations are possible</span>. Finality is <em>not</em>
inherited, that is, a type definition derived by restriction from a type
definition which is final for extension is not itself, in the absence of any
explicit <code>final</code> attribute of its own, final for anything.</p><p>Complex types for which <a class="propref" href="#ct-abstract">{abstract}</a> is <i>true</i> must
not be used as the
<a class="propref" href="#type_definition">{type definition}</a> for the <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> of element information items. It follows that they must not be referenced from an
<a href="#xsi_type">xsi:type (§2.6.1)</a> attribute in an instance document. Abstract complex types can be
used as <a class="propref" href="#ct-base_type_definition">{base type definition}</a>s, or even as the <a class="propref" href="#type_definition">{type definition}</a>s of element declarations, provided in every case a concrete derived type definition is used for <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a>, either via <a href="#xsi_type">xsi:type (§2.6.1)</a> or the operation of a substitution group.</p><p><a class="propref" href="#ct-attribute_declarations">{attribute uses}</a> are a set of attribute uses. See <a href="#cvc-complex-type">Element Locally Valid (Complex Type) (§3.4.4)</a>
and <a href="#cvc-attribute">Attribute Locally Valid (§3.2.4)</a> for details of attribute <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a>.</p><p><a class="propref" href="#ct-attribute_wildcard">{attribute wildcard}</a>s provide a more flexible specification for <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> of
attributes not explicitly included in <a class="propref" href="#ct-attribute_declarations">{attribute uses}</a>.
Informally, the specific values
of <a class="propref" href="#ct-attribute_wildcard">{attribute wildcard}</a> are interpreted as follows:
</p><ul><li><i>any</i>: <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> can include attributes with any qualified or unqualified name.</li><li>a set whose
members are either namespace names or <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>: <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> can
include any attribute(s) from the specified namespace(s). If <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> is included in the set, then any unqualified attributes are (also) allowed.</li><li><i>'not'</i> and a namespace name: <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> cannot include attributes from the specified namespace.</li><li><i>'not'</i> and <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>: <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> cannot include
unqualified attributes.</li></ul><p>
See <a href="#cvc-complex-type">Element Locally Valid (Complex Type) (§3.4.4)</a> and <a href="#cvc-wildcard-namespace">Wildcard allows Namespace Name (§3.10.4)</a> for formal
details of attribute wildcard <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a>. </p><p><a class="propref" href="#content_type">{content type}</a> determines the <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> of <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> of element information items. Informally:
</p><ul><li>A <a class="propref" href="#content_type">{content type}</a> with the distinguished value <i>empty</i> <a class="termref" href="#key-vn"><span class="arrow">·</span>validates<span class="arrow">·</span></a> elements
with no character or element information item <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>.</li><li>A <a class="propref" href="#content_type">{content type}</a> which is a <a href="#Simple_Type_Definition">Simple Type Definition (§2.2.1.2)</a> <a class="termref" href="#key-vn"><span class="arrow">·</span>validates<span class="arrow">·</span></a>
elements with character-only <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>.</li><li>An <i>element-only</i> <a class="propref" href="#content_type">{content type}</a> <a class="termref" href="#key-vn"><span class="arrow">·</span>validates<span class="arrow">·</span></a> elements with <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> that
conform to the supplied <a class="termref" href="#key-contentModel"><span class="arrow">·</span>content model<span class="arrow">·</span></a>.</li><li>A <i>mixed</i> <a class="propref" href="#content_type">{content type}</a> <a class="termref" href="#key-vn"><span class="arrow">·</span>validates<span class="arrow">·</span></a> elements whose element <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> (i.e. specifically ignoring other <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> such as character information items)
conform to the supplied <a class="termref" href="#key-contentModel"><span class="arrow">·</span>content model<span class="arrow">·</span></a>.</li></ul><p>
</p><p><a class="propref" href="#ct-exact">{prohibited substitutions}</a> determine
whether an element declaration appearing in a <a class="termref" href="#key-contentModel"><span class="arrow">·</span>
content model<span class="arrow">·</span></a> is prevented from additionally
<a class="termref" href="#key-vn"><span class="arrow">·</span>validating<span class="arrow">·</span></a> element items with an <a href="#xsi_type">xsi:type (§2.6.1)</a> attribute that
identifies a complex type definition derived by <i>extension</i> or
<i>restriction</i> from this definition, or element items in
a substitution group whose type definition is similarly derived:
If <a class="propref" href="#ct-exact">{prohibited substitutions}</a> is empty,
then all such substitutions are allowed, otherwise, the derivation method(s) it
names are disallowed.
</p><p>See <a href="#cAnnotations">Annotations (§3.13)</a> for information on the role of the
<a class="propref" href="#ct-annotations">{annotations}</a> property.</p></div><div class="div3">
<h4><a id="declare-type" name="declare-type"/>3.4.2 XML Representation of Complex Type Definitions</h4><p>The XML representation for a complex type definition schema component is a
<a class="eltref" href="#element-complexType"><complexType></a> element information item.</p><p>The XML representation for complex type definitions with
a simple type definition <a class="propref" href="#content_type">{content type}</a> is significantly different
from that of those with other <a class="propref" href="#content_type">{content type}</a>s, and this
is reflected in the presentation below, which displays first the elements
involved in the first case, then those for the second. The property mapping is shown once for each case.</p><div class="reprdef"><div class="reprHeader"><span class="reprdef">XML Representation Summary</span>: <code>complexType</code> Element Information Item</div><div class="reprBody">
<p class="element-syntax-1"><a name="element-complexType" id="element-complexType"><complexType</a><br/>  abstract = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#boolean">boolean</a> : false<br/>  block =
(<var>#all</var> | List of (<var>extension</var> | <var>restriction</var>))
<br/>  final =
(<var>#all</var> | List of (<var>extension</var> | <var>restriction</var>))
<br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  mixed = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#boolean">boolean</a> : false<br/>  name = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#NCName">NCName</a><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?, (<a class="eltref" href="#element-simpleContent">simpleContent</a> | <a class="eltref" href="#element-complexContent">complexContent</a> | ((<a class="eltref" href="#element-group">group</a> | <a class="eltref" href="#element-all">all</a> | <a class="eltref" href="#element-choice">choice</a> | <a class="eltref" href="#element-sequence">sequence</a>)?, ((<a class="eltref" href="#element-attribute">attribute</a> | <a class="eltref" href="#element-attributeGroup">attributeGroup</a>)*, <a class="eltref" href="#element-anyAttribute">anyAttribute</a>?))))<br/></complexType></p>
<div class="reprdep">Whichever alternative for the content of <a class="eltref" href="#element-complexType"><complexType></a> is
chosen, the following property mappings apply:</div>
<div class="reprcomp"><table class="reprcomp"><thead><tr><th><a href="#Complex_Type_Definition_details">Complex Type Definition</a><strong> Schema Component</strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Representation</th></tr></thead><tbody valign="top"><tr valign="top"><td><a class="propref" href="#ct-name">{name}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>name</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> if present, otherwise <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</td></tr><tr valign="top"><td><a class="propref" href="#ct-target_namespace">{target namespace}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the
<code>targetNamespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of the <a class="eltref" href="#element-schema"><schema></a> ancestor
element information item if present, otherwise <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</td></tr><tr valign="top"><td><a class="propref" href="#ct-abstract">{abstract}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>abstract</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, if present, otherwise <i>false</i>.</td></tr><tr valign="top"><td><a class="propref" href="#ct-exact">{prohibited substitutions}</a></td><td>A set corresponding to the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the
<code>block</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, if present, otherwise on the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the
<code>blockDefault</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of the ancestor <a class="eltref" href="#element-schema"><schema></a> element
information item, if present, otherwise on the empty string. Call this the <b>EBV</b> (for effective block value). Then the value of this property is
the appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">1 <b>If </b>the <b>EBV</b> is the empty string, <b>then </b>the empty set;</div><div class="clnumber">2 <b>If </b>the <b>EBV</b> is <code>#all</code>, <b>then </b><code>{</code><i>extension</i>, <i>restriction</i><code>}</code>;</div><div class="clnumber">3 <b>otherwise </b>a set with members drawn from the set above, each being present or
absent depending on whether the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> (which is a list) contains an
equivalently named item.
<div class="note"><b>Note: </b>Although the <code>blockDefault</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of <a class="eltref" href="#element-schema"><schema></a> may include values other than <i>restriction</i> or<i>extension</i>, those values are ignored in the determination of <a class="propref" href="#ct-exact">{prohibited substitutions}</a> for complex type definitions (they <em>are</em> used elsewhere).</div>
</div></div>
</td></tr><tr valign="top"><td><a class="propref" href="#ct-final">{final}</a></td><td>As for <a class="propref" href="#ct-exact">{prohibited substitutions}</a> above, but using the
<code>final</code> and <code>finalDefault</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> in place of the
<code>block</code> and <code>blockDefault</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a>.</td></tr><tr valign="top"><td><a class="propref" href="#ct-annotations">{annotations}</a></td><td>The annotations corresponding to the <a class="eltref" href="#element-annotation"><annotation></a> element information item in the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if present, in the <a class="eltref" href="#element-simpleContent"><simpleContent></a> and
<a class="eltref" href="#element-complexContent"><complexContent></a> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if present, and in their <a class="eltref" href="#element-simpleContent..restriction"><restriction></a> and <a class="eltref" href="#element-simpleContent..extension"><extension></a> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if present, otherwise <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</td></tr></tbody></table></td></tr></tbody></table></div>
<div class="reprdep">When the <a class="eltref" href="#element-simpleContent"><simpleContent></a> alternative is chosen, the following
elements are relevant, and the remaining property mappings are as below. Note that either
<a class="eltref" href="#element-simpleContent..restriction"><restriction></a> or <a class="eltref" href="#element-simpleContent..extension"><extension></a> must be chosen as the
content of <a class="eltref" href="#element-simpleContent"><simpleContent></a>.</div>
<p class="element-syntax"><a name="element-simpleContent" id="element-simpleContent"><simpleContent</a><br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?, (<a class="eltref" href="#element-simpleContent..restriction">restriction</a> | <a class="eltref" href="#element-simpleContent..extension">extension</a>))<br/></simpleContent></p>
<p class="element-syntax"><a name="element-simpleContent..restriction" id="element-simpleContent..restriction"><restriction</a><br/>  <b>base</b> = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#QName">QName</a><br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?, (<a class="eltref" href="#element-simpleType">simpleType</a>?, (<a class="eltref" href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#element-minExclusive">minExclusive</a> | <a class="eltref" href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#element-minInclusive">minInclusive</a> | <a class="eltref" href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#element-maxExclusive">maxExclusive</a> | <a class="eltref" href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#element-maxInclusive">maxInclusive</a> | <a class="eltref" href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#element-totalDigits">totalDigits</a> | <a class="eltref" href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#element-fractionDigits">fractionDigits</a> | <a class="eltref" href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#element-length">length</a> | <a class="eltref" href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#element-minLength">minLength</a> | <a class="eltref" href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#element-maxLength">maxLength</a> | <a class="eltref" href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#element-enumeration">enumeration</a> | <a class="eltref" href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#element-whiteSpace">whiteSpace</a> | <a class="eltref" href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#element-pattern">pattern</a>)*)?, ((<a class="eltref" href="#element-attribute">attribute</a> | <a class="eltref" href="#element-attributeGroup">attributeGroup</a>)*, <a class="eltref" href="#element-anyAttribute">anyAttribute</a>?))<br/></restriction></p>
<p class="element-syntax"><a name="element-simpleContent..extension" id="element-simpleContent..extension"><extension</a><br/>  <b>base</b> = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#QName">QName</a><br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?, ((<a class="eltref" href="#element-attribute">attribute</a> | <a class="eltref" href="#element-attributeGroup">attributeGroup</a>)*, <a class="eltref" href="#element-anyAttribute">anyAttribute</a>?))<br/></extension></p>
<p class="element-syntax"><a name="element-simpleContent..attributeGroup" id="element-simpleContent..attributeGroup"><attributeGroup</a><br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  <b>ref</b> = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#QName">QName</a><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?)<br/></attributeGroup></p>
<p class="element-syntax"><a name="element-anyAttribute" id="element-anyAttribute"><anyAttribute</a><br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  namespace =
((<var>##any</var> | <var>##other</var>) | List of
(<a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#anyURI">anyURI</a> | (<var>##targetNamespace</var> | <var>##local</var>))
)
 : ##any<br/>  processContents = (<var>lax</var> | <var>skip</var> | <var>strict</var>) : strict<br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?)<br/></anyAttribute></p>
<div class="reprcomp"><table class="reprcomp"><thead><tr><th><a href="#Complex_Type_Definition_details">Complex Type Definition with simple content</a><strong> Schema Component</strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Representation</th></tr></thead><tbody valign="top"><tr valign="top"><td><a class="propref" href="#ct-base_type_definition">{base type definition}</a></td><td>The type definition <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to by the
<a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>base</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a></td></tr><tr valign="top"><td><a class="propref" href="#derivation_method">{derivation method}</a></td><td>If the <a class="eltref" href="#element-simpleContent..restriction"><restriction></a> alternative
is chosen, then <i>restriction</i>, otherwise (the <a class="eltref" href="#element-simpleContent..extension"><extension></a> alternative
is chosen) <i>extension</i>.</td></tr><tr valign="top"><td><a class="propref" href="#ct-attribute_declarations">{attribute uses}</a></td><td>A union of sets of attribute uses as follows
<div class="constraintlist"><div class="clnumber">1<a name="c-add1" id="c-add1"> </a>The set of attribute uses corresponding to the <a class="eltref" href="#element-attribute"><attribute></a> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if any.</div><div class="clnumber">2<a name="c-add2" id="c-add2"> </a>The <a class="propref" href="#ag-attribute_declarations">{attribute uses}</a> of the
attribute groups <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to by the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a>s of the <code>ref</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of the <a class="eltref" href="#element-simpleContent..attributeGroup"><attributeGroup></a> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if any.</div><div class="clnumber">3 if the type definition <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to by the
<a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>base</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> is a complex type definition, the
<a class="propref" href="#ct-attribute_declarations">{attribute uses}</a> of that type definition, unless
the <a class="eltref" href="#element-simpleContent..restriction"><restriction></a> alternative is chosen, in which case some members of
that type definition's <a class="propref" href="#ct-attribute_declarations">{attribute uses}</a> may not be
included, namely those whose
<a class="propref" href="#attribute">{attribute declaration}</a>'s
<a class="propref" href="#a-name">{name}</a> and <a class="propref" href="#a-target_namespace">{target namespace}</a> are the same as
<b>one</b> of the following:<div class="constraintlist"><div class="clnumber">3.1 the <a class="propref" href="#a-name">{name}</a> and <a class="propref" href="#a-target_namespace">{target namespace}</a> of the <a class="propref" href="#attribute">{attribute declaration}</a> of an attribute use in the set per clause <a href="#c-add1">1</a> or clause <a href="#c-add2">2</a> above;</div><div class="clnumber">3.2 what would have been the <a class="propref" href="#a-name">{name}</a> and <a class="propref" href="#a-target_namespace">{target namespace}</a> of the <a class="propref" href="#attribute">{attribute declaration}</a> of an attribute use in the set per clause <a href="#c-add1">1</a> above but for the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>use</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of the relevant <a class="eltref" href="#element-attribute"><attribute></a> among the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> of <a class="eltref" href="#element-simpleContent..restriction"><restriction></a> being <i>prohibited</i>.</div></div></div></div>
</td></tr><tr valign="top"><td><a class="propref" href="#ct-attribute_wildcard">{attribute wildcard}</a></td><td>
<div class="constraintlist"><div class="clnumber">1 <span class="termdef"><a id="key-law" name="key-law">[Definition:]  </a>Let the <b>local wildcard</b> be defined as</span>
the appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">1.1 <b>If </b>there is an <a class="eltref" href="#element-anyAttribute"><anyAttribute></a> present, <b>then </b>a wildcard based
on the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a>s of the <code>namespace</code> and
<code>processContents</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> and the <a class="eltref" href="#element-annotation"><annotation></a> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, exactly as for the wildcard
corresponding to an <a class="eltref" href="#element-any"><any></a> element as set out in <a href="#declare-openness">XML Representation of Wildcard Schema Components (§3.10.2)</a>;</div><div class="clnumber">1.2 <b>otherwise </b><a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</div></div></div><div class="clnumber">2 <span class="termdef"><a id="key-eaw" name="key-eaw">[Definition:]  </a>Let the <b>complete wildcard</b> be defined as</span>
the appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">2.1 <b>If </b>there are no <a class="eltref" href="#element-simpleContent..attributeGroup"><attributeGroup></a> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> corresponding
to attribute groups with non-<a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> <a class="propref" href="#ag-attribute_wildcard">{attribute wildcard}</a>s, <b>then </b>the <a class="termref" href="#key-law"><span class="arrow">·</span>local wildcard<span class="arrow">·</span></a>.</div><div class="clnumber">2.2 <b>If </b>there are one or more <a class="eltref" href="#element-simpleContent..attributeGroup"><attributeGroup></a> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> corresponding
to attribute groups with non-<a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> <a class="propref" href="#ag-attribute_wildcard">{attribute wildcard}</a>s, <b>then </b>
the appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">2.2.1<a name="c-awi1" id="c-awi1"> </a><b>If </b>there is an <a class="eltref" href="#element-anyAttribute"><anyAttribute></a> present, <b>then </b>a wildcard whose <a class="propref" href="#process_contents">{process contents}</a> and
<a class="propref" href="#w-annotation">{annotation}</a> are those of the <a class="termref" href="#key-law"><span class="arrow">·</span>local
wildcard<span class="arrow">·</span></a>, and whose <a class="propref" href="#namespace_constraint">{namespace constraint}</a> is the intensional intersection of the <a class="propref" href="#namespace_constraint">{namespace constraint}</a> of the <a class="termref" href="#key-law"><span class="arrow">·</span>local wildcard<span class="arrow">·</span></a>
and of the <a class="propref" href="#namespace_constraint">{namespace constraint}</a>s of all the non-<a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> <a class="propref" href="#ag-attribute_wildcard">{attribute wildcard}</a>s of the attribute groups corresponding to the <a class="eltref" href="#element-simpleContent..attributeGroup"><attributeGroup></a> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, as defined in <a href="#cos-aw-intersect">Attribute Wildcard Intersection (§3.10.6)</a>.</div><div class="clnumber">2.2.2<a name="c-awi2" id="c-awi2"> </a><b>If </b>there is no <a class="eltref" href="#element-anyAttribute"><anyAttribute></a> present, <b>then </b>a wildcard whose properties are as follows:
<dl><dt class="label"><a class="propref" href="#process_contents">{process contents}</a></dt><dd>The <a class="propref" href="#process_contents">{process contents}</a> of the first non-<a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> <a class="propref" href="#ag-attribute_wildcard">{attribute wildcard}</a> of an attribute group among the
attribute groups corresponding to the <a class="eltref" href="#element-simpleContent..attributeGroup"><attributeGroup></a> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>.</dd><dt class="label"><a class="propref" href="#namespace_constraint">{namespace constraint}</a></dt><dd>The intensional intersection of the <a class="propref" href="#namespace_constraint">{namespace constraint}</a>s of all the non-<a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> <a class="propref" href="#ag-attribute_wildcard">{attribute wildcard}</a>s of the attribute groups corresponding to the <a class="eltref" href="#element-simpleContent..attributeGroup"><attributeGroup></a> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, as defined in <a href="#cos-aw-intersect">Attribute Wildcard Intersection (§3.10.6)</a>.</dd><dt class="label"><a class="propref" href="#w-annotation">{annotation}</a></dt><dd><a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</dd></dl>
</div></div>
</div></div>
</div><div class="clnumber">3 The value is then determined by
the appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">3.1 <b>If </b>the <a class="eltref" href="#element-simpleContent..restriction"><restriction></a> alternative is chosen, <b>then </b>the <a class="termref" href="#key-eaw"><span class="arrow">·</span>complete wildcard<span class="arrow">·</span></a>;</div><div class="clnumber">3.2 <b>If </b>the <a class="eltref" href="#element-simpleContent..extension"><extension></a> alternative is chosen, <b>then </b>
<div class="constraintlist"><div class="clnumber">3.2.1 <span class="termdef"><a id="key-baw" name="key-baw">[Definition:]  </a>let the <b>base
wildcard</b> be defined as</span>
the appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">3.2.1.1 <b>If </b>the type definition <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to by the
<a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>base</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> is a complex type definition
with an <a class="propref" href="#ct-attribute_wildcard">{attribute wildcard}</a>, <b>then </b>that <a class="propref" href="#ct-attribute_wildcard">{attribute wildcard}</a>.</div><div class="clnumber">3.2.1.2 <b>otherwise </b><a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</div></div>
</div><div class="clnumber">3.2.2 The value is then determined by
the appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">3.2.2.1 <b>If </b>the <a class="termref" href="#key-baw"><span class="arrow">·</span>base wildcard<span class="arrow">·</span></a> is non-<a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>, <b>then </b>
the appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">3.2.2.1.1 <b>If </b>the <a class="termref" href="#key-eaw"><span class="arrow">·</span>complete wildcard<span class="arrow">·</span></a> is <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>, <b>then </b>the <a class="termref" href="#key-baw"><span class="arrow">·</span>base wildcard<span class="arrow">·</span></a>.</div><div class="clnumber">3.2.2.1.2<a name="c-awu" id="c-awu"> </a><b>otherwise </b>a wildcard whose <a class="propref" href="#process_contents">{process contents}</a> and
<a class="propref" href="#w-annotation">{annotation}</a> are those of the <a class="termref" href="#key-eaw"><span class="arrow">·</span>complete
wildcard<span class="arrow">·</span></a>, and whose <a class="propref" href="#namespace_constraint">{namespace constraint}</a> is the
intensional union of the <a class="propref" href="#namespace_constraint">{namespace constraint}</a> of the <a class="termref" href="#key-eaw"><span class="arrow">·</span>complete wildcard<span class="arrow">·</span></a>
and of the <a class="termref" href="#key-baw"><span class="arrow">·</span>base wildcard<span class="arrow">·</span></a>, as defined in <a href="#cos-aw-union">Attribute Wildcard Union (§3.10.6)</a>.</div></div>
</div><div class="clnumber">3.2.2.2 <b>otherwise </b>(the <a class="termref" href="#key-baw"><span class="arrow">·</span>base
wildcard<span class="arrow">·</span></a> is <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>) the <a class="termref" href="#key-eaw"><span class="arrow">·</span>complete
wildcard<span class="arrow">·</span></a></div></div></div></div>
</div></div></div></div>
</td></tr><tr valign="top"><td><a class="propref" href="#content_type">{content type}</a></td><td>
the appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">1 <b>If </b>the type definition <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to by the
<a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>base</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> is a complex type definition whose own <a class="propref" href="#content_type">{content type}</a> is a
simple type definition and the <a class="eltref" href="#element-simpleContent..restriction"><restriction></a> alternative is chosen, <b>then </b>starting from either
<div class="constraintlist"><div class="clnumber">1.1<a name="std1cl" id="std1cl"> </a>the simple type definition corresponding to the <a class="eltref" href="#element-simpleType"><simpleType></a> among
the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> of <a class="eltref" href="#element-simpleContent..restriction"><restriction></a> if there
is one;</div><div class="clnumber">1.2<a name="std2cl" id="std2cl"> </a>otherwise (<a class="eltref" href="#element-simpleContent..restriction"><restriction></a> has no <a class="eltref" href="#element-simpleType"><simpleType></a> among its
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>), the simple type definition which is the <a class="propref" href="#content_type">{content type}</a> of the type definition <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to by the
<a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>base</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a></div></div>
a simple type definition which restricts the simple type definition identified in
clause <a href="#std1cl">1.1</a> or clause <a href="#std2cl">1.2</a> with a
set of facet components corresponding to the appropriate element information
items among the <a class="eltref" href="#element-simpleContent..restriction"><restriction></a>'s
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> (i.e. those which specify facets, if any), as
defined in <a href="#st-restrict-facets">Simple Type Restriction (Facets) (§3.14.6)</a>;
</div><div class="clnumber">2 <b>If </b>the type definition <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to by the
<a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>base</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> is a complex type definition
whose own <a class="propref" href="#content_type">{content type}</a> is <i>mixed</i> and a particle which
is <a class="termref" href="#cd-emptiable"><span class="arrow">·</span>emptiable<span class="arrow">·</span></a>, as defined in <a href="#cos-group-emptiable">Particle Emptiable (§3.9.6)</a> and the <a class="eltref" href="#element-simpleContent..restriction"><restriction></a> alternative is chosen, <b>then </b>starting from
the simple type definition corresponding to the <a class="eltref" href="#element-simpleType"><simpleType></a> among
the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> of <a class="eltref" href="#element-simpleContent..restriction"><restriction></a> (which
must be present)
a simple type definition which restricts that simple type definition with a
set of facet components corresponding to the appropriate element information
items among the <a class="eltref" href="#element-simpleContent..restriction"><restriction></a>'s
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> (i.e. those which specify facets, if any), as
defined in <a href="#st-restrict-facets">Simple Type Restriction (Facets) (§3.14.6)</a>;
</div><div class="clnumber">3 <b>If </b>the type definition <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to by the
<a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>base</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> is a complex type definition
(whose own <a class="propref" href="#content_type">{content type}</a> must be a
simple type definition, see below) and the <a class="eltref" href="#element-simpleContent..extension"><extension></a> alternative is chosen, <b>then </b>
the <a class="propref" href="#content_type">{content type}</a> of that complex type definition;</div><div class="clnumber">4 <b>otherwise </b>(the type definition <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to by the
<a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>base</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> is a simple type definition and
the <a class="eltref" href="#element-simpleContent..extension"><extension></a> alternative is chosen), then
that simple type definition.</div></div>
</td></tr></tbody></table></td></tr></tbody></table></div>
<div class="reprdep">When the <a class="eltref" href="#element-complexContent"><complexContent></a> alternative is chosen, the following
elements are relevant (as are the <a class="eltref" href="#element-simpleContent..attributeGroup"><attributeGroup></a> and <a class="eltref" href="#element-anyAttribute"><anyAttribute></a> elements, not repeated here), and the additional property mappings are as below. Note that either
<a class="eltref" href="#element-complexContent..restriction"><restriction></a> or <a class="eltref" href="#element-complexContent..extension"><extension></a> must be chosen as the
content of <a class="eltref" href="#element-complexContent"><complexContent></a>, but their content models are
different in this case from the case above when they occur as children of
<a class="eltref" href="#element-simpleContent"><simpleContent></a>.</div>
<div class="reprdep">The property mappings below are <em>also</em> used in the case where
the third alternative (neither <a class="eltref" href="#element-simpleContent"><simpleContent></a> nor <a class="eltref" href="#element-complexContent"><complexContent></a>) is chosen. This case is understood as shorthand for complex content restricting the <a class="termref" href="#key-urType"><span class="arrow">·</span>ur-type definition<span class="arrow">·</span></a>, and the details of the mappings should be modified as necessary.</div>
<p class="element-syntax"><a name="element-complexContent" id="element-complexContent"><complexContent</a><br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  mixed = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#boolean">boolean</a><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?, (<a class="eltref" href="#element-complexContent..restriction">restriction</a> | <a class="eltref" href="#element-complexContent..extension">extension</a>))<br/></complexContent></p>
<p class="element-syntax"><a name="element-complexContent..restriction" id="element-complexContent..restriction"><restriction</a><br/>  <b>base</b> = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#QName">QName</a><br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?, (<a class="eltref" href="#element-group">group</a> | <a class="eltref" href="#element-all">all</a> | <a class="eltref" href="#element-choice">choice</a> | <a class="eltref" href="#element-sequence">sequence</a>)?, ((<a class="eltref" href="#element-attribute">attribute</a> | <a class="eltref" href="#element-attributeGroup">attributeGroup</a>)*, <a class="eltref" href="#element-anyAttribute">anyAttribute</a>?))<br/></restriction></p>
<p class="element-syntax"><a name="element-complexContent..extension" id="element-complexContent..extension"><extension</a><br/>  <b>base</b> = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#QName">QName</a><br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?, ((<a class="eltref" href="#element-group">group</a> | <a class="eltref" href="#element-all">all</a> | <a class="eltref" href="#element-choice">choice</a> | <a class="eltref" href="#element-sequence">sequence</a>)?, ((<a class="eltref" href="#element-attribute">attribute</a> | <a class="eltref" href="#element-attributeGroup">attributeGroup</a>)*, <a class="eltref" href="#element-anyAttribute">anyAttribute</a>?)))<br/></extension></p>
<div class="reprcomp"><table class="reprcomp"><thead><tr><th><a href="#Complex_Type_Definition_details">Complex Type Definition with complex content</a><strong> Schema Component</strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Representation</th></tr></thead><tbody valign="top"><tr valign="top"><td><a class="propref" href="#ct-base_type_definition">{base type definition}</a></td><td>The type definition <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to by the
<a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>base</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a></td></tr><tr valign="top"><td><a class="propref" href="#derivation_method">{derivation method}</a></td><td>If the <a class="eltref" href="#element-complexContent..restriction"><restriction></a> alternative
is chosen, then <i>restriction</i>, otherwise (the <a class="eltref" href="#element-complexContent..extension"><extension></a> alternative
is chosen) <i>extension</i>.</td></tr><tr valign="top"><td><a class="propref" href="#ct-attribute_declarations">{attribute uses}</a></td><td>A union of sets of attribute uses as follows:
<div class="constraintlist"><div class="clnumber">1<a name="c-ad1" id="c-ad1"> </a>The set of attribute uses corresponding to the <a class="eltref" href="#element-attribute"><attribute></a> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if any.</div><div class="clnumber">2<a name="c-ad2" id="c-ad2"> </a>The <a class="propref" href="#ag-attribute_declarations">{attribute uses}</a> of the
attribute groups <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to by the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a>s of the <code>ref</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of the <a class="eltref" href="#element-simpleContent..attributeGroup"><attributeGroup></a> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if any.</div><div class="clnumber">3 The
<a class="propref" href="#ct-attribute_declarations">{attribute uses}</a> of the type definition <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to by the
<a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>base</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, unless
the <a class="eltref" href="#element-complexContent..restriction"><restriction></a> alternative
is chosen, in which case some members of
that type definition's <a class="propref" href="#ct-attribute_declarations">{attribute uses}</a> may not be
included, namely those whose
<a class="propref" href="#attribute">{attribute declaration}</a>'s
<a class="propref" href="#a-name">{name}</a> and <a class="propref" href="#a-target_namespace">{target namespace}</a> are the same as
<b>one</b> of the following:<div class="constraintlist"><div class="clnumber">3.1 The <a class="propref" href="#a-name">{name}</a> and <a class="propref" href="#a-target_namespace">{target namespace}</a> of the <a class="propref" href="#attribute">{attribute declaration}</a> of an attribute use in the set per clause <a href="#c-ad1">1</a> or clause <a href="#c-ad2">2</a> above;</div><div class="clnumber">3.2 what would have been the <a class="propref" href="#a-name">{name}</a> and <a class="propref" href="#a-target_namespace">{target namespace}</a> of the <a class="propref" href="#attribute">{attribute declaration}</a> of an attribute use in the set per clause <a href="#c-ad1">1</a> above but for the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>use</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of the relevant <a class="eltref" href="#element-attribute"><attribute></a> among the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> of <a class="eltref" href="#element-complexContent..restriction"><restriction></a> being <i>prohibited</i>.</div></div></div></div>
</td></tr><tr valign="top"><td><a class="propref" href="#ct-attribute_wildcard">{attribute wildcard}</a></td><td>As above for the <a class="eltref" href="#element-simpleContent"><simpleContent></a> alternative.</td></tr><tr valign="top"><td><a class="propref" href="#content_type">{content type}</a></td><td>
<div class="constraintlist"><div class="clnumber">1 <span class="termdef"><a id="key-efm" name="key-efm">[Definition:]  </a>Let the
<b>effective mixed</b> be </span>
the appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">1.1 <b>If </b>the <code>mixed</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> is present on <a class="eltref" href="#element-complexContent"><complexContent></a>, <b>then </b>its <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a>;</div><div class="clnumber">1.2 <b>If </b>the <code>mixed</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> is present on
<a class="eltref" href="#element-complexType"><complexType></a>, <b>then </b>its <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a>;</div><div class="clnumber">1.3 <b>otherwise </b><code>false</code>.</div></div></div><div class="clnumber">2
<span class="termdef"><a id="key-exg" name="key-exg">[Definition:]  </a>Let the <b>effective
content</b> be </span>the appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">2.1<a name="c-cme" id="c-cme"> </a><b>If </b>
<b>one</b> of the following is true<div class="constraintlist"><div class="clnumber">2.1.1 There is no <a class="eltref" href="#element-group"><group></a>, <a class="eltref" href="#element-all"><all></a>, <a class="eltref" href="#element-choice"><choice></a> or <a class="eltref" href="#element-sequence"><sequence></a> among the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>;</div><div class="clnumber">2.1.2 There is an <a class="eltref" href="#element-all"><all></a> or <a class="eltref" href="#element-sequence"><sequence></a> among
the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> with no <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> of its own excluding <a class="eltref" href="#element-annotation"><annotation></a>;</div><div class="clnumber">2.1.3 There is a <a class="eltref" href="#element-choice"><choice></a> among
the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> with no <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> of its own excluding <a class="eltref" href="#element-annotation"><annotation></a> whose <code>minOccurs</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> has the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> <code>0</code>;</div></div>
, <b>then </b>
the appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">2.1.4 <b>If </b>the <a class="termref" href="#key-efm"><span class="arrow">·</span>effective mixed<span class="arrow">·</span></a> is <code>true</code>, <b>then </b>A particle whose properties are as follows:
<dl><dt class="label"><a class="propref" href="#p-min_occurs">{min occurs}</a></dt><dd><code>1</code></dd><dt class="label"><a class="propref" href="#p-max_occurs">{max occurs}</a></dt><dd><code>1</code></dd><dt class="label"><a class="propref" href="#term">{term}</a></dt><dd>A model group whose <a class="propref" href="#compositor">{compositor}</a> is
<i>sequence</i> and whose <a class="propref" href="#particles">{particles}</a> is empty.</dd></dl>.</div><div class="clnumber">2.1.5 <b>otherwise </b><i>empty</i></div></div></div><div class="clnumber">2.2 <b>otherwise </b>the particle corresponding to
the <a class="eltref" href="#element-all"><all></a>, <a class="eltref" href="#element-choice"><choice></a>, <a class="eltref" href="#element-group"><group></a> or
<a class="eltref" href="#element-sequence"><sequence></a> among the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>.</div></div></div><div class="clnumber">3
Then the value of the property is
the appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">3.1 <b>If </b>the <a class="eltref" href="#element-complexContent..restriction"><restriction></a> alternative is chosen, <b>then </b>
the appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">3.1.1 <b>If </b>the <a class="termref" href="#key-exg"><span class="arrow">·</span>effective content<span class="arrow">·</span></a> is
<i>empty</i> , <b>then </b><i>empty</i>;</div><div class="clnumber">3.1.2<a name="c-ctrp" id="c-ctrp"> </a><b>otherwise </b>a pair consisting of
<div class="constraintlist"><div class="clnumber">3.1.2.1<a name="c-mve" id="c-mve"> </a><i>mixed</i> if the <a class="termref" href="#key-efm"><span class="arrow">·</span>effective mixed<span class="arrow">·</span></a> is <code>true</code>, otherwise <i>elementOnly</i></div><div class="clnumber">3.1.2.2 The <a class="termref" href="#key-exg"><span class="arrow">·</span>effective content<span class="arrow">·</span></a>.</div></div>
</div></div>
</div><div class="clnumber">3.2 <b>If </b>the <a class="eltref" href="#element-complexContent..extension"><extension></a> alternative is chosen, <b>then </b>
the appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">3.2.1 <b>If </b>the <a class="termref" href="#key-exg"><span class="arrow">·</span>effective
content<span class="arrow">·</span></a> is <i>empty</i>, <b>then </b>the
<a class="propref" href="#content_type">{content type}</a> of the type definition <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to
by the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>base</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a></div><div class="clnumber">3.2.2 <b>If </b>the type definition <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to
by the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>base</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> has a <a class="propref" href="#content_type">{content type}</a> of <i>empty</i>, <b>then </b>a pair as per clause <a href="#c-ctrp">3.1.2</a> above;</div><div class="clnumber">3.2.3 <b>otherwise </b>a pair of <i>mixed</i> or <i>elementOnly</i> (determined as per
clause <a href="#c-mve">3.1.2.1</a> above) and a particle whose properties are as follows:
<dl><dt class="label"><a class="propref" href="#p-min_occurs">{min occurs}</a></dt><dd><code>1</code></dd><dt class="label"><a class="propref" href="#p-max_occurs">{max occurs}</a></dt><dd><code>1</code></dd><dt class="label"><a class="propref" href="#term">{term}</a></dt><dd>A model group whose <a class="propref" href="#compositor">{compositor}</a> is
<i>sequence</i> and whose <a class="propref" href="#particles">{particles}</a> are the particle of
the <a class="propref" href="#content_type">{content type}</a> of the type definition <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to
by the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>base</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> followed by the
<a class="termref" href="#key-exg"><span class="arrow">·</span>effective content<span class="arrow">·</span></a>.</dd></dl></div></div>
</div></div></div></div>
</td></tr></tbody></table></td></tr></tbody></table></div>
</div></div><div class="note"><b>Note: </b>Aside from the simple coherence requirements enforced above, constraining
type definitions identified as restrictions to actually <em>be</em>
restrictions, that is, to <a class="termref" href="#key-vn"><span class="arrow">·</span>validate<span class="arrow">·</span></a> a
subset of the items which are
<a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a> by their base type definition, is enforced in <a href="#coss-ct">Constraints on Complex Type Definition Schema Components (§3.4.6)</a>.</div><div class="note"><b>Note: </b>The <em>only</em> substantive function of the value <i>prohibited</i> for the
<code>use</code> attribute of an <a class="eltref" href="#element-attribute"><attribute></a> is in establishing
the correspondence between a complex type defined by restriction and its XML
representation. It serves to prevent
inheritance of an identically named attribute use from the <a class="propref" href="#ct-base_type_definition">{base type definition}</a>. Such an <a class="eltref" href="#element-attribute"><attribute></a> does not correspond to any component, and hence there is no interaction with either explicit or inherited wildcards in the operation of <a href="#formal-complex-type">Complex Type Definition Validation Rules (§3.4.4)</a> or <a href="#coss-ct">Constraints on Complex Type Definition Schema Components (§3.4.6)</a>.</div><p>Careful consideration of the above concrete syntax reveals that
a type definition need consist of no more than a name, i.e. that
<code><complexType name="anyThing"/></code> is allowed.</p><div class="exampleOuter"><div class="exampleHeader">Example</div><div class="exampleInner"><pre><xs:complexType name="length1">
<xs:simpleContent>
<xs:extension base="xs:nonNegativeInteger">
<xs:attribute name="unit" type="xs:NMTOKEN"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:element name="width" type="length1"/>
<width unit="cm">25</width>
<xs:complexType name="length2">
<xs:complexContent>
<xs:restriction base="xs:anyType">
<xs:sequence>
<xs:element name="size" type="xs:nonNegativeInteger"/>
<xs:element name="unit" type="xs:NMTOKEN"/>
</xs:sequence>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:element name="depth" type="length2"/>
<depth>
<size>25</size><unit>cm</unit>
</depth>
<xs:complexType name="length3">
<xs:sequence>
<xs:element name="size" type="xs:nonNegativeInteger"/>
<xs:element name="unit" type="xs:NMTOKEN"/>
</xs:sequence>
</xs:complexType>
</pre></div><div class="exampleWrapper">
Three approaches to defining a type for length: one with
character data content constrained by reference to
a built-in datatype, and one attribute, the other two using two
elements. <code>length3</code> is the abbreviated alternative to
<code>length2</code>: they correspond to identical type definition components.
</div></div><div class="exampleOuter"><div class="exampleHeader">Example</div><div class="exampleInner"><pre><xs:complexType name="personName">
<xs:sequence>
<xs:element name="title" minOccurs="0"/>
<xs:element name="forename" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="surname"/>
</xs:sequence>
</xs:complexType>
<xs:complexType name="extendedName">
<xs:complexContent>
<xs:extension base="personName">
<xs:sequence>
<xs:element name="generation" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="addressee" type="extendedName"/>
<addressee>
<forename>Albert</forename>
<forename>Arnold</forename>
<surname>Gore</surname>
<generation>Jr</generation>
</addressee></pre></div><div class="exampleWrapper">A type definition for personal names, and a definition derived by
extension which adds a single element; an element declaration referencing the
derived definition, and a <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> instance thereof.</div></div><div class="exampleOuter"><div class="exampleHeader">Example</div><div class="exampleInner"><pre><xs:complexType name="simpleName">
<xs:complexContent>
<xs:restriction base="personName">
<xs:sequence>
<xs:element name="forename" minOccurs="1" maxOccurs="1"/>
<xs:element name="surname"/>
</xs:sequence>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:element name="who" type="simpleName"/>
<who>
<forename>Bill</forename>
<surname>Clinton</surname>
</who></pre></div><div class="exampleWrapper">A simplified type definition
derived from the base type from the previous example by restriction, eliminating one optional daughter and
fixing another to occur exactly once; an element declared by reference to it,
and a <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> instance thereof.</div></div><div class="exampleOuter"><div class="exampleHeader">Example</div><div class="exampleInner"><pre><xs:complexType name="paraType" mixed="true">
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element ref="emph"/>
<xs:element ref="strong"/>
</xs:choice>
<xs:attribute name="version" type="xs:number"/>
</xs:complexType></pre></div><div class="exampleWrapper">A further illustration of the abbreviated form, with the
<code>mixed</code> attribute appearing on <code>complexType</code> itself.</div></div></div><div class="div3">
<h4><a id="d0e7923" name="d0e7923"/>3.4.3 Constraints on XML Representations of Complex Type Definitions</h4><div class="constraintnote"><a name="src-ct" id="src-ct"/><b>Schema Representation Constraint: Complex Type Definition Representation OK</b><br/><div class="constraint">In addition to the conditions imposed on <a class="eltref" href="#element-complexType"><complexType></a> element
information items by the schema for schemas,
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 If the <a class="eltref" href="#element-complexContent"><complexContent></a> alternative is chosen, the type definition <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to
by the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>base</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> must be a complex type definition;</div><div class="clnumber">2 If the <a class="eltref" href="#element-simpleContent"><simpleContent></a> alternative is chosen,
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.1 The type definition <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to
by the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>base</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> must be
<b>one</b> of the following:<div class="constraintlist"><div class="clnumber">2.1.1 a complex type
definition whose <a class="propref" href="#content_type">{content type}</a> is a simple type definition;</div><div class="clnumber">2.1.2<a name="cl-esc" id="cl-esc"> </a>only if the
<a class="eltref" href="#element-simpleContent..restriction"><restriction></a> alternative is also chosen, a complex type
definition whose <a class="propref" href="#content_type">{content type}</a> is <i>mixed</i> and a particle
which is
<a class="termref" href="#cd-emptiable"><span class="arrow">·</span>emptiable<span class="arrow">·</span></a>, as defined in <a href="#cos-group-emptiable">Particle Emptiable (§3.9.6)</a>;</div><div class="clnumber">2.1.3 only if the
<a class="eltref" href="#element-simpleContent..extension"><extension></a> alternative is also chosen, a simple type definition.</div></div></div><div class="clnumber">2.2 If clause <a href="#cl-esc">2.1.2</a> above is satisfied, then there must be a
<a class="eltref" href="#element-simpleType"><simpleType></a> among the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> of <a class="eltref" href="#element-simpleContent..restriction"><restriction></a>.</div></div>
<div class="note"><b>Note: </b>Although not explicitly ruled out either here or in <a href="#normative-schemaSchema">Schema for Schemas (normative) (§A)</a>, specifying <code><xs:complexType . . .mixed='true'</code> when the <a class="eltref" href="#element-simpleContent"><simpleContent></a> alternative is chosen has no effect on the corresponding component, and should be avoided. This may be ruled out in a subsequent version of this specification.</div></div><div class="clnumber">3 The corresponding complex type definition component must satisfy the conditions set
out in <a href="#coss-ct">Constraints on Complex Type Definition Schema Components (§3.4.6)</a>;</div><div class="clnumber">4 If clause <a href="#c-awi1">2.2.1</a> or clause <a href="#c-awi2">2.2.2</a> in the correspondence specification above for <a class="propref" href="#ct-attribute_wildcard">{attribute wildcard}</a> is satisfied, the intensional intersection must be expressible, as defined in <a href="#cos-aw-intersect">Attribute Wildcard Intersection (§3.10.6)</a>.</div></div>
</div></div></div><div class="div3">
<h4><a id="formal-complex-type" name="formal-complex-type"/>3.4.4 Complex Type Definition Validation Rules</h4><div class="constraintnote"><a name="cvc-complex-type" id="cvc-complex-type"/><b>Validation Rule: Element Locally Valid (Complex Type)</b><br/><div class="constraint">For an element information item to be locally <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to a complex type definition
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 <a class="propref" href="#ct-abstract">{abstract}</a> is <i>false</i>.</div><div class="clnumber">2 If clause <a href="#c-nl">3.2</a> of <a href="#cvc-elt">Element Locally Valid (Element) (§3.3.4)</a> did not
apply, then the appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">2.1 <b>If </b>the <a class="propref" href="#content_type">{content type}</a> is <i>empty</i>, <b>then </b>the element
information item has no character or element information item <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>.</div><div class="clnumber">2.2<a name="c-sv2" id="c-sv2"> </a><b>If </b>the <a class="propref" href="#content_type">{content type}</a> is a simple
type definition, <b>then </b>the element information item has no element
information item <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, and the <a class="termref" href="#key-nv"><span class="arrow">·</span>normalized value<span class="arrow">·</span></a> of the element information item is <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to that simple type definition as defined by <a href="#cvc-simple-type">String Valid (§3.14.4)</a>.</div><div class="clnumber">2.3 <b>If </b>the <a class="propref" href="#content_type">{content type}</a> is <i>element-only</i>, <b>then </b>the
element information item has no character information item <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> other
than those whose <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.character">[character code]</a> is defined as a <a href="http://www.w3.org/TR/REC-xml#NT-S">white space</a>
in <a href="#ref-xml">[XML 1.0 (Second Edition)]</a>.</div><div class="clnumber">2.4 <b>If </b>the <a class="propref" href="#content_type">{content type}</a> is <i>element-only</i> or
<i>mixed</i>, <b>then </b>the sequence of the element information item's element
information item <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if any, taken in order, is <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with
respect to the <a class="propref" href="#content_type">{content type}</a>'s particle, as defined in <a href="#cvc-particle">Element Sequence Locally Valid (Particle) (§3.9.4)</a>.</div></div></div><div class="clnumber">3<a name="c-aam" id="c-aam"> </a>For each attribute information item in the element information
item's <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> excepting those whose <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[namespace name]</a> is identical to <code>http://www.w3.org/2001/XMLSchema-instance</code> and whose <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[local name]</a> is one of <code>type</code>, <code>nil</code>, <code>schemaLocation</code> or <code>noNamespaceSchemaLocation</code>,
the appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">3.1<a name="c-ctma" id="c-ctma"> </a><b>If </b>there is among the <a class="propref" href="#ct-attribute_declarations">{attribute uses}</a> an
attribute use with an <a class="propref" href="#attribute">{attribute declaration}</a> whose
<a class="propref" href="#a-name">{name}</a> matches the attribute information item's <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[local name]</a> and whose <a class="propref" href="#a-target_namespace">{target namespace}</a> is identical to the attribute information item's <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[namespace name]</a> (where an <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> <a class="propref" href="#a-target_namespace">{target namespace}</a> is taken to be identical to a <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[namespace name]</a> with no value), <b>then </b>the attribute information must be <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to that attribute use as per <a href="#cvc-au">Attribute Locally Valid (Use) (§3.5.4)</a>. In this case the <a class="propref" href="#attribute">{attribute declaration}</a> of that attribute use is the <a class="termref" href="#key-dd"><span class="arrow">·</span>context-determined declaration<span class="arrow">·</span></a> for the attribute information item with respect to <a href="#cvc-assess-attr">Schema-Validity Assessment (Attribute) (§3.2.4)</a> and <a href="#sic-a-outcome">Assessment Outcome (Attribute) (§3.2.5)</a>.</div><div class="clnumber">3.2<a name="c-avaw" id="c-avaw"> </a><b>otherwise </b>
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">3.2.1 There must be an <a class="propref" href="#ct-attribute_wildcard">{attribute wildcard}</a>.</div><div class="clnumber">3.2.2 The
attribute information item must be <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to it as defined in <a href="#cvc-wildcard">Item Valid (Wildcard) (§3.10.4)</a>.</div></div>
</div></div>
</div><div class="clnumber">4 The <a class="propref" href="#attribute">{attribute declaration}</a> of each attribute use in the <a class="propref" href="#ct-attribute_declarations">{attribute uses}</a> whose
<a class="propref" href="#required">{required}</a> is <i>true</i> matches one of the attribute information items in the element information item's <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> as per clause <a href="#c-ctma">3.1</a> above.</div><div class="clnumber">5 Let <span class="termdef"><a id="key-ida" name="key-ida">[Definition:]  </a>the <b>wild
IDs</b> be the set of all
attribute information item to which clause <a href="#c-avaw">3.2</a> applied and whose <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> resulted in
a <a class="termref" href="#key-dd"><span class="arrow">·</span>context-determined declaration<span class="arrow">·</span></a> of
<i>mustFind</i> or no <a class="termref" href="#key-dd"><span class="arrow">·</span>context-determined
declaration<span class="arrow">·</span></a> at all, and whose <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[local name]</a> and <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[namespace name]</a> resolve (as defined by <a href="#cvc-resolve-instance">QName resolution (Instance) (§3.15.4)</a>) to an attribute declaration whose <a class="propref" href="#a-simple_type_definition">{type definition}</a> is or is derived from <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a></span>. Then
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">5.1 There must be no more than one item in <a class="termref" href="#key-ida"><span class="arrow">·</span>wild IDs<span class="arrow">·</span></a>.</div><div class="clnumber">5.2 If <a class="termref" href="#key-ida"><span class="arrow">·</span>wild IDs<span class="arrow">·</span></a> is non-empty, there must not be any attribute uses among the <a class="propref" href="#ct-attribute_declarations">{attribute uses}</a> whose <a class="propref" href="#attribute">{attribute declaration}</a>'s <a class="propref" href="#a-simple_type_definition">{type definition}</a> is or is derived from <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a>.</div></div>
<div class="note"><b>Note: </b>This clause serves to ensure that even via attribute
wildcards no element has more than one attribute of type ID, and that even when
an element legitimately lacks a declared attribute of type ID, a
wildcard-validated attribute must not supply it. That is, if an element has a
type whose attribute declarations include one of type ID, it either has that
attribute or no attribute of type ID.</div>
</div></div>
<div class="note"><b>Note: </b>When an <a class="propref" href="#ct-attribute_wildcard">{attribute wildcard}</a> is present, this does
<em>not</em> introduce any ambiguity with respect to how attribute
information items for
which an attribute use is present amongst the <a class="propref" href="#ct-attribute_declarations">{attribute uses}</a> whose name and target namespace match are <a class="termref" href="#key-va"><span class="arrow">·</span>assessed<span class="arrow">·</span></a>. In such cases the attribute use <em>always</em> takes precedence, and the <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> of such items stands or falls entirely on the basis of the attribute use and its <a class="propref" href="#attribute">{attribute declaration}</a>. This follows from the details of clause <a href="#c-aam">3</a>.</div></div></div></div><div class="div3">
<h4><a id="d0e8328" name="d0e8328"/>3.4.5 Complex Type Definition Information Set Contributions</h4><div class="constraintnote"><a name="sic-attrDefault" id="sic-attrDefault"/><b>Schema Information Set Contribution: Attribute Default Value</b><br/><div class="constraint">For each attribute use in the <a class="propref" href="#ct-attribute_declarations">{attribute uses}</a> whose
<a class="propref" href="#required">{required}</a> is <i>false</i> and whose <a class="propref" href="#au-value_constraint">{value constraint}</a> is not <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> but whose <a class="propref" href="#attribute">{attribute declaration}</a> does not match one of the attribute information items in the element information item's <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> as per clause <a href="#c-ctma">3.1</a> of <a href="#cvc-complex-type">Element Locally Valid (Complex Type) (§3.4.4)</a> above, the <a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a> has an attribute information item whose properties are as below added to the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> of the element information item.<dl><dt class="label"><a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[local name]</a></dt><dd>The <a class="propref" href="#attribute">{attribute declaration}</a>'s <a class="propref" href="#a-name">{name}</a>.</dd><dt class="label"><a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[namespace name]</a></dt><dd>The <a class="propref" href="#attribute">{attribute declaration}</a>'s <a class="propref" href="#a-target_namespace">{target namespace}</a>.</dd><dt class="label"><a class="propref" href="#a-schema_normalized_value">[schema normalized value]</a></dt><dd>The <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#dt-canonical-representation">canonical lexical representation</a> of the <a class="termref" href="#key-evc"><span class="arrow">·</span>effective value constraint<span class="arrow">·</span></a> value.</dd><dt class="label"><a class="propref" href="#a-schema_default">[schema default]</a></dt><dd>The <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#dt-canonical-representation">canonical lexical representation</a> of the <a class="termref" href="#key-evc"><span class="arrow">·</span>effective value constraint<span class="arrow">·</span></a> value.</dd><dt class="label"><a class="propref" href="#a-validation_context">[validation context]</a></dt><dd>The nearest ancestor element information item with a
<a class="propref" href="#e-schema_information">[schema information]</a> property.</dd><dt class="label"><a class="propref" href="#a-validity">[validity]</a></dt><dd><i>valid</i>.</dd><dt class="label"><a class="propref" href="#a-validation_attempted">[validation attempted]</a></dt><dd><i>full</i>.</dd><dt class="label"><a class="propref" href="#a-schema_specified">[schema specified]</a></dt><dd><i>schema</i>.</dd></dl>The added items should also either have <a class="propref" href="#a-type_definition">[type definition]</a> (and <a class="propref" href="#a-member_type_definition">[member type definition]</a> if appropriate) properties, or their lighter-weight alternatives, as specified in <a href="#sic-attrType">Attribute Validated by Type (§3.2.5)</a>.</div></div></div><div class="div3">
<h4><a id="coss-ct" name="coss-ct"/>3.4.6 Constraints on Complex Type Definition Schema Components</h4><p>All complex type definitions (see <a href="#Complex_Type_Definitions">Complex Type Definitions (§3.4)</a>) must satisfy the following constraints.</p><div class="constraintnote"><a name="ct-props-correct" id="ct-props-correct"/><b>Schema Component Constraint: Complex Type Definition Properties Correct</b><br/><div class="constraint"><b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 The values of the properties of a complex type definition must be as described in
the property tableau in
<a href="#Complex_Type_Definition_details">The Complex Type Definition Schema Component (§3.4.1)</a>, modulo the impact of <a href="#conformance-missing">Missing Sub-components (§5.3)</a>.</div><div class="clnumber">2 If the <a class="propref" href="#ct-base_type_definition">{base type definition}</a> is a simple type
definition, the <a class="propref" href="#derivation_method">{derivation method}</a> must be <i>extension</i>.</div><div class="clnumber">3 Circular definitions are disallowed, except for the <a class="termref" href="#ur-type-itself"><span class="arrow">·</span>ur-type definition<span class="arrow">·</span></a>. That is, it must be possible to reach the <a class="termref" href="#ur-type-itself"><span class="arrow">·</span>ur-type definition<span class="arrow">·</span></a> by repeatedly following the <a class="propref" href="#ct-base_type_definition">{base type definition}</a>.</div><div class="clnumber">4 Two distinct attribute declarations in the <a class="propref" href="#ct-attribute_declarations">{attribute uses}</a> must not have identical <a class="propref" href="#a-name">{name}</a>s and <a class="propref" href="#a-target_namespace">{target namespace}</a>s.</div><div class="clnumber">5 Two distinct attribute declarations in the <a class="propref" href="#ct-attribute_declarations">{attribute uses}</a>
must not have <a class="propref" href="#a-simple_type_definition">{type definition}</a>s which are or are derived from <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a>.</div></div></div></div><div class="constraintnote"><a name="cos-ct-extends" id="cos-ct-extends"/><b>Schema Component Constraint: Derivation Valid (Extension)</b><br/><div class="constraint">If the <a class="propref" href="#derivation_method">{derivation method}</a> is <i>extension</i>,
the appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">1 <b>If </b>the <a class="propref" href="#ct-base_type_definition">{base type definition}</a> is a complex type
definition, <b>then </b>
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1.1 The <a class="propref" href="#ct-final">{final}</a> of the <a class="propref" href="#ct-base_type_definition">{base type definition}</a> must not contain <i>extension</i>.</div><div class="clnumber">1.2<a name="c-cte" id="c-cte"> </a>Its <a class="propref" href="#ct-attribute_declarations">{attribute uses}</a> must be a subset
of the <a class="propref" href="#ct-attribute_declarations">{attribute uses}</a> of the complex type
definition itself, that is, for every attribute use in the
<a class="propref" href="#ct-attribute_declarations">{attribute uses}</a> of the
<a class="propref" href="#ct-base_type_definition">{base type definition}</a>, there must be an attribute use in the <a class="propref" href="#ct-attribute_declarations">{attribute uses}</a> of the complex
type definition itself whose <a class="propref" href="#attribute">{attribute declaration}</a> has the same <a class="propref" href="#a-name">{name}</a>,
<a class="propref" href="#a-target_namespace">{target namespace}</a> and
<a class="propref" href="#a-simple_type_definition">{type definition}</a> as its attribute declaration.</div><div class="clnumber">1.3 If it has an <a class="propref" href="#ct-attribute_wildcard">{attribute wildcard}</a>, the complex
type definition must also have one, and the base type definition's <a class="propref" href="#ct-attribute_wildcard">{attribute wildcard}</a>'s <a class="propref" href="#namespace_constraint">{namespace constraint}</a> must be a subset of the complex type definition's <a class="propref" href="#ct-attribute_wildcard">{attribute wildcard}</a>'s <a class="propref" href="#namespace_constraint">{namespace constraint}</a>, as defined by <a href="#cos-ns-subset">Wildcard Subset (§3.10.6)</a>.</div><div class="clnumber">1.4
<b>One</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1.4.1 The <a class="propref" href="#content_type">{content type}</a> of
the <a class="propref" href="#ct-base_type_definition">{base type definition}</a> and the
<a class="propref" href="#content_type">{content type}</a> of the complex type definition itself must be the
same simple type definition.</div><div class="clnumber">1.4.2 The
<a class="propref" href="#content_type">{content type}</a> of both the <a class="propref" href="#ct-base_type_definition">{base type definition}</a> and the complex type definition itself
must be <i>empty</i>.</div><div class="clnumber">1.4.3 <b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1.4.3.1 The
<a class="propref" href="#content_type">{content type}</a> of the complex type definition itself must
specify a particle.</div><div class="clnumber">1.4.3.2 <b>One</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1.4.3.2.1 The
<a class="propref" href="#content_type">{content type}</a> of the <a class="propref" href="#ct-base_type_definition">{base type definition}</a>
must be <i>empty</i>.</div><div class="clnumber">1.4.3.2.2
<b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1.4.3.2.2.1 Both
<a class="propref" href="#content_type">{content type}</a>s must be <i>mixed</i> or both must be
<i>element-only</i>.</div><div class="clnumber">1.4.3.2.2.2 The particle of the complex type
definition must be a <a class="termref" href="#cd-model-extension"><span class="arrow">·</span>valid
extension<span class="arrow">·</span></a> of the <a class="propref" href="#ct-base_type_definition">{base type definition}</a>'s particle,
as defined in <a href="#cos-particle-extend">Particle Valid (Extension) (§3.9.6)</a>.</div></div>
</div></div></div></div></div></div>
</div><div class="clnumber">1.5 It must in principle be possible to derive the complex type
definition in two steps, the first an extension and the
second a restriction (possibly vacuous), from that type definition among its
ancestors whose <a class="propref" href="#ct-base_type_definition">{base type definition}</a> is the <a class="termref" href="#ur-type-itself"><span class="arrow">·</span>ur-type definition<span class="arrow">·</span></a>.<div class="note"><b>Note: </b>This requirement ensures that nothing removed by a restriction
is subsequently added back by an extension. It is trivial to check if the
extension in question is the only extension in its derivation, or if there are
no restrictions bar the first from the <a class="termref" href="#ur-type-itself"><span class="arrow">·</span>ur-type
definition<span class="arrow">·</span></a>.<p/>Constructing the intermediate type definition to check this
constraint is straightforward: simply re-order the derivation to put all the
extension steps first, then collapse them into a single extension. If the
resulting definition can be the basis for a valid restriction to the desired
definition, the constraint is satisfied.</div></div></div>
</div><div class="clnumber">2 <b>If </b>the <a class="propref" href="#ct-base_type_definition">{base type definition}</a> is a simple type
definition, <b>then </b>
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.1 The <a class="propref" href="#content_type">{content type}</a> must be the same simple type
definition.</div><div class="clnumber">2.2 The <a class="propref" href="#st-final">{final}</a> of the <a class="propref" href="#ct-base_type_definition">{base type definition}</a> must not contain <i>extension</i>.</div></div>
</div></div>
<span class="termdef"><a id="cd-ct-extension" name="cd-ct-extension">[Definition:]  </a>If this
constraint <a href="#cos-ct-extends">Derivation Valid (Extension) (§3.4.6)</a> holds of a complex type definition, it is a <b>valid
extension</b> of its <a class="propref" href="#ct-base_type_definition">{base type definition}</a></span>.
</div></div><div class="constraintnote"><a name="derivation-ok-restriction" id="derivation-ok-restriction"/><b>Schema Component Constraint: Derivation Valid (Restriction, Complex)</b><br/><div class="constraint">If the <a class="propref" href="#derivation_method">{derivation method}</a> is <i>restriction</i>
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 The <a class="propref" href="#ct-base_type_definition">{base type definition}</a> must be a complex type
definition whose <a class="propref" href="#ct-final">{final}</a> does not contain <i>restriction</i>.</div><div class="clnumber">2<a name="c-rad" id="c-rad"> </a>For each attribute use (call this <b>R</b>) in the <a class="propref" href="#ct-attribute_declarations">{attribute uses}</a>
the appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">2.1 <b>If </b>there is an attribute use in the
<a class="propref" href="#ct-attribute_declarations">{attribute uses}</a> of the <a class="propref" href="#ct-base_type_definition">{base type definition}</a> (call this <b>B</b>) whose <a class="propref" href="#attribute">{attribute declaration}</a> has the same <a class="propref" href="#a-name">{name}</a> and <a class="propref" href="#a-target_namespace">{target namespace}</a>, <b>then </b>
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.1.1 <b>one</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.1.1.1 <b>B</b>'s <a class="propref" href="#required">{required}</a> is <i>false</i>.</div><div class="clnumber">2.1.1.2 <b>R</b>'s <a class="propref" href="#required">{required}</a> is <i>true</i>.</div></div></div><div class="clnumber">2.1.2 <b>R</b>'s <a class="propref" href="#attribute">{attribute declaration}</a>'s <a class="propref" href="#a-simple_type_definition">{type definition}</a> must be validly derived from <b>B</b>'s <a class="propref" href="#a-simple_type_definition">{type definition}</a> given the
empty set as defined in
<a href="#cos-st-derived-ok">Type Derivation OK (Simple) (§3.14.6)</a>.</div><div class="clnumber">2.1.3 <span class="termdef"><a id="key-evc" name="key-evc">[Definition:]  </a>Let the
<b>effective value constraint</b> of an attribute use be
its <a class="propref" href="#au-value_constraint">{value constraint}</a>, if present, otherwise
its <a class="propref" href="#attribute">{attribute declaration}</a>'s <a class="propref" href="#a-value_constraint">{value constraint}</a>
</span>. Then <b>one</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.1.3.1 <b>B</b>'s <a class="termref" href="#key-evc"><span class="arrow">·</span>effective value
constraint<span class="arrow">·</span></a> is <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> or <i>default</i>.</div><div class="clnumber">2.1.3.2 <b>R</b>'s <a class="termref" href="#key-evc"><span class="arrow">·</span>effective value
constraint<span class="arrow">·</span></a> is
<i>fixed</i> with the same string as <b>B</b>'s.</div></div>
</div></div>
</div><div class="clnumber">2.2 <b>otherwise </b>the <a class="propref" href="#ct-base_type_definition">{base type definition}</a> must
have an <a class="propref" href="#ct-attribute_wildcard">{attribute wildcard}</a> and the <a class="propref" href="#a-target_namespace">{target namespace}</a> of the <b>R</b>'s <a class="propref" href="#attribute">{attribute declaration}</a> must be <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to that wildcard, as defined in <a href="#cvc-wildcard-namespace">Wildcard allows Namespace Name (§3.10.4)</a>.</div></div>
</div><div class="clnumber">3<a name="c-rad2" id="c-rad2"> </a>For each attribute use in the <a class="propref" href="#ct-attribute_declarations">{attribute uses}</a> of
the <a class="propref" href="#ct-base_type_definition">{base type definition}</a> whose <a class="propref" href="#required">{required}</a> is
<i>true</i>, there must be an attribute use with an <a class="propref" href="#attribute">{attribute declaration}</a> with the same <a class="propref" href="#a-name">{name}</a> and <a class="propref" href="#a-target_namespace">{target namespace}</a> as its <a class="propref" href="#attribute">{attribute declaration}</a> in the
<a class="propref" href="#ct-attribute_declarations">{attribute uses}</a> of the complex type definition
itself whose <a class="propref" href="#required">{required}</a> is
<i>true</i>.</div><div class="clnumber">4<a name="c-raw" id="c-raw"> </a>If there is an <a class="propref" href="#ct-attribute_wildcard">{attribute wildcard}</a>,
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">4.1 The
<a class="propref" href="#ct-base_type_definition">{base type definition}</a> must also have one.</div><div class="clnumber">4.2 The complex
type definition's <a class="propref" href="#ct-attribute_wildcard">{attribute wildcard}</a>'s <a class="propref" href="#namespace_constraint">{namespace constraint}</a> must be a subset of the <a class="propref" href="#ct-base_type_definition">{base type definition}</a>'s <a class="propref" href="#ct-attribute_wildcard">{attribute wildcard}</a>'s <a class="propref" href="#namespace_constraint">{namespace constraint}</a>, as defined by <a href="#cos-ns-subset">Wildcard Subset (§3.10.6)</a>.</div><div class="clnumber">4.3 Unless the <a class="propref" href="#ct-base_type_definition">{base type definition}</a> is the <a class="termref" href="#ur-type-itself"><span class="arrow">·</span>ur-type definition<span class="arrow">·</span></a>, the complex
type definition's <a class="propref" href="#ct-attribute_wildcard">{attribute wildcard}</a>'s <a class="propref" href="#process_contents">{process contents}</a> must be identical
to or stronger than the <a class="propref" href="#ct-base_type_definition">{base type definition}</a>'s <a class="propref" href="#ct-attribute_wildcard">{attribute wildcard}</a>'s <a class="propref" href="#process_contents">{process contents}</a>, where
<i>strict</i> is stronger than <i>lax</i> is stronger than <i>skip</i>.</div></div>
</div><div class="clnumber">5 <b>One</b> of the following must be true:<div class="constraintlist"><div class="clnumber">5.1 The <a class="propref" href="#ct-base_type_definition">{base type definition}</a> must be the <a class="termref" href="#ur-type-itself"><span class="arrow">·</span>ur-type definition<span class="arrow">·</span></a>.</div><div class="clnumber">5.2 <b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">5.2.1 The <a class="propref" href="#content_type">{content type}</a> of the complex type definition
must be a simple type definition</div><div class="clnumber">5.2.2 <b>One</b> of the following must be true:<div class="constraintlist"><div class="clnumber">5.2.2.1 The <a class="propref" href="#content_type">{content type}</a> of the <a class="propref" href="#ct-base_type_definition">{base type definition}</a> must be a simple type
definition from which
the <a class="propref" href="#content_type">{content type}</a> is validly derived given the empty set as defined in
<a href="#cos-st-derived-ok">Type Derivation OK (Simple) (§3.14.6)</a>.</div><div class="clnumber">5.2.2.2 The <a class="propref" href="#ct-base_type_definition">{base type definition}</a> must be <i>mixed</i>
and have a particle which is <a class="termref" href="#cd-emptiable"><span class="arrow">·</span>emptiable<span class="arrow">·</span></a> as defined in <a href="#cos-group-emptiable">Particle Emptiable (§3.9.6)</a>.</div></div></div></div></div><div class="clnumber">5.3 <b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">5.3.1 The <a class="propref" href="#content_type">{content type}</a> of the complex type itself
must be <i>empty</i>
</div><div class="clnumber">5.3.2 <b>One</b> of the following must be true:<div class="constraintlist"><div class="clnumber">5.3.2.1 The <a class="propref" href="#content_type">{content type}</a> of the <a class="propref" href="#ct-base_type_definition">{base type definition}</a> must also be <i>empty</i>.</div><div class="clnumber">5.3.2.2 The <a class="propref" href="#content_type">{content type}</a> of the <a class="propref" href="#ct-base_type_definition">{base type definition}</a> must be <i>elementOnly</i> or <i>mixed</i> and have a particle which is <a class="termref" href="#cd-emptiable"><span class="arrow">·</span>emptiable<span class="arrow">·</span></a> as defined in <a href="#cos-group-emptiable">Particle Emptiable (§3.9.6)</a>.</div></div></div></div></div><div class="clnumber">5.4 <b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">5.4.1 <b>One</b> of the following must be true:<div class="constraintlist"><div class="clnumber">5.4.1.1 The <a class="propref" href="#content_type">{content type}</a> of the complex type
definition itself must be <i>element-only</i></div><div class="clnumber">5.4.1.2 The <a class="propref" href="#content_type">{content type}</a> of the complex
type definition itself and of the
<a class="propref" href="#ct-base_type_definition">{base type definition}</a> must be <i>mixed</i></div></div></div><div class="clnumber">5.4.2 The particle of the complex type definition itself
must be a <a class="termref" href="#cd-model-restriction"><span class="arrow">·</span>valid restriction<span class="arrow">·</span></a> of the particle of the <a class="propref" href="#content_type">{content type}</a> of the <a class="propref" href="#ct-base_type_definition">{base type definition}</a> as defined in <a href="#cos-particle-restrict">Particle Valid (Restriction) (§3.9.6)</a>.</div></div></div></div><div class="note"><b>Note: </b>Attempts to derive complex type definitions whose <a class="propref" href="#content_type">{content type}</a> is <i>element-only</i> by restricting
a <a class="propref" href="#ct-base_type_definition">{base type definition}</a> whose <a class="propref" href="#content_type">{content type}</a>
is <i>empty</i> are not ruled out by this clause. However if the complex
type definition itself has a non-pointless particle it will fail to satisfy
<a href="#cos-particle-restrict">Particle Valid (Restriction) (§3.9.6)</a>. On the other hand some type
definitions with pointless <i>element-only</i> content, for example an empty
<a class="eltref" href="#element-sequence"><sequence></a>, will satisfy <a href="#cos-particle-restrict">Particle Valid (Restriction) (§3.9.6)</a>
with respect to an <i>empty</i> <a class="propref" href="#ct-base_type_definition">{base type definition}</a>, and
so be valid restrictions.</div></div></div>
<span class="termdef"><a id="cd-ct-restriction" name="cd-ct-restriction">[Definition:]  </a>If this
constraint <a href="#derivation-ok-restriction">Derivation Valid (Restriction, Complex) (§3.4.6)</a> holds of a complex type definition, it is a <b>valid
restriction</b> of its <a class="propref" href="#ct-base_type_definition">{base type definition}</a></span>.
</div></div><div class="note"><b>Note: </b>To restrict a complex type definition with a simple base type definition
to <i>empty</i>, use a simple type definition with a <i>fixed</i> value of
the empty string: this preserves the type information.</div><p>The following constraint defines a relation appealed to elsewhere in this specification.</p><div class="constraintnote"><a name="cos-ct-derived-ok" id="cos-ct-derived-ok"/><b>Schema Component Constraint: Type Derivation OK (Complex)</b><br/><div class="constraint">For a complex type definition (call it <b>D</b>, for derived) to be validly
derived from a type definition (call this <b>B</b>, for base) given
a subset of {<i>extension</i>, <i>restriction</i>}
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 If <b>B</b> and <b>D</b> are not the same type definition, then
the <a class="propref" href="#derivation_method">{derivation method}</a> of <b>D</b> must not be in the subset.</div><div class="clnumber">2
<b>One</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.1<a name="c-tid" id="c-tid"> </a><b>B</b> and <b>D</b> must be the same type
definition.</div><div class="clnumber">2.2 <b>B</b> must be <b>D</b>'s <a class="propref" href="#ct-base_type_definition">{base type definition}</a>.</div><div class="clnumber">2.3
<b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.3.1 <b>D</b>'s <a class="propref" href="#ct-base_type_definition">{base type definition}</a> must not be the
<a class="termref" href="#ur-type-itself"><span class="arrow">·</span>ur-type definition<span class="arrow">·</span></a>.</div><div class="clnumber">2.3.2
The appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">2.3.2.1 <b>If </b><b>D</b>'s <a class="propref" href="#ct-base_type_definition">{base type definition}</a> is complex, <b>then </b>it must be validly derived
from <b>B</b> given the subset as defined by this constraint.</div><div class="clnumber">2.3.2.2 <b>If </b><b>D</b>'s <a class="propref" href="#ct-base_type_definition">{base type definition}</a> is simple, <b>then </b>it must be validly derived
from <b>B</b> given the subset as defined in <a href="#cos-st-derived-ok">Type Derivation OK (Simple) (§3.14.6)</a>.</div></div>
</div></div>
</div></div>
</div></div>
</div></div><div class="note"><b>Note: </b>This constraint is used to check that when someone uses a type in a
context where another type was expected (either via <code>xsi:type</code> or
substitution groups), that the type used is actually derived from the expected
type, and that that derivation does not involve a form of derivation which was
ruled out by the expected type.</div><div class="note"><a id="no-identity" name="no-identity"/><p class="prefix"><b>Note:</b></p>The wording of clause <a href="#c-tid">2.1</a> above appeals to a notion of component identity which
is only incompletely defined by this version of this specification.
In some cases, the wording of this specification does make clear the
rules for component identity. These cases include:
<ul><li>When they are both top-level components with the same component type,
namespace name, and local name;</li><li>When they are necessarily the same type definition (for example, when
the two types definitions in question are the type definitions associated with
two attribute or element declarations, which are discovered to be the same
declaration);</li><li>When they are the same by construction (for example, when an element's
type definition defaults to being the same type definition as that of its
substitution-group head or when a complex type definition inherits an attribute
declaration from its base type definition).</li></ul>
<p/>In other cases two conforming implementations may disagree as to whether
components are identical.</div></div><div class="div3">
<h4><a id="d0e9252" name="d0e9252"/>3.4.7 Built-in Complex Type Definition</h4><p>There is a complex type definition nearly equivalent to the <a class="termref" href="#key-urType"><span class="arrow">·</span>ur-type definition<span class="arrow">·</span></a> present in every
schema by definition. It has the following properties:</p><table border="1" class="schemaComp"><thead><tr><th><strong><a name="ur-type-itself" id="ur-type-itself">Complex Type Definition of the Ur-Type</a></strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Value</th></tr></thead><tbody valign="top"><tr><td><a class="propref" href="#ct-name">{name}</a></td><td>anyType</td></tr><tr><td><a class="propref" href="#ct-target_namespace">{target namespace}</a></td><td>http://www.w3.org/2001/XMLSchema</td></tr><tr><td><a class="propref" href="#ct-base_type_definition">{base type definition}</a></td><td>Itself</td></tr><tr><td><a class="propref" href="#derivation_method">{derivation method}</a></td><td><i>restriction</i></td></tr><tr><td><a class="propref" href="#content_type">{content type}</a></td><td>A pair consisting of <i>mixed</i> and a
particle with the following properties:
<table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Value</th></tr></thead><tbody valign="top"><tr><td><a class="propref" href="#p-min_occurs">{min occurs}</a></td><td>1</td></tr><tr><td><a class="propref" href="#p-max_occurs">{max occurs}</a></td><td>1</td></tr><tr><td><a class="propref" href="#term">{term}</a></td><td>a model group with
the following properties:
<table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Value</th></tr></thead><tbody valign="top"><tr><td><a class="propref" href="#compositor">{compositor}</a></td><td><i>sequence</i></td></tr><tr><td><a class="propref" href="#particles">{particles}</a></td><td>
a list containing one particle with the following properties:
<table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Value</th></tr></thead><tbody valign="top"><tr><td><a class="propref" href="#p-min_occurs">{min occurs}</a></td><td>0</td></tr><tr><td><a class="propref" href="#p-max_occurs">{max occurs}</a></td><td><i>unbounded</i></td></tr><tr><td><a class="propref" href="#term">{term}</a></td><td>a wildcard with the following properties:
<table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Value</th></tr></thead><tbody valign="top"><tr><td><a class="propref" href="#namespace_constraint">{namespace constraint}</a></td><td><i>any</i></td></tr><tr><td><a class="propref" href="#process_contents">{process contents}</a></td><td><i>lax</i></td></tr></tbody></table>
</td></tr></tbody></table>
</td></tr></tbody></table>
</td></tr></tbody></table>
</td></tr><tr><td><a class="propref" href="#ct-attribute_declarations">{attribute uses}</a></td><td>The empty set</td></tr><tr><td><a class="propref" href="#ct-attribute_wildcard">{attribute wildcard}</a></td><td>
a wildcard with the following properties::
<table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Value</th></tr></thead><tbody valign="top"><tr><td><a class="propref" href="#namespace_constraint">{namespace constraint}</a></td><td><i>any</i></td></tr><tr><td><a class="propref" href="#process_contents">{process contents}</a></td><td><i>lax</i></td></tr></tbody></table></td></tr><tr><td><a class="propref" href="#ct-final">{final}</a></td><td>The empty set</td></tr><tr><td><a class="propref" href="#ct-exact">{prohibited substitutions}</a></td><td>The empty set</td></tr><tr><td><a class="propref" href="#ct-abstract">{abstract}</a></td><td><i>false</i></td></tr></tbody></table></td></tr></tbody></table><p>The <code>mixed</code> content specification together with the
<i>lax</i> wildcard and attribute specification produce the defining property for the
<a class="termref" href="#key-urType"><span class="arrow">·</span>ur-type definition<span class="arrow">·</span></a>, namely that <em>every</em> type
definition is (eventually) a restriction
of the <a class="termref" href="#key-urType"><span class="arrow">·</span>ur-type definition<span class="arrow">·</span></a>: its permissions and requirements are
(nearly) the least restrictive possible.</p><div class="note"><b>Note: </b>This specification does not provide an inventory of built-in complex
type definitions for use in user schemas. A preliminary library of complex type
definitions is available which includes both mathematical (e.g.
<code>rational</code>) and utility (e.g. <code>array</code>) type definitions.
In particular, there is a <code>text</code> type definition which is recommended for use
as the type definition in element declarations intended for general text
content, as it makes sensible provision for various aspects of
internationalization. For more details, see the schema document for the type
library at its namespace name: <a href="http://www.w3.org/2001/03/XMLSchema/TypeLibrary.xsd">http://www.w3.org/2001/03/XMLSchema/TypeLibrary.xsd</a>.</div></div></div><div class="div2">
<h3 class="withToc"><span class="nav"><a class="nav" href="#Complex_Type_Definitions"><img src="previous.jpg" alt="previous sub-section"/></a> <a class="nav" href="#cAttribute_Group_Definitions"><img src="next.jpg" alt="next sub-section"/></a></span><a id="cAttributeUse" name="cAttributeUse"/>3.5 AttributeUses</h3><div class="localToc">        3.5.1 <a href="#AU_details">The Attribute Use Schema Component</a><br/>
        3.5.2 <a href="#d0e9471">XML Representation of Attribute Use Components</a><br/>
        3.5.3 <a href="#d0e9488">Constraints on XML Representations of Attribute Uses</a><br/>
        3.5.4 <a href="#d0e9493">Attribute Use Validation Rules</a><br/>
        3.5.5 <a href="#d0e9515">Attribute Use Information Set Contributions</a><br/>
        3.5.6 <a href="#coss-attruse">Constraints on Attribute Use Schema Components</a><br/>
</div><p>An attribute use is a utility component which controls the occurrence and
defaulting behavior of attribute declarations. It plays the same role for
attribute declarations in complex types that particles play for element declarations.</p><div class="exampleOuter"><div class="exampleHeader">Example</div><div class="exampleInner"><pre><xs:complexType>
. . .
<xs:attribute ref="xml:lang" use="required"/>
<xs:attribute ref="xml:space" default="preserve"/>
<xs:attribute name="version" type="xs:number" fixed="1.0"/>
</xs:complexType>
</pre></div><div class="exampleWrapper">XML representations which all involve attribute uses, illustrating some of
the possibilities for controlling occurrence.</div></div><div class="div3">
<h4><a id="AU_details" name="AU_details"/>3.5.1 The Attribute Use Schema Component</h4><p>The attribute use schema component has the following properties:</p><div class="schemaComp"><div class="compHeader"><span class="schemaComp">Schema Component</span>: <a href="#Attribute_Use">Attribute Use</a></div><div class="compBody">
<dl class="props">
<dt><a name="required" id="required"><span class="propdef">{required}</span></a></dt><dd>A boolean.</dd>
<dt><a name="attribute" id="attribute"><span class="propdef">{attribute declaration}</span></a></dt><dd>An attribute declaration.</dd>
<dt><a name="au-value_constraint" id="au-value_constraint"><span class="propdef">{value constraint}</span></a></dt><dd>Optional. A pair
consisting of a value and one of <i>default</i>, <i>fixed</i>.</dd> </dl>
</div></div><p><a class="propref" href="#required">{required}</a> determines whether this use of an attribute
declaration requires an appropriate attribute information item to be present, or
merely allows it.</p><p><a class="propref" href="#attribute">{attribute declaration}</a> provides the attribute declaration itself,
which will in turn determine the simple type definition used.</p><p><a class="propref" href="#au-value_constraint">{value constraint}</a> allows for local specification of a
default or fixed value. This must be consistent with that of the <a class="propref" href="#attribute">{attribute declaration}</a>, in that if the <a class="propref" href="#attribute">{attribute declaration}</a> specifies a fixed value, the only allowed <a class="propref" href="#au-value_constraint">{value constraint}</a> is the same fixed value.</p></div><div class="div3">
<h4><a id="d0e9471" name="d0e9471"/>3.5.2 XML Representation of Attribute Use Components</h4><p>Attribute uses correspond to all uses of <a class="eltref" href="#element-attribute"><attribute></a> which
allow a <code>use</code> attribute. These in turn correspond to
<em>two</em> components in each case, an attribute use and its <a class="propref" href="#attribute">{attribute declaration}</a> (although note the latter is not new when the attribute use is a reference to a top-level attribute declaration). The appropriate mapping is described in <a href="#declare-attribute">XML Representation of Attribute Declaration Schema Components (§3.2.2)</a>.</p></div><div class="div3">
<h4><a id="d0e9488" name="d0e9488"/>3.5.3 Constraints on XML Representations of Attribute Uses</h4><p>None as such.</p></div><div class="div3">
<h4><a id="d0e9493" name="d0e9493"/>3.5.4 Attribute Use Validation Rules</h4><div class="constraintnote"><a name="cvc-au" id="cvc-au"/><b>Validation Rule: Attribute Locally Valid (Use)</b><br/><div class="constraint">For an attribute information item to be<a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to an attribute use its <a class="termref" href="#key-nv"><span class="arrow">·</span>normalized value<span class="arrow">·</span></a> must match the <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#dt-canonical-representation">canonical lexical representation</a> of the attribute use's <a class="propref" href="#au-value_constraint">{value constraint}</a> value, if it is present and
<i>fixed</i>.</div></div></div><div class="div3">
<h4><a id="d0e9515" name="d0e9515"/>3.5.5 Attribute Use Information Set Contributions</h4><p>None as such.</p></div><div class="div3">
<h4><a id="coss-attruse" name="coss-attruse"/>3.5.6 Constraints on Attribute Use Schema Components</h4><p>All attribute uses (see <a href="#cAttributeUse">AttributeUses (§3.5)</a>) must satisfy the following constraints.</p><div class="constraintnote"><a name="au-props-correct" id="au-props-correct"/><b>Schema Component Constraint: Attribute Use Correct</b><br/><div class="constraint"><b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 The values of the properties of an attribute use must be as described in
the property tableau in
<a href="#AU_details">The Attribute Use Schema Component (§3.5.1)</a>, modulo the impact of <a href="#conformance-missing">Missing Sub-components (§5.3)</a>.</div><div class="clnumber">2 If the <a class="propref" href="#attribute">{attribute declaration}</a> has a <i>fixed</i> <a class="propref" href="#a-value_constraint">{value constraint}</a>, then if the attribute use itself has a <a class="propref" href="#au-value_constraint">{value constraint}</a>, it must also be <i>fixed</i> and its value must match that of the <a class="propref" href="#attribute">{attribute declaration}</a>'s <a class="propref" href="#a-value_constraint">{value constraint}</a>.</div></div></div></div></div></div><div class="div2">
<h3 class="withToc"><span class="nav"><a class="nav" href="#cAttributeUse"><img src="previous.jpg" alt="previous sub-section"/></a> <a class="nav" href="#cModel_Group_Definitions"><img src="next.jpg" alt="next sub-section"/></a></span><a id="cAttribute_Group_Definitions" name="cAttribute_Group_Definitions"/>3.6 Attribute Group Definitions</h3><div class="localToc">        3.6.1 <a href="#Attribute_Group_Definition_details">The Attribute Group Definition Schema Component</a><br/>
        3.6.2 <a href="#declare-attributeGroup">XML Representation of Attribute Group Definition Schema Components</a><br/>
        3.6.3 <a href="#d0e9758">Constraints on XML Representations of Attribute Group Definitions</a><br/>
        3.6.4 <a href="#d0e9831">Attribute Group Definition Validation Rules</a><br/>
        3.6.5 <a href="#d0e9836">Attribute Group Definition Information Set
Contributions</a><br/>
        3.6.6 <a href="#coss-attrGroup">Constraints on Attribute Group Definition Schema Components</a><br/>
</div><p>A schema can name a group of attribute declarations so that they may be incorporated as a
group into complex type definitions.</p><p>
Attribute group definitions do not participate in <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> as such, but the
<a class="propref" href="#ct-attribute_declarations">{attribute uses}</a> and <a class="propref" href="#ct-attribute_wildcard">{attribute wildcard}</a> of one or
more complex type definitions may be constructed in whole or part by reference
to an attribute group. Thus, attribute group definitions provide a
replacement for some uses of XML's
<a href="http://www.w3.org/TR/REC-xml#dt-PE">parameter entity</a> facility.
Attribute group definitions are provided primarily for reference from the XML
representation of schema components
(see <a class="eltref" href="#element-complexType"><complexType></a> and <a class="eltref" href="#element-simpleContent..attributeGroup"><attributeGroup></a>).
</p><div class="exampleOuter"><div class="exampleHeader">Example</div><div class="exampleInner"><pre><xs:attributeGroup name="myAttrGroup">
<xs:attribute . . ./>
. . .
</xs:attributeGroup>
<xs:complexType name="myelement">
. . .
<xs:attributeGroup ref="myAttrGroup"/>
</xs:complexType>
</pre></div><div class="exampleWrapper">XML representations for attribute group definitions. The effect is as if the attribute
declarations in the group were present in the type definition.</div></div><div class="div3">
<h4><a id="Attribute_Group_Definition_details" name="Attribute_Group_Definition_details"/>3.6.1 The Attribute Group Definition Schema Component</h4><p>The attribute group definition schema component has the
following properties:</p><div class="schemaComp"><div class="compHeader"><span class="schemaComp">Schema Component</span>: <a href="#Attribute_Group_Definition">Attribute Group Definition</a></div><div class="compBody">
<dl class="props">
<dt><a name="ag-name" id="ag-name"><span class="propdef">{name}</span></a></dt><dd>
An NCName as defined by <a href="#ref-xml-namespaces">[XML-Namespaces]</a>.
</dd>
<dt><a name="ag-target_namespace" id="ag-target_namespace"><span class="propdef">{target namespace}</span></a></dt><dd>
Either <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> or a namespace name, as defined in <a href="#ref-xml-namespaces">[XML-Namespaces]</a>.
</dd>
<dt><a name="ag-attribute_declarations" id="ag-attribute_declarations"><span class="propdef">{attribute uses}</span></a></dt><dd>
A set of attribute uses.
</dd>
<dt><a name="ag-attribute_wildcard" id="ag-attribute_wildcard"><span class="propdef">{attribute wildcard}</span></a></dt><dd>
Optional. A wildcard.
</dd>
<dt><a name="ag-annotation" id="ag-annotation"><span class="propdef">{annotation}</span></a></dt><dd>Optional. An annotation.</dd>
</dl>
</div></div><p>Attribute groups are identified by their <a class="propref" href="#ag-name">{name}</a> and <a class="propref" href="#ag-target_namespace">{target namespace}</a>; attribute group identities must be unique within an <a class="termref" href="#key-schema"><span class="arrow">·</span>XML Schema<span class="arrow">·</span></a>. See <a href="#composition-schemaImport">References to schema components across namespaces (§4.2.3)</a> for the use of component
identifiers when importing one schema into another.</p><p><a class="propref" href="#ag-attribute_declarations">{attribute uses}</a> is a set attribute uses, allowing
for local specification of occurrence and default or fixed values.</p><p><a class="propref" href="#ag-attribute_wildcard">{attribute wildcard}</a> provides for an attribute wildcard to be included in an
attribute group.
See above under <a href="#Complex_Type_Definitions">Complex Type Definitions (§3.4)</a> for the
interpretation of
attribute wildcards during <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a>.</p><p>See <a href="#cAnnotations">Annotations (§3.13)</a> for information on the role of the
<a class="propref" href="#ag-annotation">{annotation}</a> property.</p></div><div class="div3">
<h4><a id="declare-attributeGroup" name="declare-attributeGroup"/>3.6.2 XML Representation of Attribute Group Definition Schema Components</h4><p>The XML representation for an attribute group definition schema component is an
<a class="eltref" href="#element-attributeGroup"><attributeGroup></a> element information item. It provides for
naming a group of attribute declarations and an attribute wildcard for use by reference in the XML representation of
complex type definitions and other attribute group definitions. The correspondences between the
properties of the information item and
properties of the component it corresponds to are as follows:</p><div class="reprdef"><div class="reprHeader"><span class="reprdef">XML Representation Summary</span>: <code>attributeGroup</code> Element Information Item</div><div class="reprBody">
<p class="element-syntax-1"><a name="element-attributeGroup" id="element-attributeGroup"><attributeGroup</a><br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  name = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#NCName">NCName</a><br/>  ref = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#QName">QName</a><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?, ((<a class="eltref" href="#element-attribute">attribute</a> | <a class="eltref" href="#element-attributeGroup">attributeGroup</a>)*, <a class="eltref" href="#element-anyAttribute">anyAttribute</a>?))<br/></attributeGroup></p>
<div class="reprdep">When an <a class="eltref" href="#element-attributeGroup"><attributeGroup></a> appears as a daughter of
<a class="eltref" href="#element-schema"><schema></a> or <a class="eltref" href="#element-redefine"><redefine></a>, it corresponds to an attribute group definition as
below. When it appears as a daughter of <a class="eltref" href="#element-complexType"><complexType></a> or <a class="eltref" href="#element-attributeGroup"><attributeGroup></a>, it does not correspond to any component as such.</div>
<div class="reprcomp"><table class="reprcomp"><thead><tr><th><a href="#Attribute_Group_Definition_details">Attribute Group Definition</a><strong> Schema Component</strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Representation</th></tr></thead><tbody valign="top"><tr valign="top"><td><a class="propref" href="#ag-name">{name}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>name</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a></td></tr><tr valign="top"><td><a class="propref" href="#ag-target_namespace">{target namespace}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the
<code>targetNamespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of the parent <code>schema</code>
element information item.</td></tr><tr valign="top"><td><a class="propref" href="#ag-attribute_declarations">{attribute uses}</a></td><td>The union of the set of attribute uses corresponding to the <a class="eltref" href="#element-attribute"><attribute></a> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if any, with the <a class="propref" href="#ag-attribute_declarations">{attribute uses}</a> of the
attribute groups <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to by the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a>s of the <code>ref</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of the <a class="eltref" href="#element-simpleContent..attributeGroup"><attributeGroup></a> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if any.</td></tr><tr valign="top"><td><a class="propref" href="#ag-attribute_wildcard">{attribute wildcard}</a></td><td>As for the <a class="termref" href="#key-eaw"><span class="arrow">·</span>complete wildcard<span class="arrow">·</span></a> as described in <a href="#declare-type">XML Representation of Complex Type Definitions (§3.4.2)</a>.</td></tr><tr valign="top"><td><a class="propref" href="#ag-annotation">{annotation}</a></td><td>The annotation corresponding to the <a class="eltref" href="#element-annotation"><annotation></a> element information item in the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if present, otherwise <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</td></tr></tbody></table></td></tr></tbody></table></div></div></div><p>The example above illustrates a pattern which
recurs in the XML representation of schemas: The same element, in this case <code>attributeGroup</code>, serves both to
define and to incorporate by reference. In the first case the
<code>name</code> attribute is required, in the second the <code>ref</code>
attribute is required, and the element must be empty. These two are mutually exclusive, and also conditioned
by context: the defining form, with a <code>name</code>, must occur at the top
level of a schema, whereas the referring form, with a <code>ref</code>, must
occur within a complex type definition or an attribute group definition.</p></div><div class="div3">
<h4><a id="d0e9758" name="d0e9758"/>3.6.3 Constraints on XML Representations of Attribute Group Definitions</h4><div class="constraintnote"><a name="src-attribute_group" id="src-attribute_group"/><b>Schema Representation Constraint: Attribute Group Definition Representation OK</b><br/><div class="constraint">In addition to the conditions imposed on <a class="eltref" href="#element-attributeGroup"><attributeGroup></a> element
information items by the schema for schemas,
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 The corresponding attribute group definition, if any, must satisfy the conditions set
out in <a href="#coss-attrGroup">Constraints on Attribute Group Definition Schema Components (§3.6.6)</a>.</div><div class="clnumber">2 If clause <a href="#c-awi1">2.2.1</a> or clause <a href="#c-awi2">2.2.2</a> in the correspondence specification in <a href="#declare-type">XML Representation of Complex Type Definitions (§3.4.2)</a> for <a class="propref" href="#ct-attribute_wildcard">{attribute wildcard}</a>, as referenced above, is satisfied, the intensional intersection must be expressible, as defined in <a href="#cos-aw-intersect">Attribute Wildcard Intersection (§3.10.6)</a>.</div><div class="clnumber">3 Circular group reference is disallowed outside <a class="eltref" href="#element-redefine"><redefine></a>. That is, unless this element information item's parent is <a class="eltref" href="#element-redefine"><redefine></a>, then among the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if any, there must not be an <a class="eltref" href="#element-simpleContent..attributeGroup"><attributeGroup></a> with <code>ref</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> which resolves to the component corresponding to this <a class="eltref" href="#element-attributeGroup"><attributeGroup></a>. Indirect circularity is also ruled out. That is, when <a href="#src-resolve">QName resolution (Schema Document) (§3.15.3)</a> is applied to a <a class="termref" href="#gloss-QName"><span class="arrow">·</span>QName<span class="arrow">·</span></a> arising from any <a class="eltref" href="#element-simpleContent..attributeGroup"><attributeGroup></a>s with a
<code>ref</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> among the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, it must not be the case that a <a class="termref" href="#gloss-QName"><span class="arrow">·</span>QName<span class="arrow">·</span></a> is
encountered at any depth which resolves to the
component corresponding to this <a class="eltref" href="#element-attributeGroup"><attributeGroup></a>.</div></div>
</div></div></div><div class="div3">
<h4><a id="d0e9831" name="d0e9831"/>3.6.4 Attribute Group Definition Validation Rules</h4><p>None as such.</p></div><div class="div3">
<h4><a id="d0e9836" name="d0e9836"/>3.6.5 Attribute Group Definition Information Set
Contributions</h4><p>None as such.</p></div><div class="div3">
<h4><a id="coss-attrGroup" name="coss-attrGroup"/>3.6.6 Constraints on Attribute Group Definition Schema Components</h4><p>All attribute group definitions (see <a href="#cAttribute_Group_Definitions">Attribute Group Definitions (§3.6)</a>) must satisfy the following constraint.</p><div class="constraintnote"><a name="ag-props-correct" id="ag-props-correct"/><b>Schema Component Constraint: Attribute Group Definition Properties Correct</b><br/><div class="constraint"><b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 The values of the properties of an attribute group definition must be as described in
the property tableau in
<a href="#Attribute_Group_Definition_details">The Attribute Group Definition Schema Component (§3.6.1)</a>, modulo the impact of <a href="#conformance-missing">Missing Sub-components (§5.3)</a>;</div><div class="clnumber">2 Two distinct members of the <a class="propref" href="#ag-attribute_declarations">{attribute uses}</a>
must not have <a class="propref" href="#attribute">{attribute declaration}</a>s both of whose <a class="propref" href="#a-name">{name}</a>s
match and whose <a class="propref" href="#a-target_namespace">{target namespace}</a>s are identical.</div><div class="clnumber">3 Two distinct members of the <a class="propref" href="#ag-attribute_declarations">{attribute uses}</a>
must not have <a class="propref" href="#attribute">{attribute declaration}</a>s both of whose <a class="propref" href="#a-simple_type_definition">{type definition}</a>s are or are derived from <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a>.</div></div></div></div></div></div><div class="div2">
<h3 class="withToc"><span class="nav"><a class="nav" href="#cAttribute_Group_Definitions"><img src="previous.jpg" alt="previous sub-section"/></a> <a class="nav" href="#Model_Groups"><img src="next.jpg" alt="next sub-section"/></a></span><a id="cModel_Group_Definitions" name="cModel_Group_Definitions"/>3.7 Model Group Definitions</h3><div class="localToc">        3.7.1 <a href="#Model_Group_Definition_details">The Model Group Definition Schema Component</a><br/>
        3.7.2 <a href="#declare-namedModelGroup">XML Representation of Model Group Definition Schema Components</a><br/>
        3.7.3 <a href="#d0e10150">Constraints on XML Representations of Model Group Definitions</a><br/>
        3.7.4 <a href="#d0e10162">Model Group Definition Validation Rules</a><br/>
        3.7.5 <a href="#d0e10167">Model Group Definition Information Set Contributions</a><br/>
        3.7.6 <a href="#coss-groupDef">Constraints on Model Group Definition Schema Components</a><br/>
</div><p>A model group definition associates a name and optional annotations with a <a href="#Model_Group">Model Group (§2.2.3.1)</a>.
By reference to the name, the entire model group can be incorporated by reference into a <a class="propref" href="#term">{term}</a>.</p><p>
Model group definitions are provided
primarily for reference from the <a href="#declare-type">XML Representation of Complex Type Definitions (§3.4.2)</a> (see <a class="eltref" href="#element-complexType"><complexType></a>
and <a class="eltref" href="#element-group"><group></a>). Thus, model group definitions provide a
replacement for some uses of XML's
<a href="http://www.w3.org/TR/REC-xml#dt-PE">parameter entity</a> facility.
</p><div class="exampleOuter"><div class="exampleHeader">Example</div><div class="exampleInner"><pre><xs:group name="myModelGroup">
<xs:sequence>
<xs:element ref="someThing"/>
. . .
</xs:sequence>
</xs:group>
<xs:complexType name="trivial">
<xs:group ref="myModelGroup"/>
<xs:attribute .../>
</xs:complexType>
<xs:complexType name="moreSo">
<xs:choice>
<xs:element ref="anotherThing"/>
<xs:group ref="myModelGroup"/>
</xs:choice>
<xs:attribute .../>
</xs:complexType></pre></div><div class="exampleWrapper">A minimal model group is defined and used by reference, first as the whole
content model, then as one alternative in a choice. </div></div><div class="div3">
<h4><a id="Model_Group_Definition_details" name="Model_Group_Definition_details"/>3.7.1 The Model Group Definition Schema Component</h4><p>The model group definition schema component has the following
properties:</p><div class="schemaComp"><div class="compHeader"><span class="schemaComp">Schema Component</span>: <a href="#Model_Group_Definition">Model Group Definition</a></div><div class="compBody">
<dl class="props">
<dt><a name="mg-name" id="mg-name"><span class="propdef">{name}</span></a></dt><dd>
An NCName as defined by <a href="#ref-xml-namespaces">[XML-Namespaces]</a>.
</dd>
<dt><a name="mg-target_namespace" id="mg-target_namespace"><span class="propdef">{target namespace}</span></a></dt><dd>
Either <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> or a namespace name, as defined in <a href="#ref-xml-namespaces">[XML-Namespaces]</a>.
</dd>
<dt><a name="model_group" id="model_group"><span class="propdef">{model group}</span></a></dt><dd>
A model group.
</dd>
<dt><a name="mg-annotation" id="mg-annotation"><span class="propdef">{annotation}</span></a></dt><dd>Optional. An annotation.</dd>
</dl>
</div></div><p>Model group definitions are identified by their <a class="propref" href="#mg-name">{name}</a> and <a class="propref" href="#mg-target_namespace">{target namespace}</a>; model group identities must be unique within an <a class="termref" href="#key-schema"><span class="arrow">·</span>XML Schema<span class="arrow">·</span></a>. See <a href="#composition-schemaImport">References to schema components across namespaces (§4.2.3)</a> for the use of component
identifiers when importing one schema into another.</p><p>Model group definitions <em>per se</em> do not participate in <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a>, but the <a class="propref" href="#term">{term}</a> of
a particle may correspond in whole or in part
to a model group from a model group definition.</p><p><a class="propref" href="#model_group">{model group}</a> is the <a href="#Model_Group">Model Group (§2.2.3.1)</a> for which the model group definition provides a name.</p><p>See <a href="#cAnnotations">Annotations (§3.13)</a> for information on the role of the
<a class="propref" href="#mg-annotation">{annotation}</a> property.</p></div><div class="div3">
<h4><a id="declare-namedModelGroup" name="declare-namedModelGroup"/>3.7.2 XML Representation of Model Group Definition Schema Components</h4><p>The XML representation for a model group definition schema component is a
<a class="eltref" href="#element-group"><group></a> element information item. It provides for
naming a model group for use by reference in the XML representation of
complex type definitions and model groups. The correspondences between the
properties of the information item and
properties of the component it corresponds to are as follows:</p><div class="reprdef"><div class="reprHeader"><span class="reprdef">XML Representation Summary</span>: <code>group</code> Element Information Item</div><div class="reprBody">
<p class="element-syntax-1"><a name="element-group" id="element-group"><group</a><br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  maxOccurs =
(<a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#nonNegativeInteger">nonNegativeInteger</a> | <var>unbounded</var>)
 : 1<br/>  minOccurs = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#nonNegativeInteger">nonNegativeInteger</a> : 1<br/>  name = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#NCName">NCName</a><br/>  ref = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#QName">QName</a><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?, (<a class="eltref" href="#element-all">all</a> | <a class="eltref" href="#element-choice">choice</a> | <a class="eltref" href="#element-sequence">sequence</a>)?)<br/></group></p>
<div class="reprdep">If there is a <code>name</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> (in which case the
item will have <a class="eltref" href="#element-schema"><schema></a> or <a class="eltref" href="#element-redefine"><redefine></a> as parent), then the item corresponds to
a model group definition component with properties as follows:</div>
<div class="reprcomp"><table class="reprcomp"><thead><tr><th><a href="#Model_Group_Definition_details">Model Group Definition</a><strong> Schema Component</strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Representation</th></tr></thead><tbody valign="top"><tr valign="top"><td><a class="propref" href="#mg-name">{name}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the
<code>name</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a></td></tr><tr valign="top"><td><a class="propref" href="#mg-target_namespace">{target namespace}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the
<code>targetNamespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of the parent <code>schema</code>
element information item.</td></tr><tr valign="top"><td><a class="propref" href="#model_group">{model group}</a></td><td>A model group which is the <a class="propref" href="#term">{term}</a> of a
particle corresponding to the <a class="eltref" href="#element-all"><all></a>, <a class="eltref" href="#element-choice"><choice></a> or
<a class="eltref" href="#element-sequence"><sequence></a> among the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> (there must be one).</td></tr><tr valign="top"><td><a class="propref" href="#mg-annotation">{annotation}</a></td><td>The annotation corresponding to the <a class="eltref" href="#element-annotation"><annotation></a> element information item in the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if present, otherwise <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</td></tr></tbody></table></td></tr></tbody></table></div>
<div class="reprdep">Otherwise, the item will have a <code>ref</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>,
in which case it corresponds to a particle component with properties as follows (unless <code>minOccurs=maxOccurs=0</code>, in which case the item
corresponds to no component at all):</div>
<div class="reprcomp"><table class="reprcomp"><thead><tr><th><a href="#Particle">Particle</a><strong> Schema Component</strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Representation</th></tr></thead><tbody valign="top"><tr valign="top"><td><a class="propref" href="#p-min_occurs">{min occurs}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>minOccurs</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, if present, otherwise <code>1</code>.</td></tr><tr valign="top"><td><a class="propref" href="#p-max_occurs">{max occurs}</a></td><td><i>unbounded</i>, if the <code>maxOccurs</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> equals <i>unbounded</i>, otherwise the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>maxOccurs</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, if present, otherwise <code>1</code>.</td></tr><tr valign="top"><td><a class="propref" href="#term">{term}</a></td><td>The <a class="propref" href="#model_group">{model group}</a> of the
model group definition <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to by the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>ref</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a></td></tr></tbody></table></td></tr></tbody></table></div>
</div></div><p>The name of this section is slightly misleading, in that the second, un-named,
case above (with a
<code>ref</code> and no <code>name</code>) is not really a named model
group at all, but a reference to one. Also note that in the first (named)
case above no reference is made to <code>minOccurs</code> or
<code>maxOccurs</code>: this is because the schema for schemas does not allow
them on the child of <a class="eltref" href="#element-group"><group></a> when it is named. This in turn is
because the <a class="propref" href="#p-min_occurs">{min occurs}</a> and <a class="propref" href="#p-max_occurs">{max occurs}</a> of
the particles which <em>refer</em> to the definition are what count.</p><p>Given the constraints on its appearance in content models, an
<a class="eltref" href="#element-all"><all></a> should only occur as the only item in the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> of a named model group definition or a content model: see <a href="#coss-modelGroup">Constraints on Model Group Schema Components (§3.8.6)</a>.</p></div><div class="div3">
<h4><a id="d0e10150" name="d0e10150"/>3.7.3 Constraints on XML Representations of Model Group Definitions</h4><div class="constraintnote"><a name="src-model_group_defn" id="src-model_group_defn"/><b>Schema Representation Constraint: Model Group Definition Representation OK</b><br/><div class="constraint">In addition to the conditions imposed on <a class="eltref" href="#element-group"><group></a> element
information items by the schema for schemas, the corresponding model group definition, if any, must satisfy the conditions set
out in <a href="#coss-modelGroup">Constraints on Model Group Schema Components (§3.8.6)</a>.
</div></div></div><div class="div3">
<h4><a id="d0e10162" name="d0e10162"/>3.7.4 Model Group Definition Validation Rules</h4><p>None as such.</p></div><div class="div3">
<h4><a id="d0e10167" name="d0e10167"/>3.7.5 Model Group Definition Information Set Contributions</h4><p>None as such.</p></div><div class="div3">
<h4><a id="coss-groupDef" name="coss-groupDef"/>3.7.6 Constraints on Model Group Definition Schema Components</h4><p>All model group definitions (see <a href="#cModel_Group_Definitions">Model Group Definitions (§3.7)</a>) must satisfy the following constraint.</p><div class="constraintnote"><a name="mgd-props-correct" id="mgd-props-correct"/><b>Schema Component Constraint: Model Group Definition Properties Correct</b><br/><div class="constraint">The values of the properties of a model group definition must be as described in
the property tableau in
<a href="#Model_Group_Definition_details">The Model Group Definition Schema Component (§3.7.1)</a>, modulo the impact of <a href="#conformance-missing">Missing Sub-components (§5.3)</a>.</div></div></div></div><div class="div2">
<h3 class="withToc"><span class="nav"><a class="nav" href="#cModel_Group_Definitions"><img src="previous.jpg" alt="previous sub-section"/></a> <a class="nav" href="#cParticles"><img src="next.jpg" alt="next sub-section"/></a></span><a id="Model_Groups" name="Model_Groups"/>3.8 Model Groups</h3><div class="localToc">        3.8.1 <a href="#Model_Group_details">The Model Group Schema Component</a><br/>
        3.8.2 <a href="#declare-contentModel">XML Representation of Model Group Schema Components</a><br/>
        3.8.3 <a href="#d0e10427">Constraints on XML Representations of Model Groups</a><br/>
        3.8.4 <a href="#d0e10445">Model Group Validation Rules</a><br/>
        3.8.5 <a href="#d0e10582">Model Group Information Set Contributions</a><br/>
        3.8.6 <a href="#coss-modelGroup">Constraints on Model Group Schema Components</a><br/>
</div><p>When the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> of element information items are not constrained
to be <i>empty</i> or by reference to a simple type definition
(<a href="#Simple_Type_Definitions">Simple Type Definitions (§3.14)</a>), the sequence of element
information item <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> content may be specified in
more detail with a model group. Because the <a class="propref" href="#term">{term}</a> property of a particle can be a
model group, and model groups contain particles, model groups can indirectly contain other model groups; the grammar for content models
is therefore recursive.</p><div class="exampleOuter"><div class="exampleHeader">Example</div><div class="exampleInner"><pre><xs:all>
<xs:element ref="cats"/>
<xs:element ref="dogs"/>
</xs:all>
<xs:sequence>
<xs:choice>
<xs:element ref="left"/>
<xs:element ref="right"/>
</xs:choice>
<xs:element ref="landmark"/>
</xs:sequence>
</pre></div><div class="exampleWrapper">XML representations for the three kinds of model group, the third nested
inside the second.</div></div><div class="div3">
<h4><a id="Model_Group_details" name="Model_Group_details"/>3.8.1 The Model Group Schema Component</h4><p>The model group schema component has the following
properties:</p><div class="schemaComp"><div class="compHeader"><span class="schemaComp">Schema Component</span>: <a href="#Model_Group">Model Group</a></div><div class="compBody">
<dl class="props">
<dt><a name="compositor" id="compositor"><span class="propdef">{compositor}</span></a></dt><dd>
One of <i>all</i>, <i>choice</i> or <i>sequence</i>.
</dd>
<dt><a name="particles" id="particles"><span class="propdef">{particles}</span></a></dt><dd>
A list of particles
</dd>
<dt><a name="amg-annotation" id="amg-annotation"><span class="propdef">{annotation}</span></a></dt><dd>Optional. An annotation.</dd>
</dl>
</div></div><p>specifies a sequential (<i>sequence</i>),
disjunctive (<i>choice</i>) or conjunctive (<i>all</i>) interpretation of
the <a class="propref" href="#particles">{particles}</a>. This in turn
determines whether the element
information item <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> <a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a> by the model group must:
</p><ul><li>(<i>sequence</i>) correspond, in order, to the specified <a class="propref" href="#particles">{particles}</a>;</li><li>(<i>choice</i>) corresponded to exactly one of the specified <a class="propref" href="#particles">{particles}</a>;</li><li>(<i>all</i>) contain all and only exactly zero or one of each
element specified in <a class="propref" href="#particles">{particles}</a>. The elements can occur in any
order. In this case, to reduce implementation complexity, <a class="propref" href="#particles">{particles}</a> is restricted to contain local and top-level element
declarations only, with <a class="propref" href="#p-min_occurs">{min occurs}</a><code>=0</code> or
<code>1</code>, <a class="propref" href="#p-max_occurs">{max occurs}</a><code>=1</code>.</li></ul><p>When two or more particles contained directly or indirectly in the
<a class="propref" href="#particles">{particles}</a> of a model group have identically named
element declarations as their
<a class="propref" href="#term">{term}</a>, the type definitions of those declarations must be the
same. By 'indirectly' is meant particles within the <a class="propref" href="#particles">{particles}</a>
of a group which is itself the <a class="propref" href="#term">{term}</a> of a directly contained
particle, and so on recursively.</p><p>See <a href="#cAnnotations">Annotations (§3.13)</a> for information on the role of the
<a class="propref" href="#amg-annotation">{annotation}</a> property.</p></div><div class="div3">
<h4><a id="declare-contentModel" name="declare-contentModel"/>3.8.2 XML Representation of Model Group Schema Components</h4><p>The XML representation for a model group schema component is
either an
<a class="eltref" href="#element-all"><all></a>, a <a class="eltref" href="#element-choice"><choice></a> or a <a class="eltref" href="#element-sequence"><sequence></a>
element information item. The correspondences between the
properties of those information items and
properties of the component they correspond to are as follows:</p><div class="reprdef"><div class="reprHeader"><span class="reprdef">XML Representation Summary</span>: <code>all</code> Element Information Item</div><div class="reprBody">
<p class="element-syntax-1"><a name="element-all" id="element-all"><all</a><br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  maxOccurs = <var>1</var> : 1<br/>  minOccurs = (<var>0</var> | <var>1</var>) : 1<br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?, <a class="eltref" href="#element-element">element</a>*)<br/></all></p>
<p class="element-syntax"><a name="element-choice" id="element-choice"><choice</a><br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  maxOccurs =
(<a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#nonNegativeInteger">nonNegativeInteger</a> | <var>unbounded</var>)
 : 1<br/>  minOccurs = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#nonNegativeInteger">nonNegativeInteger</a> : 1<br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?, (<a class="eltref" href="#element-element">element</a> | <a class="eltref" href="#element-group">group</a> | <a class="eltref" href="#element-choice">choice</a> | <a class="eltref" href="#element-sequence">sequence</a> | <a class="eltref" href="#element-any">any</a>)*)<br/></choice></p>
<p class="element-syntax"><a name="element-sequence" id="element-sequence"><sequence</a><br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  maxOccurs =
(<a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#nonNegativeInteger">nonNegativeInteger</a> | <var>unbounded</var>)
 : 1<br/>  minOccurs = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#nonNegativeInteger">nonNegativeInteger</a> : 1<br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?, (<a class="eltref" href="#element-element">element</a> | <a class="eltref" href="#element-group">group</a> | <a class="eltref" href="#element-choice">choice</a> | <a class="eltref" href="#element-sequence">sequence</a> | <a class="eltref" href="#element-any">any</a>)*)<br/></sequence></p>
<div class="reprdep">Each of the above items corresponds to a particle containing a model
group, with properties as follows (unless <code>minOccurs=maxOccurs=0</code>, in which case the item
corresponds to no component at all):</div>
<div class="reprcomp"><table class="reprcomp"><thead><tr><th><a href="#Particle_details">Particle</a><strong> Schema Component</strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Representation</th></tr></thead><tbody valign="top"><tr valign="top"><td><a class="propref" href="#p-min_occurs">{min occurs}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>minOccurs</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, if present, otherwise <code>1</code>.</td></tr><tr valign="top"><td><a class="propref" href="#p-max_occurs">{max occurs}</a></td><td><i>unbounded</i>, if the <code>maxOccurs</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> equals <i>unbounded</i>, otherwise the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>maxOccurs</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, if present, otherwise <code>1</code>.</td></tr><tr valign="top"><td><a class="propref" href="#term">{term}</a></td><td>A model group as given below:</td></tr></tbody></table></td></tr></tbody></table></div><div class="reprcomp"><table class="reprcomp"><thead><tr><th><a href="#Model_Group_details">Model Group</a><strong> Schema Component</strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Representation</th></tr></thead><tbody valign="top"><tr valign="top"><td><a class="propref" href="#compositor">{compositor}</a></td><td>One of <i>all</i>, <i>choice</i>,
<i>sequence</i> depending on the element information item.</td></tr><tr valign="top"><td><a class="propref" href="#particles">{particles}</a></td><td>A sequence of particles
corresponding to all the <a class="eltref" href="#element-all"><all></a>, <a class="eltref" href="#element-choice"><choice></a>,
<a class="eltref" href="#element-sequence"><sequence></a>, <a class="eltref" href="#element-any"><any></a>,
<a class="eltref" href="#element-group"><group></a> or <a class="eltref" href="#element-element"><element></a> items among the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>,
in order.</td></tr><tr valign="top"><td><a class="propref" href="#amg-annotation">{annotation}</a></td><td>The annotation corresponding to the <a class="eltref" href="#element-annotation"><annotation></a> element information item in the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if present, otherwise <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</td></tr></tbody></table></td></tr></tbody></table></div>
</div></div></div><div class="div3">
<h4><a id="d0e10427" name="d0e10427"/>3.8.3 Constraints on XML Representations of Model Groups</h4><div class="constraintnote"><a name="src-model_group" id="src-model_group"/><b>Schema Representation Constraint: Model Group Representation OK</b><br/><div class="constraint">In addition to the conditions imposed on <a class="eltref" href="#element-all"><all></a>, <a class="eltref" href="#element-choice"><choice></a> and <a class="eltref" href="#element-sequence"><sequence></a> element
information items by the schema for schemas, the corresponding particle and model group must satisfy the conditions set
out in <a href="#coss-modelGroup">Constraints on Model Group Schema Components (§3.8.6)</a> and <a href="#coss-particle">Constraints on Particle Schema Components (§3.9.6)</a>.
</div></div></div><div class="div3">
<h4><a id="d0e10445" name="d0e10445"/>3.8.4 Model Group Validation Rules</h4><div class="constraintnote"><a name="cvc-model-group" id="cvc-model-group"/><b>Validation Rule: Element Sequence Valid</b><br/><div class="constraint"><span class="termdef"><a id="key-partition" name="key-partition">[Definition:]  </a>Define a
<b>partition</b> of a sequence as a sequence of sub-sequences, some or
all of which may be empty, such that concatenating all the sub-sequences yields
the original sequence</span>.<p/>For a sequence (possibly empty) of element information items to be
locally <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to
a model group
the appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">1 <b>If </b>the <a class="propref" href="#compositor">{compositor}</a> is <i>sequence</i>, <b>then </b>there must be a
<a class="termref" href="#key-partition"><span class="arrow">·</span>partition<span class="arrow">·</span></a> of the sequence into <code>n</code> sub-sequences where <code>n</code> is the length of <a class="propref" href="#particles">{particles}</a> such that each of the sub-sequences in order is <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a>
with respect to the corresponding particle in the <a class="propref" href="#particles">{particles}</a> as defined in <a href="#cvc-particle">Element Sequence Locally Valid (Particle) (§3.9.4)</a>.</div><div class="clnumber">2 <b>If </b>the <a class="propref" href="#compositor">{compositor}</a> is <i>choice</i>, <b>then </b>there must be a
particle among the <a class="propref" href="#particles">{particles}</a> such that the sequence is
<a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to that particle as defined in <a href="#cvc-particle">Element Sequence Locally Valid (Particle) (§3.9.4)</a>.</div><div class="clnumber">3 <b>If </b>the <a class="propref" href="#compositor">{compositor}</a> is <i>all</i>, <b>then </b>there must be a
<a class="termref" href="#key-partition"><span class="arrow">·</span>partition<span class="arrow">·</span></a> of the sequence into <code>n</code> sub-sequences where <code>n</code> is the length of <a class="propref" href="#particles">{particles}</a> such that there is a one-to-one mapping between the sub-sequences and the <a class="propref" href="#particles">{particles}</a> where each sub-sequence is <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to the corresponding particle as defined in <a href="#cvc-particle">Element Sequence Locally Valid (Particle) (§3.9.4)</a>.</div></div>
<p/>Nothing in the above should be understood as ruling out groups whose
<a class="propref" href="#particles">{particles}</a> is empty: although no sequence can be <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a>
with respect to such a group whose <a class="propref" href="#compositor">{compositor}</a> is
<i>choice</i>, the empty sequence <em>is</em> <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect
to empty groups whose <a class="propref" href="#compositor">{compositor}</a> is <i>sequence</i> or <i>all</i>.</div></div><div class="note"><b>Note: </b>The above definition is implicitly non-deterministic, and should not be
taken as a recipé for implementations. Note in particular that when
<a class="propref" href="#compositor">{compositor}</a> is <i>all</i>, particles is restricted to a list
of local and top-level element declarations (see <a href="#coss-modelGroup">Constraints on Model Group Schema Components (§3.8.6)</a>). A much simpler implementation is possible than would arise from a literal interpretation of the definition above; informally, the content is <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> when each declared element occurs exactly once (or at most once, if <a class="propref" href="#p-min_occurs">{min occurs}</a> is <code>0</code>), and each is <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to its corresponding declaration. The elements can occur in arbitrary order.</div></div><div class="div3">
<h4><a id="d0e10582" name="d0e10582"/>3.8.5 Model Group Information Set Contributions</h4><p>None as such.</p></div><div class="div3">
<h4><a id="coss-modelGroup" name="coss-modelGroup"/>3.8.6 Constraints on Model Group Schema Components</h4><p>All model groups (see <a href="#Model_Groups">Model Groups (§3.8)</a>) must satisfy the following constraints.</p><div class="constraintnote"><a name="mg-props-correct" id="mg-props-correct"/><b>Schema Component Constraint: Model Group Correct</b><br/><div class="constraint"><b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 The values of the properties of a model group must be as described in
the property tableau in
<a href="#Model_Group_details">The Model Group Schema Component (§3.8.1)</a>, modulo the impact of <a href="#conformance-missing">Missing Sub-components (§5.3)</a>.</div><div class="clnumber">2 Circular groups are disallowed. That is, within the <a class="propref" href="#particles">{particles}</a> of a group there must not be at any
depth a particle whose <a class="propref" href="#term">{term}</a> is the
group itself.</div></div></div></div><div class="constraintnote"><a name="cos-all-limited" id="cos-all-limited"/><b>Schema Component Constraint: All Group Limited</b><br/><div class="constraint">When a model group has <a class="propref" href="#compositor">{compositor}</a> <i>all</i>, then
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 It appears only as the value of one or both of the following properties:<div class="constraintlist"><div class="clnumber">1.1 the <a class="propref" href="#model_group">{model group}</a> property of a model group definition.</div><div class="clnumber">1.2 the
<a class="propref" href="#term">{term}</a> property of a particle with <a class="propref" href="#p-max_occurs">{max occurs}</a><code>=1</code>which is part of a pair which constitutes the <a class="propref" href="#content_type">{content type}</a> of a
complex type definition.</div></div></div><div class="clnumber">2 The <a class="propref" href="#p-max_occurs">{max occurs}</a> of all the particles in the
<a class="propref" href="#particles">{particles}</a> of the group must be <code>0</code> or <code>1</code>.</div></div>
</div></div><div class="constraintnote"><a name="cos-element-consistent" id="cos-element-consistent"/><b>Schema Component Constraint: Element Declarations Consistent</b><br/><div class="constraint">If the <a class="propref" href="#particles">{particles}</a> contains, either directly, indirectly
(that is, within the <a class="propref" href="#particles">{particles}</a> of a contained model group,
recursively) or <a class="termref" href="#key-impl-cont"><span class="arrow">·</span>implicitly<span class="arrow">·</span></a> two or more
element declaration particles with the same <a class="propref" href="#e-name">{name}</a> and
<a class="propref" href="#e-target_namespace">{target namespace}</a>, then all their type definitions must be
the same top-level definition, that is,
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 all their
<a class="propref" href="#type_definition">{type definition}</a>s must have a non-<a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> <a class="propref" href="#ct-name">{name}</a>.</div><div class="clnumber">2 all their
<a class="propref" href="#type_definition">{type definition}</a>s must have the same <a class="propref" href="#ct-name">{name}</a>.</div><div class="clnumber">3 all their
<a class="propref" href="#type_definition">{type definition}</a>s must have the same <a class="propref" href="#ct-target_namespace">{target namespace}</a>.</div></div>
<p/><span class="termdef"><a id="key-impl-cont" name="key-impl-cont">[Definition:]  </a>A list
of particles <b>implicitly contains</b> an element declaration if a
member of the list contains that
element declaration in its <a class="termref" href="#key-eq"><span class="arrow">·</span>substitution group<span class="arrow">·</span></a></span>.</div></div><div class="constraintnote"><a name="cos-nonambig" id="cos-nonambig"/><b>Schema Component Constraint: Unique Particle Attribution</b><br/><div class="constraint">A content model must be formed such that
during <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> of an element information
item sequence, the particle component
contained directly, indirectly or <a class="termref" href="#key-impl-cont"><span class="arrow">·</span>implicitly<span class="arrow">·</span></a> therein with which to attempt to <a class="termref" href="#key-vn"><span class="arrow">·</span>validate<span class="arrow">·</span></a> each item in the sequence in turn can be uniquely determined without examining the content or attributes of that item, and without any information about the items in the remainder of the sequence.<div class="note"><b>Note: </b>This constraint reconstructs for XML Schema the equivalent constraints of
<a href="#ref-xml">[XML 1.0 (Second Edition)]</a> and SGML. Given the presence of element substitution groups and wildcards, the concise expression of this constraint is difficult,
see <a href="#non-ambig">Analysis of the Unique Particle Attribution Constraint (non-normative) (§H)</a> for further discussion.<p/>Since this constraint is expressed at the component level, it
applies to content models whose origins (e.g. via type derivation and
references to named model groups) are no longer evident. So particles at
different points in the content model are always distinct from one another,
even if they originated from the same named model group.</div></div></div><div class="note"><b>Note: </b>Because locally-scoped element declarations may or may not have a
<a class="propref" href="#e-target_namespace">{target namespace}</a>, the scope of declarations is
<em>not</em> relevant to enforcing either of the two preceding constraints.</div><p>The following constraints define relations appealed to elsewhere in this specification.</p><div class="constraintnote"><a name="cos-seq-range" id="cos-seq-range"/><b>Schema Component Constraint: Effective Total Range (all and sequence)</b><br/><div class="constraint">The effective total range of a particle whose <a class="propref" href="#term">{term}</a> is a group whose <a class="propref" href="#compositor">{compositor}</a> is
<i>all</i> or <i>sequence</i> is a pair of minimum and maximum, as follows: <dl><dt class="label">minimum</dt><dd>The product of the particle's <a class="propref" href="#p-min_occurs">{min occurs}</a> and the
sum of the <a class="propref" href="#p-min_occurs">{min occurs}</a> of every wildcard or element
declaration particle in the group's <a class="propref" href="#particles">{particles}</a> and the minimum
part of the effective total range of each of the group particles in the group's <a class="propref" href="#particles">{particles}</a> (or <code>0</code> if there are no <a class="propref" href="#particles">{particles}</a>).</dd><dt class="label">maximum</dt><dd><i>unbounded</i> if the <a class="propref" href="#p-max_occurs">{max occurs}</a> of any wildcard or element
declaration particle in the group's <a class="propref" href="#particles">{particles}</a> or the maximum
part of the effective total range of any of the group particles in the group's
<a class="propref" href="#particles">{particles}</a> is <i>unbounded</i>, or if any of those is non-zero
and the <a class="propref" href="#p-max_occurs">{max occurs}</a> of the particle itself is <i>unbounded</i>,
otherwise the product of the particle's <a class="propref" href="#p-max_occurs">{max occurs}</a> and the
sum of the <a class="propref" href="#p-max_occurs">{max occurs}</a> of every wildcard or element
declaration particle in the group's <a class="propref" href="#particles">{particles}</a> and the maximum
part of the effective total range of each of the group particles in the group's <a class="propref" href="#particles">{particles}</a> (or <code>0</code> if there are no <a class="propref" href="#particles">{particles}</a>).</dd></dl></div></div><div class="constraintnote"><a name="cos-choice-range" id="cos-choice-range"/><b>Schema Component Constraint: Effective Total Range (choice)</b><br/><div class="constraint">The effective total range of a particle whose <a class="propref" href="#term">{term}</a> is a group whose <a class="propref" href="#compositor">{compositor}</a> is
<i>choice</i> is a pair of minimum and maximum, as follows:<dl><dt class="label">minimum</dt><dd>The product of the particle's <a class="propref" href="#p-min_occurs">{min occurs}</a> and the
minimum of the <a class="propref" href="#p-min_occurs">{min occurs}</a> of every wildcard or element
declaration particle in the group's <a class="propref" href="#particles">{particles}</a> and the minimum
part of the effective total range of each of the group particles in the group's <a class="propref" href="#particles">{particles}</a> (or <code>0</code> if there are no <a class="propref" href="#particles">{particles}</a>).</dd><dt class="label">maximum</dt><dd><i>unbounded</i> if the <a class="propref" href="#p-max_occurs">{max occurs}</a> of any wildcard or element
declaration particle in the group's <a class="propref" href="#particles">{particles}</a> or the maximum
part of the effective total range of any of the group particles in the group's
<a class="propref" href="#particles">{particles}</a> is <i>unbounded</i>, or if any of those is non-zero
and the <a class="propref" href="#p-max_occurs">{max occurs}</a> of the particle itself is <i>unbounded</i>,
otherwise the product of the particle's <a class="propref" href="#p-max_occurs">{max occurs}</a> and the
maximum of the <a class="propref" href="#p-max_occurs">{max occurs}</a> of every wildcard or element
declaration particle in the group's <a class="propref" href="#particles">{particles}</a> and the maximum
part of the effective total range of each of the group particles in the group's <a class="propref" href="#particles">{particles}</a> (or <code>0</code> if there are no <a class="propref" href="#particles">{particles}</a>).</dd></dl></div></div></div></div><div class="div2">
<h3 class="withToc"><span class="nav"><a class="nav" href="#Model_Groups"><img src="previous.jpg" alt="previous sub-section"/></a> <a class="nav" href="#Wildcards"><img src="next.jpg" alt="next sub-section"/></a></span><a id="cParticles" name="cParticles"/>3.9 Particles</h3><div class="localToc">        3.9.1 <a href="#Particle_details">The Particle Schema Component</a><br/>
        3.9.2 <a href="#d0e11005">XML Representation of Particle Components</a><br/>
        3.9.3 <a href="#d0e11037">Constraints on XML Representations of Particles</a><br/>
        3.9.4 <a href="#d0e11042">Particle Validation Rules</a><br/>
        3.9.5 <a href="#d0e11288">Particle Information Set Contributions</a><br/>
        3.9.6 <a href="#coss-particle">Constraints on Particle Schema Components</a><br/>
</div><p>As described in <a href="#Model_Groups">Model Groups (§3.8)</a>, particles contribute to the definition
of content models.</p><div class="exampleOuter"><div class="exampleHeader">Example</div><div class="exampleInner"><pre><xs:element ref="egg" minOccurs="12" maxOccurs="12"/>
<xs:group ref="omelette" minOccurs="0"/>
<xs:any maxOccurs="unbounded"/>
</pre></div><div class="exampleWrapper">XML representations which all involve particles, illustrating some of
the possibilities for controlling occurrence.</div></div><div class="div3">
<h4><a id="Particle_details" name="Particle_details"/>3.9.1 The Particle Schema Component</h4><p>The particle schema component has the following properties:</p><div class="schemaComp"><div class="compHeader"><span class="schemaComp">Schema Component</span>: <a href="#Particle">Particle</a></div><div class="compBody">
<dl class="props">
<dt><a name="p-min_occurs" id="p-min_occurs"><span class="propdef">{min occurs}</span></a></dt><dd>A non-negative
integer.</dd>
<dt><a name="p-max_occurs" id="p-max_occurs"><span class="propdef">{max occurs}</span></a></dt><dd>Either a non-negative integer
or <i>unbounded</i>.</dd>
<dt><a name="term" id="term"><span class="propdef">{term}</span></a></dt><dd>One of a model group, a wildcard, or an element declaration.</dd>
</dl>
</div></div><p>In general, multiple element
information item <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, possibly with intervening character <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> if the content type
is <i>mixed</i>, can be <a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a> with
respect to a single particle. When the <a class="propref" href="#term">{term}</a> is an element
declaration or wildcard, <a class="propref" href="#p-min_occurs">{min occurs}</a> determines the minimum number of such element <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> that can occur. The number of such children must be greater than or equal to <a class="propref" href="#p-min_occurs">{min occurs}</a>. If <a class="propref" href="#p-min_occurs">{min occurs}</a> is <i>0</i>, then occurrence of such children is optional.</p><p>Again, when the <a class="propref" href="#term">{term}</a> is an element
declaration or wildcard, the number of such element <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> must be less than or equal to any numeric specification of
<a class="propref" href="#p-max_occurs">{max occurs}</a>; if <a class="propref" href="#p-max_occurs">{max occurs}</a> is <i>unbounded</i>, then there is no
upper bound on the number of such children.</p><p>When the <a class="propref" href="#term">{term}</a> is a model group, the permitted
occurrence range is determined by a combination of <a class="propref" href="#p-min_occurs">{min occurs}</a> and <a class="propref" href="#p-max_occurs">{max occurs}</a> and the occurrence ranges of the <a class="propref" href="#term">{term}</a>'s <a class="propref" href="#particles">{particles}</a>.</p></div><div class="div3">
<h4><a id="d0e11005" name="d0e11005"/>3.9.2 XML Representation of Particle Components</h4><p>Particles correspond to all three elements (<a class="eltref" href="#element-element"><element></a> not immediately within <a class="eltref" href="#element-schema"><schema></a>, <a class="eltref" href="#element-group"><group></a> not immediately within <a class="eltref" href="#element-schema"><schema></a> and <a class="eltref" href="#element-any"><any></a>) which allow <code>minOccurs</code> and <code>maxOccurs</code> attributes. These in turn correspond to
<em>two</em> components in each case, a particle and its <a class="propref" href="#term">{term}</a>. The appropriate mapping is described in <a href="#declare-element">XML Representation of Element Declaration Schema Components (§3.3.2)</a>, <a href="#declare-contentModel">XML Representation of Model Group Schema Components (§3.8.2)</a> and <a href="#declare-openness">XML Representation of Wildcard Schema Components (§3.10.2)</a> respectively.</p></div><div class="div3">
<h4><a id="d0e11037" name="d0e11037"/>3.9.3 Constraints on XML Representations of Particles</h4><p>None as such.</p></div><div class="div3">
<h4><a id="d0e11042" name="d0e11042"/>3.9.4 Particle Validation Rules</h4><div class="constraintnote"><a name="cvc-particle" id="cvc-particle"/><b>Validation Rule: Element Sequence Locally Valid (Particle)</b><br/><div class="constraint">For a sequence (possibly empty) of element information items to be
locally <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a>
with respect to a particle
the appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">1<a name="c-pw" id="c-pw"> </a><b>If </b>the <a class="propref" href="#term">{term}</a> is a wildcard, <b>then </b>
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1.1 The length of the sequence must be greater than or equal to the <a class="propref" href="#p-min_occurs">{min occurs}</a>.</div><div class="clnumber">1.2 If <a class="propref" href="#p-max_occurs">{max occurs}</a> is a number, the length of the sequence must be less than or equal to the <a class="propref" href="#p-max_occurs">{max occurs}</a>.</div><div class="clnumber">1.3 Each element
information item in the sequence must be <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to the wildcard as defined by <a href="#cvc-wildcard">Item Valid (Wildcard) (§3.10.4)</a>.</div></div>
</div><div class="clnumber">2<a name="c-cdde" id="c-cdde"> </a><b>If </b>the <a class="propref" href="#term">{term}</a> is an element declaration, <b>then </b>
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.1 The length of the sequence must be greater than or equal to the <a class="propref" href="#p-min_occurs">{min occurs}</a>.</div><div class="clnumber">2.2 If <a class="propref" href="#p-max_occurs">{max occurs}</a> is a number, the length of the sequence must be less than or equal to the <a class="propref" href="#p-max_occurs">{max occurs}</a>.</div><div class="clnumber">2.3 For each element
information item in the sequence
<b>one</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.3.1 The element declaration is local (i.e. its
<a class="propref" href="#e-scope">{scope}</a> must not be <i>global</i>), its <a class="propref" href="#e-abstract">{abstract}</a> is <i>false</i>, the element information
item's <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[namespace name]</a> is identical to the element declaration's <a class="propref" href="#e-target_namespace">{target namespace}</a> (where an <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> <a class="propref" href="#e-target_namespace">{target namespace}</a> is taken to be identical to a <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[namespace name]</a> with no value) and the element information
item's <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[local
name]</a> matches the element declaration's <a class="propref" href="#e-name">{name}</a>.<p/>In this case the element declaration is the <a class="termref" href="#key-dd"><span class="arrow">·</span>context-determined declaration<span class="arrow">·</span></a> for the element information item with respect to <a href="#cvc-assess-elt">Schema-Validity Assessment (Element) (§3.3.4)</a> and <a href="#sic-e-outcome">Assessment Outcome (Element) (§3.3.5)</a>.</div><div class="clnumber">2.3.2 The element declaration is top-level (i.e. its
<a class="propref" href="#e-scope">{scope}</a> is <i>global</i>), <a class="propref" href="#e-abstract">{abstract}</a> is <i>false</i>, the element information
item's <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[namespace name]</a> is identical to the element declaration's <a class="propref" href="#e-target_namespace">{target namespace}</a> (where an <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> <a class="propref" href="#e-target_namespace">{target namespace}</a> is taken to be identical to a <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[namespace name]</a> with no value) and the element information
item's <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[local
name]</a> matches the element declaration's <a class="propref" href="#e-name">{name}</a>.<p/>In this case the element declaration is the <a class="termref" href="#key-dd"><span class="arrow">·</span>context-determined declaration<span class="arrow">·</span></a> for the element information item with respect to <a href="#cvc-assess-elt">Schema-Validity Assessment (Element) (§3.3.4)</a> and <a href="#sic-e-outcome">Assessment Outcome (Element) (§3.3.5)</a>.</div><div class="clnumber">2.3.3<a name="c-psg" id="c-psg"> </a>The element declaration is top-level (i.e. its
<a class="propref" href="#e-scope">{scope}</a> is <i>global</i>), its <a class="propref" href="#e-exact">{disallowed substitutions}</a> does not contain <i>substitution</i>,
the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[local
]</a> and <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[namespace name]</a> of the element information item resolve to an element declaration, as
defined in <a href="#cvc-resolve-instance">QName resolution (Instance) (§3.15.4)</a> -- <span class="termdef"><a id="key-eqd" name="key-eqd">[Definition:]  </a>call this declaration the <b>substituting declaration</b></span> and the <a class="termref" href="#key-eqd"><span class="arrow">·</span>substituting declaration<span class="arrow">·</span></a> together with the particle's element declaration's <a class="propref" href="#e-exact">{disallowed substitutions}</a> is validly substitutable for the particle's element declaration as defined in <a href="#cos-equiv-derived-ok-rec">Substitution Group OK (Transitive) (§3.3.6)</a>.<p/>In this case the <a class="termref" href="#key-eqd"><span class="arrow">·</span>substituting declaration<span class="arrow">·</span></a> is the <a class="termref" href="#key-dd"><span class="arrow">·</span>context-determined declaration<span class="arrow">·</span></a> for the element information item with respect to <a href="#cvc-assess-elt">Schema-Validity Assessment (Element) (§3.3.4)</a> and <a href="#sic-e-outcome">Assessment Outcome (Element) (§3.3.5)</a>.</div></div></div></div>
</div><div class="clnumber">3 <b>If </b>the <a class="propref" href="#term">{term}</a> is a model group, <b>then </b>
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">3.1 There is a <a class="termref" href="#key-partition"><span class="arrow">·</span>partition<span class="arrow">·</span></a> of the sequence into <code>n</code> sub-sequences such that <code>n</code> is greater than or equal to <a class="propref" href="#p-min_occurs">{min occurs}</a>.</div><div class="clnumber">3.2 If <a class="propref" href="#p-max_occurs">{max occurs}</a> is a number, <code>n</code>
must be less than or equal to <a class="propref" href="#p-max_occurs">{max occurs}</a>.</div><div class="clnumber">3.3 Each sub-sequence in the <a class="termref" href="#key-partition"><span class="arrow">·</span>partition<span class="arrow">·</span></a> is <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to that model group as defined in <a href="#cvc-model-group">Element Sequence Valid (§3.8.4)</a>.</div></div>
</div></div>
<div class="note"><b>Note: </b>Clauses clause <a href="#c-pw">1</a> and clause <a href="#c-psg">2.3.3</a> do not
interact: an element information item validatable by a declaration with a substitution group head in a
different namespace is <em>not</em> validatable by a wildcard which accepts
the head's namespace but not its own.</div></div></div></div><div class="div3">
<h4><a id="d0e11288" name="d0e11288"/>3.9.5 Particle Information Set Contributions</h4><p>None as such.</p></div><div class="div3">
<h4><a id="coss-particle" name="coss-particle"/>3.9.6 Constraints on Particle Schema Components</h4><p>All particles (see <a href="#cParticles">Particles (§3.9)</a>) must satisfy the following constraints.</p><div class="constraintnote"><a name="p-props-correct" id="p-props-correct"/><b>Schema Component Constraint: Particle Correct</b><br/><div class="constraint"><b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 The values of the properties of a particle must be as described in
the property tableau in
<a href="#Particle_details">The Particle Schema Component (§3.9.1)</a>, modulo the impact of <a href="#conformance-missing">Missing Sub-components (§5.3)</a>.</div><div class="clnumber">2 If <a class="propref" href="#p-max_occurs">{max occurs}</a> is not <i>unbounded</i>, that is, it has a
numeric value, then
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.1 <a class="propref" href="#p-min_occurs">{min occurs}</a> must not be greater than <a class="propref" href="#p-max_occurs">{max occurs}</a>.</div><div class="clnumber">2.2 <a class="propref" href="#p-max_occurs">{max occurs}</a> must be greater than or equal to 1.</div></div>
</div></div></div></div><p>The following constraints define relations appealed to elsewhere in this specification.</p><div class="constraintnote"><a name="cos-particle-extend" id="cos-particle-extend"/><b>Schema Component Constraint: Particle Valid (Extension)</b><br/><div class="constraint"><span class="termdef"><a id="cd-model-extension" name="cd-model-extension">[Definition:]  </a>For a particle
(call it <b>E</b>, for extension) to be a <b>valid extension</b> of
another particle (call it <b>B</b>, for base)</span>
<b>one</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 They are the same particle.</div><div class="clnumber">2 <b>E</b>'s <a class="propref" href="#p-min_occurs">{min occurs}</a>=<a class="propref" href="#p-max_occurs">{max occurs}</a><code>=1</code> and its <a class="propref" href="#term">{term}</a> is a <i>sequence</i> group whose <a class="propref" href="#particles">{particles}</a>' first member is a particle all of whose properties, recursively, are identical to those of <b>B</b>, with the exception of <span class="anonRef">{annotation}</span> properties.</div></div>
</div></div><p>The approach to defining a type by restricting another type definition
set out here is designed to ensure that types defined in this way are
guaranteed to be a subset of the type they restrict. This is accomplished by
requiring a clear mapping between the components of the base type definition and the
restricting type definition. Permissible mappings are set out below via a set
of recursive definitions, bottoming out in the obvious cases, e.g. where an
(restricted) element declaration corresponds to another (base) element
declaration with the same name and type but the same or wider range of occurrence.</p><div class="note"><b>Note: </b>The structural correspondence approach to guaranteeing the subset
relation set out here is necessarily verbose, but has the advantage of being
checkable in a straightforward way. The working group solicits feedback on how
difficult this is in practice, and on whether other approaches are found to be viable.</div><div class="constraintnote"><a name="cos-particle-restrict" id="cos-particle-restrict"/><b>Schema Component Constraint: Particle Valid (Restriction)</b><br/><div class="constraint"><span class="termdef"><a id="cd-model-restriction" name="cd-model-restriction">[Definition:]  </a>For a particle (call it <b>R</b>, for restriction) to be a <b>valid restriction</b> of
another particle (call it <b>B</b>, for base)</span>
<b>one</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 They are the same particle.</div><div class="clnumber">2 depending on the kind of particle, per the table below, with the
qualifications that
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.1 Any top-level element declaration particle (in <b>R</b> or
<b>B</b>) which is the
<a class="propref" href="#class_exemplar">{substitution group affiliation}</a> of one or more other element declarations
and whose <a class="termref" href="#key-eq"><span class="arrow">·</span>substitution group<span class="arrow">·</span></a>
contains at least one element declaration other than itself is
treated as if it were a <i>choice</i> group whose <a class="propref" href="#p-min_occurs">{min occurs}</a> and <a class="propref" href="#p-max_occurs">{max occurs}</a> are those of the particle, and whose <a class="propref" href="#particles">{particles}</a> consists of
one particle with <a class="propref" href="#p-min_occurs">{min occurs}</a> and <a class="propref" href="#p-max_occurs">{max occurs}</a> of <code>1</code> for each of the declarations in its <a class="termref" href="#key-eq"><span class="arrow">·</span>substitution group<span class="arrow">·</span></a>.</div><div class="clnumber">2.2 Any pointless occurrences of <a class="eltref" href="#element-sequence"><sequence></a>, <a class="eltref" href="#element-choice"><choice></a> or <a class="eltref" href="#element-all"><all></a> are ignored, where pointlessness is understood as follows:
<dl><dt class="label"><a class="eltref" href="#element-sequence"><sequence></a></dt><dd><b>One</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.2.1 <a class="propref" href="#particles">{particles}</a> is empty.</div><div class="clnumber">2.2.2 <b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.2.2.1 The particle within which this <a class="eltref" href="#element-sequence"><sequence></a>
appears has <a class="propref" href="#p-max_occurs">{max occurs}</a> and <a class="propref" href="#p-min_occurs">{min occurs}</a> of
<code>1</code>.</div><div class="clnumber">2.2.2.2 <b>One</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.2.2.2.1 The <a class="eltref" href="#element-sequence"><sequence></a>'s <a class="propref" href="#particles">{particles}</a>
has only one member.</div><div class="clnumber">2.2.2.2.2 The particle within which this <a class="eltref" href="#element-sequence"><sequence></a>
appears is itself among the <a class="propref" href="#particles">{particles}</a> of a <a class="eltref" href="#element-sequence"><sequence></a>.</div></div></div></div></div></div></dd><dt class="label"><a class="eltref" href="#element-all"><all></a></dt><dd><b>One</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.2.1 <a class="propref" href="#particles">{particles}</a> is empty.</div><div class="clnumber">2.2.2 <a class="propref" href="#particles">{particles}</a> has only one member.</div></div></dd><dt class="label"><a class="eltref" href="#element-choice"><choice></a></dt><dd><b>One</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.2.1 <a class="propref" href="#particles">{particles}</a> is empty and the
particle within which this <a class="eltref" href="#element-choice"><choice></a> appears has <a class="propref" href="#p-min_occurs">{min occurs}</a> of <code>0</code>.</div><div class="clnumber">2.2.2 <b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.2.2.1 The particle within which this <a class="eltref" href="#element-choice"><choice></a>
appears has <a class="propref" href="#p-max_occurs">{max occurs}</a> and <a class="propref" href="#p-min_occurs">{min occurs}</a> of
<code>1</code>.</div><div class="clnumber">2.2.2.2 <b>One</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.2.2.2.1 The <a class="eltref" href="#element-choice"><choice></a>'s <a class="propref" href="#particles">{particles}</a>
has only one member.</div><div class="clnumber">2.2.2.2.2 The particle within which this <a class="eltref" href="#element-choice"><choice></a>
appears is itself among the <a class="propref" href="#particles">{particles}</a> of a <a class="eltref" href="#element-choice"><choice></a>.</div></div></div></div></div></div></dd></dl>
</div></div>
<table cellpadding="3" border="2" class="restricts"><thead><tr><th colspan="2"/><th colspan="6"><strong>Base Particle</strong></th></tr></thead><tbody><tr><th colspan="2"/><th>elt</th><th>any</th><th>all</th><th>choice</th><th>sequence</th></tr><tr><th rowspan="5">Derived Particle</th><th>elt</th><td><a href="#rcase-NameAndTypeOK">NameAnd- TypeOK</a></td><td><a href="#rcase-NSCompat">NSCompat</a></td><td><a href="#rcase-RecurseAsIfGroup">Recurse- AsIfGroup</a></td><td><a href="#rcase-RecurseAsIfGroup">Recurse- AsIfGroup</a></td><td><a href="#rcase-RecurseAsIfGroup">RecurseAs- IfGroup</a></td></tr><tr><th>any</th><td>Forbidden</td><td><a href="#rcase-NSSubset">NSSubset</a></td><td>Forbidden</td><td>Forbidden</td><td>Forbidden</td></tr><tr><th>all</th><td>Forbidden</td><td><a href="#rcase-NSRecurseCheckCardinality">NSRecurse- CheckCardinality</a></td><td><a href="#rcase-Recurse">Recurse</a></td><td>Forbidden</td><td>Forbidden</td></tr><tr><th>choice</th><td>Forbidden</td><td><a href="#rcase-NSRecurseCheckCardinality">NSRecurse- CheckCardinality</a></td><td>Forbidden</td><td><a href="#rcase-RecurseLax">RecurseLax</a></td><td>Forbidden</td></tr><tr><th>seq- uence</th><td>Forbidden</td><td><a href="#rcase-NSRecurseCheckCardinality">NSRecurse- CheckCardinality</a></td><td><a href="#rcase-RecurseUnordered">Recurse- Unordered</a></td><td><a href="#rcase-MapAndSum">MapAndSum</a></td><td><a href="#rcase-Recurse">Recurse</a></td></tr></tbody></table></div></div>
</div></div><div class="constraintnote"><a name="range-ok" id="range-ok"/><b>Schema Component Constraint: Occurrence Range OK</b><br/><div class="constraint">For a particle's occurrence range to be a valid restriction of another's
occurrence range
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 Its <a class="propref" href="#p-min_occurs">{min occurs}</a> is greater than or equal to the
other's <a class="propref" href="#p-min_occurs">{min occurs}</a>.</div><div class="clnumber">2 <b>one</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.1 The other's <a class="propref" href="#p-max_occurs">{max occurs}</a> is <i>unbounded</i>.</div><div class="clnumber">2.2 Both <a class="propref" href="#p-max_occurs">{max occurs}</a> are numbers, and the particle's is less than or equal to the
other's.</div></div></div></div>
</div></div><div class="constraintnote"><a name="rcase-NameAndTypeOK" id="rcase-NameAndTypeOK"/><b>Schema Component Constraint: Particle Restriction OK (Elt:Elt -- NameAndTypeOK)</b><br/><div class="constraint">For an element declaration particle to be a <a class="termref" href="#cd-model-restriction"><span class="arrow">·</span>valid restriction<span class="arrow">·</span></a> of another element declaration particle
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 The declarations' <a class="propref" href="#e-name">{name}</a>s and <a class="propref" href="#e-target_namespace">{target namespace}</a>s are the same.</div><div class="clnumber">2 <b>R</b>'s occurrence range is a valid
restriction of <b>B</b>'s occurrence range as defined by <a href="#range-ok">Occurrence Range OK (§3.9.6)</a>.</div><div class="clnumber">3 <b>One</b> of the following must be true:<div class="constraintlist"><div class="clnumber">3.1 Both <b>B</b>'s declaration's <a class="propref" href="#e-scope">{scope}</a> and
<b>R</b>'s declaration's <a class="propref" href="#e-scope">{scope}</a> are <i>global</i>.</div><div class="clnumber">3.2 <b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">3.2.1 Either <b>B</b>'s <a class="propref" href="#nillable">{nillable}</a> is <i>true</i> or <b>R</b>'s <a class="propref" href="#nillable">{nillable}</a> is <i>false</i>.</div><div class="clnumber">3.2.2 either <b>B</b>'s declaration's <a class="propref" href="#e-value_constraint">{value constraint}</a> is
absent, or is
not <i>fixed</i>, or <b>R</b>'s declaration's <a class="propref" href="#e-value_constraint">{value constraint}</a> is
<i>fixed</i> with the same value.</div><div class="clnumber">3.2.3 <b>R</b>'s declaration's <a class="propref" href="#identity-constraint_definitions">{identity-constraint definitions}</a> is
a subset of <b>B</b>'s declaration's <a class="propref" href="#identity-constraint_definitions">{identity-constraint definitions}</a>,
if any.</div><div class="clnumber">3.2.4 <b>R</b>'s declaration's <a class="propref" href="#e-exact">{disallowed substitutions}</a> is
a superset of <b>B</b>'s declaration's <a class="propref" href="#e-exact">{disallowed substitutions}</a>.</div><div class="clnumber">3.2.5 <b>R</b>'s <a class="propref" href="#type_definition">{type definition}</a> is validly derived given
{<i>extension</i>, <i>list</i>, <i>union</i>} from <b>B</b>'s <a class="propref" href="#type_definition">{type definition}</a> as defined by
<a href="#cos-ct-derived-ok">Type Derivation OK (Complex) (§3.4.6)</a> or <a href="#cos-st-derived-ok">Type Derivation OK (Simple) (§3.14.6)</a>, as appropriate.</div></div></div></div></div></div>
<div class="note"><b>Note: </b>The above constraint on <a class="propref" href="#type_definition">{type definition}</a> means that in
deriving a type by restriction, any contained type definitions must themselves be
explicitly derived by restriction from the corresponding type definitions in the
base definition, or be one of the member types of a
corresponding union..</div></div></div><div class="constraintnote"><a name="rcase-NSCompat" id="rcase-NSCompat"/><b>Schema Component Constraint: Particle Derivation OK (Elt:Any -- NSCompat)</b><br/><div class="constraint">For an element declaration particle to be a <a class="termref" href="#cd-model-restriction"><span class="arrow">·</span>valid restriction<span class="arrow">·</span></a> of a wildcard particle
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 The element declaration's <a class="propref" href="#e-target_namespace">{target namespace}</a> is
<a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to the wildcard's <a class="propref" href="#namespace_constraint">{namespace constraint}</a> as
defined by <a href="#cvc-wildcard-namespace">Wildcard allows Namespace Name (§3.10.4)</a>.</div><div class="clnumber">2 <b>R</b>'s occurrence range is a valid
restriction of <b>B</b>'s occurrence range as defined by <a href="#range-ok">Occurrence Range OK (§3.9.6)</a>.</div></div>
</div></div><div class="constraintnote"><a name="rcase-RecurseAsIfGroup" id="rcase-RecurseAsIfGroup"/><b>Schema Component Constraint: Particle Derivation OK (Elt:All/Choice/Sequence -- RecurseAsIfGroup)</b><br/><div class="constraint">For an element declaration particle to be a <a class="termref" href="#cd-model-restriction"><span class="arrow">·</span>valid restriction<span class="arrow">·</span></a> of a group particle (<i>all</i>, <i>choice</i> or <i>sequence</i>)
a group particle of the variety corresponding to <b>B</b>'s, with
<a class="propref" href="#p-min_occurs">{min occurs}</a> and <a class="propref" href="#p-max_occurs">{max occurs}</a> of <code>1</code> and with <a class="propref" href="#particles">{particles}</a> consisting of a single particle
the same as the element declaration must be a <a class="termref" href="#cd-model-restriction"><span class="arrow">·</span>valid restriction<span class="arrow">·</span></a> of the group as defined by <a href="#rcase-Recurse">Particle Derivation OK (All:All,Sequence:Sequence -- Recurse) (§3.9.6)</a>, <a href="#rcase-RecurseLax">Particle Derivation OK (Choice:Choice -- RecurseLax) (§3.9.6)</a> or <a href="#rcase-Recurse">Particle Derivation OK (All:All,Sequence:Sequence -- Recurse) (§3.9.6)</a>, depending on whether the group is <i>all</i>, <i>choice</i> or <i>sequence</i>.</div></div><div class="constraintnote"><a name="rcase-NSSubset" id="rcase-NSSubset"/><b>Schema Component Constraint: Particle Derivation OK (Any:Any -- NSSubset)</b><br/><div class="constraint">For a wildcard particle to be a <a class="termref" href="#cd-model-restriction"><span class="arrow">·</span>valid restriction<span class="arrow">·</span></a> of another wildcard particle
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 <b>R</b>'s occurrence range must be a valid
restriction of <b>B</b>'s occurrence range as defined by <a href="#range-ok">Occurrence Range OK (§3.9.6)</a>.</div><div class="clnumber">2 <b>R</b>'s <a class="propref" href="#namespace_constraint">{namespace constraint}</a> must be an intensional
subset of <b>B</b>'s <a class="propref" href="#namespace_constraint">{namespace constraint}</a> as defined by <a href="#cos-ns-subset">Wildcard Subset (§3.10.6)</a>.</div><div class="clnumber">3 Unless <b>B</b> is the content model wildcard of
the <a class="termref" href="#ur-type-itself"><span class="arrow">·</span>ur-type definition<span class="arrow">·</span></a>, <b>R</b>'s <a class="propref" href="#process_contents">{process contents}</a> must be identical
to or stronger than <b>B</b>'s <a class="propref" href="#process_contents">{process contents}</a>, where
<i>strict</i> is stronger than <i>lax</i> is stronger than <i>skip</i>.</div></div>
<div class="note"><a id="procContNote" name="procContNote"/><p class="prefix"><b>Note:</b></p>The exception to the third clause above for derivations from
the <a class="termref" href="#ur-type-itself"><span class="arrow">·</span>ur-type definition<span class="arrow">·</span></a> is necessary as
its wildcards have a <a class="propref" href="#process_contents">{process contents}</a> of <i>lax</i>, so
without this exception, no use of wildcards with <a class="propref" href="#process_contents">{process contents}</a> of <i>skip</i> would be possible.</div></div></div><div class="constraintnote"><a name="rcase-NSRecurseCheckCardinality" id="rcase-NSRecurseCheckCardinality"/><b>Schema Component Constraint: Particle Derivation OK (All/Choice/Sequence:Any -- NSRecurseCheckCardinality)</b><br/><div class="constraint">For a group particle to be a <a class="termref" href="#cd-model-restriction"><span class="arrow">·</span>valid restriction<span class="arrow">·</span></a> of a wildcard particle
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 Every member of the <a class="propref" href="#particles">{particles}</a> of the group is a
<a class="termref" href="#cd-model-restriction"><span class="arrow">·</span>valid restriction<span class="arrow">·</span></a> of the wildcard
as defined by <a href="#cos-particle-restrict">Particle Valid (Restriction) (§3.9.6)</a>.</div><div class="clnumber">2 The effective total range of the group, as defined by <a href="#cos-seq-range">Effective Total Range (all and sequence) (§3.8.6)</a> (if
the group is <i>all</i> or <i>sequence</i>) or
<a href="#cos-choice-range">Effective Total Range (choice) (§3.8.6)</a> (if it is <i>choice</i>) is a valid
restriction of <b>B</b>'s occurrence range as defined by <a href="#range-ok">Occurrence Range OK (§3.9.6)</a>.</div></div>
</div></div><div class="constraintnote"><a name="rcase-Recurse" id="rcase-Recurse"/><b>Schema Component Constraint: Particle Derivation OK (All:All,Sequence:Sequence -- Recurse)</b><br/><div class="constraint">For an <i>all</i> or <i>sequence</i> group particle to be a <a class="termref" href="#cd-model-restriction"><span class="arrow">·</span>valid restriction<span class="arrow">·</span></a> of another group particle with the same <a class="propref" href="#compositor">{compositor}</a>
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 <b>R</b>'s occurrence range is a valid
restriction of <b>B</b>'s occurrence range as defined by <a href="#range-ok">Occurrence Range OK (§3.9.6)</a>.</div><div class="clnumber">2 There is a complete <a class="termref" href="#key-op"><span class="arrow">·</span>order-preserving<span class="arrow">·</span></a> functional mapping from the particles in the
<a class="propref" href="#particles">{particles}</a> of <b>R</b> to the particles in the <a class="propref" href="#particles">{particles}</a> of <b>B</b> such that
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.1 Each particle in the <a class="propref" href="#particles">{particles}</a> of <b>R</b> is a
<a class="termref" href="#cd-model-restriction"><span class="arrow">·</span>valid restriction<span class="arrow">·</span></a> of the
particle in the <a class="propref" href="#particles">{particles}</a> of <b>B</b> it maps to as defined
by <a href="#cos-particle-restrict">Particle Valid (Restriction) (§3.9.6)</a>.</div><div class="clnumber">2.2 All particles in the <a class="propref" href="#particles">{particles}</a> of <b>B</b> which
are not mapped to by any particle in the <a class="propref" href="#particles">{particles}</a> of <b>R</b>
are <a class="termref" href="#cd-emptiable"><span class="arrow">·</span>emptiable<span class="arrow">·</span></a> as defined by <a href="#cos-group-emptiable">Particle Emptiable (§3.9.6)</a>.</div></div></div></div>
<div class="note"><b>Note: </b>Although the <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> semantics of an <i>all</i> group does not
depend on the order of its particles, derived <i>all</i> groups are required to
match the order of their base in order to simplify checking that the derivation is OK.</div><span class="termdef"><a id="key-op" name="key-op">[Definition:]  </a>A complete functional mapping is
<b>order-preserving</b> if each particle <b>r</b> in the domain <b>R</b> maps to a
particle <b>b</b> in the range <b>B</b> which follows (not necessarily
immediately) the particle in the range
<b>B</b> mapped to by the predecessor of <b>r</b>, if any, where
"predecessor" and "follows" are defined with respect
to the order of the lists which constitute <b>R</b> and <b>B</b></span>.</div></div><div class="constraintnote"><a name="rcase-RecurseLax" id="rcase-RecurseLax"/><b>Schema Component Constraint: Particle Derivation OK (Choice:Choice -- RecurseLax)</b><br/><div class="constraint">For a <i>choice</i> group particle to be a <a class="termref" href="#cd-model-restriction"><span class="arrow">·</span>valid restriction<span class="arrow">·</span></a> of another <i>choice</i> group particle
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 <b>R</b>'s occurrence range is a valid
restriction of <b>B</b>'s occurrence range as defined by <a href="#range-ok">Occurrence Range OK (§3.9.6)</a>;</div><div class="clnumber">2 There is a complete <a class="termref" href="#key-op"><span class="arrow">·</span>order-preserving<span class="arrow">·</span></a> functional mapping from the particles in the
<a class="propref" href="#particles">{particles}</a> of <b>R</b> to the particles in the <a class="propref" href="#particles">{particles}</a> of <b>B</b> such that each particle in the <a class="propref" href="#particles">{particles}</a> of <b>R</b> is a
<a class="termref" href="#cd-model-restriction"><span class="arrow">·</span>valid restriction<span class="arrow">·</span></a> of the
particle in the <a class="propref" href="#particles">{particles}</a> of <b>B</b> it maps to as defined
by <a href="#cos-particle-restrict">Particle Valid (Restriction) (§3.9.6)</a>.</div></div>
<div class="note"><b>Note: </b>Although the <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> semantics of a <i>choice</i> group does not
depend on the order of its particles, derived <i>choice</i> groups are
required to
match the order of their base in order to simplify checking that the derivation is OK.</div></div></div><div class="constraintnote"><a name="rcase-RecurseUnordered" id="rcase-RecurseUnordered"/><b>Schema Component Constraint: Particle Derivation OK (Sequence:All -- RecurseUnordered)</b><br/><div class="constraint">For a <i>sequence</i> group particle to be a <a class="termref" href="#cd-model-restriction"><span class="arrow">·</span>valid restriction<span class="arrow">·</span></a> of an <i>all</i> group particle
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 <b>R</b>'s occurrence range is a valid
restriction of <b>B</b>'s occurrence range as defined by <a href="#range-ok">Occurrence Range OK (§3.9.6)</a>.</div><div class="clnumber">2 There is a complete functional mapping from the particles in the
<a class="propref" href="#particles">{particles}</a> of <b>R</b> to the particles in the <a class="propref" href="#particles">{particles}</a> of <b>B</b> such that
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.1 No particle in the <a class="propref" href="#particles">{particles}</a> of <b>B</b> is mapped
to by more than one of the particles in the
<a class="propref" href="#particles">{particles}</a> of <b>R</b>;</div><div class="clnumber">2.2 Each particle in the <a class="propref" href="#particles">{particles}</a> of <b>R</b> is a
<a class="termref" href="#cd-model-restriction"><span class="arrow">·</span>valid restriction<span class="arrow">·</span></a> of the
particle in the <a class="propref" href="#particles">{particles}</a> of <b>B</b> it maps to as defined
by <a href="#cos-particle-restrict">Particle Valid (Restriction) (§3.9.6)</a>;</div><div class="clnumber">2.3 All particles in the <a class="propref" href="#particles">{particles}</a> of <b>B</b> which
are not mapped to by any particle in the <a class="propref" href="#particles">{particles}</a> of <b>R</b>
are <a class="termref" href="#cd-emptiable"><span class="arrow">·</span>emptiable<span class="arrow">·</span></a> as defined by <a href="#cos-group-emptiable">Particle Emptiable (§3.9.6)</a>.</div></div>
</div></div>
<div class="note"><b>Note: </b>Although this clause allows reordering, because of the limits on the
contents of <i>all</i> groups the checking process can still be deterministic.</div></div></div><div class="constraintnote"><a name="rcase-MapAndSum" id="rcase-MapAndSum"/><b>Schema Component Constraint: Particle Derivation OK (Sequence:Choice -- MapAndSum)</b><br/><div class="constraint">For a <i>sequence</i> group particle to be a <a class="termref" href="#cd-model-restriction"><span class="arrow">·</span>valid restriction<span class="arrow">·</span></a> of a <i>choice</i> group particle
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 There is a complete functional mapping from the particles in the
<a class="propref" href="#particles">{particles}</a> of <b>R</b> to the particles in the <a class="propref" href="#particles">{particles}</a> of <b>B</b> such that each particle in the <a class="propref" href="#particles">{particles}</a> of <b>R</b> is a
<a class="termref" href="#cd-model-restriction"><span class="arrow">·</span>valid restriction<span class="arrow">·</span></a> of the
particle in the <a class="propref" href="#particles">{particles}</a> of <b>B</b> it maps to as defined
by <a href="#cos-particle-restrict">Particle Valid (Restriction) (§3.9.6)</a>.</div><div class="clnumber">2 The pair consisting of the product of the <a class="propref" href="#p-min_occurs">{min occurs}</a> of <b>R</b> and the length of its <a class="propref" href="#particles">{particles}</a> and <i>unbounded</i> if <a class="propref" href="#p-max_occurs">{max occurs}</a> is <i>unbounded</i> otherwise the product of the <a class="propref" href="#p-max_occurs">{max occurs}</a> of <b>R</b> and the length of its <a class="propref" href="#particles">{particles}</a> is a valid
restriction of <b>B</b>'s occurrence range as defined by <a href="#range-ok">Occurrence Range OK (§3.9.6)</a>.<div class="note"><b>Note: </b>This clause is in principle more restrictive than absolutely
necessary, but in practice will cover all the likely cases, and is much easier
to specify than the fully general version.</div></div></div>
<div class="note"><b>Note: </b>This case allows the "unfolding" of iterated disjunctions
into sequences. It may be particularly useful when the disjunction is an
implicit one arising from the use of substitution groups.</div></div></div><div class="constraintnote"><a name="cos-group-emptiable" id="cos-group-emptiable"/><b>Schema Component Constraint: Particle Emptiable</b><br/><div class="constraint"><span class="termdef"><a id="cd-emptiable" name="cd-emptiable">[Definition:]  </a>For a particle to be
<b>emptiable</b></span>
<b>one</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 Its <a class="propref" href="#p-min_occurs">{min occurs}</a> is <code>0</code>.</div><div class="clnumber">2 Its <a class="propref" href="#term">{term}</a> is a group and the minimum part of the
effective total range of that group, as defined by <a href="#cos-seq-range">Effective Total Range (all and sequence) (§3.8.6)</a> (if
the group is <i>all</i> or <i>sequence</i>) or
<a href="#cos-choice-range">Effective Total Range (choice) (§3.8.6)</a> (if it is <i>choice</i>), is <code>0</code>.</div></div>
</div></div></div></div><div class="div2">
<h3 class="withToc"><span class="nav"><a class="nav" href="#cParticles"><img src="previous.jpg" alt="previous sub-section"/></a> <a class="nav" href="#cIdentity-constraint_Definitions"><img src="next.jpg" alt="next sub-section"/></a></span><a id="Wildcards" name="Wildcards"/>3.10 Wildcards</h3><div class="localToc">        3.10.1 <a href="#Wildcard_details">The Wildcard Schema Component</a><br/>
        3.10.2 <a href="#declare-openness">XML Representation of Wildcard Schema Components</a><br/>
        3.10.3 <a href="#d0e12788">Constraints on XML Representations of Wildcards</a><br/>
        3.10.4 <a href="#d0e12802">Wildcard Validation Rules</a><br/>
        3.10.5 <a href="#d0e12923">Wildcard Information Set Contributions</a><br/>
        3.10.6 <a href="#coss-wildcard">Constraints on Wildcard Schema Components</a><br/>
</div><p>In order to exploit the full potential for extensibility offered by XML
plus namespaces, more provision is needed than DTDs allow for targeted flexibility in content
models and attribute declarations. A wildcard provides for <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> of
attribute and element information items dependent on their namespace
name, but independently of their local name.</p><div class="exampleOuter"><div class="exampleHeader">Example</div><div class="exampleInner"><pre><xs:any processContents="skip"/>
<xs:any namespace="##other" processContents="lax"/>
<xs:any namespace="http://www.w3.org/1999/XSL/Transform"/>
<xs:any namespace="##targetNamespace"/>
<xs:anyAttribute namespace="http://www.w3.org/XML/1998/namespace"/></pre></div><div class="exampleWrapper">XML representations of the four basic types of wildcard, plus one attribute wildcard.</div></div><div class="div3">
<h4><a id="Wildcard_details" name="Wildcard_details"/>3.10.1 The Wildcard Schema Component</h4><p>The wildcard schema component has the following properties:</p><div class="schemaComp"><div class="compHeader"><span class="schemaComp">Schema Component</span>: <a href="#Wildcard">Wildcard</a></div><div class="compBody">
<dl class="props">
<dt><a name="namespace_constraint" id="namespace_constraint"><span class="propdef">{namespace constraint}</span></a></dt><dd>
One of <i>any</i>; a pair of <i>not</i> and a namespace name
or <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>; or a set whose
members are either namespace names or <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.
</dd>
<dt><a name="process_contents" id="process_contents"><span class="propdef">{process contents}</span></a></dt><dd>One of <i>skip</i>, <i>lax</i> or <i>strict</i>.</dd>
<dt><a name="w-annotation" id="w-annotation"><span class="propdef">{annotation}</span></a></dt><dd>Optional. An annotation.</dd>
</dl>
</div></div><p><a class="propref" href="#namespace_constraint">{namespace constraint}</a> provides for <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> of attribute and element items that:
</p><ol class="enumar"><li>(<i>any</i>) have any namespace or are not namespace-qualified;</li><li>(<i>not</i> and a namespace name) are namespace-qualified with a namespace
other than the specified namespace name;</li><li>(<i>not</i> and <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>) are namespace-qualified;</li><li>(a set whose
members are either namespace names or <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>) have any of the
specified namespaces and/or, if <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> is included in the set, are unqualified.</li></ol><p><a class="propref" href="#process_contents">{process contents}</a> controls the impact on <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a>
of the information items allowed by wildcards, as follows:
</p><dl><dt class="label">strict</dt><dd>There must be a top-level declaration for the item available, or the item
must have an <code>xsi:type</code>, and the item
must be <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> as appropriate.</dd><dt class="label">skip</dt><dd>No constraints at all: the item must simply be well-formed XML.</dd><dt class="label">lax</dt><dd>If the item has a uniquely
determined declaration available, it must be <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to
that definition, that is, <a class="termref" href="#key-vn"><span class="arrow">·</span>validate<span class="arrow">·</span></a>
if you
can, don't worry if you can't.</dd></dl><p>
</p><p>See <a href="#cAnnotations">Annotations (§3.13)</a> for information on the role of the
<a class="propref" href="#w-annotation">{annotation}</a> property.</p></div><div class="div3">
<h4><a id="declare-openness" name="declare-openness"/>3.10.2 XML Representation of Wildcard Schema Components</h4><p>The XML representation for a wildcard schema component is an
<a class="eltref" href="#element-any"><any></a> or <a class="eltref" href="#element-anyAttribute"><anyAttribute></a> element information item. The correspondences between the
properties of an <a class="eltref" href="#element-any"><any></a> information item and
properties of the components it corresponds to are as follows (see <a class="eltref" href="#element-complexType"><complexType></a> and <a class="eltref" href="#element-attributeGroup"><attributeGroup></a> for the correspondences for <a class="eltref" href="#element-anyAttribute"><anyAttribute></a>):</p><div class="reprdef"><div class="reprHeader"><span class="reprdef">XML Representation Summary</span>: <code>any</code> Element Information Item</div><div class="reprBody">
<p class="element-syntax-1"><a name="element-any" id="element-any"><any</a><br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  maxOccurs =
(<a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#nonNegativeInteger">nonNegativeInteger</a> | <var>unbounded</var>)
 : 1<br/>  minOccurs = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#nonNegativeInteger">nonNegativeInteger</a> : 1<br/>  namespace =
((<var>##any</var> | <var>##other</var>) | List of
(<a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#anyURI">anyURI</a> | (<var>##targetNamespace</var> | <var>##local</var>))
)
 : ##any<br/>  processContents = (<var>lax</var> | <var>skip</var> | <var>strict</var>) : strict<br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?)<br/></any></p>
<div class="reprdep">A particle containing a wildcard, with properties as follows (unless <code>minOccurs=maxOccurs=0</code>, in which case the item
corresponds to no component at all):</div>
<div class="reprcomp"><table class="reprcomp"><thead><tr><th><a href="#Particle_details">Particle</a><strong> Schema Component</strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Representation</th></tr></thead><tbody valign="top"><tr valign="top"><td><a class="propref" href="#p-min_occurs">{min occurs}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>minOccurs</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, if present, otherwise <code>1</code>.</td></tr><tr valign="top"><td><a class="propref" href="#p-max_occurs">{max occurs}</a></td><td><i>unbounded</i>, if the <code>maxOccurs</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> equals <i>unbounded</i>, otherwise the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>maxOccurs</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, if present, otherwise <code>1</code>.</td></tr><tr valign="top"><td><a class="propref" href="#term">{term}</a></td><td>A wildcard as given below:</td></tr></tbody></table></td></tr></tbody></table></div>
<div class="reprcomp"><table class="reprcomp"><thead><tr><th><a href="#Wildcard_details">Wildcard</a><strong> Schema Component</strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Representation</th></tr></thead><tbody valign="top"><tr valign="top"><td><a class="propref" href="#namespace_constraint">{namespace constraint}</a></td><td>Dependent on the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the
<code>namespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>: if absent, then <i>any</i>, otherwise as follows:<dl><dt class="label">##any</dt><dd><i>any</i></dd><dt class="label">##other</dt><dd>a pair of <i>not</i> and the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>targetNamespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of the <a class="eltref" href="#element-schema"><schema></a> ancestor
element information item if present, otherwise <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</dd><dt class="label"><em>otherwise</em></dt><dd>a set whose members are namespace names corresponding to the
space-delimited substrings of the string, except
<div class="constraintlist"><div class="clnumber">1 if one such
substring is <code>##targetNamespace</code>, the corresponding member is the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>targetNamespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of the <a class="eltref" href="#element-schema"><schema></a> ancestor
element information item if present, otherwise <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</div><div class="clnumber">2 if one such
substring is <code>##local</code>, the corresponding member is <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</div></div>
</dd></dl>
</td></tr><tr valign="top"><td><a class="propref" href="#process_contents">{process contents}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the
<code>processContents</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, if present, otherwise <i>strict</i>.</td></tr><tr valign="top"><td><a class="propref" href="#w-annotation">{annotation}</a></td><td>The annotation corresponding to the <a class="eltref" href="#element-annotation"><annotation></a> element information item in the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if present, otherwise <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</td></tr></tbody></table></td></tr></tbody></table></div></div></div><p>Wildcards are subject to the same ambiguity constraints
(<a href="#cos-nonambig">Unique Particle Attribution (§3.8.6)</a>) as other
content model particles: If an instance element could match either an explicit
particle and a wildcard, or one of two wildcards, within the content model of a
type, that model is in error.</p></div><div class="div3">
<h4><a id="d0e12788" name="d0e12788"/>3.10.3 Constraints on XML Representations of Wildcards</h4><div class="constraintnote"><a name="src-wildcard" id="src-wildcard"/><b>Schema Representation Constraint: Wildcard Representation OK</b><br/><div class="constraint">In addition to the conditions imposed on <a class="eltref" href="#element-any"><any></a> element
information items by the schema for schemas, the corresponding particle and model group must satisfy the conditions set
out in <a href="#coss-modelGroup">Constraints on Model Group Schema Components (§3.8.6)</a> and <a href="#coss-particle">Constraints on Particle Schema Components (§3.9.6)</a>.</div></div></div><div class="div3">
<h4><a id="d0e12802" name="d0e12802"/>3.10.4 Wildcard Validation Rules</h4><div class="constraintnote"><a name="cvc-wildcard" id="cvc-wildcard"/><b>Validation Rule: Item Valid (Wildcard)</b><br/><div class="constraint">For an element or attribute information item to be locally <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to a wildcard
constraint
its <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[namespace name]</a> must be <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to the wildcard constraint, as defined in <a href="#cvc-wildcard-namespace">Wildcard allows Namespace Name (§3.10.4)</a>.<p/>When this constraint applies
the appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">1 <b>If </b><a class="propref" href="#process_contents">{process contents}</a> is <i>lax</i>, <b>then </b>the item has no <a class="termref" href="#key-dd"><span class="arrow">·</span>context-determined declaration<span class="arrow">·</span></a> with respect to <a href="#sic-e-outcome">Assessment Outcome (Element) (§3.3.5)</a>, <a href="#cvc-assess-elt">Schema-Validity Assessment (Element) (§3.3.4)</a> and <a href="#cvc-assess-attr">Schema-Validity Assessment (Attribute) (§3.2.4)</a>.</div><div class="clnumber">2 <b>If </b><a class="propref" href="#process_contents">{process contents}</a> is <i>strict</i>, <b>then </b>the item's <a class="termref" href="#key-dd"><span class="arrow">·</span>context-determined declaration<span class="arrow">·</span></a> is <i>mustFind</i>.</div><div class="clnumber">3 <b>If </b><a class="propref" href="#process_contents">{process contents}</a> is <i>skip</i>, <b>then </b>the item's <a class="termref" href="#key-dd"><span class="arrow">·</span>context-determined declaration<span class="arrow">·</span></a> is <i>skip</i>.</div></div>
</div></div><div class="constraintnote"><a name="cvc-wildcard-namespace" id="cvc-wildcard-namespace"/><b>Validation Rule: Wildcard allows Namespace Name</b><br/><div class="constraint">For a value which is either a namespace name or <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> to be <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to a wildcard constraint (the
value of a <a class="propref" href="#namespace_constraint">{namespace constraint}</a>)
<b>one</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 The constraint must be <i>any</i>.</div><div class="clnumber">2 <b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.1 The constraint is a pair of <i>not</i> and a namespace name or
<a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> (<span class="termdef"><a id="key-nst" name="key-nst">[Definition:]  </a>call this the <b>namespace test</b>)</span>.</div><div class="clnumber">2.2 The value must not be identical to the <a class="termref" href="#key-nst"><span class="arrow">·</span>namespace test<span class="arrow">·</span></a>.</div><div class="clnumber">2.3 The value must not be <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</div></div></div><div class="clnumber">3 The constraint is a set, and the value is identical to one of the members of the set.</div></div>
</div></div></div><div class="div3">
<h4><a id="d0e12923" name="d0e12923"/>3.10.5 Wildcard Information Set Contributions</h4><p>None as such.</p></div><div class="div3">
<h4><a id="coss-wildcard" name="coss-wildcard"/>3.10.6 Constraints on Wildcard Schema Components</h4><p>All wildcards (see <a href="#Wildcards">Wildcards (§3.10)</a>) must satisfy the following constraint.</p><div class="constraintnote"><a name="w-props-correct" id="w-props-correct"/><b>Schema Component Constraint: Wildcard Properties Correct</b><br/><div class="constraint">The values of the properties of a wildcard must be as described in
the property tableau in
<a href="#Wildcard_details">The Wildcard Schema Component (§3.10.1)</a>, modulo the impact of <a href="#conformance-missing">Missing Sub-components (§5.3)</a>.</div></div><p>The following constraints define a relation appealed to elsewhere in this specification.</p><div class="constraintnote"><a name="cos-ns-subset" id="cos-ns-subset"/><b>Schema Component Constraint: Wildcard Subset</b><br/><div class="constraint">For a namespace constraint (call it <b>sub</b>) to be an intensional subset of
another namespace constraint (call it <b>super</b>)
<b>one</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 <b>super</b> must be <i>any</i>.</div><div class="clnumber">2 <b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.1 <b>sub</b> must be a pair of <i>not</i> and
a value
(a namespace name or
<a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>).</div><div class="clnumber">2.2 <b>super</b> must be a pair of <i>not</i> and the same value.</div></div></div><div class="clnumber">3 <b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">3.1 <b>sub</b> must be a set whose members are either namespace names or
<a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</div><div class="clnumber">3.2 <b>One</b> of the following must be true:<div class="constraintlist"><div class="clnumber">3.2.1 <b>super</b> must be the same set or a superset thereof.</div><div class="clnumber">3.2.2 <b>super</b> must be a pair of <i>not</i> and a value (a namespace name or
<a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>)
and neither that value nor <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> must be in <b>sub</b>'s set.</div></div></div></div></div></div>
</div></div><div class="constraintnote"><a name="cos-aw-union" id="cos-aw-union"/><b>Schema Component Constraint: Attribute Wildcard Union</b><br/><div class="constraint">For a wildcard's <a class="propref" href="#namespace_constraint">{namespace constraint}</a> value to be the intensional
union of two other such values (call them <b>O1</b> and <b>O2</b>):
the appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">1 <b>If </b><b>O1</b> and <b>O2</b> are the same value, <b>then </b>that value must be the value.</div><div class="clnumber">2 <b>If </b>either <b>O1</b> or <b>O2</b> is <i>any</i>, <b>then </b><i>any</i> must be the value.</div><div class="clnumber">3 <b>If </b>both <b>O1</b> and <b>O2</b> are sets of (namespace names
or <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>), <b>then </b>the union of those sets must be the value.</div><div class="clnumber">4 <b>If </b>the two are negations of different values (namespace names or <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>), <b>then </b>a pair of <i>not</i> and <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> must be the value.</div><div class="clnumber">5 <b>If </b>either <b>O1</b> or <b>O2</b> is a pair of <i>not</i>
and a namespace name and the other is a set of (namespace names or <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>) (call this set <b>S</b>), <b>then </b>
The appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">5.1 <b>If </b>the set <b>S</b> includes both the negated namespace name and <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>, <b>then </b><i>any</i> must be the value.</div><div class="clnumber">5.2 <b>If </b>the set <b>S</b> includes the negated namespace name but not <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>, <b>then </b>a pair of <i>not</i> and <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> must be the value.</div><div class="clnumber">5.3 <b>If </b>the set <b>S</b> includes <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>
but not the negated namespace name, <b>then </b>the union is not expressible.</div><div class="clnumber">5.4 <b>If </b>the set <b>S</b> does not include either the negated namespace
name or <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>, <b>then </b>whichever of <b>O1</b> or <b>O2</b> is a pair of <i>not</i>
and a namespace name must be the value.</div></div>
</div><div class="clnumber">6 <b>If </b>either <b>O1</b> or <b>O2</b> is a pair of <i>not</i>
and <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> and the other is a set of
(namespace names or <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>) (again, call this
set <b>S</b>), <b>then </b>
The appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">6.1 <b>If </b>the set <b>S</b> includes <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>, <b>then </b><i>any</i> must be the value.</div><div class="clnumber">6.2 <b>If </b>the set <b>S</b> does not include <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>, <b>then </b>a pair of <i>not</i> and <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> must be the value.</div></div>
</div></div>
In the case where there are more than two values, the intensional
union is determined by identifying the intensional union of two
of the values as above, then the intensional union of that value with
the third (providing the first union was expressible), and so on as required.
</div></div><div class="constraintnote"><a name="cos-aw-intersect" id="cos-aw-intersect"/><b>Schema Component Constraint: Attribute Wildcard Intersection</b><br/><div class="constraint">For a wildcard's <a class="propref" href="#namespace_constraint">{namespace constraint}</a> value to be the intensional
intersection of two other such values (call them <b>O1</b> and <b>O2</b>):
the appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">1 <b>If </b><b>O1</b> and <b>O2</b> are the same value, <b>then </b>that value must be the value.</div><div class="clnumber">2 <b>If </b>either <b>O1</b> or <b>O2</b> is <i>any</i>, <b>then </b>the
other must be the value.</div><div class="clnumber">3 <b>If </b>either <b>O1</b> or <b>O2</b> is a pair of <i>not</i>
and a value (a namespace name or <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>) and the other is a set of (namespace names or <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>), <b>then </b>that set,
minus the negated value if it was in the set, minus <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> if it was in the set, must be the value.</div><div class="clnumber">4 <b>If </b>both <b>O1</b> and <b>O2</b> are sets of (namespace names
or <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>), <b>then </b>the intersection of those sets must be the value.</div><div class="clnumber">5 <b>If </b>the two are negations of different namespace names, <b>then </b>the intersection is not expressible.</div><div class="clnumber">6 <b>If </b>the one is a negation of a namespace name and the other is a
negation of <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>, <b>then </b>the one which is the negation of a namespace name must be the value.</div></div>
In the case where there are more than two values, the intensional
intersection is determined by identifying the intensional intersection of two
of the values as above, then the intensional intersection of that value with
the third (providing the first intersection was expressible), and so on as required.
</div></div></div></div><div class="div2">
<h3 class="withToc"><span class="nav"><a class="nav" href="#Wildcards"><img src="previous.jpg" alt="previous sub-section"/></a> <a class="nav" href="#cNotation_Declarations"><img src="next.jpg" alt="next sub-section"/></a></span><a id="cIdentity-constraint_Definitions" name="cIdentity-constraint_Definitions"/>3.11 Identity-constraint Definitions</h3><div class="localToc">        3.11.1 <a href="#Identity-constraint_Definition_details">The Identity-constraint Definition Schema Component</a><br/>
        3.11.2 <a href="#declare-key">XML Representation of Identity-constraint Definition Schema Components</a><br/>
        3.11.3 <a href="#d0e13803">Constraints on XML Representations of Identity-constraint Definitions</a><br/>
        3.11.4 <a href="#d0e13819">Identity-constraint Definition Validation Rules</a><br/>
        3.11.5 <a href="#d0e14060">Identity-constraint Definition Information Set Contributions</a><br/>
        3.11.6 <a href="#coss-identity-constraint">Constraints on Identity-constraint Definition Schema Components</a><br/>
</div><p>Identity-constraint definition components provide for uniqueness and
reference constraints with respect to the contents of multiple elements and attributes.</p><div class="exampleOuter"><div class="exampleHeader">Example</div><div class="exampleInner"><pre><xs:key name="fullName">
<xs:selector xpath=".//person"/>
<xs:field xpath="forename"/>
<xs:field xpath="surname"/>
</xs:key>
<xs:keyref name="personRef" refer="fullName">
<xs:selector xpath=".//personPointer"/>
<xs:field xpath="@first"/>
<xs:field xpath="@last"/>
</xs:keyref>
<xs:unique name="nearlyID">
<xs:selector xpath=".//*"/>
<xs:field xpath="@id"/>
</xs:unique></pre></div><div class="exampleWrapper">XML representations for the three kinds of identity-constraint definitions.</div></div><div class="div3">
<h4><a id="Identity-constraint_Definition_details" name="Identity-constraint_Definition_details"/>3.11.1 The Identity-constraint Definition Schema Component</h4><p>The identity-constraint definition schema component has the following
properties:
</p><div class="schemaComp"><div class="compHeader"><span class="schemaComp">Schema Component</span>: <a href="#Identity-constraint_Definition">Identity-constraint Definition</a></div><div class="compBody">
<dl class="props">
<dt><a name="c-name" id="c-name"><span class="propdef">{name}</span></a></dt><dd>
An NCName as defined by <a href="#ref-xml-namespaces">[XML-Namespaces]</a>.
</dd>
<dt><a name="c-target_namespace" id="c-target_namespace"><span class="propdef">{target namespace}</span></a></dt><dd>
Either <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> or a namespace name, as defined in <a href="#ref-xml-namespaces">[XML-Namespaces]</a>.
</dd>
<dt><a name="identity-constraint_name" id="identity-constraint_name"><span class="propdef">{identity-constraint category}</span></a></dt><dd>
One of <i>key</i>, <i>keyref</i> or <i>unique</i>.
</dd>
<dt><a name="selector" id="selector"><span class="propdef">{selector}</span></a></dt><dd>
A restricted XPath (<a href="#bib-xpath">[XPath]</a>) expression.</dd>
<dt><a name="fields" id="fields"><span class="propdef">{fields}</span></a></dt><dd>
A non-empty list of restricted XPath (<a href="#bib-xpath">[XPath]</a>) expressions.</dd>
<dt><a name="referenced_key" id="referenced_key"><span class="propdef">{referenced key}</span></a></dt><dd>
Required if <a class="propref" href="#identity-constraint_name">{identity-constraint category}</a> is <i>keyref</i>, forbidden
otherwise. An identity-constraint definition with <a class="propref" href="#identity-constraint_name">{identity-constraint category}</a>
equal to <i>key</i> or <i>unique</i>.
</dd>
<dt><a name="rc-annotation" id="rc-annotation"><span class="propdef">{annotation}</span></a></dt><dd>Optional. A set of annotations.</dd>
</dl>
</div></div><p>Identity-constraint definitions are identified by their <a class="propref" href="#c-name">{name}</a> and <a class="propref" href="#c-target_namespace">{target namespace}</a>; Identity-constraint definition identities must be unique within an <a class="termref" href="#key-schema"><span class="arrow">·</span>XML Schema<span class="arrow">·</span></a>. See <a href="#composition-schemaImport">References to schema components across namespaces (§4.2.3)</a> for the use of component
identifiers when importing one schema into another.</p><p>Informally, <a class="propref" href="#identity-constraint_name">{identity-constraint category}</a> identifies the Identity-constraint definition as playing one of
three roles:
</p><ul><li>(<i>unique</i>) the Identity-constraint definition asserts uniqueness, with respect to the content
identified by <a class="propref" href="#selector">{selector}</a>, of the tuples resulting from
evaluation of the <a class="propref" href="#fields">{fields}</a> XPath expression(s). </li><li>(<i>key</i>) the Identity-constraint definition asserts uniqueness as for
<i>unique</i>. <i>key</i> further asserts that all selected content
actually has such tuples.</li><li>(<i>keyref</i>) the Identity-constraint definition asserts a correspondence, with respect to the content
identified by <a class="propref" href="#selector">{selector}</a>, of the tuples resulting from
evaluation of the <a class="propref" href="#fields">{fields}</a> XPath expression(s), with those of the <a class="propref" href="#referenced_key">{referenced key}</a>. </li></ul><p> </p><p>These constraints are specified along side the specification of types for the
attributes and elements involved, i.e. something declared as of type integer
may also serve as a key. Each constraint declaration has a name, which exists in a
single symbol space for constraints. The equality and inequality conditions
appealed to in checking these constraints apply to the <em>value</em> of
the fields selected, so that for example <code>3.0</code> and <code>3</code>
would be conflicting keys if they were both number, but non-conflicting if
they were both strings, or one was a string and one a number. Values of
differing type can only be equal if one type is derived from the other, and the
value is in the value space of both.</p><p>Overall the augmentations to XML's <code>ID/IDREF</code> mechanism are:</p><ul><li>Functioning as a part of an identity-constraint is in addition to, not instead of,
having a type;</li><li>Not just attribute values, but also element content and combinations
of values and content can be declared to be unique;</li><li>Identity-constraints are specified to hold within the scope of particular elements;</li><li>(Combinations of) attribute values and/or element content can be
declared to be keys, that is, not only unique, but always present and non-nillable;</li><li>The comparison between <i>keyref</i> <a class="propref" href="#fields">{fields}</a> and
<i>key</i> or <i>unique</i> <a class="propref" href="#fields">{fields}</a> is by value equality,
not by string equality.</li></ul><p><a class="propref" href="#selector">{selector}</a> specifies a restricted XPath (<a href="#bib-xpath">[XPath]</a>) expression relative to
instances of the element being declared. This must identify a node set of
subordinate elements (i.e. contained within the declared element) to which the constraint applies.</p><p><a class="propref" href="#fields">{fields}</a> specifies XPath expressions relative to each
element selected by a <a class="propref" href="#selector">{selector}</a>. This must identify
a single node (element or attribute) whose content or value, which must be
of a simple type, is used in the constraint. It is possible to specify an
ordered list of <a class="propref" href="#fields">{fields}</a>s, to cater to multi-field keys,
keyrefs, and uniqueness constraints.
</p><p>In order to reduce the burden on implementers, in particular
implementers of streaming processors, only restricted subsets of XPath
expressions are allowed in <a class="propref" href="#selector">{selector}</a> and <a class="propref" href="#fields">{fields}</a>. The details are given in <a href="#coss-identity-constraint">Constraints on Identity-constraint Definition Schema Components (§3.11.6)</a>.</p><div class="note"><b>Note: </b>Provision for multi-field keys etc. goes beyond what is supported by <code>xsl:key</code>.</div><p>See <a href="#cAnnotations">Annotations (§3.13)</a> for information on the role of the
<a class="propref" href="#rc-annotation">{annotation}</a> property.</p></div><div class="div3">
<h4><a id="declare-key" name="declare-key"/>3.11.2 XML Representation of Identity-constraint Definition Schema Components</h4><p>The XML representation for an identity-constraint definition schema component is
either a
<a class="eltref" href="#element-key"><key></a>, a <a class="eltref" href="#element-keyref"><keyref></a> or a <a class="eltref" href="#element-unique"><unique></a>
element information item. The correspondences between the
properties of those information items and
properties of the component they correspond to are as follows:</p><div class="reprdef"><div class="reprHeader"><span class="reprdef">XML Representation Summary</span>: <code>unique</code> Element Information Item</div><div class="reprBody">
<p class="element-syntax-1"><a name="element-unique" id="element-unique"><unique</a><br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  <b>name</b> = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#NCName">NCName</a><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?, (<a class="eltref" href="#element-selector">selector</a>, <a class="eltref" href="#element-field">field</a>+))<br/></unique></p>
<p class="element-syntax"><a name="element-key" id="element-key"><key</a><br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  <b>name</b> = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#NCName">NCName</a><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?, (<a class="eltref" href="#element-selector">selector</a>, <a class="eltref" href="#element-field">field</a>+))<br/></key></p>
<p class="element-syntax"><a name="element-keyref" id="element-keyref"><keyref</a><br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  <b>name</b> = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#NCName">NCName</a><br/>  <b>refer</b> = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#QName">QName</a><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?, (<a class="eltref" href="#element-selector">selector</a>, <a class="eltref" href="#element-field">field</a>+))<br/></keyref></p>
<p class="element-syntax"><a name="element-selector" id="element-selector"><selector</a><br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  <b>xpath</b> = <em>a subset of XPath expression, see below</em><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?)<br/></selector></p>
<p class="element-syntax"><a name="element-field" id="element-field"><field</a><br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  <b>xpath</b> = <em>a subset of XPath expression, see below</em><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?)<br/></field></p>
<div class="reprcomp"><table class="reprcomp"><thead><tr><th><a href="#Identity-constraint_Definition_details">Identity-constraint Definition</a><strong> Schema Component</strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Representation</th></tr></thead><tbody valign="top"><tr valign="top"><td><a class="propref" href="#c-name">{name}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>name</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a></td></tr><tr valign="top"><td><a class="propref" href="#c-target_namespace">{target namespace}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the
<code>targetNamespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of the parent <code>schema</code>
element information item.</td></tr><tr valign="top"><td><a class="propref" href="#identity-constraint_name">{identity-constraint category}</a></td><td>One of <i>key</i>, <i>keyref</i> or
<i>unique</i>, depending on the item.</td></tr><tr valign="top"><td><a class="propref" href="#selector">{selector}</a></td><td>A restricted XPath expression corresponding to the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of
the <code>xpath</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of the <a class="eltref" href="#element-selector"><selector></a> element information item among the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a></td></tr><tr valign="top"><td><a class="propref" href="#fields">{fields}</a></td><td>A sequence of XPath expressions, corresponding to the
<a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a>s of the <code>xpath</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>s of the <a class="eltref" href="#element-field"><field></a> element information item <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, in order.</td></tr><tr valign="top"><td><a class="propref" href="#referenced_key">{referenced key}</a></td><td>If the item is a <a class="eltref" href="#element-keyref"><keyref></a>, the
identity-constraint definition <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to by the
<a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>refer</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, otherwise <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</td></tr><tr valign="top"><td><a class="propref" href="#rc-annotation">{annotation}</a></td><td>The annotations corresponding to the <a class="eltref" href="#element-annotation"><annotation></a> element information item in the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if present, and in the <a class="eltref" href="#element-selector"><selector></a> and <a class="eltref" href="#element-field"><field></a> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if present, otherwise <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</td></tr></tbody></table></td></tr></tbody></table></div></div></div><div class="exampleOuter"><div class="exampleHeader">Example</div><div class="exampleInner"><pre><xs:element name="vehicle">
<xs:complexType>
. . .
<xs:attribute name="plateNumber" type="xs:integer"/>
<xs:attribute name="state" type="twoLetterCode"/>
</xs:complexType>
</xs:element>
<xs:element name="state">
<xs:complexType>
<xs:sequence>
<xs:element name="code" type="twoLetterCode"/>
<xs:element ref="vehicle" maxOccurs="unbounded"/>
<xs:element ref="person" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:key name="reg"> <!-- vehicles are keyed by their plate within states -->
<xs:selector xpath=".//vehicle"/>
<xs:field xpath="@plateNumber"/>
</xs:key>
</xs:element>
<xs:element name="root">
<xs:complexType>
<xs:sequence>
. . .
<xs:element ref="state" maxOccurs="unbounded"/>
. . .
</xs:sequence>
</xs:complexType>
<xs:key name="state"> <!-- states are keyed by their code -->
<xs:selector xpath=".//state"/>
<xs:field xpath="code"/>
</xs:key>
<xs:keyref name="vehicleState" refer="state">
<!-- every vehicle refers to its state -->
<xs:selector xpath=".//vehicle"/>
<xs:field xpath="@state"/>
</xs:keyref>
<xs:key name="regKey"> <!-- vehicles are keyed by a pair of state and plate -->
<xs:selector xpath=".//vehicle"/>
<xs:field xpath="@state"/>
<xs:field xpath="@plateNumber"/>
</xs:key>
<xs:keyref name="carRef" refer="regKey"> <!-- people's cars are a reference -->
<xs:selector xpath=".//car"/>
<xs:field xpath="@regState"/>
<xs:field xpath="@regPlate"/>
</xs:keyref>
</xs:element>
<xs:element name="person">
<xs:complexType>
<xs:sequence>
. . .
<xs:element name="car">
<xs:complexType>
<xs:attribute name="regState" type="twoLetterCode"/>
<xs:attribute name="regPlate" type="xs:integer"/>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element></pre></div><div class="exampleWrapper">A <code>state</code> element is defined, which
contains a <code>code</code> child and some <code>vehicle</code> and <code>person</code>
children. A <code>vehicle</code> in turn has a <code>plateNumber</code> attribute,
which is an integer, and a <code>state</code> attribute. State's
<code>code</code>s are a key for them within the document. Vehicle's
<code>plateNumber</code>s are a key for them within states, and
<code>state</code> and
<code>plateNumber</code> is asserted to be a <i>key</i> for
<code>vehicle</code> within the document as a whole. Furthermore, a <code>person</code> element has
an empty <code>car</code> child, with <code>regState</code> and
<code>regPlate</code> attributes, which are then asserted together to refer to
<code>vehicle</code>s via the <code>carRef</code> constraint. The requirement
that a <code>vehicle</code>'s <code>state</code> match its containing
<code>state</code>'s <code>code</code> is not expressed here.</div></div></div><div class="div3">
<h4><a id="d0e13803" name="d0e13803"/>3.11.3 Constraints on XML Representations of Identity-constraint Definitions</h4><div class="constraintnote"><a name="src-identity-constraint" id="src-identity-constraint"/><b>Schema Representation Constraint: Identity-constraint Definition Representation OK</b><br/><div class="constraint">In addition to the conditions imposed on <a class="eltref" href="#element-key"><key></a>, <a class="eltref" href="#element-keyref"><keyref></a> and <a class="eltref" href="#element-unique"><unique></a> element
information items by the schema for schemas, the corresponding identity-constraint definition must satisfy the conditions set
out in <a href="#coss-identity-constraint">Constraints on Identity-constraint Definition Schema Components (§3.11.6)</a>.</div></div></div><div class="div3">
<h4><a id="d0e13819" name="d0e13819"/>3.11.4 Identity-constraint Definition Validation Rules</h4><div class="constraintnote"><a name="cvc-identity-constraint" id="cvc-identity-constraint"/><b>Validation Rule: Identity-constraint Satisfied</b><br/><div class="constraint">For an element information item to be locally <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to an identity-constraint
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 The <a class="propref" href="#selector">{selector}</a>, with the element information item as the
context node, evaluates to a node-set (as defined in
<a href="#bib-xpath">[XPath]</a>). <span class="termdef"><a id="key-tns" name="key-tns">[Definition:]  </a>Call this the <b>target node set</b></span>.</div><div class="clnumber">2 Each node in the <a class="termref" href="#key-tns"><span class="arrow">·</span>target node set<span class="arrow">·</span></a> is
either the context node oran
element node among its descendants.</div><div class="clnumber">3 For each node in the <a class="termref" href="#key-tns"><span class="arrow">·</span>target node set<span class="arrow">·</span></a> all of the <a class="propref" href="#fields">{fields}</a>, with that node as the context
node, evaluate to either an empty node-set or a node-set with exactly one
member, which must have a simple type. <span class="termdef"><a id="key-ks" name="key-ks">[Definition:]  </a>Call the sequence of the
type-determined values (as defined in <a href="#ref-xsp2">[XML Schemas: Datatypes]</a>) of the
<span class="anonRef">[schema normalized value]</span> of the element and/or attribute information items in those node-sets in order the <b>key-sequence</b> of the node</span>.</div><div class="clnumber">4
<span class="termdef"><a id="key-qns" name="key-qns">[Definition:]  </a>Call the subset of the <a class="termref" href="#key-tns"><span class="arrow">·</span>target node set<span class="arrow">·</span></a> for
which all the <a class="propref" href="#fields">{fields}</a> evaluate to a node-set with exactly one
member which is an element or attribute node with a simple type the <b>qualified node set</b></span>.
The appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">4.1<a name="c-u" id="c-u"> </a><b>If </b>the <a class="propref" href="#identity-constraint_name">{identity-constraint category}</a> is <i>unique</i>, <b>then </b>no two members of the <a class="termref" href="#key-qns"><span class="arrow">·</span>qualified node
set<span class="arrow">·</span></a> have <a class="termref" href="#key-ks"><span class="arrow">·</span>key-sequences<span class="arrow">·</span></a> whose members
are pairwise equal, as defined by <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#equal">Equal</a> in <a href="#ref-xsp2">[XML Schemas: Datatypes]</a>.</div><div class="clnumber">4.2<a name="c-k" id="c-k"> </a><b>If </b>the <a class="propref" href="#identity-constraint_name">{identity-constraint category}</a> is <i>key</i>, <b>then </b>
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">4.2.1 The <a class="termref" href="#key-tns"><span class="arrow">·</span>target node set<span class="arrow">·</span></a> and the <a class="termref" href="#key-qns"><span class="arrow">·</span>qualified node
set<span class="arrow">·</span></a> are equal, that is, every member of the <a class="termref" href="#key-tns"><span class="arrow">·</span>target node set<span class="arrow">·</span></a> is also a member of the <a class="termref" href="#key-qns"><span class="arrow">·</span>qualified node
set<span class="arrow">·</span></a> and <em>vice versa</em>.</div><div class="clnumber">4.2.2 No two members of the <a class="termref" href="#key-qns"><span class="arrow">·</span>qualified node
set<span class="arrow">·</span></a> have <a class="termref" href="#key-ks"><span class="arrow">·</span>key-sequences<span class="arrow">·</span></a> whose members
are pairwise equal, as defined by <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#equal">Equal</a> in <a href="#ref-xsp2">[XML Schemas: Datatypes]</a>.</div><div class="clnumber">4.2.3<a name="c-nlbl" id="c-nlbl"> </a>No element member of the <a class="termref" href="#key-ks"><span class="arrow">·</span>key-sequence<span class="arrow">·</span></a> of any
member of the <a class="termref" href="#key-qns"><span class="arrow">·</span>qualified node
set<span class="arrow">·</span></a> was assessed as <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> by reference to an element
declaration whose <a class="propref" href="#nillable">{nillable}</a> is <i>true</i>.</div></div>
</div><div class="clnumber">4.3<a name="cl-krv" id="cl-krv"> </a><b>If </b>the <a class="propref" href="#identity-constraint_name">{identity-constraint category}</a> is <i>keyref</i>, <b>then </b>for each member of the <a class="termref" href="#key-qns"><span class="arrow">·</span>qualified node
set<span class="arrow">·</span></a> (call this the <b>keyref member</b>), there must be a <a class="termref" href="#key-nt"><span class="arrow">·</span>node table<span class="arrow">·</span></a> associated with the
<a class="propref" href="#referenced_key">{referenced key}</a> in the <a class="propref" href="#e-id_constraint_table">[identity-constraint table]</a>
of the element information item (see <a href="#sic-key">Identity-constraint Table (§3.11.5)</a>, which must be
understood as logically prior to this clause of this constraint, below) and
there must be an entry in that table whose
<a class="termref" href="#key-ks"><span class="arrow">·</span>key-sequence<span class="arrow">·</span></a> is equal to the
<b>keyref member's</b> <a class="termref" href="#key-ks"><span class="arrow">·</span>key-sequence<span class="arrow">·</span></a> member for
member, as defined by <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#equal">Equal</a> in <a href="#ref-xsp2">[XML Schemas: Datatypes]</a>.</div></div>
</div></div>
<div class="note"><b>Note: </b>The use of <span class="anonRef">[schema normalized value]</span> in the definition
of <a class="termref" href="#key-ks"><span class="arrow">·</span>key sequence<span class="arrow">·</span></a> above means that
<i>default</i> or <i>fixed</i> value constraints may play a part in <a class="termref" href="#key-ks"><span class="arrow">·</span>key sequence<span class="arrow">·</span></a>s.</div></div></div><div class="note"><b>Note: </b>Because the validation of <i>keyref</i> (see clause <a href="#cl-krv">4.3</a>) depends on finding
appropriate entries in a element information item's <a class="termref" href="#key-nt"><span class="arrow">·</span>node
table<span class="arrow">·</span></a>, and <a class="termref" href="#key-nt"><span class="arrow">·</span>node tables<span class="arrow">·</span></a> are assembled
strictly recursively from the node tables of descendants, only element
information items within the sub-tree rooted at the element information item
being <a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a> can be referenced successfully.</div><div class="note"><b>Note: </b>Although this specification defines a <a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a>
contribution which would enable schema-aware processors to implement clause <a href="#c-nlbl">4.2.3</a> above (<a href="#sic-elt-decl">Element Declaration (§3.3.5)</a>), processors are not required to
provide it. This clause can be read as if in the absence of this infoset contribution, the
value of the relevant <a class="propref" href="#nillable">{nillable}</a> property must be available.</div></div><div class="div3">
<h4><a id="d0e14060" name="d0e14060"/>3.11.5 Identity-constraint Definition Information Set Contributions</h4><div class="constraintnote"><a name="sic-key" id="sic-key"/><b>Schema Information Set Contribution: Identity-constraint Table</b><br/><div class="constraint"><span class="termdef"><a id="key-ec" name="key-ec">[Definition:]  </a>An <b>eligible
identity-constraint</b> of an element information item is one such that clause <a href="#c-u">4.1</a> or clause <a href="#c-k">4.2</a> of <a href="#cvc-identity-constraint">Identity-constraint Satisfied (§3.11.4)</a> is satisfied
with respect to that item and that constraint,
or such that any of the element information item <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> of that item have an
<a class="propref" href="#e-id_constraint_table">[identity-constraint table]</a> property whose value has an entry for that constraint</span>.<p/><span class="termdef"><a id="key-nt" name="key-nt">[Definition:]  </a>A <b>node table</b> is a set
of pairs each consisting of
a <a class="termref" href="#key-ks"><span class="arrow">·</span>key-sequence<span class="arrow">·</span></a> and an element node</span>.<p/>Whenever an element information item has one or more <a class="termref" href="#key-ec"><span class="arrow">·</span>eligible identity-constraints<span class="arrow">·</span></a>, in the <a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a> that element information item has a property as follows:<div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> element information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="e-id_constraint_table" id="e-id_constraint_table"><span class="propdef">[identity-constraint table]</span></a></dt><dd>
one
<b>Identity-constraint Binding</b>
information item for each <a class="termref" href="#key-ec"><span class="arrow">·</span>eligible identity-constraint<span class="arrow">·</span></a>, with
properties as follows:
<div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> Identity-constraint Binding information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="cb-definition" id="cb-definition"><span class="propdef">[definition]</span></a></dt><dd>The <a class="termref" href="#key-ec"><span class="arrow">·</span>eligible identity-constraint<span class="arrow">·</span></a>.</dd>
<dt><a name="cb-node_table" id="cb-node_table"><span class="propdef">[node table]</span></a></dt><dd>A <a class="termref" href="#key-nt"><span class="arrow">·</span>node table<span class="arrow">·</span></a> with one entry for every
<a class="termref" href="#key-ks"><span class="arrow">·</span>key-sequence<span class="arrow">·</span></a> (call it <b>k</b>) and node (call it <b>n</b>) such that
<b>one</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1<a name="c-kc" id="c-kc"> </a>There is an entry in one of the <a class="termref" href="#key-nt"><span class="arrow">·</span>node
tables<span class="arrow">·</span></a> associated with the <a class="propref" href="#cb-definition">[definition]</a> in an
<b>Identity-constraint Binding</b>
information item in at least one of the <a class="propref" href="#e-id_constraint_table">[identity-constraint table]</a>s of the element information item <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> of the element
information item whose <a class="termref" href="#key-ks"><span class="arrow">·</span>key-sequence<span class="arrow">·</span></a> is <b>k</b> and whose node is <b>n</b>;</div><div class="clnumber">2 <b>n</b> appears with
<a class="termref" href="#key-ks"><span class="arrow">·</span>key-sequence<span class="arrow">·</span></a> <b>k</b> in the <a class="termref" href="#key-qns"><span class="arrow">·</span>qualified node
set<span class="arrow">·</span></a> for the <a class="propref" href="#cb-definition">[definition]</a>.</div></div>
provided no two entries have the same <a class="termref" href="#key-ks"><span class="arrow">·</span>key-sequence<span class="arrow">·</span></a> but distinct nodes. Potential conflicts are resolved by not including any conflicting entries which would have owed their inclusion to clause <a href="#c-kc">1</a> above. Note that if all the conflicting entries arose under clause <a href="#c-kc">1</a> above, this means no entry at all will appear for the offending <a class="termref" href="#key-ks"><span class="arrow">·</span>key-sequence<span class="arrow">·</span></a>.</dd>
</dl></div></div>
</dd>
</dl></div></div><div class="note"><b>Note: </b>The complexity of the above arises from the fact that
<i>keyref</i> identity-constraints may be defined on domains distinct from the
embedded domain of the identity-constraint they reference, or the domains may be the
same but self-embedding at some depth. In either case the <a class="termref" href="#key-nt"><span class="arrow">·</span>node
table<span class="arrow">·</span></a> for the referenced identity-constraint needs to propagate upwards, with
conflict resolution.<p/>The <b>Identity-constraint Binding</b>
information item, unlike others in this
specification, is essentially an internal bookkeeping mechanism. It is introduced to
support the definition of <a href="#cvc-identity-constraint">Identity-constraint Satisfied (§3.11.4)</a> above.
Accordingly, conformant processors may, but are <em>not</em> required to,
expose them via
<a class="propref" href="#e-id_constraint_table">[identity-constraint table]</a> properties in the <a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a>.
In other words, the above constraints may be read as saying <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> of
identity-constraints proceeds <em>as if</em> such infoset items existed.
</div></div></div></div><div class="div3">
<h4><a id="coss-identity-constraint" name="coss-identity-constraint"/>3.11.6 Constraints on Identity-constraint Definition Schema Components</h4><p>All identity-constraint definitions (see <a href="#cIdentity-constraint_Definitions">Identity-constraint Definitions (§3.11)</a>) must satisfy the following constraint.</p><div class="constraintnote"><a name="c-props-correct" id="c-props-correct"/><b>Schema Component Constraint: Identity-constraint Definition Properties Correct</b><br/><div class="constraint"><b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 The values of the properties of an identity-constraint definition must be as described in
the property tableau in
<a href="#Identity-constraint_Definition_details">The Identity-constraint Definition Schema Component (§3.11.1)</a>, modulo the impact of <a href="#conformance-missing">Missing Sub-components (§5.3)</a>.</div><div class="clnumber">2 If the <a class="propref" href="#identity-constraint_name">{identity-constraint category}</a> is <i>keyref</i>, the
cardinality of the <a class="propref" href="#fields">{fields}</a> must equal that of the <a class="propref" href="#fields">{fields}</a> of the <a class="propref" href="#referenced_key">{referenced key}</a>.</div></div></div></div><div class="constraintnote"><a name="c-selector-xpath" id="c-selector-xpath"/><b>Schema Component Constraint: Selector Value OK</b><br/><div class="constraint"><b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 The <a class="propref" href="#selector">{selector}</a> must be a valid XPath
expression, as defined in <a href="#bib-xpath">[XPath]</a>.</div><div class="clnumber">2 <b>One</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.1 It must conform to the following extended BNF:
<table width="100%" border="1" cellpadding="5" class="scrap"><tbody><tr align="left"><td><strong><font color="red">Selector XPath expressions</font></strong></td></tr><tr><td><table border="0"><tbody><tr valign="baseline"><td><a id="Selector" name="Selector"/>[1]   </td><td><code>Selector</code></td><td>   ::=   </td><td><code><a href="#Path">Path</a> ( '|' <a href="#Path">Path</a> )*</code></td></tr></tbody><tbody><tr valign="baseline"><td><a id="Path" name="Path"/>[2]   </td><td><code>Path</code></td><td>   ::=   </td><td><code>('.//')? <a href="#Step">Step</a> ( '/' <a href="#Step">Step</a> )*</code></td></tr></tbody><tbody><tr valign="baseline"><td><a id="Step" name="Step"/>[3]   </td><td><code>Step</code></td><td>   ::=   </td><td><code>'.' | <a href="#NameTest">NameTest</a></code></td></tr></tbody><tbody><tr valign="baseline"><td><a id="NameTest" name="NameTest"/>[4]   </td><td><code>NameTest</code></td><td>   ::=   </td><td><code><a href="http://www.w3.org/TR/REC-xml-names/#NT-QName">QName</a> | '*' | <a href="http://www.w3.org/TR/REC-xml-names/#NT-NCName">NCName</a> ':' '*'</code></td></tr></tbody></table></td></tr></tbody></table>
</div><div class="clnumber">2.2 It must be an XPath expression involving the <code>child</code> axis whose abbreviated form is
as given above.</div></div></div></div>For readability, whitespace may be used in selector XPath expressions even though not
explicitly allowed by the grammar: <a href="#whitespace">whitespace</a> may be freely added within patterns before or after any <a href="#token">token</a>.
<table width="100%" border="1" cellpadding="5" class="scrap"><tbody><tr align="left"><td><strong><font color="red">Lexical productions</font></strong></td></tr><tr><td><table border="0"><tbody><tr valign="baseline"><td><a id="token" name="token"/>[5]   </td><td><code>token</code></td><td>   ::=   </td><td><code>'.' | '/' | '//' | '|' | '@' | <a href="#NameTest">NameTest</a></code></td></tr></tbody><tbody><tr valign="baseline"><td><a id="whitespace" name="whitespace"/>[6]   </td><td><code>whitespace</code></td><td>   ::=   </td><td><code><a href="http://www.w3.org/TR/REC-xml#NT-S">S</a></code></td></tr></tbody></table></td></tr></tbody></table><p/>
When tokenizing, the longest possible token is always returned.</div></div><div class="constraintnote"><a name="c-fields-xpaths" id="c-fields-xpaths"/><b>Schema Component Constraint: Fields Value OK</b><br/><div class="constraint"><b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 Each member of the <a class="propref" href="#fields">{fields}</a> must be a valid XPath
expression, as defined in <a href="#bib-xpath">[XPath]</a>.</div><div class="clnumber">2 <b>One</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.1 It must conform to the extended BNF given
above for <a href="#Selector">Selector</a>, with the following modification:
<table width="100%" border="1" cellpadding="5" class="scrap"><tbody><tr align="left"><td><strong><font color="red">Path in Field XPath expressions</font></strong></td></tr><tr><td><table border="0"><tbody><tr valign="baseline"><td><a id="fPath" name="fPath"/>[7]   </td><td><code>Path</code></td><td>   ::=   </td><td><code>('.//')? ( <a href="#Step">Step</a> '/' )* ( <a href="#Step">Step</a> | '@' <a href="#NameTest">NameTest</a> )</code></td></tr></tbody></table></td></tr></tbody></table>
This production differs from the one above in allowing the final
step to match an attribute node.
</div><div class="clnumber">2.2 It must be an XPath expression involving the <code>child</code> and/or <code>attribute</code> axes whose abbreviated form is
as given above.</div></div></div></div>For readability, whitespace may be used in field XPath expressions even though not
explicitly allowed by the grammar: <a href="#whitespace">whitespace</a> may be freely added within patterns before or after any <a href="#token">token</a>.
<p/>When tokenizing, the longest possible token is always returned.</div></div></div></div><div class="div2">
<h3 class="withToc"><span class="nav"><a class="nav" href="#cIdentity-constraint_Definitions"><img src="previous.jpg" alt="previous sub-section"/></a> <a class="nav" href="#cAnnotations"><img src="next.jpg" alt="next sub-section"/></a></span><a id="cNotation_Declarations" name="cNotation_Declarations"/>3.12 Notation Declarations</h3><div class="localToc">        3.12.1 <a href="#Notation_Declaration_details">The Notation Declaration Schema Component</a><br/>
        3.12.2 <a href="#declare-notation">XML Representation of Notation Declaration Schema Components</a><br/>
        3.12.3 <a href="#d0e14542">Constraints on XML Representations of Notation Declarations</a><br/>
        3.12.4 <a href="#d0e14554">Notation Declaration Validation Rules</a><br/>
        3.12.5 <a href="#d0e14559">Notation Declaration Information Set Contributions</a><br/>
        3.12.6 <a href="#coss-notation">Constraints on Notation Declaration Schema Components</a><br/>
</div><p>Notation declarations reconstruct XML 1.0 NOTATION declarations.</p><div class="exampleOuter"><div class="exampleHeader">Example</div><div class="exampleInner"><pre><xs:notation name="jpeg" public="image/jpeg" system="viewer.exe"></pre></div><div class="exampleWrapper">The XML representation of a notation declaration.</div></div><div class="div3">
<h4><a id="Notation_Declaration_details" name="Notation_Declaration_details"/>3.12.1 The Notation Declaration Schema Component</h4><p>The notation declaration schema component has the following
properties:</p><div class="schemaComp"><div class="compHeader"><span class="schemaComp">Schema Component</span>: <a href="#Notation_Declaration">Notation Declaration</a></div><div class="compBody">
<dl class="props">
<dt><a name="n-name" id="n-name"><span class="propdef">{name}</span></a></dt><dd>
An NCName as defined by <a href="#ref-xml-namespaces">[XML-Namespaces]</a>.
</dd>
<dt><a name="n-target_namespace" id="n-target_namespace"><span class="propdef">{target namespace}</span></a></dt><dd>
Either <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> or a namespace name, as defined in <a href="#ref-xml-namespaces">[XML-Namespaces]</a>.
</dd>
<dt><a name="system_identifier" id="system_identifier"><span class="propdef">{system identifier}</span></a></dt><dd>
Optional if <a class="propref" href="#public_identifier">{public identifier}</a> is present. A URI reference.
</dd>
<dt><a name="public_identifier" id="public_identifier"><span class="propdef">{public identifier}</span></a></dt><dd>
Optional if <a class="propref" href="#system_identifier">{system identifier}</a> is present. A public identifier, as defined in <a href="#ref-xml">[XML 1.0 (Second Edition)]</a>.
</dd>
<dt><a name="n-annotation" id="n-annotation"><span class="propdef">{annotation}</span></a></dt><dd>Optional. An annotation.</dd>
</dl>
</div></div><p>Notation declarations do not participate in <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> as such.
They are referenced in the course of <a class="termref" href="#key-vn"><span class="arrow">·</span>validating<span class="arrow">·</span></a> strings as members of
the <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#NOTATION">NOTATION</a> simple type.</p><p>See <a href="#cAnnotations">Annotations (§3.13)</a> for information on the role of the
<a class="propref" href="#n-annotation">{annotation}</a> property.</p></div><div class="div3">
<h4><a id="declare-notation" name="declare-notation"/>3.12.2 XML Representation of Notation Declaration Schema Components</h4><p>The XML representation for a notation declaration schema component is
a
<a class="eltref" href="#element-notation"><notation></a>
element information item. The correspondences between the
properties of that information item and
properties of the component it corresponds to are as follows:</p><div class="reprdef"><div class="reprHeader"><span class="reprdef">XML Representation Summary</span>: <code>notation</code> Element Information Item</div><div class="reprBody">
<p class="element-syntax-1"><a name="element-notation" id="element-notation"><notation</a><br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  <b>name</b> = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#NCName">NCName</a><br/>  public = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#token">token</a><br/>  system = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#anyURI">anyURI</a><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?)<br/></notation></p>
<div class="reprcomp"><table class="reprcomp"><thead><tr><th><a href="#Notation_Declaration_details">Notation Declaration</a><strong> Schema Component</strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Representation</th></tr></thead><tbody valign="top"><tr valign="top"><td><a class="propref" href="#n-name">{name}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the
<code>name</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a></td></tr><tr valign="top"><td><a class="propref" href="#n-target_namespace">{target namespace}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the
<code>targetNamespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of the parent <code>schema</code>
element information item.</td></tr><tr valign="top"><td><a class="propref" href="#system_identifier">{system identifier}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>system</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, if present, otherwise <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</td></tr><tr valign="top"><td><a class="propref" href="#public_identifier">{public identifier}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>public</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a></td></tr><tr valign="top"><td><a class="propref" href="#n-annotation">{annotation}</a></td><td>The annotation corresponding to the <a class="eltref" href="#element-annotation"><annotation></a> element information item in the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if present, otherwise <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</td></tr></tbody></table></td></tr></tbody></table></div></div></div><div class="exampleOuter"><div class="exampleHeader">Example</div><div class="exampleInner"><pre><xs:notation name="jpeg"
public="image/jpeg" system="viewer.exe" />
<xs:element name="picture">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:hexBinary">
<xs:attribute name="pictype">
<xs:simpleType>
<xs:restriction base="xs:NOTATION">
<xs:enumeration value="jpeg"/>
<xs:enumeration value="png"/>
. . .
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
<picture pictype="jpeg">...</picture></pre></div></div></div><div class="div3">
<h4><a id="d0e14542" name="d0e14542"/>3.12.3 Constraints on XML Representations of Notation Declarations</h4><div class="constraintnote"><a name="src-notation" id="src-notation"/><b>Schema Representation Constraint: Notation Definition Representation OK</b><br/><div class="constraint">In addition to the conditions imposed on <a class="eltref" href="#element-notation"><notation></a> element
information items by the schema for schemas, the corresponding notation definition must satisfy the conditions set
out in <a href="#coss-notation">Constraints on Notation Declaration Schema Components (§3.12.6)</a>.</div></div></div><div class="div3">
<h4><a id="d0e14554" name="d0e14554"/>3.12.4 Notation Declaration Validation Rules</h4><p>None as such.</p></div><div class="div3">
<h4><a id="d0e14559" name="d0e14559"/>3.12.5 Notation Declaration Information Set Contributions</h4><div class="constraintnote"><a name="sic-notation-used" id="sic-notation-used"/><b>Schema Information Set Contribution: Validated with Notation</b><br/><div class="constraint">Whenever an attribute information item is <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to a <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#NOTATION">NOTATION</a>, in the <a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a> its parent element information item either has a property as follows:<div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> element information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="e-notation" id="e-notation"><span class="propdef">[notation]</span></a></dt><dd>An
<a class="termref" href="#key-iso"><span class="arrow">·</span>item isomorphic<span class="arrow">·</span></a> to the notation declaration whose <a class="propref" href="#n-name">{name}</a> and <a class="propref" href="#n-target_namespace">{target namespace}</a> match the <a class="termref" href="#q-local"><span class="arrow">·</span>local name<span class="arrow">·</span></a> and <a class="termref" href="#q-uri"><span class="arrow">·</span>namespace name<span class="arrow">·</span></a> (as defined in <a href="#src-qname">QName Interpretation (§3.15.3)</a>) of the attribute item's <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a></dd>
</dl></div></div>or has a pair of properties as follows:<div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> element information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="e-notation_system" id="e-notation_system"><span class="propdef">[notation system]</span></a></dt><dd>The value of the <a class="propref" href="#system_identifier">{system identifier}</a> of that notation declaration.</dd>
<dt><a name="e-notation_public" id="e-notation_public"><span class="propdef">[notation public]</span></a></dt><dd>The value of the <a class="propref" href="#public_identifier">{public identifier}</a> of that notation declaration.</dd>
</dl></div></div><div class="note"><b>Note: </b>For compatibility, only one such attribute should appear on any given
element. If more than one such attribute <em>does</em> appear, which one
supplies the infoset property or properties above is not defined.</div></div></div></div><div class="div3">
<h4><a id="coss-notation" name="coss-notation"/>3.12.6 Constraints on Notation Declaration Schema Components</h4><p>All notation declarations (see <a href="#cNotation_Declarations">Notation Declarations (§3.12)</a>) must satisfy the following constraint.</p><div class="constraintnote"><a name="n-props-correct" id="n-props-correct"/><b>Schema Component Constraint: Notation Declaration Correct</b><br/><div class="constraint">The values of the properties of a notation declaration must be as described in
the property tableau in
<a href="#Notation_Declaration_details">The Notation Declaration Schema Component (§3.12.1)</a>, modulo the impact of <a href="#conformance-missing">Missing Sub-components (§5.3)</a>.</div></div></div></div><div class="div2">
<h3 class="withToc"><span class="nav"><a class="nav" href="#cNotation_Declarations"><img src="previous.jpg" alt="previous sub-section"/></a> <a class="nav" href="#Simple_Type_Definitions"><img src="next.jpg" alt="next sub-section"/></a></span><a id="cAnnotations" name="cAnnotations"/>3.13 Annotations</h3><div class="localToc">        3.13.1 <a href="#Annotation_details">The Annotation Schema Component</a><br/>
        3.13.2 <a href="#declare-annotation">XML Representation of Annotation Schema Components</a><br/>
        3.13.3 <a href="#d0e14747">Constraints on XML Representations of Annotations</a><br/>
        3.13.4 <a href="#d0e14759">Annotation Validation Rules</a><br/>
        3.13.5 <a href="#d0e14764">Annotation Information Set Contributions</a><br/>
        3.13.6 <a href="#coss-annotation">Constraints on Annotation Schema Components</a><br/>
</div><p>Annotations provide for human- and machine-targeted annotations of
schema components.</p><div class="exampleOuter"><div class="exampleHeader">Example</div><div class="exampleInner"><pre><xs:simpleType fn:note="special">
<xs:annotation>
<xs:documentation>A type for experts only</xs:documentation>
<xs:appinfo>
<fn:specialHandling>checkForPrimes</fn:specialHandling>
</xs:appinfo>
</xs:annotation>
</pre></div><div class="exampleWrapper">XML representations of three kinds of annotation.</div></div><div class="div3">
<h4><a id="Annotation_details" name="Annotation_details"/>3.13.1 The Annotation Schema Component</h4><p>The annotation schema component has the following
properties:</p><div class="schemaComp"><div class="compHeader"><span class="schemaComp">Schema Component</span>: <a href="#Annotation">Annotation</a></div><div class="compBody">
<dl class="props">
<dt><a name="application_information" id="application_information"><span class="propdef">{application information}</span></a></dt><dd>
A sequence of element information items.
</dd>
<dt><a name="user_information" id="user_information"><span class="propdef">{user information}</span></a></dt><dd>
A sequence of element information items.
</dd>
<dt><a name="attributes" id="attributes"><span class="propdef">{attributes}</span></a></dt><dd>A sequence of attribute
information items.</dd>
</dl>
</div></div><p><a class="propref" href="#user_information">{user information}</a> is intended for human consumption,
<a class="propref" href="#application_information">{application information}</a> for automatic processing. In both
cases, provision is made for an optional URI reference to supplement the local
information, as the value of the <code>source</code> attribute of the
respective element information items. <a class="termref" href="#key-vn"><span class="arrow">·</span>Validation<span class="arrow">·</span></a> does <em>not</em> involve dereferencing these URIs, when present. In the case of <a class="propref" href="#user_information">{user information}</a>, indication should be given as to the identity of the (human) language used in the contents, using the <code>xml:lang</code> attribute.</p><p><a class="propref" href="#attributes">{attributes}</a> ensures that when schema authors take
advantage of the provision for adding attributes from namespaces other than the
XML Schema namespace to schema documents, they are available within the components
corresponding to the element items where such attributes appear.</p><p>Annotations do not participate in <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> as such. Provided
an annotation itself satisfies all relevant <a class="termref" href="#gloss-cos"><span class="arrow">·</span>Schema
Component Constraints<span class="arrow">·</span></a> it <em>cannot</em> affect the <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> of element information items.</p></div><div class="div3">
<h4><a id="declare-annotation" name="declare-annotation"/>3.13.2 XML Representation of Annotation Schema Components</h4><p>Annotation of schemas and schema components, with material for human or
computer consumption, is provided for by allowing application information and
human information at the beginning of most major schema elements, and anywhere
at the top level of schemas. The XML representation for an annotation schema component is
an
<a class="eltref" href="#element-annotation"><annotation></a>
element information item. The correspondences between the
properties of that information item and
properties of the component it corresponds to are as follows:</p><div class="reprdef"><div class="reprHeader"><span class="reprdef">XML Representation Summary</span>: <code>annotation</code> Element Information Item</div><div class="reprBody">
<p class="element-syntax-1"><a name="element-annotation" id="element-annotation"><annotation</a><br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-appinfo">appinfo</a> | <a class="eltref" href="#element-documentation">documentation</a>)*<br/></annotation></p>
<p class="element-syntax"><a name="element-appinfo" id="element-appinfo"><appinfo</a><br/>  source = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#anyURI">anyURI</a><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<em>{any}</em>)*<br/></appinfo></p>
<p class="element-syntax"><a name="element-documentation" id="element-documentation"><documentation</a><br/>  source = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#anyURI">anyURI</a><br/>  xml:lang = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#language">language</a><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<em>{any}</em>)*<br/></documentation></p>
<div class="reprcomp"><table class="reprcomp"><thead><tr><th><a href="#Annotation_details">Annotation</a><strong> Schema Component</strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Representation</th></tr></thead><tbody valign="top"><tr valign="top"><td><a class="propref" href="#application_information">{application information}</a></td><td>A sequence of the <a class="eltref" href="#element-appinfo"><appinfo></a> element
information items from among the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, in order, if any, otherwise the
empty sequence.</td></tr><tr valign="top"><td><a class="propref" href="#user_information">{user information}</a></td><td>A sequence of the <a class="eltref" href="#element-documentation"><documentation></a> element
information items from among the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, in order, if any, otherwise the
empty sequence.</td></tr><tr valign="top"><td><a class="propref" href="#attributes">{attributes}</a></td><td>A sequence of attribute information items, namely
those allowed by the attribute wildcard in the type definition for the <a class="eltref" href="#element-annotation"><annotation></a> item itself or for the enclosing items which correspond to the component within which the annotation component is located.</td></tr></tbody></table></td></tr></tbody></table></div></div></div><p>The annotation component corresponding to the <a class="eltref" href="#element-annotation"><annotation></a>
element in the example above will have one element item in each of its <a class="propref" href="#user_information">{user information}</a> and <a class="propref" href="#application_information">{application information}</a> and one attribute item in its <a class="propref" href="#attributes">{attributes}</a>.</p></div><div class="div3">
<h4><a id="d0e14747" name="d0e14747"/>3.13.3 Constraints on XML Representations of Annotations</h4><div class="constraintnote"><a name="src-annotation" id="src-annotation"/><b>Schema Representation Constraint: Annotation Definition Representation OK</b><br/><div class="constraint">In addition to the conditions imposed on <a class="eltref" href="#element-annotation"><annotation></a> element
information items by the schema for schemas, the corresponding annotation must satisfy the conditions set
out in <a href="#coss-annotation">Constraints on Annotation Schema Components (§3.13.6)</a>.</div></div></div><div class="div3">
<h4><a id="d0e14759" name="d0e14759"/>3.13.4 Annotation Validation Rules</h4><p>None as such.</p></div><div class="div3">
<h4><a id="d0e14764" name="d0e14764"/>3.13.5 Annotation Information Set Contributions</h4><p>None as such: the addition of annotations to the <a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a> is
covered by the <a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a> contributions of the enclosing components.</p></div><div class="div3">
<h4><a id="coss-annotation" name="coss-annotation"/>3.13.6 Constraints on Annotation Schema Components</h4><p>All annotations (see <a href="#cAnnotations">Annotations (§3.13)</a>) must satisfy the following constraint.</p><div class="constraintnote"><a name="an-props-correct" id="an-props-correct"/><b>Schema Component Constraint: Annotation Correct</b><br/><div class="constraint">The values of the properties of an annotation must be as described in
the property tableau in
<a href="#Annotation_details">The Annotation Schema Component (§3.13.1)</a>, modulo the impact of <a href="#conformance-missing">Missing Sub-components (§5.3)</a>.</div></div></div></div><div class="div2">
<h3 class="withToc"><span class="nav"><a class="nav" href="#cAnnotations"><img src="previous.jpg" alt="previous sub-section"/></a> <a class="nav" href="#Schemas"><img src="next.jpg" alt="next sub-section"/></a></span><a id="Simple_Type_Definitions" name="Simple_Type_Definitions"/>3.14 Simple Type Definitions</h3><div class="localToc">        3.14.1 <a href="#Simple_Type_Definition_details">(non-normative) The Simple Type Definition Schema Component</a><br/>
        3.14.2 <a href="#declare-datatype">(non-normative) XML Representation of Simple Type Definition Schema Components</a><br/>
        3.14.3 <a href="#d0e15439">(non-normative) Constraints on XML Representations of Simple Type Definitions</a><br/>
        3.14.4 <a href="#d0e15503">Simple Type Definition Validation Rules</a><br/>
        3.14.5 <a href="#d0e15574">Simple Type Definition Information Set
Contributions</a><br/>
        3.14.6 <a href="#coss-st">Constraints on Simple Type Definition
Schema Components</a><br/>
        3.14.7 <a href="#d0e16395">Built-in Simple Type Definition</a><br/>
</div><div class="note"><b>Note: </b>This section consists of a combination of non-normative versions of
normative material from <a href="#ref-xsp2">[XML Schemas: Datatypes]</a>, for local cross-reference
purposes, and normative material relating to the interface between schema
components defined in this specification and the simple type definition component.</div><p>Simple type definitions provide for constraining character information item <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> of element and attribute
information items.</p><div class="exampleOuter"><div class="exampleHeader">Example</div><div class="exampleInner"><pre><xs:simpleType name="fahrenheitWaterTemp">
<xs:restriction base="xs:number">
<xs:fractionDigits value="2"/>
<xs:minExclusive value="0.00"/>
<xs:maxExclusive value="100.00"/>
</xs:restriction>
</xs:simpleType></pre></div><div class="exampleWrapper">The XML representation of a simple type definition.</div></div><div class="div3">
<h4><a id="Simple_Type_Definition_details" name="Simple_Type_Definition_details"/>3.14.1 (non-normative) The Simple Type Definition Schema Component</h4><p>The simple type definition schema component has the following properties:
</p><div class="schemaComp"><div class="compHeader"><span class="schemaComp">Schema Component</span>: <a href="#Simple_Type_Definition">Simple Type Definition</a></div><div class="compBody">
<dl class="props">
<dt><a name="st-name" id="st-name"><span class="propdef">{name}</span></a></dt><dd>Optional. An NCName as defined by
<a href="#ref-xml-namespaces">[XML-Namespaces]</a>.</dd>
<dt><a name="st-target_namespace" id="st-target_namespace"><span class="propdef">{target namespace}</span></a></dt><dd>Either
<a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> or a namespace name, as defined in
<a href="#ref-xml-namespaces">[XML-Namespaces]</a>.</dd>
<dt><a name="st-base_type_definition" id="st-base_type_definition"><span class="propdef">{base type definition}</span></a></dt><dd>A simple type definition, which may be the
<a class="termref" href="#simple-ur-type-itself"><span class="arrow">·</span>simple ur-type definition<span class="arrow">·</span></a>.</dd>
<dt><a name="facets" id="facets"><span class="propdef">{facets}</span></a></dt><dd>A set of constraining
facets.</dd>
<dt><a name="fundamental_facets" id="fundamental_facets"><span class="propdef">{fundamental facets}</span></a></dt><dd>A set of
fundamental facets.</dd>
<dt><a name="st-final" id="st-final"><span class="propdef">{final}</span></a></dt><dd>
A subset of {<i>extension</i>, <i>list</i>, <i>restriction</i>, <i>union</i>}.
</dd>
<dt><a name="variety" id="variety"><span class="propdef">{variety}</span></a></dt><dd>One of {<i>atomic</i>, <i>list</i>,
<i>union</i>}. Depending on the value of <a class="propref" href="#variety">{variety}</a>, further properties are
defined as follows:
<dl><dt class="label">atomic</dt><dd><dl class="props">
<dt><a name="st-primitive_type_definition" id="st-primitive_type_definition"><span class="propdef">{primitive type definition}</span></a></dt><dd>A
built-in primitive simple type definition.</dd>
</dl></dd><dt class="label">list</dt><dd><dl class="props">
<dt><a name="st-item_type_definition" id="st-item_type_definition"><span class="propdef">{item type definition}</span></a></dt><dd>A
simple type definition.</dd>
</dl></dd><dt class="label">union</dt><dd><dl class="props">
<dt><a name="st-member_type_definitions" id="st-member_type_definitions"><span class="propdef">{member type definitions}</span></a></dt><dd>A non-empty sequence of
simple type definitions.</dd>
</dl></dd></dl>
</dd>
<dt><a name="st-annotation" id="st-annotation"><span class="propdef">{annotation}</span></a></dt><dd>Optional. An
annotation.</dd>
</dl>
</div></div><p>Simple types are identified by their <a class="propref" href="#st-name">{name}</a> and <a class="propref" href="#st-target_namespace">{target namespace}</a>. Except
for anonymous simple types (those with no <a class="propref" href="#st-name">{name}</a>), since
type definitions (i.e. both simple and complex type definitions taken together) must be uniquely identified within an <a class="termref" href="#key-schema"><span class="arrow">·</span>XML
Schema<span class="arrow">·</span></a>, no simple type definition can have the same name as another
simple or complex type definition. Simple type <a class="propref" href="#st-name">{name}</a>s and <a class="propref" href="#ct-target_namespace">{target namespace}</a>s
are provided for reference from
instances (see <a href="#xsi_type">xsi:type (§2.6.1)</a>), and for use in the XML
representation of schema components
(specifically in <a class="eltref" href="#element-element"><element></a> and <a class="eltref" href="#element-attribute"><attribute></a>). See <a href="#composition-schemaImport">References to schema components across namespaces (§4.2.3)</a> for the use of component
identifiers when importing one schema into another.</p><div class="note"><b>Note: </b>The <a class="propref" href="#st-name">{name}</a> of a simple type is not <em>ipso
facto</em> the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[(local) name]</a> of the
element or attribute information items <a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a> by that definition. The connection between a
name and a type definition is described in <a href="#cElement_Declarations">Element Declarations (§3.3)</a> and <a href="#cAttribute_Declarations">Attribute Declarations (§3.2)</a>. </div><p>A simple type definition with an empty specification for <a class="propref" href="#st-final">{final}</a> can be used as the
<a class="propref" href="#st-base_type_definition">{base type definition}</a> for other types derived by either of
extension or restriction, or as the <a class="propref" href="#st-item_type_definition">{item type definition}</a> in
the definition of a list, or in the <a class="propref" href="#st-member_type_definitions">{member type definitions}</a> of
a union; the explicit values <i>extension</i>, <i>restriction</i>,
<i>list</i> and <i>union</i> prevent further
derivations by extension (to yield a complex type) and restriction (to yield a
simple type) and use in constructing lists and unions respectively.</p><p><a class="propref" href="#variety">{variety}</a> determines whether the simple type corresponds to
an <i>atomic</i>, <i>list</i> or <i>union</i> type as defined by <a href="#ref-xsp2">[XML Schemas: Datatypes]</a>.</p><p>As described in <a href="#Type_Derivation">Type Definition Hierarchy (§2.2.1.1)</a>, every simple type definition is
a <a class="termref" href="#key-typeRestriction"><span class="arrow">·</span>restriction<span class="arrow">·</span></a> of some other simple
type (the <a class="propref" href="#st-base_type_definition">{base type definition}</a>), which is the <a class="termref" href="#key-simpleUrType"><span class="arrow">·</span>simple ur-type definition<span class="arrow">·</span></a> if and only if the type
definition in question is one of the built-in primitive datatypes, or a list or
union type definition which is not itself derived by restriction from a
list or union respectively. Each
<em>atomic</em> type is ultimately a restriction of exactly one such
built-in primitive datatype, which is its <a class="propref" href="#st-primitive_type_definition">{primitive type definition}</a>.</p><p><a class="propref" href="#facets">{facets}</a> for each simple type definition are selected from those defined in
<a href="#ref-xsp2">[XML Schemas: Datatypes]</a>. For <i>atomic</i> definitions, these are restricted to those appropriate for
the corresponding <a class="propref" href="#st-primitive_type_definition">{primitive type definition}</a>. Therefore, the value
space and lexical space (i.e. what is <a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a> by any atomic simple type) is determined by the
pair (<a class="propref" href="#st-primitive_type_definition">{primitive type definition}</a>, <a class="propref" href="#facets">{facets}</a>). </p><p>As specified in <a href="#ref-xsp2">[XML Schemas: Datatypes]</a>, <i>list</i> simple type definitions <a class="termref" href="#key-vn"><span class="arrow">·</span>validate<span class="arrow">·</span></a> space separated tokens, each of
which conforms to a specified simple type definition, the <a class="propref" href="#st-item_type_definition">{item type definition}</a>. The item type specified
must not itself be a <i>list</i> type, and must be one of the types identified in <a href="#ref-xsp2">[XML Schemas: Datatypes]</a> as a
suitable item type for a list simple type. In this case the <a class="propref" href="#facets">{facets}</a>
apply to the list itself, and are restricted to those appropriate for lists.</p><p>A <i>union</i> simple type definition <a class="termref" href="#key-vn"><span class="arrow">·</span>validates<span class="arrow">·</span></a> strings which satisfy at
least one of its <a class="propref" href="#st-member_type_definitions">{member type definitions}</a>. As in the case of
<i>list</i>, the <a class="propref" href="#facets">{facets}</a>
apply to the union itself, and are restricted to those appropriate for unions.</p><p>The <a class="termref" href="#key-simpleUrType"><span class="arrow">·</span>simple ur-type definition<span class="arrow">·</span></a>
must <em>not</em> be named as the <a class="termref" href="#st-base_type_definition"><span class="arrow">·</span>base type definition<span class="arrow">·</span></a> of any user-defined atomic simple type definitions: as it has no constraining facets, this would be incoherent.</p><p>See <a href="#cAnnotations">Annotations (§3.13)</a> for information on the role of the
<a class="propref" href="#st-annotation">{annotation}</a> property.</p></div><div class="div3">
<h4><a id="declare-datatype" name="declare-datatype"/>3.14.2 (non-normative) XML Representation of Simple Type Definition Schema Components</h4><div class="note"><b>Note: </b>This section reproduces a version of material from <a href="#ref-xsp2">[XML Schemas: Datatypes]</a>, for local cross-reference purposes.</div><div class="reprdef"><div class="reprHeader"><span class="reprdef">XML Representation Summary</span>: <code>simpleType</code> Element Information Item</div><div class="reprBody">
<p class="element-syntax-1"><a name="element-simpleType" id="element-simpleType"><simpleType</a><br/>  final =
(<var>#all</var> | List of (<var>list</var> | <var>union</var> | <var>restriction</var>))
<br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  name = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#NCName">NCName</a><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?, (<a class="eltref" href="#element-restriction">restriction</a> | <a class="eltref" href="#element-list">list</a> | <a class="eltref" href="#element-union">union</a>))<br/></simpleType></p>
<p class="element-syntax"><a name="element-restriction" id="element-restriction"><restriction</a><br/>  base = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#QName">QName</a><br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?, (<a class="eltref" href="#element-simpleType">simpleType</a>?, (<a class="eltref" href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#element-minExclusive">minExclusive</a> | <a class="eltref" href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#element-minInclusive">minInclusive</a> | <a class="eltref" href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#element-maxExclusive">maxExclusive</a> | <a class="eltref" href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#element-maxInclusive">maxInclusive</a> | <a class="eltref" href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#element-totalDigits">totalDigits</a> | <a class="eltref" href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#element-fractionDigits">fractionDigits</a> | <a class="eltref" href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#element-length">length</a> | <a class="eltref" href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#element-minLength">minLength</a> | <a class="eltref" href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#element-maxLength">maxLength</a> | <a class="eltref" href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#element-enumeration">enumeration</a> | <a class="eltref" href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#element-whiteSpace">whiteSpace</a> | <a class="eltref" href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#element-pattern">pattern</a>)*))<br/></restriction></p>
<p class="element-syntax"><a name="element-list" id="element-list"><list</a><br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  itemType = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#QName">QName</a><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?, <a class="eltref" href="#element-simpleType">simpleType</a>?)<br/></list></p>
<p class="element-syntax"><a name="element-union" id="element-union"><union</a><br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  memberTypes = List of <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#QName">QName</a><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?, <a class="eltref" href="#element-simpleType">simpleType</a>*)<br/></union></p>
<div class="reprcomp"><table class="reprcomp"><thead><tr><th><a href="#Simple_Type_Definition_details">Simple Type Definition</a><strong> Schema Component</strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Representation</th></tr></thead><tbody valign="top"><tr valign="top"><td><a class="propref" href="#st-name">{name}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>name</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> if present, otherwise <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</td></tr><tr valign="top"><td><a class="propref" href="#st-target_namespace">{target namespace}</a></td><td>The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the
<code>targetNamespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of the <a class="eltref" href="#element-schema"><schema></a> ancestor
element information item if present, otherwise <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</td></tr><tr valign="top"><td><a class="propref" href="#st-base_type_definition">{base type definition}</a></td><td>
The appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">1 <b>If </b>the <a class="eltref" href="#element-restriction"><restriction></a> alternative is chosen, <b>then </b>the type definition <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to by the
<a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>base</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of <a class="eltref" href="#element-restriction"><restriction></a>, if present, otherwise the
type definition corresponding to the <a class="eltref" href="#element-simpleType"><simpleType></a> among
the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> of <a class="eltref" href="#element-restriction"><restriction></a>.</div><div class="clnumber">2 <b>If </b>the <a class="eltref" href="#element-list"><list></a> or <a class="eltref" href="#element-union"><union></a> alternative is chosen, <b>then </b>the <a class="termref" href="#simple-ur-type-itself"><span class="arrow">·</span>simple ur-type definition<span class="arrow">·</span></a>.</div></div>
</td></tr><tr valign="top"><td><a class="propref" href="#st-final">{final}</a></td><td>As for the <a class="propref" href="#ct-exact">{prohibited substitutions}</a> property of
complex type definitions, but using the
<code>final</code> and <code>finalDefault</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> in place of the
<code>block</code> and <code>blockDefault</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> and with the
relevant set being <code>{</code><i>extension</i>,
<i>restriction</i>, <i>list</i>, <i>union</i><code>}</code>.</td></tr><tr valign="top"><td><a class="propref" href="#variety">{variety}</a></td><td>If the <a class="eltref" href="#element-list"><list></a> alternative is chosen,
then <i>list</i>, otherwise if the <a class="eltref" href="#element-union"><union></a> alternative is
chosen, then <i>union</i>, otherwise (the <a class="eltref" href="#element-restriction"><restriction></a>
alternative is chosen), then the <a class="propref" href="#variety">{variety}</a> of the <a class="propref" href="#st-base_type_definition">{base type definition}</a>.</td></tr></tbody></table></td></tr></tbody></table></div>
<div class="reprdep">If the <a class="propref" href="#variety">{variety}</a> is <i>atomic</i>, the following
additional property mappings also apply:</div>
<div class="reprcomp"><table class="reprcomp"><thead><tr><th><a href="#Simple_Type_Definition_details">Atomic Simple Type Definition</a><strong> Schema Component</strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Representation</th></tr></thead><tbody valign="top"><tr valign="top"><td><a class="propref" href="#st-primitive_type_definition">{primitive type definition}</a></td><td>The built-in primitive type
definition from which the <a class="propref" href="#st-base_type_definition">{base type definition}</a> is derived.</td></tr><tr valign="top"><td><a class="propref" href="#facets">{facets}</a></td><td>A set of facet components <a class="termref" href="#key-facets-restriction"><span class="arrow">·</span>constituting a restriction<span class="arrow">·</span></a>
of the <a class="propref" href="#facets">{facets}</a> of the
<a class="propref" href="#st-base_type_definition">{base type definition}</a> with respect to a
set of facet components corresponding to the appropriate element information items among the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> of <a class="eltref" href="#element-restriction"><restriction></a> (i.e. those which specify facets, if any), as
defined in <a href="#st-restrict-facets">Simple Type Restriction (Facets) (§3.14.6)</a>.</td></tr></tbody></table></td></tr></tbody></table></div>
<div class="reprdep">If the <a class="propref" href="#variety">{variety}</a> is <i>list</i>, the following
additional property mappings also apply:</div>
<div class="reprcomp"><table class="reprcomp"><thead><tr><th><a href="#Simple_Type_Definition_details">List Simple Type Definition</a><strong> Schema Component</strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Representation</th></tr></thead><tbody valign="top"><tr valign="top"><td><a class="propref" href="#st-item_type_definition">{item type definition}</a></td><td>
The appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">1 <b>If </b>the <a class="eltref" href="#element-list"><list></a> alternative is chosen, <b>then </b>the type definition <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to by the
<a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>itemType</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of <a class="eltref" href="#element-list"><list></a>, if present, otherwise the
type definition corresponding to the <a class="eltref" href="#element-simpleType"><simpleType></a> among
the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> of <a class="eltref" href="#element-list"><list></a>.</div><div class="clnumber">2 <b>If </b>the <a class="eltref" href="#element-restriction"><restriction></a> option is chosen, <b>then </b>the <a class="propref" href="#st-item_type_definition">{item type definition}</a> of the <a class="propref" href="#st-base_type_definition">{base type definition}</a>.</div></div>
</td></tr><tr valign="top"><td><a class="propref" href="#facets">{facets}</a></td><td>If the <a class="eltref" href="#element-restriction"><restriction></a> alternative is
chosen, a set of facet components <a class="termref" href="#key-facets-restriction"><span class="arrow">·</span>constituting a restriction<span class="arrow">·</span></a>
of the <a class="propref" href="#facets">{facets}</a> of the
<a class="propref" href="#st-base_type_definition">{base type definition}</a> with respect to a
set of facet components corresponding to the appropriate element information items among the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> of <a class="eltref" href="#element-restriction"><restriction></a> (i.e. those which specify facets, if any), as
defined in <a href="#st-restrict-facets">Simple Type Restriction (Facets) (§3.14.6)</a>, otherwise the empty set.</td></tr></tbody></table></td></tr></tbody></table></div>
<div class="reprdep">If the <a class="propref" href="#variety">{variety}</a> is <i>union</i>, the following
additional property mappings also apply:</div>
<div class="reprcomp"><table class="reprcomp"><thead><tr><th><a href="#Simple_Type_Definition_details">Union Simple Type Definition</a><strong> Schema Component</strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Representation</th></tr></thead><tbody valign="top"><tr valign="top"><td><a class="propref" href="#st-member_type_definitions">{member type definitions}</a></td><td>The appropriate <b>case</b> among the following:<div class="constraintlist"><div class="clnumber">1 <b>If </b>the <a class="eltref" href="#element-union"><union></a> alternative is chosen, <b>then </b><span class="termdef"><a id="key-exm" name="key-exm">[Definition:]  </a>define the
<b>explicit members</b> as</span> the type definitions <a class="termref" href="#src-resolve"><span class="arrow">·</span>resolved<span class="arrow">·</span></a> to by the
items in the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>memberTypes</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, if any, followed by the
type definitions corresponding to the <a class="eltref" href="#element-simpleType"><simpleType></a>s among the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> of <a class="eltref" href="#element-union"><union></a>, if any. The actual value is then formed by replacing any union type definition
in the <a class="termref" href="#key-exm"><span class="arrow">·</span>explicit members<span class="arrow">·</span></a> with the members of
their <a class="propref" href="#st-member_type_definitions">{member type definitions}</a>, in order.</div><div class="clnumber">2 <b>If </b>the <a class="eltref" href="#element-restriction"><restriction></a> option is chosen, <b>then </b>the <a class="propref" href="#st-member_type_definitions">{member type definitions}</a> of the <a class="propref" href="#st-base_type_definition">{base type definition}</a>.</div></div>
</td></tr><tr valign="top"><td><a class="propref" href="#facets">{facets}</a></td><td>If the <a class="eltref" href="#element-restriction"><restriction></a> alternative is
chosen, a set of facet components <a class="termref" href="#key-facets-restriction"><span class="arrow">·</span>constituting a restriction<span class="arrow">·</span></a>
of the <a class="propref" href="#facets">{facets}</a> of the
<a class="propref" href="#st-base_type_definition">{base type definition}</a> with respect to a
set of facet components corresponding to the appropriate element information items among the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> of <a class="eltref" href="#element-restriction"><restriction></a> (i.e. those which specify facets, if any), as
defined in <a href="#st-restrict-facets">Simple Type Restriction (Facets) (§3.14.6)</a>, otherwise the empty set.</td></tr></tbody></table></td></tr></tbody></table></div>
</div></div></div><div class="div3">
<h4><a id="d0e15439" name="d0e15439"/>3.14.3 Constraints on XML Representations of Simple Type Definitions</h4><div class="constraintnote"><a name="src-simple-type" id="src-simple-type"/><b>Schema Representation Constraint: Simple Type Definition Representation OK</b><br/><div class="constraint">In addition to the conditions imposed on <a class="eltref" href="#element-simpleType"><simpleType></a> element
information items by the schema for schemas,
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 The corresponding simple type definition, if any, must satisfy the conditions set
out in <a href="#coss-st">Constraints on Simple Type Definition
Schema Components (§3.14.6)</a>.</div><div class="clnumber">2 If the <a class="eltref" href="#element-restriction"><restriction></a> alternative is chosen, either
it must have a <code>base</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> or a <a class="eltref" href="#element-simpleType"><simpleType></a>
among its <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, but not both.</div><div class="clnumber">3 If the <a class="eltref" href="#element-list"><list></a> alternative is chosen, either
it must have an <code>itemType</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> or a <a class="eltref" href="#element-simpleType"><simpleType></a>
among its <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, but not both.</div><div class="clnumber">4 Circular union type definition is disallowed. That is, if the <a class="eltref" href="#element-union"><union></a> alternative is chosen, there must not be any entries in the <code>memberTypes</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> at any depth which resolve to the component corresponding to the <a class="eltref" href="#element-simpleType"><simpleType></a>.</div></div>
</div></div></div><div class="div3">
<h4><a id="d0e15503" name="d0e15503"/>3.14.4 Simple Type Definition Validation Rules</h4><div class="constraintnote"><a name="cvc-simple-type" id="cvc-simple-type"/><b>Validation Rule: String Valid</b><br/><div class="constraint">For a string to be locally <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to a simple type definition
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 It is schema-valid with respect to that definition as defined by
<a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#cvc-datatype-valid">Datatype Valid</a> in <a href="#ref-xsp2">[XML Schemas: Datatypes]</a>.</div><div class="clnumber">2 The appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">2.1 <b>If </b>The definition is <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ENTITY">ENTITY</a> or is validly
derived from <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ENTITY">ENTITY</a> given the empty set,
as defined in <a href="#cos-st-derived-ok">Type Derivation OK (Simple) (§3.14.6)</a>, <b>then </b>the string must be a <a class="termref" href="#key-vde"><span class="arrow">·</span>declared
entity name<span class="arrow">·</span></a>.</div><div class="clnumber">2.2 <b>If </b>The definition is <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ENTITIES">ENTITIES</a> or is validly
derived from <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ENTITIES">ENTITIES</a> given the empty set,
as defined in <a href="#cos-st-derived-ok">Type Derivation OK (Simple) (§3.14.6)</a>, <b>then </b>every whitespace-delimited substring of the string must be a <a class="termref" href="#key-vde"><span class="arrow">·</span>declared
entity name<span class="arrow">·</span></a>.</div><div class="clnumber">2.3 <b>otherwise </b>no further condition applies.</div></div></div></div>
<p/><span class="termdef"><a id="key-vde" name="key-vde">[Definition:]  </a>A string is a <b>declared entity name</b> if it is equal to the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.entity.unparsed">[name]</a> of some unparsed entity
information item in the value of the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.document">[unparsedEntities]</a> property of the document information item
at the root of the infoset containing the element or attribute information item
whose <a class="termref" href="#key-nv"><span class="arrow">·</span>normalized value<span class="arrow">·</span></a> the string is.</span></div></div></div><div class="div3">
<h4><a id="d0e15574" name="d0e15574"/>3.14.5 Simple Type Definition Information Set
Contributions</h4><p>None as such.</p></div><div class="div3">
<h4><a id="coss-st" name="coss-st"/>3.14.6 Constraints on Simple Type Definition
Schema Components</h4><p>All simple type definitions other than the <a class="termref" href="#simple-ur-type-itself"><span class="arrow">·</span>simple ur-type
definition<span class="arrow">·</span></a> and the built-in primitive datatype definitions (see <a href="#Simple_Type_Definitions">Simple Type Definitions (§3.14)</a>) must satisfy both the following constraints.</p><div class="constraintnote"><a name="st-props-correct" id="st-props-correct"/><b>Schema Component Constraint: Simple Type Definition Properties Correct</b><br/><div class="constraint"><b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 The values of the properties of a simple type definition must be as described in
the property tableau in
<a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#dc-defn">Datatype definition</a>, modulo the impact of <a href="#conformance-missing">Missing Sub-components (§5.3)</a>.</div><div class="clnumber">2 All simple type definitions must be derived
ultimately from the <a class="termref" href="#simple-ur-type-itself"><span class="arrow">·</span>simple ur-type
definition (so<span class="arrow">·</span></a> circular definitions are disallowed). That is, it must be possible to reach a built-in
primitive datatype or the <a class="termref" href="#simple-ur-type-itself"><span class="arrow">·</span>simple ur-type definition<span class="arrow">·</span></a> by repeatedly following the <a class="propref" href="#st-base_type_definition">{base type definition}</a>.</div><div class="clnumber">3 The <a class="propref" href="#st-final">{final}</a> of the <a class="propref" href="#st-base_type_definition">{base type definition}</a> must not contain <i>restriction</i>.</div></div></div></div><div class="constraintnote"><a name="cos-st-restricts" id="cos-st-restricts"/><b>Schema Component Constraint: Derivation Valid (Restriction, Simple)</b><br/><div class="constraint">The appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">1 <b>If </b>the <a class="propref" href="#variety">{variety}</a> is <i>atomic</i>, <b>then </b>
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1.1 The <a class="propref" href="#st-base_type_definition">{base type definition}</a> must be an atomic simple type
definition or a built-in
primitive datatype.</div><div class="clnumber">1.2 The <a class="propref" href="#st-final">{final}</a> of the <a class="propref" href="#st-base_type_definition">{base type definition}</a> must not contain <i>restriction</i>.</div><div class="clnumber">1.3 For each facet in the <a class="propref" href="#facets">{facets}</a> (call this <b>DF</b>)
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1.3.1 <b>DF</b> must be an allowed constraining facet for the
<a class="propref" href="#st-primitive_type_definition">{primitive type definition}</a>, as specified in the appropriate
subsection of <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#built-in-primitive-datatypes">3.2 Primitive datatypes</a>.</div><div class="clnumber">1.3.2 If there is a facet of the same kind in the
<a class="propref" href="#facets">{facets}</a> of the <a class="propref" href="#st-base_type_definition">{base type definition}</a> (call
this <b>BF</b>),then the <b>DF</b>'s
<span class="anonRef">{value}</span> must be a valid restriction of <b>BF</b>'s <span class="anonRef">{value}</span> as
defined in <a href="#ref-xsp2">[XML Schemas: Datatypes]</a>.</div></div>
</div></div></div><div class="clnumber">2 <b>If </b>the <a class="propref" href="#variety">{variety}</a> is <i>list</i>, <b>then </b>
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.1 The <a class="propref" href="#st-item_type_definition">{item type definition}</a> must have a <a class="propref" href="#variety">{variety}</a> of <i>atomic</i> or <i>union</i> (in which case all the <a class="propref" href="#st-member_type_definitions">{member type definitions}</a> must be <i>atomic</i>).</div><div class="clnumber">2.2 </div><div class="clnumber">2.3 The appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">2.3.1 <b>If </b>the <a class="propref" href="#st-base_type_definition">{base type definition}</a>
is the
<a class="termref" href="#simple-ur-type-itself"><span class="arrow">·</span>simple ur-type definition<span class="arrow">·</span></a>
, <b>then </b>
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.3.1.1 The <a class="propref" href="#st-final">{final}</a> of the <a class="propref" href="#st-item_type_definition">{item type definition}</a> must not contain <i>list</i>.</div><div class="clnumber">2.3.1.2 The <a class="propref" href="#facets">{facets}</a> must only contain the
<i>whiteSpace</i> facet component.</div></div>
</div><div class="clnumber">2.3.2 <b>otherwise </b>
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.3.2.1 The <a class="propref" href="#st-base_type_definition">{base type definition}</a> must have a <a class="propref" href="#variety">{variety}</a> of <i>list</i>.</div><div class="clnumber">2.3.2.2 The <a class="propref" href="#st-final">{final}</a> of the <a class="propref" href="#st-base_type_definition">{base type definition}</a> must not contain <i>restriction</i>.</div><div class="clnumber">2.3.2.3 The <a class="propref" href="#st-item_type_definition">{item type definition}</a> must
be validly derived from the <a class="propref" href="#st-base_type_definition">{base type definition}</a>'s <a class="propref" href="#st-item_type_definition">{item type definition}</a> given the empty set, as defined in <a href="#cos-st-derived-ok">Type Derivation OK (Simple) (§3.14.6)</a>.</div><div class="clnumber">2.3.2.4 Only <i>length</i>, <i>minLength</i>, <i>maxLength</i>, <i>whiteSpace</i>,
<i>pattern</i> and <i>enumeration</i> facet components are allowed among
the <a class="propref" href="#facets">{facets}</a>.</div><div class="clnumber">2.3.2.5 For each facet in the <a class="propref" href="#facets">{facets}</a> (call this <b>DF</b>), if there is a facet of the same kind in the
<a class="propref" href="#facets">{facets}</a> of the <a class="propref" href="#st-base_type_definition">{base type definition}</a> (call
this <b>BF</b>),then the <b>DF</b>'s
<span class="anonRef">{value}</span> must be a valid restriction of <b>BF</b>'s <span class="anonRef">{value}</span> as
defined in <a href="#ref-xsp2">[XML Schemas: Datatypes]</a>.</div></div>
</div></div>The first case above will apply when a list is derived by
specifying an item type, the second when derived by restriction from another list.</div></div></div><div class="clnumber">3 <b>If </b>the <a class="propref" href="#variety">{variety}</a> is <i>union</i>, <b>then </b>
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">3.1 The <a class="propref" href="#st-member_type_definitions">{member type definitions}</a> must all have <a class="propref" href="#variety">{variety}</a> of <i>atomic</i> or <i>list</i>.</div><div class="clnumber">3.2 </div><div class="clnumber">3.3 The appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">3.3.1 <b>If </b>the <a class="propref" href="#st-base_type_definition">{base type definition}</a>
is the
<a class="termref" href="#simple-ur-type-itself"><span class="arrow">·</span>simple ur-type definition<span class="arrow">·</span></a>
, <b>then </b>
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">3.3.1.1 All of the <a class="propref" href="#st-member_type_definitions">{member type definitions}</a> must
have a <a class="propref" href="#st-final">{final}</a> which does not contain <i>union</i>.</div><div class="clnumber">3.3.1.2 The <a class="propref" href="#facets">{facets}</a> must be empty.</div></div>
</div><div class="clnumber">3.3.2 <b>otherwise </b>
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">3.3.2.1 The <a class="propref" href="#st-base_type_definition">{base type definition}</a> must have a <a class="propref" href="#variety">{variety}</a> of <i>union</i>.</div><div class="clnumber">3.3.2.2 The <a class="propref" href="#st-final">{final}</a> of the <a class="propref" href="#st-base_type_definition">{base type definition}</a> must not contain <i>restriction</i>.</div><div class="clnumber">3.3.2.3 The <a class="propref" href="#st-member_type_definitions">{member type definitions}</a>, in order, must
be validly derived from the corresponding type definitions in the <a class="propref" href="#st-base_type_definition">{base type definition}</a>'s <a class="propref" href="#st-member_type_definitions">{member type definitions}</a> given the empty set, as defined in <a href="#cos-st-derived-ok">Type Derivation OK (Simple) (§3.14.6)</a>.</div><div class="clnumber">3.3.2.4 Only <i>pattern</i> and <i>enumeration</i> facet components are allowed among
the <a class="propref" href="#facets">{facets}</a>.</div><div class="clnumber">3.3.2.5 For each facet in the <a class="propref" href="#facets">{facets}</a> (call this <b>DF</b>), if there is a facet of the same kind in the
<a class="propref" href="#facets">{facets}</a> of the <a class="propref" href="#st-base_type_definition">{base type definition}</a> (call
this <b>BF</b>),then the <b>DF</b>'s
<span class="anonRef">{value}</span> must be a valid restriction of <b>BF</b>'s <span class="anonRef">{value}</span> as
defined in <a href="#ref-xsp2">[XML Schemas: Datatypes]</a>.</div></div>
</div></div>The first case above will apply when a union is derived by
specifying one or more member types, the second when derived by restriction from another union.</div></div></div></div><span class="termdef"><a id="cd-st-restriction" name="cd-st-restriction">[Definition:]  </a>If this
constraint <a href="#cos-st-restricts">Derivation Valid (Restriction, Simple) (§3.14.6)</a> holds of a simple type definition, it is a <b>valid
restriction</b> of its <a class="termref" href="#st-base_type_definition"><span class="arrow">·</span>base type definition<span class="arrow">·</span></a></span>.</div></div><p>The following constraint defines relations appealed to elsewhere in this specification.</p><div class="constraintnote"><a name="cos-st-derived-ok" id="cos-st-derived-ok"/><b>Schema Component Constraint: Type Derivation OK (Simple)</b><br/><div class="constraint">For a simple type definition (call it <b>D</b>, for derived) to be validly
derived from a type definition (call this <b>B</b>, for base) given a
subset of {<i>extension</i>, <i>restriction</i>, <i>list</i>, <i>union</i>} (of which
only <i>restriction</i> is actually relevant)
<b>one</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1<a name="c-stid" id="c-stid"> </a>They are the same type
definition.</div><div class="clnumber">2 <b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.1 <i>restriction</i> is not in the
subset, or in the <a class="propref" href="#st-final">{final}</a> of its own <a class="propref" href="#st-base_type_definition">{base type definition}</a>;</div><div class="clnumber">2.2 <b>One</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.2.1 <b>D</b>'s <a class="termref" href="#st-base_type_definition"><span class="arrow">·</span>base type definition<span class="arrow">·</span></a> is <b>B</b>.</div><div class="clnumber">2.2.2 <b>D</b>'s <a class="termref" href="#st-base_type_definition"><span class="arrow">·</span>base type definition<span class="arrow">·</span></a> is not the
<a class="termref" href="#ur-type-itself"><span class="arrow">·</span>ur-type definition<span class="arrow">·</span></a> and is validly derived
from <b>B</b> given the subset, as defined by this constraint.</div><div class="clnumber">2.2.3 <b>D</b>'s <a class="propref" href="#variety">{variety}</a> is <i>list</i> or <i>union</i> and <b>B</b>
is the <a class="termref" href="#simple-ur-type-itself"><span class="arrow">·</span>simple ur-type definition<span class="arrow">·</span></a>.</div><div class="clnumber">2.2.4 <b>B</b>'s <a class="propref" href="#variety">{variety}</a> is <i>union</i> and
<b>D</b> is validly derived
from a type definition in <b>B</b>'s <a class="propref" href="#st-member_type_definitions">{member type definitions}</a> given the subset, as defined by this constraint.</div></div></div></div></div></div>
</div></div><div class="note"><b>Note: </b>With respect to clause <a href="#c-stid">1</a>, see the Note on identity at
the end of <a href="#no-identity"> (§3.4.6)</a> above.</div><div class="constraintnote"><a name="st-restrict-facets" id="st-restrict-facets"/><b>Schema Component Constraint: Simple Type Restriction (Facets)</b><br/><div class="constraint">For a simple type definition (call it <b>R</b>) to restrict another simple type
definition (call it <b>B</b>) with a
set of facets (call this <b>S</b>)
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 The <a class="propref" href="#variety">{variety}</a> of <b>R</b> is the same as that of <b>B</b>.</div><div class="clnumber">2 If <a class="propref" href="#variety">{variety}</a> is <i>atomic</i>, the
<a class="propref" href="#st-primitive_type_definition">{primitive type definition}</a> of <b>R</b> is the same as that of <b>B</b>.</div><div class="clnumber">3<a name="c-fr" id="c-fr"> </a>The <a class="propref" href="#facets">{facets}</a> of <b>R</b> are the union of <b>S</b> and
the <a class="propref" href="#facets">{facets}</a> of <b>B</b>, eliminating duplicates. To eliminate
duplicates, when a facet of the same kind occurs in both <b>S</b> and
the <a class="propref" href="#facets">{facets}</a> of <b>B</b>, the one in the <a class="propref" href="#facets">{facets}</a>
of <b>B</b> is not included, with the exception of <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#dt-enumeration">enumeration</a> and <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#dt-pattern">pattern</a> facets, for which multiple occurrences with distinct values are allowed.<p/>Additional constraint(s) may apply depending on the kind of facet, see
the appropriate sub-section of <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#rf-facets">4.3
Constraining Facets</a></div></div>
<p/><span class="termdef"><a id="key-facets-restriction" name="key-facets-restriction">[Definition:]  </a>If
clause <a href="#c-fr">3</a> above holds, the <a class="propref" href="#facets">{facets}</a> of <b>R</b>
<b>constitute a restriction</b> of the <a class="propref" href="#facets">{facets}</a> of
<b>B</b> with respect to <b>S</b></span>.</div></div></div><div class="div3">
<h4><a id="d0e16395" name="d0e16395"/>3.14.7 Built-in Simple Type Definition</h4><p>There is a simple type definition nearly equivalent to the <a class="termref" href="#key-simpleUrType"><span class="arrow">·</span>simple ur-type definition<span class="arrow">·</span></a> present in every
schema by definition. It has the following properties:</p><table border="1" class="schemaComp"><thead><tr><th><strong><a name="simple-ur-type-itself" id="simple-ur-type-itself">Simple Type Definition of the Ur-Type</a></strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Value</th></tr></thead><tbody valign="top"><tr><td><a class="propref" href="#st-name">{name}</a></td><td>anySimpleType</td></tr><tr><td><a class="propref" href="#st-target_namespace">{target namespace}</a></td><td>http://www.w3.org/2001/XMLSchema</td></tr><tr><td><a class="propref" href="#st-base_type_definition">{base type definition}</a></td><td><a class="termref" href="#ur-type-itself"><span class="arrow">·</span>the ur-type definition<span class="arrow">·</span></a></td></tr><tr><td><a class="propref" href="#st-final">{final}</a></td><td>The empty set</td></tr><tr><td><a class="propref" href="#variety">{variety}</a></td><td><a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a></td></tr></tbody></table></td></tr></tbody></table><p>The <a class="termref" href="#key-simpleUrType"><span class="arrow">·</span>simple ur-type definition<span class="arrow">·</span></a> is the root of the simple type definition
hierarchy, and as such mediates between the other simple type
definitions, which all eventually trace back to it via their <a class="propref" href="#st-base_type_definition">{base type definition}</a> properties, and the <a class="termref" href="#key-urType"><span class="arrow">·</span>ur-type definition<span class="arrow">·</span></a>, which is
<em>its</em> <a class="propref" href="#st-base_type_definition">{base type definition}</a>. This is
why the <a class="termref" href="#simple-ur-type-itself"><span class="arrow">·</span>simple ur-type definition<span class="arrow">·</span></a> is exempted
from the first clause of <a href="#st-props-correct">Simple Type Definition Properties Correct (§3.14.6)</a>, which would
otherwise bar it because of its derivation from a complex type definition and absence of <a class="propref" href="#variety">{variety}</a>.</p><p>Simple type definitions for all the built-in primitive datatypes, namely <i>string</i>, <i>boolean</i>, <i>float</i>,
<i>double</i>, <i>number</i>, <i>dateTime</i>, <i>duration</i>,
<i>time</i>, <i>date</i>, <i>gMonth</i>, <i>gMonthDay</i>, <i>gDay</i>, <i>gYear</i>, <i>gYearMonth</i>, <i>hexBinary</i>, <i>base64Binary</i>, <i>anyURI</i> (see the <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#built-in-primitive-datatypes">Primitive
Datatypes</a> section of <a href="#ref-xsp2">[XML Schemas: Datatypes]</a>) are present by definition in every schema. All
are in the XML Schema <a class="propref" href="#st-target_namespace">{target namespace}</a> (namespace
name <code>http://www.w3.org/2001/XMLSchema</code>), have an <i>atomic</i> <a class="propref" href="#variety">{variety}</a> with an empty
<a class="propref" href="#facets">{facets}</a> and the <a class="termref" href="#key-simpleUrType"><span class="arrow">·</span>simple ur-type definition<span class="arrow">·</span></a> as
their <a class="termref" href="#st-base_type_definition"><span class="arrow">·</span>base type definition<span class="arrow">·</span></a> and themselves as <a class="propref" href="#st-primitive_type_definition">{primitive type definition}</a>.</p><p>Similarly, simple type definitions for all the built-in derived
datatypes (see the <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#built-in-derived">Derived
Datatypes</a> section of <a href="#ref-xsp2">[XML Schemas: Datatypes]</a>) are present by definition in every schema, with
properties as specified in <a href="#ref-xsp2">[XML Schemas: Datatypes]</a> and as represented in XML in
<a href="#normative-schemaSchema">Schema for Schemas (normative) (§A)</a>.</p></div></div><div class="div2">
<h3 class="withToc"><span class="nav"><a class="nav" href="#Simple_Type_Definitions"><img src="previous.jpg" alt="previous sub-section"/></a> </span><a id="Schemas" name="Schemas"/>3.15 Schemas as a Whole</h3><div class="localToc">        3.15.1 <a href="#Schema_details">The Schema Itself</a><br/>
        3.15.2 <a href="#declare-schema">XML Representations of Schemas</a><br/>
        3.15.3 <a href="#d0e16860">Constraints on XML Representations of Schemas</a><br/>
        3.15.4 <a href="#d0e17196">Validation Rules for Schemas as a Whole</a><br/>
        3.15.5 <a href="#d0e17275">Schema Information Set Contributions</a><br/>
        3.15.6 <a href="#coss-schema">Constraints on Schemas as a Whole</a><br/>
</div><p>A schema consists of a set of schema components.</p><div class="exampleOuter"><div class="exampleHeader">Example</div><div class="exampleInner"><pre><xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.example.com/example">
. . .
</xs:schema></pre></div><div class="exampleWrapper">The XML representation of the skeleton of a schema.</div></div><div class="div3">
<h4><a id="Schema_details" name="Schema_details"/>3.15.1 The Schema Itself</h4><p>At the abstract level, the schema itself is just a container for its components.</p><div class="schemaComp"><div class="compHeader"><span class="schemaComp">Schema Component</span>: <a href="#key-schema">Schema</a></div><div class="compBody">
<dl class="props">
<dt><a name="type_definitions" id="type_definitions"><span class="propdef">{type definitions}</span></a></dt><dd>A set of
named simple and complex type definitions.</dd>
<dt><a name="attribute_declarations" id="attribute_declarations"><span class="propdef">{attribute declarations}</span></a></dt><dd>A set of
named (top-level) attribute declarations.</dd>
<dt><a name="element_declarations" id="element_declarations"><span class="propdef">{element declarations}</span></a></dt><dd>A set of
named (top-level) element declarations.</dd>
<dt><a name="attribute_group_definitions" id="attribute_group_definitions"><span class="propdef">{attribute group definitions}</span></a></dt><dd>A set of named
attribute group definitions.</dd>
<dt><a name="model_group_definitions" id="model_group_definitions"><span class="propdef">{model group definitions}</span></a></dt><dd>A set of named
model group definitions.</dd>
<dt><a name="notation_declarations" id="notation_declarations"><span class="propdef">{notation declarations}</span></a></dt><dd>A set of
notation declarations.</dd>
<dt><a name="annotations" id="annotations"><span class="propdef">{annotations}</span></a></dt><dd>A set of annotations.</dd>
</dl>
</div></div></div><div class="div3">
<h4><a id="declare-schema" name="declare-schema"/>3.15.2 XML Representations of Schemas</h4><p>A schema is represented in XML by one or more <a class="termref" href="#key-schemaDoc"><span class="arrow">·</span>schema documents<span class="arrow">·</span></a>, that is, one or more <a class="eltref" href="#element-schema"><schema></a> element information items. A <a class="termref" href="#key-schemaDoc"><span class="arrow">·</span>schema document<span class="arrow">·</span></a> contains representations for a collection of schema components, e.g. type definitions and element declarations, which have a common <span class="anonRef">{target namespace}</span>. A <a class="termref" href="#key-schemaDoc"><span class="arrow">·</span>schema document<span class="arrow">·</span></a> which has one or more <a class="eltref" href="#element-import"><import></a> element information items corresponds to a schema with components with more than one <span class="anonRef">{target namespace}</span>, see <a href="#src-import">Import Constraints and Semantics (§4.2.3)</a>.</p><div class="reprdef"><div class="reprHeader"><span class="reprdef">XML Representation Summary</span>: <code>schema</code> Element Information Item</div><div class="reprBody">
<p class="element-syntax-1"><a name="element-schema" id="element-schema"><schema</a><br/>  attributeFormDefault = (<var>qualified</var> | <var>unqualified</var>) : unqualified<br/>  blockDefault =
(<var>#all</var> | List of (<var>extension</var> | <var>restriction</var> | <var>substitution</var>))
 : ''<br/>  elementFormDefault = (<var>qualified</var> | <var>unqualified</var>) : unqualified<br/>  finalDefault =
(<var>#all</var> | List of (<var>extension</var> | <var>restriction</var> | <var>list</var> | <var>union</var>))
 : ''<br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  targetNamespace = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#anyURI">anyURI</a><br/>  version = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#token">token</a><br/>  xml:lang = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#language">language</a><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>((<a class="eltref" href="#element-include">include</a> | <a class="eltref" href="#element-import">import</a> | <a class="eltref" href="#element-redefine">redefine</a> | <a class="eltref" href="#element-annotation">annotation</a>)*, (((<a class="eltref" href="#element-simpleType">simpleType</a> | <a class="eltref" href="#element-complexType">complexType</a> | <a class="eltref" href="#element-group">group</a> | <a class="eltref" href="#element-attributeGroup">attributeGroup</a>) | <a class="eltref" href="#element-element">element</a> | <a class="eltref" href="#element-attribute">attribute</a> | <a class="eltref" href="#element-notation">notation</a>), <a class="eltref" href="#element-annotation">annotation</a>*)*)<br/></schema></p>
<div class="reprcomp"><table class="reprcomp"><thead><tr><th><a href="#key-schema">Schema</a><strong> Schema Component</strong></th></tr></thead><tbody><tr><td><table cellpadding="3" border="0"><thead><tr><th align="left">Property</th><th align="left">Representation</th></tr></thead><tbody valign="top"><tr valign="top"><td><a class="propref" href="#type_definitions">{type definitions}</a></td><td>The simple and complex type definitions
corresponding to all the <a class="eltref" href="#element-simpleType"><simpleType></a> and <a class="eltref" href="#element-complexType"><complexType></a> element information items in the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if any, plus any included or imported definitions, see <a href="#compound-schema">Assembling a schema for a single target namespace from multiple schema definition documents (§4.2.1)</a> and <a href="#composition-schemaImport">References to schema components across namespaces (§4.2.3)</a>.</td></tr><tr valign="top"><td><a class="propref" href="#attribute_declarations">{attribute declarations}</a></td><td>The (top-level) attribute declarations
corresponding to all the <a class="eltref" href="#element-attribute"><attribute></a> element information items in the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if any, plus any included or imported declarations, see <a href="#compound-schema">Assembling a schema for a single target namespace from multiple schema definition documents (§4.2.1)</a> and <a href="#composition-schemaImport">References to schema components across namespaces (§4.2.3)</a>.</td></tr><tr valign="top"><td><a class="propref" href="#element_declarations">{element declarations}</a></td><td>The (top-level) element declarations
corresponding to all the <a class="eltref" href="#element-element"><element></a> element information items in the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if any, plus any included or imported declarations, see <a href="#compound-schema">Assembling a schema for a single target namespace from multiple schema definition documents (§4.2.1)</a> and <a href="#composition-schemaImport">References to schema components across namespaces (§4.2.3)</a>.</td></tr><tr valign="top"><td><a class="propref" href="#attribute_group_definitions">{attribute group definitions}</a></td><td>The attribute group definitions
corresponding to all the <a class="eltref" href="#element-attributeGroup"><attributeGroup></a> element information items in the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if any, plus any included or imported definitions, see <a href="#compound-schema">Assembling a schema for a single target namespace from multiple schema definition documents (§4.2.1)</a> and <a href="#composition-schemaImport">References to schema components across namespaces (§4.2.3)</a>.</td></tr><tr valign="top"><td><a class="propref" href="#model_group_definitions">{model group definitions}</a></td><td>The model group definitions
corresponding to all the <a class="eltref" href="#element-group"><group></a> element information items in the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if any, plus any included or imported definitions, see <a href="#compound-schema">Assembling a schema for a single target namespace from multiple schema definition documents (§4.2.1)</a> and <a href="#composition-schemaImport">References to schema components across namespaces (§4.2.3)</a>.</td></tr><tr valign="top"><td><a class="propref" href="#notation_declarations">{notation declarations}</a></td><td>The notation declarations
corresponding to all the <a class="eltref" href="#element-notation"><notation></a> element information items in the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if any, plus any included or imported declarations, see <a href="#compound-schema">Assembling a schema for a single target namespace from multiple schema definition documents (§4.2.1)</a> and <a href="#composition-schemaImport">References to schema components across namespaces (§4.2.3)</a>.</td></tr><tr valign="top"><td><a class="propref" href="#annotations">{annotations}</a></td><td>The annotations
corresponding to all the <a class="eltref" href="#element-annotation"><annotation></a> element information items in the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, if any.</td></tr></tbody></table></td></tr></tbody></table></div>
</div></div><p>Note that none of the attribute information items displayed above
correspond directly to properties of schemas. The <code>blockDefault</code>,
<code>finalDefault</code>, <code>attributeFormDefault</code>, <code>elementFormDefault</code>and <code>targetNamespace</code> attributes are appealed to in the sub-sections above, as they provide
global information applicable to many representation/component correspondences. The
other attributes (<code>id</code> and <code>version</code>) are for user
convenience, and this specification defines no semantics for them.</p><p>The definition of the schema abstract data model in <a href="#concepts-data-model">XML Schema Abstract Data Model (§2.2)</a> makes clear that most components have a <span class="anonRef">{target namespace}</span>. Most components corresponding to representations within a given <a class="eltref" href="#element-schema"><schema></a> element information item will have a <span class="anonRef">{target namespace}</span> which corresponds to the <code>targetNamespace</code> attribute. </p><p>Since the empty string is not a legal namespace name, supplying
an empty string for <code>targetNamespace</code> is incoherent, and is <em>not</em> the same
as not specifying it at all. The appropriate form of schema document
corresponding to a <a class="termref" href="#key-schema"><span class="arrow">·</span>schema<span class="arrow">·</span></a> whose components have no
<a class="propref" href="#e-target_namespace">{target namespace}</a> is one which has no
<code>targetNamespace</code> attribute specified at all.</p><div class="note"><b>Note: </b>The XML namespaces Recommendation discusses only instance document syntax for
elements and attributes; it therefore provides no direct framework for managing
the names of type definitions, attribute group definitions, and so on.
Nevertheless, the specification applies the target namespace facility uniformly to all
schema components, i.e. not only declarations but also definitions have a <span class="anonRef">{target namespace}</span>.</div><p>Although the example schema at the beginning of this section might be a complete XML document, <a class="eltref" href="#element-schema"><schema></a>
need not be the document element, but can appear within other documents.
Indeed there is no requirement that a schema correspond to a (text) document
at all: it could correspond to an element information item constructed 'by
hand', for instance via a DOM-conformant API.</p><p>Aside from <a class="eltref" href="#element-include"><include></a> and <a class="eltref" href="#element-import"><import></a>, which do not correspond directly to any schema component at all, each of the element information
items which may appear in the content of <a class="eltref" href="#element-schema"><schema></a> corresponds to
a schema component, and all except <a class="eltref" href="#element-annotation"><annotation></a> are named. The
sections below
present each such item in turn, setting out the
components to which it may correspond.</p><div class="div4">
<h5><a id="refSchemaConstructs" name="refSchemaConstructs"/>3.15.2.1 References to Schema Components</h5><p>Reference to
schema components from a schema document is managed in a uniform way,
whether the component corresponds to an element information item from the same schema document or is imported
(<a href="#composition-schemaImport">References to schema components across namespaces (§4.2.3)</a>) from an external schema (which may,
but need not, correspond to an actual schema document). The form
of all such references is a
<a class="termref" href="#gloss-QName"><span class="arrow">·</span>QName<span class="arrow">·</span></a>.</p><p><span class="termdef"><a id="gloss-QName" name="gloss-QName">[Definition:]  </a>A <b>QName</b> is a name
with an optional namespace qualification, as defined in <a href="#ref-xml-namespaces">[XML-Namespaces]</a>. When used in connection with the XML
representation of schema components or references to them, this refers to the
simple type <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#QName">QName</a> as defined in <a href="#ref-xsp2">[XML Schemas: Datatypes]</a></span>.</p><p><span class="termdef"><a id="gloss-NCName" name="gloss-NCName">[Definition:]  </a>An <b>NCName</b> is a name
with no colon, as defined in <a href="#ref-xml-namespaces">[XML-Namespaces]</a>. When used in connection with the XML
representation of schema components in this specification, this refers to the
simple type <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#NCName">NCName</a> as defined in <a href="#ref-xsp2">[XML Schemas: Datatypes]</a></span>.</p><p>In each of the XML
representation expositions in the following sections, an attribute is shown as
having type <code>QName</code> if and only if it is
interpreted as referencing a schema component.</p><div class="exampleOuter"><div class="exampleHeader">Example</div><div class="exampleInner"><pre><xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xhtml="http://www.w3.org/1999/xhtml"
xmlns="http://www.example.com"
targetNamespace="http://www.example.com">
. . .
<xs:element name="elem1" type="Address"/>
<xs:element name="elem2" type="xhtml:blockquote"/>
<xs:attribute name="attr1"
type="xsl:quantity"/>
. . .
</xs:schema>
</pre></div><div class="exampleWrapper">The first of these is most probably a local reference, i.e. a reference
to a type
definition corresponding to a <a class="eltref" href="#element-complexType"><complexType></a> element information item
located elsewhere in the schema document, the other two refer to type
definitions from schemas for other namespaces and assume that their namespaces
have been declared for import. See <a href="#composition-schemaImport">References to schema components across namespaces (§4.2.3)</a> for a discussion of importing.</div></div></div><div class="div4">
<h5><a id="d0e16826" name="d0e16826"/>3.15.2.2 References to Schema Components from Elsewhere</h5><p>The names of schema components such as type definitions and element
declarations are not of type <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a>: they are not
unique within a schema, just within a symbol space. This means that simple
fragment identifiers will not always work to reference schema components from outside
the context of schema documents.</p><p>There is currently no provision in the definition of the interpretation
of fragment identifiers for the <code>text/xml</code> MIME type, which is the
MIME type for schemas, for referencing
schema components as such. However,
<a href="#ref-xpointer">[XPointer]</a> provides a mechanism which maps well onto the
notion of symbol spaces as it is reflected in the XML representation of schema components. A fragment identifier of the form
<code>#xpointer(xs:schema/xs:element[@name="person"])</code> will uniquely identify
the representation of a top-level element declaration with name <code>person</code>, and similar fragment
identifiers can obviously be constructed for the other global symbol spaces.</p><p>Short-form fragment identifiers may also be used in some cases, that is
when a DTD or XML Schema is available for the schema in question, and the
provision of an <code>id</code> attribute for the representations of all primary and secondary schema
components, which <em>is</em> of type
<a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a>, has been exploited.</p><p>It is a matter for applications to specify whether they interpret
document-level references of either of the above varieties as being to the relevant element information item (i.e. without
special recognition of the relation of schema documents to schema components) or as being to the
corresponding schema component.</p></div></div><div class="div3">
<h4><a id="d0e16860" name="d0e16860"/>3.15.3 Constraints on XML Representations of Schemas</h4><div class="constraintnote"><a name="src-qname" id="src-qname"/><b>Schema Representation Constraint: QName Interpretation</b><br/><div class="constraint">Where the type of an attribute information item in a document involved in
<a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> is
identified as
<a class="termref" href="#gloss-QName"><span class="arrow">·</span>QName<span class="arrow">·</span></a>, its <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> is composed of a
<span class="termdef"><a id="q-local" name="q-local">[Definition:]  </a><b>local name</b></span> and a <span class="termdef"><a id="q-uri" name="q-uri">[Definition:]  </a><b>namespace name</b></span>. Its <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> is determined based on its <a class="termref" href="#key-nv"><span class="arrow">·</span>normalized value<span class="arrow">·</span></a> and
the containing element information item's <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[in-scope
namespaces]</a> following <a href="#ref-xml-namespaces">[XML-Namespaces]</a>:<p/>The appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">1 <b>If </b>its <a class="termref" href="#key-nv"><span class="arrow">·</span>normalized value<span class="arrow">·</span></a> is prefixed, <b>then </b>
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1.1 There must be a namespace in the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[in-scope
namespaces]</a> whose <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.namespace">[prefix]</a> matches the prefix.</div><div class="clnumber">1.2 its <a class="termref" href="#q-uri"><span class="arrow">·</span>namespace name<span class="arrow">·</span></a> is the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.namespace">[namespace
name]</a> of that namespace.</div><div class="clnumber">1.3 Its <a class="termref" href="#q-local"><span class="arrow">·</span>local name<span class="arrow">·</span></a> is the portion of
its <a class="termref" href="#key-nv"><span class="arrow">·</span>normalized value<span class="arrow">·</span></a> after the colon (<code>':'</code>).</div></div>
</div><div class="clnumber">2 <b>otherwise </b>(its <a class="termref" href="#key-nv"><span class="arrow">·</span>normalized value<span class="arrow">·</span></a> is unprefixed) <b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.1 its <a class="termref" href="#q-local"><span class="arrow">·</span>local name<span class="arrow">·</span></a> is its <a class="termref" href="#key-nv"><span class="arrow">·</span>normalized value<span class="arrow">·</span></a>.</div><div class="clnumber">2.2 The appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">2.2.1 <b>If </b>there is a namespace in the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[in-scope
namespaces]</a> whose <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.namespace">[prefix]</a> has no value, <b>then </b>its <a class="termref" href="#q-uri"><span class="arrow">·</span>namespace name<span class="arrow">·</span></a> is the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.namespace">[namespace
name]</a> of that namespace.</div><div class="clnumber">2.2.2 <b>otherwise </b>its <a class="termref" href="#q-uri"><span class="arrow">·</span>namespace name<span class="arrow">·</span></a> is <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</div></div></div></div></div></div><p/>In the absence of the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[in-scope namespaces]</a> property in the infoset for the schema document in question, processors must reconstruct equivalent information as necessary, using the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[ namespace attributes]</a> of the containing element information item and its ancestors.</div></div><p><span class="termdef"><a id="key-resolve" name="key-resolve">[Definition:]  </a>Whenever the word <b>resolve</b> in any form is used in this
chapter in connection with a <a class="termref" href="#gloss-QName"><span class="arrow">·</span>QName<span class="arrow">·</span></a> in a
schema document, the
following definition <a href="#src-resolve">QName resolution (Schema Document) (§3.15.3)</a> should be understood</span>:</p><div class="constraintnote"><a name="src-resolve" id="src-resolve"/><b>Schema Representation Constraint: QName resolution (Schema Document)</b><br/><div class="constraint">For a <a class="termref" href="#gloss-QName"><span class="arrow">·</span>QName<span class="arrow">·</span></a>
to resolve to a schema component of a specified kind
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 That component is a member of the value of the appropriate
property of the schema which corresponds to the schema
document within which the <a class="termref" href="#gloss-QName"><span class="arrow">·</span>QName<span class="arrow">·</span></a>
appears, that is
the appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">1.1 <b>If </b>the kind specified is simple or complex type definition, <b>then </b>the property is the <a class="propref" href="#type_definitions">{type definitions}</a>.</div><div class="clnumber">1.2 <b>If </b>the kind specified is attribute declaration, <b>then </b>the property is the <a class="propref" href="#attribute_declarations">{attribute declarations}</a>.</div><div class="clnumber">1.3 <b>If </b>the kind specified is element declaration, <b>then </b>the property is the <a class="propref" href="#element_declarations">{element declarations}</a>.</div><div class="clnumber">1.4 <b>If </b>the kind specified
is attribute group, <b>then </b>the property is the <a class="propref" href="#attribute_group_definitions">{attribute group definitions}</a>.</div><div class="clnumber">1.5 <b>If </b>the kind specified is
model group, <b>then </b>the property is the <a class="propref" href="#model_group_definitions">{model group definitions}</a>.</div><div class="clnumber">1.6 <b>If </b>the kind specified is notation declaration, <b>then </b>the property is the <a class="propref" href="#notation_declarations">{notation declarations}</a>.</div></div>
</div><div class="clnumber">2 The
component's <span class="anonRef">{name}</span> matches the <a class="termref" href="#q-local"><span class="arrow">·</span>local
name<span class="arrow">·</span></a> of the <a class="termref" href="#gloss-QName"><span class="arrow">·</span>QName<span class="arrow">·</span></a>;</div><div class="clnumber">3 The component's <span class="anonRef">{target namespace}</span> is identical to the <a class="termref" href="#q-uri"><span class="arrow">·</span>namespace name<span class="arrow">·</span></a> of the <a class="termref" href="#gloss-QName"><span class="arrow">·</span>QName<span class="arrow">·</span></a>;</div><div class="clnumber">4 The appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">4.1 <b>If </b>the <a class="termref" href="#q-uri"><span class="arrow">·</span>namespace name<span class="arrow">·</span></a> of the <a class="termref" href="#gloss-QName"><span class="arrow">·</span>QName<span class="arrow">·</span></a> is <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>, <b>then </b>
<b>one</b> of the following must be true:<div class="constraintlist"><div class="clnumber">4.1.1 The <a class="eltref" href="#element-schema"><schema></a> element information item of the schema document containing the <a class="termref" href="#gloss-QName"><span class="arrow">·</span>QName<span class="arrow">·</span></a> has no <code>targetNamespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>.</div><div class="clnumber">4.1.2 The <a class="eltref" href="#element-schema"><schema></a> element information item of the that schema document contains an <a class="eltref" href="#element-import"><import></a> element
information item with no <code>namespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>.</div></div>
</div><div class="clnumber">4.2 <b>otherwise </b>the <a class="termref" href="#q-uri"><span class="arrow">·</span>namespace name<span class="arrow">·</span></a> of the <a class="termref" href="#gloss-QName"><span class="arrow">·</span>QName<span class="arrow">·</span></a> is
the same as
<b>one</b> of the following:<div class="constraintlist"><div class="clnumber">4.2.1 The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>targetNamespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of
the <a class="eltref" href="#element-schema"><schema></a> element information item of the schema document containing the <a class="termref" href="#gloss-QName"><span class="arrow">·</span>QName<span class="arrow">·</span></a>.</div><div class="clnumber">4.2.2 The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>namespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of some
<a class="eltref" href="#element-import"><import></a> element information item contained in the <a class="eltref" href="#element-schema"><schema></a> element information item of that schema document.</div></div>.</div></div></div></div>
</div></div></div><div class="div3">
<h4><a id="d0e17196" name="d0e17196"/>3.15.4 Validation Rules for Schemas as a Whole</h4><p>As the discussion above at <a href="#components">Schema Component Details (§3)</a> makes clear, at the level of schema components and <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a>, reference to components by name is normally not involved. In a
few cases, however, qualified names appearing in information items being
<a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a> must be resolved to schema components by such lookup. The following
constraint is appealed to in these cases.</p><div class="constraintnote"><a name="cvc-resolve-instance" id="cvc-resolve-instance"/><b>Validation Rule: QName resolution (Instance)</b><br/><div class="constraint">A pair of a local name and a namespace name (or <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>)
resolve to a schema component of a specified kind in the context of <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> by appeal to the appropriate
property of the schema being used for the <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a>. Each such property indexes components by name. The property to use is determined by the kind of component specified, that is,
the appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">1 <b>If </b>the kind specified is simple or complex type definition, <b>then </b>the property is the <a class="propref" href="#type_definitions">{type definitions}</a>.</div><div class="clnumber">2 <b>If </b>the kind specified is attribute declaration, <b>then </b>the property is the <a class="propref" href="#attribute_declarations">{attribute declarations}</a>.</div><div class="clnumber">3 <b>If </b>the kind specified is element declaration, <b>then </b>the property is the <a class="propref" href="#element_declarations">{element declarations}</a>.</div><div class="clnumber">4 <b>If </b>the kind specified
is attribute group, <b>then </b>the property is the <a class="propref" href="#attribute_group_definitions">{attribute group definitions}</a>.</div><div class="clnumber">5 <b>If </b>the kind specified is
model group, <b>then </b>the property is the <a class="propref" href="#model_group_definitions">{model group definitions}</a>.</div><div class="clnumber">6 <b>If </b>the kind specified is notation declaration, <b>then </b>the property is the <a class="propref" href="#notation_declarations">{notation declarations}</a>.</div></div>
The component resolved to is the entry in the table whose <span class="anonRef">{name}</span> matches the local name of the pair and whose <span class="anonRef">{target namespace}</span> is identical to the namespace name of the pair.
</div></div></div><div class="div3">
<h4><a id="d0e17275" name="d0e17275"/>3.15.5 Schema Information Set Contributions</h4><div class="constraintnote"><a name="sic-schema" id="sic-schema"/><b>Schema Information Set Contribution: Schema Information</b><br/><div class="constraint">Schema components provide a wealth of information about the basis of
<a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a>, which may well be of relevance to
subsequent processing. Reflecting component structure into a form suitable for
inclusion in the <a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a> is the way this specification provides for making this
information available.<p/>Accordingly, <span class="termdef"><a id="key-iso" name="key-iso">[Definition:]  </a> by an <b>item isomorphic</b> to a component is meant an information item whose type is equivalent to the component's, with one property per property of the component, with the same name, and value either the same atomic value, or an information item corresponding in the same way to its component value, recursively, as necessary</span>.<p/>Processors must add a property in the <a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a>
to the element information item at which <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> began, as follows:<div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> element information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="e-schema_information" id="e-schema_information"><span class="propdef">[schema information]</span></a></dt><dd>A set of <b>namespace schema information</b> information items, one for each namespace name which appears as the
<span class="anonRef">{target namespace}</span> of any schema component in the schema used for that
assessment, and one for <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> if any schema
component in the schema had no <span class="anonRef">{target namespace}</span>. Each <b>namespace schema information</b> information item has the
following properties and values:
<div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> namespace schema information information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="nsi-schema_namespace" id="nsi-schema_namespace"><span class="propdef">[schema namespace]</span></a></dt><dd>A namespace
name or <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</dd>
<dt><a name="nsi-schema_components" id="nsi-schema_components"><span class="propdef">[schema components]</span></a></dt><dd>A (possibly
empty) set of schema component information items, each one an <a class="termref" href="#key-iso"><span class="arrow">·</span>item isomorphic<span class="arrow">·</span></a> to a component whose <span class="anonRef">{target
namespace}</span> is the sibling <a class="propref" href="#nsi-schema_namespace">[schema namespace]</a>
property above, drawn from the schema used for <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a>.</dd>
<dt><a name="nsi-schema_documents" id="nsi-schema_documents"><span class="propdef">[schema documents]</span></a></dt><dd>A
(possibly empty) set of <b>schema document</b> information items, with
properties and values as follows, for each schema document which
contributed components to the schema, and whose
<code>targetNamespace</code> matches the sibling <a class="propref" href="#nsi-schema_namespace">[schema namespace]</a> property above (or whose
<code>targetNamespace</code> was <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>
but that contributed components to that namespace by being <a class="eltref" href="#element-include"><include></a>d
by a schema document with that <code>targetNamespace</code> as per <a href="#compound-schema">Assembling a schema for a single target namespace from multiple schema definition documents (§4.2.1)</a>):
<div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> schema document information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="sd-document_location" id="sd-document_location"><span class="propdef">[document location]</span></a></dt><dd>Either a URI reference, if available, otherwise
<a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>
</dd>
<dt><a name="sd-document" id="sd-document"><span class="propdef">[document]</span></a></dt><dd>A document
information item, if available, otherwise <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>.</dd>
</dl></div></div>
</dd>
</dl></div></div>
</dd>
</dl></div></div>The <a class="propref" href="#nsi-schema_components">{schema components}</a> property is provided for
processors which wish to provide a single access point to the
components of the schema which was used during <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a>. Lightweight processors are free to leave it empty, but if it <em>is</em> provided, it must contain at a minimum all the top-level (i.e. named) components which actually figured in the <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a>, either directly or (because an anonymous component which figured is contained within) indirectly.</div></div><div class="constraintnote"><a name="sic-id" id="sic-id"/><b>Schema Information Set Contribution: ID/IDREF Table</b><br/><div class="constraint">In the <a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a> a set of <b>ID/IDREF binding</b> information items is associated
with the <a class="termref" href="#key-vr"><span class="arrow">·</span>validation root<span class="arrow">·</span></a> element information
item:<div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> element information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="e-ii_table" id="e-ii_table"><span class="propdef">[ID/IDREF table]</span></a></dt><dd>A (possibly empty) set of
<b>ID/IDREF binding</b> information items, as specified below.</dd>
</dl></div></div><span class="termdef"><a id="key-eas" name="key-eas">[Definition:]  </a>Let the
<b>eligible item set</b> be the set of consisting of every attribute or element
information item</span> for which
<b>all</b> of the following are true<div class="constraintlist"><div class="clnumber">1 its <span class="anonRef">[validation context]</span> is the
<a class="termref" href="#key-vr"><span class="arrow">·</span>validation root<span class="arrow">·</span></a>;</div><div class="clnumber">2 it was successfully <a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a> with respect to an attribute
declaration as per <a href="#cvc-attribute">Attribute Locally Valid (§3.2.4)</a> or element declaration as per
<a href="#cvc-elt">Element Locally Valid (Element) (§3.3.4)</a> (as appropriate) whose attribute <a class="propref" href="#a-simple_type_definition">{type definition}</a> or element <a class="propref" href="#type_definition">{type definition}</a> (respectively) is the
built-in <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a>, <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#IDREF">IDREF</a> or <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#IDREFS">IDREFS</a> simple type definition or a type derived from one of them.</div></div><p/>Then there is one <b>ID/IDREF binding</b> in the <a class="propref" href="#e-ii_table">[ID/IDREF table]</a>
for every distinct string which is<b>one</b> of the following:<div class="constraintlist"><div class="clnumber">1 the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of a member of the <a class="termref" href="#key-eas"><span class="arrow">·</span>eligible
item set<span class="arrow">·</span></a> whose type definition is or is derived from <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a> or <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#IDREF">IDREF</a>;</div><div class="clnumber">2 one of the items in the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of a member of the <a class="termref" href="#key-eas"><span class="arrow">·</span>eligible
item set<span class="arrow">·</span></a> whose type definition is or is derived from <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#IDREFS">IDREFS</a>.</div></div>Each <b>ID/IDREF binding</b> has properties as follows:<div class="psviDef"><div class="psviHeader"><span class="psviDef">PSVI Contributions
for</span> ID/IDREF binding information items
</div><div class="psviBody"><dl class="psvi">
<dt><a name="iib-id" id="iib-id"><span class="propdef">[id]</span></a></dt><dd>The string identified above.</dd>
<dt><a name="iib-binding" id="iib-binding"><span class="propdef">[binding]</span></a></dt><dd>A set consisting of every element information item for which
<b>all</b> of the following are true<div class="constraintlist"><div class="clnumber">1 its <a class="propref" href="#e-validation_context">[validation context]</a> is the
<a class="termref" href="#key-vr"><span class="arrow">·</span>validation root<span class="arrow">·</span></a>;</div><div class="clnumber">2 it has an attribute information item in
its <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> or an element information item in its <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> which was <a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a> by the
built-in <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a> simple type definition or a type derived from it whose
<span class="anonRef">[schema normalized value]</span> is the <a class="propref" href="#iib-id">[id]</a> of
this <b>ID/IDREF binding</b>.</div></div>
</dd>
</dl></div></div>The net effect of the above is to have one entry for every string used as an
id, whether by declaration or by reference, associated with those elements, if
any, which actually purport to have that id. See <a href="#cvc-id">Validation Root Valid (ID/IDREF) (§3.3.4)</a> above
for the validation rule which actually checks for errors here.<div class="note"><b>Note: </b>The <b>ID/IDREF binding</b>
information item, unlike most other aspects of this
specification, is essentially an internal bookkeeping mechanism. It is introduced to
support the definition of <a href="#cvc-id">Validation Root Valid (ID/IDREF) (§3.3.4)</a> above.
Accordingly, conformant processors may, but are <em>not</em> required to,
expose it in the <a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a>.
In other words, the above constraint may be read as saying <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> proceeds <em>as if</em> such an infoset item existed.</div></div></div></div><div class="div3">
<h4><a id="coss-schema" name="coss-schema"/>3.15.6 Constraints on Schemas as a Whole</h4><p>All schemas (see <a href="#Schemas">Schemas as a Whole (§3.15)</a>) must satisfy the following constraint.</p><div class="constraintnote"><a name="sch-props-correct" id="sch-props-correct"/><b>Schema Component Constraint: Schema Properties Correct</b><br/><div class="constraint"><b>All</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 The values of the properties of a schema must be as described in
the property tableau in
<a href="#Schema_details">The Schema Itself (§3.15.1)</a>, modulo the impact of <a href="#conformance-missing">Missing Sub-components (§5.3)</a>;</div><div class="clnumber">2<a name="c-nmd" id="c-nmd"> </a>Each of the <a class="propref" href="#type_definitions">{type definitions}</a>, <a class="propref" href="#element_declarations">{element declarations}</a>, <a class="propref" href="#attribute_group_definitions">{attribute group definitions}</a>, <a class="propref" href="#model_group_definitions">{model group definitions}</a> and <a class="propref" href="#notation_declarations">{notation declarations}</a> must not contain two or more schema components with the same <span class="anonRef">{name}</span> and <span class="anonRef">{target
namespace}</span>.</div></div></div></div></div></div></div><div class="div1">
<h2><a id="composition" name="composition"/>4 Schemas and Namespaces: Access and Composition</h2><p>This chapter defines the mechanisms by which this specification establishes the necessary
precondition for <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a>, namely access to
one or more schemas. This chapter also sets out in detail the relationship
between schemas and namespaces, as well as mechanisms for
modularization of schemas, including provision for incorporating definitions
and declarations from one schema in another, possibly with modifications.</p><p><a href="#concepts-conformance">Conformance (§2.4)</a> describes three levels of conformance for schema
processors, and <a href="#conformance">Schemas and Schema-validity Assessment (§5)</a> provides a formal definition of
<a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a>. This section sets out
in detail the 3-layer architecture implied by the three conformance levels.
The layers
are: </p><ol class="enumar"><li>The <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> core, relating schema components and instance
information items; </li><li>Schema representation: the connections between XML
representations and schema components, including the
relationships between namespaces and schema components; </li><li>XML Schema web-interoperability guidelines: instance->schema and
schema->schema connections for the WWW. </li></ol><p>Layer 1 specifies the manner in which a schema composed of schema components
can be applied to in the <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> of an instance element information item. Layer 2 specifies the use of <a class="eltref" href="#element-schema"><schema></a>
elements in XML documents as the standard XML representation for
schema information in a broad range of computer systems and execution
environments. To support interoperation over the World Wide Web in particular,
layer 3 provides a set of conventions for schema reference on the
Web. Additional details on each of the three layers is provided in the sections below.</p><div class="div2">
<h3><span class="nav"> <a class="nav" href="#layer2"><img src="next.jpg" alt="next sub-section"/></a></span><a id="layer1" name="layer1"/>4.1 Layer 1: Summary of the Schema-validity Assessment Core</h3><p>The fundamental purpose of the <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> core is to define <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> for a single
element information item and its descendants with respect to a
complex type
definition. All processors are required to implement this core predicate in a
manner which conforms exactly to this specification. </p><p><a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> is defined with reference to an <a class="termref" href="#key-schema"><span class="arrow">·</span>XML Schema<span class="arrow">·</span></a> (note <em>not</em> a
<a class="termref" href="#key-schemaDoc"><span class="arrow">·</span>schema document<span class="arrow">·</span></a>) which consists of (at a minimum) the set of schema
components (definitions and declarations) required for that
<a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a>. This is not a circular definition, but rather a
<em>post facto</em> observation: no element information item can
be fully assessed unless all the components required by any aspect of
its (potentially recursive) <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> are present in the schema.</p><p>As specified above, each schema component is associated directly or
indirectly with a target namespace, or explicitly with no namespace. In the case of multi-namespace documents,
components for more than one target namespace will co-exist in a schema.</p><p>Processors have the option to assemble (and perhaps to optimize or
pre-compile) the entire schema prior to the start of an <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> episode, or to
gather the schema lazily as individual components are required. In all
cases it is required that:</p><ul><li>The processor succeed in locating the <a class="termref" href="#key-component"><span class="arrow">·</span>schema components<span class="arrow">·</span></a>
transitively required to complete an <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> (note that components derived
from <a class="termref" href="#key-schemaDoc"><span class="arrow">·</span>schema documents<span class="arrow">·</span></a> can be integrated
with components obtained through other means);</li><li>no definition or declaration changes once it has been established;</li><li>if the processor chooses to acquire declarations and definitions
dynamically, that there be no side effects of such dynamic acquisition that
would cause the results of <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> to differ from that which would have
been obtained from the same schema components acquired in bulk.</li></ul><div class="note"><b>Note: </b> the <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> core is defined in terms of schema components at the
abstract level, and no mention is made of the schema definition
syntax (i.e. <a class="eltref" href="#element-schema"><schema></a>). Although many processors will acquire
schemas in this format, others may operate on compiled representations, on a
programmatic representation as exposed in some programming language, etc.
</div><p>The obligation of a schema-aware processor as far as the <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a>
core is concerned is to implement one or more of the options for <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> given below in <a href="#validation_outcome">Assessing Schema-Validity (§5.2)</a>. Neither the
choice of element information item for that <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a>, nor which of the
means of initiating <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> are used, is within the scope of this specification.</p><p>Although <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> is defined recursively, it is also intended to be
implementable in streaming
processors. Such processors may choose to incrementally assemble the schema during
processing in response, for example, to encountering new namespaces.
The implication of the
invariants expressed above is that such incremental assembly must
result in an <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a>
outcome that is the
<em>same</em> as would
be given if <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> was undertaken again
with the final, fully assembled schema. </p></div><div class="div2">
<h3 class="withToc"><span class="nav"><a class="nav" href="#layer1"><img src="previous.jpg" alt="previous sub-section"/></a> <a class="nav" href="#composition-instances"><img src="next.jpg" alt="next sub-section"/></a></span><a id="layer2" name="layer2"/>4.2 Layer 2: Schema Documents, Namespaces and Composition</h3><div class="localToc">        4.2.1 <a href="#compound-schema">Assembling a schema for a single target namespace from multiple schema definition documents</a><br/>
        4.2.2 <a href="#modify-schema">Including modified component definitions</a><br/>
        4.2.3 <a href="#composition-schemaImport">References to schema components across namespaces</a><br/>
</div><p>The sub-sections of <a href="#components">Schema Component Details (§3)</a> define an
XML representation for type definitions and element declarations and so on,
specifying their target namespace and collecting them into schema documents.
The two following sections relate to assembling a complete schema for <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> from multiple sources. They should <em>not</em> be understood as a form of text substitution, but rather as providing mechanisms for distributed definition of schema components, with appropriate schema-specific semantics.</p><div class="note"><b>Note: </b> The core <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> architecture requires that a complete schema with
all the necessary declarations and definitions be
available. This may involve resolving both
instance->schema and schema->schema references. As observed earlier in <a href="#concepts-conformance">Conformance (§2.4)</a>, the precise mechanisms for resolving such references are expected to evolve over time.
In support of such evolution, this specification observes the design principle that references from
one schema document to a schema use mechanisms that directly parallel those used to
reference a schema from an instance document.</div><div class="note"><b>Note: </b>In the sections below, "schemaLocation" really belongs at layer 3.
For convenience, it is documented with the layer 2 mechanisms of import and
include, with which it is closely associated.</div><div class="div3">
<h4><a id="compound-schema" name="compound-schema"/>4.2.1 Assembling a schema for a single target namespace from multiple schema definition documents</h4><p>Schema components for a single target namespace can be assembled from
several <a class="termref" href="#key-schemaDoc"><span class="arrow">·</span>schema documents<span class="arrow">·</span></a>, that is several <a class="eltref" href="#element-schema"><schema></a> element
information items: </p><div class="reprdef"><div class="reprHeader"><span class="reprdef">XML Representation Summary</span>: <code>include</code> Element Information Item</div><div class="reprBody">
<p class="element-syntax-1"><a name="element-include" id="element-include"><include</a><br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  <b>schemaLocation</b> = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#anyURI">anyURI</a><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?)<br/></include></p>
</div></div><p>A <a class="eltref" href="#element-schema"><schema></a> information item may contain any number of <a class="eltref" href="#element-include"><include></a> elements. Their <code>schemaLocation</code> attributes, consisting of a URI reference, identify other <a class="termref" href="#key-schemaDoc"><span class="arrow">·</span>schema documents<span class="arrow">·</span></a>, that is <a class="eltref" href="#element-schema"><schema></a> information items.
</p><p>The <a class="termref" href="#key-schema"><span class="arrow">·</span>XML Schema<span class="arrow">·</span></a> corresponding
to <a class="eltref" href="#element-schema"><schema></a> contains not only the components corresponding to its definition and declaration <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, but also
all the components of all the <a class="termref" href="#key-schema"><span class="arrow">·</span>XML Schemas<span class="arrow">·</span></a> corresponding to any <a class="eltref" href="#element-include"><include></a>d schema documents.
Such included schema documents must either (a) have the same
<code>targetNamespace</code> as the <a class="eltref" href="#element-include"><include></a>ing schema document, or
(b) no <code>targetNamespace</code> at all, in which case the <a class="eltref" href="#element-include"><include></a>d schema document is converted to the <a class="eltref" href="#element-include"><include></a>ing schema document's <code>targetNamespace</code>.</p><div class="constraintnote"><a name="src-include" id="src-include"/><b>Schema Representation Constraint: Inclusion Constraints and Semantics</b><br/><div class="constraint">In addition to the conditions imposed on <a class="eltref" href="#element-include"><include></a> element
information items by the schema for schemas,
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1<a name="c-ins" id="c-ins"> </a>If the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>schemaLocation</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>
successfully resolves
<b>one</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1.1<a name="c-vxd" id="c-vxd"> </a>It resolves to (a fragment of) a resource which is an XML
document (of type
<code>application/xml</code> or <code>text/xml</code> with an XML declaration
for preference, but this is not required), which in turn corresponds to a <a class="eltref" href="#element-schema"><schema></a>
element information item in a well-formed information set, which in turn
corresponds to a valid schema.</div><div class="clnumber">1.2 It resolves to a <a class="eltref" href="#element-schema"><schema></a>
element information item in a well-formed information set, which in turn
corresponds to a valid schema.</div></div>
In either case call the <a class="eltref" href="#element-include"><include></a>d <a class="eltref" href="#element-schema"><schema></a> item <b>SII</b>, the valid
schema <b>I</b> and the <a class="eltref" href="#element-include"><include></a>ing item's parent <a class="eltref" href="#element-schema"><schema></a> item <b>SII’</b>.</div><div class="clnumber">2 <b>One</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.1<a name="c-normi" id="c-normi"> </a><b>SII</b> has a <code>targetNamespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, and its <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> is identical to the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>targetNamespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of <b>SII’</b> (which must have such an <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>).</div><div class="clnumber">2.2<a name="c-normi2" id="c-normi2"> </a>Neither <b>SII</b> nor <b>SII’</b> have a <code>targetNamespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>.</div><div class="clnumber">2.3<a name="c-chami" id="c-chami"> </a><b>SII</b> has no <code>targetNamespace</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> (but <b>SII’</b> does).</div></div></div><div class="clnumber">3 The appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">3.1 <b>If </b>clause <a href="#c-normi">2.1</a> or clause <a href="#c-normi2">2.2</a> above is satisfied, <b>then </b>the schema corresponding to <b>SII’</b> must include not only definitions or
declarations corresponding to the appropriate members of its own <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, but also components identical to all the <a class="termref" href="#key-component"><span class="arrow">·</span>schema components<span class="arrow">·</span></a> of <b>I</b>.</div><div class="clnumber">3.2<a name="c-docham" id="c-docham"> </a><b>If </b>clause <a href="#c-chami">2.3</a> above is satisfied, <b>then </b>the schema corresponding to the
<a class="eltref" href="#element-include"><include></a>d
item's parent <a class="eltref" href="#element-schema"><schema></a> must include not only definitions or
declarations corresponding to the appropriate members of its own <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>,
but also components identical to all the <a class="termref" href="#key-component"><span class="arrow">·</span>schema
components<span class="arrow">·</span></a> of <b>I</b>, except that anywhere the <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> target
namespace name would have appeared, the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the
<code>targetNamespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of <b>SII’</b> is used. In
particular, it replaces <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> in the following places:
<div class="constraintlist"><div class="clnumber">3.2.1 The <span class="anonRef">{target namespace}</span> of named schema
components, both at the top level and (in the case of nested type
definitions and nested attribute and
element declarations whose <code>code</code> was <i>qualified</i>) nested within definitions;</div><div class="clnumber">3.2.2 The <a class="propref" href="#namespace_constraint">{namespace constraint}</a> of a wildcard, whether negated or not;</div></div>
</div></div></div></div>
<p/>It is <em>not</em> an error for the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the
<code>schemaLocation</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> to fail to resolve it all, in which case no
corresponding inclusion is performed. It
<em>is</em> an error for it to resolve but the rest of clause 1 above to
fail to be satisfied. Failure to resolve may well cause less than complete
<a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> outcomes, of course.<p/>As discussed in <a href="#conformance-missing">Missing Sub-components (§5.3)</a>, <a class="termref" href="#gloss-QName"><span class="arrow">·</span>QName<span class="arrow">·</span></a>s in XML representations may fail to
<a class="termref" href="#key-resolve"><span class="arrow">·</span>resolve<span class="arrow">·</span></a>, rendering components incomplete
and unusable because of missing subcomponents. During schema construction,
implementations must retain <a class="termref" href="#gloss-QName"><span class="arrow">·</span>QName<span class="arrow">·</span></a> values for such references, in case an appropriately-named component becomes available to discharge the reference by the time it is actually needed. <a class="termref" href="#key-null"><span class="arrow">·</span>Absent<span class="arrow">·</span></a> target <a class="termref" href="#q-uri"><span class="arrow">·</span>namespace name<span class="arrow">·</span></a>s of such as-yet unresolved reference <a class="termref" href="#gloss-QName"><span class="arrow">·</span>QName<span class="arrow">·</span></a>s in <a class="eltref" href="#element-include"><include></a>d components must also be converted if clause <a href="#c-docham">3.2</a> is satisfied.</div></div><div class="note"><b>Note: </b>The above is carefully worded so that multiple <a class="eltref" href="#element-include"><include></a>ing of the same schema document will not constitute a violation of
clause <a href="#c-nmd">2</a> of <a href="#sch-props-correct">Schema Properties Correct (§3.15.6)</a>, but applications are
allowed, indeed encouraged, to avoid <a class="eltref" href="#element-include"><include></a>ing the same schema document more than once to forestall the necessity of establishing identity
component by component.</div></div><div class="div3">
<h4><a id="modify-schema" name="modify-schema"/>4.2.2 Including modified component definitions</h4><p>In order to provide some support for evolution and versioning, it is
possible to incorporate components corresponding to a schema document
<em>with modifications</em>. The modifications have a pervasive impact,
that is, only the redefined components are used, even when referenced from
other incorporated components, whether redefined themselves or not.</p><div class="reprdef"><div class="reprHeader"><span class="reprdef">XML Representation Summary</span>: <code>redefine</code> Element Information Item</div><div class="reprBody">
<p class="element-syntax-1"><a name="element-redefine" id="element-redefine"><redefine</a><br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  <b>schemaLocation</b> = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#anyURI">anyURI</a><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a> | (<a class="eltref" href="#element-simpleType">simpleType</a> | <a class="eltref" href="#element-complexType">complexType</a> | <a class="eltref" href="#element-group">group</a> | <a class="eltref" href="#element-attributeGroup">attributeGroup</a>))*<br/></redefine></p>
</div></div><p>A <a class="eltref" href="#element-schema"><schema></a> information item may contain any number of <a class="eltref" href="#element-redefine"><redefine></a> elements. Their <code>schemaLocation</code> attributes, consisting of a URI reference, identify other <a class="termref" href="#key-schemaDoc"><span class="arrow">·</span>schema documents<span class="arrow">·</span></a>, that is <a class="eltref" href="#element-schema"><schema></a> information items.
</p><p>The <a class="termref" href="#key-schema"><span class="arrow">·</span>XML Schema<span class="arrow">·</span></a> corresponding
to <a class="eltref" href="#element-schema"><schema></a> contains not only the components corresponding to its definition and declaration <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, but also
all the components of all the <a class="termref" href="#key-schema"><span class="arrow">·</span>XML Schemas<span class="arrow">·</span></a> corresponding to any <a class="eltref" href="#element-redefine"><redefine></a>d schema documents.
Such schema documents must either (a) have the same
<code>targetNamespace</code> as the <a class="eltref" href="#element-redefine"><redefine></a>ing schema document, or
(b) no <code>targetNamespace</code> at all, in which case the <a class="eltref" href="#element-redefine"><redefine></a>d schema document is converted to the <a class="eltref" href="#element-redefine"><redefine></a>ing schema document's <code>targetNamespace</code>.</p><p>The definitions within the <a class="eltref" href="#element-redefine"><redefine></a> element itself are
restricted to be redefinitions of components from the <a class="eltref" href="#element-redefine"><redefine></a>d
schema document, <em>in terms of themselves</em>. That is,
</p><ul><li>Type
definitions must use themselves as their base type definition;</li><li>
Attribute
group definitions and model group definitions must be supersets or subsets of their original
definitions, either by including exactly one
reference to themselves or by containing only (possibly restricted) components
which appear in a corresponding way in their <a class="eltref" href="#element-redefine"><redefine></a>d selves.</li></ul><p>Not all the components of the <a class="eltref" href="#element-redefine"><redefine></a>d
schema document need be redefined.</p><p>This mechanism is intended to provide a declarative and modular approach to
schema modification, with functionality no different except in scope from what
would be achieved by wholesale text copying and redefinition by editing. In
particular redefining a type is not guaranteed to be side-effect free: it may
have unexpected impacts on other type definitions which are based
on the redefined one, even to the extent that some such definitions become
ill-formed.</p><div class="note"><b>Note: </b>The pervasive impact of redefinition reinforces the need for
implementations to adopt some form of lazy or 'just-in-time' approach to
component construction, which is also called for in order to avoid
inappropriate dependencies on the order in which definitions and references appear in (collections of) schema documents.</div><div class="exampleOuter"><div class="exampleHeader">Example</div><div class="exampleInner"><pre>v1.xsd:
<xs:complexType name="personName">
<xs:sequence>
<xs:element name="title" minOccurs="0"/>
<xs:element name="forename" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
</xs:complexType>
<xs:element name="addressee" type="personName"/>
v2.xsd:
<xs:redefine schemaLocation="v1.xsd">
<xs:complexType name="personName">
<xs:complexContent>
<xs:extension base="personName">
<xs:sequence>
<xs:element name="generation" minOccurs="0"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:redefine>
<xs:element name="author" type="personName"/>
</pre></div><div class="exampleWrapper">The schema corresponding to <code>v2.xsd</code> has everything specified
by <code>v1.xsd</code>, with the <code>personName</code> type redefined, as
well as everything it specifies itself. According to
this schema, elements constrained
by the <code>personName</code> type may end with a <code>generation</code>
element. This includes not only the <code>author</code> element, but also the
<code>addressee</code> element.</div></div><div class="constraintnote"><a name="src-redefine" id="src-redefine"/><b>Schema Representation Constraint: Redefinition Constraints and Semantics</b><br/><div class="constraint">In addition to the conditions imposed on <a class="eltref" href="#element-redefine"><redefine></a> element
information items by the schema for schemas
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 If there are any element information items among the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>
other than <a class="eltref" href="#element-annotation"><annotation></a> then the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the
<code>schemaLocation</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> must
successfully resolve.</div><div class="clnumber">2 If the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>schemaLocation</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>
successfully resolves
<b>one</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.1 it resolves to (a fragment of) a resource which is an XML document
(see clause <a href="#c-vxd">1.1</a>), which in turn corresponds to a <a class="eltref" href="#element-schema"><schema></a>
element information item in a well-formed information set, which in turn
corresponds to a valid schema.</div><div class="clnumber">2.2 It resolves to a <a class="eltref" href="#element-schema"><schema></a>
element information item in a well-formed information set, which in turn
corresponds to a valid schema.</div></div>
In either case call the <a class="eltref" href="#element-redefine"><redefine></a>d <a class="eltref" href="#element-schema"><schema></a> item <b>SII</b>, the valid
schema <b>I</b> and the <a class="eltref" href="#element-redefine"><redefine></a>ing item's parent <a class="eltref" href="#element-schema"><schema></a> item <b>SII’</b>.</div><div class="clnumber">3 <b>One</b> of the following must be true:<div class="constraintlist"><div class="clnumber">3.1<a name="c-normir" id="c-normir"> </a><b>SII</b> has a <code>targetNamespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, and its <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> is identical to the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>targetNamespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of <b>SII’</b> (which must have such an <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>).</div><div class="clnumber">3.2<a name="c-normi2r" id="c-normi2r"> </a>Neither <b>SII</b> nor <b>SII’</b> have a <code>targetNamespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>.</div><div class="clnumber">3.3<a name="c-chamir" id="c-chamir"> </a><b>SII</b> has no <code>targetNamespace</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> (but <b>SII’</b> does).</div></div></div><div class="clnumber">4 The appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">4.1 <b>If </b>clause <a href="#c-normir">3.1</a> or clause <a href="#c-normi2r">3.2</a> above is satisfied, <b>then </b>the schema corresponding to <b>SII’</b> must include not only definitions or
declarations corresponding to the appropriate members of its own
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, but also components identical to all the <a class="termref" href="#key-component"><span class="arrow">·</span>schema components<span class="arrow">·</span></a> of <b>I</b>, with the
exception of those explicitly redefined (see <a href="#src-expredef">Individual Component Redefinition (§4.2.2)</a> below).</div><div class="clnumber">4.2 <b>If </b>clause <a href="#c-chamir">3.3</a> above is satisfied, <b>then </b>the schema corresponding to <b>SII’</b> must include not only definitions or
declarations corresponding to the appropriate members of its own <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>,
but also components identical to all the <a class="termref" href="#key-component"><span class="arrow">·</span>schema
components<span class="arrow">·</span></a> of <b>I</b>, with the
exception of those explicitly redefined (see <a href="#src-expredef">Individual Component Redefinition (§4.2.2)</a>
below), except that anywhere the <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> target
namespace name would have appeared, the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the
<code>targetNamespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of <b>SII’</b> is
used (see clause <a href="#c-docham">3.2</a> in <a href="#src-include">Inclusion Constraints and Semantics (§4.2.1)</a> for details).</div></div></div><div class="clnumber">5 Within the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, each <a class="eltref" href="#element-simpleType"><simpleType></a> must
have a <a class="eltref" href="#element-restriction"><restriction></a> among its <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> and each <a class="eltref" href="#element-complexType"><complexType></a> must have a <code>restriction</code> or <code>extension</code> among its grand-<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of whose <code>base</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> must be the same as the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of its own <code>name</code> attribute plus target namespace;</div><div class="clnumber">6 Within the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, for each <a class="eltref" href="#element-group"><group></a> the appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">6.1 <b>If </b>it has a <a class="eltref" href="#element-group"><group></a> among its contents at some level the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of whose
<code>ref</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> is the same as the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of its own
<code>name</code> attribute plus target namespace, <b>then </b>
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">6.1.1 It must have exactly one such group.</div><div class="clnumber">6.1.2 The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of both that group's <code>minOccurs</code> and
<code>maxOccurs</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> must be <code>1</code> (or <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>).</div></div>
</div><div class="clnumber">6.2 <b>If </b>it has no such self-reference, <b>then </b>
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">6.2.1 The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of its own <code>name</code> attribute plus target
namespace must successfully <a class="termref" href="#key-resolve"><span class="arrow">·</span>resolve<span class="arrow">·</span></a> to a
model group definition in <b>I</b>.</div><div class="clnumber">6.2.2 The <a class="propref" href="#model_group">{model group}</a> of the model group definition which
corresponds to it per <a href="#declare-namedModelGroup">XML Representation of Model Group Definition Schema Components (§3.7.2)</a> must be a <a class="termref" href="#cd-model-restriction"><span class="arrow">·</span>valid
restriction<span class="arrow">·</span></a> of the <a class="propref" href="#model_group">{model group}</a> of that model group
definition in <b>I</b>, as defined in <a href="#cos-particle-restrict">Particle Valid (Restriction) (§3.9.6)</a>.</div></div></div></div></div><div class="clnumber">7 Within the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, for each <a class="eltref" href="#element-attributeGroup"><attributeGroup></a>
the appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">7.1 <b>If </b>it has an <a class="eltref" href="#element-attributeGroup"><attributeGroup></a> among its contents the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of whose
<code>ref</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> is the same as the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of its own
<code>name</code> attribute plus target namespace, <b>then </b>it must have exactly one such group.</div><div class="clnumber">7.2<a name="c-agrere" id="c-agrere"> </a><b>If </b>it has no such self-reference, <b>then </b>
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">7.2.1 The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of its own <code>name</code> attribute plus target
namespace must successfully <a class="termref" href="#key-resolve"><span class="arrow">·</span>resolve<span class="arrow">·</span></a> to an
attribute group definition in <b>I</b>.</div><div class="clnumber">7.2.2 The <a class="propref" href="#ag-attribute_declarations">{attribute uses}</a> and <a class="propref" href="#ag-attribute_wildcard">{attribute wildcard}</a> of the attribute group definition which
corresponds to it per <a href="#declare-attributeGroup">XML Representation of Attribute Group Definition Schema Components (§3.6.2)</a> must be <a class="termref" href="#cd-model-restriction"><span class="arrow">·</span>valid
restrictions<span class="arrow">·</span></a> of the <a class="propref" href="#ag-attribute_declarations">{attribute uses}</a> and
<a class="propref" href="#ag-attribute_wildcard">{attribute wildcard}</a> of that attribute group
definition in <b>I</b>, as defined in clause <a href="#c-rad">2</a>, clause <a href="#c-rad2">3</a> and clause <a href="#c-raw">4</a> of <a href="#derivation-ok-restriction">Derivation Valid (Restriction, Complex) (§3.4.6)</a> (where references to the base type definition are understood as references to the attribute group
definition in <b>I</b>).</div></div></div></div>
<div class="note"><b>Note: </b>An attribute group restrictively redefined per clause <a href="#c-agrere">7.2</a> corresponds to an attribute group whose <a class="propref" href="#ag-attribute_declarations">{attribute uses}</a> consist all and only of those attribute uses corresponding to <a class="eltref" href="#element-attribute"><attribute></a>s explicitly present among the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> of the <a class="eltref" href="#element-redefine"><redefine></a>ing <a class="eltref" href="#element-attributeGroup"><attributeGroup></a>. No inheritance from the <a class="eltref" href="#element-redefine"><redefine></a>d attribute group occurs. Its <a class="propref" href="#ag-attribute_wildcard">{attribute wildcard}</a> is similarly based purely on an explicit <a class="eltref" href="#element-anyAttribute"><anyAttribute></a>, if present.</div>
</div></div>
</div></div><div class="constraintnote"><a name="src-expredef" id="src-expredef"/><b>Schema Representation Constraint: Individual Component Redefinition</b><br/><div class="constraint">Corresponding to each non-<a class="eltref" href="#element-annotation"><annotation></a> member of the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> of a <a class="eltref" href="#element-redefine"><redefine></a> there are one or two schema components in
the <a class="eltref" href="#element-redefine"><redefine></a>ing schema:<div class="constraintlist"><div class="clnumber">1 The <a class="eltref" href="#element-simpleType"><simpleType></a> and <a class="eltref" href="#element-complexType"><complexType></a>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> information items each
correspond to two components:<div class="constraintlist"><div class="clnumber">1.1 One component which corresponds to the top-level definition item with
the same <code>name</code> in
the <a class="eltref" href="#element-redefine"><redefine></a>d schema document, as defined in <a href="#components">Schema Component Details (§3)</a>, except that its <span class="anonRef">{name}</span> is <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a>;</div><div class="clnumber">1.2 One component which corresponds to the information item itself, as defined
in <a href="#components">Schema Component Details (§3)</a>, except that its <span class="anonRef">{base type definition}</span> is
the component defined in 1.1 above.</div></div>This pairing ensures the coherence constraints on type definitions
are respected, while at the same time achieving the desired effect, namely that
references to names of redefined components in both the <a class="eltref" href="#element-redefine"><redefine></a>ing and
<a class="eltref" href="#element-redefine"><redefine></a>d schema documents resolve to the redefined component
as specified in 1.2 above.</div><div class="clnumber">2 The <a class="eltref" href="#element-group"><group></a> and <a class="eltref" href="#element-attributeGroup"><attributeGroup></a>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> each correspond to a single component, as defined in <a href="#components">Schema Component Details (§3)</a>, except that if and when a self-reference based on a <code>ref</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> whose <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> is the same as the item's <code>name</code> plus target namespace is resolved, a component which corresponds to the top-level definition item of that name and the appropriate kind in
<b>I</b> is used.</div></div>In all cases there must be a top-level definition item of the appropriate name and kind in
the <a class="eltref" href="#element-redefine"><redefine></a>d schema document.</div></div><div class="note"><b>Note: </b>The above is carefully worded so that multiple equivalent <a class="eltref" href="#element-redefine"><redefine></a>ing of the same schema document will not constitute a violation of
clause <a href="#c-nmd">2</a> of <a href="#sch-props-correct">Schema Properties Correct (§3.15.6)</a>, but applications are
allowed, indeed encouraged, to avoid <a class="eltref" href="#element-redefine"><redefine></a>ing the same
schema document in the same way more than once to forestall the necessity of
establishing identity component by component (although this will have to be
done for the individual redefinitions themselves).</div></div><div class="div3">
<h4><a id="composition-schemaImport" name="composition-schemaImport"/>4.2.3 References to schema components across namespaces</h4><p>As described in <a href="#concepts-data-model">XML Schema Abstract Data Model (§2.2)</a>, every top-level schema component is associated with
a target namespace (or, explicitly, with none). This section sets out
the exact mechanism and syntax in the XML form of
schema definition by which a reference to a foreign component is made, that is, a component with a different target namespace from that of the referring component.</p><p>Two things are required: not only a means
of addressing such foreign components but also a signal to schema-aware processors that a
schema document contains such references:</p><div class="reprdef"><div class="reprHeader"><span class="reprdef">XML Representation Summary</span>: <code>import</code> Element Information Item</div><div class="reprBody">
<p class="element-syntax-1"><a name="element-import" id="element-import"><import</a><br/>  id = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ID">ID</a><br/>  namespace = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#anyURI">anyURI</a><br/>  schemaLocation = <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#anyURI">anyURI</a><br/>  <em>{any attributes with non-schema namespace . . .}</em>><br/><em>  Content: </em>(<a class="eltref" href="#element-annotation">annotation</a>?)<br/></import></p>
</div></div><p>The <a class="eltref" href="#element-import"><import></a> element information item identifies namespaces
used in external references, i.e. those whose
<a class="termref" href="#gloss-QName"><span class="arrow">·</span>QName<span class="arrow">·</span></a> identifies them as coming from a
different namespace (or none) than the enclosing schema document's
<code>targetNamespace</code>. The <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of its <code>namespace</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> indicates that the containing schema document may contain
qualified references to schema components in that namespace (via one or more
prefixes declared with namespace declarations in the normal way). If that
attribute is absent, then the import allows unqualified reference to components
with no target namespace.
Note that components to be imported need not be in the form of a
<a class="termref" href="#key-schemaDoc"><span class="arrow">·</span>schema document<span class="arrow">·</span></a>; the processor
is free to access or construct components using means of its own
choosing.</p><p>The
<a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>schemaLocation</code>, if present, gives a
hint as to where a serialization of a <a class="termref" href="#key-schemaDoc"><span class="arrow">·</span>schema document<span class="arrow">·</span></a> with declarations and definitions for that
namespace (or none) may be found. When no
<code>schemaLocation</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> is present, the schema author is leaving the
identification of that schema to the instance, application or user, via the mechanisms described
below in <a href="#composition-instances">Layer 3: Schema Document Access and Web-interoperability (§4.3)</a>. When a <code>schemaLocation</code> is present, it
must contain a single URI reference which the schema author
warrants will resolve to a serialization of a <a class="termref" href="#key-schemaDoc"><span class="arrow">·</span>schema document<span class="arrow">·</span></a> containing the component(s) in the
<a class="eltref" href="#element-import"><import></a>ed namespace referred to elsewhere in the containing
schema document.</p><div class="note"><b>Note: </b>Since both the <code>namespace</code> and <code>schemaLocation</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> are optional, a bare <code><import/></code> information item
is allowed. This simply allows unqualified reference to foreign
components with no target namespace without giving any hints as to where to find them.</div><div class="exampleOuter"><div class="exampleHeader">Example</div><div class="exampleWrapper">The same namespace may be used both for real work, and in the course of
defining schema components in terms of foreign components:</div><div class="exampleInner"><pre><schema xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:html="http://www.w3.org/1999/xhtml"
targetNamespace="uri:mywork" xmlns:my="uri:mywork">
<import namespace="http://www.w3.org/1999/xhtml"/>
<annotation>
<documentation>
<html:p>[Some documentation for my schema]</html:p>
</documentation>
</annotation>
. . .
<complexType name="myType">
<sequence>
<element ref="html:p" minOccurs="0"/>
</sequence>
. . .
</complexType>
<element name="myElt" type="my:myType"/>
</schema>
</pre></div><div class="exampleWrapper">The treatment of references as <a class="termref" href="#gloss-QName"><span class="arrow">·</span>QNames<span class="arrow">·</span></a> implies that since (with the exception of
the schema for schemas) the target namespace and the XML Schema namespace
differ, without massive redeclaration of the default namespace
<em>either</em> internal references to the names being defined in a schema document
<em>or</em> the schema declaration and definition elements themselves must
be explicitly qualified. This example takes the first option -- most other
examples in this specification have taken the second.</div></div><div class="constraintnote"><a name="src-import" id="src-import"/><b>Schema Representation Constraint: Import Constraints and Semantics</b><br/><div class="constraint">In addition to the conditions imposed on <a class="eltref" href="#element-import"><import></a> element
information items by the schema for schemas
<b>all</b> of the following must be true:<div class="constraintlist"><div class="clnumber">1 The appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">1.1 <b>If </b>the <code>namespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> is present, <b>then </b>its <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> must not match the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the
enclosing <a class="eltref" href="#element-schema"><schema></a>'s <code>targetNamespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>.</div><div class="clnumber">1.2 <b>If </b>the <code>namespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> is not present, <b>then </b>the enclosing <a class="eltref" href="#element-schema"><schema></a> must have a <code>targetNamespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a></div></div></div><div class="clnumber">2<a name="c-ims" id="c-ims"> </a>If the application schema reference strategy using the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a>s of
the <code>schemaLocation</code> and <code>namespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a>,
provides a referent, as defined by <a href="#schema_reference">Schema Document Location Strategy (§4.3.2)</a>,
<b>one</b> of the following must be true:<div class="constraintlist"><div class="clnumber">2.1 The referent is (a fragment of) a resource which is an XML document
(see clause <a href="#c-vxd">1.1</a>), which in turn corresponds to a <a class="eltref" href="#element-schema"><schema></a>
element information item in a well-formed information set, which in turn
corresponds to a valid schema.</div><div class="clnumber">2.2 The referent is a <a class="eltref" href="#element-schema"><schema></a>
element information item in a well-formed information set, which in turn
corresponds to a valid schema.</div></div>
In either case call the <a class="eltref" href="#element-schema"><schema></a> item <b>SII</b> and the valid schema <b>I</b>.</div><div class="clnumber">3 The appropriate <b>case</b> among the following
must be true:<div class="constraintlist"><div class="clnumber">3.1 <b>If </b>there is a <code>namespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, <b>then </b>its <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> must be identical to the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of the <code>targetNamespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> of <b>SII</b>.</div><div class="clnumber">3.2 <b>If </b>there is no <code>namespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>, <b>then </b><b>SII</b>
must have no <code>targetNamespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a></div></div></div></div>
<p/>It is <em>not</em> an error for the application schema reference
strategy to fail. It
<em>is</em> an error for it to resolve but the rest of clause <a href="#c-ims">2</a> above to
fail to be satisfied. Failure to find a referent may well cause less than complete
<a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> outcomes, of course.<p/>The <a class="termref" href="#key-component"><span class="arrow">·</span>schema components<span class="arrow">·</span></a> (that is
<a class="propref" href="#type_definitions">{type definitions}</a>, <a class="propref" href="#attribute_declarations">{attribute declarations}</a>, <a class="propref" href="#element_declarations">{element declarations}</a>, <a class="propref" href="#attribute_group_definitions">{attribute group definitions}</a>, <a class="propref" href="#model_group_definitions">{model group definitions}</a>, <a class="propref" href="#notation_declarations">{notation declarations}</a>) of a schema corresponding to a
<a class="eltref" href="#element-schema"><schema></a> element information item with one or more <a class="eltref" href="#element-import"><import></a> element information items must include not only definitions or declarations corresponding to the appropriate members of its <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, but also, for each of those <a class="eltref" href="#element-import"><import></a> element information items for which clause <a href="#c-ims">2</a> above is satisfied, a set of <a class="termref" href="#key-component"><span class="arrow">·</span>schema components<span class="arrow">·</span></a> identical to all the <a class="termref" href="#key-component"><span class="arrow">·</span>schema components<span class="arrow">·</span></a> of <b>I</b>.</div></div><div class="note"><b>Note: </b>The above is carefully worded so that multiple <a class="eltref" href="#element-import"><import></a>ing of the same schema document will not constitute a violation of
clause <a href="#c-nmd">2</a> of <a href="#sch-props-correct">Schema Properties Correct (§3.15.6)</a>, but applications are
allowed, indeed encouraged, to avoid <a class="eltref" href="#element-import"><import></a>ing the same schema document more than once to forestall the necessity of establishing identity
component by component. Given that the <code>schemaLocation</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a> is only a hint, it is open to applications to ignore all but the
first <a class="eltref" href="#element-import"><import></a> for a given namespace, regardless of the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of
<code>schemaLocation</code>, but such a strategy risks missing useful
information when new <code>schemaLocation</code>s are offered.</div></div></div><div class="div2">
<h3 class="withToc"><span class="nav"><a class="nav" href="#layer2"><img src="previous.jpg" alt="previous sub-section"/></a> </span><a id="composition-instances" name="composition-instances"/>4.3 Layer 3: Schema Document Access and Web-interoperability</h3><div class="localToc">        4.3.1 <a href="#schema-repr">Standards for representation of schemas and retrieval of schema documents on the Web</a><br/>
        4.3.2 <a href="#schema-loc">How schema definitions are located on the Web</a><br/>
</div><p>Layers 1 and 2 provide a framework for <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> and XML definition of schemas in a broad variety of environments. Over time, a range
of standards and conventions may well evolve to support interoperability of XML
Schema implementations on the World Wide Web. Layer 3 defines the minimum level
of function required of all conformant processors operating on the Web:
it is intended that, over time, future standards (e.g. XML Packages) for interoperability on the
Web and in other environments can be introduced without the need to republish
this specification.</p><div class="div3">
<h4><a id="schema-repr" name="schema-repr"/>4.3.1 Standards for representation of schemas and retrieval of schema documents on the Web</h4><p>For interoperability, serialized <a class="termref" href="#key-schemaDoc"><span class="arrow">·</span>schema documents<span class="arrow">·</span></a>, like all other Web resources, may be identified by
URI and retrieved using the standard mechanisms of the Web (e.g. http, https,
etc.) Such documents on the Web must be part of XML documents (see clause <a href="#c-vxd">1.1</a>), and are represented in the
standard XML schema definition form described by layer 2 (that is as <a class="eltref" href="#element-schema"><schema></a>
element information items). </p><div class="note"><b>Note: </b> there will often be times when a schema document will be a
complete XML 1.0 document whose document element is <a class="eltref" href="#element-schema"><schema></a>. There will be
other occasions in which <a class="eltref" href="#element-schema"><schema></a> items will be contained in other
documents, perhaps referenced using fragment and/or XPointer notation.
</div><div class="note"><b>Note: </b>The variations among server software and web site administration policies
make it difficult to recommend any particular approach to retrieval requests
intended to retrieve serialized <a class="termref" href="#key-schemaDoc"><span class="arrow">·</span>schema documents<span class="arrow">·</span></a>. An <code>Accept</code> header of <code>application/xml,
text/xml; q=0.9, */*</code> is perhaps a reasonable starting point.</div></div><div class="div3">
<h4><a id="schema-loc" name="schema-loc"/>4.3.2 How schema definitions are located on the Web</h4><p>As described in <a href="#layer1">Layer 1: Summary of the Schema-validity Assessment Core (§4.1)</a>, processors are responsible for providing the
schema components (definitions and declarations) needed for <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a>. This
section introduces a set of normative conventions to facilitate interoperability
for instance and schema documents retrieved and processed from the Web.</p><div class="note"><b>Note: </b> As discussed above in <a href="#layer2">Layer 2: Schema Documents, Namespaces and Composition (§4.2)</a>, other non-Web mechanisms for delivering schemas for <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> may exist, but are outside the scope of this specification.</div><p>Processors on the Web are free to undertake <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> against arbitrary
schemas in any of the ways set out in <a href="#validation_outcome">Assessing Schema-Validity (§5.2)</a>. However, it
is useful to have a common convention for determining the schema to use. Accordingly, general-purpose schema-aware processors (i.e. those not
specialized to one or a fixed set of pre-determined schemas)
undertaking <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> of a document on the web
must behave as follows:
</p><ul><li>unless directed otherwise by the user, <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> is undertaken on the document
element information item of the specified document;</li><li>unless directed otherwise by the user, the
processor is required to construct a schema corresponding to a schema document
whose <code>targetNamespace</code> is
identical to the
namespace name, if any, of the element information item on which <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> is undertaken.</li></ul><p>
</p><p>The composition of the complete
schema for use in <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> is discussed in <a href="#layer2">Layer 2: Schema Documents, Namespaces and Composition (§4.2)</a> above.
The means used to locate appropriate schema document(s) are processor and
application dependent, subject to the following requirements: </p><ol class="enumar"><li>Schemas are represented on the Web in the form specified above in <a href="#schema-repr">Standards for representation of schemas and retrieval of schema documents on the Web (§4.3.1)</a>;</li><li>The author of a document uses namespace declarations to indicate the intended
interpretation of names appearing therein; there may or may not be a schema
retrievable via the namespace name. Accordingly whether a processor's default
behavior is or is not to attempt such dereferencing, it must always provide
for user-directed overriding of that default.
<div class="note"><b>Note: </b> Experience suggests that it is not in all cases safe or desirable from
a performance point of view to dereference namespace names as a matter of course. User community and/or
consumer/provider agreements may establish circumstances in which such dereference is a sensible
default strategy: this specification allows but does not require particular communities to
establish and implement such conventions. Users are always free to supply namespace names as schema location information when dereferencing <em>is</em> desired: see below.</div></li><li>
On the other hand, in case a document author (human or not) created a
document with a particular schema in view, and warrants that some or
all of the document conforms to that schema, the
<code>schemaLocation</code> and <code>noNamespaceSchemaLocation</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> (in the XML Schema instance namespace,
that is, <code>http://www.w3.org/2001/XMLSchema-instance</code>) (hereafter
<code>xsi:schemaLocation</code> and
<code>xsi:noNamespaceSchemaLocation</code>) are provided. The first records
the author's warrant with pairs of URI references (one for the namespace name, and
one for a hint as to the location of a schema document defining names for that
namespace name). The second similarly provides a URI reference as a hint as to
the location of a schema document with no <code>targetNamespace</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attribute]</a>.<p/>Unless directed otherwise, for example by the invoking application
or by command line option, processors
should attempt to dereference each schema document location URI in the
<a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a> of such
<code>xsi:schemaLocation</code> and <code>xsi:noNamespaceSchemaLocation</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a>, see details below.</li><li><code>xsi:schemaLocation</code> and
<code>xsi:noNamespaceSchemaLocation</code> <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> can occur on any
element. However, it is an error if such an attribute occurs
<em>after</em> the first appearance of an element or attribute information
item within an
element information item initially <a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a> whose <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[namespace name]</a> it addresses. According to the rules of
<a href="#layer1">Layer 1: Summary of the Schema-validity Assessment Core (§4.1)</a>, the corresponding schema may be lazily assembled, but is otherwise
stable throughout <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a>. Although schema location attributes can occur
on any element, and can be processed incrementally as discovered, their effect
is essentially global to the <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a>. Definitions and declarations remain
in effect beyond the scope of the element on which the binding is declared.
</li></ol><div class="exampleOuter"><div class="exampleHeader">Example</div><div class="exampleWrapper">Multiple schema bindings can be declared using a single
attribute. For example consider a stylesheet:</div><div class="exampleInner"><pre>
<stylesheet xmlns="http://www.w3.org/1999/XSL/Transform"
xmlns:html="http://www.w3.org/1999/xhtml"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.w3.org/1999/XSL/Transform
http://www.w3.org/1999/XSL/Transform.xsd
http://www.w3.org/1999/xhtml
http://www.w3.org/1999/xhtml.xsd">
</pre></div><div class="exampleWrapper">The namespace names used in <code>schemaLocation</code> can, but need not
be identical to those actually qualifying the element within whose start tag
it is found or its other attributes. For example, as above, all
schema location information can be declared on the document element
of a document, if desired,
regardless of where the namespaces are actually used. </div></div><div class="constraintnote"><a name="schema_reference" id="schema_reference"/><b>Schema Representation Constraint: Schema Document Location Strategy</b><br/><div class="constraint">Given a namespace name (or none) and (optionally) a URI reference from
<code>xsi:schemaLocation</code> or <code>xsi:noNamespaceSchemaLocation</code>,
schema-aware processors may implement any combination of the following
strategies, in any order:
<div class="constraintlist"><div class="clnumber">1
Do nothing, for instance because a schema containing components for the
given namespace name is already known to be available, or because it
is known in advance that no efforts to locate schema documents will be successful
(for
example in embedded systems);
</div><div class="clnumber">2
Based on the location URI,
identify an existing schema document,
either as a resource which is an XML document or a <a class="eltref" href="#element-schema"><schema></a> element
information item, in some local schema repository;
</div><div class="clnumber">3
Based on the namespace name, identify an existing schema document,
either as a resource which is an XML document or a <a class="eltref" href="#element-schema"><schema></a> element
information item, in some local schema repository;
</div><div class="clnumber">4
Attempt to resolve the location URI,
to locate a
resource on the web which is or contains or references a <a class="eltref" href="#element-schema"><schema></a> element;
</div><div class="clnumber">5
Attempt to resolve the namespace name to locate such a resource.
</div></div>
Whenever possible configuration and/or invocation options for selecting and/or ordering
the implemented strategies should be provided.
</div></div><p>Improved or alternative conventions for Web interoperability can
be standardized in the future without reopening this specification. For
example, the W3C is currently considering initiatives to standardize the
packaging of resources relating to particular documents and/or namespaces: this
would be an addition to the mechanisms described here for layer 3. This
architecture also facilitates innovation at layer 2: for example, it would be
possible in the future to define an additional standard for the representation of
schema components which allowed e.g. type definitions to be specified piece by
piece, rather than all at once.</p></div></div></div><div class="div1">
<h2><a id="conformance" name="conformance"/>5 Schemas and Schema-validity Assessment</h2><p>The architecture of schema-aware processing allows for a rich characterization of XML documents: schema validity is not a binary predicate.</p><p>This specification distinguishes between errors in schema construction and structure, on the
one hand, and schema validation outcomes, on the other.</p><div class="div2">
<h3><span class="nav"> <a class="nav" href="#validation_outcome"><img src="next.jpg" alt="next sub-section"/></a></span><a id="conformance-schemaValidity" name="conformance-schemaValidity"/>5.1 Errors in Schema Construction and Structure</h3><p>Before <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> can be attempted, a schema is required.
Special-purpose applications are free to determine a schema for use in <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> by whatever
means are appropriate, but general purpose processors should implement the
strategy set out in <a href="#schema_reference">Schema Document Location Strategy (§4.3.2)</a>, starting with the
namespaces declared in the document whose <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> is being undertaken, and the <a class="termref" href="#key-vv"><span class="arrow">·</span>actual value<span class="arrow">·</span></a>s of the
<code>xsi:schemaLocation</code> and <code>xsi:noNamespaceSchemaLocation</code>
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> thereof, if any, along with any other information about
schema identity or schema document location provided by users in
application-specific ways, if any.</p><p>It is an
error if a
schema and all the components which are the value of any of its properties,
recursively, fail to satisfy all the relevant Constraints on Schemas set out in
the last section of each of the subsections of <a href="#components">Schema Component Details (§3)</a>.</p><p>If a schema is derived from one or more schema documents (that is, one or
more <a class="eltref" href="#element-schema"><schema></a> element information items) based on the
correspondence rules set out in <a href="#components">Schema Component Details (§3)</a> and <a href="#composition">Schemas and Namespaces: Access and Composition (§4)</a>, two additional
conditions hold:
</p><ul><li>It is an error if any such schema document would not be fully valid with respect
to a schema corresponding to the <a href="#normative-schemaSchema">Schema for Schemas (normative) (§A)</a>, that
is, following schema-validation with such a schema, the <a class="eltref" href="#element-schema"><schema></a> element
information items would have a <a class="propref" href="#e-validation_attempted">[validation attempted]</a>
property with value <i>full</i> or <i>partial</i> and a
<a class="propref" href="#e-validity">[validity]</a> property
with value <i>valid</i>.</li><li>It is an error if any such schema document is or contains any element
information items which violate any of the relevant Schema Representation
Constraints set out in <a href="#outcome-src">Schema Representation Constraints (§C.3)</a>.</li></ul><p>
</p><p>The three cases described above are the only types of error which this
specification defines. With respect to the processes of the checking of schema structure
and the construction of schemas corresponding to schema documents, this
specification imposes no restrictions on processors after an error is detected.
However <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> with respect to schema-like entities which do <em>not</em>
satisfy all the above conditions is incoherent. Accordingly, conformant
processors must not attempt to undertake <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> using such non-schemas.</p></div><div class="div2">
<h3><span class="nav"><a class="nav" href="#conformance-schemaValidity"><img src="previous.jpg" alt="previous sub-section"/></a> <a class="nav" href="#conformance-missing"><img src="next.jpg" alt="next sub-section"/></a></span><a id="validation_outcome" name="validation_outcome"/>5.2 Assessing Schema-Validity</h3><p>With a schema which satisfies the conditions expressed in <a href="#conformance-schemaValidity">Errors in Schema Construction and Structure (§5.1)</a> above, the schema-validity of an element information item can be assessed. Three primary approaches to this are possible:
</p><div class="constraintlist"><div class="clnumber">1 The user or application identifies a complex type definition from among the
<a class="propref" href="#type_definitions">{type definitions}</a> of the schema, and appeals to <a href="#cvc-assess-elt">Schema-Validity Assessment (Element) (§3.3.4)</a> (clause <a href="#c-td">1.2</a>);</div><div class="clnumber">2<a name="c-res" id="c-res"> </a>The user or application identifies a element declaration from among the
<a class="propref" href="#element_declarations">{element declarations}</a> of the schema, checks that its <a class="propref" href="#e-name">{name}</a> and <a class="propref" href="#e-target_namespace">{target namespace}</a> match the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[local name]</a> and <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[namespace name]</a> of the item, and appeals to <a href="#cvc-assess-elt">Schema-Validity Assessment (Element) (§3.3.4)</a> (clause <a href="#c-ed">1.1</a>);</div><div class="clnumber">3 The processor starts from <a href="#cvc-assess-elt">Schema-Validity Assessment (Element) (§3.3.4)</a> with no
stipulated declaration or definition, and either <a class="termref" href="#key-sva"><span class="arrow">·</span>strict<span class="arrow">·</span></a> or <a class="termref" href="#key-lva"><span class="arrow">·</span>lax<span class="arrow">·</span></a> assessment ensues, depending on whether or not the element information and the schema determine either an element declaration (by name) or a type definition (via <code>xsi:type</code>) or not.</div></div><p>
</p><p>The outcome of this effort, in any case, will be manifest in the
<span class="anonRef">[validation attempted]</span>
and <span class="anonRef">[validity]</span> properties on
the element information item and its <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> and <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>,
recursively, as defined by <a href="#sic-e-outcome">Assessment Outcome (Element) (§3.3.5)</a> and <a href="#sic-a-outcome">Assessment Outcome (Attribute) (§3.2.5)</a>. It is up to applications to decide what constitutes a successful outcome.</p><p>Note that every element and attribute information item
participating in the <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> will also have a <span class="anonRef">[validation context]</span> property
which refers back to the element information item at which <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> began. <span class="termdef"><a id="key-vr" name="key-vr">[Definition:]  </a>This item, that is the element information item at which <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> began, is called the <b>validation root</b></span>.</p><div class="note"><b>Note: </b>This specification does not reconstruct the XML 1.0 notion of
<em>root</em> in either schemas or instances. Equivalent
functionality is provided for at <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a>
invocation, via clause <a href="#c-res">2</a> above.</div><div class="note"><b>Note: </b>This specification has nothing normative to say about multiple <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a>
episodes. It should however be clear from the above that if a processor
restarts <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> with respect to a <a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a>
some <a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a> contributions from the previous <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a>
may be overwritten. Restarting nonetheless may be useful, particularly at a node whose
<span class="anonRef">[validation attempted]</span> property is <i>none</i>, in which
case there are three obvious cases in which additional useful information may result:
<ul><li><a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> was not attempted because
of a <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> failure, but declarations
and/or definitions are available for at least some of the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> or <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a>;</li><li><a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> was not attempted because a
named definition or declaration was missing, but after further effort the
processor has retrieved it.</li><li><a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> was not attempted because
it was <i>skip</i>ped, but the processor has at least some declarations
and/or definitions available for at least some of the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> or <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a>.</li></ul>
</div></div><div class="div2">
<h3><span class="nav"><a class="nav" href="#validation_outcome"><img src="previous.jpg" alt="previous sub-section"/></a> <a class="nav" href="#conformance-processorResponsibilities"><img src="next.jpg" alt="next sub-section"/></a></span><a id="conformance-missing" name="conformance-missing"/>5.3 Missing Sub-components</h3><p>At the beginning of <a href="#components">Schema Component Details (§3)</a>, attention is drawn to the
fact that most kinds of schema components have properties which are described therein
as having other components, or sets of other components, as values, but that
when components are constructed on the basis of their correspondence with
element information items in schema documents, such properties usually
correspond to <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#QName">QNames</a>, and the
<a class="termref" href="#src-resolve"><span class="arrow">·</span>resolution<span class="arrow">·</span></a> of such <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#QName">QNames</a> may fail, resulting in one or more values of or containing <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> where a component is mandated.</p><p>If at any time during <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a>, an
element or attribute information item is being <a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a> with respect to a component of any kind any of whose
properties has or contains such an <a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> value,
the <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> is modified, as following:
</p><ul><li>In the case of attribute information items, the effect is
as if clause <a href="#c-a1">1</a> of <a href="#cvc-attribute">Attribute Locally Valid (§3.2.4)</a> had failed;</li><li>In the case of element information items, the effect is
as if clause <a href="#c-ea">1</a> of <a href="#cvc-elt">Element Locally Valid (Element) (§3.3.4)</a> had failed;</li><li>In the case of element information items, processors may choose to
continue <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a>: see <a class="termref" href="#key-lva"><span class="arrow">·</span>lax assessment<span class="arrow">·</span></a>.</li></ul><p>
</p><p>Because of the value specification for <a class="propref" href="#e-validation_attempted">[validation attempted]</a> in <a href="#sic-e-outcome">Assessment Outcome (Element) (§3.3.5)</a>, if this situation ever arises, the
document as a whole cannot show a <a class="propref" href="#e-validation_attempted">[validation attempted]</a>
of <i>full</i>.</p></div><div class="div2">
<h3><span class="nav"><a class="nav" href="#conformance-missing"><img src="previous.jpg" alt="previous sub-section"/></a> </span><a id="conformance-processorResponsibilities" name="conformance-processorResponsibilities"/>5.4 Responsibilities of Schema-aware Processors</h3><p>Schema-aware processors are responsible for processing XML documents,
schemas and schema documents, as appropriate given the level of conformance
(as defined in <a href="#concepts-conformance">Conformance (§2.4)</a>) they support,
consistently with the conditions set out above.</p></div></div></div><div class="back"><div class="div1">
<h2><a id="normative-schemaSchema" name="normative-schemaSchema"/>A Schema for Schemas (normative)</h2><p>The XML representation of the schema for schema documents is presented here
as a normative
part of the specification, and as an illustrative example of how the XML Schema
language can
define itself using its own constructs. The names of XML
Schema language types, elements, attributes and groups defined here
are evocative of their purpose, but are occasionally verbose. </p><p>There is some annotation in comments, but a fuller annotation will require
the use of embedded documentation facilities or a hyperlinked external
annotation for which tools are not yet readily available.</p><p>Since a schema document is an XML document, it has optional XML and doctype
declarations that are provided here for completeness. The root
<code>schema</code> element defines a new schema. Since this is a schema for
<em>XML Schema: Structures</em>, the <code>targetNamespace</code> references the XML Schema namespace itself.</p><pre><!DOCTYPE xs:schema PUBLIC "-//W3C//DTD XMLSCHEMA 200102//EN" "XMLSchema.dtd" [
<!-- provide ID type information even for parsers which only read the
internal subset -->
<!ATTLIST xs:schema id ID #IMPLIED>
<!ATTLIST xs:complexType id ID #IMPLIED>
<!ATTLIST xs:complexContent id ID #IMPLIED>
<!ATTLIST xs:simpleContent id ID #IMPLIED>
<!ATTLIST xs:extension id ID #IMPLIED>
<!ATTLIST xs:element id ID #IMPLIED>
<!ATTLIST xs:group id ID #IMPLIED>
<!ATTLIST xs:all id ID #IMPLIED>
<!ATTLIST xs:choice id ID #IMPLIED>
<!ATTLIST xs:sequence id ID #IMPLIED>
<!ATTLIST xs:any id ID #IMPLIED>
<!ATTLIST xs:anyAttribute id ID #IMPLIED>
<!ATTLIST xs:attribute id ID #IMPLIED>
<!ATTLIST xs:attributeGroup id ID #IMPLIED>
<!ATTLIST xs:unique id ID #IMPLIED>
<!ATTLIST xs:key id ID #IMPLIED>
<!ATTLIST xs:keyref id ID #IMPLIED>
<!ATTLIST xs:selector id ID #IMPLIED>
<!ATTLIST xs:field id ID #IMPLIED>
<!ATTLIST xs:include id ID #IMPLIED>
<!ATTLIST xs:import id ID #IMPLIED>
<!ATTLIST xs:redefine id ID #IMPLIED>
<!ATTLIST xs:notation id ID #IMPLIED>
]>
<?xml version='1.0'?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" blockDefault="#all"
elementFormDefault="qualified" xml:lang="EN"
targetNamespace="http://www.w3.org/2001/XMLSchema"
version="Id: structures.xsd,v 1.2 2004/01/15 11:34:25 ht Exp ">
<xs:annotation>
<xs:documentation source="../structures/structures-with-errata.html.html">
The schema corresponding to this document is normative,
with respect to the syntactic constraints it expresses in the
XML Schema language. The documentation (within &lt;documentation> elements)
below, is not normative, but rather highlights important aspects of
the W3C Recommendation of which this is a part</xs:documentation>
</xs:annotation>
<xs:annotation>
<xs:documentation>
The simpleType element and all of its members are defined
in datatypes.xsd</xs:documentation>
</xs:annotation>
<xs:include schemaLocation="datatypes.xsd"/>
<xs:import namespace="http://www.w3.org/XML/1998/namespace"
schemaLocation="http://www.w3.org/2001/xml.xsd">
<xs:annotation>
<xs:documentation>
Get access to the xml: attribute groups for xml:lang
as declared on 'schema' and 'documentation' below
</xs:documentation>
</xs:annotation>
</xs:import>
<xs:complexType name="openAttrs">
<xs:annotation>
<xs:documentation>
This type is extended by almost all schema types
to allow attributes from other namespaces to be
added to user schemas.
</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:restriction base="xs:anyType">
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="annotated">
<xs:annotation>
<xs:documentation>
This type is extended by all types which allow annotation
other than &lt;schema> itself
</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="xs:openAttrs">
<xs:sequence>
<xs:element ref="xs:annotation" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="id" type="xs:ID"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:group name="schemaTop">
<xs:annotation>
<xs:documentation>
This group is for the
elements which occur freely at the top level of schemas.
All of their types are based on the "annotated" type by extension.</xs:documentation>
</xs:annotation>
<xs:choice>
<xs:group ref="xs:redefinable"/>
<xs:element ref="xs:element"/>
<xs:element ref="xs:attribute"/>
<xs:element ref="xs:notation"/>
</xs:choice>
</xs:group>
<xs:group name="redefinable">
<xs:annotation>
<xs:documentation>
This group is for the
elements which can self-redefine (see &lt;redefine> below).</xs:documentation>
</xs:annotation>
<xs:choice>
<xs:element ref="xs:simpleType"/>
<xs:element ref="xs:complexType"/>
<xs:element ref="xs:group"/>
<xs:element ref="xs:attributeGroup"/>
</xs:choice>
</xs:group>
<xs:simpleType name="formChoice">
<xs:annotation>
<xs:documentation>
A utility type, not for public use</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="qualified"/>
<xs:enumeration value="unqualified"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="reducedDerivationControl">
<xs:annotation>
<xs:documentation>
A utility type, not for public use</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:derivationControl">
<xs:enumeration value="extension"/>
<xs:enumeration value="restriction"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="derivationSet">
<xs:annotation>
<xs:documentation>
A utility type, not for public use</xs:documentation>
<xs:documentation>
#all or (possibly empty) subset of {extension, restriction}</xs:documentation>
</xs:annotation>
<xs:union>
<xs:simpleType>
<xs:restriction base="xs:token">
<xs:enumeration value="#all"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType>
<xs:list itemType="xs:reducedDerivationControl"/>
</xs:simpleType>
</xs:union>
</xs:simpleType>
<xs:simpleType name="typeDerivationControl">
<xs:annotation>
<xs:documentation>
A utility type, not for public use</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:derivationControl">
<xs:enumeration value="extension"/>
<xs:enumeration value="restriction"/>
<xs:enumeration value="list"/>
<xs:enumeration value="union"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType name="fullDerivationSet">
<xs:annotation>
<xs:documentation>
A utility type, not for public use</xs:documentation>
<xs:documentation>
#all or (possibly empty) subset of {extension, restriction, list, union}</xs:documentation>
</xs:annotation>
<xs:union>
<xs:simpleType>
<xs:restriction base="xs:token">
<xs:enumeration value="#all"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType>
<xs:list itemType="xs:typeDerivationControl"/>
</xs:simpleType>
</xs:union>
</xs:simpleType>
<xs:element name="schema" id="schema">
<xs:annotation>
<xs:documentation
source="http://www.w3.org/TR/xmlschema-1/#element-schema"/>
</xs:annotation>
<xs:complexType>
<xs:complexContent>
<xs:extension base="xs:openAttrs">
<xs:sequence>
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element ref="xs:include"/>
<xs:element ref="xs:import"/>
<xs:element ref="xs:redefine"/>
<xs:element ref="xs:annotation"/>
</xs:choice>
<xs:sequence minOccurs="0" maxOccurs="unbounded">
<xs:group ref="xs:schemaTop"/>
<xs:element ref="xs:annotation" minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
</xs:sequence>
<xs:attribute name="targetNamespace" type="xs:anyURI"/>
<xs:attribute name="version" type="xs:token"/>
<xs:attribute name="finalDefault" type="xs:fullDerivationSet"
default="" use="optional"/>
<xs:attribute name="blockDefault" type="xs:blockSet" default=""
use="optional"/>
<xs:attribute name="attributeFormDefault" type="xs:formChoice"
default="unqualified" use="optional"/>
<xs:attribute name="elementFormDefault" type="xs:formChoice"
default="unqualified" use="optional"/>
<xs:attribute name="id" type="xs:ID"/>
<xs:attribute ref="xml:lang"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:key name="element">
<xs:selector xpath="xs:element"/>
<xs:field xpath="@name"/>
</xs:key>
<xs:key name="attribute">
<xs:selector xpath="xs:attribute"/>
<xs:field xpath="@name"/>
</xs:key>
<xs:key name="type">
<xs:selector xpath="xs:complexType|xs:simpleType"/>
<xs:field xpath="@name"/>
</xs:key>
<xs:key name="group">
<xs:selector xpath="xs:group"/>
<xs:field xpath="@name"/>
</xs:key>
<xs:key name="attributeGroup">
<xs:selector xpath="xs:attributeGroup"/>
<xs:field xpath="@name"/>
</xs:key>
<xs:key name="notation">
<xs:selector xpath="xs:notation"/>
<xs:field xpath="@name"/>
</xs:key>
<xs:key name="identityConstraint">
<xs:selector xpath=".//xs:key|.//xs:unique|.//xs:keyref"/>
<xs:field xpath="@name"/>
</xs:key>
</xs:element>
<xs:simpleType name="allNNI">
<xs:annotation>
<xs:documentation>
for maxOccurs</xs:documentation>
</xs:annotation>
<xs:union memberTypes="xs:nonNegativeInteger">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="unbounded"/>
</xs:restriction>
</xs:simpleType>
</xs:union>
</xs:simpleType>
<xs:attributeGroup name="occurs">
<xs:annotation>
<xs:documentation>
for all particles</xs:documentation>
</xs:annotation>
<xs:attribute name="minOccurs" type="xs:nonNegativeInteger" default="1"
use="optional"/>
<xs:attribute name="maxOccurs" type="xs:allNNI" default="1" use="optional"/>
</xs:attributeGroup>
<xs:attributeGroup name="defRef">
<xs:annotation>
<xs:documentation>
for element, group and attributeGroup,
which both define and reference</xs:documentation>
</xs:annotation>
<xs:attribute name="name" type="xs:NCName"/>
<xs:attribute name="ref" type="xs:QName"/>
</xs:attributeGroup>
<xs:group name="typeDefParticle">
<xs:annotation>
<xs:documentation>
'complexType' uses this</xs:documentation>
</xs:annotation>
<xs:choice>
<xs:element name="group" type="xs:groupRef"/>
<xs:element ref="xs:all"/>
<xs:element ref="xs:choice"/>
<xs:element ref="xs:sequence"/>
</xs:choice>
</xs:group>
<xs:group name="nestedParticle">
<xs:choice>
<xs:element name="element" type="xs:localElement"/>
<xs:element name="group" type="xs:groupRef"/>
<xs:element ref="xs:choice"/>
<xs:element ref="xs:sequence"/>
<xs:element ref="xs:any"/>
</xs:choice>
</xs:group>
<xs:group name="particle">
<xs:choice>
<xs:element name="element" type="xs:localElement"/>
<xs:element name="group" type="xs:groupRef"/>
<xs:element ref="xs:all"/>
<xs:element ref="xs:choice"/>
<xs:element ref="xs:sequence"/>
<xs:element ref="xs:any"/>
</xs:choice>
</xs:group>
<xs:complexType name="attribute">
<xs:complexContent>
<xs:extension base="xs:annotated">
<xs:sequence>
<xs:element name="simpleType" type="xs:localSimpleType" minOccurs="0"/>
</xs:sequence>
<xs:attributeGroup ref="xs:defRef"/>
<xs:attribute name="type" type="xs:QName"/>
<xs:attribute name="use" default="optional" use="optional">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="prohibited"/>
<xs:enumeration value="optional"/>
<xs:enumeration value="required"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="default" type="xs:string"/>
<xs:attribute name="fixed" type="xs:string"/>
<xs:attribute name="form" type="xs:formChoice"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="topLevelAttribute">
<xs:complexContent>
<xs:restriction base="xs:attribute">
<xs:sequence>
<xs:element ref="xs:annotation" minOccurs="0"/>
<xs:element name="simpleType" type="xs:localSimpleType" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="ref" use="prohibited"/>
<xs:attribute name="form" use="prohibited"/>
<xs:attribute name="use" use="prohibited"/>
<xs:attribute name="name" type="xs:NCName" use="required"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:group name="attrDecls">
<xs:sequence>
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element name="attribute" type="xs:attribute"/>
<xs:element name="attributeGroup" type="xs:attributeGroupRef"/>
</xs:choice>
<xs:element ref="xs:anyAttribute" minOccurs="0"/>
</xs:sequence>
</xs:group>
<xs:element name="anyAttribute" type="xs:wildcard" id="anyAttribute">
<xs:annotation>
<xs:documentation
source="http://www.w3.org/TR/xmlschema-1/#element-anyAttribute"/>
</xs:annotation>
</xs:element>
<xs:group name="complexTypeModel">
<xs:choice>
<xs:element ref="xs:simpleContent"/>
<xs:element ref="xs:complexContent"/>
<xs:sequence>
<xs:annotation>
<xs:documentation>
This branch is short for
&lt;complexContent>
&lt;restriction base="xs:anyType">
...
&lt;/restriction>
&lt;/complexContent></xs:documentation>
</xs:annotation>
<xs:group ref="xs:typeDefParticle" minOccurs="0"/>
<xs:group ref="xs:attrDecls"/>
</xs:sequence>
</xs:choice>
</xs:group>
<xs:complexType name="complexType" abstract="true">
<xs:complexContent>
<xs:extension base="xs:annotated">
<xs:group ref="xs:complexTypeModel"/>
<xs:attribute name="name" type="xs:NCName">
<xs:annotation>
<xs:documentation>
Will be restricted to required or forbidden</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="mixed" type="xs:boolean" default="false"
use="optional">
<xs:annotation>
<xs:documentation>
Not allowed if simpleContent child is chosen.
May be overriden by setting on complexContent child.</xs:documentation>
</xs:annotation>
</xs:attribute>
<xs:attribute name="abstract" type="xs:boolean" default="false"
use="optional"/>
<xs:attribute name="final" type="xs:derivationSet"/>
<xs:attribute name="block" type="xs:derivationSet"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="topLevelComplexType">
<xs:complexContent>
<xs:restriction base="xs:complexType">
<xs:sequence>
<xs:element ref="xs:annotation" minOccurs="0"/>
<xs:group ref="xs:complexTypeModel"/>
</xs:sequence>
<xs:attribute name="name" type="xs:NCName" use="required"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="localComplexType">
<xs:complexContent>
<xs:restriction base="xs:complexType">
<xs:sequence>
<xs:element ref="xs:annotation" minOccurs="0"/>
<xs:group ref="xs:complexTypeModel"/>
</xs:sequence>
<xs:attribute name="name" use="prohibited"/>
<xs:attribute name="abstract" use="prohibited"/>
<xs:attribute name="final" use="prohibited"/>
<xs:attribute name="block" use="prohibited"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="restrictionType">
<xs:complexContent>
<xs:extension base="xs:annotated">
<xs:sequence>
<xs:choice minOccurs="0">
<xs:group ref="xs:typeDefParticle"/>
<xs:group ref="xs:simpleRestrictionModel"/>
</xs:choice>
<xs:group ref="xs:attrDecls"/>
</xs:sequence>
<xs:attribute name="base" type="xs:QName" use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="complexRestrictionType">
<xs:complexContent>
<xs:restriction base="xs:restrictionType">
<xs:sequence>
<xs:element ref="xs:annotation" minOccurs="0"/>
<xs:choice minOccurs="0">
<xs:annotation>
<xs:documentation>This choice is added simply to
make this a valid restriction per the REC</xs:documentation>
</xs:annotation>
<xs:group ref="xs:typeDefParticle"/>
</xs:choice>
<xs:group ref="xs:attrDecls"/>
</xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="extensionType">
<xs:complexContent>
<xs:extension base="xs:annotated">
<xs:sequence>
<xs:group ref="xs:typeDefParticle" minOccurs="0"/>
<xs:group ref="xs:attrDecls"/>
</xs:sequence>
<xs:attribute name="base" type="xs:QName" use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="complexContent" id="complexContent">
<xs:annotation>
<xs:documentation
source="http://www.w3.org/TR/xmlschema-1/#element-complexContent"/>
</xs:annotation>
<xs:complexType>
<xs:complexContent>
<xs:extension base="xs:annotated">
<xs:choice>
<xs:element name="restriction" type="xs:complexRestrictionType"/>
<xs:element name="extension" type="xs:extensionType"/>
</xs:choice>
<xs:attribute name="mixed" type="xs:boolean">
<xs:annotation>
<xs:documentation>
Overrides any setting on complexType parent.</xs:documentation>
</xs:annotation>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
<xs:complexType name="simpleRestrictionType">
<xs:complexContent>
<xs:restriction base="xs:restrictionType">
<xs:sequence>
<xs:element ref="xs:annotation" minOccurs="0"/>
<xs:choice minOccurs="0">
<xs:annotation>
<xs:documentation>This choice is added simply to
make this a valid restriction per the REC</xs:documentation>
</xs:annotation>
<xs:group ref="xs:simpleRestrictionModel"/>
</xs:choice>
<xs:group ref="xs:attrDecls"/>
</xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="simpleExtensionType">
<xs:complexContent>
<xs:restriction base="xs:extensionType">
<xs:sequence>
<xs:annotation>
<xs:documentation>
No typeDefParticle group reference</xs:documentation>
</xs:annotation>
<xs:element ref="xs:annotation" minOccurs="0"/>
<xs:group ref="xs:attrDecls"/>
</xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:element name="simpleContent" id="simpleContent">
<xs:annotation>
<xs:documentation
source="http://www.w3.org/TR/xmlschema-1/#element-simpleContent"/>
</xs:annotation>
<xs:complexType>
<xs:complexContent>
<xs:extension base="xs:annotated">
<xs:choice>
<xs:element name="restriction" type="xs:simpleRestrictionType"/>
<xs:element name="extension" type="xs:simpleExtensionType"/>
</xs:choice>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
<xs:element name="complexType" type="xs:topLevelComplexType" id="complexType">
<xs:annotation>
<xs:documentation
source="http://www.w3.org/TR/xmlschema-1/#element-complexType"/>
</xs:annotation>
</xs:element>
<xs:simpleType name="blockSet">
<xs:annotation>
<xs:documentation>
A utility type, not for public use</xs:documentation>
<xs:documentation>
#all or (possibly empty) subset of {substitution, extension,
restriction}</xs:documentation>
</xs:annotation>
<xs:union>
<xs:simpleType>
<xs:restriction base="xs:token">
<xs:enumeration value="#all"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType>
<xs:list>
<xs:simpleType>
<xs:restriction base="xs:derivationControl">
<xs:enumeration value="extension"/>
<xs:enumeration value="restriction"/>
<xs:enumeration value="substitution"/>
</xs:restriction>
</xs:simpleType>
</xs:list>
</xs:simpleType>
</xs:union>
</xs:simpleType>
<xs:complexType name="element" abstract="true">
<xs:annotation>
<xs:documentation>
The element element can be used either
at the top level to define an element-type binding globally,
or within a content model to either reference a globally-defined
element or type or declare an element-type binding locally.
The ref form is not allowed at the top level.</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="xs:annotated">
<xs:sequence>
<xs:choice minOccurs="0">
<xs:element name="simpleType" type="xs:localSimpleType"/>
<xs:element name="complexType" type="xs:localComplexType"/>
</xs:choice>
<xs:group ref="xs:identityConstraint" minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:attributeGroup ref="xs:defRef"/>
<xs:attribute name="type" type="xs:QName"/>
<xs:attribute name="substitutionGroup" type="xs:QName"/>
<xs:attributeGroup ref="xs:occurs"/>
<xs:attribute name="default" type="xs:string"/>
<xs:attribute name="fixed" type="xs:string"/>
<xs:attribute name="nillable" type="xs:boolean" default="false"
use="optional"/>
<xs:attribute name="abstract" type="xs:boolean" default="false"
use="optional"/>
<xs:attribute name="final" type="xs:derivationSet"/>
<xs:attribute name="block" type="xs:blockSet"/>
<xs:attribute name="form" type="xs:formChoice"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="topLevelElement">
<xs:complexContent>
<xs:restriction base="xs:element">
<xs:sequence>
<xs:element ref="xs:annotation" minOccurs="0"/>
<xs:choice minOccurs="0">
<xs:element name="simpleType" type="xs:localSimpleType"/>
<xs:element name="complexType" type="xs:localComplexType"/>
</xs:choice>
<xs:group ref="xs:identityConstraint" minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="ref" use="prohibited"/>
<xs:attribute name="form" use="prohibited"/>
<xs:attribute name="minOccurs" use="prohibited"/>
<xs:attribute name="maxOccurs" use="prohibited"/>
<xs:attribute name="name" type="xs:NCName" use="required"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="localElement">
<xs:complexContent>
<xs:restriction base="xs:element">
<xs:sequence>
<xs:element ref="xs:annotation" minOccurs="0"/>
<xs:choice minOccurs="0">
<xs:element name="simpleType" type="xs:localSimpleType"/>
<xs:element name="complexType" type="xs:localComplexType"/>
</xs:choice>
<xs:group ref="xs:identityConstraint" minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="substitutionGroup" use="prohibited"/>
<xs:attribute name="final" use="prohibited"/>
<xs:attribute name="abstract" use="prohibited"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:element name="element" type="xs:topLevelElement" id="element">
<xs:annotation>
<xs:documentation
source="http://www.w3.org/TR/xmlschema-1/#element-element"/>
</xs:annotation>
</xs:element>
<xs:complexType name="group" abstract="true">
<xs:annotation>
<xs:documentation>
group type for explicit groups, named top-level groups and
group references</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:extension base="xs:annotated">
<xs:group ref="xs:particle" minOccurs="0" maxOccurs="unbounded"/>
<xs:attributeGroup ref="xs:defRef"/>
<xs:attributeGroup ref="xs:occurs"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="realGroup">
<xs:complexContent>
<xs:restriction base="xs:group">
<xs:sequence>
<xs:element ref="xs:annotation" minOccurs="0"/>
<xs:choice minOccurs="0" maxOccurs="1">
<xs:element ref="xs:all"/>
<xs:element ref="xs:choice"/>
<xs:element ref="xs:sequence"/>
</xs:choice>
</xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="namedGroup">
<xs:complexContent>
<xs:restriction base="xs:realGroup">
<xs:sequence>
<xs:element ref="xs:annotation" minOccurs="0"/>
<xs:choice minOccurs="1" maxOccurs="1">
<xs:element name="all">
<xs:complexType>
<xs:complexContent>
<xs:restriction base="xs:all">
<xs:group ref="xs:allModel"/>
<xs:attribute name="minOccurs" use="prohibited"/>
<xs:attribute name="maxOccurs" use="prohibited"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
</xs:element>
<xs:element name="choice" type="xs:simpleExplicitGroup"/>
<xs:element name="sequence" type="xs:simpleExplicitGroup"/>
</xs:choice>
</xs:sequence>
<xs:attribute name="name" type="xs:NCName" use="required"/>
<xs:attribute name="ref" use="prohibited"/>
<xs:attribute name="minOccurs" use="prohibited"/>
<xs:attribute name="maxOccurs" use="prohibited"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="groupRef">
<xs:complexContent>
<xs:restriction base="xs:realGroup">
<xs:sequence>
<xs:element ref="xs:annotation" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="ref" type="xs:QName" use="required"/>
<xs:attribute name="name" use="prohibited"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="explicitGroup">
<xs:annotation>
<xs:documentation>
group type for the three kinds of group</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:restriction base="xs:group">
<xs:sequence>
<xs:element ref="xs:annotation" minOccurs="0"/>
<xs:group ref="xs:nestedParticle" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="name" type="xs:NCName" use="prohibited"/>
<xs:attribute name="ref" type="xs:QName" use="prohibited"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="simpleExplicitGroup">
<xs:complexContent>
<xs:restriction base="xs:explicitGroup">
<xs:sequence>
<xs:element ref="xs:annotation" minOccurs="0"/>
<xs:group ref="xs:nestedParticle" minOccurs="0" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="minOccurs" use="prohibited"/>
<xs:attribute name="maxOccurs" use="prohibited"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:group name="allModel">
<xs:sequence>
<xs:element ref="xs:annotation" minOccurs="0"/>
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>This choice with min/max is here to
avoid a pblm with the Elt:All/Choice/Seq
Particle derivation constraint</xs:documentation>
</xs:annotation>
<xs:element name="element" type="xs:narrowMaxMin"/>
</xs:choice>
</xs:sequence>
</xs:group>
<xs:complexType name="narrowMaxMin">
<xs:annotation>
<xs:documentation>restricted max/min</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:restriction base="xs:localElement">
<xs:sequence>
<xs:element ref="xs:annotation" minOccurs="0"/>
<xs:choice minOccurs="0">
<xs:element name="simpleType" type="xs:localSimpleType"/>
<xs:element name="complexType" type="xs:localComplexType"/>
</xs:choice>
<xs:group ref="xs:identityConstraint" minOccurs="0"
maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="minOccurs" default="1" use="optional">
<xs:simpleType>
<xs:restriction base="xs:nonNegativeInteger">
<xs:enumeration value="0"/>
<xs:enumeration value="1"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="maxOccurs" default="1" use="optional">
<xs:simpleType>
<xs:restriction base="xs:allNNI">
<xs:enumeration value="0"/>
<xs:enumeration value="1"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="all">
<xs:annotation>
<xs:documentation>
Only elements allowed inside</xs:documentation>
</xs:annotation>
<xs:complexContent>
<xs:restriction base="xs:explicitGroup">
<xs:group ref="xs:allModel"/>
<xs:attribute name="minOccurs" default="1" use="optional">
<xs:simpleType>
<xs:restriction base="xs:nonNegativeInteger">
<xs:enumeration value="0"/>
<xs:enumeration value="1"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:attribute name="maxOccurs" default="1" use="optional">
<xs:simpleType>
<xs:restriction base="xs:allNNI">
<xs:enumeration value="1"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:element name="all" type="xs:all" id="all">
<xs:annotation>
<xs:documentation source="http://www.w3.org/TR/xmlschema-1/#element-all"/>
</xs:annotation>
</xs:element>
<xs:element name="choice" type="xs:explicitGroup" id="choice">
<xs:annotation>
<xs:documentation
source="http://www.w3.org/TR/xmlschema-1/#element-choice"/>
</xs:annotation>
</xs:element>
<xs:element name="sequence" type="xs:explicitGroup" id="sequence">
<xs:annotation>
<xs:documentation
source="http://www.w3.org/TR/xmlschema-1/#element-sequence"/>
</xs:annotation>
</xs:element>
<xs:element name="group" type="xs:namedGroup" id="group">
<xs:annotation>
<xs:documentation source="http://www.w3.org/TR/xmlschema-1/#element-group"/>
</xs:annotation>
</xs:element>
<xs:complexType name="wildcard">
<xs:complexContent>
<xs:extension base="xs:annotated">
<xs:attribute name="namespace" type="xs:namespaceList" default="##any"
use="optional"/>
<xs:attribute name="processContents" default="strict" use="optional">
<xs:simpleType>
<xs:restriction base="xs:NMTOKEN">
<xs:enumeration value="skip"/>
<xs:enumeration value="lax"/>
<xs:enumeration value="strict"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:element name="any" id="any">
<xs:annotation>
<xs:documentation source="http://www.w3.org/TR/xmlschema-1/#element-any"/>
</xs:annotation>
<xs:complexType>
<xs:complexContent>
<xs:extension base="xs:wildcard">
<xs:attributeGroup ref="xs:occurs"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
<xs:annotation>
<xs:documentation>
simple type for the value of the 'namespace' attr of
'any' and 'anyAttribute'</xs:documentation>
</xs:annotation>
<xs:annotation>
<xs:documentation>
Value is
##any - - any non-conflicting WFXML/attribute at all
##other - - any non-conflicting WFXML/attribute from
namespace other than targetNS
##local - - any unqualified non-conflicting WFXML/attribute
one or - - any non-conflicting WFXML/attribute from
more URI the listed namespaces
references
(space separated)
##targetNamespace or ##local may appear in the above list, to
refer to the targetNamespace of the enclosing
schema or an absent targetNamespace respectively</xs:documentation>
</xs:annotation>
<xs:simpleType name="namespaceList">
<xs:annotation>
<xs:documentation>
A utility type, not for public use</xs:documentation>
</xs:annotation>
<xs:union>
<xs:simpleType>
<xs:restriction base="xs:token">
<xs:enumeration value="##any"/>
<xs:enumeration value="##other"/>
</xs:restriction>
</xs:simpleType>
<xs:simpleType>
<xs:list>
<xs:simpleType>
<xs:union memberTypes="xs:anyURI">
<xs:simpleType>
<xs:restriction base="xs:token">
<xs:enumeration value="##targetNamespace"/>
<xs:enumeration value="##local"/>
</xs:restriction>
</xs:simpleType>
</xs:union>
</xs:simpleType>
</xs:list>
</xs:simpleType>
</xs:union>
</xs:simpleType>
<xs:element name="attribute" type="xs:topLevelAttribute" id="attribute">
<xs:annotation>
<xs:documentation
source="http://www.w3.org/TR/xmlschema-1/#element-attribute"/>
</xs:annotation>
</xs:element>
<xs:complexType name="attributeGroup" abstract="true">
<xs:complexContent>
<xs:extension base="xs:annotated">
<xs:group ref="xs:attrDecls"/>
<xs:attributeGroup ref="xs:defRef"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="namedAttributeGroup">
<xs:complexContent>
<xs:restriction base="xs:attributeGroup">
<xs:sequence>
<xs:element ref="xs:annotation" minOccurs="0"/>
<xs:group ref="xs:attrDecls"/>
</xs:sequence>
<xs:attribute name="name" type="xs:NCName" use="required"/>
<xs:attribute name="ref" use="prohibited"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="attributeGroupRef">
<xs:complexContent>
<xs:restriction base="xs:attributeGroup">
<xs:sequence>
<xs:element ref="xs:annotation" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="ref" type="xs:QName" use="required"/>
<xs:attribute name="name" use="prohibited"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:restriction>
</xs:complexContent>
</xs:complexType>
<xs:element name="attributeGroup" type="xs:namedAttributeGroup"
id="attributeGroup">
<xs:annotation>
<xs:documentation
source="http://www.w3.org/TR/xmlschema-1/#element-attributeGroup"/>
</xs:annotation>
</xs:element>
<xs:element name="include" id="include">
<xs:annotation>
<xs:documentation
source="http://www.w3.org/TR/xmlschema-1/#element-include"/>
</xs:annotation>
<xs:complexType>
<xs:complexContent>
<xs:extension base="xs:annotated">
<xs:attribute name="schemaLocation" type="xs:anyURI" use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
<xs:element name="redefine" id="redefine">
<xs:annotation>
<xs:documentation
source="http://www.w3.org/TR/xmlschema-1/#element-redefine"/>
</xs:annotation>
<xs:complexType>
<xs:complexContent>
<xs:extension base="xs:openAttrs">
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element ref="xs:annotation"/>
<xs:group ref="xs:redefinable"/>
</xs:choice>
<xs:attribute name="schemaLocation" type="xs:anyURI" use="required"/>
<xs:attribute name="id" type="xs:ID"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
<xs:element name="import" id="import">
<xs:annotation>
<xs:documentation
source="http://www.w3.org/TR/xmlschema-1/#element-import"/>
</xs:annotation>
<xs:complexType>
<xs:complexContent>
<xs:extension base="xs:annotated">
<xs:attribute name="namespace" type="xs:anyURI"/>
<xs:attribute name="schemaLocation" type="xs:anyURI"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
<xs:element name="selector" id="selector">
<xs:annotation>
<xs:documentation
source="http://www.w3.org/TR/xmlschema-1/#element-selector"/>
</xs:annotation>
<xs:complexType>
<xs:complexContent>
<xs:extension base="xs:annotated">
<xs:attribute name="xpath" use="required">
<xs:simpleType>
<xs:annotation>
<xs:documentation>A subset of XPath expressions for use
in selectors</xs:documentation>
<xs:documentation>A utility type, not for public
use</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:token">
<xs:annotation>
<xs:documentation>The following pattern is intended to allow XPath
expressions per the following EBNF:
Selector ::= Path ( '|' Path )*
Path ::= ('.//')? Step ( '/' Step )*
Step ::= '.' | NameTest
NameTest ::= QName | '*' | NCName ':' '*'
child:: is also allowed
</xs:documentation>
</xs:annotation>
<xs:pattern
value="(\.//)?(((child::)?((\i\c*:)?(\i\c*|\*)))|\.)(/(((child::)?((\i\c*:)?(\i\c*|\*)))|\.))*(\|(\.//)?(((child::)?((\i\c*:)?(\i\c*|\*)))|\.)(/(((child::)?((\i\c*:)?(\i\c*|\*)))|\.))*)*"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
<xs:element name="field" id="field">
<xs:annotation>
<xs:documentation source="http://www.w3.org/TR/xmlschema-1/#element-field"/>
</xs:annotation>
<xs:complexType>
<xs:complexContent>
<xs:extension base="xs:annotated">
<xs:attribute name="xpath" use="required">
<xs:simpleType>
<xs:annotation>
<xs:documentation>A subset of XPath expressions for use
in fields</xs:documentation>
<xs:documentation>A utility type, not for public
use</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:token">
<xs:annotation>
<xs:documentation>The following pattern is intended to allow XPath
expressions per the same EBNF as for selector,
with the following change:
Path ::= ('.//')? ( Step '/' )* ( Step | '@' NameTest )
</xs:documentation>
</xs:annotation>
<xs:pattern
value="(\.//)?((((child::)?((\i\c*:)?(\i\c*|\*)))|\.)/)*((((child::)?((\i\c*:)?(\i\c*|\*)))|\.)|((attribute::|@)((\i\c*:)?(\i\c*|\*))))(\|(\.//)?((((child::)?((\i\c*:)?(\i\c*|\*)))|\.)/)*((((child::)?((\i\c*:)?(\i\c*|\*)))|\.)|((attribute::|@)((\i\c*:)?(\i\c*|\*)))))*"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
<xs:complexType name="keybase">
<xs:complexContent>
<xs:extension base="xs:annotated">
<xs:sequence>
<xs:element ref="xs:selector"/>
<xs:element ref="xs:field" minOccurs="1" maxOccurs="unbounded"/>
</xs:sequence>
<xs:attribute name="name" type="xs:NCName" use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:group name="identityConstraint">
<xs:annotation>
<xs:documentation>The three kinds of identity constraints, all with
type of or derived from 'keybase'.
</xs:documentation>
</xs:annotation>
<xs:choice>
<xs:element ref="xs:unique"/>
<xs:element ref="xs:key"/>
<xs:element ref="xs:keyref"/>
</xs:choice>
</xs:group>
<xs:element name="unique" type="xs:keybase" id="unique">
<xs:annotation>
<xs:documentation
source="http://www.w3.org/TR/xmlschema-1/#element-unique"/>
</xs:annotation>
</xs:element>
<xs:element name="key" type="xs:keybase" id="key">
<xs:annotation>
<xs:documentation source="http://www.w3.org/TR/xmlschema-1/#element-key"/>
</xs:annotation>
</xs:element>
<xs:element name="keyref" id="keyref">
<xs:annotation>
<xs:documentation
source="http://www.w3.org/TR/xmlschema-1/#element-keyref"/>
</xs:annotation>
<xs:complexType>
<xs:complexContent>
<xs:extension base="xs:keybase">
<xs:attribute name="refer" type="xs:QName" use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
<xs:element name="notation" id="notation">
<xs:annotation>
<xs:documentation
source="http://www.w3.org/TR/xmlschema-1/#element-notation"/>
</xs:annotation>
<xs:complexType>
<xs:complexContent>
<xs:extension base="xs:annotated">
<xs:attribute name="name" type="xs:NCName" use="required"/>
<xs:attribute name="public" type="xs:public"/>
<xs:attribute name="system" type="xs:anyURI"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
<xs:simpleType name="public">
<xs:annotation>
<xs:documentation>
A utility type, not for public use</xs:documentation>
<xs:documentation>
A public identifier, per ISO 8879</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:token"/>
</xs:simpleType>
<xs:element name="appinfo" id="appinfo">
<xs:annotation>
<xs:documentation
source="http://www.w3.org/TR/xmlschema-1/#element-appinfo"/>
</xs:annotation>
<xs:complexType mixed="true">
<xs:sequence minOccurs="0" maxOccurs="unbounded">
<xs:any processContents="lax"/>
</xs:sequence>
<xs:attribute name="source" type="xs:anyURI"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
</xs:element>
<xs:element name="documentation" id="documentation">
<xs:annotation>
<xs:documentation
source="http://www.w3.org/TR/xmlschema-1/#element-documentation"/>
</xs:annotation>
<xs:complexType mixed="true">
<xs:sequence minOccurs="0" maxOccurs="unbounded">
<xs:any processContents="lax"/>
</xs:sequence>
<xs:attribute name="source" type="xs:anyURI"/>
<xs:attribute ref="xml:lang"/>
<xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
</xs:element>
<xs:element name="annotation" id="annotation">
<xs:annotation>
<xs:documentation
source="http://www.w3.org/TR/xmlschema-1/#element-annotation"/>
</xs:annotation>
<xs:complexType>
<xs:complexContent>
<xs:extension base="xs:openAttrs">
<xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element ref="xs:appinfo"/>
<xs:element ref="xs:documentation"/>
</xs:choice>
<xs:attribute name="id" type="xs:ID"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
</xs:element>
<xs:annotation>
<xs:documentation>
notations for use within XML Schema schemas</xs:documentation>
</xs:annotation>
<xs:notation name="XMLSchemaStructures" public="structures"
system="http://www.w3.org/2000/08/XMLSchema.xsd"/>
<xs:notation name="XML" public="REC-xml-19980210"
system="http://www.w3.org/TR/1998/REC-xml-19980210"/>
<xs:complexType name="anyType" mixed="true">
<xs:annotation>
<xs:documentation>
Not the real urType, but as close an approximation as we can
get in the XML representation</xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:any minOccurs="0" maxOccurs="unbounded" processContents="lax"/>
</xs:sequence>
<xs:anyAttribute processContents="lax"/>
</xs:complexType>
</xs:schema>
</pre><div class="note"><b>Note: </b>And that is the end of the schema for schema documents.</div></div><div class="div1">
<h2><a id="normative-references" name="normative-references"/>B References (normative)</h2><dl><dt class="label"><a id="ref-xml" name="ref-xml"/>XML 1.0 (Second Edition)</dt><dd> <em>Extensible
Markup Language (XML) 1.0, Second Edition</em>, Tim Bray et al., eds., W3C,
6 October 2000. See
<a href="http://www.w3.org/TR/2000/REC-xml-20001006">http://www.w3.org/TR/2000/REC-xml-20001006</a>
</dd><dt class="label"><a id="ref-xsreq" name="ref-xsreq"/>XML Schema Requirements</dt><dd>
<em>XML Schema Requirements </em>, Ashok Malhotra and Murray Maloney, eds.,
W3C, 15 February 1999. See <a href="http://www.w3.org/TR/1999/NOTE-xml-schema-req-19990215">http://www.w3.org/TR/1999/NOTE-xml-schema-req-19990215</a> </dd><dt class="label"><a id="ref-xsp2" name="ref-xsp2"/>XML Schemas: Datatypes</dt><dd>
<em>XML Schema Part 2: Datatypes</em>, Paul V. Biron and Ashok
Malhotra, eds., W3C, 2 May 2001. See <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html">http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html</a> </dd><dt class="label"><a id="ref-xmlinfo" name="ref-xmlinfo"/>XML-Infoset</dt><dd><em>XML Information Set</em>,
John Cowan and Richard Tobin, eds., W3C, 16 March 2001. See
<a href="http://www.w3.org/TR/2001/WD-xml-infoset-20010316/">http://www.w3.org/TR/2001/WD-xml-infoset-20010316/</a>
</dd><dt class="label"><a id="ref-xml-namespaces" name="ref-xml-namespaces"/>XML-Namespaces</dt><dd>
<em>Namespaces in XML</em>, Tim Bray et al., eds., W3C, 14 January 1999. See
<a href="http://www.w3.org/TR/1999/REC-xml-names-19990114/">http://www.w3.org/TR/1999/REC-xml-names-19990114/</a> </dd><dt class="label"><a id="bib-xpath" name="bib-xpath"/>XPath</dt><dd><em>XML Path Language</em>, James Clark
and Steve DeRose, eds., W3C, 16 November 1999. See <a href="http://www.w3.org/TR/1999/REC-xpath-19991116">http://www.w3.org/TR/1999/REC-xpath-19991116</a></dd><dt class="label"><a id="ref-xpointer" name="ref-xpointer"/>XPointer</dt><dd> <em>XML
Pointer Language (XPointer)</em>, Eve Maler and Steve DeRose, eds., W3C, 8 January 2001. See <a href="http://www.w3.org/TR/2001/WD-xptr-20010108/">http://www.w3.org/TR/2001/WD-xptr-20010108/</a> </dd></dl></div><div class="div1">
<h2><a id="outcomes" name="outcomes"/>C Outcome Tabulations (normative)</h2><p>To facilitate consistent reporting of schema errors and <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a>
failures, this section tabulates and provides unique names for all the
constraints listed in this document. Wherever such constraints have numbered
parts, reports should use the name given below plus the part number, separated
by a period ('.'). Thus for example <code>cos-ct-extends.1.2</code> should be
used to report a violation of the clause <a href="#c-cte">1.2</a> of
<a href="#cos-ct-extends">Derivation Valid (Extension) (§3.4.6)</a>.</p>
<h3><span class="nav"> <a class="nav" href="#PSVI_contributions"><img src="next.jpg" alt="next sub-section"/></a></span><a id="validation_failures" name="validation_failures"/>C.1 Validation Rules</h3><p/><dl><dt>cvc-assess-attr</dt><dd><a href="#cvc-assess-attr">Schema-Validity Assessment (Attribute)</a></dd><dt>cvc-assess-elt</dt><dd><a href="#cvc-assess-elt">Schema-Validity Assessment (Element)</a></dd><dt>cvc-attribute</dt><dd><a href="#cvc-attribute">Attribute Locally Valid</a></dd><dt>cvc-au</dt><dd><a href="#cvc-au">Attribute Locally Valid (Use)</a></dd><dt>cvc-complex-type</dt><dd><a href="#cvc-complex-type">Element Locally Valid (Complex Type)</a></dd><dt>cvc-datatype-valid</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#cvc-datatype-valid">Datatype Valid</a></dd><dt>cvc-elt</dt><dd><a href="#cvc-elt">Element Locally Valid (Element)</a></dd><dt>cvc-enumeration-valid</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#cvc-enumeration-valid">enumeration valid</a></dd><dt>cvc-facet-valid</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#cvc-facet-valid">Facet Valid</a></dd><dt>cvc-fractionDigits-valid</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#cvc-fractionDigits-valid">fractionDigits Valid</a></dd><dt>cvc-id</dt><dd><a href="#cvc-id">Validation Root Valid (ID/IDREF)</a></dd><dt>cvc-identity-constraint</dt><dd><a href="#cvc-identity-constraint">Identity-constraint Satisfied</a></dd><dt>cvc-length-valid</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#cvc-length-valid">Length Valid</a></dd><dt>cvc-maxExclusive-valid</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#cvc-maxExclusive-valid">maxExclusive Valid</a></dd><dt>cvc-maxInclusive-valid</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#cvc-maxInclusive-valid">maxInclusive Valid</a></dd><dt>cvc-maxLength-valid</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#cvc-maxLength-valid">maxLength Valid</a></dd><dt>cvc-minExclusive-valid</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#cvc-minExclusive-valid">minExclusive Valid</a></dd><dt>cvc-minInclusive-valid</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#cvc-minInclusive-valid">minInclusive Valid</a></dd><dt>cvc-minLength-valid</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#cvc-minLength-valid">minLength Valid</a></dd><dt>cvc-model-group</dt><dd><a href="#cvc-model-group">Element Sequence Valid</a></dd><dt>cvc-particle</dt><dd><a href="#cvc-particle">Element Sequence Locally Valid (Particle)</a></dd><dt>cvc-pattern-valid</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#cvc-pattern-valid">pattern valid</a></dd><dt>cvc-resolve-instance</dt><dd><a href="#cvc-resolve-instance">QName resolution (Instance)</a></dd><dt>cvc-simple-type</dt><dd><a href="#cvc-simple-type">String Valid</a></dd><dt>cvc-totalDigits-valid</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#cvc-totalDigits-valid">totalDigits Valid</a></dd><dt>cvc-type</dt><dd><a href="#cvc-type">Element Locally Valid (Type)</a></dd><dt>cvc-wildcard</dt><dd><a href="#cvc-wildcard">Item Valid (Wildcard)</a></dd><dt>cvc-wildcard-namespace</dt><dd><a href="#cvc-wildcard-namespace">Wildcard allows Namespace Name</a></dd></dl>
<h3><span class="nav"><a class="nav" href="#validation_failures"><img src="previous.jpg" alt="previous sub-section"/></a> <a class="nav" href="#outcome-src"><img src="next.jpg" alt="next sub-section"/></a></span><a id="PSVI_contributions" name="PSVI_contributions"/>C.2 Contributions to the post-schema-validation infoset</h3><dl><dt>attribute information item properties</dt><dd><a href="#a-declaration">[attribute declaration]</a>
(<a href="#sic-attr-decl">Attribute Declaration</a>)
<br/><a href="#a-member_type_definition">[member type definition]</a>
(<a href="#sic-attrType">Attribute Validated by Type</a>)
<br/><a href="#a-member_type_definition_anonymous">[member type definition anonymous]</a>
(<a href="#sic-attrType">Attribute Validated by Type</a>)
<br/><a href="#a-member_type_definition_name">[member type definition name]</a>
(<a href="#sic-attrType">Attribute Validated by Type</a>)
<br/><a href="#a-member_type_definition_namespace">[member type definition namespace]</a>
(<a href="#sic-attrType">Attribute Validated by Type</a>)
<br/><a href="#a-schema_default">[schema default]</a>
(<a href="#sic-attrType">Attribute Validated by Type</a>)
<br/><a href="#a-schema_error_code">[schema error code]</a>
(<a href="#sic-attr-error-code">Validation Failure (Attribute)</a>)
<br/><a href="#a-schema_normalized_value">[schema normalized value]</a>
(<a href="#sic-attrType">Attribute Validated by Type</a>)
<br/><a href="#a-schema_specified">[schema specified]</a>
(<a href="#sic-a-outcome">Assessment Outcome (Attribute)</a>)
<br/><a href="#a-type_definition">[type definition]</a>
(<a href="#sic-attrType">Attribute Validated by Type</a>)
<br/><a href="#a-type_definition_anonymous">[type definition anonymous]</a>
(<a href="#sic-attrType">Attribute Validated by Type</a>)
<br/><a href="#a-type_definition_name">[type definition name]</a>
(<a href="#sic-attrType">Attribute Validated by Type</a>)
<br/><a href="#a-type_definition_namespace">[type definition namespace]</a>
(<a href="#sic-attrType">Attribute Validated by Type</a>)
<br/><a href="#a-type_definition_type">[type definition type]</a>
(<a href="#sic-attrType">Attribute Validated by Type</a>)
<br/><a href="#a-validation_attempted">[validation attempted]</a>
(<a href="#sic-a-outcome">Assessment Outcome (Attribute)</a>)
<br/><a href="#a-validation_context">[validation context]</a>
(<a href="#sic-a-outcome">Assessment Outcome (Attribute)</a>)
<br/><a href="#a-validity">[validity]</a>
(<a href="#sic-a-outcome">Assessment Outcome (Attribute)</a>)
<br/></dd><dt>element information item properties</dt><dd><a href="#e-declaration">[element declaration]</a>
(<a href="#sic-elt-decl">Element Declaration</a>)
<br/><a href="#e-ii_table">[ID/IDREF table]</a>
(<a href="#sic-id">ID/IDREF Table</a>)
<br/><a href="#e-id_constraint_table">[identity-constraint table]</a>
(<a href="#sic-key">Identity-constraint Table</a>)
<br/><a href="#e-member_type_definition">[member type definition]</a>
(<a href="#sic-eltType">Element Validated by Type</a>)
<br/><a href="#e-member_type_definition_anonymous">[member type definition anonymous]</a>
(<a href="#sic-eltType">Element Validated by Type</a>)
<br/><a href="#e-member_type_definition_name">[member type definition name]</a>
(<a href="#sic-eltType">Element Validated by Type</a>)
<br/><a href="#e-member_type_definition_namespace">[member type definition namespace]</a>
(<a href="#sic-eltType">Element Validated by Type</a>)
<br/><a href="#e-nil">[nil]</a>
(<a href="#sic-elt-decl">Element Declaration</a>)
<br/><a href="#e-notation">[notation]</a>
(<a href="#sic-notation-used">Validated with Notation</a>)
<br/><a href="#e-notation_public">[notation public]</a>
(<a href="#sic-notation-used">Validated with Notation</a>)
<br/><a href="#e-notation_system">[notation system]</a>
(<a href="#sic-notation-used">Validated with Notation</a>)
<br/><a href="#e-schema_default">[schema default]</a>
(<a href="#sic-eltType">Element Validated by Type</a>)
<br/><a href="#e-schema_error_code">[schema error code]</a>
(<a href="#sic-elt-error-code">Validation Failure (Element)</a>)
<br/><a href="#e-schema_information">[schema information]</a>
(<a href="#sic-schema">Schema Information</a>)
<br/><a href="#e-schema_normalized_value">[schema normalized value]</a>
(<a href="#sic-eltType">Element Validated by Type</a>)
<br/><a href="#e-schema_specified">[schema specified]</a>
(<a href="#sic-eltDefault">Element Default Value</a>)
<br/><a href="#e-type_definition">[type definition]</a>
(<a href="#sic-eltType">Element Validated by Type</a>)
<br/><a href="#e-type_definition_anonymous">[type definition anonymous]</a>
(<a href="#sic-eltType">Element Validated by Type</a>)
<br/><a href="#e-type_definition_name">[type definition name]</a>
(<a href="#sic-eltType">Element Validated by Type</a>)
<br/><a href="#e-type_definition_namespace">[type definition namespace]</a>
(<a href="#sic-eltType">Element Validated by Type</a>)
<br/><a href="#e-type_definition_type">[type definition type]</a>
(<a href="#sic-eltType">Element Validated by Type</a>)
<br/><a href="#e-validation_attempted">[validation attempted]</a>
(<a href="#sic-e-outcome">Assessment Outcome (Element)</a>)
<br/><a href="#e-validation_context">[validation context]</a>
(<a href="#sic-e-outcome">Assessment Outcome (Element)</a>)
<br/><a href="#e-validity">[validity]</a>
(<a href="#sic-e-outcome">Assessment Outcome (Element)</a>)
<br/></dd><dt>ID/IDREF binding information item properties</dt><dd><a href="#iib-binding">[binding]</a>
(<a href="#sic-id">ID/IDREF Table</a>)
<br/><a href="#iib-id">[id]</a>
(<a href="#sic-id">ID/IDREF Table</a>)
<br/></dd><dt>Identity-constraint Binding information item properties</dt><dd><a href="#cb-definition">[definition]</a>
(<a href="#sic-key">Identity-constraint Table</a>)
<br/><a href="#cb-node_table">[node table]</a>
(<a href="#sic-key">Identity-constraint Table</a>)
<br/></dd><dt>namespace schema information information item properties</dt><dd><a href="#nsi-schema_components">[schema components]</a>
(<a href="#sic-schema">Schema Information</a>)
<br/><a href="#nsi-schema_documents">[schema documents]</a>
(<a href="#sic-schema">Schema Information</a>)
<br/><a href="#nsi-schema_namespace">[schema namespace]</a>
(<a href="#sic-schema">Schema Information</a>)
<br/></dd><dt>schema document information item properties</dt><dd><a href="#sd-document">[document]</a>
(<a href="#sic-schema">Schema Information</a>)
<br/><a href="#sd-document_location">[document location]</a>
(<a href="#sic-schema">Schema Information</a>)
<br/></dd></dl>
<h3><span class="nav"><a class="nav" href="#PSVI_contributions"><img src="previous.jpg" alt="previous sub-section"/></a> <a class="nav" href="#outcome-cos"><img src="next.jpg" alt="next sub-section"/></a></span><a id="outcome-src" name="outcome-src"/>C.3 Schema Representation Constraints</h3><p/><dl><dt>schema_reference</dt><dd><a href="#schema_reference">Schema Document Location Strategy</a></dd><dt>src-annotation</dt><dd><a href="#src-annotation">Annotation Definition Representation OK</a></dd><dt>src-attribute</dt><dd><a href="#src-attribute">Attribute Declaration Representation OK</a></dd><dt>src-attribute_group</dt><dd><a href="#src-attribute_group">Attribute Group Definition Representation OK</a></dd><dt>src-ct</dt><dd><a href="#src-ct">Complex Type Definition Representation OK</a></dd><dt>src-element</dt><dd><a href="#src-element">Element Declaration Representation OK</a></dd><dt>src-expredef</dt><dd><a href="#src-expredef">Individual Component Redefinition</a></dd><dt>src-identity-constraint</dt><dd><a href="#src-identity-constraint">Identity-constraint Definition Representation OK</a></dd><dt>src-import</dt><dd><a href="#src-import">Import Constraints and Semantics</a></dd><dt>src-include</dt><dd><a href="#src-include">Inclusion Constraints and Semantics</a></dd><dt>src-list-itemType-or-simpleType</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#src-list-itemType-or-simpleType">itemType attribute or simpleType child</a></dd><dt>src-model_group</dt><dd><a href="#src-model_group">Model Group Representation OK</a></dd><dt>src-model_group_defn</dt><dd><a href="#src-model_group_defn">Model Group Definition Representation OK</a></dd><dt>src-multiple-enumerations</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#src-multiple-enumerations">Multiple enumerations</a></dd><dt>src-multiple-patterns</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#src-multiple-patterns">Multiple patterns</a></dd><dt>src-notation</dt><dd><a href="#src-notation">Notation Definition Representation OK</a></dd><dt>src-qname</dt><dd><a href="#src-qname">QName Interpretation</a></dd><dt>src-redefine</dt><dd><a href="#src-redefine">Redefinition Constraints and Semantics</a></dd><dt>src-resolve</dt><dd><a href="#src-resolve">QName resolution (Schema Document)</a></dd><dt>src-restriction-base-or-simpleType</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#src-restriction-base-or-simpleType">base attribute or simpleType child</a></dd><dt>src-simple-type</dt><dd><a href="#src-simple-type">Simple Type Definition Representation OK</a></dd><dt>src-single-facet-value</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#src-single-facet-value">Single Facet Value</a></dd><dt>src-union-memberTypes-or-simpleTypes</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#src-union-memberTypes-or-simpleTypes">memberTypes attribute or simpleType children</a></dd><dt>src-wildcard</dt><dd><a href="#src-wildcard">Wildcard Representation OK</a></dd></dl>
<h3><span class="nav"><a class="nav" href="#outcome-src"><img src="previous.jpg" alt="previous sub-section"/></a> </span><a id="outcome-cos" name="outcome-cos"/>C.4 Schema Component Constraints</h3><dl><dt>a-props-correct</dt><dd><a href="#a-props-correct">Attribute Declaration Properties Correct</a></dd><dt>ag-props-correct</dt><dd><a href="#ag-props-correct">Attribute Group Definition Properties Correct</a></dd><dt>an-props-correct</dt><dd><a href="#an-props-correct">Annotation Correct</a></dd><dt>au-props-correct</dt><dd><a href="#au-props-correct">Attribute Use Correct</a></dd><dt>c-fields-xpaths</dt><dd><a href="#c-fields-xpaths">Fields Value OK</a></dd><dt>c-props-correct</dt><dd><a href="#c-props-correct">Identity-constraint Definition Properties Correct</a></dd><dt>c-selector-xpath</dt><dd><a href="#c-selector-xpath">Selector Value OK</a></dd><dt>cos-all-limited</dt><dd><a href="#cos-all-limited">All Group Limited</a></dd><dt>cos-applicable-facets</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#cos-applicable-facets">applicable facets</a></dd><dt>cos-aw-intersect</dt><dd><a href="#cos-aw-intersect">Attribute Wildcard Intersection</a></dd><dt>cos-aw-union</dt><dd><a href="#cos-aw-union">Attribute Wildcard Union</a></dd><dt>cos-choice-range</dt><dd><a href="#cos-choice-range">Effective Total Range (choice)</a></dd><dt>cos-ct-derived-ok</dt><dd><a href="#cos-ct-derived-ok">Type Derivation OK (Complex)</a></dd><dt>cos-ct-extends</dt><dd><a href="#cos-ct-extends">Derivation Valid (Extension)</a></dd><dt>cos-element-consistent</dt><dd><a href="#cos-element-consistent">Element Declarations Consistent</a></dd><dt>cos-equiv-class</dt><dd><a href="#cos-equiv-class">Substitution Group</a></dd><dt>cos-equiv-derived-ok-rec</dt><dd><a href="#cos-equiv-derived-ok-rec">Substitution Group OK (Transitive)</a></dd><dt>cos-group-emptiable</dt><dd><a href="#cos-group-emptiable">Particle Emptiable</a></dd><dt>cos-list-of-atomic</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#cos-list-of-atomic">list of atomic</a></dd><dt>cos-no-circular-unions</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#cos-no-circular-unions">no circular unions</a></dd><dt>cos-nonambig</dt><dd><a href="#cos-nonambig">Unique Particle Attribution</a></dd><dt>cos-ns-subset</dt><dd><a href="#cos-ns-subset">Wildcard Subset</a></dd><dt>cos-particle-extend</dt><dd><a href="#cos-particle-extend">Particle Valid (Extension)</a></dd><dt>cos-particle-restrict</dt><dd><a href="#cos-particle-restrict">Particle Valid (Restriction)</a></dd><dt>cos-seq-range</dt><dd><a href="#cos-seq-range">Effective Total Range (all and sequence)</a></dd><dt>cos-st-derived-ok</dt><dd><a href="#cos-st-derived-ok">Type Derivation OK (Simple)</a></dd><dt>cos-st-restricts</dt><dd><a href="#cos-st-restricts">Derivation Valid (Restriction, Simple)</a></dd><dt>cos-valid-default</dt><dd><a href="#cos-valid-default">Element Default Valid (Immediate)</a></dd><dt>ct-props-correct</dt><dd><a href="#ct-props-correct">Complex Type Definition Properties Correct</a></dd><dt>derivation-ok-restriction</dt><dd><a href="#derivation-ok-restriction">Derivation Valid (Restriction, Complex)</a></dd><dt>e-props-correct</dt><dd><a href="#e-props-correct">Element Declaration Properties Correct</a></dd><dt>enumeration-required-notation</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#enumeration-required-notation">enumeration facet value required for NOTATION</a></dd><dt>enumeration-valid-restriction</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#enumeration-valid-restriction">enumeration valid restriction</a></dd><dt>fractionDigits-totalDigits</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#fractionDigits-totalDigits">fractionDigits less than or equal to totalDigits</a></dd><dt>fractionDigits-valid-restriction</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#fractionDigits-valid-restriction">fractionDigits valid restriction</a></dd><dt>length-minLength-maxLength</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#length-minLength-maxLength">length and minLength or maxLength</a></dd><dt>length-valid-restriction</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#length-valid-restriction">length valid restriction</a></dd><dt>maxExclusive-valid-restriction</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#maxExclusive-valid-restriction">maxExclusive valid restriction</a></dd><dt>maxInclusive-maxExclusive</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#maxInclusive-maxExclusive">maxInclusive and maxExclusive</a></dd><dt>maxInclusive-valid-restriction</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#maxInclusive-valid-restriction">maxInclusive valid restriction</a></dd><dt>maxLength-valid-restriction</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#maxLength-valid-restriction">maxLength valid restriction</a></dd><dt>mg-props-correct</dt><dd><a href="#mg-props-correct">Model Group Correct</a></dd><dt>mgd-props-correct</dt><dd><a href="#mgd-props-correct">Model Group Definition Properties Correct</a></dd><dt>minExclusive-less-than-equal-to-maxExclusive</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#minExclusive-less-than-equal-to-maxExclusive">minExclusive <= maxExclusive</a></dd><dt>minExclusive-less-than-maxInclusive</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#minExclusive-less-than-maxInclusive">minExclusive < maxInclusive</a></dd><dt>minExclusive-valid-restriction</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#minExclusive-valid-restriction">minExclusive valid restriction</a></dd><dt>minInclusive-less-than-equal-to-maxInclusive</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#minInclusive-less-than-equal-to-maxInclusive">minInclusive <= maxInclusive</a></dd><dt>minInclusive-less-than-maxExclusive</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#minInclusive-less-than-maxExclusive">minInclusive < maxExclusive</a></dd><dt>minInclusive-minExclusive</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#minInclusive-minExclusive">minInclusive and minExclusive</a></dd><dt>minInclusive-valid-restriction</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#minInclusive-valid-restriction">minInclusive valid restriction</a></dd><dt>minLength-less-than-equal-to-maxLength</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#minLength-less-than-equal-to-maxLength">minLength <= maxLength</a></dd><dt>minLength-valid-restriction</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#minLength-valid-restriction">minLength valid restriction</a></dd><dt>n-props-correct</dt><dd><a href="#n-props-correct">Notation Declaration Correct</a></dd><dt>no-xmlns</dt><dd><a href="#no-xmlns">xmlns Not Allowed</a></dd><dt>no-xsi</dt><dd><a href="#no-xsi">xsi: Not Allowed</a></dd><dt>p-props-correct</dt><dd><a href="#p-props-correct">Particle Correct</a></dd><dt>range-ok</dt><dd><a href="#range-ok">Occurrence Range OK</a></dd><dt>rcase-MapAndSum</dt><dd><a href="#rcase-MapAndSum">Particle Derivation OK (Sequence:Choice -- MapAndSum)</a></dd><dt>rcase-NameAndTypeOK</dt><dd><a href="#rcase-NameAndTypeOK">Particle Restriction OK (Elt:Elt -- NameAndTypeOK)</a></dd><dt>rcase-NSCompat</dt><dd><a href="#rcase-NSCompat">Particle Derivation OK (Elt:Any -- NSCompat)</a></dd><dt>rcase-NSRecurseCheckCardinality</dt><dd><a href="#rcase-NSRecurseCheckCardinality">Particle Derivation OK (All/Choice/Sequence:Any -- NSRecurseCheckCardinality)</a></dd><dt>rcase-NSSubset</dt><dd><a href="#rcase-NSSubset">Particle Derivation OK (Any:Any -- NSSubset)</a></dd><dt>rcase-Recurse</dt><dd><a href="#rcase-Recurse">Particle Derivation OK (All:All,Sequence:Sequence -- Recurse)</a></dd><dt>rcase-RecurseAsIfGroup</dt><dd><a href="#rcase-RecurseAsIfGroup">Particle Derivation OK (Elt:All/Choice/Sequence -- RecurseAsIfGroup)</a></dd><dt>rcase-RecurseLax</dt><dd><a href="#rcase-RecurseLax">Particle Derivation OK (Choice:Choice -- RecurseLax)</a></dd><dt>rcase-RecurseUnordered</dt><dd><a href="#rcase-RecurseUnordered">Particle Derivation OK (Sequence:All -- RecurseUnordered)</a></dd><dt>sch-props-correct</dt><dd><a href="#sch-props-correct">Schema Properties Correct</a></dd><dt>st-props-correct</dt><dd><a href="#st-props-correct">Simple Type Definition Properties Correct</a></dd><dt>st-restrict-facets</dt><dd><a href="#st-restrict-facets">Simple Type Restriction (Facets)</a></dd><dt>totalDigits-valid-restriction</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#totalDigits-valid-restriction">totalDigits valid restriction</a></dd><dt>w-props-correct</dt><dd><a href="#w-props-correct">Wildcard Properties Correct</a></dd><dt>whiteSpace-valid-restriction</dt><dd><a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#whiteSpace-valid-restriction">whiteSpace valid restriction</a></dd></dl></div><div class="div1">
<h2><a id="infoset" name="infoset"/>D Required Information Set Items and Properties (normative)</h2><p>This specification requires as a precondition for <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> an information set as defined in <a href="#ref-xmlinfo">[XML-Infoset]</a> which supports at least the following information items and properties:</p><dl><dt class="label">Attribute Information Item</dt><dd><a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[local name]</a>, <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[namespace name]</a>,
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[normalized value]</a></dd><dt class="label">Character Information Item</dt><dd><a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.character">[character code]</a></dd><dt class="label">Element Information Item</dt><dd><a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[local name]</a>, <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[namespace name]</a>,
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>, <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a>, <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[in-scope namespaces]</a> or
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[namespace attributes]</a></dd><dt class="label">Namespace Information Item</dt><dd><a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.namespace">[prefix]</a>, <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.namespace">[namespace name]</a></dd></dl><p>In addition, infosets should support the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.document">[unparsedEntities]</a> property of the Document Information Item. Failure to do so will mean all items of type <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ENTITY">ENTITY</a> or <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#ENTITIES">ENTITIES</a> will fail to <a class="termref" href="#key-vn"><span class="arrow">·</span>validate<span class="arrow">·</span></a>.</p><p>This specification does not require any destructive alterations to the input
information set: all the information set contributions specified herein are additive.</p><p>This appendix is intended to satisfy the requirements for <a href="http://www.w3.org/TR/2001/WD-xml-infoset-20010316/#conformance">Conformance</a> to the <a href="#ref-xmlinfo">[XML-Infoset]</a> specification.</p></div><div class="div1">
<h2><a id="component-diagram" name="component-diagram"/>E Schema Components Diagram (non-normative)</h2><img border="0" usemap="#compImage" alt="Diagram of schema components" src="components.gif"/><map id="compImage" name="compImage"><area title="Notation Declaration Schema Component" href="#Notation_Declaration_details" coords="13,1,163,66" alt="Notation Declaration Schema Component" shape="rect"/><area title="Schema Component" href="#Schema_details" coords="297,1,367,112" alt="Schema Component" shape="rect"/><area title="Element Declaration Schema Component" href="#Element_Declaration_details" coords="48,147,252,304" alt="Element Declaration Schema Component" shape="rect"/><area title="Identity Constraint Definition Schema Component" href="#Identity-constraint_Definition_details" coords="369,163,562,263" alt="Identity Constraint Definition Schema Component" shape="rect"/><area title="Model Group Definition Schema Component" href="#Model_Group_Definition_details" coords="445,287,609,333" alt="Model Group Definition Schema Component" shape="rect"/><area title="Simple Type Definition Schema Component" href="#Simple_Type_Definition_details" coords="13,439,176,521" alt="Simple Type Definition Schema Component" shape="rect"/><area title="Complex Type Definition Schema Component" href="#Complex_Type_Definition_details" coords="282,419,457,521" alt="Complex Type Definition Schema Component" shape="rect"/><area title="Particle Schema Component" href="#Particle_details" coords="480,457,585,521" alt="Particle Schema Component" shape="rect"/><area title="Model Group Schema Component" href="#Model_Group_details" coords="518,603,620,649" alt="Model Group Schema Component" shape="rect"/><area title="Attribute Use Schema Component" href="#AU_details" coords="224,690,352,754" alt="Attribute Use Schema Component" shape="rect"/><area title="Wildcard Schema Component" href="#Wildcard_details" coords="387,690,545,754" alt="Wildcard Schema Component" shape="rect"/><area title="Attribute Declaration Schema Component" href="#Attribute_Declaration_details" coords="13,786,165,848" alt="Attribute Declaration Schema Component" shape="rect"/><area title="Attribute Group Definition Schema Component" href="#Attribute_Group_Definition_details" coords="431,801,609,848" alt="Attribute Group Definition Schema Component" shape="rect"/><area alt="Schema Components" nohref="nohref" shape="default"/></map></div><div class="div1">
<h2><a id="normative-glossary" name="normative-glossary"/>F Glossary (non-normative)</h2><p>The listing below is for the benefit of readers of a printed version of this
document: it collects together all the definitions which appear in the
document above.</p><dl><dt><a href="#key-null">absent</a></dt><dd>Throughout this specification, the
term <b>absent</b> is used as a distinguished property value denoting absence</dd><dt><a href="#key-vv">actual value</a></dt><dd>The
phrase <b>actual value</b> is used to refer to the member of the value space of the
simple type definition associated with an attribute information item which corresponds to
its <a class="termref" href="#key-nv"><span class="arrow">·</span>normalized value<span class="arrow">·</span></a></dd><dt><a href="#key-va">assessment</a></dt><dd> the word <b>assessment</b> is used to refer
to the overall process of
local validation, schema-validity assessment and infoset augmentation</dd><dt><a href="#key-baseTypeDefinition">base type definition</a></dt><dd>A type definition used as the
basis for an <a class="termref" href="#key-typeExtension"><span class="arrow">·</span>extension<span class="arrow">·</span></a> or
<a class="termref" href="#key-typeRestriction"><span class="arrow">·</span>restriction<span class="arrow">·</span></a> is known as
the <b>base type definition</b> of that definition</dd><dt><a href="#key-compName">component name</a></dt><dd>Declarations and
definitions may have and be identified by <b>name</b>s, which are NCNames as defined by <a href="#ref-xml-namespaces">[XML-Namespaces]</a></dd><dt><a href="#key-interchange">conformance to the XML Representation of Schemas</a></dt><dd><a class="termref" href="#key-minimallyConforming"><span class="arrow">·</span>Minimally conforming<span class="arrow">·</span></a> processors which accept
schemas represented in the form of XML documents as described in <a href="#layer2">Layer 2: Schema Documents, Namespaces and Composition (§4.2)</a> are
additionally said to provide <b>conformance to the XML Representation of Schemas</b>.
</dd><dt><a href="#key-contentModel">content model</a></dt><dd>A particle can
be used in a complex type definition to constrain the <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a>
of the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> of an element information item; such a particle is called
a <b>content model</b></dd><dt><a href="#key-dd">context-determined declaration</a></dt><dd>During <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a>, associations
between element and attribute information items among the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a>
and <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[attributes]</a> on the one hand, and element and attribute
declarations on the other, are established as a side-effect. Such
declarations are called the <b>context-determined declarations</b></dd><dt><a href="#key-declaration">declaration</a></dt><dd><b>declaration</b> components are associated by
(qualified) name to information items being <a class="termref" href="#key-vn"><span class="arrow">·</span>validated<span class="arrow">·</span></a></dd><dt><a href="#key-vde">declared entity name</a></dt><dd>A string is a <b>declared entity name</b> if it is equal to the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.entity.unparsed">[name]</a> of some unparsed entity
information item in the value of the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.document">[unparsedEntities]</a> property of the document information item
at the root of the infoset containing the element or attribute information item
whose <a class="termref" href="#key-nv"><span class="arrow">·</span>normalized value<span class="arrow">·</span></a> the string is.</dd><dt><a href="#key-definition">definition</a></dt><dd><b>definition</b> components define
internal schema components that can be used in other schema components</dd><dt><a href="#key-equivalenceClass">element substitution group</a></dt><dd>Through
the new mechanism of <b>element substitution groups</b>, XML Schemas provides a more powerful model supporting substitution of one named element for another</dd><dt><a href="#key-typeExtension">extension</a></dt><dd>A complex type definition
which allows element or attribute content in addition to that allowed by
another specified type
definition is said to be an <b>extension</b></dd><dt><a href="#key-ct-final">final</a></dt><dd>the complex type is said to be
<b>final</b>, because no
further derivations are possible</dd><dt><a href="#key-fullyConforming">fully conforming</a></dt><dd> <b>Fully conforming</b>
processors are network-enabled processors which are not only both <a class="termref" href="#key-minimallyConforming"><span class="arrow">·</span>minimally conforming<span class="arrow">·</span></a> and <a class="termref" href="#key-interchange"><span class="arrow">·</span>in conformance to the XML Representation of Schemas<span class="arrow">·</span></a>, but which additionally must be capable of accessing
schema documents from the World Wide Web according to <a href="#web-representation">Representation of Schemas on the World Wide Web (§2.7)</a> and <a href="#schema-loc">How schema definitions are located on the Web (§4.3.2)</a>.
</dd><dt><a href="#key-impl-cont">implicitly contains</a></dt><dd>A list
of particles <b>implicitly contains</b> an element declaration if a
member of the list contains that
element declaration in its <a class="termref" href="#key-eq"><span class="arrow">·</span>substitution group<span class="arrow">·</span></a></dd><dt><a href="#key-iv">initial value</a></dt><dd>the
<b>initial value</b> of some
attribute information item is the value of the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">[normalized
value]</a> property of that item. Similarly, the <b>initial value</b> of an element information item is the string composed of, in order, the
<a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.character">[character code]</a> of each character information item in the <a class="xpropref" href="http://www.w3.org/TR/xml-infoset/#infoitem.element">[children]</a> of that
element information item</dd><dt><a href="#key-iso">item isomorphic to a component</a></dt><dd> by an <b>item isomorphic</b> to a component is meant an information item whose type is equivalent to the component's, with one property per property of the component, with the same name, and value either the same atomic value, or an information item corresponding in the same way to its component value, recursively, as necessary</dd><dt><a href="#key-lva">laxly assessed</a></dt><dd>an element information item's
schema validity may be <b>laxly assessed</b> if its <a class="termref" href="#key-dd"><span class="arrow">·</span>context-determined declaration<span class="arrow">·</span></a> is not <i>skip</i> by <a class="termref" href="#key-vn"><span class="arrow">·</span>validating<span class="arrow">·</span></a> with respect to the <a class="termref" href="#ur-type-itself"><span class="arrow">·</span>ur-type definition<span class="arrow">·</span></a> as per <a href="#cvc-type">Element Locally Valid (Type) (§3.3.4)</a></dd><dt><a href="#key-minimallyConforming">minimally conforming</a></dt><dd><b>Minimally conforming</b> processors must completely and
correctly implement the <a class="termref" href="#gloss-cos"><span class="arrow">·</span>Schema Component
Constraints<span class="arrow">·</span></a>, <a class="termref" href="#gloss-cvc"><span class="arrow">·</span>Validation Rules<span class="arrow">·</span></a>,
and <a class="termref" href="#gloss-sic"><span class="arrow">·</span>Schema Information
Set Contributions<span class="arrow">·</span></a> contained in this specification</dd><dt><a href="#gloss-NCName">NCName</a></dt><dd>An <b>NCName</b> is a name
with no colon, as defined in <a href="#ref-xml-namespaces">[XML-Namespaces]</a>. When used in connection with the XML
representation of schema components in this specification, this refers to the
simple type <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#NCName">NCName</a> as defined in <a href="#ref-xsp2">[XML Schemas: Datatypes]</a></dd><dt><a href="#key-nv">normalized value</a></dt><dd>The
<b>normalized value</b> of an element or
attribute information item is an <a class="termref" href="#key-iv"><span class="arrow">·</span>initial value<span class="arrow">·</span></a> whose white space, if any, has been
normalized according to the value of the <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#rf-whiteSpace">whiteSpace facet</a> of the
simple type definition used in its <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a>:
</dd><dt><a href="#key-partition">partition</a></dt><dd>Define a
<b>partition</b> of a sequence as a sequence of sub-sequences, some or
all of which may be empty, such that concatenating all the sub-sequences yields
the original sequence</dd><dt><a href="#key-psvi">post-schema-validation infoset</a></dt><dd>We refer to the augmented infoset which results from conformant processing as defined in this specification as the <b>post-schema-validation infoset</b>, or PSVI</dd><dt><a href="#gloss-QName">QName</a></dt><dd>A <b>QName</b> is a name
with an optional namespace qualification, as defined in <a href="#ref-xml-namespaces">[XML-Namespaces]</a>. When used in connection with the XML
representation of schema components or references to them, this refers to the
simple type <a href="http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/datatypes.html#QName">QName</a> as defined in <a href="#ref-xsp2">[XML Schemas: Datatypes]</a></dd><dt><a href="#key-resolve">resolve</a></dt><dd>Whenever the word <b>resolve</b> in any form is used in this
chapter in connection with a <a class="termref" href="#gloss-QName"><span class="arrow">·</span>QName<span class="arrow">·</span></a> in a
schema document, the
following definition <a href="#src-resolve">QName resolution (Schema Document) (§3.15.3)</a> should be understood</dd><dt><a href="#key-typeRestriction">restriction</a></dt><dd>A type
definition whose
declarations or facets are in a one-to-one relation with those of another
specified type
definition, with each in turn restricting the possibilities of the one it
corresponds to, is said to be a <b>restriction</b></dd><dt><a href="#key-component">schema component</a></dt><dd> <b>Schema component</b> is the generic term for the building blocks that comprise the abstract data model of the schema.
</dd><dt><a href="#gloss-cos">Schema Component Constraint</a></dt><dd>Constraints on the schema components themselves, i.e.
conditions components must satisfy to be components at all. Located in the
sixth sub-section of the per-component sections of <a href="#components">Schema Component Details (§3)</a>
and tabulated in <a href="#outcome-cos">Schema Component Constraints (§C.4)</a></dd><dt><a href="#key-schemaDoc">schema document</a></dt><dd>A document in
this form (i.e. a <a class="eltref" href="#element-schema"><schema></a> element information item) is a <b>schema document</b></dd><dt><a href="#gloss-sic">Schema Information Set Contribution</a></dt><dd>Augmentations to <a class="termref" href="#key-psvi"><span class="arrow">·</span>post-schema-validation infoset<span class="arrow">·</span></a>s
expressed by schema components, which follow
as a consequence of <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> and/or <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a>.
Located in the
fifth sub-section of the per-component sections of <a href="#components">Schema Component Details (§3)</a>
and tabulated in <a href="#PSVI_contributions">Contributions to the post-schema-validation infoset (§C.2)</a></dd><dt><a href="#gloss-src">Schema Representation Constraint</a></dt><dd>Constraints on the
representation of schema components in XML beyond those which are expressed
in <a href="#normative-schemaSchema">Schema for Schemas (normative) (§A)</a>. Located in the
third sub-section of the per-component sections of <a href="#components">Schema Component Details (§3)</a>
and tabulated in <a href="#outcome-src">Schema Representation Constraints (§C.3)</a></dd><dt><a href="#key-simpleUrType">simple ur-type definition</a></dt><dd>the <b>simple
ur-type definition</b>, a special restriction of the
<a class="termref" href="#key-urType"><span class="arrow">·</span>ur-type
definition<span class="arrow">·</span></a>, whose name is <b>anySimpleType</b> in the XML Schema namespace</dd><dt><a href="#key-eq">substitution group</a></dt><dd>Every element
declaration (call this <b>HEAD</b>)
in the <a class="propref" href="#element_declarations">{element declarations}</a> of a schema defines a
<b>substitution group</b>, a subset of those <a class="propref" href="#element_declarations">{element declarations}</a>, as follows:</dd><dt><a href="#key-symbolSpace">symbol space</a></dt><dd>this specification introduces the term
<b>symbol space</b> to denote a
collection of names, each of which is unique with respect to the others</dd><dt><a href="#key-targetNS">target namespace</a></dt><dd>Several kinds
of component have a <b>target namespace</b>, which is either
<a class="termref" href="#key-null"><span class="arrow">·</span>absent<span class="arrow">·</span></a> or a namespace name, also as
defined by <a href="#ref-xml-namespaces">[XML-Namespaces]</a></dd><dt><a href="#key-typeDefn">type definition</a></dt><dd>This specification uses
the phrase <b>type definition</b> in cases where no distinction
need be made between simple and complex types</dd><dt><a href="#key-typeDefinitionHierarchy">Type Definition Hierarchy</a></dt><dd>Except for a distinguished <a class="termref" href="#key-urType"><span class="arrow">·</span>ur-type definition<span class="arrow">·</span></a>, every <a class="termref" href="#key-typeDefn"><span class="arrow">·</span>type definition<span class="arrow">·</span></a> is, by construction, either a
<a class="termref" href="#key-typeRestriction"><span class="arrow">·</span>restriction<span class="arrow">·</span></a> or an <a class="termref" href="#key-typeExtension"><span class="arrow">·</span>extension<span class="arrow">·</span></a> of some other type definition. The graph of these relationships forms a tree known as the <b>Type Definition Hierarchy</b></dd><dt><a href="#key-urType">ur-type definition</a></dt><dd>A distinguished complex
type definition, the <b>ur-type
definition</b>, whose
name is <i>anyType</i> in the XML Schema namespace, is present in each <a class="termref" href="#key-schema"><span class="arrow">·</span>XML Schema<span class="arrow">·</span></a>, serving as the root of the type
definition hierarchy for that schema</dd><dt><a href="#key-vn">valid</a></dt><dd>the
word <b>valid</b> and its derivatives are used to refer to
clause <a href="#c-lsv">1</a> above, the determination of local
schema-validity</dd><dt><a href="#cd-ct-extension">valid extension</a></dt><dd>If this
constraint <a href="#cos-ct-extends">Derivation Valid (Extension) (§3.4.6)</a> holds of a complex type definition, it is a <b>valid
extension</b> of its <a class="propref" href="#ct-base_type_definition">{base type definition}</a></dd><dt><a href="#cd-ct-restriction">valid restriction</a></dt><dd>If this
constraint <a href="#derivation-ok-restriction">Derivation Valid (Restriction, Complex) (§3.4.6)</a> holds of a complex type definition, it is a <b>valid
restriction</b> of its <a class="propref" href="#ct-base_type_definition">{base type definition}</a></dd><dt><a href="#cd-st-restriction">valid restriction</a></dt><dd>If this
constraint <a href="#cos-st-restricts">Derivation Valid (Restriction, Simple) (§3.14.6)</a> holds of a simple type definition, it is a <b>valid
restriction</b> of its <a class="termref" href="#st-base_type_definition"><span class="arrow">·</span>base type definition<span class="arrow">·</span></a></dd><dt><a href="#key-vr">validation root</a></dt><dd>This item, that is the element information item at which <a class="termref" href="#key-va"><span class="arrow">·</span>assessment<span class="arrow">·</span></a> began, is called the <b>validation root</b></dd><dt><a href="#gloss-cvc">Validation Rules</a></dt><dd>Contributions to <a class="termref" href="#key-vn"><span class="arrow">·</span>validation<span class="arrow">·</span></a> associated
with schema components. Located in the
fourth sub-section of the per-component sections of <a href="#components">Schema Component Details (§3)</a>
and tabulated in <a href="#validation_failures">Validation Rules (§C.1)</a></dd><dt><a href="#key-schema">XML Schema</a></dt><dd>
An <b>XML Schema</b> is a
set of <a class="termref" href="#key-component"><span class="arrow">·</span>schema components<span class="arrow">·</span></a></dd></dl></div><div class="div1">
<h2><a id="nonnormative-schemaDTD" name="nonnormative-schemaDTD"/>G DTD for Schemas (non-normative)</h2><p>The DTD for schema documents is given below. Note there is <em>no</em>
implication here that <code>schema</code> must be the root element of a
document.</p><p>Although this DTD is non-normative, any XML document which is
not valid per this DTD, given redefinitions in its internal subset of the
'p' and 's' parameter entities below appropriate to its namespace
declaration of the XML Schema namespace, is almost certainly not
a valid schema document, with the exception of documents with multiple namespace
prefixes for the XML Schema namespace itself. Accordingly
authoring XML Schema documents using this DTD and DTD-based authoring tools, and
specifying it as the DOCTYPE of documents intended to be XML Schema
documents and validating them with a validating XML parser, are
sensible development strategies which users are encouraged to adopt
until XML Schema-based authoring tools and validators are more widely available.</p><pre><!-- DTD for XML Schemas: Part 1: Structures
Public Identifier: "-//W3C//DTD XMLSCHEMA 200102//EN"
Official Location: http://www.w3.org/2001/XMLSchema.dtd -->
<!-- Id: structures.dtd,v 1.1 2003/08/28 13:30:52 ht Exp -->
<!-- With the exception of cases with multiple namespace
prefixes for the XML Schema namespace, any XML document which is
not valid per this DTD given redefinitions in its internal subset of the
'p' and 's' parameter entities below appropriate to its namespace
declaration of the XML Schema namespace is almost certainly not
a valid schema. -->
<!-- The simpleType element and its constituent parts
are defined in XML Schema: Part 2: Datatypes -->
<!ENTITY % xs-datatypes PUBLIC 'datatypes' 'datatypes.dtd' >
<!ENTITY % p 'xs:'> <!-- can be overriden in the internal subset of a
schema document to establish a different
namespace prefix -->
<!ENTITY % s ':xs'> <!-- if %p is defined (e.g. as foo:) then you must
also define %s as the suffix for the appropriate
namespace declaration (e.g. :foo) -->
<!ENTITY % nds 'xmlns%s;'>
<!-- Define all the element names, with optional prefix -->
<!ENTITY % schema "%p;schema">
<!ENTITY % complexType "%p;complexType">
<!ENTITY % complexContent "%p;complexContent">
<!ENTITY % simpleContent "%p;simpleContent">
<!ENTITY % extension "%p;extension">
<!ENTITY % element "%p;element">
<!ENTITY % unique "%p;unique">
<!ENTITY % key "%p;key">
<!ENTITY % keyref "%p;keyref">
<!ENTITY % selector "%p;selector">
<!ENTITY % field "%p;field">
<!ENTITY % group "%p;group">
<!ENTITY % all "%p;all">
<!ENTITY % choice "%p;choice">
<!ENTITY % sequence "%p;sequence">
<!ENTITY % any "%p;any">
<!ENTITY % anyAttribute "%p;anyAttribute">
<!ENTITY % attribute "%p;attribute">
<!ENTITY % attributeGroup "%p;attributeGroup">
<!ENTITY % include "%p;include">
<!ENTITY % import "%p;import">
<!ENTITY % redefine "%p;redefine">
<!ENTITY % notation "%p;notation">
<!-- annotation elements -->
<!ENTITY % annotation "%p;annotation">
<!ENTITY % appinfo "%p;appinfo">
<!ENTITY % documentation "%p;documentation">
<!-- Customisation entities for the ATTLIST of each element type.
Define one of these if your schema takes advantage of the
anyAttribute='##other' in the schema for schemas -->
<!ENTITY % schemaAttrs ''>
<!ENTITY % complexTypeAttrs ''>
<!ENTITY % complexContentAttrs ''>
<!ENTITY % simpleContentAttrs ''>
<!ENTITY % extensionAttrs ''>
<!ENTITY % elementAttrs ''>
<!ENTITY % groupAttrs ''>
<!ENTITY % allAttrs ''>
<!ENTITY % choiceAttrs ''>
<!ENTITY % sequenceAttrs ''>
<!ENTITY % anyAttrs ''>
<!ENTITY % anyAttributeAttrs ''>
<!ENTITY % attributeAttrs ''>
<!ENTITY % attributeGroupAttrs ''>
<!ENTITY % uniqueAttrs ''>
<!ENTITY % keyAttrs ''>
<!ENTITY % keyrefAttrs ''>
<!ENTITY % selectorAttrs ''>
<!ENTITY % fieldAttrs ''>
<!ENTITY % includeAttrs ''>
<!ENTITY % importAttrs ''>
<!ENTITY % redefineAttrs ''>
<!ENTITY % notationAttrs ''>
<!ENTITY % annotationAttrs ''>
<!ENTITY % appinfoAttrs ''>
<!ENTITY % documentationAttrs ''>
<!ENTITY % complexDerivationSet "CDATA">
<!-- #all or space-separated list drawn from derivationChoice -->
<!ENTITY % blockSet "CDATA">
<!-- #all or space-separated list drawn from
derivationChoice + 'substitution' -->
<!ENTITY % mgs '%all; | %choice; | %sequence;'>
<!ENTITY % cs '%choice; | %sequence;'>
<!ENTITY % formValues '(qualified|unqualified)'>
<!ENTITY % attrDecls '((%attribute;| %attributeGroup;)*,(%anyAttribute;)?)'>
<!ENTITY % particleAndAttrs '((%mgs; | %group;)?, %attrDecls;)'>
<!-- This is used in part2 -->
<!ENTITY % restriction1 '((%mgs; | %group;)?)'>
%xs-datatypes;
<!-- the duplication below is to produce an unambiguous content model
which allows annotation everywhere -->
<!ELEMENT %schema; ((%include; | %import; | %redefine; | %annotation;)*,
((%simpleType; | %complexType;
| %element; | %attribute;
| %attributeGroup; | %group;
| %notation; ),
(%annotation;)*)* )>
<!ATTLIST %schema;
targetNamespace %URIref; #IMPLIED
version CDATA #IMPLIED
%nds; %URIref; #FIXED 'http://www.w3.org/2001/XMLSchema'
xmlns CDATA #IMPLIED
finalDefault %complexDerivationSet; ''
blockDefault %blockSet; ''
id ID #IMPLIED
elementFormDefault %formValues; 'unqualified'
attributeFormDefault %formValues; 'unqualified'
xml:lang CDATA #IMPLIED
%schemaAttrs;>
<!-- Note the xmlns declaration is NOT in the Schema for Schemas,
because at the Infoset level where schemas operate,
xmlns(:prefix) is NOT an attribute! -->
<!-- The declaration of xmlns is a convenience for schema authors -->
<!-- The id attribute here and below is for use in external references
from non-schemas using simple fragment identifiers.
It is NOT used for schema-to-schema reference, internal or
external. -->
<!-- a type is a named content type specification which allows attribute
declarations-->
<!-- -->
<!ELEMENT %complexType; ((%annotation;)?,
(%simpleContent;|%complexContent;|
%particleAndAttrs;))>
<!ATTLIST %complexType;
name %NCName; #IMPLIED
id ID #IMPLIED
abstract %boolean; #IMPLIED
final %complexDerivationSet; #IMPLIED
block %complexDerivationSet; #IMPLIED
mixed (true|false) 'false'
%complexTypeAttrs;>
<!-- particleAndAttrs is shorthand for a root type -->
<!-- mixed is disallowed if simpleContent, overriden if complexContent
has one too. -->
<!-- If anyAttribute appears in one or more referenced attributeGroups
and/or explicitly, the intersection of the permissions is used -->
<!ELEMENT %complexContent; ((%annotation;)?, (%restriction;|%extension;))>
<!ATTLIST %complexContent;
mixed (true|false) #IMPLIED
id ID #IMPLIED
%complexContentAttrs;>
<!-- restriction should use the branch defined above, not the simple
one from part2; extension should use the full model -->
<!ELEMENT %simpleContent; ((%annotation;)?, (%restriction;|%extension;))>
<!ATTLIST %simpleContent;
id ID #IMPLIED
%simpleContentAttrs;>
<!-- restriction should use the simple branch from part2, not the
one defined above; extension should have no particle -->
<!ELEMENT %extension; ((%annotation;)?, (%particleAndAttrs;))>
<!ATTLIST %extension;
base %QName; #REQUIRED
id ID #IMPLIED
%extensionAttrs;>
<!-- an element is declared by either:
a name and a type (either nested or referenced via the type attribute)
or a ref to an existing element declaration -->
<!ELEMENT %element; ((%annotation;)?, (%complexType;| %simpleType;)?,
(%unique; | %key; | %keyref;)*)>
<!-- simpleType or complexType only if no type|ref attribute -->
<!-- ref not allowed at top level -->
<!ATTLIST %element;
name %NCName; #IMPLIED
id ID #IMPLIED
ref %QName; #IMPLIED
type %QName; #IMPLIED
minOccurs %nonNegativeInteger; #IMPLIED
maxOccurs CDATA #IMPLIED
nillable %boolean; #IMPLIED
substitutionGroup %QName; #IMPLIED
abstract %boolean; #IMPLIED
final %complexDerivationSet; #IMPLIED
block %blockSet; #IMPLIED
default CDATA #IMPLIED
fixed CDATA #IMPLIED
form %formValues; #IMPLIED
%elementAttrs;>
<!-- type and ref are mutually exclusive.
name and ref are mutually exclusive, one is required -->
<!-- In the absence of type AND ref, type defaults to type of
substitutionGroup, if any, else the ur-type, i.e. unconstrained -->
<!-- default and fixed are mutually exclusive -->
<!ELEMENT %group; ((%annotation;)?,(%mgs;)?)>
<!ATTLIST %group;
name %NCName; #IMPLIED
ref %QName; #IMPLIED
minOccurs %nonNegativeInteger; #IMPLIED
maxOccurs CDATA #IMPLIED
id ID #IMPLIED
%groupAttrs;>
<!ELEMENT %all; ((%annotation;)?, (%element;)*)>
<!ATTLIST %all;
minOccurs (1) #IMPLIED
maxOccurs (1) #IMPLIED
id ID #IMPLIED
%allAttrs;>
<!ELEMENT %choice; ((%annotation;)?, (%element;| %group;| %cs; | %any;)*)>
<!ATTLIST %choice;
minOccurs %nonNegativeInteger; #IMPLIED
maxOccurs CDATA #IMPLIED
id ID #IMPLIED
%choiceAttrs;>
<!ELEMENT %sequence; ((%annotation;)?, (%element;| %group;| %cs; | %any;)*)>
<!ATTLIST %sequence;
minOccurs %nonNegativeInteger; #IMPLIED
maxOccurs CDATA #IMPLIED
id ID #IMPLIED
%sequenceAttrs;>
<!-- an anonymous grouping in a model, or
a top-level named group definition, or a reference to same -->
<!-- Note that if order is 'all', group is not allowed inside.
If order is 'all' THIS group must be alone (or referenced alone) at
the top level of a content model -->
<!-- If order is 'all', minOccurs==maxOccurs==1 on element/any inside -->
<!-- Should allow minOccurs=0 inside order='all' . . . -->
<!ELEMENT %any; (%annotation;)?>
<!ATTLIST %any;
namespace CDATA '##any'
processContents (skip|lax|strict) 'strict'
minOccurs %nonNegativeInteger; '1'
maxOccurs CDATA '1'
id ID #IMPLIED
%anyAttrs;>
<!-- namespace is interpreted as follows:
##any - - any non-conflicting WFXML at all
##other - - any non-conflicting WFXML from namespace other
than targetNamespace
##local - - any unqualified non-conflicting WFXML/attribute
one or - - any non-conflicting WFXML from
more URI the listed namespaces
references
##targetNamespace ##local may appear in the above list,
with the obvious meaning -->
<!ELEMENT %anyAttribute; (%annotation;)?>
<!ATTLIST %anyAttribute;
namespace CDATA '##any'
processContents (skip|lax|strict) 'strict'
id ID #IMPLIED
%anyAttributeAttrs;>
<!-- namespace is interpreted as for 'any' above -->
<!-- simpleType only if no type|ref attribute -->
<!-- ref not allowed at top level, name iff at top level -->
<!ELEMENT %attribute; ((%annotation;)?, (%simpleType;)?)>
<!ATTLIST %attribute;
name %NCName; #IMPLIED
id ID #IMPLIED
ref %QName; #IMPLIED
type %QName; #IMPLIED
use (prohibited|optional|required) #IMPLIED
default CDATA #IMPLIED
fixed CDATA #IMPLIED
form %formValues; #IMPLIED
%attributeAttrs;>
<!-- type and ref are mutually exclusive.
name and ref are mutually exclusive, one is required -->
<!-- default for use is optional when nested, none otherwise -->
<!-- default and fixed are mutually exclusive -->
<!-- type attr and simpleType content are mutually exclusive -->
<!-- an attributeGroup is a named collection of attribute decls, or a
reference thereto -->
<!ELEMENT %attributeGroup; ((%annotation;)?,
(%attribute; | %attributeGroup;)*,
(%anyAttribute;)?) >
<!ATTLIST %attributeGroup;
name %NCName; #IMPLIED
id ID #IMPLIED
ref %QName; #IMPLIED
%attributeGroupAttrs;>
<!-- ref iff no content, no name. ref iff not top level -->
<!-- better reference mechanisms -->
<!ELEMENT %unique; ((%annotation;)?, %selector;, (%field;)+)>
<!ATTLIST %unique;
name %NCName; #REQUIRED
id ID #IMPLIED
%uniqueAttrs;>
<!ELEMENT %key; ((%annotation;)?, %selector;, (%field;)+)>
<!ATTLIST %key;
name %NCName; #REQUIRED
id ID #IMPLIED
%keyAttrs;>
<!ELEMENT %keyref; ((%annotation;)?, %selector;, (%field;)+)>
<!ATTLIST %keyref;
name %NCName; #REQUIRED
refer %QName; #REQUIRED
id ID #IMPLIED
%keyrefAttrs;>
<!ELEMENT %selector; ((%annotation;)?)>
<!ATTLIST %selector;
xpath %XPathExpr; #REQUIRED
id ID #IMPLIED
%selectorAttrs;>
<!ELEMENT %field; ((%annotation;)?)>
<!ATTLIST %field;
xpath %XPathExpr; #REQUIRED
id ID #IMPLIED
%fieldAttrs;>
<!-- Schema combination mechanisms -->
<!ELEMENT %include; (%annotation;)?>
<!ATTLIST %include;
schemaLocation %URIref; #REQUIRED
id ID #IMPLIED
%includeAttrs;>
<!ELEMENT %import; (%annotation;)?>
<!ATTLIST %import;
namespace %URIref; #IMPLIED
schemaLocation %URIref; #IMPLIED
id ID #IMPLIED
%importAttrs;>
<!ELEMENT %redefine; (%annotation; | %simpleType; | %complexType; |
%attributeGroup; | %group;)*>
<!ATTLIST %redefine;
schemaLocation %URIref; #REQUIRED
id ID #IMPLIED
%redefineAttrs;>
<!ELEMENT %notation; (%annotation;)?>
<!ATTLIST %notation;
name %NCName; #REQUIRED
id ID #IMPLIED
public CDATA #REQUIRED
system %URIref; #IMPLIED
%notationAttrs;>
<!-- Annotation is either application information or documentation -->
<!-- By having these here they are available for datatypes as well
as all the structures elements -->
<!ELEMENT %annotation; (%appinfo; | %documentation;)*>
<!ATTLIST %annotation; %annotationAttrs;>
<!-- User must define annotation elements in internal subset for this
to work -->
<!ELEMENT %appinfo; ANY> <!-- too restrictive -->
<!ATTLIST %appinfo;
source %URIref; #IMPLIED
id ID #IMPLIED
%appinfoAttrs;>
<!ELEMENT %documentation; ANY> <!-- too restrictive -->
<!ATTLIST %documentation;
source %URIref; #IMPLIED
id ID #IMPLIED
xml:lang CDATA #IMPLIED
%documentationAttrs;>
<!NOTATION XMLSchemaStructures PUBLIC
'structures' 'http://www.w3.org/2001/XMLSchema.xsd' >
<!NOTATION XML PUBLIC
'REC-xml-1998-0210' 'http://www.w3.org/TR/1998/REC-xml-19980210' >
</pre></div><div class="div1">
<h2><a id="non-ambig" name="non-ambig"/>H Analysis of the Unique Particle Attribution Constraint (non-normative)</h2><p>A specification of the import of <a href="#cos-nonambig">Unique Particle Attribution (§3.8.6)</a> which does
not appeal to a processing model is difficult. What follows is intended as
guidance, without claiming to be complete.</p><p><span class="termdef"><a id="key-overlap" name="key-overlap">[Definition:]  </a>Two non-group
particles <b>overlap</b> if </span>
</p><ul><li>They are both element declaration particles whose declarations have the
same <a class="propref" href="#e-name">{name}</a> and <a class="propref" href="#e-target_namespace">{target namespace}</a>.</li></ul><p>
or
</p><ul><li>They are both element declaration particles one of whose <a class="propref" href="#e-name">{name}</a> and <a class="propref" href="#e-target_namespace">{target namespace}</a> are the same as those of an element declaration in the
other's <a class="termref" href="#key-eq"><span class="arrow">·</span>substitution group<span class="arrow">·</span></a>.</li></ul><p>
or
</p><ul><li>They are both wildcards, and the intensional intersection of their <a class="propref" href="#namespace_constraint">{namespace constraint}</a>s as defined
in <a href="#cos-aw-intersect">Attribute Wildcard Intersection (§3.10.6)</a> is not the empty set.</li></ul><p>
or
</p><ul><li>One is a wildcard and the other an element declaration, and the
<a class="propref" href="#e-target_namespace">{target namespace}</a> of any
member of its <a class="termref" href="#key-eq"><span class="arrow">·</span>substitution group<span class="arrow">·</span></a> is <a class="termref" href="#key-vn"><span class="arrow">·</span>valid<span class="arrow">·</span></a> with respect to the <a class="propref" href="#namespace_constraint">{namespace constraint}</a> of the wildcard.</li></ul><p>
</p><p>A content model will violate the unique attribution constraint if it
contains two particles which <a class="termref" href="#key-overlap"><span class="arrow">·</span>overlap<span class="arrow">·</span></a> and which either
</p><ul><li>are both in the <a class="propref" href="#particles">{particles}</a> of a <i>choice</i> or
<i>all</i> group</li></ul><p>
or
</p><ul><li>may <a class="termref" href="#key-vn"><span class="arrow">·</span>validate<span class="arrow">·</span></a> adjacent information items and the first has
<a class="propref" href="#p-min_occurs">{min occurs}</a> less than <a class="propref" href="#p-max_occurs">{max occurs}</a>.</li></ul><p>
</p><p>Two particles may <a class="termref" href="#key-vn"><span class="arrow">·</span>validate<span class="arrow">·</span></a> adjacent information items if they are
separated by at most epsilon transitions in the most obvious transcription of a
content model into a finite-state automaton.</p><p>A precise formulation of this constraint can also be offered in terms of
operations on finite-state automaton: transcribe the content model into an
automaton in the usual way using epsilon transitions for optionality and
unbounded maxOccurs, unfolding other numeric occurrence ranges and treating the heads of substitution groups as if
they were choices over all elements in the group, <em>but</em> using not
element QNames as transition labels, but rather pairs of element QNames and
positions in the model. Determinize this automaton, treating wildcard transitions as opaque. Now replace all
QName+position transition labels with the element QNames alone. If the result has any states
with two or more identical-QName-labeled transitions from it, or a
QName-labeled transition and a wildcard transition which subsumes it, or two
wildcard transitions whose intentional intersection is non-empty, the model does not
satisfy the Unique Attribution constraint. </p></div><div class="div1">
<h2><a id="nonnormative-references" name="nonnormative-references"/>I References (non-normative)</h2><dl><dt class="label"><a id="ref-dcd" name="ref-dcd"/>DCD</dt><dd> <em>Document
Content Description for XML (DCD)</em>, Tim Bray et al., eds., W3C, 10 August 1998.
See <a href="http://www.w3.org/TR/1998/NOTE-dcd-19980731">http://www.w3.org/TR/1998/NOTE-dcd-19980731</a> </dd><dt class="label"><a id="ref-ddml" name="ref-ddml"/>DDML</dt><dd> <em>Document
Definition Markup Language</em>, Ronald Bourret, John Cowan, Ingo Macherius,
Simon St. Laurent, eds., W3C, 19 January 1999. See
<a href="http://www.w3.org/TR/1999/NOTE-ddml-19990119">http://www.w3.org/TR/1999/NOTE-ddml-19990119
</a></dd><dt class="label"><a id="ref-sox" name="ref-sox"/>SOX</dt><dd> <em>Schema for
Object-oriented XML</em>, Andrew Davidson et al., eds., W3C, 1998. See
<a href="http://www.w3.org/1999/07/NOTE-SOX-19990730/">http://www.w3.org/1999/07/NOTE-SOX-19990730/</a> </dd><dt class="label"><a id="ref-sox-1.1" name="ref-sox-1.1"/>SOX-2</dt><dd> <em>Schema
for Object-oriented XML</em>, Version 2.0, Andrew Davidson, et al., W3C, 30
July 1999. See
<a href="http://www.w3.org/TR/NOTE-SOX/">http://www.w3.org/TR/NOTE-SOX/</a></dd><dt class="label"><a id="ref-xdr" name="ref-xdr"/>XDR</dt><dd> <em>XML-Data
Reduced</em>, Charles Frankston and Henry S. Thompson, 3 July 1998. See
<a href="http://www.ltg.ed.ac.uk/~ht/XMLData-Reduced.htm">http://www.ltg.ed.ac.uk/~ht/XMLData-Reduced.htm
</a> </dd><dt class="label"><a id="bib-expo" name="bib-expo"/>XML Schema: Primer</dt><dd><em>XML Schema Part 0:
Primer</em>, David C. Fallside, ed., W3C, 2 May 2001. See <a href="http://www.w3.org/TR/2004/REC-xmlschema-0-20041028/primer.html">http://www.w3.org/TR/2004/REC-xmlschema-0-20041028/primer.html</a></dd><dt class="label"><a id="ref-xml-data" name="ref-xml-data"/>XML-Data</dt><dd>
<em>XML-Data</em>, Andrew Layman et al., W3C, 05 January 1998. See
<a href="http://www.w3.org/TR/1998/NOTE-XML-data-0105/">http://www.w3.org/TR/1998/NOTE-XML-data-0105/</a> </dd></dl></div><div class="div1">
<h2><a id="acknowledgments" name="acknowledgments"/>J Acknowledgements (non-normative)</h2><p>The following
contributed material to the first edition of this specification:</p><blockquote><p>David Fallside, IBM<br/>Scott Lawrence, Agranat Systems<br/>Andrew Layman, Microsoft<br/>Eve L. Maler, Sun Microsystems<br/>Asir S. Vedamuthu, webMethods, Inc</p></blockquote><p>The editors acknowledge the members of the XML Schema Working Group, the members of other W3C Working Groups, and industry experts in other
forums who have contributed directly or indirectly to the process or content of
creating this document. The Working Group is particularly grateful to Lotus
Development Corp. and IBM for providing teleconferencing facilities.</p><p>
At the time the first edition of this
specification was published, the members of the XML Schema Working Group
were:</p><ul><li>Jim Barnette, Defense Information Systems Agency (DISA)</li><li>Paul V. Biron, Health Level Seven</li><li>Don Box, DevelopMentor</li><li>Allen Brown, Microsoft</li><li>Lee Buck, TIBCO Extensibility</li><li>Charles E. Campbell, Informix</li><li>Wayne Carr, Intel</li><li>Peter Chen, Bootstrap Alliance and LSU</li><li>David Cleary, Progress Software</li><li>Dan Connolly, W3C (<i>staff contact</i>) </li><li>Ugo Corda, Xerox</li><li>Roger L. Costello, MITRE</li><li>Haavard Danielson, Progress Software</li><li>Josef Dietl, Mozquito Technologies</li><li>David Ezell, Hewlett-Packard Company
</li><li>Alexander Falk, Altova GmbH</li><li>David Fallside, IBM</li><li>Dan Fox, Defense Logistics Information Service (DLIS)</li><li>Matthew Fuchs, Commerce One</li><li>Andrew Goodchild, Distributed Systems Technology Centre (DSTC Pty Ltd)</li><li>Paul Grosso, Arbortext, Inc</li><li>Martin Gudgin, DevelopMentor</li><li>Dave Hollander, Contivo, Inc (<i>co-chair</i>) </li><li>Mary Holstege, Invited Expert</li><li>Jane Hunter, Distributed Systems Technology Centre (DSTC Pty Ltd)</li><li>Rick Jelliffe, Academia Sinica</li><li>Simon Johnston, Rational Software</li><li>Bob Lojek, Mozquito Technologies</li><li>Ashok Malhotra, Microsoft</li><li>Lisa Martin, IBM</li><li>Noah Mendelsohn, Lotus Development Corporation</li><li>Adrian Michel, Commerce One</li><li>Alex Milowski, Invited Expert</li><li>Don Mullen, TIBCO Extensibility</li><li>Dave Peterson, Graphic Communications Association</li><li>Jonathan Robie, Software AG</li><li>Eric Sedlar, Oracle Corp.</li><li>C. M. Sperberg-McQueen, W3C (<i>co-chair</i>) </li><li>Bob Streich, Calico Commerce</li><li>William K. Stumbo, Xerox</li><li>Henry S. Thompson, University of Edinburgh</li><li>Mark Tucker, Health Level Seven</li><li>Asir S. Vedamuthu, webMethods, Inc</li><li>Priscilla Walmsley, XMLSolutions</li><li>Norm Walsh, Sun Microsystems</li><li>Aki Yoshida, SAP AG</li><li>Kongyi Zhou, Oracle Corp.</li></ul><p>The XML Schema Working Group has benefited in its work from the
participation and contributions of a number of people not currently
members of the Working Group, including
in particular those named below. Affiliations given are those current at
the time of their work with the WG.
</p><ul><li>Paula Angerstein, Vignette Corporation</li><li>David Beech, Oracle Corp.</li><li>Gabe Beged-Dov, Rogue Wave Software</li><li>Greg Bumgardner, Rogue Wave Software</li><li>Dean Burson, Lotus Development Corporation</li><li>Mike Cokus, MITRE</li><li>Andrew Eisenberg, Progress Software</li><li>Rob Ellman, Calico Commerce</li><li>George Feinberg, Object Design</li><li>Charles Frankston, Microsoft</li><li>Ernesto Guerrieri, Inso</li><li>Michael Hyman, Microsoft</li><li>Renato Iannella, Distributed Systems Technology Centre (DSTC Pty Ltd)</li><li>Dianne Kennedy, Graphic Communications Association</li><li>Janet Koenig, Sun Microsystems</li><li>Setrag Khoshafian, Technology Deployment International (TDI)</li><li>Ara Kullukian, Technology Deployment International (TDI)</li><li>Andrew Layman, Microsoft</li><li>Dmitry Lenkov, Hewlett-Packard Company</li><li>John McCarthy, Lawrence Berkeley National Laboratory</li><li>Murata Makoto, Xerox</li><li>Eve Maler, Sun Microsystems</li><li>Murray Maloney, Muzmo Communication, acting for Commerce One</li><li>Chris Olds, Wall Data</li><li>Frank Olken, Lawrence Berkeley National Laboratory</li><li>Shriram Revankar, Xerox</li><li>Mark Reinhold, Sun Microsystems</li><li>John C. Schneider, MITRE</li><li>Lew Shannon, NCR</li><li>William Shea, Merrill Lynch</li><li>Ralph Swick, W3C</li><li>Tony Stewart, Rivcom</li><li>Matt Timmermans, Microstar</li><li>Jim Trezzo, Oracle Corp.</li><li>Steph Tryphonas, Microstar</li></ul><p>The lists given above pertain to the first edition.
At the time work on this second edition was completed,
the membership of the Working Group was:</p><ul><li>Leonid Arbouzov, Sun Microsystems</li><li>Jim Barnette, Defense Information Systems Agency (DISA)</li><li>Paul V. Biron, Health Level Seven</li><li>Allen Brown, Microsoft</li><li>Charles E. Campbell, Invited expert</li><li>Peter Chen, Invited expert</li><li>Tony Cincotta, NIST</li><li>David Ezell, National Association of Convenience Stores</li><li>Matthew Fuchs, Invited expert</li><li>Sandy Gao, IBM</li><li>Andrew Goodchild, Distributed Systems Technology Centre (DSTC Pty Ltd)</li><li>Xan Gregg, Invited expert</li><li>Mary Holstege, Mark Logic</li><li>Mario Jeckle, DaimlerChrysler</li><li>Marcel Jemio, Data Interchange Standards Association</li><li>Kohsuke Kawaguchi, Sun Microsystems</li><li>Ashok Malhotra, Invited expert</li><li>Lisa Martin, IBM</li><li>Jim Melton, Oracle Corp</li><li>Noah Mendelsohn, IBM</li><li>Dave Peterson, Invited expert</li><li>Anli Shundi, TIBCO Extensibility</li><li>C. M. Sperberg-McQueen, W3C (<i>co-chair</i>) </li><li>Hoylen Sue, Distributed Systems Technology Centre (DSTC Pty Ltd)</li><li>Henry S. Thompson, University of Edinburgh</li><li>Asir S. Vedamuthu, webMethods, Inc</li><li>Priscilla Walmsley, Invited expert</li><li>Kongyi Zhou, Oracle Corp.</li></ul><p>
We note with sadness the accidental death of Mario Jeckle
shortly after the completion of work on this document.
In addition to those named above, several
people served on the Working Group during the development
of this second edition:
</p><ul><li>Oriol Carbo, University of Edinburgh</li><li>Tyng-Ruey Chuang, Academia Sinica</li><li>Joey Coyle, Health Level 7</li><li>Tim Ewald, DevelopMentor</li><li>Nelson Hung, Corel</li><li>Melanie Kudela, Uniform Code Council</li><li>Matthew MacKenzie, XML Global</li><li>Cliff Schmidt, Microsoft</li><li>John Stanton, Defense Information Systems Agency</li><li>John Tebbutt, NIST</li><li>Ross Thompson, Contivo</li><li>Scott Vorthmann, TIBCO Extensibility</li></ul></div></div></body></html>