discontinued / server · Files

REC-wsdl20-20070626.1 422 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 6642 6643 6644 6645 6646 6647 6648 6649 6650 6651 6652 6653 6654 6655 6656 6657 6658 6659 6660 6661 6662 6663 6664 6665 6666 6667 6668 6669 6670 6671 6672 6673 6674 6675 6676 6677 6678 6679 6680 6681 6682 6683 6684 6685 6686 6687 6688 6689 6690 6691 6692 6693 6694 6695 6696 6697 6698 6699 6700 6701 6702 6703 6704 6705 6706 6707 6708 6709 6710 6711 6712 6713 6714 6715 6716 6717 6718 6719 6720 6721 6722 6723 6724 6725 6726 6727 6728 6729 6730 6731 6732 6733 6734 6735 6736 6737 6738 6739 6740 6741 6742 6743 6744 6745 6746 6747 6748 6749 6750 6751 6752 6753 6754 6755 6756 6757 6758 6759 6760 6761 6762 6763 6764 6765 6766 6767 6768 6769 6770 6771 6772 6773 6774 6775 6776 6777 6778 6779 6780 6781 6782 6783 6784 6785 6786 6787 6788 6789 6790 6791 6792 6793 6794 6795 6796 6797 6798 6799 6800 6801 6802 6803 6804 6805 6806 6807 6808 6809 6810 6811 6812 6813 6814 6815 6816 6817 6818 6819 6820 6821 6822 6823 6824 6825 6826 6827 6828 6829 6830 6831 6832 6833 6834 6835 6836 6837 6838 6839 6840 6841 6842 6843 6844 6845 6846 6847 6848 6849 6850 6851 6852 6853 6854 6855 6856 6857 6858 6859 6860 6861 6862 6863 6864 6865 6866 6867 6868 6869 6870 6871 6872 6873 6874 6875 6876 6877 6878 6879 6880 6881 6882 6883 6884 6885 6886 6887 6888 6889 6890 6891 6892 6893 6894 6895 6896 6897 6898 6899 6900 6901 6902 6903 6904 6905 6906 6907 6908 6909 6910 6911 6912 6913 6914 6915 6916 6917 6918 6919 6920 6921 6922 6923 6924 6925 6926 6927 6928 6929 6930 6931 6932 6933 6934 6935 6936 6937 6938 6939 6940 6941 6942 6943 6944 6945 6946 6947 6948 6949 6950 6951 6952 6953 6954 6955 6956 6957 6958 6959 6960 6961 6962 6963 6964 6965 6966 6967 6968 6969 6970 6971 6972 6973 6974 6975 6976 6977 6978 6979 6980 6981 6982 6983 6984 6985 6986 6987 6988 6989 6990 6991 6992 6993 6994 6995 6996 6997 6998 6999 7000 7001 7002 7003 7004 7005 7006 7007 7008 7009 7010 7011 7012 7013 7014 7015 7016 7017 7018 7019 7020 7021 7022 7023 7024 7025 7026 7027 7028 7029 7030 7031 7032 7033 7034 7035 7036 7037 7038 7039 7040 7041 7042 7043 7044 7045 7046 7047 7048 7049 7050 7051 7052 7053 7054 7055 7056 7057 7058 7059 7060 7061 7062 7063 7064 7065 7066 7067 7068 7069 7070 7071 7072 7073 7074 7075 7076 7077 7078 7079 7080 7081 7082 7083 7084 7085 7086 7087 7088 7089 7090 7091 7092 7093 7094 7095 7096 7097 7098 7099 7100 7101 7102 7103 7104 7105 7106 7107 7108 7109 7110 7111 7112 7113 7114 7115 7116 7117 7118 7119 7120 7121 7122 7123 7124 7125 7126 7127 7128 7129 7130 7131 7132 7133 7134 7135 7136 7137 7138 7139 7140 7141 7142 7143 7144 7145 7146 7147 7148 7149 7150 7151 7152 7153 7154 7155 7156 7157 7158 7159 7160 7161 7162 7163 7164 7165 7166 7167 7168 7169 7170 7171 7172 7173 7174 7175 7176 7177 7178 7179 7180 7181 7182 7183 7184 7185 7186 7187 7188 7189 7190 7191 7192 7193 7194 7195 7196 7197 7198 7199 7200 7201 7202 7203 7204 7205 7206 7207 7208 7209 7210 7211 7212 7213 7214 7215 7216 7217 7218 7219 7220 7221 7222 7223 7224 7225 7226 7227 7228 7229 7230 7231 7232 7233 7234 7235 7236 7237 7238 7239 7240 7241 7242 7243 7244 7245 7246 7247 7248 7249 7250 7251 7252 7253 7254 7255 7256 7257 7258 7259 7260 7261 7262 7263 7264 7265 7266 7267 7268 7269 7270 7271 7272 7273 7274 7275 7276 7277 7278 7279 7280 7281 7282 7283 7284 7285 7286 7287 7288 7289 7290 7291 7292 7293 7294 7295 7296 7297 7298 7299 7300 7301 7302 7303 7304 7305 7306 7307 7308 7309 7310 7311 7312 7313 7314 7315 7316 7317 7318 7319 7320 7321 7322 7323 7324 7325 7326 7327 7328 7329 7330 7331 7332 7333 7334 7335 7336 7337 7338 7339 7340 7341 7342 7343 7344 7345 7346 7347 7348 7349 7350 7351 7352 7353 7354 7355 7356 7357 7358 7359 7360 7361 7362 7363 7364 7365 7366 7367 7368 7369 7370 7371 7372 7373 7374 7375 7376 7377 7378 7379 7380 7381 7382 7383 7384 7385 7386 7387 7388 7389 7390 7391 7392 7393 7394 7395 7396 7397 7398 7399 7400 7401 7402 7403 7404 7405 7406 7407 7408 7409 7410 7411 7412 7413 7414 7415 7416 7417 7418 7419 7420 7421 7422 7423 7424 7425 7426 7427 7428 7429 7430 7431 7432 7433 7434 7435 7436 7437 7438 7439 7440 7441 7442 7443 7444 7445 7446 7447 7448 7449 7450 7451 7452 7453 7454 7455 7456 7457 7458 7459 7460 7461 7462 7463 7464 7465 7466 7467 7468 7469 7470 7471 7472 7473 7474 7475 7476 7477 7478 7479 7480 7481 7482 7483 7484 7485 7486 7487 7488 7489 7490 7491 7492 7493 7494 7495 7496 7497 7498 7499 7500 7501 7502 7503 7504 7505 7506 7507 7508 7509 7510 7511 7512 7513 7514 7515 7516 7517 7518 7519 7520 7521 7522 7523 7524 7525 7526 7527 7528 7529 7530 7531 7532 7533 7534 7535 7536 7537 7538 7539 7540 7541 7542 7543 7544 7545 7546 7547 7548 7549 7550 7551 7552 7553 7554 7555 7556 7557 7558 7559 7560 7561 7562 7563 7564 7565 7566 7567 7568 7569 7570 7571 7572 7573 7574 7575 7576 7577 7578 7579 7580 7581 7582 7583 7584 7585 7586 7587 7588 7589 7590 7591 7592 7593 7594 7595 7596 7597 7598 7599 7600 7601 7602 7603 7604 7605 7606 7607 7608 7609 7610 7611 7612 7613 7614 7615 7616 7617 7618 7619 7620 7621 7622 7623 7624 7625 7626 7627 7628 7629 7630 7631 7632 7633 7634 7635 7636 7637 7638 7639 7640 7641 7642 7643 7644 7645 7646 7647 7648 7649 7650 7651 7652 7653 7654 7655 7656 7657 7658 7659 7660 7661 7662 7663 7664 7665 7666 7667 7668 7669 7670 7671 7672 7673 7674 7675 7676 7677 7678 7679 7680 7681 7682 7683 7684 7685 7686 7687 7688 7689 7690 7691 7692 7693 7694 7695 7696 7697 7698 7699 7700 7701 7702 7703 7704 7705 7706 7707 7708 7709 7710 7711 7712 7713 7714 7715 7716 7717 7718 7719 7720 7721 7722 7723 7724 7725 7726 7727 7728 7729 7730 7731 7732 7733 7734 7735 7736 7737 7738 7739 7740 7741 7742 7743 7744 7745 7746 7747 7748 7749 7750 7751 7752 7753 7754 7755 7756 7757 7758 7759 7760 7761 7762 7763 7764 7765 7766 7767 7768 7769 7770 7771 7772 7773 7774 7775 7776 7777 7778 7779 7780 7781 7782 7783 7784 7785 7786 7787 7788 7789 7790 7791 7792 7793 7794 7795 7796 7797 7798 7799 7800 7801 7802 7803 7804 7805 7806 7807 7808 7809 7810 7811 7812 7813 7814 7815 7816 7817 7818 7819 7820 7821 7822 7823 7824 7825 7826 7827 7828 7829 7830 7831 7832 7833 7834 7835 7836 7837 7838 7839 7840 7841 7842 7843 7844 7845 7846 7847 7848 7849 7850 7851 7852 7853 7854 7855 7856 7857 7858 7859 7860 7861 7862 7863 7864 7865 7866 7867 7868 7869 7870 7871 7872 7873 7874 7875 7876 7877 7878 7879 7880 7881 7882 7883 7884 7885 7886 7887 7888 7889 7890 7891 7892 7893 7894 7895 7896 7897 7898 7899 7900 7901 7902 7903 7904 7905 7906 7907 7908 7909 7910 7911 7912 7913 7914 7915 7916 7917 7918 7919 7920 7921 7922 7923 7924 7925 7926 7927 7928 7929 7930 7931 7932 7933 7934 7935 7936 7937 7938 7939 7940 7941 7942 7943 7944 7945 7946 7947 7948 7949 7950 7951 7952 7953 7954 7955 7956 7957 7958 7959 7960 7961 7962 7963 7964 7965 7966 7967 7968 7969 7970 7971 7972 7973 7974 7975 7976 7977 7978 7979 7980 7981 7982 7983 7984 7985 7986 7987 7988 7989 7990 7991 7992 7993 7994 7995 7996 7997 7998 7999 8000 8001 8002 8003 8004 8005 8006 8007 8008 8009 8010 8011 8012 8013 8014 8015 8016 8017 8018 8019 8020 8021 8022 8023 8024 8025 8026 8027 8028 8029 8030 8031 8032 8033 8034 8035 8036 8037 8038 8039 8040 8041 8042 8043 8044 8045 8046 8047 8048 8049 8050 8051 8052 8053 8054 8055 8056 8057 8058 8059 8060 8061 8062 8063 8064 8065 8066 8067 8068 8069 8070 8071 8072 8073 8074 8075 8076 8077 8078 8079 8080 8081 8082 8083 8084 8085 8086 8087 8088 8089 8090 8091 8092 8093 8094 8095 8096 8097 8098 8099 8100 8101 8102 8103 8104 8105 8106 8107 8108 8109 8110 8111 8112 8113 8114 8115 8116 8117 8118 8119 8120 8121 8122 8123 8124 8125 8126 8127 8128 8129 8130 8131 8132 8133 8134 8135 8136 8137 8138 8139 8140 8141 8142 8143 8144 8145 8146 8147 8148 8149 8150 8151 8152 8153 8154 8155 8156 8157 8158 8159 8160 8161 8162 8163 8164 8165 8166 8167 8168 8169 8170 8171 8172 8173 8174 8175 8176 8177 8178 8179 8180 8181 8182 8183 8184 8185 8186 8187 8188 8189 8190 8191 8192 8193 8194 8195 8196 8197 8198 8199 8200 8201 8202 8203 8204 8205 8206 8207 8208 8209 8210 8211 8212 8213 8214 8215 8216 8217 8218 8219 8220 8221 8222 8223 8224 8225 8226 8227 8228 8229 8230 8231 8232 8233 8234 8235 8236 8237 8238 8239 8240 8241 8242 8243 8244 8245 8246 8247 8248 8249 8250 8251 8252 8253 8254 8255 8256 8257 8258 8259 8260 8261 8262 8263 8264 8265 8266 8267 8268 8269 8270 8271 8272 8273 8274 8275 8276 8277 8278 8279 8280 8281 8282 8283 8284 8285 8286 8287 8288 8289 8290 8291 8292 8293 8294 8295 8296 8297 8298 8299 8300 8301 8302 8303 8304 8305 8306 8307 8308 8309 8310 8311 8312 8313 8314 8315 8316 8317 8318 8319 8320 8321 8322 8323 8324 8325 8326 8327 8328 8329 8330 8331 8332 8333 8334 8335 8336 8337 8338 8339 8340 8341 8342 8343 8344 8345 8346 8347 8348 8349 8350 8351 8352 8353 8354 8355 8356 8357 8358 8359 8360 8361 8362 8363 8364 8365 8366 8367 8368 8369 8370 8371 8372 8373 8374 8375 8376 8377 8378 8379 8380 8381 8382 8383 8384 8385 8386 8387 8388 8389 8390 8391 8392 8393 8394 8395 8396 8397 8398 8399 8400 8401 8402 8403 8404 8405 8406 8407 8408 8409 8410 8411 8412 8413 8414 8415 8416 8417 8418 8419 8420 8421 8422 8423 8424 8425 8426 8427 8428 8429 8430 8431 8432 8433 8434 8435 8436 8437 8438 8439 8440 8441 8442 8443 8444 8445 8446 8447 8448 8449 8450 8451 8452 8453 8454 8455 8456 8457 8458 8459 8460 8461 8462 8463 8464 8465 8466 8467 8468 8469 8470 8471 8472 8473 8474 8475 8476 8477 8478 8479 8480 8481 8482 8483 8484 8485 8486 8487 8488 8489 8490 8491 8492 8493 8494 8495 8496 8497 8498 8499 8500 8501 8502 8503 8504 8505 8506 8507 8508 8509 8510 8511 8512 8513 8514 8515 8516 8517 8518 8519 8520 8521 8522 8523 8524 8525 8526 8527 8528 8529 8530 8531 8532 8533 8534 8535 8536 8537 8538 8539 8540 8541 8542 8543 8544 8545 8546 8547 8548 8549 8550 8551 8552 8553 8554 8555 8556 8557 8558 8559 8560 8561 8562 8563 8564 8565 8566 8567 8568 8569 8570 8571 8572 8573 8574 8575 8576 8577 8578 8579 8580 8581 8582 8583 8584 8585 8586 8587 8588 8589 8590 8591 8592 8593 8594 8595 8596 8597 8598 8599 8600 8601 8602 8603 8604 8605 8606 8607 8608 8609 8610 8611 8612 8613 8614 8615 8616 8617 8618 8619 8620 8621 8622 8623 8624 8625 8626 8627 8628 8629 8630 8631 8632 8633 8634 8635 8636 8637 8638 8639 8640 8641 8642 8643 8644 8645 8646 8647 8648 8649 8650 8651 8652 8653 8654 8655 8656 8657 8658 8659 8660 8661 8662 8663 8664 8665 8666 8667 8668 8669 8670 8671 8672 8673 8674 8675 8676 8677 8678 8679 8680 8681 8682 8683 8684 8685 8686 8687 8688 8689 8690 8691 8692 8693 8694 8695 8696 8697 8698 8699 8700 8701 8702 8703 8704 8705 8706 8707 8708 8709 8710 8711 8712 8713 8714 8715 8716 8717 8718 8719 8720 8721 8722 8723 8724 8725 8726 8727 8728 8729 8730 8731 8732 8733 8734 8735 8736 8737 8738 8739 8740 8741 8742 8743 8744 8745 8746 8747 8748 8749 8750 8751 8752 8753 8754 8755 8756 8757 8758 8759 8760 8761 8762 8763 8764 8765 8766 8767 8768 8769 8770 8771 8772 8773 8774 8775 8776 8777 8778 8779 8780 8781 8782 8783 8784 8785 8786 8787 8788 8789 8790 8791 8792 8793 8794 8795 8796 8797 8798 8799 8800 8801 8802 8803 8804 8805 8806 8807 8808 8809 8810 8811 8812 8813 8814 8815 8816 8817 8818 8819 8820 8821 8822 8823 8824 8825 8826 8827 8828 8829 8830 8831 8832 8833 8834 8835 8836 8837 8838 8839 8840 8841 8842 8843 8844 8845 8846 8847 8848 8849 8850 8851 8852 8853 8854 8855 8856 8857 8858 8859 8860 8861 8862 8863 8864 8865 8866 8867 8868 8869 8870 8871 8872 8873 8874 8875 8876 8877 8878 8879 8880 8881 8882 8883 8884 8885 8886 8887 8888 8889 8890 8891 8892 8893 8894 8895 8896 8897 8898 8899 8900 8901 8902 8903 8904 8905 8906 8907 8908 8909 8910 8911 8912 8913 8914 8915 8916 8917 8918 8919 8920 8921 8922 8923 8924 8925 8926 8927 8928 8929 8930 8931 8932 8933 8934 8935 8936 8937 8938 8939 8940 8941 8942 8943 8944 8945 8946 8947 8948 8949 8950 8951 8952 8953 8954 8955 8956 8957 8958 8959 8960 8961 8962 8963 8964 8965 8966 8967 8968 8969 8970 8971 8972 8973 8974 8975 8976 8977 8978 8979 8980 8981 8982 8983 8984 8985 8986 8987 8988 8989 8990 8991 8992 8993 8994 8995 8996 8997 8998 8999 9000 9001 9002 9003 9004 9005 9006 9007 9008 9009 9010 9011 9012 9013 9014 9015 9016 9017 9018 9019 9020 9021 9022 9023 9024 9025 9026 9027 9028 9029 9030 9031 9032 9033 9034 9035 9036 9037 9038 9039 9040 9041 9042 9043 9044 9045 9046 9047 9048 9049 9050 9051 9052 9053 9054 9055 9056 9057 9058 9059 9060 9061 9062 9063 9064 9065 9066 9067 9068 9069 9070 9071 9072 9073 9074 9075 9076 9077 9078 9079 9080 9081 9082 9083 9084 9085 9086 9087 9088 9089 9090 9091 9092 9093 9094 9095 9096 9097 9098 9099 9100 9101 9102 9103 9104 9105 9106 9107 9108 9109 9110 9111 9112 9113 9114 9115 9116 9117 9118 9119 9120 9121 9122 9123 9124 9125 9126 9127 9128 9129 9130 9131 9132 9133 9134 9135 9136 9137 9138 9139 9140 9141 9142 9143 9144 9145 9146 9147 9148 9149 9150 9151 9152 9153 9154 9155 9156 9157 9158 9159 9160 9161 9162 9163 9164 9165 9166 9167 9168 9169 9170 9171 9172 9173 9174 9175 9176 9177 9178 9179 9180 9181 9182 9183 9184 9185 9186 9187 9188 9189 9190 9191 9192 9193 9194 9195 9196 9197 9198 9199 9200 9201 9202 9203 9204 9205 9206 9207 9208 9209 9210 9211 9212 9213 9214 9215 9216 9217 9218 9219 9220 9221 9222 9223 9224 9225 9226 9227 9228 9229 9230 9231 9232 9233 9234 9235 9236 9237 9238 9239 9240 9241 9242 9243 9244 9245 9246 9247 9248 9249 9250 9251 9252 9253 9254 9255 9256 9257 9258 9259 9260 9261 9262 9263 9264 9265 9266 9267 9268 9269 9270 9271 9272 9273 9274 9275 9276 9277 9278 9279 9280 9281 9282 9283 9284 9285 9286 9287 9288 9289 9290 9291 9292 9293 9294 9295 9296 9297 9298 9299 9300 9301 9302 9303 9304 9305 9306 9307 9308 9309 9310 9311 9312 9313 9314 9315 9316 9317 9318 9319 9320 9321 9322 9323 9324 9325 9326 9327 9328 9329 9330 9331 9332 9333 9334 9335 9336 9337 9338 9339 9340 9341 9342 9343 9344 9345 9346 9347 9348 9349 9350 9351 9352 9353 9354 9355 9356 9357 9358 9359 9360 9361 9362 9363 9364 9365 9366 9367 9368 9369 9370 9371 9372 9373 9374 9375 9376 9377 9378 9379 9380 9381 9382 9383 9384 9385 9386 9387 9388 9389 9390 9391 9392 9393 9394 9395 9396 9397 9398 9399 9400 9401 9402 9403 9404 9405 9406 9407 9408 9409 9410 9411 9412 9413 9414 9415 9416 9417 9418 9419 9420 9421 9422 9423 9424 9425 9426 9427 9428 9429 9430 9431 9432 9433 9434 9435 9436 9437 9438 9439 9440 9441 9442 9443 9444 9445 9446 9447 9448 9449 9450 9451 9452 9453 9454 9455 9456 9457 9458 9459 9460 9461 9462 9463 9464 9465 9466 9467 9468 9469 9470 9471 9472 9473 9474 9475 9476 9477 9478 9479 9480 9481 9482 9483 9484 9485 9486 9487 9488 9489 9490 9491 9492 9493 9494 9495 9496 9497 9498 9499 9500 9501 9502 9503 9504 9505 9506 9507 9508 9509 9510 9511 9512 9513 9514 9515 9516 9517 9518 9519 9520 9521 9522 9523 9524 9525 9526 9527 9528 9529 9530 9531 9532 9533 9534 9535 9536 9537 9538 9539 9540 9541 9542 9543 9544 9545 9546 9547 9548 9549 9550 9551 9552 9553 9554 9555 9556 9557 9558 9559 9560 9561 9562 9563 9564 9565 9566 9567 9568 9569 9570 9571 9572 9573 9574 9575 9576 9577 9578 9579 9580 9581 9582 9583 9584 9585 9586 9587 9588 9589 9590 9591 9592 9593 9594 9595 9596 9597 9598 9599 9600 9601 9602 9603 9604 9605 9606 9607 9608 9609 9610 9611 9612 9613 9614 9615 9616 9617 9618 9619 9620 9621 9622 9623 9624 9625 9626 9627 9628 9629 9630 9631 9632 9633 9634 9635 9636 9637 9638 9639 9640 9641 9642 9643 9644 9645 9646 9647 9648 9649 9650 9651 9652 9653 9654 9655 9656 9657 9658 9659 9660 9661 9662 9663 9664 9665 9666 9667 9668 9669 9670 9671 9672 9673 9674 9675 9676 9677 9678 9679 9680 9681 9682 9683 9684 9685 9686 9687 9688 9689 9690 9691 9692 9693 9694 9695 9696 9697 9698 9699 9700 9701 9702 9703 9704 9705 9706 9707 9708 9709 9710 9711 9712 9713 9714 9715 9716 9717 9718 9719 9720 9721 9722 9723 9724 9725 9726 9727 9728 9729 9730 9731 9732 9733 9734 9735 9736 9737 9738 9739 9740 9741 9742 9743 9744 9745 9746 9747 9748 9749 9750 9751 9752 9753 9754 9755 9756 9757 9758 9759 9760 9761 9762 9763 9764 9765 9766 9767 9768 9769 9770 9771 9772 9773 9774 9775 9776 9777 9778 9779 9780 9781 9782 9783 9784 9785 9786 9787 9788 9789 9790 9791 9792 9793 9794 9795 9796 9797 9798 9799 9800 9801 9802 9803 9804 9805 9806 9807 9808 9809 9810 9811 9812 9813 9814 9815 9816 9817 9818 9819 9820 9821 9822 9823 9824 9825 9826 9827 9828 9829 9830 9831 9832 9833 9834 9835 9836 9837 9838 9839 9840 9841 9842 9843 9844 9845 9846 9847 9848 9849 9850 9851 9852 9853 9854 9855 9856 9857 9858 9859 9860 9861 9862 9863 9864 9865 9866 9867 9868 9869 9870 9871 9872 9873 9874 9875 9876 9877 9878 9879 9880 9881 9882 9883 9884 9885 9886 9887 9888 9889 9890 9891 9892 9893 9894 9895 9896 9897 9898 9899 9900 9901 9902 9903 9904 9905 9906 9907 9908 9909 9910 9911 9912 9913 9914 9915 9916 9917 9918 9919 9920 9921 9922 9923 9924 9925 9926 9927 9928 9929 9930 9931 9932 9933 9934 9935 9936 9937 9938 9939 9940 9941 9942 9943 9944 9945 9946 9947 9948 9949 9950 9951 9952 9953 9954 9955 9956 9957 9958 9959 9960 9961 9962 9963 9964 9965 9966 9967 9968 9969 9970 9971 9972 9973 9974 9975 9976 9977 9978 9979 9980 9981 9982 9983 9984 9985 9986 9987 9988 9989 9990 9991 9992 9993 9994 9995 9996 9997 9998 9999 10000 10001 10002 10003 10004 10005 10006 10007 10008 10009 10010 10011 10012 10013 10014 10015 10016 10017 10018 10019 10020 10021 10022 10023 10024 10025 10026 10027 10028 10029 10030 10031 10032 10033 10034 10035 10036 10037 10038 10039 10040 10041 10042 10043 10044 10045 10046 10047 10048 10049 10050 10051 10052 10053 10054 10055 10056 10057 10058 10059 10060 10061 10062 10063 10064 10065 10066 10067 10068 10069 10070 10071 10072 10073 10074 10075 10076 10077 10078 10079 10080 10081 10082 10083 10084 10085 10086 10087 10088 10089 10090 10091 10092 10093 10094 10095 10096 10097 10098 10099 10100 10101 10102 10103 10104 10105 10106 10107 10108 10109 10110 
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html lang="en" xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<meta http-equiv="Content-Type" content=
"text/html; charset=utf-8" />
<title>Web Services Description Language (WSDL) Version 2.0 Part 1:
Core Language</title>

<style type="text/css" xml:space="preserve">
/*<![CDATA[*/
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; }

dt.label       { display: run-in; }

li, p           { margin-top: 0.3em;
                 margin-bottom: 0.3em; }

.diff-chg       { background-color: yellow; }
.diff-del       { background-color: red; text-decoration: line-through;}
.diff-add       { background-color: lime; }

table          { empty-cells: show; }

table caption {
        font-weight: normal;
        font-style: italic;
        text-align: left;
        margin-bottom: .5em;
}

div.issue {
  color: red;
}
.rfc2119 {
  font-variant: small-caps;
}

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}

          th { color: #000000; background-color: #CCCC99; }
          span.test-assertion { background-color: #FFC0CB; }
          span.test-assertion-tr:hover { background-color: #FFC0CB; }
/*]]>*/
</style>
<link rel="stylesheet" type="text/css" href=
"http://www.w3.org/StyleSheets/TR/W3C-REC.css" />
</head>
<body>
<div class="head">
<p><a href="http://www.w3.org/"><img src=
"http://www.w3.org/Icons/w3c_home" alt="W3C" height="48" width=
"72" /></a></p>
<h1><a name="title" id="title"></a>Web Services Description
Language (WSDL) Version 2.0 Part 1: Core Language</h1>
<h2><a name="w3c-doctype" id="w3c-doctype"></a>W3C Recommendation
26 June 2007</h2>
<dl>
<dt>This version:</dt>
<dd><a href=
"http://www.w3.org/TR/2007/REC-wsdl20-20070626">http://www.w3.org/TR/2007/REC-wsdl20-20070626</a></dd>
<dt>Latest version:</dt>
<dd><a href=
"http://www.w3.org/TR/wsdl20">http://www.w3.org/TR/wsdl20</a></dd>
<dt>Previous version:</dt>
<dd><a href=
"http://www.w3.org/TR/2007/PR-wsdl20-20070523">http://www.w3.org/TR/2007/PR-wsdl20-20070523</a></dd>
<dt>Editors:</dt>
<dd>Roberto Chinnici, Sun Microsystems</dd>
<dd>Jean-Jacques Moreau, Canon</dd>
<dd>Arthur Ryman, IBM</dd>
<dd>Sanjiva Weerawarana, WSO2</dd>
</dl>
<p>Please refer to the <a href=
"http://www.w3.org/2007/06/wsdl20-errata.html"><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="wsdl20-z.html">XHTML with Z Notation</a>, <a href=
"wsdl20.pdf">PDF</a>, <a href="wsdl20.ps">PostScript</a>, <a href=
"wsdl20.xml">XML</a>, and&#160;<a href="wsdl20.txt">plain
text</a>.</p>
<p>See also <a href=
"http://www.w3.org/2003/03/Translations/byTechnology?technology=wsdl20">
<strong>translations</strong></a>.</p>
<p class="copyright"><a href=
"http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>&#160;©&#160;2007&#160;<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> rules apply.</p>
</div>
<hr />
<div>
<h2><a name="abstract" id="abstract"></a>Abstract</h2>
<p>This document describes the Web Services Description Language
Version 2.0 (WSDL 2.0), an XML language for describing Web
services. This specification defines the core language which can be
used to describe Web services based on an abstract model of what
the service offers. It also defines the conformance criteria for
documents in this language.</p>
</div>
<div>
<h2><a name="status" id="status"></a>Status of this Document</h2>
<p><em>This section describes the status of this document at the
time of its publication. Other documents may supersede this
document. A list of current W3C publications and the latest
revision of this technical report can be found in the <a href=
"http://www.w3.org/TR/">W3C technical reports index</a> at
http://www.w3.org/TR/.</em></p>
<p>This is the <a href=
"http://www.w3.org/2005/10/Process-20051014/tr.html#RecsW3C">W3C
Recommendation</a> of Web Services Description Language (WSDL)
Version 2.0 Part 1: Core Language for review by W3C Members and
other interested parties. It has been produced by the <a href=
"http://www.w3.org/2002/ws/desc/">Web Services Description Working
Group</a>, which is part of the <a href=
"http://www.w3.org/2002/ws/Activity">W3C Web Services
Activity</a>.</p>
<p>Please send comments about this document to the public <a href=
"mailto:public-ws-desc-comments@w3.org">public-ws-desc-comments@w3.org</a>
mailing list (<a href=
"http://lists.w3.org/Archives/Public/public-ws-desc-comments/">public
archive</a>).</p>
<p>The Working Group released a test suite along with an <a href=
"http://www.w3.org/2002/ws/desc/5/impl-report/">implementation
report</a>. A <a href="wsdl20-diff.html">diff-marked version
against the previous version of this document</a> is available.</p>
<p>This document has been reviewed by W3C Members, by software
developers, and by other W3C groups and interested parties, and is
endorsed by the Director as a W3C Recommendation. It is a stable
document and may be used as reference material or cited from
another document. W3C's role in making the Recommendation is to
draw attention to the specification and to promote its widespread
deployment. This enhances the functionality and interoperability of
the Web.</p>
<p>This document is governed by the <a href=
"http://www.w3.org/TR/2002/NOTE-patent-practice-20020124">24
January 2002 CPP</a> as amended by the <a href=
"http://www.w3.org/2004/02/05-pp-transition">W3C Patent Policy
Transition Procedure</a>. W3C maintains a <a href=
"http://www.w3.org/2002/ws/desc/2/04/24-IPR-statements.html">public
list of any patent disclosures</a> made in connection with the
deliverables of the group; that page also includes instructions for
disclosing a patent. An individual who has actual knowledge of a
patent which the individual believes contains <a href=
"http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">
Essential Claim(s)</a> must 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>
</div>
<div class="toc">
<h2><a name="contents" id="contents"></a>Table of Contents</h2>
<p class="toc">1. <a href="#intro">Introduction</a>
<br />
&#160;&#160;&#160;&#160;1.1 <a href="#intro_ws">Service
Description</a>
<br />
&#160;&#160;&#160;&#160;1.2 <a href="#meaning">The Meaning of a
Service Description</a>
<br />
&#160;&#160;&#160;&#160;1.3 <a href="#markup">Document
Conformance</a>
<br />
&#160;&#160;&#160;&#160;1.4 <a href="#notation">Notational
Conventions</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;1.4.1 <a href=
"#rfc2119keywords">RFC 2119 Keywords</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;1.4.2 <a href=
"#rfc3986namespaces">RFC 3986 Namespaces</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;1.4.3 <a href=
"#xmlSchemaAnyURI">XML Schema anyURI</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;1.4.4 <a href=
"#nsprefixes">Prefixes and Namespaces Used in This
Specification</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;1.4.5 <a href=
"#terminology">Terms Used in This Specification</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;1.4.6 <a href=
"#xmlinfosetproperties">XML Information Set Properties</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;1.4.7 <a href=
"#wsdlcomponentmodelproperties">WSDL 2.0 Component Model
Properties</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;1.4.8 <a href=
"#znotation">Z Notation</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;1.4.9 <a href=
"#bnfpseudoschemas">BNF Pseudo-Schemas</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;1.4.10 <a href=
"#assertions">Assertions</a>
<br />
2. <a href="#component_model">Component Model</a>
<br />
&#160;&#160;&#160;&#160;2.1 <a href="#Description">Description</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.1.1 <a href=
"#Description_details">The Description Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.1.2 <a href=
"#Description_XMLRep">XML Representation of Description
Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.1.2.1
<a href="#Description_targetnamespace_attribute">targetNamespace
attribute information item</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.1.3 <a href=
"#Description_Mapping">Mapping Description's XML Representation to
Component Properties</a>
<br />
&#160;&#160;&#160;&#160;2.2 <a href="#Interface">Interface</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.2.1 <a href=
"#Interface_details">The Interface Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.2.2 <a href=
"#Interface_XMLRep">XML Representation of Interface Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.2.2.1
<a href="#Interface_name_attribute">name attribute information item
with interface [owner element]</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.2.2.2
<a href="#Interface_extends_attribute">extends attribute
information item</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.2.2.3
<a href="#Interface_styleDefault_attribute">styleDefault attribute
information item</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.2.3 <a href=
"#Interface_Mapping">Mapping Interface's XML Representation to
Component Properties</a>
<br />
&#160;&#160;&#160;&#160;2.3 <a href="#InterfaceFault">Interface
Fault</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.3.1 <a href=
"#InterfaceFault_details">The Interface Fault Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.3.2 <a href=
"#InterfaceFault_XMLRep">XML Representation of Interface Fault
Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.3.2.1
<a href="#Interfacefault_name_attribute">name attribute information
item with fault [owner element]</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.3.2.2
<a href="#Interface_element_attribute">element attribute
information item with fault [owner element]</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.3.3 <a href=
"#InterfaceFault_Mapping">Mapping Interface Fault's XML
Representation to Component Properties</a>
<br />
&#160;&#160;&#160;&#160;2.4 <a href="#InterfaceOperation">Interface
Operation</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.4.1 <a href=
"#InterfaceOperation_details">The Interface Operation Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.4.1.1
<a href="#MessageExchangePattern">Message Exchange Pattern</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.4.1.2
<a href="#InterfaceOperationStyle">Operation Style</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.4.2 <a href=
"#InterfaceOperation_XMLRep">XML Representation of Interface
Operation Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.4.2.1
<a href="#Interfaceoperation_name_attribute">name attribute
information item with operation [owner element]</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.4.2.2
<a href="#Interfaceoperation_pattern_attribute">pattern attribute
information item with operation [owner element]</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.4.2.3
<a href="#InterfaceOperation_style_attribute">style attribute
information item with operation [owner element]</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.4.3 <a href=
"#InterfaceOperation_Mapping">Mapping Interface Operation's XML
Representation to Component Properties</a>
<br />
&#160;&#160;&#160;&#160;2.5 <a href=
"#InterfaceMessageReference">Interface Message Reference</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.5.1 <a href=
"#InterfaceMessageReference_details">The Interface Message
Reference Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.5.2 <a href=
"#InterfaceMessageReference_XMLRep">XML Representation of Interface
Message Reference Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.5.2.1
<a href=
"#InterfaceMessageReference_messageReference_attribute">messageLabel
attribute information item with input or output [owner element]</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.5.2.2
<a href="#InterfaceMessageReference_element_attribute">element
attribute information item with input or output [owner element]</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.5.3 <a href=
"#InterfaceMessageReference_Mapping">Mapping Interface Message
Reference's XML Representation to Component Properties</a>
<br />
&#160;&#160;&#160;&#160;2.6 <a href=
"#InterfaceFaultReference">Interface Fault Reference</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.6.1 <a href=
"#InterfaceFaultReference_details">The Interface Fault Reference
Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.6.2 <a href=
"#InterfaceFaultReference_XMLRep">XML Representation of Interface
Fault Reference</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.6.2.1
<a href="#InterfaceFaultReference_ref_attribute">ref attribute
information item with infault, or outfault [owner element]</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.6.2.2
<a href=
"#InterfaceFaultReference_messageReference_attribute">messageLabel
attribute information item with infault, or outfault [owner
element]</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.6.3 <a href=
"#InterfaceFaultReference_Mapping">Mapping Interface Fault
Reference's XML Representation to Component Properties</a>
<br />
&#160;&#160;&#160;&#160;2.7 <a href="#Binding">Binding</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.7.1 <a href=
"#Binding_details">The Binding Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.7.2 <a href=
"#Binding_XMLRep">XML Representation of Binding Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.7.2.1
<a href="#Binding_name_attribute">name attribute information item
with binding [owner element]</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.7.2.2
<a href="#Binding_interface_attribute">interface attribute
information item with binding [owner element]</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.7.2.3
<a href="#Binding_type_attribute">type attribute information item
with binding [owner element]</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.7.2.4
<a href="#Binding_extension_elements">Binding extension
elements</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.7.3 <a href=
"#Binding_Mapping">Mapping Binding's XML Representation to
Component Properties</a>
<br />
&#160;&#160;&#160;&#160;2.8 <a href="#Binding_Fault">Binding
Fault</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.8.1 <a href=
"#Binding_Fault_details">The Binding Fault Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.8.2 <a href=
"#Binding_Fault_XMLRep">XML Representation of Binding Fault
Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.8.2.1
<a href="#Binding_Fault_ref_attribute">ref attribute information
item with fault [owner element]</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.8.2.2
<a href="#Binding_Fault_extension_elements">Binding Fault extension
elements</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.8.3 <a href=
"#Binding_Fault_Mapping">Mapping Binding Fault's XML Representation
to Component Properties</a>
<br />
&#160;&#160;&#160;&#160;2.9 <a href="#Binding_Operation">Binding
Operation</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.9.1 <a href=
"#Binding_Operation_details">The Binding Operation Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.9.2 <a href=
"#Binding_Operation_XMLRep">XML Representation of Binding Operation
Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.9.2.1
<a href="#Binding_Operation_ref_attribute">ref attribute
information item with operation [owner element]</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.9.2.2
<a href="#Binding_Operation_extension_elements">Binding Operation
extension elements</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.9.3 <a href=
"#Binding_Operation_Mapping">Mapping Binding Operation's XML
Representation to Component Properties</a>
<br />
&#160;&#160;&#160;&#160;2.10 <a href=
"#Binding_Message_Reference">Binding Message Reference</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.10.1 <a href=
"#Binding_Message_Reference_details">The Binding Message Reference
Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.10.2 <a href=
"#Binding_Message_Reference_XMLRep">XML Representation of Binding
Message Reference Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.10.2.1
<a href="#Binding_Message_Reference_name_attribute">messageLabel
attribute information item with input or output [owner element]</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.10.2.2
<a href="#Binding_Message_Reference_extension_elements">Binding
Message Reference extension elements</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.10.3 <a href=
"#Binding_Message_Reference_Mapping">Mapping Binding Message
Reference's XML Representation to Component Properties</a>
<br />
&#160;&#160;&#160;&#160;2.11 <a href=
"#Binding_Fault_Reference">Binding Fault Reference</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.11.1 <a href=
"#Binding_Fault_Reference_details">The Binding Fault Reference
Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.11.2 <a href=
"#Binding_Fault_Reference_XMLRep">XML Representation of Binding
Fault Reference Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.11.2.1
<a href="#Binding_Fault_Reference_ref_attribute">ref attribute
information item with infault or outfault [owner element]</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.11.2.2
<a href=
"#Binding_Fault_Reference_messageLabel_attribute">messageLabel
attribute information item with infault or outfault [owner
element]</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.11.2.3
<a href="#Binding_Fault_Reference_extension_elements">Binding Fault
Reference extension elements</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.11.3 <a href=
"#Binding_Fault_Reference_Mapping">Mapping Binding Fault
Reference's XML Representation to Component Properties</a>
<br />
&#160;&#160;&#160;&#160;2.12 <a href="#Service">Service</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.12.1 <a href=
"#Service_details">The Service Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.12.2 <a href=
"#Service_XMLRep">XML Representation of Service Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.12.2.1
<a href="#Service_name_attribute">name attribute information item
with service [owner element]</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.12.2.2
<a href="#Service_interface_attribute">interface attribute
information item with service [owner element]</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.12.3 <a href=
"#Service_Mapping">Mapping Service's XML Representation to
Component Properties</a>
<br />
&#160;&#160;&#160;&#160;2.13 <a href="#Endpoint">Endpoint</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.13.1 <a href=
"#Endpoint_details">The Endpoint Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.13.2 <a href=
"#Endpoint_XMLRep">XML Representation of Endpoint Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.13.2.1
<a href="#Endpoint_name_attribute">name attribute information item
with endpoint [owner element]</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.13.2.2
<a href="#Endpoint_binding_attribute">binding attribute information
item with endpoint [owner element]</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.13.2.3
<a href="#Endpoint_address_attribute">address attribute information
item with endpoint [owner element]</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.13.2.4
<a href="#Endpoint_extension_elements">Endpoint extension
elements</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;2.13.3 <a href=
"#Endpoint_Mapping">Mapping Endpoint's XML Representation to
Component Properties</a>
<br />
&#160;&#160;&#160;&#160;2.14 <a href="#simpletypes">XML Schema 1.0
Simple Types Used in the Component Model</a>
<br />
&#160;&#160;&#160;&#160;2.15 <a href="#compequiv">Equivalence of
Components</a>
<br />
&#160;&#160;&#160;&#160;2.16 <a href="#symbolspaces">Symbol
Spaces</a>
<br />
&#160;&#160;&#160;&#160;2.17 <a href="#qnameres">QName
resolution</a>
<br />
&#160;&#160;&#160;&#160;2.18 <a href="#uricompare">Comparing URIs
and IRIs</a>
<br />
3. <a href="#eii-types">Types</a>
<br />
&#160;&#160;&#160;&#160;3.1 <a href="#xsd-types">Using W3C XML
Schema Definition Language</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;3.1.1 <a href=
"#import-xsd">Importing XML Schema</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;3.1.1.1
<a href="#namespace-attribute">namespace attribute information
item</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;3.1.1.2
<a href="#schemaLocation-attribute">schemaLocation attribute
information item</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;3.1.2 <a href=
"#inlining-xsd">Inlining XML Schema</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;3.1.3 <a href=
"#references-definitions">References to Element Declarations and
Type Definitions</a>
<br />
&#160;&#160;&#160;&#160;3.2 <a href="#other-types">Using Other
Schema Languages</a>
<br />
&#160;&#160;&#160;&#160;3.3 <a href="#wsdlx-references">Describing
Messages that Refer to Services and Endpoints</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;3.3.1 <a href=
"#wsdlx-interface-aii">wsdlx:interface attribute information
item</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;3.3.2 <a href=
"#wsdlx-binding-aii">wsdlx:binding attribute information item</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;3.3.3 <a href=
"#wsdlx-consistency">wsdlx:interface and wsdlx:binding
Consistency</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;3.3.4 <a href=
"#wsdlx-xsanyuri">Use of wsdlx:interface and wsdlx:binding with
xs:anyURI</a>
<br />
4. <a href="#modularize">Modularizing WSDL 2.0 descriptions</a>
<br />
&#160;&#160;&#160;&#160;4.1 <a href="#includes">Including
Descriptions</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;4.1.1 <a href=
"#include_location_attribute">location attribute information item
with include [owner element]</a>
<br />
&#160;&#160;&#160;&#160;4.2 <a href="#imports">Importing
Descriptions</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;4.2.1 <a href=
"#import_namespace_attribute">namespace attribute information
item</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;4.2.2 <a href=
"#import_location_attribute">location attribute information item
with import [owner element]</a>
<br />
&#160;&#160;&#160;&#160;4.3 <a href=
"#extensions-and-modules">Extensions</a>
<br />
5. <a href="#eii-documentation">Documentation</a>
<br />
6. <a href="#language-extensibility">Language Extensibility</a>
<br />
&#160;&#160;&#160;&#160;6.1 <a href=
"#eii-extensibility">Element-based Extensibility</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;6.1.1 <a href=
"#mandatoryext">Mandatory extensions</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;6.1.2 <a href=
"#required-aii">required attribute information item</a>
<br />
&#160;&#160;&#160;&#160;6.2 <a href=
"#aii-extensibility">Attribute-based Extensibility</a>
<br />
&#160;&#160;&#160;&#160;6.3 <a href=
"#extensibility-semantics">Extensibility Semantics</a>
<br />
7. <a href="#wsdllocation">Locating WSDL 2.0 Documents</a>
<br />
&#160;&#160;&#160;&#160;7.1 <a href=
"#wsdlLocation-aii">wsdli:wsdlLocation attribute information
item</a>
<br />
8. <a href="#conformance">Conformance</a>
<br />
&#160;&#160;&#160;&#160;8.1 <a href="#infoset">XML Information Set
Conformance</a>
<br />
9. <a href="#Syntax-Summary">XML Syntax Summary (Non-Normative)</a>
<br />
10. <a href="#References">References</a>
<br />
&#160;&#160;&#160;&#160;10.1 <a href=
"#Normative-References">Normative References</a>
<br />
&#160;&#160;&#160;&#160;10.2 <a href=
"#Informative-References">Informative References</a>
<br /></p>
<h3><a name="appendices" id="appendices"></a>Appendices</h3>
<p class="toc">A. <a href="#ietf-draft">The application/wsdl+xml
Media Type</a>
<br />
&#160;&#160;&#160;&#160;A.1 <a href="#ietf-reg">Registration</a>
<br />
&#160;&#160;&#160;&#160;A.2 <a href="#frag-ids">Fragment
Identifiers</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;A.2.1 <a href=
"#wsdl.description">The Description Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;A.2.2 <a href=
"#wsdl.elementDeclaration">The Element Declaration Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;A.2.3 <a href=
"#wsdl.typeDefinition">The Type Definition Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;A.2.4 <a href=
"#wsdl.interface">The Interface Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;A.2.5 <a href=
"#wsdl.interfaceFault">The Interface Fault Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;A.2.6 <a href=
"#wsdl.interfaceOperation">The Interface Operation Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;A.2.7 <a href=
"#wsdl.interfaceMessageReference">The Interface Message Reference
Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;A.2.8 <a href=
"#wsdl.interfaceFaultReference">The Interface Fault Reference
Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;A.2.9 <a href=
"#wsdl.binding">The Binding Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;A.2.10 <a href=
"#wsdl.bindingFault">The Binding Fault Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;A.2.11 <a href=
"#wsdl.bindingOperation">The Binding Operation Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;A.2.12 <a href=
"#wsdl.bindingMessageReference">The Binding Message Reference
Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;A.2.13 <a href=
"#wsdl.bindingFaultReference">The Binding Fault Reference
Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;A.2.14 <a href=
"#wsdl.service">The Service Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;A.2.15 <a href=
"#wsdl.endpoint">The Endpoint Component</a>
<br />
&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;A.2.16 <a href=
"#wsdl.extension">Extension Components</a>
<br />
&#160;&#160;&#160;&#160;A.3 <a href="#ietf-sec">Security
considerations</a>
<br />
B. <a href="#acknowledgments">Acknowledgements</a> (Non-Normative)
<br />
C. <a href="#wsdl-iri-references">IRI-References for WSDL 2.0
Components</a> (Non-Normative)
<br />
&#160;&#160;&#160;&#160;C.1 <a href="#wsdl-iris">WSDL 2.0 IRIs</a>
<br />
&#160;&#160;&#160;&#160;C.2 <a href=
"#component-designator-canonical-form">Canonical Form for WSDL 2.0
Component Designators</a>
<br />
&#160;&#160;&#160;&#160;C.3 <a href="#Iri-ref-ex">Example</a>
<br />
D. <a href="#componentsummary">Component Summary</a>
(Non-Normative)
<br />
E. <a href="#assertionsummary">Assertion Summary</a>
(Non-Normative)
<br /></p>
</div>
<hr />
<div class="body">
<div class="div1">
<h2><a name="intro" id="intro"></a>1. Introduction</h2>
<p>Web Services Description Language Version 2.0 (WSDL 2.0)
provides a model and an XML format for describing Web services.
WSDL 2.0 enables one to separate the description of the abstract
functionality offered by a service from concrete details of a
service description such as “how” and “where” that functionality is
offered.</p>
<p>This specification defines a language for describing the
abstract functionality of a service as well as a framework for
describing the concrete details of a service description. It also
defines the conformance criteria for documents in this
language.</p>
<p>The companion specification, <em>Web Services Description
Language (WSDL) Version 2.0 Part 2: Adjuncts</em> [<cite><a href=
"#WSDL-PART2">WSDL 2.0 Adjuncts</a></cite>] describes extensions
for message exchange patterns, operation safety, operation styles
and binding extensions (for SOAP [<cite><a href=
"#SOAP12-PART1">SOAP 1.2 Part 1: Messaging Framework (Second
Edition)</a></cite>] and HTTP [<cite><a href="#RFC2616">IETF RFC
2616</a></cite>]).</p>
<div class="div2">
<h3><a name="intro_ws" id="intro_ws"></a>1.1 Service
Description</h3>
<p>WSDL 2.0 describes a Web service in two fundamental stages: one
abstract and one concrete. Within each stage, the description uses
a number of constructs to promote reusability of the description
and to separate independent design concerns.</p>
<p>At an abstract level, WSDL 2.0 describes a Web service in terms
of the messages it sends and receives; messages are described
independent of a specific wire format using a type system,
typically XML Schema.</p>
<p>An <em>operation</em> associates a message exchange pattern with
one or more messages. A <em>message exchange pattern</em>
identifies the sequence and cardinality of messages sent and/or
received as well as who they are logically sent to and/or received
from. An <em>interface</em> groups together operations without any
commitment to transport or wire format.</p>
<p>At a concrete level, a <em>binding</em> specifies transport and
wire format details for one or more interfaces. An
<em>endpoint</em> associates a network address with a binding. And
finally, a <em>service</em> groups together endpoints that
implement a common interface.</p>
</div>
<div class="div2">
<h3><a name="meaning" id="meaning"></a>1.2 The Meaning of a Service
Description</h3>
<p>A WSDL 2.0 service description indicates how potential clients
are intended to interact with the described service. It represents
an assertion that the described service fully implements and
conforms to what the WSDL 2.0 document describes. For example, as
further explained in section <a href="#mandatoryext"><strong>6.1.1
Mandatory extensions</strong></a>, if the WSDL 2.0 document
specifies a particular optional extension, the functionality
implied by that extension is only optional to the client. It must
be supported by the Web service.</p>
<p>A WSDL 2.0 interface describes potential interactions with a Web
service, not required interactions. The declaration of an operation
in a WSDL 2.0 interface is not an assertion that the interaction
described by the operation must occur. Rather it is an assertion
that if such an interaction is (somehow) initiated, then the
declared operation describes how that interaction is intended to
occur.</p>
</div>
<div class="div2">
<h3><a name="markup" id="markup"></a>1.3 Document Conformance</h3>
<p>An <em>element information item</em> (as defined in
[<cite><a href="#XMLInfoSet">XML Information Set</a></cite>]) whose
namespace name is "http://www.w3.org/ns/wsdl" and whose local part
is <code>description</code> conforms to this specification if it is
valid according to the XML Schema for that element as defined by
this specification (<a href=
"http://www.w3.org/2007/06/wsdl/wsdl20.xsd">http://www.w3.org/2007/06/wsdl/wsdl20.xsd</a>)
and additionally adheres to all the constraints contained in this
specification and conforms to the specifications of any extensions
contained in it. Such a conformant <em>element information
item</em> constitutes a <em>WSDL 2.0 document</em>.</p>
<p>The definition of the WSDL 2.0 language is based on the XML
Information Set [<cite><a href="#XMLInfoSet">XML Information
Set</a></cite>] but also imposes many semantic constraints over and
above structural conformance to this XML Infoset. In order to
precisely describe these constraints, and as an aid in precisely
defining the meaning of each WSDL 2.0 document, the WSDL 2.0
specification defines a component model <a href=
"#component_model"><strong>2. Component Model</strong></a> as an
additional layer of abstraction above the XML Infoset. Constraints
and meaning are defined in terms of this component model, and the
definition of each component includes a mapping that specifies how
values in the component model are derived from corresponding items
in the XML Infoset.</p>
<p>An XML 1.0 document that is valid with respect to the WSDL 2.0
XML Schema and that maps to a valid WSDL 2.0 Component Model is
conformant to the WSDL 2.0 specification.</p>
</div>
<div class="div2">
<h3><a name="notation" id="notation"></a>1.4 Notational
Conventions</h3>
<p>All parts of this specification are normative, with the
EXCEPTION of notes, pseudo-schemas, examples, and sections
explicitly marked as “Non-Normative”.</p>
<div class="div3">
<h4><a name="rfc2119keywords" id="rfc2119keywords"></a>1.4.1 RFC
2119 Keywords</h4>
<p>The keywords “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL
NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL”
in this document are to be interpreted as described in RFC 2119
[<cite><a href="#RFC2119">IETF RFC 2119</a></cite>].</p>
</div>
<div class="div3">
<h4><a name="rfc3986namespaces" id="rfc3986namespaces"></a>1.4.2
RFC 3986 Namespaces</h4>
<p>Namespace names of the general form:</p>
<ul>
<li>
<p>"http://example.org/..." and</p>
</li>
<li>
<p>"http://example.com/..."</p>
</li>
</ul>
<p>represent application or context-dependent URIs [<cite><a href=
"#RFC3986">IETF RFC 3986</a></cite>].</p>
</div>
<div class="div3">
<h4><a name="xmlSchemaAnyURI" id="xmlSchemaAnyURI"></a>1.4.3 XML
Schema anyURI</h4>
<p>This specification uses the XML Schema type
<code>xs:anyURI</code> (see [<cite><a href="#XMLSchemaP2">XML
Schema: Datatypes</a></cite>]). It is defined so that
<code>xs:anyURI</code> values are essentially IRIs (see
[<cite><a href="#RFC3987">IETF RFC 3987</a></cite>]). The
conversion from <code>xs:anyURI</code> values to an actual URI is
via an escaping procedure defined by (see [<cite><a href=
"#XLink">XLink 1.0</a></cite>]), which is identical in most
respects to IRI Section 3.1 (see [<cite><a href="#RFC3987">IETF RFC
3987</a></cite>]).</p>
<p>For interoperability, WSDL authors are advised to avoid the
US-ASCII characters: "&lt;", "&gt;", '"', space, "{", "}", "|",
"\", "^", and "`", which are allowed by the <code>xs:anyURI</code>
type, but disallowed in IRIs.</p>
</div>
<div class="div3">
<h4><a name="nsprefixes" id="nsprefixes"></a>1.4.4 Prefixes and
Namespaces Used in This Specification</h4>
<p>This specification uses predefined namespace prefixes
throughout; they are given in the following list. Note that the
choice of any namespace prefix is arbitrary and not semantically
significant (see [<cite><a href="#XMLNS">XML
Namespaces</a></cite>]).</p>
<a name="tabprefns" id="tabprefns"></a>
<table border="1" summary=
"Mapping of prefixes used in this document to their associated namespace name">
<caption>Table 1-1. Prefixes and Namespaces used in this
specification</caption>
<tbody>
<tr>
<th rowspan="1" colspan="1">Prefix</th>
<th rowspan="1" colspan="1">Namespace</th>
<th rowspan="1" colspan="1">Notes</th>
</tr>
<tr>
<td rowspan="1" colspan="1">wsdl</td>
<td rowspan="1" colspan="1">"http://www.w3.org/ns/wsdl"</td>
<td rowspan="1" colspan="1">Defined by this specification.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">wsdli</td>
<td rowspan="1" colspan="1">
"http://www.w3.org/ns/wsdl-instance"</td>
<td rowspan="1" colspan="1">Defined by this specification <a href=
"#wsdlLocation-aii"><strong>7.1 wsdli:wsdlLocation attribute
information item</strong></a>.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">wsdlx</td>
<td rowspan="1" colspan="1">
"http://www.w3.org/ns/wsdl-extensions"</td>
<td rowspan="1" colspan="1">Defined by this specification <a href=
"#wsdlx-references"><strong>3.3 Describing Messages that Refer to
Services and Endpoints</strong></a>.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">wrpc</td>
<td rowspan="1" colspan="1">"http://www.w3.org/ns/wsdl/rpc"</td>
<td rowspan="1" colspan="1">Defined by WSDL 2.0: Adjuncts
[<cite><a href="#WSDL-PART2">WSDL 2.0 Adjuncts</a></cite>].</td>
</tr>
<tr>
<td rowspan="1" colspan="1">wsoap</td>
<td rowspan="1" colspan="1">"http://www.w3.org/ns/wsdl/soap"</td>
<td rowspan="1" colspan="1">Defined by WSDL 2.0: Adjuncts
[<cite><a href="#WSDL-PART2">WSDL 2.0 Adjuncts</a></cite>].</td>
</tr>
<tr>
<td rowspan="1" colspan="1">whttp</td>
<td rowspan="1" colspan="1">"http://www.w3.org/ns/wsdl/http"</td>
<td rowspan="1" colspan="1">Defined by WSDL 2.0: Adjuncts
[<cite><a href="#WSDL-PART2">WSDL 2.0 Adjuncts</a></cite>].</td>
</tr>
<tr>
<td rowspan="1" colspan="1">xs</td>
<td rowspan="1" colspan="1">"http://www.w3.org/2001/XMLSchema"</td>
<td rowspan="1" colspan="1">Defined in the W3C XML Schema
specification [<cite><a href="#XMLSchemaP1">XML Schema:
Structures</a></cite>], [<cite><a href="#XMLSchemaP2">XML Schema:
Datatypes</a></cite>].</td>
</tr>
<tr>
<td rowspan="1" colspan="1">xsi</td>
<td rowspan="1" colspan="1">
"http://www.w3.org/2001/XMLSchema-instance"</td>
<td rowspan="1" colspan="1">Defined in the W3C XML Schema
specification [<cite><a href="#XMLSchemaP1">XML Schema:
Structures</a></cite>], [<cite><a href="#XMLSchemaP2">XML Schema:
Datatypes</a></cite>].</td>
</tr>
</tbody>
</table>

<br /></div>
<div class="div3">
<h4><a name="terminology" id="terminology"></a>1.4.5 Terms Used in
This Specification</h4>
<p>This section describes the terms and concepts introduced in Part
1 of the WSDL Version 2.0 specification (this document).</p>
<dl>
<dt class="label">Actual Value</dt>
<dd>
<p>As in [<cite><a href="#XMLSchemaP1">XML Schema:
Structures</a></cite>], the expression "actual value" 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 normalized value. This will often be a string,
but may also be an integer, a boolean, an IRI-reference, etc.</p>
</dd>
<dt class="label">Inlined Schema</dt>
<dd>
<p>An XML schema that is defined in the <code>wsdl:types</code>
<em>element information item</em> of a WSDL 2.0 description. For
example, an XML Schema defined in an <code>xs:schema</code>
<em>element information item</em> <a href=
"#inlining-xsd"><strong>3.1.2 Inlining XML Schema</strong></a>.</p>
</dd>
</dl>
</div>
<div class="div3">
<h4><a name="xmlinfosetproperties" id=
"xmlinfosetproperties"></a>1.4.6 XML Information Set
Properties</h4>
<p>This specification refers to properties in the XML Information
Set [<cite><a href="#XMLInfoSet">XML Information Set</a></cite>].
Such properties are denoted by square brackets, e.g. [children],
[attributes].</p>
</div>
<div class="div3">
<h4><a name="wsdlcomponentmodelproperties" id=
"wsdlcomponentmodelproperties"></a>1.4.7 WSDL 2.0 Component Model
Properties</h4>
<p>This specification defines and refers to properties in the WSDL
2.0 Component Model <a href="#component_model"><strong>2. Component
Model</strong></a>. Such properties are denoted by curly brackets,
e.g. {<a href="#property-Interface.name">name</a>}, {<a href=
"#property-Description.interfaces">interfaces</a>}.</p>
<p>This specification uses a consistent naming convention for
component model properties that refer to components. If a property
refers to a required or optional component, then the property name
is the same as the component name. If a property refers to a set of
components, then the property name is the pluralized form of the
component name.</p>
</div>
<div class="div3">
<h4><a name="znotation" id="znotation"></a>1.4.8 Z Notation</h4>
<p>Z Notation [<cite><a href="#ZNotationReferenceManual">Z Notation
Reference Manual</a></cite>] was used in the development of this
specification. Z Notation is a formal specification language that
is based on standard mathematical notation. The Z Notation for this
specification has been verified using the Fuzz 2000 type-checker
[<cite><a href="#Fuzz2000">Fuzz 2000</a></cite>].</p>
<p>Since Z Notation is not widely known, it is not included the
normative version of this specification. However, it is included in
a <a href="wsdl20-z.html">non-normative version</a> which allows to
dynamically hide and show the Z Notation. Browsers correctly
display the mathematical Unicode characters, provided that the
required fonts are installed. Mathematical fonts for Mozilla
Firefox can be downloaded from the <a href=
"http://www.mozilla.org/projects/mathml/fonts/">Mozilla Web
site</a>.</p>
<p>The Z Notation was used to improve the quality of the normative
text that defines the Component Model, and to help ensure that the
test suite covered all important rules implied by the Component
Model. However, the Z Notation is non-normative, so any conflict
between it and the normative text is an error in the Z Notation.
Readers and implementers may nevertheless find the Z Notation
useful in cases where the normative text is unclear.</p>
<p>There are two elements of Z Notation syntax that conflict with
the notational conventions described in the preceding sections. In
Z Notation, square brackets are used to introduce basic sets, e.g.
[<span class="zi">ID</span>], which conflicts with the use of
square brackets to denote XML Information Set properties <a href=
"#xmlinfosetproperties"><strong>1.4.6 XML Information Set
Properties</strong></a>. Also, in Z Notation, curly brackets are
used to denote set display and set comprehension, e.g.
{1<span class="zprefix">,</span> 2<span class="zprefix">,</span>
3}, which conflicts with the use of curly brackets to denote WSDL
2.0 Component Model properties <a href=
"#wsdlcomponentmodelproperties"><strong>1.4.7 WSDL 2.0 Component
Model Properties</strong></a>. However, the intended meaning of
square and curly brackets should be clear from their context and
this minor notational conflict should not cause any confusion.</p>
</div>
<div class="div3">
<h4><a name="bnfpseudoschemas" id="bnfpseudoschemas"></a>1.4.9 BNF
Pseudo-Schemas</h4>
<p>Pseudo-schemas are provided for each component, before the
description of the component. They use BNF-style conventions for
attributes and elements: "?" denotes optionality (i.e. zero or one
occurrences), "*" denotes zero or more occurrences, "+" one or more
occurrences, "[" and "]" are used to form groups, and "|"
represents choice. Attributes are conventionally assigned a value
which corresponds to their type, as defined in the normative
schema. Elements with simple content are conventionally assigned a
value which corresponds to the type of their content, as defined in
the normative schema. Pseudo schemas do not include extension
points for brevity.</p>
<div class="exampleInner">
<pre xml:space="preserve">
&lt;!-- sample pseudo-schema --&gt;
&lt;<strong>defined_element</strong>
      required_attribute_of_type_string="<em>xs:string</em>"
      optional_attribute_of_type_int="<em>xs:int</em>"? &gt;
  &lt;required_element /&gt;
  &lt;optional_element /&gt;?
  &lt;one_or_more_of_these_elements /&gt;+
  [ &lt;choice_1 /&gt; | &lt;choice_2 /&gt; ]*
&lt;/<strong>defined_element</strong>&gt;
</pre></div>
</div>
<div class="div3">
<h4><a name="assertions" id="assertions"></a>1.4.10 Assertions</h4>
<p>Assertions about WSDL 2.0 documents and components that are not
enforced by the normative XML schema for WSDL 2.0 are marked by a
dagger symbol (†) at the end of a sentence. Each assertion has been
assigned a unique identifier that consists of a descriptive textual
prefix and a unique numeric suffix. The numeric suffixes are
assigned sequentially and never reused so there may be gaps in the
sequence. The assertion identifiers MAY be used by implementations
of this specification for any purpose, e.g. error reporting.</p>
<p>The assertions and their identifiers are summarized in section
<a href="#assertionsummary"><strong>E. Assertion
Summary</strong></a>.</p>
</div>
</div>
</div>
<div class="div1">
<h2><a name="component_model" id="component_model"></a>2. Component
Model</h2>
<p>This section describes the conceptual model of WSDL 2.0 as a set
of components with attached properties, which collectively describe
a Web service. This model is called the <em>Component Model</em> of
WSDL 2.0. A <em>valid WSDL 2.0 component model</em> is a set of
WSDL 2.0 components and properties that satisfy all the
requirements given in this specification as indicated by keywords
whose interpretation is defined by RFC 2119 [<cite><a href=
"#RFC2119">IETF RFC 2119</a></cite>].</p>
<a name="zed-ComponentModel" id="zed-ComponentModel"></a>
<p>Components are typed collections of properties that correspond
to different aspects of Web services. Each subsection herein
describes a different type of component, its defined properties,
and its representation as an XML Infoset [<cite><a href=
"#XMLInfoSet">XML Information Set</a></cite>].</p>
<a name="zed-Component" id="zed-Component"></a><a name="zed-ID" id=
"zed-ID"></a><a name="zed-Identifier" id=
"zed-Identifier"></a><a name="zed-Id" id="zed-Id"></a><a name=
"zed-ComponentModel1" id="zed-ComponentModel1"></a><a name=
"zed-IdentifierValid" id="zed-IdentifierValid"></a><a name=
"zed-InterfaceComponents" id="zed-InterfaceComponents"></a><a name=
"zed-InterfaceComponentIds" id=
"zed-InterfaceComponentIds"></a><a name="zed-BindingComponents" id=
"zed-BindingComponents"></a><a name="zed-BindingComponentIds" id=
"zed-BindingComponentIds"></a><a name="zed-ServiceComponents" id=
"zed-ServiceComponents"></a><a name="zed-ServiceComponentIds" id=
"zed-ServiceComponentIds"></a><a name="zed-OtherComponents" id=
"zed-OtherComponents"></a><a name="zed-OtherComponentIds" id=
"zed-OtherComponentIds"></a><a name="zed-ComponentModel2" id=
"zed-ComponentModel2"></a><a name="zed-Base" id=
"zed-Base"></a><a name="zed-BaseValid" id=
"zed-BaseValid"></a><a name="zed-NestedBase" id=
"zed-NestedBase"></a><a name="zed-NestedBaseValid" id=
"zed-NestedBaseValid"></a>
<p>Properties are unordered and unique with respect to the
component they are associated with. Individual properties'
definitions may constrain their content (e.g., to a typed value,
another component, or a set of typed values or components), and
components may require the presence of a property to be considered
conformant. Such properties are marked as REQUIRED, whereas those
that are not required to be present are marked as OPTIONAL. By
convention, when specifying the mapping rules from the XML Infoset
representation of a component to the component itself, an optional
property that is absent in the component in question is described
as being “empty”. Unless otherwise specified, when a property is
identified as being a collection (a set or a list), its value may
be a 0-element (empty) collection. In order to simplify the
presentation of the rules that deal with sets of components, for
all OPTIONAL properties whose type is a set, the absence of such a
property from a component MUST be treated as semantically
equivalent to the presence of a property with the same name and
whose value is the empty set. In other words, every OPTIONAL
set-valued property MUST be assumed to have the empty set as its
default value, to be used in case the property is absent.</p>
<a name="zed-OPTIONAL" id="zed-OPTIONAL"></a>
<p>Component definitions are serializable in XML 1.0 format but are
independent of any particular serialization of the component model.
Component definitions use a subset (see <a href=
"#simpletypes"><strong>2.14 XML Schema 1.0 Simple Types Used in the
Component Model</strong></a>) of the simple types defined by the
XML Schema 1.0 specification [<cite><a href="#XMLSchemaP2">XML
Schema: Datatypes</a></cite>].</p>
<p>In addition to the direct XML Infoset representation described
here, the component model allows components external to the Infoset
through the mechanisms described in <a href=
"#modularize"><strong>4. Modularizing WSDL 2.0
descriptions</strong></a>.</p>
<p>A component model can be extracted from a given XML Infoset
which conforms to the XML Schema for WSDL 2.0 by recursively
mapping Information Items to their identified components, starting
with the <code>wsdl:description</code> <em>element information
item</em>. This includes the application of the mechanisms
described in <a href="#modularize"><strong>4. Modularizing WSDL 2.0
descriptions</strong></a>.</p>
<p>This document does not specify a means of producing an XML
Infoset representation from a component model instance. In
particular, there are in general many valid ways to modularize a
given component model instance into one or more XML Infosets.</p>
<div class="div2">
<h3><a name="Description" id="Description"></a>2.1 Description</h3>
<div class="div3">
<h4><a name="Description_details" id=
"Description_details"></a>2.1.1 The Description Component</h4>
<p>At a high level, the <a href=
"#component-Description">Description</a> component is just a
container for two categories of components: WSDL 2.0 components and
type system components.</p>
<p>WSDL 2.0 components are interfaces, bindings and services. Type
system components are element declarations and type
definitions.</p>
<p>Type system components describe the constraints on a message's
content. By default, these constraints are expressed in terms of
the [<cite><a href="#XMLInfoSet">XML Information Set</a></cite>],
i.e. they define the [local name], [namespace name], [children] and
[attributes] properties of an <em>element information item</em>.
Type systems based upon other data models are generally
accommodated by extensions to WSDL 2.0; see <a href=
"#language-extensibility"><strong>6. Language
Extensibility</strong></a>. In the case where they define
information equivalent to that of a XML Schema global element
declaration, they can be treated as if they were such a
declaration.</p>
<p>This specification does not define the behavior of a WSDL 2.0
document that uses multiple schema languages for describing type
system components simultaneously.</p>
<a name="zed-ElementContentModel" id="zed-ElementContentModel"></a>
<p>An <a name="component-ElementDeclaration" id=
"component-ElementDeclaration">Element Declaration</a> component
defines the name and content model of an <em>element information
item</em> such as that defined by an XML Schema global element
declaration. It has a {<a name="property-ElementDeclaration.name"
id="property-ElementDeclaration.name">name</a>} property that is
the QName of the <em>element information item</em> and a {<a name=
"property-ElementDeclaration.system" id=
"property-ElementDeclaration.system">system</a>} property that is
the namespace IRI of the extension <em>element information
item</em>s for the type system, e.g. the namespace of XML
Schema.</p>
<a name="zed-ElementDeclaration" id=
"zed-ElementDeclaration"></a><a name="zed-ElementDeclarationCM" id=
"zed-ElementDeclarationCM"></a>
<p>A <a name="component-TypeDefinition" id=
"component-TypeDefinition">Type Definition</a> component defines
the content model of an <em>element information item</em> such as
that defined by an XML Schema global type definition. It has a
{<a name="property-TypeDefinition.name" id=
"property-TypeDefinition.name">name</a>} property that is the QName
of the type and a {<a name="property-TypeDefinition.system" id=
"property-TypeDefinition.system">system</a>} property that is the
namespace IRI of the extension <em>element information item</em>s
for the type system, e.g. the namespace of XML Schema.</p>
<a name="zed-TypeDefinition" id="zed-TypeDefinition"></a><a name=
"zed-TypeDefinitionCM" id="zed-TypeDefinitionCM"></a>
<p><a href="#component-Interface">Interface</a>, <a href=
"#component-Binding">Binding</a>, <a href=
"#component-Service">Service</a>, <a href=
"#component-ElementDeclaration">Element Declaration</a>, and
<a href="#component-TypeDefinition">Type Definition</a> components
are directly contained in the <a href=
"#component-Description">Description</a> component and are referred
to as <em>top-level components</em>. The top-level WSDL 2.0
components contain other components, e.g. <a href=
"#component-InterfaceOperation">Interface Operation</a> and
<a href="#component-Endpoint">Endpoint</a>, which are referred to
as <em>nested components</em>. Nested components may contain other
nested components. The component that contains a nested component
is referred to as the <em>parent</em> of the nested component.
Nested components have a {<a name="property-.parent" id=
"property-.parent">parent</a>} property that is a reference to
their parent component.</p>
<a name="zed-TopLevelComponent" id=
"zed-TopLevelComponent"></a><a name="zed-Name" id=
"zed-Name"></a><a name="zed-Parent" id="zed-Parent"></a><a name=
"zed-ParentValid" id="zed-ParentValid"></a><a name=
"zed-NestedComponent" id="zed-NestedComponent"></a><a name=
"zed-ParentId" id="zed-ParentId"></a>
<p>The properties of the <a name="component-Description" id=
"component-Description">Description</a> component are as
follows:</p>
<ul>
<li>
<p>{<a name="property-Description.interfaces" id=
"property-Description.interfaces">interfaces</a>} OPTIONAL. A set
of <a href="#component-Interface">Interface</a> components.</p>
</li>
<li>
<p>{<a name="property-Description.bindings" id=
"property-Description.bindings">bindings</a>} OPTIONAL. A set of
<a href="#component-Binding">Binding</a> components.</p>
</li>
<li>
<p>{<a name="property-Description.services" id=
"property-Description.services">services</a>} OPTIONAL. A set of
<a href="#component-Service">Service</a> components.</p>
</li>
<li>
<p>{<a name="property-Description.elementdeclarations" id=
"property-Description.elementdeclarations">element
declarations</a>} OPTIONAL. A set of <a href=
"#component-ElementDeclaration">Element Declaration</a>
components.</p>
</li>
<li>
<p>{<a name="property-Description.typedefinitions" id=
"property-Description.typedefinitions">type definitions</a>}
REQUIRED. A set of <a href="#component-TypeDefinition">Type
Definition</a> components.</p>
</li>
</ul>
<a name="zed-Description" id="zed-Description"></a><a name=
"zed-stringTD..." id="zed-stringTD..."></a><a name=
"zed-BuiltInTypeDefComps" id="zed-BuiltInTypeDefComps"></a><a name=
"zed-XMLSchemaURI" id="zed-XMLSchemaURI"></a><a name=
"zed-BuiltInTypeDefIds" id="zed-BuiltInTypeDefIds"></a><a name=
"zed-DescriptionTypeDefs" id="zed-DescriptionTypeDefs"></a><a name=
"zed-DescriptionKey" id="zed-DescriptionKey"></a><a name=
"zed-DescriptionCM" id="zed-DescriptionCM"></a>
<p>The set of top-level components contained in the <a href=
"#component-Description">Description</a> component associated with
an initial WSDL 2.0 document consists of the components defined in
the initial document, plus the components associated with the WSDL
2.0 documents that the initial document includes, plus the
components defined by other WSDL 2.0 documents in the namespaces
that the initial document imports. The component model makes no
distinction between the components that are defined in the initial
document versus those that are defined in the included documents or
imported namespaces. However, any WSDL 2.0 document that contains
component definitions that refer by QName to WSDL 2.0 components
that belong to a different namespace MUST contain a
<code>wsdl:import</code> <em>element information item</em> for that
namespace (see <a href="#imports"><strong>4.2 Importing
Descriptions</strong></a> ). Furthermore, all QName references,
whether to the same or to different namespaces must resolve to
components (see <a href="#qnameres"><strong>2.17 QName
resolution</strong></a> ).</p>
<p>When using the XML Schema language to describe type system
components, the inclusion of <a href=
"#component-ElementDeclaration">Element Declaration</a> components
and <a href="#component-TypeDefinition">Type Definition</a>
components in a <a href="#component-Description">Description</a>
component is governed by the rules in <a href=
"#xsd-types"><strong>3.1 Using W3C XML Schema Definition
Language</strong></a>.</p>
<p>In addition to WSDL 2.0 components and type system components,
additional extension components MAY be added via extensibility
<a href="#language-extensibility"><strong>6. Language
Extensibility</strong></a>. Further, additional properties to WSDL
2.0 and type system components MAY also be added via
extensibility.</p>
</div>
<div class="div3">
<h4><a name="Description_XMLRep" id="Description_XMLRep"></a>2.1.2
XML Representation of Description Component</h4>
<div class="exampleInner">
<pre xml:space="preserve">
&lt;<strong>description</strong>
      targetNamespace="<em>xs:anyURI</em>" &gt;
  &lt;documentation /&gt;*
  [ &lt;import /&gt; | &lt;include /&gt; ]*
  &lt;types /&gt;?
  [ &lt;interface /&gt; | &lt;binding /&gt; | &lt;service /&gt; ]*
&lt;/<strong>description</strong>&gt;
</pre></div>
<p>WSDL 2.0 descriptions are represented in XML by one or more WSDL
2.0 Information Sets (Infosets), that is one or more
<code>description</code> <em>element information item</em>s. A WSDL
2.0 Infoset contains representations for a collection of WSDL 2.0
components that share a common target namespace and zero or more
<code>wsdl:import</code> <em>element information item</em>s
<a href="#imports"><strong>4.2 Importing Descriptions</strong></a>
that correspond to a collection with components from multiple
target namespaces.</p>
<p>The components directly defined or included within a <a href=
"#component-Description">Description</a> component are said to
belong to the same <em>target namespace</em>. The target namespace
therefore groups a set of related component definitions and
represents an unambiguous name for the intended semantics of the
collection of components. <span id="Description-1001" class=
"test-assertion-tr">The value of the <code>targetNamespace</code>
<em>attribute information item</em> SHOULD be
dereferencable.<sup><a href="#Description-1001-summary" title=
"Link to assertion Description-1001 summary">†</a></sup></span>
<span id="Description-1002" class="test-assertion-tr">It SHOULD
resolve to a human or machine processable document that directly or
indirectly defines the intended semantics of those
components.<sup><a href="#Description-1002-summary" title=
"Link to assertion Description-1002 summary">†</a></sup></span>
<span id="Description-1003" class="test-assertion-tr">It MAY
resolve to a WSDL 2.0 document that provides service description
information for that namespace.<sup><a href=
"#Description-1003-summary" title=
"Link to assertion Description-1003 summary">†</a></sup></span></p>
<p><span id="Description-1004" class="test-assertion-tr">If a WSDL
2.0 document is split into multiple WSDL 2.0 documents (which may
be combined as needed via <a href="#includes"><strong>4.1 Including
Descriptions</strong></a>), then the <code>targetNamespace</code>
<em>attribute information item</em> SHOULD resolve to a master WSDL
2.0 document that includes all the WSDL 2.0 documents needed for
that service description.<sup><a href="#Description-1004-summary"
title=
"Link to assertion Description-1004 summary">†</a></sup></span>
This approach enables the WSDL 2.0 component designator fragment
identifiers to be properly resolved.</p>
<p>Components that belong to imported namespaces have different
target namespace values than that of the importing WSDL 2.0
document. Thus importing is the mechanism to use components from
one namespace in the definition of components from another
namespace.</p>
<p>Note that each WSDL 2.0 document or type system component of the
same kind must be uniquely identified by its qualified name. That
is, if two distinct components of the same kind (<a href=
"#component-Interface">Interface</a>, <a href=
"#component-Binding">Binding</a>, etc.) are in the same target
namespace, then their QNames MUST be unique. However, different
kinds of components (e.g., an <a href=
"#component-Interface">Interface</a> component and a <a href=
"#component-Binding">Binding</a> component) MAY have the same
QName. Thus, QNames of components must be unique within the space
of those components in a given target namespace.</p>
<p>The <code>description</code> <em>element information item</em>
has the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>description</code>.</p>
</li>
<li>
<p>A [namespace name] of "http://www.w3.org/ns/wsdl".</p>
</li>
<li>
<p>One or more <em>attribute information item</em>s amongst its
[attributes] as follows:</p>
<ul>
<li>
<p>A REQUIRED <code>targetNamespace</code> <em>attribute
information item</em> as described below in <a href=
"#Description_targetnamespace_attribute"><strong>2.1.2.1
targetNamespace attribute information item</strong></a>.</p>
</li>
<li>
<p>Zero or more namespace qualified <em>attribute information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl".</p>
</li>
</ul>
</li>
<li>
<p><span id="Description-1005" class="test-assertion-tr">Zero or
more <em>element information item</em>s amongst its [children], in
order as follows:<sup><a href="#Description-1005-summary" title=
"Link to assertion Description-1005 summary">†</a></sup></span></p>
<ol class="enumar">
<li>
<p>Zero or more <code>documentation</code> <em>element information
item</em>s (see <a href="#eii-documentation"><strong>5.
Documentation</strong></a>).</p>
</li>
<li>
<p>Zero or more <em>element information item</em>s from among the
following, in any order:</p>
<ul>
<li>
<p>Zero or more <code>include</code> <em>element information
item</em>s (see <a href="#includes"><strong>4.1 Including
Descriptions</strong></a>)</p>
</li>
<li>
<p>Zero or more <code>import</code> <em>element information
item</em>s (see <a href="#imports"><strong>4.2 Importing
Descriptions</strong></a>)</p>
</li>
<li>
<p>Zero or more namespace-qualified <em>element information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl".</p>
</li>
</ul>
</li>
<li>
<p>An OPTIONAL <code>types</code> <em>element information item</em>
(see <a href="#eii-types"><strong>3. Types</strong></a>).</p>
</li>
<li>
<p>Zero or more <em>element information item</em>s from among the
following, in any order:</p>
<ul>
<li>
<p><code>interface</code> <em>element information item</em>s (see
<a href="#Interface_XMLRep"><strong>2.2.2 XML Representation of
Interface Component</strong></a>).</p>
</li>
<li>
<p><code>binding</code> <em>element information item</em>s (see
<a href="#Binding_XMLRep"><strong>2.7.2 XML Representation of
Binding Component</strong></a>).</p>
</li>
<li>
<p><code>service</code> <em>element information item</em>s (see
<a href="#Service_XMLRep"><strong>2.12.2 XML Representation of
Service Component</strong></a>).</p>
</li>
<li>
<p>Zero or more namespace-qualified <em>element information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl".</p>
</li>
</ul>
</li>
</ol>
</li>
</ul>
<div class="div4">
<h5><a name="Description_targetnamespace_attribute" id=
"Description_targetnamespace_attribute"></a>2.1.2.1
<code>targetNamespace</code> <em>attribute information
item</em></h5>
<p>The <code>targetNamespace</code> <em>attribute information
item</em> defines the namespace affiliation of top-level components
defined in this <code>description</code> <em>element information
item</em>. <a href="#component-Interface">Interface</a>, <a href=
"#component-Binding">Binding</a> and <a href=
"#component-Service">Service</a> are top-level components.</p>
<p>The <code>targetNamespace</code> <em>attribute information
item</em> has the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>targetNamespace</code></p>
</li>
<li>
<p>A [namespace name] which has no value</p>
</li>
</ul>
<p>The type of the <code>targetNamespace</code> <em>attribute
information item</em> is <em>xs:anyURI</em>. <span id=
"Description-1006" class="test-assertion-tr">Its value MUST be an
absolute IRI (see [<cite><a href="#RFC3987">IETF RFC
3987</a></cite>]) and should be dereferencable.<sup><a href=
"#Description-1006-summary" title=
"Link to assertion Description-1006 summary">†</a></sup></span></p>
</div>
</div>
<div class="div3">
<h4><a name="Description_Mapping" id=
"Description_Mapping"></a>2.1.3 Mapping Description's XML
Representation to Component Properties</h4>
<p>The mapping from the XML Representation of the
<code>description</code> <em>element information item</em> (see
<a href="#Description_XMLRep"><strong>2.1.2 XML Representation of
Description Component</strong></a>) to the properties of the
<a href="#component-Description">Description</a> component is
described in <a href="#tab_Description_Mapping">Table 2-1</a>.</p>
<a name="tab_Description_Mapping" id="tab_Description_Mapping"></a>
<table border="1">
<caption>Table 2-1. Mapping from XML Representation to Description
Component Properties</caption>
<col width="20%" span="1" />
<col width="80%" span="1" />
<tbody>
<tr>
<th rowspan="1" colspan="1">Property</th>
<th rowspan="1" colspan="1">Value</th>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-Description.interfaces">interfaces</a>}</td>
<td rowspan="1" colspan="1">The set of <a href=
"#component-Interface">Interface</a> components corresponding to
all the <code>interface</code> <em>element information item</em>s
in the [children] of the <code>description</code> <em>element
information item</em>, if any, plus any included (via
<code>wsdl:include</code>) or imported (via
<code>wsdl:import</code>) <a href=
"#component-Interface">Interface</a> components (see <a href=
"#modularize"><strong>4. Modularizing WSDL 2.0
descriptions</strong></a>).</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-Description.bindings">bindings</a>}</td>
<td rowspan="1" colspan="1">The set of <a href=
"#component-Binding">Binding</a> components corresponding to all
the <code>binding</code> <em>element information item</em>s in the
[children] of the <code>description</code> <em>element information
item</em>, if any, plus any included (via
<code>wsdl:include</code>) or imported (via
<code>wsdl:import</code>) <a href="#component-Binding">Binding</a>
components (see <a href="#modularize"><strong>4. Modularizing WSDL
2.0 descriptions</strong></a>).</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-Description.services">services</a>}</td>
<td rowspan="1" colspan="1">The set of <a href=
"#component-Service">Service</a> components corresponding to all
the <code>service</code> <em>element information item</em>s in the
[children] of the <code>description</code> <em>element information
item</em>, if any, plus any included (via
<code>wsdl:include</code>) or imported (via
<code>wsdl:import</code>) <a href="#component-Service">Service</a>
components (see <a href="#modularize"><strong>4. Modularizing WSDL
2.0 descriptions</strong></a>).</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-Description.elementdeclarations">element
declarations</a>}</td>
<td rowspan="1" colspan="1">The set of <a href=
"#component-ElementDeclaration">Element Declaration</a> components
corresponding to all the element declarations defined as
descendants of the <code>types</code> <em>element information
item</em>, if any, plus any included (via <code>xs:include</code>)
or imported (via <code>xs:import</code>) <a href=
"#component-ElementDeclaration">Element Declaration</a> components.
At a minimum this will include all the global element declarations
defined by XML Schema <code>element</code> <em>element information
item</em>s. It MAY also include any declarations from some other
type system which describes the [local name], [namespace name],
[attributes] and [children] properties of an <em>element
information item</em>. <span id="Types-1007" class=
"test-assertion-tr">Each XML Schema element declaration MUST have a
unique QName.<sup><a href="#Types-1007-summary" title=
"Link to assertion Types-1007 summary">†</a></sup></span></td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-Description.typedefinitions">type definitions</a>}</td>
<td rowspan="1" colspan="1">The set of <a href=
"#component-TypeDefinition">Type Definition</a> components
corresponding to all the type definitions defined as descendants of
the <code>types</code> <em>element information item</em>, if any,
plus any included (via <code>xs:include</code>) or imported (via
<code>xs:import</code>) <a href="#component-TypeDefinition">Type
Definition</a> components. In addition, the built-in datatypes
defined by XML Schema Part 2: Datatypes Second Edition
[<cite><a href="#XMLSchemaP2">XML Schema: Datatypes</a></cite>],
namely the nineteen primitive datatypes <code>xs:string</code>,
<code>xs:boolean</code>, <code>xs:decimal</code>,
<code>xs:float</code>, <code>xs:double</code>,
<code>xs:duration</code>, <code>xs:dateTime</code>,
<code>xs:time</code>, <code>xs:date</code>,
<code>xs:gYearMonth</code>, <code>xs:gYear</code>,
<code>xs:gMonthDay</code>, <code>xs:gDay</code>,
<code>xs:gMonth</code>, <code>xs:hexBinary</code>,
<code>xs:base64Binary</code>, <code>xs:anyURI</code>,
<code>xs:QName</code>, <code>xs:NOTATION</code>, and the
twenty-five derived datatypes <code>xs:normalizedString</code>,
<code>xs:token</code>, <code>xs:language</code>,
<code>xs:NMTOKEN</code>, <code>xs:NMTOKENS</code>,
<code>xs:Name</code>, <code>xs:NCName</code>, <code>xs:ID</code>,
<code>xs:IDREF</code>, <code>xs:IDREFS</code>,
<code>xs:ENTITY</code>, <code>xs:ENTITIES</code>,
<code>xs:integer</code>, <code>xs:nonPositiveInteger</code>,
<code>xs:negativeInteger</code>, <code>xs:long</code>,
<code>xs:int</code>, <code>xs:short</code>, <code>xs:byte</code>,
<code>xs:nonNegativeInteger</code>, <code>xs:unsignedLong</code>,
<code>xs:unsignedInt</code>, <code>xs:unsignedShort</code>,
<code>xs:unsignedByte</code>, <code>xs:positiveInteger</code>. The
set MAY also include any definitions from some other type system
which describes the [attributes] and [children] properties of an
<em>element information item</em>. <span id="Types-1008" class=
"test-assertion-tr">Each XML Schema type definition MUST have a
unique QName.<sup><a href="#Types-1008-summary" title=
"Link to assertion Types-1008 summary">†</a></sup></span></td>
</tr>
</tbody>
</table>

<br /></div>
</div>
<div class="div2">
<h3><a name="Interface" id="Interface"></a>2.2 Interface</h3>
<div class="div3">
<h4><a name="Interface_details" id="Interface_details"></a>2.2.1
The Interface Component</h4>
<p>An <a href="#component-Interface">Interface</a> component
describes sequences of messages that a service sends and/or
receives. It does this by grouping related messages into
operations. An operation is a sequence of input and output
messages, and an interface is a set of operations.</p>
<p>An interface can optionally extend one or more other interfaces.
<span id="Interface-1009" class="test-assertion-tr">To avoid
circular definitions, an interface MUST NOT appear in the set of
interfaces it extends, either directly or indirectly. <sup><a href=
"#Interface-1009-summary" title=
"Link to assertion Interface-1009 summary">†</a></sup></span> The
set of operations available in an interface includes all the
operations defined by the interfaces it extends directly or
indirectly, together with any operations it directly defines. The
operations directly defined on an interface are referred to as the
<em>declared</em> operations of the interface. In the process,
operation components that are equivalent per <a href=
"#compequiv"><strong>2.15 Equivalence of Components</strong></a>
are treated as one single component. The interface extension
mechanism behaves in a similar way for all other components that
can be defined inside an interface, namely <a href=
"#component-InterfaceFault">Interface Fault</a> components.</p>
<p>Interfaces are named constructs and can be referred to by QName
(see <a href="#qnameres"><strong>2.17 QName
resolution</strong></a>). For instance, <a href=
"#component-Binding">Binding</a> components refer to interfaces in
this way.</p>
<p>The properties of the <a name="component-Interface" id=
"component-Interface">Interface</a> component are as follows:</p>
<ul>
<li>
<p>{<a name="property-Interface.name" id=
"property-Interface.name">name</a>} REQUIRED. An
<em>xs:QName</em>.</p>
</li>
<li>
<p>{<a name="property-Interface.extendedinterfaces" id=
"property-Interface.extendedinterfaces">extended interfaces</a>}
OPTIONAL. A set of declared <a href=
"#component-Interface">Interface</a> components which this
interface extends.</p>
</li>
<li>
<p>{<a name="property-Interface.interfacefaults" id=
"property-Interface.interfacefaults">interface faults</a>}
OPTIONAL. The set of declared <a href=
"#component-InterfaceFault">Interface Fault</a> components. Note
that the namespace name of the {<a href=
"#property-InterfaceFault.name">name</a>} property of each <a href=
"#component-InterfaceFault">Interface Fault</a> in this set is the
same as the namespace name of the {<a href=
"#property-Interface.name">name</a>} property of this <a href=
"#component-Interface">Interface</a> component.</p>
</li>
<li>
<p>{<a name="property-Interface.interfaceoperations" id=
"property-Interface.interfaceoperations">interface operations</a>}
OPTIONAL. A set of declared <a href=
"#component-InterfaceOperation">Interface Operation</a> components.
Note that the namespace name of the {<a href=
"#property-InterfaceOperation.name">name</a>} property of each
<a href="#component-InterfaceOperation">Interface Operation</a> in
this set is the same as the namespace name of the {<a href=
"#property-Interface.name">name</a>} property of this <a href=
"#component-Interface">Interface</a> component.</p>
</li>
</ul>
<a name="zed-Interface" id="zed-Interface"></a><a name=
"zed-InterfaceRI" id="zed-InterfaceRI"></a>
<p><span id="Interface-1010" class="test-assertion-tr">For each
<a href="#component-Interface">Interface</a> component in the
{<a href="#property-Description.interfaces">interfaces</a>}
property of a <a href="#component-Description">Description</a>
component, the {<a href="#property-Interface.name">name</a>}
property MUST be unique.<sup><a href="#Interface-1010-summary"
title=
"Link to assertion Interface-1010 summary">†</a></sup></span></p>
<a name="zed-InterfaceKey" id="zed-InterfaceKey"></a><a name=
"zed-InterfaceParent" id="zed-InterfaceParent"></a><a name=
"zed-InterfaceAllExtendedInterfaces" id=
"zed-InterfaceAllExtendedInterfaces"></a><a name=
"zed-InterfaceExtendsAcyclic" id=
"zed-InterfaceExtendsAcyclic"></a><a name=
"zed-InterfaceAllInterfaceOperations" id=
"zed-InterfaceAllInterfaceOperations"></a><a name=
"zed-InterfaceAllInterfaceFaults" id=
"zed-InterfaceAllInterfaceFaults"></a><a name="zed-InterfaceCM" id=
"zed-InterfaceCM"></a></div>
<div class="div3">
<h4><a name="Interface_XMLRep" id="Interface_XMLRep"></a>2.2.2 XML
Representation of Interface Component</h4>
<div class="exampleInner">
<pre xml:space="preserve">
&lt;description&gt;
  &lt;<strong>interface</strong>
        name="<em>xs:NCName</em>" 
        extends="<em>list of xs:QName</em>"?
        styleDefault="<em>list of xs:anyURI</em>"? &gt;
    &lt;documentation /&gt;*
    [ &lt;fault /&gt; | &lt;operation /&gt; ]*
  &lt;/<strong>interface</strong>&gt;
&lt;/description&gt;
</pre></div>
<p>The XML representation for an <a href=
"#component-Interface">Interface</a> component is an <em>element
information item</em> with the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>interface</code></p>
</li>
<li>
<p>A [namespace name] of "http://www.w3.org/ns/wsdl"</p>
</li>
<li>
<p>One or more <em>attribute information item</em>s amongst its
[attributes] as follows:</p>
<ul>
<li>
<p>A REQUIRED <code>name</code> <em>attribute information item</em>
as described below in <a href=
"#Interface_name_attribute"><strong>2.2.2.1 name attribute
information item with interface [owner element]</strong></a>.</p>
</li>
<li>
<p>An OPTIONAL <code>extends</code> <em>attribute information
item</em> as described below in <a href=
"#Interface_extends_attribute"><strong>2.2.2.2 extends attribute
information item</strong></a>.</p>
</li>
<li>
<p>An OPTIONAL <code>styleDefault</code> <em>attribute information
item</em> as described below in <a href=
"#Interface_styleDefault_attribute"><strong>2.2.2.3 styleDefault
attribute information item</strong></a>.</p>
</li>
<li>
<p>Zero or more namespace qualified <em>attribute information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl".</p>
</li>
</ul>
</li>
<li>
<p>Zero or more <em>element information item</em>s amongst its
[children], in order, as follows:</p>
<ol class="enumar">
<li>
<p>Zero or more <code>documentation</code> <em>element information
item</em>s (see <a href="#eii-documentation"><strong>5.
Documentation</strong></a>).</p>
</li>
<li>
<p>Zero or more <em>element information item</em>s from among the
following, in any order:</p>
<ul>
<li>
<p>Zero or more <code>fault</code> <em>element information
item</em>s <a href="#InterfaceFault_XMLRep"><strong>2.3.2 XML
Representation of Interface Fault Component</strong></a>.</p>
</li>
<li>
<p>Zero or more <code>operation</code> <em>element information
item</em>s <a href="#InterfaceOperation_XMLRep"><strong>2.4.2 XML
Representation of Interface Operation Component</strong></a>.</p>
</li>
<li>
<p>Zero or more namespace-qualified <em>element information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl".</p>
</li>
</ul>
</li>
</ol>
</li>
</ul>
<div class="div4">
<h5><a name="Interface_name_attribute" id=
"Interface_name_attribute"></a>2.2.2.1 <code>name</code>
<em>attribute information item</em> with <code>interface</code>
[owner element]</h5>
<p>The <code>name</code> <em>attribute information item</em>
together with the <code>targetNamespace</code> <em>attribute
information item</em> of the [parent] <code>description</code>
<em>element information item</em> forms the QName of the
interface.</p>
<p>The <code>name</code> <em>attribute information item</em> has
the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>name</code></p>
</li>
<li>
<p>A [namespace name] which has no value</p>
</li>
</ul>
<p>The type of the <code>name</code> <em>attribute information
item</em> is <em>xs:NCName</em>.</p>
</div>
<div class="div4">
<h5><a name="Interface_extends_attribute" id=
"Interface_extends_attribute"></a>2.2.2.2 <code>extends</code>
<em>attribute information item</em></h5>
<p>The <code>extends</code> <em>attribute information item</em>
lists the interfaces that this interface derives from.</p>
<p>The <code>extends</code> <em>attribute information item</em> has
the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>extends</code></p>
</li>
<li>
<p>A [namespace name] which has no value</p>
</li>
</ul>
<p>The type of the <code>extends</code> <em>attribute information
item</em> is a whitespace-separated list of <em>xs:QName</em>.</p>
<p><span id="Interface-1011" class="test-assertion-tr">The list of
<em>xs:QName</em> in an <code>extends</code> <em>attribute
information item</em> MUST NOT contain duplicates.<sup><a href=
"#Interface-1011-summary" title=
"Link to assertion Interface-1011 summary">†</a></sup></span></p>
</div>
<div class="div4">
<h5><a name="Interface_styleDefault_attribute" id=
"Interface_styleDefault_attribute"></a>2.2.2.3
<code>styleDefault</code> <em>attribute information item</em></h5>
<p>The <code>styleDefault</code> <em>attribute information
item</em> indicates the default style (see <a href=
"#InterfaceOperationStyle"><strong>2.4.1.2 Operation
Style</strong></a>) used to construct the {<a href=
"#property-InterfaceMessageReference.elementdeclaration">element
declaration</a>} properties of {<a href=
"#property-InterfaceOperation.interfacemessagereferences">interface
message references</a>} of all operations contained within the
[owner element] <code>interface</code>.</p>
<p>The <code>styleDefault</code> <em>attribute information
item</em> has the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>styleDefault.</code></p>
</li>
<li>
<p>A [namespace name] which has no value.</p>
</li>
</ul>
<p>The type of the <code>styleDefault</code> <em>attribute
information item</em> is <em>list of xs:anyURI</em>. <span id=
"Interface-1012" class="test-assertion-tr">Its value, if present,
MUST contain absolute IRIs (see [<cite><a href="#RFC3987">IETF RFC
3987</a></cite>]).<sup><a href="#Interface-1012-summary" title=
"Link to assertion Interface-1012 summary">†</a></sup></span></p>
</div>
</div>
<div class="div3">
<h4><a name="Interface_Mapping" id="Interface_Mapping"></a>2.2.3
Mapping Interface's XML Representation to Component Properties</h4>
<p>The mapping from the XML Representation of the
<code>interface</code> <em>element information item</em> (see
<a href="#Interface_XMLRep"><strong>2.2.2 XML Representation of
Interface Component</strong></a>) to the properties of the <a href=
"#component-Interface">Interface</a> component is as described in
<a href="#tab_Interface_Mapping">Table 2-2</a>.</p>
<a name="tab_Interface_Mapping" id="tab_Interface_Mapping"></a>
<table border="1">
<caption>Table 2-2. Mapping from XML Representation to Interface
Component Properties</caption>
<col width="20%" span="1" />
<col width="80%" span="1" />
<tbody>
<tr>
<th rowspan="1" colspan="1">Property</th>
<th rowspan="1" colspan="1">Value</th>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-Interface.name">name</a>}</td>
<td rowspan="1" colspan="1">The QName whose local name is actual
value of the <code>name</code> <em>attribute information item</em>
and whose namespace name is the actual value of the
<code>targetNamespace</code> <em>attribute information item</em> of
the [parent] <code>description</code> <em>element information
item</em></td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-Interface.extendedinterfaces">extended
interfaces</a>}</td>
<td rowspan="1" colspan="1">The set of <a href=
"#component-Interface">Interface</a> components resolved to by the
values in the <code>extends</code> <em>attribute information
item</em>, if any (see <a href="#qnameres"><strong>2.17 QName
resolution</strong></a>).</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-Interface.interfacefaults">interface faults</a>}</td>
<td rowspan="1" colspan="1">The set of <a href=
"#component-InterfaceFault">Interface Fault</a> components
corresponding to the <code>fault</code> <em>element information
item</em>s in [children], if any.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-Interface.interfaceoperations">interface
operations</a>}</td>
<td rowspan="1" colspan="1">The set of <a href=
"#component-InterfaceOperation">Interface Operation</a> components
corresponding to the <code>operation</code> <em>element information
item</em>s in [children], if any.</td>
</tr>
</tbody>
</table>

<br />
<p>Recall that, per <a href="#Interface_details"><strong>2.2.1 The
Interface Component</strong></a>, the <a href=
"#component-Interface">Interface</a> components in the {<a href=
"#property-Interface.extendedinterfaces">extended interfaces</a>}
property of a given <a href="#component-Interface">Interface</a>
component MUST NOT contain that <a href=
"#component-Interface">Interface</a> component in any of their
{<a href="#property-Interface.extendedinterfaces">extended
interfaces</a>} properties, that is to say, recursive extension of
interfaces is disallowed.</p>
</div>
</div>
<div class="div2">
<h3><a name="InterfaceFault" id="InterfaceFault"></a>2.3 Interface
Fault</h3>
<div class="div3">
<h4><a name="InterfaceFault_details" id=
"InterfaceFault_details"></a>2.3.1 The Interface Fault
Component</h4>
<p>A fault is an event that occurs during the execution of a
message exchange that disrupts the normal flow of messages.</p>
<p>A fault is typically raised when a party is unable to
communicate an error condition inside the normal message flow, or a
party wishes to terminate a message exchange. A fault message may
be used to communicate out of band information such as the reason
for the error, the origin of the fault, as well as other informal
diagnostics such as a program stack trace.</p>
<p>An <a href="#component-InterfaceFault">Interface Fault</a>
component describes a fault that MAY occur during invocation of an
operation of the interface. The <a href=
"#component-InterfaceFault">Interface Fault</a> component declares
an abstract fault by naming it and indicating the contents of the
fault message. When and how the fault message flows is indicated by
the <a href="#component-InterfaceOperation">Interface Operation</a>
component.</p>
<p>The <a href="#component-InterfaceFault">Interface Fault</a>
component provides a clear mechanism to name and describe the set
of faults an interface may generate. This allows operations to
easily identify the individual faults they may generate by name.
This mechanism allows the ready identification of the same fault
occurring across multiple operations and referenced in multiple
bindings as well as reducing duplication of description for an
individual fault.</p>
<p>Faults other than the ones described in the <a href=
"#component-Interface">Interface</a> component may also be
generated at run-time, i.e. faults are an open set. The <a href=
"#component-Interface">Interface</a> component describes faults
that have application level semantics, i.e. that the client or
service is expected to handle, and potentially recover from, as
part of the application processing logic. For example, an <a href=
"#component-Interface">Interface</a> component that accepts a
credit card number may describe faults that indicate the credit
card number is invalid, has been reported stolen, or has expired.
The <a href="#component-Interface">Interface</a> component does not
describe general system faults such as network failures, out of
memory conditions, out of disk space conditions, invalid message
formats, etc., although these faults may be generated as part of
the message exchange. Such general system faults can reasonably be
expected to occur in any message exchange and explicitly describing
them in an <a href="#component-Interface">Interface</a> component
is therefore uninformative.</p>
<p>The properties of the <a name="component-InterfaceFault" id=
"component-InterfaceFault">Interface Fault</a> component are as
follows:</p>
<ul>
<li>
<p>{<a name="property-InterfaceFault.name" id=
"property-InterfaceFault.name">name</a>} REQUIRED. An
<em>xs:QName</em>.</p>
</li>
<li>
<p>{<a name="property-InterfaceFault.messagecontentmodel" id=
"property-InterfaceFault.messagecontentmodel">message content
model</a>} REQUIRED. <span id="InterfaceFault-1013" class=
"test-assertion-tr">An <em>xs:token</em> with one of the values
<em>#any</em>, <em>#none</em>, <em>#other</em>, or
<em>#element</em>.<sup><a href="#InterfaceFault-1013-summary"
title="Link to assertion InterfaceFault-1013 summary">†</a></sup></span>
A value of <em>#any</em> indicates that the fault content is any
single element. A value of <em>#none</em> indicates there is no
fault content. A value of <em>#other</em> indicates that the fault
content is described by some other extension property that
references a declaration in a non-XML extension type system. A
value of <em>#element</em> indicates that the fault consists of a
single element described by the global element declaration
referenced by the {<a href=
"#property-InterfaceFault.elementdeclaration">element
declaration</a>} property. This property is used only when the
fault is described using an XML-based data model.</p>
</li>
<li>
<p>{<a name="property-InterfaceFault.elementdeclaration" id=
"property-InterfaceFault.elementdeclaration">element
declaration</a>} OPTIONAL. A reference to an <a href=
"#component-ElementDeclaration">Element Declaration</a> component
in the {<a href="#property-Description.elementdeclarations">element
declarations</a>} property of the <a href=
"#component-Description">Description</a> component. This element
represents the content or “payload” of the fault. <span id=
"InterfaceFault-1014" class="test-assertion-tr">When the {<a href=
"#property-InterfaceFault.messagecontentmodel">message content
model</a>} property has the value <em>#any</em> or <em>#none</em>
the {<a href="#property-InterfaceFault.elementdeclaration">element
declaration</a>} property MUST be empty.<sup><a href=
"#InterfaceFault-1014-summary" title=
"Link to assertion InterfaceFault-1014 summary">†</a></sup></span></p>
</li>
<li>
<p>{<a name="property-InterfaceFault.parent" id=
"property-InterfaceFault.parent">parent</a>} REQUIRED. The <a href=
"#component-Interface">Interface</a> component that contains this
component in its {<a href=
"#property-Interface.interfacefaults">interface faults</a>}
property.</p>
</li>
</ul>
<a name="zed-InterfaceFault" id="zed-InterfaceFault"></a><a name=
"zed-InterfaceFaultRI" id="zed-InterfaceFaultRI"></a>
<p>For each <a href="#component-InterfaceFault">Interface Fault</a>
component in the {<a href=
"#property-Interface.interfacefaults">interface faults</a>}
property of an <a href="#component-Interface">Interface</a>
component, the {<a href="#property-InterfaceFault.name">name</a>}
property must be unique. Note that this constraint is enforced by
the normative WSDL 2.0 XML schema.</p>
<p><a href="#component-InterfaceFault">Interface Fault</a>
components are uniquely identified by the QName of the enclosing
<a href="#component-Interface">Interface</a> component and QName of
the <a href="#component-InterfaceFault">Interface Fault</a>
component itself.</p>
<a name="zed-InterfaceFaultKey" id="zed-InterfaceFaultKey"></a>
<div class="note">
<p class="prefix"><strong>Note:</strong></p>
<p>Despite having a {<a href=
"#property-InterfaceFault.name">name</a>} property, <a href=
"#component-InterfaceFault">Interface Fault</a> components cannot
be identified solely by their QName. Indeed, two <a href=
"#component-Interface">Interface</a> components whose {<a href=
"#property-Interface.name">name</a>} property value has the same
namespace name, but different local names, can contain <a href=
"#component-InterfaceFault">Interface Fault</a> components with the
same {<a href="#property-InterfaceFault.name">name</a>} property
value. Thus, the {<a href="#property-InterfaceFault.name">name</a>}
property of <a href="#component-InterfaceFault">Interface Fault</a>
component is not sufficient to form the unique identity of an
<a href="#component-InterfaceFault">Interface Fault</a> component.
A method for uniquely identifying components is defined in <a href=
"#frag-ids"><strong>A.2 Fragment Identifiers</strong></a>. See
<a href="#wsdl.interfaceFault"><strong>A.2.5 The Interface Fault
Component</strong></a> for the definition of the fragment
identifier for the <a href="#component-InterfaceFault">Interface
Fault</a> component.</p>
</div>
<p><span id="InterfaceFault-1015" class="test-assertion-tr">In
cases where, due to an interface extending one or more other
interfaces, two or more <a href=
"#component-InterfaceFault">Interface Fault</a> components have the
same value for their {<a href=
"#property-InterfaceFault.name">name</a>} property, then the
component models of those <a href=
"#component-InterfaceFault">Interface Fault</a> components MUST be
equivalent (see <a href="#compequiv"><strong>2.15 Equivalence of
Components</strong></a>). <sup><a href=
"#InterfaceFault-1015-summary" title=
"Link to assertion InterfaceFault-1015 summary">†</a></sup></span>
If the <a href="#component-InterfaceFault">Interface Fault</a>
components are equivalent then they are considered to collapse into
a single component. Within the same <a href=
"#component-Interface">Interface</a> component, if two <a href=
"#component-InterfaceFault">Interface Fault</a> components are not
equivalent then their {<a href=
"#property-InterfaceFault.name">name</a>} properties MUST NOT be
equal.</p>
<a name="zed-InterfaceFaultNameUnique" id=
"zed-InterfaceFaultNameUnique"></a>
<p>Note that, due to the above rules, if two interfaces that have
the same value for the namespace name of their {<a href=
"#property-Interface.name">name</a>} property also have one or more
faults that have the same value for their {<a href=
"#property-InterfaceFault.name">name</a>} property, then those two
interfaces cannot both form part of the derivation chain of a
derived interface unless those faults are the same fault.</p>
<p><span id="InterfaceFault-1016" class="test-assertion-tr">For the
above reason, it is considered good practice to ensure, where
necessary, that the local name of the {<a href=
"#property-InterfaceFault.name">name</a>} property of <a href=
"#component-InterfaceFault">Interface Fault</a> components within a
namespace SHOULD be unique, thus allowing such derivation to occur
without inadvertent error.<sup><a href=
"#InterfaceFault-1016-summary" title=
"Link to assertion InterfaceFault-1016 summary">†</a></sup></span></p>
<p>If a type system NOT based on the XML Infoset [<cite><a href=
"#XMLInfoSet">XML Information Set</a></cite>] is in use (as
considered in <a href="#other-types"><strong>3.2 Using Other Schema
Languages</strong></a>) then additional properties would need to be
added to the <a href="#component-InterfaceFault">Interface
Fault</a> component (along with extension attributes to its XML
representation) to allow associating such message types with the
message reference.</p>
<a name="zed-InterfaceFaultCM" id="zed-InterfaceFaultCM"></a></div>
<div class="div3">
<h4><a name="InterfaceFault_XMLRep" id=
"InterfaceFault_XMLRep"></a>2.3.2 XML Representation of Interface
Fault Component</h4>
<div class="exampleInner">
<pre xml:space="preserve">
&lt;description&gt;
  &lt;interface&gt;
    &lt;<strong>fault</strong>
          name="<em>xs:NCName</em>" 
          element="<em>union of xs:QName, xs:token</em>"? &gt;
      &lt;documentation /&gt;*
    &lt;/<strong>fault</strong>&gt;
  &lt;/interface&gt;
&lt;/description&gt;
</pre></div>
<p>The XML representation for an <a href=
"#component-InterfaceFault">Interface Fault</a> component is an
<em>element information item</em> with the following Infoset
properties:</p>
<ul>
<li>
<p>A [local name] of <code>fault</code></p>
</li>
<li>
<p>A [namespace name] of "http://www.w3.org/ns/wsdl"</p>
</li>
<li>
<p>One or more <em>attribute information item</em>s amongst its
[attributes] as follows:</p>
<ul>
<li>
<p>A REQUIRED <code>name</code> <em>attribute information item</em>
as described below in <a href=
"#Interfacefault_name_attribute"><strong>2.3.2.1 name attribute
information item with fault [owner element]</strong></a>.</p>
</li>
<li>
<p>An OPTIONAL <code>element</code> <em>attribute information
item</em> as described below in <a href=
"#Interface_element_attribute"><strong>2.3.2.2 element attribute
information item with fault [owner element]</strong></a>.</p>
</li>
<li>
<p>Zero or more namespace qualified <em>attribute information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl".</p>
</li>
</ul>
</li>
<li>
<p>Zero or more <em>element information item</em> amongst its
[children], in order, as follows:</p>
<ol class="enumar">
<li>
<p>Zero or more <code>documentation</code> <em>element information
item</em>s (see <a href="#eii-documentation"><strong>5.
Documentation</strong></a>).</p>
</li>
<li>
<p>Zero or more namespace-qualified <em>element information
item</em> s whose [namespace name] is NOT "
http://www.w3.org/ns/wsdl " .</p>
</li>
</ol>
</li>
</ul>
<div class="div4">
<h5><a name="Interfacefault_name_attribute" id=
"Interfacefault_name_attribute"></a>2.3.2.1 <code>name</code>
<em>attribute information item</em> with <code>fault</code> [owner
element]</h5>
<p>The <code>name</code> <em>attribute information item</em>
identifies a given <code>fault</code> <em>element information
item</em> inside a given <code>interface</code> <em>element
information item</em>.</p>
<p>The <code>name</code> <em>attribute information item</em> has
the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>name</code></p>
</li>
<li>
<p>A [namespace name] which has no value</p>
</li>
</ul>
<p>The type of the <code>name</code> <em>attribute information
item</em> is <em>xs:NCName</em>.</p>
</div>
<div class="div4">
<h5><a name="Interface_element_attribute" id=
"Interface_element_attribute"></a>2.3.2.2 <code>element</code>
<em>attribute information item</em> with <code>fault</code> [owner
element]</h5>
<p>The <code>element</code> <em>attribute information item</em>
refers, by QName, to an <a href=
"#component-ElementDeclaration">Element Declaration</a>
component.</p>
<p>The <code>element</code> <em>attribute information item</em> has
the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>element</code>.</p>
</li>
<li>
<p>A [namespace name] which has no value.</p>
</li>
</ul>
<p>The type of the <code>element</code> <em>attribute information
item</em> is a union of <em>xs:QName</em> and <em>xs:token</em>
where the allowed token values are <em>#any</em>, <em>#none</em>,
or <em>#other</em>.</p>
</div>
</div>
<div class="div3">
<h4><a name="InterfaceFault_Mapping" id=
"InterfaceFault_Mapping"></a>2.3.3 Mapping Interface Fault's XML
Representation to Component Properties</h4>
<p>The mapping from the XML Representation of the
<code>fault</code> <em>element information item</em> (see <a href=
"#InterfaceFault_XMLRep"><strong>2.3.2 XML Representation of
Interface Fault Component</strong></a>) to the properties of the
<a href="#component-InterfaceFault">Interface Fault</a> component
is as described in <a href="#tab_InterfaceFault_Mapping">Table
2-3</a>.</p>
<a name="tab_InterfaceFault_Mapping" id=
"tab_InterfaceFault_Mapping"></a>
<table border="1">
<caption>Table 2-3. Mapping from XML Representation to Interface
Fault Component Properties</caption>
<col width="20%" span="1" />
<col width="80%" span="1" />
<tbody>
<tr>
<th rowspan="1" colspan="1">Property</th>
<th rowspan="1" colspan="1">Value</th>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-InterfaceFault.name">name</a>}</td>
<td rowspan="1" colspan="1">The QName whose local name is the
actual value of the <code>name</code> <em>attribute information
item</em>. and whose namespace name is the actual value of the
<code>targetNamespace</code> <em>attribute information item</em> of
the [parent] <code>description</code> <em>element information
item</em> of the [parent] <code>interface</code> <em>element
information item</em>.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-InterfaceFault.messagecontentmodel">message content
model</a>}</td>
<td rowspan="1" colspan="1">If the <code>element</code>
<em>attribute information item</em> is present and its value is a
QName, then <em>#element</em>; otherwise the actual value of the
<code>element</code> <em>attribute information item</em>, if any;
otherwise <em>#other</em>.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-InterfaceFault.elementdeclaration">element
declaration</a>}</td>
<td rowspan="1" colspan="1">If the <code>element</code>
<em>attribute information item</em> is present and its value is a
QName, then the <a href="#component-ElementDeclaration">Element
Declaration</a> component from the {<a href=
"#property-Description.elementdeclarations">element
declarations</a>} property of the <a href=
"#component-Description">Description</a> component resolved to by
the value of the <code>element</code> <em>attribute information
item</em> (see <a href="#qnameres"><strong>2.17 QName
resolution</strong></a>); otherwise empty. <span id=
"InterfaceFault-1017" class="test-assertion-tr">If the
<code>element</code> <em>attribute information item</em> has a
value, then it MUST resolve to an <a href=
"#component-ElementDeclaration">Element Declaration</a> component
from the {<a href=
"#property-Description.elementdeclarations">element
declarations</a>} property of the <a href=
"#component-Description">Description</a> component.<sup><a href=
"#InterfaceFault-1017-summary" title=
"Link to assertion InterfaceFault-1017 summary">†</a></sup></span></td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-InterfaceFault.parent">parent</a>}</td>
<td rowspan="1" colspan="1">The <a href=
"#component-Interface">Interface</a> component corresponding to the
<code>interface</code> <em>element information item</em> in
[parent].</td>
</tr>
</tbody>
</table>

<br /></div>
</div>
<div class="div2">
<h3><a name="InterfaceOperation" id="InterfaceOperation"></a>2.4
Interface Operation</h3>
<div class="div3">
<h4><a name="InterfaceOperation_details" id=
"InterfaceOperation_details"></a>2.4.1 The Interface Operation
Component</h4>
<p>An <a href="#component-InterfaceOperation">Interface
Operation</a> component describes an operation that a given
interface supports. An operation is an interaction with the service
consisting of a set of (ordinary and fault) messages exchanged
between the service and the other parties involved in the
interaction. The sequencing and cardinality of the messages
involved in a particular interaction is governed by the <em>message
exchange pattern</em> used by the operation (see {<a href=
"#property-InterfaceOperation.messageexchangepattern">message
exchange pattern</a>} property).</p>
<p>A message exchange pattern defines placeholders for messages,
the participants in the pattern (i.e., the sources and sinks of the
messages), and the cardinality and sequencing of messages exchanged
by the participants. The message placeholders are associated with
specific message types by the operation that uses the pattern by
means of message and fault references (see {<a href=
"#property-InterfaceOperation.interfacemessagereferences">interface
message references</a>} and {<a href=
"#property-InterfaceOperation.interfacefaultreferences">interface
fault references</a>} properties). The service whose operation is
using the pattern becomes one of the participants of the pattern.
This specification does not define a machine understandable
language for defining message exchange patterns, nor does it define
any specific patterns. The companion specification, [<cite><a href=
"#WSDL-PART2">WSDL 2.0 Adjuncts</a></cite>] defines a set of such
patterns and defines identifying IRIs any of which MAY be used as
the value of the {<a href=
"#property-InterfaceOperation.messageexchangepattern">message
exchange pattern</a>} property.</p>
<p>The properties of the <a name="component-InterfaceOperation" id=
"component-InterfaceOperation">Interface Operation</a> component
are as follows:</p>
<ul>
<li>
<p>{<a name="property-InterfaceOperation.name" id=
"property-InterfaceOperation.name">name</a>} REQUIRED. An
<em>xs:QName</em>.</p>
</li>
<li>
<p>{<a name="property-InterfaceOperation.messageexchangepattern"
id="property-InterfaceOperation.messageexchangepattern">message
exchange pattern</a>} REQUIRED. An <em>xs:anyURI</em> identifying
the message exchange pattern used by the operation. <span id=
"InterfaceOperation-1018" class="test-assertion-tr">This
<em>xs:anyURI</em> MUST be an absolute IRI (see [<cite><a href=
"#RFC3987">IETF RFC 3987</a></cite>]).<sup><a href=
"#InterfaceOperation-1018-summary" title=
"Link to assertion InterfaceOperation-1018 summary">†</a></sup></span></p>
</li>
<li>
<p>{<a name=
"property-InterfaceOperation.interfacemessagereferences" id=
"property-InterfaceOperation.interfacemessagereferences">interface
message references</a>} OPTIONAL. A set of <a href=
"#component-InterfaceMessageReference">Interface Message
Reference</a> components for the ordinary messages the operation
accepts or sends.</p>
</li>
<li>
<p>{<a name="property-InterfaceOperation.interfacefaultreferences"
id="property-InterfaceOperation.interfacefaultreferences">interface
fault references</a>} OPTIONAL. A set of <a href=
"#component-InterfaceFaultReference">Interface Fault Reference</a>
components for the fault messages the operation accepts or
sends.</p>
</li>
<li>
<p>{<a name="property-InterfaceOperation.style" id=
"property-InterfaceOperation.style">style</a>} OPTIONAL. A set of
<em>xs:anyURI</em>s identifying the rules that were used to
construct the {<a href=
"#property-InterfaceMessageReference.elementdeclaration">element
declaration</a>} properties of {<a href=
"#property-InterfaceOperation.interfacemessagereferences">interface
message references</a>}. (See <a href=
"#InterfaceOperationStyle"><strong>2.4.1.2 Operation
Style</strong></a>.) <span id="InterfaceOperation-1019" class=
"test-assertion-tr">These <em>xs:anyURI</em>s MUST be absolute IRIs
(see [<cite><a href="#RFC3986">IETF RFC
3986</a></cite>]).<sup><a href="#InterfaceOperation-1019-summary"
title=
"Link to assertion InterfaceOperation-1019 summary">†</a></sup></span></p>
</li>
<li>
<p>{<a name="property-InterfaceOperation.parent" id=
"property-InterfaceOperation.parent">parent</a>} REQUIRED. The
<a href="#component-Interface">Interface</a> component that
contains this component in its {<a href=
"#property-Interface.interfaceoperations">interface operations</a>}
property.</p>
</li>
</ul>
<a name="zed-InterfaceOperation" id=
"zed-InterfaceOperation"></a><a name="zed-InterfaceOperationRI" id=
"zed-InterfaceOperationRI"></a>
<p>For each <a href="#component-InterfaceOperation">Interface
Operation</a> component in the {<a href=
"#property-Interface.interfaceoperations">interface operations</a>}
property of an <a href="#component-Interface">Interface</a>
component, the {<a href=
"#property-InterfaceOperation.name">name</a>} property MUST be
unique. Note that this constraint is enforced by the normative WSDL
2.0 XML schema.</p>
<p><a href="#component-InterfaceOperation">Interface Operation</a>
components are uniquely identified by the QName of the enclosing
<a href="#component-Interface">Interface</a> component and QName of
the <a href="#component-InterfaceOperation">Interface Operation</a>
component itself.</p>
<a name="zed-InterfaceOperationKey" id=
"zed-InterfaceOperationKey"></a>
<div class="note">
<p class="prefix"><strong>Note:</strong></p>
<p>Despite having a {<a href=
"#property-InterfaceOperation.name">name</a>} property, <a href=
"#component-InterfaceOperation">Interface Operation</a> components
cannot be identified solely by their QName. Indeed, two <a href=
"#component-Interface">Interface</a> components whose {<a href=
"#property-Interface.name">name</a>} property value has the same
namespace name, but different local names, can contain <a href=
"#component-InterfaceOperation">Interface Operation</a> components
with the same {<a href=
"#property-InterfaceOperation.name">name</a>} property value. Thus,
the {<a href="#property-InterfaceOperation.name">name</a>} property
of <a href="#component-InterfaceOperation">Interface Operation</a>
components is not sufficient to form the unique identity of an
<a href="#component-InterfaceOperation">Interface Operation</a>
component. A method for uniquely identifying components is defined
in <a href="#frag-ids"><strong>A.2 Fragment
Identifiers</strong></a> . See <a href=
"#wsdl.interfaceOperation"><strong>A.2.6 The Interface Operation
Component</strong></a> for the definition of the fragment
identifier for the <a href=
"#component-InterfaceOperation">Interface Operation</a>
component.</p>
</div>
<p><span id="InterfaceOperation-1020" class="test-assertion-tr">In
cases where, due to an interface extending one or more other
interfaces, two or more <a href=
"#component-InterfaceOperation">Interface Operation</a> components
have the same value for their {<a href=
"#property-InterfaceOperation.name">name</a>} property, then the
component models of those Interface Operation components MUST be
equivalent (see <a href="#compequiv"><strong>2.15 Equivalence of
Components</strong></a>).<sup><a href=
"#InterfaceOperation-1020-summary" title=
"Link to assertion InterfaceOperation-1020 summary">†</a></sup></span>
If the <a href="#component-InterfaceOperation">Interface
Operation</a> components are equivalent then they are considered to
collapse into a single component. Within the same <a href=
"#component-Interface">Interface</a> component, if two <a href=
"#component-InterfaceOperation">Interface Operation</a> components
are not equivalent then their {<a href=
"#property-InterfaceOperation.name">name</a>} properties MUST NOT
be equal.</p>
<a name="zed-InterfaceOperationNameUnique" id=
"zed-InterfaceOperationNameUnique"></a>
<p>Note that, due to the above rules, if two interfaces that have
the same value for the namespace name of their {<a href=
"#property-Interface.name">name</a>} property also have one or more
operations that have the same value for their {<a href=
"#property-InterfaceOperation.name">name</a>} property, then those
two interfaces cannot both form part of the derivation chain of a
derived interface unless those operations are the same
operation.</p>
<p><span id="InterfaceOperation-1021" class="test-assertion-tr">For
the above reason, it is considered good practice to ensure, where
necessary, that the {<a href=
"#property-InterfaceOperation.name">name</a>} property of <a href=
"#component-InterfaceOperation">Interface Operation</a> components
within a namespace SHOULD be unique, thus allowing such derivation
to occur without inadvertent error.<sup><a href=
"#InterfaceOperation-1021-summary" title=
"Link to assertion InterfaceOperation-1021 summary">†</a></sup></span></p>
<p>More than one <a href=
"#component-InterfaceFaultReference">Interface Fault Reference</a>
component in the {<a href=
"#property-InterfaceOperation.interfacefaultreferences">interface
fault references</a>} property of an <a href=
"#component-InterfaceOperation">Interface Operation</a> component
may refer to the same message label. In that case, the listed fault
types define alternative fault messages. This allows one to
indicate that there is more than one type of fault that is related
to that message.</p>
<a name="zed-InterfaceOperationParent" id=
"zed-InterfaceOperationParent"></a><a name=
"zed-InterfaceOperationCM" id="zed-InterfaceOperationCM"></a>
<div class="div4">
<h5><a name="MessageExchangePattern" id=
"MessageExchangePattern"></a>2.4.1.1 Message Exchange Pattern</h5>
<p>This section describes some aspects of message exchange patterns
in more detail. Refer to the <em>Web Services Description Language
(WSDL) Version 2.0 Part 2: Adjuncts</em> specification
[<cite><a href="#WSDL-PART2">WSDL 2.0 Adjuncts</a></cite>] for a
complete discussion of the semantics of message exchange patterns
in general, as well as the definitions of the message exchange
patterns that are predefined by WSDL 2.0.</p>
<p>A <em>placeholder message</em> is a template for an actual
message as described by an <a href=
"#component-InterfaceMessageReference">Interface Message
Reference</a> component. Although a placeholder message is not
itself a component, it is useful to regard it as having both a
{<a href="#property-InterfaceMessageReference.messagelabel">message
label</a>} and a {<a href=
"#property-InterfaceMessageReference.direction">direction</a>}
property which define the values of the actual <a href=
"#component-InterfaceMessageReference">Interface Message
Reference</a> component that corresponds to it. A placeholder
message is also associated with some node that exchanges the
message with the service. Furthermore, a placeholder message may be
designated as optional in the exchange.</p>
<a name="zed-Node" id="zed-Node"></a><a name=
"zed-PlaceholderMessage" id="zed-PlaceholderMessage"></a>
<p>A <em>fault propagation ruleset</em> specifies the relation
between the <a href="#component-InterfaceFaultReference">Interface
Fault Reference</a> and <a href=
"#component-InterfaceMessageReference">Interface Message
Reference</a> components of an <a href=
"#component-InterfaceOperation">Interface Operation</a> component.
The <em>Web Services Description Language (WSDL) Version 2.0 Part
2: Adjuncts</em> specification [<cite><a href="#WSDL-PART2">WSDL
2.0 Adjuncts</a></cite>] defines three fault propagation rulesets
which we will refer to as <em>fault-replaces-message</em>,
<em>message-triggers-fault</em>, and <em>no-faults</em>. These
three fault propagation rulesets are used by the predefined message
exchange patterns defined in [<cite><a href="#WSDL-PART2">WSDL 2.0
Adjuncts</a></cite>]. Other message exchange patterns can define
additional fault propagation rulesets.</p>
<a name="zed-FaultPropagationRuleset" id=
"zed-FaultPropagationRuleset"></a>
<p>A <em>message exchange pattern</em> is a template for the
exchange of one or more messages, and their associated faults,
between the service and one or more other nodes as described by an
<a href="#component-InterfaceOperation">Interface Operation</a>
component. The service and the other nodes are referred to as the
<em>participants</em> in the exchange. More specifically, a message
exchange pattern consists of a sequence of one or more placeholder
messages. Each placeholder message within this sequence is uniquely
identified by its {<a href=
"#property-InterfaceMessageReference.messagelabel">message
label</a>} property. <span id="MEP-1022" class=
"test-assertion-tr">A message exchange pattern is itself uniquely
identified by an absolute IRI, which is used as the value of the
{<a href=
"#property-InterfaceOperation.messageexchangepattern">message
exchange pattern</a>} property of the <a href=
"#component-InterfaceOperation">Interface Operation</a> component,
and which specifies the fault propagation ruleset that its faults
obey.<sup><a href="#MEP-1022-summary" title=
"Link to assertion MEP-1022 summary">†</a></sup></span></p>
<a name="zed-MessageExchangePattern" id=
"zed-MessageExchangePattern"></a></div>
<div class="div4">
<h5><a name="InterfaceOperationStyle" id=
"InterfaceOperationStyle"></a>2.4.1.2 Operation Style</h5>
<p>An operation style specifies additional information about an
operation. For example, an operation style may define structural
constraints on the element declarations of the interface message
reference or interface fault components used by the operation. This
additional information in no way affects the messages and faults
exchanged with the service and it can therefore be safely ignored
in that context. However, the additional information can be used
for other purposes, for example, improved code generation. The
{<a href="#property-InterfaceOperation.style">style</a>} property
of the <a href="#component-InterfaceOperation">Interface
Operation</a> component contains a set of zero or more IRIs that
identify operation styles. <span id="InterfaceOperation-1023"
class="test-assertion-tr">An <a href=
"#component-InterfaceOperation">Interface Operation</a> component
MUST satisfy the specification defined by each operation style
identified by its {<a href=
"#property-InterfaceOperation.style">style</a>} property.
<sup><a href="#InterfaceOperation-1023-summary" title=
"Link to assertion InterfaceOperation-1023 summary">†</a></sup></span>
If no <a href="#component-InterfaceOperation">Interface
Operation</a> component can simultaneously satisfy all of the
styles, the document is invalid.</p>
<p>If the {<a href="#property-InterfaceOperation.style">style</a>}
property of an <a href="#component-InterfaceOperation">Interface
Operation</a> component does have a value, then that value (a set
of IRIs) specifies the rules that were used to define the element
declarations (or other properties that define the message and fault
contents; see <a href="#other-types"><strong>3.2 Using Other Schema
Languages</strong></a>) of the <a href=
"#component-InterfaceMessageReference">Interface Message
Reference</a> or <a href="#component-InterfaceFault">Interface
Fault</a> components used by the operation. Although a given
operation style has the ability to constrain <em>all</em> input and
output messages and faults of an operation, it MAY choose to
constrain any combination thereof, e.g. only the messages, or only
the inputs.</p>
<p>Please refer to the <em>Web Services Description Language (WSDL)
Version 2.0 Part 2: Adjuncts</em> specification [<cite><a href=
"#WSDL-PART2">WSDL 2.0 Adjuncts</a></cite>] for particular
operation style definitions.</p>
</div>
</div>
<div class="div3">
<h4><a name="InterfaceOperation_XMLRep" id=
"InterfaceOperation_XMLRep"></a>2.4.2 XML Representation of
Interface Operation Component</h4>
<div class="exampleInner">
<pre xml:space="preserve">
&lt;description&gt;
  &lt;interface&gt;
    &lt;<strong>operation</strong>
          name="<em>xs:NCName</em>" 
          pattern="<em>xs:anyURI</em>"?
          style="<em>list of xs:anyURI</em>"? &gt;
      &lt;documentation /&gt;*
      [ &lt;input /&gt; | &lt;output /&gt; | &lt;infault /&gt; | &lt;outfault /&gt; ]*
    &lt;/<strong>operation</strong>&gt;
  &lt;/interface&gt;
&lt;/description&gt;
</pre></div>
<p>The XML representation for an <a href=
"#component-InterfaceOperation">Interface Operation</a> component
is an <em>element information item</em> with the following Infoset
properties:</p>
<ul>
<li>
<p>A [local name] of <code>operation</code></p>
</li>
<li>
<p>A [namespace name] of "http://www.w3.org/ns/wsdl"</p>
</li>
<li>
<p>Two or more <em>attribute information item</em>s amongst its
[attributes] as follows:</p>
<ul>
<li>
<p>A REQUIRED <code>name</code> <em>attribute information item</em>
as described below in <a href=
"#Interfaceoperation_name_attribute"><strong>2.4.2.1 name attribute
information item with operation [owner element]</strong></a>.</p>
</li>
<li>
<p>An OPTIONAL <code>pattern</code> <em>attribute information
item</em> as described below in <a href=
"#Interfaceoperation_pattern_attribute"><strong>2.4.2.2 pattern
attribute information item with operation [owner
element]</strong></a>.</p>
</li>
<li>
<p>An OPTIONAL <code>style</code> <em>attribute information
item</em> as described below in <a href=
"#InterfaceOperation_style_attribute"><strong>2.4.2.3 style
attribute information item with operation [owner
element]</strong></a>.</p>
</li>
<li>
<p>Zero or more namespace qualified <em>attribute information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl".</p>
</li>
</ul>
</li>
<li>
<p>One or more <em>element information item</em> amongst its
[children], in order, as follows:</p>
<ol class="enumar">
<li>
<p>Zero or more <code>documentation</code> <em>element information
item</em>s (see <a href="#eii-documentation"><strong>5.
Documentation</strong></a>).</p>
</li>
<li>
<p>One or more <em>element information item</em>s from among the
following, in any order:</p>
<ul>
<li>
<p>One or more <em>element information item</em>s from among the
following, in any order:</p>
<ul>
<li>
<p>Zero or more <code>input</code> <em>element information
item</em>s (see <a href=
"#InterfaceMessageReference_XMLRep"><strong>2.5.2 XML
Representation of Interface Message Reference
Component</strong></a>).</p>
</li>
<li>
<p>Zero or more <code>output</code> <em>element information
item</em>s (see <a href=
"#InterfaceMessageReference_XMLRep"><strong>2.5.2 XML
Representation of Interface Message Reference
Component</strong></a>).</p>
</li>
<li>
<p>Zero or more <code>infault</code> <em>element information
item</em>s (see <a href=
"#InterfaceFaultReference_XMLRep"><strong>2.6.2 XML Representation
of Interface Fault Reference</strong></a>).</p>
</li>
<li>
<p>Zero or more <code>outfault</code> <em>element information
item</em>s (see <a href=
"#InterfaceFaultReference_XMLRep"><strong>2.6.2 XML Representation
of Interface Fault Reference</strong></a>).</p>
</li>
</ul>
</li>
<li>
<p>Zero or more namespace-qualified <em>element information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl".</p>
</li>
</ul>
</li>
</ol>
</li>
</ul>
<div class="div4">
<h5><a name="Interfaceoperation_name_attribute" id=
"Interfaceoperation_name_attribute"></a>2.4.2.1 <code>name</code>
<em>attribute information item</em> with <code>operation</code>
[owner element]</h5>
<p>The <code>name</code> <em>attribute information item</em>
identifies a given <code>operation</code> <em>element information
item</em> inside a given <code>interface</code> <em>element
information item</em>.</p>
<p>The <code>name</code> <em>attribute information item</em> has
the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>name</code></p>
</li>
<li>
<p>A [namespace name] which has no value</p>
</li>
</ul>
<p>The type of the <code>name</code> <em>attribute information
item</em> is <em>xs:NCName</em>.</p>
</div>
<div class="div4">
<h5><a name="Interfaceoperation_pattern_attribute" id=
"Interfaceoperation_pattern_attribute"></a>2.4.2.2
<code>pattern</code> <em>attribute information item</em> with
<code>operation</code> [owner element]</h5>
<p>The <code>pattern</code> <em>attribute information item</em>
identifies the message exchange pattern a given operation uses.</p>
<p>The <code>pattern</code> <em>attribute information item</em> has
the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>pattern</code></p>
</li>
<li>
<p>A [namespace name] which has no value</p>
</li>
</ul>
<p>The type of the <code>pattern</code> <em>attribute information
item</em> is <em>xs:anyURI</em>. Note that its value must be an
absolute IRI (see [<cite><a href="#RFC3987">IETF RFC
3987</a></cite>]).</p>
</div>
<div class="div4">
<h5><a name="InterfaceOperation_style_attribute" id=
"InterfaceOperation_style_attribute"></a>2.4.2.3 <code>style</code>
<em>attribute information item</em> with <code>operation</code>
[owner element]</h5>
<p>The <code>style</code> <em>attribute information item</em>
indicates the rules that were used to construct the {<a href=
"#property-InterfaceMessageReference.elementdeclaration">element
declaration</a>} properties of the <a href=
"#component-InterfaceMessageReference">Interface Message
Reference</a> components which are members of the {<a href=
"#property-InterfaceOperation.interfacemessagereferences">interface
message references</a>} property of the [owner element]
operation.</p>
<p>The <code>style</code> <em>attribute information item</em> has
the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>style</code></p>
</li>
<li>
<p>A [namespace name] which has no value</p>
</li>
</ul>
<p>The type of the <code>style</code> <em>attribute information
item</em> is <em>list of xs:anyURI</em>. Note that its value must
be an absolute IRI (see [<cite><a href="#RFC3987">IETF RFC
3987</a></cite>]).</p>
</div>
</div>
<div class="div3">
<h4><a name="InterfaceOperation_Mapping" id=
"InterfaceOperation_Mapping"></a>2.4.3 Mapping Interface
Operation's XML Representation to Component Properties</h4>
<p>The mapping from the XML Representation of the
<code>operation</code> <em>element information item</em> (see
<a href="#InterfaceOperation_XMLRep"><strong>2.4.2 XML
Representation of Interface Operation Component</strong></a>) to
the properties of the Interface Operation component (see <a href=
"#InterfaceOperation_details"><strong>2.4.1 The Interface Operation
Component</strong></a>) is as described in <a href=
"#tab_InterfaceOperation_Mapping">Table 2-4</a>.</p>
<a name="tab_InterfaceOperation_Mapping" id=
"tab_InterfaceOperation_Mapping"></a>
<table border="1">
<caption>Table 2-4. Mapping from XML Representation to Interface
Operation Component Properties</caption>
<col width="20%" span="1" />
<col width="80%" span="1" />
<tbody>
<tr>
<th rowspan="1" colspan="1">Property</th>
<th rowspan="1" colspan="1">Value</th>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-InterfaceOperation.name">name</a>}</td>
<td rowspan="1" colspan="1">The QName whose local name is the
actual value of the <code>name</code> <em>attribute information
item</em> and whose namespace name is the actual value of the
<code>targetNamespace</code> <em>attribute information item</em> of
the [parent] <code>description</code> <em>element information
item</em> of the [parent] <code>interface</code> <em>element
information item</em>.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-InterfaceOperation.messageexchangepattern">message
exchange pattern</a>}</td>
<td rowspan="1" colspan="1">The actual value of the
<code>pattern</code> <em>attribute information item</em>; otherwise
'http://www.w3.org/ns/wsdl/in-out'.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-InterfaceOperation.interfacemessagereferences">interface
message references</a>}</td>
<td rowspan="1" colspan="1">The set of message references
corresponding to the <code>input</code> and <code>output</code>
<em>element information item</em>s in [children], if any.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-InterfaceOperation.interfacefaultreferences">interface
fault references</a>}</td>
<td rowspan="1" colspan="1">The set of interface fault references
corresponding to the <code>infault</code> and <code>outfault</code>
<em>element information item</em>s in [children], if any.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-InterfaceOperation.style">style</a>}</td>
<td rowspan="1" colspan="1">The set containing the IRIs in the
actual value of the <code>style</code> <em>attribute information
item</em>, if present; otherwise the set containing the IRIs in the
actual value of the <code>styleDefault</code> <em>attribute
information item</em> of the [parent] <code>interface</code>
<em>element information item</em>, if present; otherwise
empty.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-InterfaceOperation.parent">parent</a>}</td>
<td rowspan="1" colspan="1">The <a href=
"#component-Interface">Interface</a> component corresponding to the
<code>interface</code> <em>element information item</em> in
[parent].</td>
</tr>
</tbody>
</table>

<br /></div>
</div>
<div class="div2">
<h3><a name="InterfaceMessageReference" id=
"InterfaceMessageReference"></a>2.5 Interface Message
Reference</h3>
<div class="div3">
<h4><a name="InterfaceMessageReference_details" id=
"InterfaceMessageReference_details"></a>2.5.1 The Interface Message
Reference Component</h4>
<p>An <a href="#component-InterfaceMessageReference">Interface
Message Reference</a> component defines the content, or
<em>payload</em>, of a message exchanged in an operation. By
default, the message content is defined by an XML-based type system
such as XML Schema. Other type systems may be used via the WSDL 2.0
type system extension mechanism.</p>
<p>A message exchange pattern defines a set of placeholder messages
that participate in the pattern and assigns them unique message
labels within the pattern (e.g. 'In', 'Out'). The purpose of an
<a href="#component-InterfaceMessageReference">Interface Message
Reference</a> component is to associate an actual message element
(XML element declaration or some other declaration (see <a href=
"#other-types"><strong>3.2 Using Other Schema
Languages</strong></a>)) with a message in the pattern, as
identified by its message label. Later, when the message exchange
pattern is instantiated, messages corresponding to that particular
label will follow the element assignment made by the <a href=
"#component-InterfaceMessageReference">Interface Message
Reference</a> component.</p>
<p>The properties of the <a name=
"component-InterfaceMessageReference" id=
"component-InterfaceMessageReference">Interface Message
Reference</a> component are as follows:</p>
<ul>
<li>
<p>{<a name="property-InterfaceMessageReference.messagelabel" id=
"property-InterfaceMessageReference.messagelabel">message
label</a>} REQUIRED. An <em>xs:NCName</em>. This property
identifies the role this message plays in the {<a href=
"#property-InterfaceOperation.messageexchangepattern">message
exchange pattern</a>} of the <a href=
"#component-InterfaceOperation">Interface Operation</a> component
this message is contained within. <span id="MessageLabel-1024"
class="test-assertion-tr">The value of this property MUST match the
name of a placeholder message defined by the message exchange
pattern.<sup><a href="#MessageLabel-1024-summary" title=
"Link to assertion MessageLabel-1024 summary">†</a></sup></span></p>
</li>
<li>
<p>{<a name="property-InterfaceMessageReference.direction" id=
"property-InterfaceMessageReference.direction">direction</a>}
REQUIRED. <span id="InterfaceMessageReference-1025" class=
"test-assertion-tr">An <em>xs:token</em> with one of the values
<em>in</em> or <em>out</em>, indicating whether the message is
coming to the service or going from the service,
respectively.<sup><a href="#InterfaceMessageReference-1025-summary"
title=
"Link to assertion InterfaceMessageReference-1025 summary">†</a></sup></span>&#160;
<span id="InterfaceMessageReference-1026" class=
"test-assertion-tr">The direction MUST be the same as the direction
of the message identified by the {<a href=
"#property-InterfaceMessageReference.messagelabel">message
label</a>} property in the {<a href=
"#property-InterfaceOperation.messageexchangepattern">message
exchange pattern</a>} of the <a href=
"#component-InterfaceOperation">Interface Operation</a> component
this is contained within.<sup><a href=
"#InterfaceMessageReference-1026-summary" title=
"Link to assertion InterfaceMessageReference-1026 summary">†</a></sup></span></p>
</li>
<li>
<p>{<a name=
"property-InterfaceMessageReference.messagecontentmodel" id=
"property-InterfaceMessageReference.messagecontentmodel">message
content model</a>} REQUIRED. <span id=
"InterfaceMessageReference-1027" class="test-assertion-tr">An
<em>xs:token</em> with one of the values <em>#any</em>,
<em>#none</em>, <em>#other</em>, or <em>#element</em>.<sup><a href=
"#InterfaceMessageReference-1027-summary" title=
"Link to assertion InterfaceMessageReference-1027 summary">†</a></sup></span>
A value of <em>#any</em> indicates that the message content is any
single element. A value of <em>#none</em> indicates there is no
message content. A value of <em>#other</em> indicates that the
message content is described by some other extension property that
references a declaration in a non-XML extension type system. A
value of <em>#element</em> indicates that the message consists of a
single element described by the global element declaration
referenced by the {<a href=
"#property-InterfaceMessageReference.elementdeclaration">element
declaration</a>} property. This property is used only when the
message is described using an XML-based data model.</p>
</li>
<li>
<p>{<a name="property-InterfaceMessageReference.elementdeclaration"
id="property-InterfaceMessageReference.elementdeclaration">element
declaration</a>} OPTIONAL. A reference to an <a href=
"#component-ElementDeclaration">Element Declaration</a> component
in the {<a href="#property-Description.elementdeclarations">element
declarations</a>} property of the <a href=
"#component-Description">Description</a> component. This element
represents the content or “payload” of the message. <span id=
"InterfaceMessageReference-1028" class="test-assertion-tr">When the
{<a href=
"#property-InterfaceMessageReference.messagecontentmodel">message
content model</a>} property has the value <em>#any</em> or
<em>#none</em>, the {<a href=
"#property-InterfaceMessageReference.elementdeclaration">element
declaration</a>} property MUST be empty.<sup><a href=
"#InterfaceMessageReference-1028-summary" title=
"Link to assertion InterfaceMessageReference-1028 summary">†</a></sup></span></p>
</li>
<li>
<p>{<a name="property-InterfaceMessageReference.parent" id=
"property-InterfaceMessageReference.parent">parent</a>} REQUIRED.
The <a href="#component-InterfaceOperation">Interface Operation</a>
component that contains this component in its {<a href=
"#property-InterfaceOperation.interfacemessagereferences">interface
message references</a>} property.</p>
</li>
</ul>
<a name="zed-Direction" id="zed-Direction"></a><a name=
"zed-MessageContentModel" id="zed-MessageContentModel"></a><a name=
"zed-InterfaceMessageReference" id=
"zed-InterfaceMessageReference"></a><a name=
"zed-InterfaceMessageReferenceRI" id=
"zed-InterfaceMessageReferenceRI"></a>
<p><span id="InterfaceMessageReference-1029" class=
"test-assertion-tr">For each <a href=
"#component-InterfaceMessageReference">Interface Message
Reference</a> component in the {<a href=
"#property-InterfaceOperation.interfacemessagereferences">interface
message references</a>} property of an <a href=
"#component-InterfaceOperation">Interface Operation</a> component,
its {<a href=
"#property-InterfaceMessageReference.messagelabel">message
label</a>} property MUST be unique.<sup><a href=
"#InterfaceMessageReference-1029-summary" title=
"Link to assertion InterfaceMessageReference-1029 summary">†</a></sup></span></p>
<a name="zed-InterfaceMessageReferenceKey" id=
"zed-InterfaceMessageReferenceKey"></a>
<p>If a type system not based upon the XML Infoset is in use (as
considered in <a href="#other-types"><strong>3.2 Using Other Schema
Languages</strong></a>), then additional properties would need to
be added to the <a href=
"#component-InterfaceMessageReference">Interface Message
Reference</a> component (along with extension attributes to its XML
representation) to allow associating such message types with the
message reference.</p>
<a name="zed-InterfaceMessageReferenceCM" id=
"zed-InterfaceMessageReferenceCM"></a></div>
<div class="div3">
<h4><a name="InterfaceMessageReference_XMLRep" id=
"InterfaceMessageReference_XMLRep"></a>2.5.2 XML Representation of
Interface Message Reference Component</h4>
<div class="exampleInner">
<pre xml:space="preserve">
&lt;description&gt;
  &lt;interface&gt;
    &lt;operation&gt;
      &lt;<strong>input</strong>
            messageLabel="<em>xs:NCName</em>"?
            element="<em>union of xs:QName, xs:token</em>"? &gt;
        &lt;documentation /&gt;*
      &lt;/<strong>input</strong>&gt;
      &lt;<strong>output</strong>
            messageLabel="<em>xs:NCName</em>"?
            element="<em>union of xs:QName, xs:token</em>"? &gt;
        &lt;documentation /&gt;*
      &lt;/<strong>output</strong>&gt;
    &lt;/operation&gt;
  &lt;/interface&gt;
&lt;/description&gt;
</pre></div>
<p>The XML representation for an <a href=
"#component-InterfaceMessageReference">Interface Message
Reference</a> component is an <em>element information item</em>
with the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>input</code> or <code>output</code></p>
</li>
<li>
<p>A [namespace name] of "http://www.w3.org/ns/wsdl"</p>
</li>
<li>
<p>Zero or more <em>attribute information item</em>s amongst its
[attributes] as follows:</p>
<ul>
<li>
<p>An OPTIONAL <code>messageLabel</code> <em>attribute information
item</em> as described below in <a href=
"#InterfaceMessageReference_messageReference_attribute"><strong>2.5.2.1
messageLabel attribute information item with input or output [owner
element]</strong></a>.</p>
</li>
<li>
<p>An OPTIONAL <code>element</code> <em>attribute information
item</em> as described below in <a href=
"#InterfaceMessageReference_element_attribute"><strong>2.5.2.2
element attribute information item with input or output [owner
element]</strong></a>.</p>
</li>
<li>
<p>Zero or more namespace qualified <em>attribute information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl".</p>
</li>
</ul>
</li>
<li>
<p>Zero or more <em>element information item</em> amongst its
[children], in order, as follows:</p>
<ol class="enumar">
<li>
<p>Zero or more <code>documentation</code> <em>element information
item</em>s (see <a href="#eii-documentation"><strong>5.
Documentation</strong></a>).</p>
</li>
<li>
<p>Zero or more namespace-qualified <em>element information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl".</p>
</li>
</ol>
</li>
</ul>
<div class="div4">
<h5><a name="InterfaceMessageReference_messageReference_attribute"
id=
"InterfaceMessageReference_messageReference_attribute"></a>2.5.2.1
<code>messageLabel</code> <em>attribute information item</em> with
<code>input</code> or <code>output</code> [owner element]</h5>
<p>The <code>messageLabel</code> <em>attribute information
item</em> identifies the role of this message in the message
exchange pattern of the given <code>operation</code> <em>element
information item</em>.</p>
<p>The <code>messageLabel</code> <em>attribute information
item</em> has the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>messageLabel</code></p>
</li>
<li>
<p>A [namespace name] which has no value</p>
</li>
</ul>
<p>The type of the <code>messageLabel</code> <em>attribute
information item</em> is <em>xs:NCName</em>.</p>
</div>
<div class="div4">
<h5><a name="InterfaceMessageReference_element_attribute" id=
"InterfaceMessageReference_element_attribute"></a>2.5.2.2
<code>element</code> <em>attribute information item</em> with
<code>input</code> or <code>output</code> [owner element]</h5>
<p>The <code>element</code> <em>attribute information item</em> has
the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>element</code>.</p>
</li>
<li>
<p>A [namespace name] which has no value.</p>
</li>
</ul>
<p>The type of the <code>element</code> <em>attribute information
item</em> is a union of <em>xs:QName</em> and <em>xs:token</em>
where the allowed token values are <em>#any</em>, <em>#none</em>,
or <em>#other</em>.</p>
</div>
</div>
<div class="div3">
<h4><a name="InterfaceMessageReference_Mapping" id=
"InterfaceMessageReference_Mapping"></a>2.5.3 Mapping Interface
Message Reference's XML Representation to Component Properties</h4>
<p>The mapping from the XML Representation of the interface message
reference <em>element information item</em> (see <a href=
"#InterfaceMessageReference_XMLRep"><strong>2.5.2 XML
Representation of Interface Message Reference
Component</strong></a>) to the properties of the <a href=
"#component-InterfaceMessageReference">Interface Message
Reference</a> component (see <a href=
"#InterfaceMessageReference_details"><strong>2.5.1 The Interface
Message Reference Component</strong></a>) is as described in
<a href="#tab_InterfaceMessageReference_Mapping">Table 2-5</a> and
uses the definitions below.</p>
<p>Define the <em>message exchange pattern</em> of the <em>element
information item</em> to be the {<a href=
"#property-InterfaceOperation.messageexchangepattern">message
exchange pattern</a>} of the parent <a href=
"#component-InterfaceOperation">Interface Operation</a>
component.</p>
<p>Define the <em>message direction</em> of the <em>element
information item</em> to be <em>in</em> if its local name is
<code>input</code>, and <em>out</em> if its local name is
<code>output</code>.</p>
<p>Note that the <code>messageLabel</code> <em>attribute
information item</em> of an interface message reference <em>element
information item</em> must be present if the message exchange
pattern has more than one placeholder message with {<a href=
"#property-InterfaceMessageReference.direction">direction</a>}
equal to the message direction.</p>
<p><span id="MessageLabel-1030" class="test-assertion-tr">If the
<code>messageLabel</code> <em>attribute information item</em> of an
interface message reference <em>element information item</em> is
present, then its actual value MUST match the {<a href=
"#property-InterfaceMessageReference.messagelabel">message
label</a>} of some placeholder message with {<a href=
"#property-InterfaceMessageReference.direction">direction</a>}
equal to the message direction. <sup><a href=
"#MessageLabel-1030-summary" title=
"Link to assertion MessageLabel-1030 summary">†</a></sup></span></p>
<p><span id="MessageLabel-1031" class="test-assertion-tr">If the
<code>messageLabel</code> <em>attribute information item</em> of an
interface message reference <em>element information item</em> is
absent then there MUST be a unique placeholder message with
{<a href=
"#property-InterfaceMessageReference.direction">direction</a>}
equal to the message direction. <sup><a href=
"#MessageLabel-1031-summary" title=
"Link to assertion MessageLabel-1031 summary">†</a></sup></span></p>
<p>Define the <em>effective message label</em> of an interface
message reference <em>element information item</em> to be either
the actual value of the <code>messageLabel</code> <em>attribute
information item</em> if it is present, or the {<a href=
"#property-InterfaceMessageReference.messagelabel">message
label</a>} of the unique placeholder message with {<a href=
"#property-InterfaceMessageReference.direction">direction</a>}
equal to the message direction if the <em>attribute information
item</em> is absent.</p>
<p><span id="MessageLabel-1032" class="test-assertion-tr">If the
local name is <code>input</code> then the message exchange pattern
MUST have at least one placeholder message with direction
"In".<sup><a href="#MessageLabel-1032-summary" title=
"Link to assertion MessageLabel-1032 summary">†</a></sup></span></p>
<p><span id="MessageLabel-1033" class="test-assertion-tr">If the
local name is <code>output</code> then the message exchange pattern
MUST have at least one placeholder message with direction
"Out".<sup><a href="#MessageLabel-1033-summary" title=
"Link to assertion MessageLabel-1033 summary">†</a></sup></span></p>
<p><span id="MessageLabel-1034" class="test-assertion-tr">If the
local name is <code>infault</code> then the message exchange
pattern MUST support at least one fault in the "In"
direction.<sup><a href="#MessageLabel-1034-summary" title=
"Link to assertion MessageLabel-1034 summary">†</a></sup></span></p>
<p><span id="MessageLabel-1035" class="test-assertion-tr">If the
local name is <code>outfault</code> then the message exchange
pattern MUST support at least one fault in the "Out"
direction.<sup><a href="#MessageLabel-1035-summary" title=
"Link to assertion MessageLabel-1035 summary">†</a></sup></span></p>
<a name="tab_InterfaceMessageReference_Mapping" id=
"tab_InterfaceMessageReference_Mapping"></a>
<table border="1">
<caption>Table 2-5. Mapping from XML Representation to Interface
Message Reference Component Properties</caption>
<col width="20%" span="1" />
<col width="80%" span="1" />
<tbody>
<tr>
<th rowspan="1" colspan="1">Property</th>
<th rowspan="1" colspan="1">Value</th>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-InterfaceMessageReference.messagelabel">message
label</a>}</td>
<td rowspan="1" colspan="1">The effective message label.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-InterfaceMessageReference.direction">direction</a>}</td>
<td rowspan="1" colspan="1">The message direction.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-InterfaceMessageReference.messagecontentmodel">message
content model</a>}</td>
<td rowspan="1" colspan="1">If the <code>element</code>
<em>attribute information item</em> is present and its value is a
QName, then <em>#element</em>; otherwise the actual value of the
<code>element</code> <em>attribute information item</em>, if any;
otherwise <em>#other</em>.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-InterfaceMessageReference.elementdeclaration">element
declaration</a>}</td>
<td rowspan="1" colspan="1">If the <code>element</code>
<em>attribute information item</em> is present and its value is a
QName, then the <a href="#component-ElementDeclaration">Element
Declaration</a> component from the {<a href=
"#property-Description.elementdeclarations">element
declarations</a>} property of the <a href=
"#component-Description">Description</a> component resolved to by
the value of the <code>element</code> <em>attribute information
item</em> (see <a href="#qnameres"><strong>2.17 QName
resolution</strong></a>); otherwise empty. <span id=
"InterfaceMessageReference-1036" class="test-assertion-tr">If the
<code>element</code> <em>attribute information item</em> has a
value, then it MUST resolve to an <a href=
"#component-ElementDeclaration">Element Declaration</a> component
from the {<a href=
"#property-Description.elementdeclarations">element
declarations</a>} property of the <a href=
"#component-Description">Description</a> component.<sup><a href=
"#InterfaceMessageReference-1036-summary" title=
"Link to assertion InterfaceMessageReference-1036 summary">†</a></sup></span></td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-InterfaceMessageReference.parent">parent</a>}</td>
<td rowspan="1" colspan="1">The <a href=
"#component-InterfaceOperation">Interface Operation</a> component
corresponding to the <code>interface</code> <em>element information
item</em> in [parent].</td>
</tr>
</tbody>
</table>

<br /></div>
</div>
<div class="div2">
<h3><a name="InterfaceFaultReference" id=
"InterfaceFaultReference"></a>2.6 Interface Fault Reference</h3>
<div class="div3">
<h4><a name="InterfaceFaultReference_details" id=
"InterfaceFaultReference_details"></a>2.6.1 The Interface Fault
Reference Component</h4>
<p>An <a href="#component-InterfaceFaultReference">Interface Fault
Reference</a> component associates a defined type, specified by an
<a href="#component-InterfaceFault">Interface Fault</a> component,
to a fault message exchanged in an operation.</p>
<p>A message exchange pattern defines a set of placeholder messages
that participate in the pattern and assigns them unique message
labels within the pattern (e.g. 'In', 'Out'). The purpose of an
<a href="#component-InterfaceFaultReference">Interface Fault
Reference</a> component is to associate an actual message type (XML
element declaration or some other declaration (see <a href=
"#other-types"><strong>3.2 Using Other Schema
Languages</strong></a>) for message content, as specified by an
<a href="#component-InterfaceFault">Interface Fault</a> component)
with a fault message occurring in the pattern. In order to identify
the fault message it describes, the <a href=
"#component-InterfaceFaultReference">Interface Fault Reference</a>
component uses the message label of the message the fault is
associated with, as a key.</p>
<p>As indicated earlier, the companion specification
[<cite><a href="#WSDL-PART2">WSDL 2.0 Adjuncts</a></cite>] defines
several <em>fault propagation rulesets</em> that a given message
exchange pattern may use. For the ruleset
<em>fault-replaces-message</em>, the message that the fault relates
to identifies the message <em>in place of which</em> the declared
fault message will occur. Thus, the fault message will travel in
the <em>same</em> direction as the message it replaces in the
pattern. For the ruleset <em>message-triggers-fault</em>, the
message that the fault relates to identifies the message <em>after
which</em> the indicated fault may occur, in the opposite direction
of the referred to message. That is, the fault message will travel
in the <em>opposite</em> direction of the message it comes after in
the message exchange pattern.</p>
<p>The properties of the <a name=
"component-InterfaceFaultReference" id=
"component-InterfaceFaultReference">Interface Fault Reference</a>
component are as follows:</p>
<ul>
<li>
<p>{<a name="property-InterfaceFaultReference.interfacefault" id=
"property-InterfaceFaultReference.interfacefault">interface
fault</a>} REQUIRED. An <a href=
"#component-InterfaceFault">Interface Fault</a> component in the
{<a href="#property-Interface.interfacefaults">interface
faults</a>} property of the [parent] <a href=
"#component-InterfaceOperation">Interface Operation</a> component's
[parent] <a href="#component-Interface">Interface</a> component, or
an <a href="#component-Interface">Interface</a> component that it
directly or indirectly extends. Identifying the <a href=
"#component-InterfaceFault">Interface Fault</a> component therefore
indirectly defines the actual content or payload of the fault
message.</p>
</li>
<li>
<p>{<a name="property-InterfaceFaultReference.messagelabel" id=
"property-InterfaceFaultReference.messagelabel">message label</a>}
REQUIRED. An <em>xs:NCName</em>. This property identifies the
message this fault relates to among those defined in the {<a href=
"#property-InterfaceOperation.messageexchangepattern">message
exchange pattern</a>} property of the <a href=
"#component-InterfaceOperation">Interface Operation</a> component
it is contained within. <span id="InterfaceFaultReference-1037"
class="test-assertion-tr">The value of this property MUST match the
name of a placeholder message defined by the message exchange
pattern.<sup><a href="#InterfaceFaultReference-1037-summary" title=
"Link to assertion InterfaceFaultReference-1037 summary">†</a></sup></span></p>
</li>
<li>
<p>{<a name="property-InterfaceFaultReference.direction" id=
"property-InterfaceFaultReference.direction">direction</a>}
REQUIRED. A <em>xs:token</em> with one of the values <em>in</em> or
<em>out</em>, indicating whether the fault is coming to the service
or going from the service, respectively. <span id=
"InterfaceFaultReference-1038" class="test-assertion-tr">The
direction MUST be consistent with the direction implied by the
fault propagation ruleset used in the message exchange pattern of
the operation.<sup><a href="#InterfaceFaultReference-1038-summary"
title=
"Link to assertion InterfaceFaultReference-1038 summary">†</a></sup></span>
For example, if the ruleset <em>fault-replaces-message</em> is
used, then a fault that refers to an outgoing message would have a
{<a href=
"#property-InterfaceFaultReference.direction">direction</a>}
property value of <em>out</em>. On the other hand, if the ruleset
<em>message-triggers-fault</em> is used, then a fault that refers
to an outgoing message would have a {<a href=
"#property-InterfaceFaultReference.direction">direction</a>}
property value of <em>in</em> as the fault travels in the opposite
direction of the message.</p>
</li>
<li>
<p>{<a name="property-InterfaceFaultReference.parent" id=
"property-InterfaceFaultReference.parent">parent</a>} REQUIRED. The
<a href="#component-InterfaceOperation">Interface Operation</a>
component that contains this component in its {<a href=
"#property-InterfaceOperation.interfacefaultreferences">interface
fault references</a>} property.</p>
</li>
</ul>
<a name="zed-InterfaceFaultReference" id=
"zed-InterfaceFaultReference"></a><a name=
"zed-InterfaceFaultReferenceRI" id=
"zed-InterfaceFaultReferenceRI"></a>
<p><span id="InterfaceFaultReference-1039" class=
"test-assertion-tr">For each <a href=
"#component-InterfaceFaultReference">Interface Fault Reference</a>
component in the {<a href=
"#property-InterfaceOperation.interfacefaultreferences">interface
fault references</a>} property of an <a href=
"#component-InterfaceOperation">Interface Operation</a> component,
the combination of its {<a href=
"#property-InterfaceFaultReference.interfacefault">interface
fault</a>} and {<a href=
"#property-InterfaceFaultReference.messagelabel">message label</a>}
properties MUST be unique.<sup><a href=
"#InterfaceFaultReference-1039-summary" title=
"Link to assertion InterfaceFaultReference-1039 summary">†</a></sup></span></p>
<a name="zed-InterfaceFaultReferenceKey" id=
"zed-InterfaceFaultReferenceKey"></a><a name=
"zed-InterfaceFaultReferenceConsistent" id=
"zed-InterfaceFaultReferenceConsistent"></a><a name=
"zed-InterfaceFaultReferenceCM" id=
"zed-InterfaceFaultReferenceCM"></a></div>
<div class="div3">
<h4><a name="InterfaceFaultReference_XMLRep" id=
"InterfaceFaultReference_XMLRep"></a>2.6.2 XML Representation of
Interface Fault Reference</h4>
<div class="exampleInner">
<pre xml:space="preserve">
&lt;description&gt;
  &lt;interface&gt;
    &lt;operation&gt;
      &lt;<strong>infault</strong>
            ref="<em>xs:QName</em>"
            messageLabel="<em>xs:NCName</em>"? &gt;
        &lt;documentation /&gt;*
      &lt;/<strong>infault</strong>&gt;*
      &lt;<strong>outfault</strong>
            ref="<em>xs:QName</em>"
            messageLabel="<em>xs:NCName</em>"? &gt;
        &lt;documentation /&gt;*
      &lt;/<strong>outfault</strong>&gt;*
    &lt;/operation&gt;
  &lt;/interface&gt;
&lt;/description&gt;
</pre></div>
<p>The XML representation for an <a href=
"#component-InterfaceFaultReference">Interface Fault Reference</a>
component is an <em>element information item</em> with the
following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>infault</code> or
<code>outfault</code></p>
</li>
<li>
<p>A [namespace name] of "http://www.w3.org/ns/wsdl"</p>
</li>
<li>
<p>One or more <em>attribute information item</em>s amongst its
[attributes] as follows:</p>
<ul>
<li>
<p>A REQUIRED <code>ref</code> <em>attribute information item</em>
as described below in <a href=
"#InterfaceFaultReference_ref_attribute"><strong>2.6.2.1 ref
attribute information item with infault, or outfault [owner
element]</strong></a>.</p>
</li>
<li>
<p>An OPTIONAL <code>messageLabel</code> <em>attribute information
item</em> as described below in <a href=
"#InterfaceFaultReference_messageReference_attribute"><strong>2.6.2.2
messageLabel attribute information item with infault, or outfault
[owner element]</strong></a>.</p>
</li>
<li>
<p>Zero or more namespace qualified <em>attribute information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl".</p>
</li>
</ul>
</li>
<li>
<p>Zero or more <em>element information item</em> amongst its
[children], in order, as follows:</p>
<ol class="enumar">
<li>
<p>Zero or more <code>documentation</code> <em>element information
item</em>s (see <a href="#eii-documentation"><strong>5.
Documentation</strong></a>).</p>
</li>
<li>
<p>Zero or more namespace-qualified <em>element information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl".</p>
</li>
</ol>
</li>
</ul>
<div class="div4">
<h5><a name="InterfaceFaultReference_ref_attribute" id=
"InterfaceFaultReference_ref_attribute"></a>2.6.2.1
<code>ref</code> <em>attribute information item</em> with
<code>infault</code>, or <code>outfault</code> [owner element]</h5>
<p>The <code>ref</code> <em>attribute information item</em> refers
to a fault component.</p>
<p>The <code>ref</code> <em>attribute information item</em> has the
following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>ref</code></p>
</li>
<li>
<p>A [namespace name] which has no value</p>
</li>
</ul>
<p>The type of the <code>ref</code> <em>attribute information
item</em> is <em>xs:QName</em>.</p>
</div>
<div class="div4">
<h5><a name="InterfaceFaultReference_messageReference_attribute"
id="InterfaceFaultReference_messageReference_attribute"></a>2.6.2.2
<code>messageLabel</code> <em>attribute information item</em> with
<code>infault</code>, or <code>outfault</code> [owner element]</h5>
<p>The <code>messageLabel</code> <em>attribute information
item</em> identifies the message in the message exchange pattern of
the given <code>operation</code> <em>element information item</em>
that is associated with this fault.</p>
<p>The <code>messageLabel</code> <em>attribute information
item</em> has the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>messageLabel</code></p>
</li>
<li>
<p>A [namespace name] which has no value</p>
</li>
</ul>
<p>The type of the <code>messageLabel</code> <em>attribute
information item</em> is <em>xs:NCName</em>.</p>
<p><span id="InterfaceFaultReference-1040" class=
"test-assertion-tr">The <code>messageLabel</code> <em>attribute
information item</em> MUST be present in the XML representation of
an <a href="#component-InterfaceFaultReference">Interface Fault
Reference</a> component with a given {<a href=
"#property-InterfaceFaultReference.direction">direction</a>}, if
the {<a href=
"#property-InterfaceOperation.messageexchangepattern">message
exchange pattern</a>} of the parent <a href=
"#component-InterfaceOperation">Interface Operation</a> component
has more than one fault with that direction.<sup><a href=
"#InterfaceFaultReference-1040-summary" title=
"Link to assertion InterfaceFaultReference-1040 summary">†</a></sup></span>
Recall that the <em>fault propagation ruleset</em> of the {<a href=
"#property-InterfaceOperation.messageexchangepattern">message
exchange pattern</a>} specifies the relation between faults and
messages. For example, the <em>fault-replaces-message</em> ruleset
specifies that the faults have the same direction as the messages,
while the <em>message-triggers-fault</em> ruleset specifies that
the faults have the opposite direction from the messages.</p>
</div>
</div>
<div class="div3">
<h4><a name="InterfaceFaultReference_Mapping" id=
"InterfaceFaultReference_Mapping"></a>2.6.3 Mapping Interface Fault
Reference's XML Representation to Component Properties</h4>
<p>The mapping from the XML Representation of the message reference
<em>element information item</em> (see <a href=
"#InterfaceFaultReference_XMLRep"><strong>2.6.2 XML Representation
of Interface Fault Reference</strong></a>) to the properties of the
Interface Fault Reference component (see <a href=
"#InterfaceFaultReference_details"><strong>2.6.1 The Interface
Fault Reference Component</strong></a>) is as described in <a href=
"#tab_InterfaceFaultReference_Mapping">Table 2-6</a> and uses the
definitions below.</p>
<p>Define the <em>message exchange pattern</em> of the <em>element
information item</em> to be the {<a href=
"#property-InterfaceOperation.messageexchangepattern">message
exchange pattern</a>} of the parent <a href=
"#component-InterfaceOperation">Interface Operation</a>
component.</p>
<p>Define the <em>fault direction</em> of the <em>element
information item</em> to be <em>in</em> if its local name is
<code>infault</code> and <em>out</em> if its local name is
<code>outfault</code>.</p>
<p>Define the <em>message direction</em> of the <em>element
information item</em> to be the {<a href=
"#property-InterfaceMessageReference.direction">direction</a>} of
the placeholder message associated with the fault as specified by
the fault propagation ruleset of the message exchange pattern.</p>
<p><span id="MessageLabel-1041" class="test-assertion-tr">The
<code>messageLabel</code> <em>attribute information item</em> of an
interface fault reference <em>element information item</em> MUST be
present if the message exchange pattern has more than one
placeholder message with {<a href=
"#property-InterfaceMessageReference.direction">direction</a>}
equal to the message direction. <sup><a href=
"#MessageLabel-1041-summary" title=
"Link to assertion MessageLabel-1041 summary">†</a></sup></span></p>
<p><span id="MessageLabel-1042" class="test-assertion-tr">If the
<code>messageLabel</code> <em>attribute information item</em> of an
interface fault reference <em>element information item</em> is
present then its actual value MUST match the {<a href=
"#property-InterfaceMessageReference.messagelabel">message
label</a>} of some placeholder message with {<a href=
"#property-InterfaceMessageReference.direction">direction</a>}
equal to the message direction. <sup><a href=
"#MessageLabel-1042-summary" title=
"Link to assertion MessageLabel-1042 summary">†</a></sup></span></p>
<p><span id="MessageLabel-1043" class="test-assertion-tr">If the
<code>messageLabel</code> <em>attribute information item</em> of an
interface fault reference <em>element information item</em> is
absent then there MUST be a unique placeholder message with
{<a href=
"#property-InterfaceMessageReference.direction">direction</a>}
equal to the message direction. <sup><a href=
"#MessageLabel-1043-summary" title=
"Link to assertion MessageLabel-1043 summary">†</a></sup></span></p>
<p>Define the <em>effective message label</em> of an interface
fault reference <em>element information item</em> to be either the
actual value of the <code>messageLabel</code> <em>attribute
information item</em> if it is present, or the {<a href=
"#property-InterfaceMessageReference.messagelabel">message
label</a>} of the unique placeholder message whose {<a href=
"#property-InterfaceMessageReference.direction">direction</a>} is
equal to the message direction if the <em>attribute information
item</em> is absent.</p>
<a name="tab_InterfaceFaultReference_Mapping" id=
"tab_InterfaceFaultReference_Mapping"></a>
<table border="1">
<caption>Table 2-6. Mapping from XML Representation to Interface
Fault Reference Component Properties</caption>
<col width="20%" span="1" />
<col width="80%" span="1" />
<tbody>
<tr>
<th rowspan="1" colspan="1">Property</th>
<th rowspan="1" colspan="1">Value</th>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-InterfaceFaultReference.interfacefault">interface
fault</a>}</td>
<td rowspan="1" colspan="1">The <a href=
"#component-InterfaceFault">Interface Fault</a> component from
{<a href="#property-Interface.interfacefaults">interface
faults</a>} property of the parent <a href=
"#component-Interface">Interface</a> component, or an <a href=
"#component-Interface">Interface</a> component that it directly or
indirectly extends, with {<a href=
"#property-InterfaceFault.name">name</a>} equal to the actual value
of the <code>ref</code> <em>attribute information item</em>.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-InterfaceFaultReference.messagelabel">message
label</a>}</td>
<td rowspan="1" colspan="1">The effective message label.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-InterfaceFaultReference.direction">direction</a>}</td>
<td rowspan="1" colspan="1">The fault direction.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-InterfaceFaultReference.parent">parent</a>}</td>
<td rowspan="1" colspan="1">The <a href=
"#component-InterfaceOperation">Interface Operation</a> component
corresponding to the <code>interface</code> <em>element information
item</em> in [parent].</td>
</tr>
</tbody>
</table>

<br /></div>
</div>
<div class="div2">
<h3><a name="Binding" id="Binding"></a>2.7 Binding</h3>
<div class="div3">
<h4><a name="Binding_details" id="Binding_details"></a>2.7.1 The
Binding Component</h4>
<p>A <a href="#component-Binding">Binding</a> component describes a
concrete message format and transmission protocol which may be used
to define an endpoint (see <a href="#Endpoint"><strong>2.13
Endpoint</strong></a>). That is, a <a href=
"#component-Binding">Binding</a> component defines the
implementation details necessary to access the service.</p>
<p><a href="#component-Binding">Binding</a> components can be used
to describe such information in a reusable manner for any interface
or specifically for a given interface. Furthermore, binding
information MAY be specified on a per-operation basis (see <a href=
"#Binding_Operation_details"><strong>2.9.1 The Binding Operation
Component</strong></a>) within an interface, in addition to across
all operations of an interface.</p>
<p><span id="Binding-1044" class="test-assertion-tr">If a <a href=
"#component-Binding">Binding</a> component specifies any
operation-specific binding details (by including <a href=
"#component-BindingOperation">Binding Operation</a> components) or
any fault binding details (by including <a href=
"#component-BindingFault">Binding Fault</a> components), then it
MUST specify an interface the <a href=
"#component-Binding">Binding</a> component applies to, so as to
indicate which interface the operations come from.<sup><a href=
"#Binding-1044-summary" title=
"Link to assertion Binding-1044 summary">†</a></sup></span></p>
<p>Conversely, a <a href="#component-Binding">Binding</a> component
which omits any operation-specific binding details and any fault
binding details MAY omit specifying an interface. <a href=
"#component-Binding">Binding</a> components that do not specify an
interface MAY be used to specify operation-independent binding
details for <a href="#component-Service">Service</a> components
with different interfaces. That is, such <a href=
"#component-Binding">Binding</a> components are reusable across one
or more interfaces.</p>
<p>No concrete binding details are given in this specification. The
companion specification, <em>Web Services Description Language
(WSDL) Version 2.0 Part 2: Adjuncts</em> [<cite><a href=
"#WSDL-PART2">WSDL 2.0 Adjuncts</a></cite>] defines such bindings
for SOAP 1.2 [<cite><a href="#SOAP12-PART1">SOAP 1.2 Part 1:
Messaging Framework (Second Edition)</a></cite>] and HTTP
[<cite><a href="#RFC2616">IETF RFC 2616</a></cite>]. Other
specifications MAY define additional binding details. Such
specifications are expected to annotate the <a href=
"#component-Binding">Binding</a> component (and its sub-components)
with additional properties and specify the mapping from the XML
representation to these properties.</p>
<p><span id="Binding-1045" class="test-assertion-tr">A <a href=
"#component-Binding">Binding</a> component that defines bindings
for an <a href="#component-Interface">Interface</a> component MUST
define bindings for all the operations of that <a href=
"#component-Interface">Interface</a> component.<sup><a href=
"#Binding-1045-summary" title=
"Link to assertion Binding-1045 summary">†</a></sup></span> The
bindings can occur via defaulting rules which allow one to specify
default bindings for all operations and faults (see, for example
[<cite><a href="#WSDL-PART2">WSDL 2.0 Adjuncts</a></cite>]) or by
defining bindings for each <a href=
"#component-InterfaceOperation">Interface Operation</a> and
<a href="#component-InterfaceFault">Interface Fault</a> component
of the <a href="#component-Interface">Interface</a> component.</p>
<p><span id="Binding-1046" class="test-assertion-tr">Similarly,
whenever a reusable <a href="#component-Binding">Binding</a>
component (i.e. one that does not specify an <a href=
"#component-Interface">Interface</a> component) is applied to a
specific <a href="#component-Interface">Interface</a> component in
the context of an <a href="#component-Endpoint">Endpoint</a>
component (see <a href="#Endpoint_details"><strong>2.13.1 The
Endpoint Component</strong></a>), the <a href=
"#component-Binding">Binding</a> component MUST define bindings for
each <a href="#component-InterfaceOperation">Interface
Operation</a> and <a href="#component-InterfaceFault">Interface
Fault</a> component of the <a href=
"#component-Interface">Interface</a> component, via a combination
of properties defined on the <a href=
"#component-Binding">Binding</a> component itself and default
binding rules specific to its binding type.<sup><a href=
"#Binding-1046-summary" title=
"Link to assertion Binding-1046 summary">†</a></sup></span></p>
<p><span id="Binding-1047" class="test-assertion-tr">A <a href=
"#component-Binding">Binding</a> component that defines bindings
for an <a href="#component-Interface">Interface</a> component MUST
define bindings for all the faults of that <a href=
"#component-Interface">Interface</a> component that are referenced
from any of the operations in that <a href=
"#component-Interface">Interface</a> component.<sup><a href=
"#Binding-1047-summary" title=
"Link to assertion Binding-1047 summary">†</a></sup></span> As for
the case of operations, the binding can be defined by defaulting
rules. Note that only the faults actually referenced by operations
are required to have bindings.</p>
<p>Bindings are named constructs and can be referred to by QName
(see <a href="#qnameres"><strong>2.17 QName
resolution</strong></a>). For instance, <a href=
"#component-Endpoint">Endpoint</a> components refer to bindings in
this way.</p>
<p>The properties of the <a name="component-Binding" id=
"component-Binding">Binding</a> component are as follows:</p>
<ul>
<li>
<p>{<a name="property-Binding.name" id=
"property-Binding.name">name</a>} REQUIRED. An
<em>xs:QName</em>.</p>
</li>
<li>
<p>{<a name="property-Binding.interface" id=
"property-Binding.interface">interface</a>} OPTIONAL. An <a href=
"#component-Interface">Interface</a> component indicating the
interface for which binding information is being specified.</p>
</li>
<li>
<p>{<a name="property-Binding.type" id=
"property-Binding.type">type</a>} REQUIRED. An <em>xs:anyURI</em>.
<span id="Binding-1048" class="test-assertion-tr">This
<em>xs:anyURI</em> MUST be an absolute IRI as defined by
[<cite><a href="#RFC3987">IETF RFC 3987</a></cite>].<sup><a href=
"#Binding-1048-summary" title=
"Link to assertion Binding-1048 summary">†</a></sup></span> The
value of this IRI indicates what kind of concrete binding details
are contained within this <a href="#component-Binding">Binding</a>
component. Specifications (such as [<cite><a href=
"#WSDL-PART2">WSDL 2.0 Adjuncts</a></cite>]) that define such
concrete binding details MUST specify appropriate values for this
property. The value of this property MAY be the namespace name of
the extension elements or attributes which define those concrete
binding details.</p>
</li>
<li>
<p>{<a name="property-Binding.bindingfaults" id=
"property-Binding.bindingfaults">binding faults</a>} OPTIONAL. A
set of <a href="#component-BindingFault">Binding Fault</a>
components.</p>
</li>
<li>
<p>{<a name="property-Binding.bindingoperations" id=
"property-Binding.bindingoperations">binding operations</a>}
OPTIONAL. A set of <a href="#component-BindingOperation">Binding
Operation</a> components.</p>
</li>
</ul>
<a name="zed-Binding" id="zed-Binding"></a><a name="zed-BindingRI"
id="zed-BindingRI"></a>
<p><span id="Binding-1049" class="test-assertion-tr">For each
<a href="#component-Binding">Binding</a> component in the {<a href=
"#property-Description.bindings">bindings</a>} property of a
<a href="#component-Description">Description</a> component, the
{<a href="#property-Binding.name">name</a>} property MUST be
unique.<sup><a href="#Binding-1049-summary" title=
"Link to assertion Binding-1049 summary">†</a></sup></span></p>
<a name="zed-BindingKey" id="zed-BindingKey"></a><a name=
"zed-BindingParent" id="zed-BindingParent"></a><a name=
"zed-BindingCM" id="zed-BindingCM"></a></div>
<div class="div3">
<h4><a name="Binding_XMLRep" id="Binding_XMLRep"></a>2.7.2 XML
Representation of Binding Component</h4>
<div class="exampleInner">
<pre xml:space="preserve">
&lt;description&gt;
  &lt;<strong>binding</strong>
        name="<em>xs:NCName</em>" 
        interface="<em>xs:QName</em>"?
        type="<em>xs:anyURI</em>" &gt;
    &lt;documentation /&gt;*
    [ &lt;fault /&gt; | &lt;operation /&gt; ]*
  &lt;/<strong>binding</strong>&gt;
&lt;/description&gt;
</pre></div>
<p>The XML representation for a <a href=
"#component-Binding">Binding</a> component is an <em>element
information item</em> with the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>binding</code></p>
</li>
<li>
<p>A [namespace name] of "http://www.w3.org/ns/wsdl"</p>
</li>
<li>
<p>Two or more <em>attribute information item</em>s amongst its
[attributes] as follows:</p>
<ul>
<li>
<p>A REQUIRED <code>name</code> <em>attribute information item</em>
as described below in <a href=
"#Binding_name_attribute"><strong>2.7.2.1 name attribute
information item with binding [owner element]</strong></a>.</p>
</li>
<li>
<p>An OPTIONAL <code>interface</code> <em>attribute information
item</em> as described below in <a href=
"#Binding_interface_attribute"><strong>2.7.2.2 interface attribute
information item with binding [owner element]</strong></a>.</p>
</li>
<li>
<p>An REQUIRED <code>type</code> <em>attribute information
item</em> as described below in <a href=
"#Binding_type_attribute"><strong>2.7.2.3 type attribute
information item with binding [owner element]</strong></a>.</p>
</li>
<li>
<p>Zero or more namespace qualified <em>attribute information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl".</p>
</li>
</ul>
</li>
<li>
<p>Zero or more <em>element information item</em>s amongst its
[children], in order, as follows:</p>
<ol class="enumar">
<li>
<p>Zero or more <code>documentation</code> <em>element information
item</em>s (see <a href="#eii-documentation"><strong>5.
Documentation</strong></a>).</p>
</li>
<li>
<p>Zero or more <em>element information item</em>s from among the
following, in any order:</p>
<ul>
<li>
<p>Zero or more <code>fault</code> <em>element information
item</em>s (see <a href="#Binding_Fault_XMLRep"><strong>2.8.2 XML
Representation of Binding Fault Component</strong></a>).</p>
</li>
<li>
<p>Zero or more <code>operation</code> <em>element information
item</em>s (see <a href="#Binding_Operation_XMLRep"><strong>2.9.2
XML Representation of Binding Operation
Component</strong></a>).</p>
</li>
<li>
<p>Zero or more namespace-qualified <em>element information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl". Such <em>element information
item</em>s are considered to be binding extension elements(see
<a href="#Binding_extension_elements"><strong>2.7.2.4 Binding
extension elements</strong></a>).</p>
</li>
</ul>
</li>
</ol>
</li>
</ul>
<div class="div4">
<h5><a name="Binding_name_attribute" id=
"Binding_name_attribute"></a>2.7.2.1 <code>name</code>
<em>attribute information item</em> with <code>binding</code>
[owner element]</h5>
<p>The <code>name</code> <em>attribute information item</em>
together with the <code>targetNamespace</code> <em>attribute
information item</em> of the <code>description</code> <em>element
information item</em> forms the QName of the binding.</p>
<p>The <code>name</code> <em>attribute information item</em> has
the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>name</code></p>
</li>
<li>
<p>A [namespace name] which has no value</p>
</li>
</ul>
<p>The type of the <code>name</code> <em>attribute information
item</em> is <em>xs:NCName</em>.</p>
</div>
<div class="div4">
<h5><a name="Binding_interface_attribute" id=
"Binding_interface_attribute"></a>2.7.2.2 <code>interface</code>
<em>attribute information item</em> with <code>binding</code>
[owner element]</h5>
<p>The <code>interface</code> <em>attribute information item</em>
refers, by QName, to an <a href=
"#component-Interface">Interface</a> component.</p>
<p>The <code>interface</code> <em>attribute information item</em>
has the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>interface</code></p>
</li>
<li>
<p>A [namespace name] which has no value</p>
</li>
</ul>
<p>The type of the <code>interface</code> <em>attribute information
item</em> is <em>xs:QName</em>.</p>
</div>
<div class="div4">
<h5><a name="Binding_type_attribute" id=
"Binding_type_attribute"></a>2.7.2.3 <code>type</code>
<em>attribute information item</em> with <code>binding</code>
[owner element]</h5>
<p>The <code>type</code> <em>attribute information item</em>
identifies the kind of binding details contained in the <a href=
"#component-Binding">Binding</a> component.</p>
<p>The <code>type</code> <em>attribute information item</em> has
the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>type</code></p>
</li>
<li>
<p>A [namespace name] which has no value</p>
</li>
</ul>
<p>The type of the <code>type</code> <em>attribute information
item</em> is <em>xs:anyURI</em>.</p>
</div>
<div class="div4">
<h5><a name="Binding_extension_elements" id=
"Binding_extension_elements"></a>2.7.2.4 Binding extension
elements</h5>
<p>Binding extension elements are used to provide information
specific to a particular binding. The semantics of such <em>element
information item</em>s are defined by the specification for those
<em>element information item</em>s. Such specifications are
expected to annotate the <a href="#component-Binding">Binding</a>
component with additional properties and specify the mapping from
the XML representation to those properties.</p>
</div>
</div>
<div class="div3">
<h4><a name="Binding_Mapping" id="Binding_Mapping"></a>2.7.3
Mapping Binding's XML Representation to Component Properties</h4>
<p>The mapping from the XML Representation of the
<code>binding</code> <em>element information item</em> (see
<a href="#Binding_XMLRep"><strong>2.7.2 XML Representation of
Binding Component</strong></a>) to the properties of the <a href=
"#component-Binding">Binding</a> component (see <a href=
"#Binding_details"><strong>2.7.1 The Binding
Component</strong></a>) is as described in <a href=
"#tab_Binding_Mapping">Table 2-7</a>.</p>
<a name="tab_Binding_Mapping" id="tab_Binding_Mapping"></a>
<table border="1">
<caption>Table 2-7. Mapping from XML Representation to Binding
Component Properties</caption>
<col width="20%" span="1" />
<col width="80%" span="1" />
<tbody>
<tr>
<th rowspan="1" colspan="1">Property</th>
<th rowspan="1" colspan="1">Value</th>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-Binding.name">name</a>}</td>
<td rowspan="1" colspan="1">The QName whose local name is the
actual value of the <code>name</code> <em>attribute information
item</em> and whose namespace name is the actual value of the
<code>targetNamespace</code> <em>attribute information item</em> of
the [parent] <code>description</code> <em>element information
item</em>.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-Binding.interface">interface</a>}</td>
<td rowspan="1" colspan="1">The <a href=
"#component-Interface">Interface</a> component resolved to by the
actual value of the <code>interface</code> <em>attribute
information item</em> (see <a href="#qnameres"><strong>2.17 QName
resolution</strong></a>), if any.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-Binding.type">type</a>}</td>
<td rowspan="1" colspan="1">The actual value of the
<code>type</code> <em>attribute information item</em>.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-Binding.bindingfaults">binding faults</a>}</td>
<td rowspan="1" colspan="1">The set of <a href=
"#component-BindingFault">Binding Fault</a> components
corresponding to the <code>fault</code> <em>element information
item</em>s in [children], if any.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-Binding.bindingoperations">binding operations</a>}</td>
<td rowspan="1" colspan="1">The set of <a href=
"#component-BindingOperation">Binding Operation</a> components
corresponding to the <code>operation</code> <em>element information
item</em>s in [children], if any.</td>
</tr>
</tbody>
</table>

<br /></div>
</div>
<div class="div2">
<h3><a name="Binding_Fault" id="Binding_Fault"></a>2.8 Binding
Fault</h3>
<div class="div3">
<h4><a name="Binding_Fault_details" id=
"Binding_Fault_details"></a>2.8.1 The Binding Fault Component</h4>
<p>A <a href="#component-BindingFault">Binding Fault</a> component
describes a concrete binding of a particular fault within an
interface to a particular concrete message format. A particular
fault of an interface is uniquely identified by its {<a href=
"#property-InterfaceFault.name">name</a>} property.</p>
<p>Note that the fault does not occur by itself -it occurs as part
of a message exchange as defined by an <a href=
"#component-InterfaceOperation">Interface Operation</a> component
(and its binding counterpart the <a href=
"#component-BindingOperation">Binding Operation</a> component).
Thus, the fault binding information specified in a <a href=
"#component-BindingFault">Binding Fault</a> component describes how
faults that occur within a message exchange of an operation will be
formatted and carried in the transport.</p>
<p>The properties of the <a name="component-BindingFault" id=
"component-BindingFault">Binding Fault</a> component are as
follows:</p>
<ul>
<li>
<p>{<a name="property-BindingFault.interfacefault" id=
"property-BindingFault.interfacefault">interface fault</a>}
REQUIRED. An <a href="#component-InterfaceFault">Interface
Fault</a> component in the {<a href=
"#property-Interface.interfacefaults">interface faults</a>}
property of the <a href="#component-Interface">Interface</a>
component identified by the {<a href=
"#property-Binding.interface">interface</a>} property of the parent
<a href="#component-Binding">Binding</a> component, or an <a href=
"#component-Interface">Interface</a> component that that <a href=
"#component-Interface">Interface</a> component directly or
indirectly extends. This is the <a href=
"#component-InterfaceFault">Interface Fault</a> component for which
binding information is being specified.</p>
</li>
<li>
<p>{<a name="property-BindingFault.parent" id=
"property-BindingFault.parent">parent</a>} REQUIRED. The <a href=
"#component-Binding">Binding</a> component that contains this
component in its {<a href="#property-Binding.bindingfaults">binding
faults</a>} property.</p>
</li>
</ul>
<a name="zed-BindingFault" id="zed-BindingFault"></a><a name=
"zed-BindingFaultRI" id="zed-BindingFaultRI"></a>
<p><span id="BindingFault-1050" class="test-assertion-tr">For each
<a href="#component-BindingFault">Binding Fault</a> component in
the {<a href="#property-Binding.bindingfaults">binding faults</a>}
property of a <a href="#component-Binding">Binding</a> component,
the {<a href="#property-BindingFault.interfacefault">interface
fault</a>} property MUST be unique.<sup><a href=
"#BindingFault-1050-summary" title=
"Link to assertion BindingFault-1050 summary">†</a></sup></span>
That is, one cannot define multiple bindings for the same fault
within a given <a href="#component-Binding">Binding</a>
component.</p>
<a name="zed-BindingFaultKey" id="zed-BindingFaultKey"></a><a name=
"zed-BindingFaultConsistent" id=
"zed-BindingFaultConsistent"></a><a name="zed-BindingFaultCM" id=
"zed-BindingFaultCM"></a></div>
<div class="div3">
<h4><a name="Binding_Fault_XMLRep" id=
"Binding_Fault_XMLRep"></a>2.8.2 XML Representation of Binding
Fault Component</h4>
<div class="exampleInner">
<pre xml:space="preserve">
&lt;description&gt;
  &lt;binding&gt;
    &lt;<strong>fault</strong>
          ref="<em>xs:QName</em>" &gt;
      &lt;documentation /&gt;*
    &lt;/<strong>fault</strong>&gt;
  &lt;/binding&gt;
&lt;/description&gt;
</pre></div>
<p>The XML representation for a <a href=
"#component-BindingFault">Binding Fault</a> component is an
<em>element information item</em> with the following Infoset
properties:</p>
<ul>
<li>
<p>A [local name] of <code>fault</code></p>
</li>
<li>
<p>A [namespace name] of "http://www.w3.org/ns/wsdl"</p>
</li>
<li>
<p>One or more <em>attribute information item</em>s amongst its
[attributes] as follows:</p>
<ul>
<li>
<p>A REQUIRED <code>ref</code> <em>attribute information item</em>
as described below in <a href=
"#Binding_Fault_ref_attribute"><strong>2.8.2.1 ref attribute
information item with fault [owner element]</strong></a>.</p>
</li>
<li>
<p>Zero or more namespace qualified <em>attribute information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl".</p>
</li>
</ul>
</li>
<li>
<p>Zero or more <em>element information item</em> amongst its
[children], in order, as follows:</p>
<ol class="enumar">
<li>
<p>Zero or more <code>documentation</code> <em>element information
item</em>s (see <a href="#eii-documentation"><strong>5.
Documentation</strong></a>).</p>
</li>
<li>
<p>Zero or more namespace-qualified <em>element information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl". Such <em>element information
item</em>s are considered to be binding fault extension elements as
described further below (see <a href=
"#Binding_Fault_extension_elements"><strong>2.8.2.2 Binding Fault
extension elements</strong></a>).</p>
</li>
</ol>
</li>
</ul>
<div class="div4">
<h5><a name="Binding_Fault_ref_attribute" id=
"Binding_Fault_ref_attribute"></a>2.8.2.1 <code>ref</code>
<em>attribute information item</em> with <code>fault</code> [owner
element]</h5>
<p>The <code>ref</code> <em>attribute information item</em> has the
following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>ref</code></p>
</li>
<li>
<p>A [namespace name] which has no value</p>
</li>
</ul>
<p>The type of the <code>ref</code> <em>attribute information
item</em> is <em>xs:QName</em>.</p>
</div>
<div class="div4">
<h5><a name="Binding_Fault_extension_elements" id=
"Binding_Fault_extension_elements"></a>2.8.2.2 Binding Fault
extension elements</h5>
<p>Binding Fault extension elements are used to provide information
specific to a particular fault in a binding. The semantics of such
<em>element information item</em>s are defined by the specification
for those <em>element information item</em>s. Such specifications
are expected to annotate the <a href=
"#component-BindingFault">Binding Fault</a> component with
additional properties and specify the mapping from the XML
representation to those properties.</p>
</div>
</div>
<div class="div3">
<h4><a name="Binding_Fault_Mapping" id=
"Binding_Fault_Mapping"></a>2.8.3 Mapping Binding Fault's XML
Representation to Component Properties</h4>
<p>The mapping from the XML Representation of the
<code>fault</code> <em>element information item</em> (see <a href=
"#Binding_Fault_XMLRep"><strong>2.8.2 XML Representation of Binding
Fault Component</strong></a>) to the properties of the <a href=
"#component-BindingFault">Binding Fault</a> component (see <a href=
"#Binding_Fault_details"><strong>2.8.1 The Binding Fault
Component</strong></a>) is as described in <a href=
"#tab_Binding_Fault_Mapping">Table 2-8</a>.</p>
<a name="tab_Binding_Fault_Mapping" id=
"tab_Binding_Fault_Mapping"></a>
<table border="1">
<caption>Table 2-8. Mapping from XML Representation to Binding
Fault Component Properties</caption>
<col width="20%" span="1" />
<col width="80%" span="1" />
<tbody>
<tr>
<th rowspan="1" colspan="1">Property</th>
<th rowspan="1" colspan="1">Value</th>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-BindingFault.interfacefault">interface fault</a>}</td>
<td rowspan="1" colspan="1">The <a href=
"#component-InterfaceFault">Interface Fault</a> component
corresponding to the actual value of the <code>ref</code>
<em>attribute information item</em>.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-BindingFault.parent">parent</a>}</td>
<td rowspan="1" colspan="1">The <a href=
"#component-Binding">Binding</a> component corresponding to the
<code>binding</code> <em>element information item</em> in
[parent].</td>
</tr>
</tbody>
</table>

<br /></div>
</div>
<div class="div2">
<h3><a name="Binding_Operation" id="Binding_Operation"></a>2.9
Binding Operation</h3>
<div class="div3">
<h4><a name="Binding_Operation_details" id=
"Binding_Operation_details"></a>2.9.1 The Binding Operation
Component</h4>
<p>The <a href="#component-BindingOperation">Binding Operation</a>
component describes the concrete message format(s) and protocol
interaction(s) associated with a particular interface operation for
a given endpoint. A particular operation of an interface is
uniquely identified by its {<a href=
"#property-InterfaceOperation.name">name</a>} property.</p>
<p>The properties of the <a name="component-BindingOperation" id=
"component-BindingOperation">Binding Operation</a> component are as
follows:</p>
<ul>
<li>
<p>{<a name="property-BindingOperation.interfaceoperation" id=
"property-BindingOperation.interfaceoperation">interface
operation</a>} REQUIRED. An <a href=
"#component-InterfaceOperation">Interface Operation</a> component
in the {<a href="#property-Interface.interfaceoperations">interface
operations</a>} property of the <a href=
"#component-Interface">Interface</a> component identified by the
{<a href="#property-Binding.interface">interface</a>} property of
the [parent] <a href="#component-Binding">Binding</a> component, or
an Interface component that that <a href=
"#component-Interface">Interface</a> component directly or
indirectly extends. This is the <a href=
"#component-InterfaceOperation">Interface Operation</a> component
for which binding information is being specified.</p>
</li>
<li>
<p>{<a name="property-BindingOperation.bindingmessagereferences"
id="property-BindingOperation.bindingmessagereferences">binding
message references</a>} OPTIONAL. A set of <a href=
"#component-BindingMessageReference">Binding Message Reference</a>
components.</p>
</li>
<li>
<p>{<a name="property-BindingOperation.bindingfaultreferences" id=
"property-BindingOperation.bindingfaultreferences">binding fault
references</a>} OPTIONAL. A set of <a href=
"#component-BindingFaultReference">Binding Fault Reference</a>
components.</p>
</li>
<li>
<p>{<a name="property-BindingOperation.parent" id=
"property-BindingOperation.parent">parent</a>} REQUIRED. The
<a href="#component-Binding">Binding</a> component that contains
this component in its {<a href=
"#property-Binding.bindingoperations">binding operations</a>}
property.</p>
</li>
</ul>
<a name="zed-BindingOperation" id=
"zed-BindingOperation"></a><a name="zed-BindingOperationRI" id=
"zed-BindingOperationRI"></a>
<p><span id="BindingOperation-1051" class="test-assertion-tr">For
each <a href="#component-BindingOperation">Binding Operation</a>
component in the {<a href=
"#property-Binding.bindingoperations">binding operations</a>}
property of a <a href="#component-Binding">Binding</a> component,
the {<a href=
"#property-BindingOperation.interfaceoperation">interface
operation</a>} property MUST be unique.<sup><a href=
"#BindingOperation-1051-summary" title=
"Link to assertion BindingOperation-1051 summary">†</a></sup></span>
That is, one cannot define multiple bindings for the same operation
within a given <a href="#component-Binding">Binding</a>
component.</p>
<a name="zed-BindingOperationKey" id=
"zed-BindingOperationKey"></a><a name="zed-BindingOperationParent"
id="zed-BindingOperationParent"></a><a name=
"zed-BindingOperationConsistent" id=
"zed-BindingOperationConsistent"></a><a name=
"zed-BindingOperationCM" id="zed-BindingOperationCM"></a></div>
<div class="div3">
<h4><a name="Binding_Operation_XMLRep" id=
"Binding_Operation_XMLRep"></a>2.9.2 XML Representation of Binding
Operation Component</h4>
<div class="exampleInner">
<pre xml:space="preserve">
&lt;description&gt;
  &lt;binding&gt;
    &lt;<strong>operation</strong>
          ref="<em>xs:QName</em>" &gt;
      &lt;documentation /&gt;*
      [ &lt;input /&gt; | &lt;output /&gt; | &lt;infault /&gt; | &lt;outfault /&gt; ]*
    &lt;/<strong>operation</strong>&gt;
  &lt;/binding&gt;
&lt;/description&gt;
</pre></div>
<p>The XML representation for a <a href=
"#component-BindingOperation">Binding Operation</a> component is an
<em>element information item</em> with the following Infoset
properties:</p>
<ul>
<li>
<p>A [local name] of <code>operation</code></p>
</li>
<li>
<p>A [namespace name] of "http://www.w3.org/ns/wsdl"</p>
</li>
<li>
<p>One or more <em>attribute information item</em>s amongst its
[attributes] as follows:</p>
<ul>
<li>
<p>A REQUIRED <code>ref</code> <em>attribute information item</em>
as described below in <a href=
"#Binding_Operation_ref_attribute"><strong>2.9.2.1 ref attribute
information item with operation [owner element]</strong></a>.</p>
</li>
<li>
<p>Zero or more namespace qualified <em>attribute information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl".</p>
</li>
</ul>
</li>
<li>
<p>Zero or more <em>element information item</em>s amongst its
[children], in order, as follows:</p>
<ol class="enumar">
<li>
<p>Zero or more <code>documentation</code> <em>element information
item</em>s (see <a href="#eii-documentation"><strong>5.
Documentation</strong></a>).</p>
</li>
<li>
<p>Zero or more <em>element information item</em>s from among the
following, in any order:</p>
<ul>
<li>
<p>Zero or more <code>input</code> <em>element information
item</em>s (see <a href="#Binding_Message_Reference"><strong>2.10
Binding Message Reference</strong></a>)</p>
</li>
<li>
<p>Zero or more <code>output</code> <em>element information
item</em>s (see <a href="#Binding_Message_Reference"><strong>2.10
Binding Message Reference</strong></a>)</p>
</li>
<li>
<p>Zero or more <code>infault</code> <em>element information
item</em>s (see <a href="#Binding_Fault_Reference"><strong>2.11
Binding Fault Reference</strong></a>)</p>
</li>
<li>
<p>Zero or more <code>outfault</code> <em>element information
item</em>s (see <a href="#Binding_Fault_Reference"><strong>2.11
Binding Fault Reference</strong></a>)</p>
</li>
<li>
<p>Zero or more namespace-qualified <em>element information
item</em> whose [namespace name] is NOT " http://www.w3.org/ns/wsdl
". Such <em>element information item</em>s are considered to be
binding operation extension elements as described below (see
<a href="#Binding_Operation_extension_elements"><strong>2.9.2.2
Binding Operation extension elements</strong></a>).</p>
</li>
</ul>
</li>
</ol>
</li>
</ul>
<div class="div4">
<h5><a name="Binding_Operation_ref_attribute" id=
"Binding_Operation_ref_attribute"></a>2.9.2.1 <code>ref</code>
<em>attribute information item</em> with <code>operation</code>
[owner element]</h5>
<p>The <code>ref</code> <em>attribute information item</em> has the
following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>ref</code></p>
</li>
<li>
<p>A [namespace name] which has no value</p>
</li>
</ul>
<p>The type of the <code>ref</code> <em>attribute information
item</em> is <em>xs:QName</em>.</p>
</div>
<div class="div4">
<h5><a name="Binding_Operation_extension_elements" id=
"Binding_Operation_extension_elements"></a>2.9.2.2 Binding
Operation extension elements</h5>
<p>Binding Operation extension elements are used to provide
information specific to a particular operation in a binding. The
semantics of such <em>element information item</em>s are defined by
the specification for those <em>element information item</em>s.
Such specifications are expected to annotate the <a href=
"#component-BindingOperation">Binding Operation</a> component with
additional properties and specify the mapping from the XML
representation to those properties.</p>
</div>
</div>
<div class="div3">
<h4><a name="Binding_Operation_Mapping" id=
"Binding_Operation_Mapping"></a>2.9.3 Mapping Binding Operation's
XML Representation to Component Properties</h4>
<p>The mapping from the XML Representation of the
<code>operation</code> <em>element information item</em> (see
<a href="#Binding_Operation_XMLRep"><strong>2.9.2 XML
Representation of Binding Operation Component</strong></a>) to the
properties of the <a href="#component-BindingOperation">Binding
Operation</a> component is as described in <a href=
"#tab_Binding_Operation_Mapping">Table 2-9</a>.</p>
<a name="tab_Binding_Operation_Mapping" id=
"tab_Binding_Operation_Mapping"></a>
<table border="1">
<caption>Table 2-9. Mapping from XML Representation to Binding
Operation Component Properties</caption>
<col width="20%" span="1" />
<col width="80%" span="1" />
<tbody>
<tr>
<th rowspan="1" colspan="1">Property</th>
<th rowspan="1" colspan="1">Value</th>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-BindingOperation.interfaceoperation">interface
operation</a>}</td>
<td rowspan="1" colspan="1">The <a href=
"#component-InterfaceOperation">Interface Operation</a> component
corresponding to the actual value of the <code>ref</code>
<em>attribute information item</em>.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-BindingOperation.bindingmessagereferences">binding
message references</a>}</td>
<td rowspan="1" colspan="1">The set of <a href=
"#component-BindingMessageReference">Binding Message Reference</a>
components corresponding to the <code>input</code> and
<code>output</code> <em>element information item</em>s in
[children], if any.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-BindingOperation.bindingfaultreferences">binding fault
references</a>}</td>
<td rowspan="1" colspan="1">The set of <a href=
"#component-BindingFaultReference">Binding Fault Reference</a>
components corresponding to the <code>infault</code> and
<code>outfault</code> <em>element information item</em>s in
[children], if any.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-BindingOperation.parent">parent</a>}</td>
<td rowspan="1" colspan="1">The <a href=
"#component-Binding">Binding</a> component corresponding to the
<code>binding</code> <em>element information item</em> in
[parent].</td>
</tr>
</tbody>
</table>

<br /></div>
</div>
<div class="div2">
<h3><a name="Binding_Message_Reference" id=
"Binding_Message_Reference"></a>2.10 Binding Message Reference</h3>
<div class="div3">
<h4><a name="Binding_Message_Reference_details" id=
"Binding_Message_Reference_details"></a>2.10.1 The Binding Message
Reference Component</h4>
<p>A <a href="#component-BindingMessageReference">Binding Message
Reference</a> component describes a concrete binding of a
particular message participating in an operation to a particular
concrete message format.</p>
<p>The properties of the <a name=
"component-BindingMessageReference" id=
"component-BindingMessageReference">Binding Message Reference</a>
component are as follows:</p>
<ul>
<li>
<p>{<a name=
"property-BindingMessageReference.interfacemessagereference" id=
"property-BindingMessageReference.interfacemessagereference">interface
message reference</a>} REQUIRED. An <a href=
"#component-InterfaceMessageReference">Interface Message
Reference</a> component among those in the {<a href=
"#property-InterfaceOperation.interfacemessagereferences">interface
message references</a>} property of the <a href=
"#component-InterfaceOperation">Interface Operation</a> component
being bound by the containing <a href=
"#component-BindingOperation">Binding Operation</a> component.</p>
</li>
<li>
<p>{<a name="property-BindingMessageReference.parent" id=
"property-BindingMessageReference.parent">parent</a>} REQUIRED. The
<a href="#component-BindingOperation">Binding Operation</a>
component that contains this component in its {<a href=
"#property-BindingOperation.bindingmessagereferences">binding
message references</a>} property.</p>
</li>
</ul>
<a name="zed-BindingMessageReference" id=
"zed-BindingMessageReference"></a><a name=
"zed-BindingMessageReferenceRI" id=
"zed-BindingMessageReferenceRI"></a>
<p><span id="BindingMessageReference-1052" class=
"test-assertion-tr">For each <a href=
"#component-BindingMessageReference">Binding Message Reference</a>
component in the {<a href=
"#property-BindingOperation.bindingmessagereferences">binding
message references</a>} property of a <a href=
"#component-BindingOperation">Binding Operation</a> component, the
{<a href=
"#property-BindingMessageReference.interfacemessagereference">interface
message reference</a>} property MUST be unique.<sup><a href=
"#BindingMessageReference-1052-summary" title=
"Link to assertion BindingMessageReference-1052 summary">†</a></sup></span>
That is, the same message cannot be bound twice within the same
operation.</p>
<a name="zed-BindingMessageReferenceKey" id=
"zed-BindingMessageReferenceKey"></a><a name=
"zed-BindingMessageReferenceConsistent" id=
"zed-BindingMessageReferenceConsistent"></a><a name=
"zed-BindingMessageReferenceCM" id=
"zed-BindingMessageReferenceCM"></a></div>
<div class="div3">
<h4><a name="Binding_Message_Reference_XMLRep" id=
"Binding_Message_Reference_XMLRep"></a>2.10.2 XML Representation of
Binding Message Reference Component</h4>
<div class="exampleInner">
<pre xml:space="preserve">
&lt;description&gt;
  &lt;binding&gt;
    &lt;operation&gt;
      &lt;<strong>input</strong>
            messageLabel="<em>xs:NCName</em>"? &gt;
        &lt;documentation /&gt;*
      &lt;/<strong>input</strong>&gt;
      &lt;<strong>output</strong>
            messageLabel="<em>xs:NCName</em>"? &gt;
        &lt;documentation /&gt;*
      &lt;/<strong>output</strong>&gt;
    &lt;/operation&gt;
  &lt;/binding&gt;
&lt;/description&gt;
</pre></div>
<p>The XML representation for a <a href=
"#component-BindingMessageReference">Binding Message Reference</a>
component is an <em>element information item</em> with the
following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>input</code> or <code>output</code>.</p>
</li>
<li>
<p>A [namespace name] of "http://www.w3.org/ns/wsdl".</p>
</li>
<li>
<p>Zero or more <em>attribute information item</em>s amongst its
[attributes] as follows:</p>
<ul>
<li>
<p>An OPTIONAL <code>messageLabel</code> <em>attribute information
item</em> as described below in <a href=
"#Binding_Message_Reference_name_attribute"><strong>2.10.2.1
messageLabel attribute information item with input or output [owner
element]</strong></a>.</p>
</li>
<li>
<p>Zero or more namespace qualified <em>attribute information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl".</p>
</li>
</ul>
</li>
<li>
<p>Zero or more <em>element information item</em> amongst its
[children], in order, as follows:</p>
<ol class="enumar">
<li>
<p>Zero or more <code>documentation</code> <em>element information
item</em>s (see <a href="#eii-documentation"><strong>5.
Documentation</strong></a>).</p>
</li>
<li>
<p>Zero or more namespace-qualified <em>element information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl". Such <em>element information
item</em>s are considered to be binding message reference extension
elements as described below (see <a href=
"#Binding_Message_Reference_extension_elements"><strong>2.10.2.2
Binding Message Reference extension elements</strong></a>).</p>
</li>
</ol>
</li>
</ul>
<div class="div4">
<h5><a name="Binding_Message_Reference_name_attribute" id=
"Binding_Message_Reference_name_attribute"></a>2.10.2.1
<code>messageLabel</code> <em>attribute information item</em> with
<code>input</code> or <code>output</code> [owner element]</h5>
<p>The <code>messageLabel</code> <em>attribute information
item</em> has the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>messageLabel</code>.</p>
</li>
<li>
<p>A [namespace name] which has no value.</p>
</li>
</ul>
<p>The type of the <code>messageLabel</code> <em>attribute
information item</em> is <em>xs:NCName</em>.</p>
</div>
<div class="div4">
<h5><a name="Binding_Message_Reference_extension_elements" id=
"Binding_Message_Reference_extension_elements"></a>2.10.2.2 Binding
Message Reference extension elements</h5>
<p>Binding Message Reference extension elements are used to provide
information specific to a particular message in an operation. The
semantics of such <em>element information item</em>s are defined by
the specification for those <em>element information item</em>s.
Such specifications are expected to annotate the <a href=
"#component-BindingMessageReference">Binding Message Reference</a>
component with additional properties and specify the mapping from
the XML representation to those properties.</p>
</div>
</div>
<div class="div3">
<h4><a name="Binding_Message_Reference_Mapping" id=
"Binding_Message_Reference_Mapping"></a>2.10.3 Mapping Binding
Message Reference's XML Representation to Component Properties</h4>
<p>The mapping from the XML Representation of the
<code>binding</code> <em>element information item</em> (see
<a href="#Binding_Message_Reference_XMLRep"><strong>2.10.2 XML
Representation of Binding Message Reference Component</strong></a>)
to the properties of the <a href=
"#component-BindingMessageReference">Binding Message Reference</a>
component is as described in <a href=
"#tab_Binding_Message_Reference_Mapping">Table 2-10</a> and uses
the definitions below.</p>
<p>Define the <em>message exchange pattern</em> of the <em>element
information item</em> to be the {<a href=
"#property-InterfaceOperation.messageexchangepattern">message
exchange pattern</a>} of the <a href=
"#component-InterfaceOperation">Interface Operation</a> component
being bound.</p>
<p>Define the <em>message direction</em> of the <em>element
information item</em> to be <em>in</em> if its local name is
<code>input</code> and <em>out</em> if its local name is
<code>output</code>.</p>
<p>Note that the <code>messageLabel</code> <em>attribute
information item</em> of a binding message reference <em>element
information item</em> must be present if the message exchange
pattern has more than one placeholder message with {<a href=
"#property-InterfaceMessageReference.direction">direction</a>}
equal to the message direction.</p>
<p><span id="MessageLabel-1053" class="test-assertion-tr">If the
<code>messageLabel</code> <em>attribute information item</em> of a
binding message reference <em>element information item</em> is
present then its actual value MUST match the {<a href=
"#property-InterfaceMessageReference.messagelabel">message
label</a>} of some placeholder message with {<a href=
"#property-InterfaceMessageReference.direction">direction</a>}
equal to the message direction. <sup><a href=
"#MessageLabel-1053-summary" title=
"Link to assertion MessageLabel-1053 summary">†</a></sup></span></p>
<p><span id="MessageLabel-1054" class="test-assertion-tr">If the
<code>messageLabel</code> <em>attribute information item</em> of a
binding message reference <em>element information item</em> is
absent then there MUST be a unique placeholder message with
{<a href=
"#property-InterfaceMessageReference.direction">direction</a>}
equal to the message direction. <sup><a href=
"#MessageLabel-1054-summary" title=
"Link to assertion MessageLabel-1054 summary">†</a></sup></span></p>
<p>Define the <em>effective message label</em> of a binding message
reference <em>element information item</em> to be either the actual
value of the <code>messageLabel</code> <em>attribute information
item</em> if it is present, or the {<a href=
"#property-InterfaceMessageReference.messagelabel">message
label</a>} of the unique placeholder message with {<a href=
"#property-InterfaceMessageReference.direction">direction</a>}
equal to the message direction if the <em>attribute information
item</em> is absent.</p>
<a name="tab_Binding_Message_Reference_Mapping" id=
"tab_Binding_Message_Reference_Mapping"></a>
<table border="1">
<caption>Table 2-10. Mapping from XML Representation to Binding
Message Reference Component Properties</caption>
<col width="20%" span="1" />
<col width="80%" span="1" />
<tbody>
<tr>
<th rowspan="1" colspan="1">Property</th>
<th rowspan="1" colspan="1">Value</th>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-BindingMessageReference.interfacemessagereference">interface
message reference</a>}</td>
<td rowspan="1" colspan="1">The <a href=
"#component-InterfaceMessageReference">Interface Message
Reference</a> component in the {<a href=
"#property-InterfaceOperation.interfacemessagereferences">interface
message references</a>} of the <a href=
"#component-InterfaceOperation">Interface Operation</a> component
being bound with {<a href=
"#property-InterfaceMessageReference.messagelabel">message
label</a>} equal to the effective message label.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{parent}</td>
<td rowspan="1" colspan="1">The <a href=
"#component-BindingOperation">Binding Operation</a> component
corresponding to the <code>operation</code> <em>element information
item</em> in [parent].</td>
</tr>
</tbody>
</table>

<br /></div>
</div>
<div class="div2">
<h3><a name="Binding_Fault_Reference" id=
"Binding_Fault_Reference"></a>2.11 Binding Fault Reference</h3>
<div class="div3">
<h4><a name="Binding_Fault_Reference_details" id=
"Binding_Fault_Reference_details"></a>2.11.1 The Binding Fault
Reference Component</h4>
<p>A <a href="#component-BindingFaultReference">Binding Fault
Reference</a> component describes a concrete binding of a
particular fault participating in an operation to a particular
concrete message format.</p>
<p>The properties of the <a name="component-BindingFaultReference"
id="component-BindingFaultReference">Binding Fault Reference</a>
component are as follows:</p>
<ul>
<li>
<p>{<a name=
"property-BindingFaultReference.interfacefaultreference" id=
"property-BindingFaultReference.interfacefaultreference">interface
fault reference</a>} REQUIRED. An <a href=
"#component-InterfaceFaultReference">Interface Fault Reference</a>
component among those in the {<a href=
"#property-InterfaceOperation.interfacefaultreferences">interface
fault references</a>} property of the <a href=
"#component-InterfaceOperation">Interface Operation</a> component
being bound by the parent <a href=
"#component-BindingOperation">Binding Operation</a> component.</p>
</li>
<li>
<p>{<a name="property-BindingFaultReference.parent" id=
"property-BindingFaultReference.parent">parent</a>} REQUIRED. The
<a href="#component-BindingOperation">Binding Operation</a>
component that contains this component in its {<a href=
"#property-BindingOperation.bindingfaultreferences">binding fault
references</a>} property.</p>
</li>
</ul>
<a name="zed-BindingFaultReference" id=
"zed-BindingFaultReference"></a><a name=
"zed-BindingFaultReferenceRI" id="zed-BindingFaultReferenceRI"></a>
<p><span id="BindingFaultReference-1055" class=
"test-assertion-tr">For each <a href=
"#component-BindingFaultReference">Binding Fault Reference</a>
component in the {<a href=
"#property-BindingOperation.bindingfaultreferences">binding fault
references</a>} property of a <a href=
"#component-BindingOperation">Binding Operation</a> component, the
{<a href=
"#property-BindingFaultReference.interfacefaultreference">interface
fault reference</a>} property MUST be unique.<sup><a href=
"#BindingFaultReference-1055-summary" title=
"Link to assertion BindingFaultReference-1055 summary">†</a></sup></span>
That is, the same fault cannot be bound twice within the same
operation.</p>
<a name="zed-BindingFaultReferenceKey" id=
"zed-BindingFaultReferenceKey"></a><a name=
"zed-BindingFaultReferenceConsistent" id=
"zed-BindingFaultReferenceConsistent"></a><a name=
"zed-BindingFaultReferenceCM" id=
"zed-BindingFaultReferenceCM"></a></div>
<div class="div3">
<h4><a name="Binding_Fault_Reference_XMLRep" id=
"Binding_Fault_Reference_XMLRep"></a>2.11.2 XML Representation of
Binding Fault Reference Component</h4>
<div class="exampleInner">
<pre xml:space="preserve">
&lt;description&gt;
  &lt;binding&gt;
    &lt;operation&gt;
      &lt;<strong>infault</strong>
            ref="<em>xs:QName</em>"
            messageLabel="<em>xs:NCName</em>"?&gt;
        &lt;documentation /&gt;*
      &lt;/<strong>infault</strong>&gt;
      &lt;<strong>outfault</strong>
            ref="<em>xs:QName</em>"
            messageLabel="<em>xs:NCName</em>"?&gt;
        &lt;documentation /&gt;*
      &lt;/<strong>outfault</strong>&gt;
    &lt;/operation&gt;
  &lt;/binding&gt;
&lt;/description&gt;
</pre></div>
<p>The XML representation for a <a href=
"#component-BindingFaultReference">Binding Fault Reference</a>
component is an <em>element information item</em> with the
following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>infault</code> or
<code>outfault</code>.</p>
</li>
<li>
<p>A [namespace name] of "http://www.w3.org/ns/wsdl".</p>
</li>
<li>
<p>One or more <em>attribute information item</em>s amongst its
[attributes] as follows:</p>
<ul>
<li>
<p>A REQUIRED <code>ref</code> <em>attribute information item</em>
as described below in <a href=
"#Binding_Fault_Reference_ref_attribute"><strong>2.11.2.1 ref
attribute information item with infault or outfault [owner
element]</strong></a>.</p>
<p>An OPTIONAL <code>messageLabel</code> <em>attribute information
item</em> as described below in <a href=
"#Binding_Fault_Reference_messageLabel_attribute"><strong>2.11.2.2
messageLabel attribute information item with infault or outfault
[owner element]</strong></a>.</p>
</li>
<li>
<p>Zero or more namespace qualified <em>attribute information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl".</p>
</li>
</ul>
</li>
<li>
<p>Zero or more <em>element information item</em> amongst its
[children], in order, as follows:</p>
<ol class="enumar">
<li>
<p>Zero or more <code>documentation</code> <em>element information
item</em>s (see <a href="#eii-documentation"><strong>5.
Documentation</strong></a>).</p>
</li>
<li>
<p>Zero or more namespace-qualified <em>element information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl". Such <em>element information
item</em>s are considered to be binding fault reference extension
elements as described below (see <a href=
"#Binding_Fault_Reference_extension_elements"><strong>2.11.2.3
Binding Fault Reference extension elements</strong></a>).</p>
</li>
</ol>
</li>
</ul>
<div class="div4">
<h5><a name="Binding_Fault_Reference_ref_attribute" id=
"Binding_Fault_Reference_ref_attribute"></a>2.11.2.1
<code>ref</code> <em>attribute information item</em> with
<code>infault</code> or <code>outfault</code> [owner element]</h5>
<p>The <code>ref</code> <em>attribute information item</em> has the
following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>ref</code>.</p>
</li>
<li>
<p>A [namespace name] which has no value.</p>
</li>
</ul>
<p>The type of the <code>ref</code> <em>attribute information
item</em> is <em>xs:QName</em>.</p>
</div>
<div class="div4">
<h5><a name="Binding_Fault_Reference_messageLabel_attribute" id=
"Binding_Fault_Reference_messageLabel_attribute"></a>2.11.2.2
<code>messageLabel</code> <em>attribute information item</em> with
<code>infault</code> or <code>outfault</code> [owner element]</h5>
<p>The <code>messageLabel</code> <em>attribute information
item</em> has the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>messageLabel</code>.</p>
</li>
<li>
<p>A [namespace name] which has no value.</p>
</li>
</ul>
<p>The type of the <code>messageLabel</code> <em>attribute
information item</em> is <em>xs:NCName</em>.</p>
</div>
<div class="div4">
<h5><a name="Binding_Fault_Reference_extension_elements" id=
"Binding_Fault_Reference_extension_elements"></a>2.11.2.3 Binding
Fault Reference extension elements</h5>
<p>Binding Fault Reference extension elements are used to provide
information specific to a particular fault in an operation. The
semantics of such <em>element information item</em>s are defined by
the specification for those <em>element information item</em>s.
Such specifications are expected to annotate the <a href=
"#component-BindingFaultReference">Binding Fault Reference</a>
component with additional properties and specify the mapping from
the XML representation to those properties.</p>
</div>
</div>
<div class="div3">
<h4><a name="Binding_Fault_Reference_Mapping" id=
"Binding_Fault_Reference_Mapping"></a>2.11.3 Mapping Binding Fault
Reference's XML Representation to Component Properties</h4>
<p>The mapping from the XML Representation of the
<code>binding</code> <em>element information item</em> (see
<a href="#Binding_Fault_Reference_XMLRep"><strong>2.11.2 XML
Representation of Binding Fault Reference Component</strong></a>)
to the properties of the <a href=
"#component-BindingFaultReference">Binding Fault Reference</a>
component is as described in <a href=
"#tab_Binding_Fault_Reference_Mapping">Table 2-11</a> and uses the
definitions below.</p>
<p>Define the <em>message exchange pattern</em> of the <em>element
information item</em> to be the {<a href=
"#property-InterfaceOperation.messageexchangepattern">message
exchange pattern</a>} of the <a href=
"#component-InterfaceOperation">Interface Operation</a> component
being bound.</p>
<p>Define the <em>fault direction</em> of the <em>element
information item</em> to be <em>in</em> if its local name is
<code>infault</code> and <em>out</em> if its local name is
<code>outfault</code>.</p>
<p>Define the <em>message direction</em> of the <em>element
information item</em> to be the {<a href=
"#property-InterfaceMessageReference.direction">direction</a>} of
the placeholder message associated with the fault as specified by
the fault propagation ruleset of the message exchange pattern.</p>
<p><span id="MessageLabel-1056" class="test-assertion-tr">The
<code>messageLabel</code> <em>attribute information item</em> of a
binding fault reference <em>element information item</em> MUST be
present if the message exchange pattern has more than one
placeholder message with {<a href=
"#property-InterfaceMessageReference.direction">direction</a>}
equal to the message direction. <sup><a href=
"#MessageLabel-1056-summary" title=
"Link to assertion MessageLabel-1056 summary">†</a></sup></span></p>
<p><span id="MessageLabel-1057" class="test-assertion-tr">If the
<code>messageLabel</code> <em>attribute information item</em> of a
binding fault reference <em>element information item</em> is
present then its actual value MUST match the {<a href=
"#property-InterfaceMessageReference.messagelabel">message
label</a>} of some placeholder message with {<a href=
"#property-InterfaceMessageReference.direction">direction</a>}
equal to the message direction. <sup><a href=
"#MessageLabel-1057-summary" title=
"Link to assertion MessageLabel-1057 summary">†</a></sup></span></p>
<p><span id="MessageLabel-1058" class="test-assertion-tr">If the
<code>messageLabel</code> <em>attribute information item</em> of a
binding fault reference <em>element information item</em> is absent
then there MUST be a unique placeholder message with {<a href=
"#property-InterfaceMessageReference.direction">direction</a>}
equal to the message direction. <sup><a href=
"#MessageLabel-1058-summary" title=
"Link to assertion MessageLabel-1058 summary">†</a></sup></span></p>
<p>Define the <em>effective message label</em> of a binding fault
reference <em>element information item</em> to be either the actual
value of the <code>messageLabel</code> <em>attribute information
item</em> if it is present, or the {<a href=
"#property-InterfaceMessageReference.messagelabel">message
label</a>} of the unique placeholder message with {<a href=
"#property-InterfaceMessageReference.direction">direction</a>}
equal to the message direction if the <em>attribute information
item</em> is absent.</p>
<p><span id="BindingFaultReference-1059" class=
"test-assertion-tr">There MUST be an <a href=
"#component-InterfaceFaultReference">Interface Fault Reference</a>
component in the {<a href=
"#property-InterfaceOperation.interfacefaultreferences">interface
fault references</a>} of the <a href=
"#component-InterfaceOperation">Interface Operation</a> being bound
with {<a href=
"#property-InterfaceFaultReference.messagelabel">message label</a>}
equal to the effective message label and with {<a href=
"#property-InterfaceFaultReference.interfacefault">interface
fault</a>} equal to an <a href=
"#component-InterfaceFault">Interface Fault</a> component with
{<a href="#property-InterfaceFault.name">name</a>} equal to the
actual value of the <code>ref</code> <em>attribute information
item</em>.<sup><a href="#BindingFaultReference-1059-summary" title=
"Link to assertion BindingFaultReference-1059 summary">†</a></sup></span></p>
<a name="tab_Binding_Fault_Reference_Mapping" id=
"tab_Binding_Fault_Reference_Mapping"></a>
<table border="1">
<caption>Table 2-11. Mapping from XML Representation to Binding
Fault Reference Component Properties</caption>
<col width="20%" span="1" />
<col width="80%" span="1" />
<tbody>
<tr>
<th rowspan="1" colspan="1">Property</th>
<th rowspan="1" colspan="1">Value</th>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-BindingFaultReference.interfacefaultreference">interface
fault reference</a>}</td>
<td rowspan="1" colspan="1">The <a href=
"#component-InterfaceFaultReference">Interface Fault Reference</a>
component in the {<a href=
"#property-InterfaceOperation.interfacefaultreferences">interface
fault references</a>} of the <a href=
"#component-InterfaceOperation">Interface Operation</a> being bound
with {<a href=
"#property-InterfaceFaultReference.messagelabel">message label</a>}
equal to the effective message label, and with {<a href=
"#property-InterfaceFaultReference.interfacefault">interface
fault</a>} equal to an <a href=
"#component-InterfaceFault">Interface Fault</a> component with
{<a href="#property-InterfaceFault.name">name</a>} equal to the
actual value of the <code>ref</code> <em>attribute information
item</em>.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{parent}</td>
<td rowspan="1" colspan="1">The <a href=
"#component-BindingOperation">Binding Operation</a> component
corresponding to the <code>operation</code> <em>element information
item</em> in [parent].</td>
</tr>
</tbody>
</table>

<br /></div>
</div>
<div class="div2">
<h3><a name="Service" id="Service"></a>2.12 Service</h3>
<div class="div3">
<h4><a name="Service_details" id="Service_details"></a>2.12.1 The
Service Component</h4>
<p>A <a href="#component-Service">Service</a> component describes a
set of endpoints (see <a href="#Endpoint"><strong>2.13
Endpoint</strong></a>) at which a particular deployed
implementation of the service is provided. The endpoints thus are
in effect alternate places at which the service is provided.</p>
<p>Services are named constructs and can be referred to by QName
(see <a href="#qnameres"><strong>2.17 QName
resolution</strong></a>).</p>
<p>The properties of the <a name="component-Service" id=
"component-Service">Service</a> component are as follows:</p>
<ul>
<li>
<p>{<a name="property-Service.name" id=
"property-Service.name">name</a>} REQUIRED. An
<em>xs:QName</em>.</p>
</li>
<li>
<p>{<a name="property-Service.interface" id=
"property-Service.interface">interface</a>} REQUIRED. An <a href=
"#component-Interface">Interface</a> component.</p>
</li>
<li>
<p>{<a name="property-Service.endpoints" id=
"property-Service.endpoints">endpoints</a>} REQUIRED. A non-empty
set of <a href="#component-Endpoint">Endpoint</a> components.</p>
</li>
</ul>
<a name="zed-Service" id="zed-Service"></a><a name="zed-ServiceRI"
id="zed-ServiceRI"></a>
<p><span id="Service-1060" class="test-assertion-tr">For each
<a href="#component-Service">Service</a> component in the {<a href=
"#property-Description.services">services</a>} property of a
<a href="#component-Description">Description</a> component, the
{<a href="#property-Service.name">name</a>} property MUST be
unique.<sup><a href="#Service-1060-summary" title=
"Link to assertion Service-1060 summary">†</a></sup></span></p>
<a name="zed-ServiceKey" id="zed-ServiceKey"></a><a name=
"zed-ServiceParent" id="zed-ServiceParent"></a><a name=
"zed-ServiceCM" id="zed-ServiceCM"></a></div>
<div class="div3">
<h4><a name="Service_XMLRep" id="Service_XMLRep"></a>2.12.2 XML
Representation of Service Component</h4>
<div class="exampleInner">
<pre xml:space="preserve">
&lt;description&gt;
  &lt;<strong>service</strong>
        name="<em>xs:NCName</em>" 
        interface="<em>xs:QName</em>" &gt;
    &lt;documentation /&gt;*
    &lt;endpoint /&gt;+
  &lt;/<strong>service</strong>&gt;
&lt;/description&gt;
</pre></div>
<p>The XML representation for a <a href=
"#component-Service">Service</a> component is an <em>element
information item</em> with the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>service</code></p>
</li>
<li>
<p>A [namespace name] of "http://www.w3.org/ns/wsdl"</p>
</li>
<li>
<p>Two or more <em>attribute information item</em>s amongst its
[attributes] as follows:</p>
<ul>
<li>
<p>A REQUIRED <code>name</code> <em>attribute information item</em>
as described below in <a href=
"#Service_name_attribute"><strong>2.12.2.1 name attribute
information item with service [owner element]</strong></a>.</p>
</li>
<li>
<p>A REQUIRED <code>interface</code> <em>attribute information
item</em> as described below in <a href=
"#Service_interface_attribute"><strong>2.12.2.2 interface attribute
information item with service [owner element]</strong></a>.</p>
</li>
<li>
<p>Zero or more namespace qualified <em>attribute information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl".</p>
</li>
</ul>
</li>
<li>
<p>One or more <em>element information item</em> amongst its
[children], in order, as follows:</p>
<ol class="enumar">
<li>
<p>Zero or more <code>documentation</code> <em>element information
item</em>s (see <a href="#eii-documentation"><strong>5.
Documentation</strong></a>).</p>
</li>
<li>
<p>One or more <em>element information item</em>s from among the
following, in any order:</p>
<ul>
<li>
<p>One or more <code>endpoint</code> <em>element information
item</em>s (see <a href="#Endpoint_XMLRep"><strong>2.13.2 XML
Representation of Endpoint Component</strong></a></p>
</li>
<li>
<p>Zero or more namespace-qualified <em>element information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl".</p>
</li>
</ul>
</li>
</ol>
</li>
</ul>
<div class="div4">
<h5><a name="Service_name_attribute" id=
"Service_name_attribute"></a>2.12.2.1 <code>name</code>
<em>attribute information item</em> with <code>service</code>
[owner element]</h5>
<p>The <code>name</code> <em>attribute information item</em>
together with the <code>targetNamespace</code> <em>attribute
information item</em> of the <code>description</code> <em>element
information item</em> forms the QName of the service.</p>
<p>The <code>name</code> <em>attribute information item</em> has
the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>name</code></p>
</li>
<li>
<p>A [namespace name] which has no value</p>
</li>
</ul>
<p>The type of the <code>name</code> <em>attribute information
item</em> is <em>xs:NCName</em>.</p>
</div>
<div class="div4">
<h5><a name="Service_interface_attribute" id=
"Service_interface_attribute"></a>2.12.2.2 <code>interface</code>
<em>attribute information item</em> with <code>service</code>
[owner element]</h5>
<p>The <code>interface</code> <em>attribute information item</em>
identifies the interface that the service is an instance of.</p>
<p>The <code>interface</code> <em>attribute information item</em>
has the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>interface</code></p>
</li>
<li>
<p>A [namespace name] which has no value</p>
</li>
</ul>
<p>The type of the <code>interface</code> <em>attribute information
item</em> is <em>xs:QName.</em>.</p>
</div>
</div>
<div class="div3">
<h4><a name="Service_Mapping" id="Service_Mapping"></a>2.12.3
Mapping Service's XML Representation to Component Properties</h4>
<p>The mapping from the XML Representation of the
<code>service</code> <em>element information item</em> (see
<a href="#Service_XMLRep"><strong>2.12.2 XML Representation of
Service Component</strong></a>) to the properties of the <a href=
"#component-Service">Service</a> component is as described in
<a href="#tab_Service_Mapping">Table 2-12</a>.</p>
<a name="tab_Service_Mapping" id="tab_Service_Mapping"></a>
<table border="1">
<caption>Table 2-12. Mapping from XML Representation to Service
Component Properties</caption>
<col width="20%" span="1" />
<col width="80%" span="1" />
<tbody>
<tr>
<th rowspan="1" colspan="1">Property</th>
<th rowspan="1" colspan="1">Value</th>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-Service.name">name</a>}</td>
<td rowspan="1" colspan="1">The QName whose local name is the
actual value of the <code>name</code> <em>attribute information
item</em>, and whose namespace name is the actual value of the
<code>targetNamespace</code> <em>attribute information item</em> of
the [parent] <code>description</code> <em>element information
item</em>.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-Service.interface">interface</a>}</td>
<td rowspan="1" colspan="1"><span>The <a href=
"#component-Interface">Interface</a> component resolved to by the
actual value of the <code>interface</code> <em>attribute
information item</em> (see <a href="#qnameres"><strong>2.17 QName
resolution</strong></a>).</span></td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-Service.endpoints">endpoints</a>}</td>
<td rowspan="1" colspan="1">The <a href=
"#component-Endpoint">Endpoint</a> components corresponding to the
<code>endpoint</code> <em>element information item</em>s in
[children].</td>
</tr>
</tbody>
</table>

<br /></div>
</div>
<div class="div2">
<h3><a name="Endpoint" id="Endpoint"></a>2.13 Endpoint</h3>
<div class="div3">
<h4><a name="Endpoint_details" id="Endpoint_details"></a>2.13.1 The
Endpoint Component</h4>
<p>An <a href="#component-Endpoint">Endpoint</a> component defines
the particulars of a specific endpoint at which a given service is
available.</p>
<p><a href="#component-Endpoint">Endpoint</a> components are local
to a given <a href="#component-Service">Service</a> component (see
<a href="#frag-ids"><strong>A.2 Fragment
Identifiers</strong></a>).</p>
<p>The <a href="#component-Binding">Binding</a> component specified
by the {<a href="#property-Endpoint.binding">binding</a>} property
of an <a href="#component-Endpoint">Endpoint</a> component is said
to be <em>applied</em> to the <a href=
"#component-Interface">Interface</a> component which is the value
of the {<a href="#property-Service.interface">interface</a>}
property of the parent <a href="#component-Service">Service</a>
component of the <a href="#component-Endpoint">Endpoint</a>.
According to the constraints given below, if this <a href=
"#component-Binding">Binding</a> component has an {<a href=
"#property-Binding.interface">interface</a>} property, its value
must be the <a href="#component-Interface">Interface</a> component
the <a href="#component-Binding">Binding</a> component is applied
to.</p>
<p>The {<a href="#property-Endpoint.address">address</a>} property
is optional to allow for means other than IRIs to be used, e.g. a
WS-Addressing Endpoint Reference [<cite><a href="#WSA-Core">WSA 1.0
Core</a></cite>]. It is also possible that, in certain scenarios,
an address will not be required, in which case this property may be
absent.</p>
<p>The properties of the <a name="component-Endpoint" id=
"component-Endpoint">Endpoint</a> component are as follows:</p>
<ul>
<li>
<p>{<a name="property-Endpoint.name" id=
"property-Endpoint.name">name</a>} REQUIRED. An
<em>xs:NCName</em>.</p>
</li>
<li>
<p>{<a name="property-Endpoint.binding" id=
"property-Endpoint.binding">binding</a>} REQUIRED. A <a href=
"#component-Binding">Binding</a> component.</p>
</li>
<li>
<p>{<a name="property-Endpoint.address" id=
"property-Endpoint.address">address</a>} OPTIONAL. An
<em>xs:anyURI</em>. <span id="Endpoint-1061" class=
"test-assertion-tr">This <em>xs:anyURI</em> MUST be an absolute IRI
as defined by [<cite><a href="#RFC3987">IETF RFC
3987</a></cite>].<sup><a href="#Endpoint-1061-summary" title=
"Link to assertion Endpoint-1061 summary">†</a></sup></span> If
present, the value of this attribute represents the network address
at which the service indicated by the parent <a href=
"#component-Service">Service</a> component's {<a href=
"#property-Service.interface">interface</a>} property is offered
via the binding referred to by the {<a href=
"#property-Endpoint.binding">binding</a>} property.
<strong>Note</strong> that the presence in this property of the
characters "?" and "#" can conflict with those potentially added by
the query string serialization mechanism, as defined in <a href=
"http://www.w3.org/TR/2007/REC-wsdl20-adjuncts-20070626/#_http_x-www-form-urlencoded">
Serialization as "application/x-www-form-urlencoded"</a>
([<cite><a href="#WSDL-PART2">WSDL 2.0 Adjuncts</a></cite>],
section 6.8.2).</p>
</li>
<li>
<p>{<a name="property-Endpoint.parent" id=
"property-Endpoint.parent">parent</a>} REQUIRED. The <a href=
"#component-Service">Service</a> component that contains this
component in its {<a href=
"#property-Service.endpoints">endpoints</a>} property.</p>
</li>
</ul>
<a name="zed-Endpoint" id="zed-Endpoint"></a><a name=
"zed-EndpointRI" id="zed-EndpointRI"></a>
<p>For each <a href="#component-Endpoint">Endpoint</a> component in
the {<a href="#property-Service.endpoints">endpoints</a>} property
of a <a href="#component-Service">Service</a> component, the
{<a href="#property-Endpoint.name">name</a>} property MUST be
unique. Note that this constraint is enforced by the normative WSDL
2.0 XML schema.</p>
<a name="zed-EndpointKey" id="zed-EndpointKey"></a>
<p><span id="Endpoint-1062" class="test-assertion-tr">For each
<a href="#component-Endpoint">Endpoint</a> component in the
{<a href="#property-Service.endpoints">endpoints</a>} property of a
<a href="#component-Service">Service</a> component, the {<a href=
"#property-Endpoint.binding">binding</a>} property MUST either be a
<a href="#component-Binding">Binding</a> component with an
unspecified {<a href="#property-Binding.interface">interface</a>}
property or a <a href="#component-Binding">Binding</a> component
with an {<a href="#property-Binding.interface">interface</a>}
property equal to the {<a href=
"#property-Service.interface">interface</a>} property of the
<a href="#component-Service">Service</a> component.<sup><a href=
"#Endpoint-1062-summary" title=
"Link to assertion Endpoint-1062 summary">†</a></sup></span></p>
<a name="zed-EndpointConsistent" id=
"zed-EndpointConsistent"></a><a name="zed-EndpointCM" id=
"zed-EndpointCM"></a></div>
<div class="div3">
<h4><a name="Endpoint_XMLRep" id="Endpoint_XMLRep"></a>2.13.2 XML
Representation of Endpoint Component</h4>
<div class="exampleInner">
<pre xml:space="preserve">
&lt;description&gt;
  &lt;service&gt;
    &lt;<strong>endpoint</strong>
          name="<em>xs:NCName</em>" 
          binding="<em>xs:QName</em>"
          address="<em>xs:anyURI</em>"? &gt;
      &lt;documentation /&gt;*
    &lt;/<strong>endpoint</strong>&gt;+
  &lt;/service&gt;
&lt;/description&gt;
</pre></div>
<p>The XML representation for a <a href=
"#component-Endpoint">Endpoint</a> component is an <em>element
information item</em> with the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>endpoint</code>.</p>
</li>
<li>
<p>A [namespace name] of "http://www.w3.org/ns/wsdl".</p>
</li>
<li>
<p>Two or more <em>attribute information item</em>s amongst its
[attributes] as follows:</p>
<ul>
<li>
<p>A REQUIRED <code>name</code> <em>attribute information item</em>
as described below in <a href=
"#Endpoint_name_attribute"><strong>2.13.2.1 name attribute
information item with endpoint [owner element]</strong></a>.</p>
</li>
<li>
<p>A REQUIRED <code>binding</code> <em>attribute information
item</em> as described below in <a href=
"#Endpoint_binding_attribute"><strong>2.13.2.2 binding attribute
information item with endpoint [owner element]</strong></a>.</p>
</li>
<li>
<p>An OPTIONAL <code>address</code> <em>attribute information
item</em> as described below in <a href=
"#Endpoint_address_attribute"><strong>2.13.2.3 address attribute
information item with endpoint [owner element]</strong></a>.</p>
</li>
<li>
<p>Zero or more namespace qualified <em>attribute information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl".</p>
</li>
</ul>
</li>
<li>
<p>Zero or more <em>element information item</em> amongst its
[children], in order, as follows:</p>
<ol class="enumar">
<li>
<p>Zero or more <code>documentation</code> <em>element information
item</em>s (see <a href="#eii-documentation"><strong>5.
Documentation</strong></a>).</p>
</li>
<li>
<p>Zero or more namespace-qualified <em>element information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl". Such <em>element information
item</em>s are considered to be endpoint extension elements as
described below (see <a href=
"#Endpoint_extension_elements"><strong>2.13.2.4 Endpoint extension
elements</strong></a>).</p>
</li>
</ol>
</li>
</ul>
<div class="div4">
<h5><a name="Endpoint_name_attribute" id=
"Endpoint_name_attribute"></a>2.13.2.1 <code>name</code>
<em>attribute information item</em> with <code>endpoint</code>
[owner element]</h5>
<p>The <code>name</code> <em>attribute information item</em>
together with the <code>targetNamespace</code> <em>attribute
information item</em> of the <code>description</code> <em>element
information item</em> forms the QName of the endpoint.</p>
<p>The <code>name</code> <em>attribute information item</em> has
the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>name</code>.</p>
</li>
<li>
<p>A [namespace name] which has no value.</p>
</li>
</ul>
<p>The type of the <code>name</code> <em>attribute information
item</em> is <em>xs:NCName</em>.</p>
</div>
<div class="div4">
<h5><a name="Endpoint_binding_attribute" id=
"Endpoint_binding_attribute"></a>2.13.2.2 <code>binding</code>
<em>attribute information item</em> with <code>endpoint</code>
[owner element]</h5>
<p>The <code>binding</code> <em>attribute information item</em>
refers, by QName, to a <a href="#component-Binding">Binding</a>
component</p>
<p>The <code>binding</code> <em>attribute information item</em> has
the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>binding</code></p>
</li>
<li>
<p>A [namespace name] which has no value</p>
</li>
</ul>
<p>The type of the <code>binding</code> <em>attribute information
item</em> is <em>xs:QName</em>.</p>
</div>
<div class="div4">
<h5><a name="Endpoint_address_attribute" id=
"Endpoint_address_attribute"></a>2.13.2.3 <code>address</code>
<em>attribute information item</em> with <code>endpoint</code>
[owner element]</h5>
<p>The <code>address</code> <em>attribute information item</em>
specifies the address of the endpoint.</p>
<p>The <code>address</code> <em>attribute information item</em> has
the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>address</code></p>
</li>
<li>
<p>A [namespace name] which has no value</p>
</li>
</ul>
<p>The type of the <code>address</code> <em>attribute information
item</em> is <em>xs:anyURI</em>.</p>
</div>
<div class="div4">
<h5><a name="Endpoint_extension_elements" id=
"Endpoint_extension_elements"></a>2.13.2.4 Endpoint extension
elements</h5>
<p>Endpoint extension elements are used to provide information
specific to a particular endpoint in a server. The semantics of
such <em>element information item</em>s are defined by the
specification for those <em>element information item</em>s. Such
specifications are expected to annotate the <a href=
"#component-Endpoint">Endpoint</a> component with additional
properties and specify the mapping from the XML representation to
those properties.</p>
</div>
</div>
<div class="div3">
<h4><a name="Endpoint_Mapping" id="Endpoint_Mapping"></a>2.13.3
Mapping Endpoint's XML Representation to Component Properties</h4>
<p>The mapping from the XML Representation of the
<code>endpoint</code> <em>element information item</em> (see
<a href="#Endpoint_XMLRep"><strong>2.13.2 XML Representation of
Endpoint Component</strong></a>) to the properties of the <a href=
"#component-Endpoint">Endpoint</a> component is as described in
<a href="#tab_Endpoint_Mapping">Table 2-13</a>.</p>
<a name="tab_Endpoint_Mapping" id="tab_Endpoint_Mapping"></a>
<table border="1">
<caption>Table 2-13. Mapping from XML Representation to Endpoint
Component Properties</caption>
<col width="20%" span="1" />
<col width="80%" span="1" />
<tbody>
<tr>
<th rowspan="1" colspan="1">Property</th>
<th rowspan="1" colspan="1">Value</th>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-Endpoint.name">name</a>}</td>
<td rowspan="1" colspan="1">The actual value of the
<code>name</code> <em>attribute information item</em>.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-Endpoint.binding">binding</a>}</td>
<td rowspan="1" colspan="1">The <a href=
"#component-Binding">Binding</a> component resolved to by the
actual value of the <code>binding</code> <em>attribute information
item</em> (see <a href="#qnameres"><strong>2.17 QName
resolution</strong></a> ).</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-Endpoint.address">address</a>}</td>
<td rowspan="1" colspan="1">The actual value of the
<code>address</code> <em>attribute information item</em> if
present; otherwise empty.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">{<a href=
"#property-Endpoint.parent">parent</a>}</td>
<td rowspan="1" colspan="1">The <a href=
"#component-Service">Service</a> component corresponding to the
<code>service</code> <em>element information item</em> in
[parent].</td>
</tr>
</tbody>
</table>

<br /></div>
</div>
<div class="div2">
<h3><a name="simpletypes" id="simpletypes"></a>2.14 XML Schema 1.0
Simple Types Used in the Component Model</h3>
<p>The XML Schema 1.0 simple types [<cite><a href=
"#XMLSchemaP2">XML Schema: Datatypes</a></cite>] used in this
specification are:</p>
<ul>
<li>
<p><em>xs:token</em></p>
</li>
<li>
<p><em>xs:NCName</em></p>
</li>
<li>
<p><em>xs:anyURI</em></p>
</li>
<li>
<p><em>xs:QName</em></p>
</li>
<li>
<p><em>xs:boolean</em></p>
</li>
</ul>
<a name="zed-NCName" id="zed-NCName"></a><a name="zed-URI" id=
"zed-URI"></a><a name="zed-AbsoluteURI" id=
"zed-AbsoluteURI"></a><a name="zed-QName" id=
"zed-QName"></a><a name="zed-Boolean" id="zed-Boolean"></a></div>
<div class="div2">
<h3><a name="compequiv" id="compequiv"></a>2.15 Equivalence of
Components</h3>
<p>Two component instances of the same type are considered
equivalent if, for each property value of the first component,
there is a corresponding property with an equivalent value on the
second component, and vice versa.</p>
<ul>
<li>
<p>For values of a simple type (see <a href=
"#simpletypes"><strong>2.14 XML Schema 1.0 Simple Types Used in the
Component Model</strong></a>) this means that they contain the same
values. For instance, two string values are equivalent if they
contain the same sequence of Unicode characters, as described in
[<cite><a href="#CHARMOD">Character Model for the WWW</a></cite>],
or two boolean values are equivalent if they contain the same
canonical value (<code>true</code> or <code>false</code>).</p>
</li>
<li>
<p>Values which are references to other components are considered
equivalent when they refer to equivalent components (as determined
above).</p>
</li>
<li>
<p>List-based values are considered equivalent if they have the
same length and their elements at corresponding positions are
equivalent.</p>
</li>
<li>
<p>Finally, set-based values are considered equivalent if, for each
value in the first, there is an equivalent value in the second, and
vice versa.</p>
</li>
</ul>
<p><span id="Equivalence-1063" class="test-assertion-tr">Extension
properties which are not string values, sets of strings or
references MUST describe their values' equivalence
rules.<sup><a href="#Equivalence-1063-summary" title=
"Link to assertion Equivalence-1063 summary">†</a></sup></span></p>
<p>Because different top-level components (e.g., <a href=
"#component-Interface">Interface</a>, <a href=
"#component-Binding">Binding</a>, and <a href=
"#component-Service">Service</a>) are required to have different
names, it is possible to determine whether two top-level components
of a given type are equivalent by simply examining their {name}
property.</p>
<p>The <a href="#component-Binding">Binding</a> component specified
by the {<a href="#property-Endpoint.binding">binding</a>} property
of an <a href="#component-Endpoint">Endpoint</a> is said to be
applied to the <a href="#component-Interface">Interface</a>
component which is the value of the {<a href=
"#property-Service.interface">interface</a>} property of the
{<a href="#property-Endpoint.parent">parent</a>} <a href=
"#component-Service">Service</a> component for the <a href=
"#component-Endpoint">Endpoint</a>. Note that, if this <a href=
"#component-Binding">Binding</a> component has an {<a href=
"#property-Binding.interface">interface</a>} property, then its
value MUST be the <a href="#component-Interface">Interface</a>
component that the <a href="#component-Binding">Binding</a>
component is applied to.</p>
</div>
<div class="div2">
<h3><a name="symbolspaces" id="symbolspaces"></a>2.16 Symbol
Spaces</h3>
<p>This specification defines three symbol spaces, one for each
top-level component type (<a href=
"#component-Interface">Interface</a>, <a href=
"#component-Binding">Binding</a> and <a href=
"#component-Service">Service</a>).</p>
<p>Within a symbol space, all qualified names (that is, the
{<a name="property-.name" id="property-.name">name</a>} property)
are unique. Between symbol spaces, the names need not be unique.
Thus it is perfectly coherent to have, for example, a binding and
an interface that have the same name.</p>
<p>When XML Schema is being used as one of the type systems for a
WSDL 2.0 description, then six other symbol spaces also exist, one
for each of: global element declarations, global attribute
declarations, named model groups, named attribute groups, type
definitions and key constraints, as defined by [<cite><a href=
"#XMLSchemaP1">XML Schema: Structures</a></cite>]. Other type
systems may define additional symbol spaces.</p>
</div>
<div class="div2">
<h3><a name="qnameres" id="qnameres"></a>2.17 QName resolution</h3>
<p>In its serialized form WSDL 2.0 makes significant use of
references between components. Such references are made using the
Qualified Name, or QName, of the component being referred to.
QNames are a tuple, consisting of two parts; a namespace name and a
local name. The namespace name for a component is represented by
the value of the <code>targetNamespace</code> <em>attribute
information item</em> of the [parent] <code>description</code>
<em>element information item</em>. The local name is represented by
the {<a href="#property-.name">name</a>} property of the
component.</p>
<p>QName references are resolved by looking in the appropriate
property of the <a href="#component-Description">Description</a>
component. For example, to resolve a QName of an interface (as
referred to by the <code>interface</code> <em>attribute information
item</em> on a binding), the {<a href=
"#property-Description.interfaces">interfaces</a>} property of the
<a href="#component-Description">Description</a> component would be
inspected.</p>
<p>If the appropriate property of the <a href=
"#component-Description">Description</a> component does not contain
a component with the required QName, then the reference is a broken
reference. <span id="QName-resolution-1064" class=
"test-assertion-tr">A <a href=
"#component-Description">Description</a> component MUST NOT have
such broken references.<sup><a href=
"#QName-resolution-1064-summary" title=
"Link to assertion QName-resolution-1064 summary">†</a></sup></span></p>
</div>
<div class="div2">
<h3><a name="uricompare" id="uricompare"></a>2.18 Comparing URIs
and IRIs</h3>
<p>This specification uses absolute URIs and IRIs to identify
several components and components characteristics (for example,
operation message exchange patterns and styles). <span id=
"Compare-URI-IRI-1065" class="test-assertion-tr">When such absolute
URIs and IRIs are being compared to determine equivalence (see
<a href="#compequiv"><strong>2.15 Equivalence of
Components</strong></a>), they MUST be compared
character-by-character as indicated in [<cite><a href=
"#RFC3987">IETF RFC 3987</a></cite>].<sup><a href=
"#Compare-URI-IRI-1065-summary" title=
"Link to assertion Compare-URI-IRI-1065 summary">†</a></sup></span></p>
</div>
</div>
<div class="div1">
<h2><a name="eii-types" id="eii-types"></a>3. Types</h2>
<div class="exampleInner">
<pre xml:space="preserve">
&lt;description&gt;
  &lt;<strong>types</strong>&gt;
    &lt;documentation /&gt;*
    [ &lt;xs:import namespace="<em>xs:anyURI</em>" schemaLocation="<em>xs:anyURI</em>"? /&gt; |
      &lt;xs:schema targetNamespace="<em>xs:anyURI</em>"? /&gt; |
      <em>other extension elements</em> ]*
  &lt;/<strong>types</strong>&gt;
&lt;/description&gt;
</pre></div>
<p>The content of messages and faults may be constrained using type
system components. These constraints are based upon a specific data
model, and expressed using a particular schema language.</p>
<p>Although a variety of data models can be accommodated (through
WSDL 2.0 extensions), this specification only defines a means of
expressing constraints based upon the XML Infoset [<cite><a href=
"#XMLInfoSet">XML Information Set</a></cite>]. Furthermore,
although a number of alternate schema languages can be used to
constrain the XML Infoset (as long as they support the semantics of
either inlining or importing schema), this specification only
defines the use of XML Schema [<cite><a href="#XMLSchemaP1">XML
Schema: Structures</a></cite>], [<cite><a href="#XMLSchemaP2">XML
Schema: Datatypes</a></cite>].</p>
<p>Specifically, the {<a href=
"#property-Description.elementdeclarations">element
declarations</a>} and {<a href=
"#property-Description.typedefinitions">type definitions</a>}
properties of the <a href="#component-Description">Description</a>
component are collections of imported and inlined schema components
that describe Infoset <em>element information item</em>s.</p>
<p>When extensions are used to enable the use of a non-Infoset data
model, or a non-Schema constraint language, the
<code>wsdl:required</code> attribute information item MAY be used
to require support for that extension.</p>
<div class="note">
<p class="prefix"><strong>Note:</strong></p>
<p>Support for the W3C XML Schema [<cite><a href="#XMLSchemaP1">XML
Schema: Structures</a></cite>], [<cite><a href="#XMLSchemaP2">XML
Schema: Datatypes</a></cite>] is included in the conformance
criteria for WSDL 2.0 documents (see <a href=
"#xsd-types"><strong>3.1 Using W3C XML Schema Definition
Language</strong></a> ).</p>
</div>
<p>The schema components contained in the {<a href=
"#property-Description.elementdeclarations">element
declarations</a>} property of the <a href=
"#component-Description">Description</a> component provide the type
system used for <a href=
"#component-InterfaceMessageReference">Interface Message
Reference</a> and <a href="#component-InterfaceFault">Interface
Fault</a> components. <a href=
"#component-InterfaceMessageReference">Interface Message
Reference</a> components indicate their structure and content by
using the standard <em>attribute information item</em>s
<code>element</code>, or for alternate schema languages in which
these concepts do not map well, by using alternative <em>attribute
information item</em> extensions. <a href=
"#component-InterfaceFault">Interface Fault</a> components behave
similarly. Such extensions should define how they reference type
system components. Such type system components MAY appear in
additional collection properties on the <a href=
"#component-Description">Description</a> component.</p>
<p>Extensions in the form of <em>attribute information item</em>s
can be used to refer to constraints (type definitions or analogous
constructs) described using other schema languages or type systems.
Such components MAY appear in additional collection properties on
the <a href="#component-Description">Description</a> component.</p>
<p>The <code>types</code> <em>element information item</em>
encloses data type definitions, based upon the XML Infoset, used to
define messages and has the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>types</code>.</p>
</li>
<li>
<p>A [namespace name] of "http://www.w3.org/ns/wsdl".</p>
</li>
<li>
<p>Zero or more namespace qualified <em>attribute information
item</em>s whose [namespace name] is NOT
http://www.w3.org/ns/wsdl</p>
</li>
<li>
<p>Zero or more <em>element information item</em>s amongst its
[children] as follows:</p>
<ul>
<li>
<p>Zero or more <code>documentation</code> <em>element information
item</em>s (see <a href="#eii-documentation"><strong>5.
Documentation</strong></a>) in its [children] property.</p>
</li>
<li>
<p>Zero or more <em>element information item</em>s from among the
following, in any order:</p>
<ul>
<li>
<p><code>xs:import</code> <em>element information item</em>s</p>
</li>
<li>
<p><code>xs:schema</code> <em>element information item</em>s</p>
</li>
<li>
<p>Other namespace qualified <em>element information item</em>s
whose namespace is NOT http://www.w3.org/ns/wsdl</p>
</li>
</ul>
</li>
</ul>
</li>
</ul>
<div class="div2">
<h3><a name="xsd-types" id="xsd-types"></a>3.1 Using W3C XML Schema
Definition Language</h3>
<p>XML Schema MAY be used as the schema language via import or
inlining.</p>
<p><span id="Schema-1066" class="test-assertion-tr">A WSDL 2.0
document MUST NOT refer to XML Schema components in a given
namespace UNLESS an <code>xs:import</code> or
<code>xs:schema</code> <em>element information item</em> for that
namespace is present OR the namespace is the XML Schema namespace,
http://www.w3.org/2001/XMLSchema, which contains built-in types as
defined in XML Schema Part 2: Datatypes Second Edition
[<cite><a href="#XMLSchemaP2">XML Schema:
Datatypes</a></cite>].<sup><a href="#Schema-1066-summary" title=
"Link to assertion Schema-1066 summary">†</a></sup></span> That is,
using the <code>xs:import</code> or <code>xs:schema</code>
<em>element information item</em> is a necessary condition for
making XML Schema components, other than the built-in components,
referenceable within a WSDL 2.0 document. The built-in XML Schema
datatypes are built-in to the WSDL 2.0 component model and are
contained in the {<a href=
"#property-Description.typedefinitions">type definitions</a>}
property of the <a href="#component-Description">Description</a>
component. A WSDL 2.0 document that refers to any element
declaration or type definition component of the XML Schema
namespace, except the built-in primitive and derived types, MUST
import http://www.w3.org/2001/XMLSchema.</p>
<p><a href="#tab_SchemaVisibility">Table 3-1</a> summarizes the
referenceability of schema components.</p>
<a name="tab_SchemaVisibility" id="tab_SchemaVisibility"></a>
<table border="1">
<caption>Table 3-1. Referenceability of schema components</caption>
<col width="20%" span="1" />
<col width="40%" span="1" />
<col width="40%" span="1" />
<tbody>
<tr>
<th rowspan="1" colspan="1"></th>
<th rowspan="1" colspan="1">XML Representation</th>
<th rowspan="1" colspan="1">Referenceability of XML Schema
Components</th>
</tr>
<tr>
<td rowspan="1" colspan="1">Including description</td>
<td rowspan="1" colspan="1">description/include</td>
<td rowspan="1" colspan="1">XML Schema components in the included
<a href="#component-Description">Description</a> component's
{<a href="#property-Description.elementdeclarations">element
declarations</a>} and {<a href=
"#property-Description.typedefinitions">type definitions</a>}
properties are referenceable.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">Importing description</td>
<td rowspan="1" colspan="1">description/import</td>
<td rowspan="1" colspan="1">None of the XML Schema Components in
the imported <a href="#component-Description">Description</a>
component are referenceable.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">Importing XML Schema</td>
<td rowspan="1" colspan="1">description/types/xs:import</td>
<td rowspan="1" colspan="1"><a href=
"#component-ElementDeclaration">Element Declaration</a> and
<a href="#component-TypeDefinition">Type Definition</a> components
in the imported namespace are referenceable.</td>
</tr>
<tr>
<td rowspan="1" colspan="1">Inlined XML Schema</td>
<td rowspan="1" colspan="1">description/types/xs:schema</td>
<td rowspan="1" colspan="1"><a href=
"#component-ElementDeclaration">Element Declaration</a> and
<a href="#component-TypeDefinition">Type Definition</a> components
in the inlined XML Schema are referenceable.</td>
</tr>
</tbody>
</table>

<br />
<div class="div3">
<h4><a name="import-xsd" id="import-xsd"></a>3.1.1 Importing XML
Schema</h4>
<p>Importing an XML Schema uses the syntax and semantics of the
<code>xs:import</code> mechanism defined by XML Schema
[<cite><a href="#XMLSchemaP1">XML Schema: Structures</a></cite>],
[<cite><a href="#XMLSchemaP2">XML Schema: Datatypes</a></cite>],
with the differences defined in this section and the following one.
The schema components defined in the imported namespace are
referenceable by QName (see <a href="#qnameres"><strong>2.17 QName
resolution</strong></a>). Only components in the imported namespace
are referenceable in the WSDL 2.0 document. <span id=
"Description-1067" class="test-assertion-tr">For each component in
the imported namespace, a corresponding <a href=
"#component-ElementDeclaration">Element Declaration</a> component
or <a href="#component-TypeDefinition">Type Definition</a>
component MUST appear in the {<a href=
"#property-Description.elementdeclarations">element
declarations</a>} or {<a href=
"#property-Description.typedefinitions">type definitions</a>}
property respectively of the <a href=
"#component-Description">Description</a> component corresponding to
the WSDL document that imports the schema, or that imports directly
or indirectly a WSDL document that imports the schema.<sup><a href=
"#Description-1067-summary" title=
"Link to assertion Description-1067 summary">†</a></sup></span>
<span id="Description-1068" class="test-assertion-tr">Schema
components not in an imported namespace MUST NOT appear in the
{<a href="#property-Description.elementdeclarations">element
declarations</a>} or {<a href=
"#property-Description.typedefinitions">type definitions</a>}
properties.<sup><a href="#Description-1068-summary" title=
"Link to assertion Description-1068 summary">†</a></sup></span></p>
<p>A child <em>element information item</em> of the
<code>types</code> <em>element information item</em> is defined
with the Infoset properties as follows:</p>
<ul>
<li>
<p>A [local name] of "import".</p>
</li>
<li>
<p>A [namespace name] of "http://www.w3.org/2001/XMLSchema".</p>
</li>
<li>
<p>One or two <em>attribute information item</em>s as follows:</p>
<ul>
<li>
<p>A REQUIRED <code>namespace</code> <em>attribute information
item</em> as described below.</p>
</li>
<li>
<p>An OPTIONAL <code>schemaLocation</code> <em>attribute
information item</em> as described below.</p>
</li>
</ul>
</li>
</ul>
<div class="div4">
<h5><a name="namespace-attribute" id=
"namespace-attribute"></a>3.1.1.1 <code>namespace</code>
<em>attribute information item</em></h5>
<p>The <code>namespace</code> <em>attribute information item</em>
defines the namespace of the element declarations and type
definitions imported from the referenced schema. <span id=
"Schema-1069" class="test-assertion-tr">The referenced schema MUST
contain a <code>targetNamespace</code> <em>attribute information
item</em> on its <code>xs:schema</code> <em>element information
item</em>.<sup><a href="#Schema-1069-summary" title=
"Link to assertion Schema-1069 summary">†</a></sup></span>
<span id="Schema-1070" class="test-assertion-tr">The value of the
<code>targetNamespace</code> <em>attribute information item</em> of
the <code>xs:schema</code> <em>element information item</em> of an
imported schema MUST equal the value of the <code>namespace</code>
of the <code>import</code> <em>element information item</em> in the
importing WSDL 2.0 document.<sup><a href="#Schema-1070-summary"
title="Link to assertion Schema-1070 summary">†</a></sup></span>
Note that a WSDL 2.0 document must not import a schema that does
not have a <code>targetNamespace</code> <em>attribute information
item</em> on its <code>xs:schema</code> <em>element information
item</em>. Such schemas must first be included (using
<code>xs:include</code>) in a schema that contains a
<code>targetNamespace</code> <em>attribute information item</em> on
its <code>xs:schema</code> <em>element information item</em>, which
can then be either imported or inlined in the WSDL 2.0
document.</p>
<p>The <code>namespace</code> <em>attribute information item</em>
has the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of namespace</p>
</li>
<li>
<p>A [namespace name] which has no value.</p>
</li>
</ul>
<p>The type of the <code>namespace</code> <em>attribute information
item</em> is <em>xs:anyURI</em>.</p>
</div>
<div class="div4">
<h5><a name="schemaLocation-attribute" id=
"schemaLocation-attribute"></a>3.1.1.2 <code>schemaLocation</code>
<em>attribute information item</em></h5>
<p>The <code>schemaLocation</code> <em>attribute information
item</em>, if present, provides a hint to the XML Schema processor
as to where the schema may be located. Caching and cataloging
technologies may provide better information than this hint. The
<code>schemaLocation</code> <em>attribute information item</em> has
the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of schemaLocation.</p>
</li>
<li>
<p>A [namespace name] which has no value.</p>
</li>
</ul>
<p>The type of the <code>schemaLocation</code> <em>attribute
information item</em> is <em>xs:anyURI.</em></p>
<p>Every QName reference must resolve (see <a href=
"#qnameres"><strong>2.17 QName resolution</strong></a>). Note that,
when resolving QNames references for schema definitions, the
namespace must be imported by the referring WSDL 2.0 document (see
<a href="#xsd-types"><strong>3.1 Using W3C XML Schema Definition
Language</strong></a>).</p>
</div>
</div>
<div class="div3">
<h4><a name="inlining-xsd" id="inlining-xsd"></a>3.1.2 Inlining XML
Schema</h4>
<p>Inlining an XML schema uses the existing top-level
<code>xs:schema</code> <em>element information item</em> defined by
XML Schema [<cite><a href="#XMLSchemaP1">XML Schema:
Structures</a></cite>]. Conceptually, inlining can be viewed as
simply cutting and pasting an existing schema document to a
location inside the types <em>element information item</em>.</p>
<p>The schema components defined and declared in the inlined schema
document are referenceable by QName (see <a href=
"#qnameres"><strong>2.17 QName resolution</strong></a>). Only
components defined and declared in the schema itself and components
included by it via <code>xs:include</code> are referenceable.
<span id="Description-1071" class="test-assertion-tr">For each
component defined and declared in the inlined schema document or
included by <code>xs:include</code>, a corresponding <a href=
"#component-ElementDeclaration">Element Declaration</a> component
or <a href="#component-TypeDefinition">Type Definition</a>
component MUST appear in the {<a href=
"#property-Description.elementdeclarations">element
declarations</a>} property or {<a href=
"#property-Description.typedefinitions">type definitions</a>}
property respectively of the <a href=
"#component-Description">Description</a> component corresponding to
the WSDL document that contains the schema, or that imports
directly or indirectly a WSDL document that contains the
schema.<sup><a href="#Description-1071-summary" title=
"Link to assertion Description-1071 summary">†</a></sup></span><span id="Description-1072"
class="test-assertion-tr">Schema components not defined or declared
in the inlined schema document or included by
<code>xs:include</code> MUST NOT appear in the {<a href=
"#property-Description.elementdeclarations">element
declarations</a>} or {<a href=
"#property-Description.typedefinitions">type definitions</a>}
properties.<sup><a href="#Description-1072-summary" title=
"Link to assertion Description-1072 summary">†</a></sup></span></p>
<p>Note that components in the namespace that the inline schema
imports via <code>xs:import</code> are not automatically
referenceable from the WSDL 2.0 document that contains the inline
schema. If the namespace referenced in a QName is contained in an
inline schema, it MAY be imported without a
<code>schemaLocation</code> attribute, so long as the inline schema
has been resolved in the current component model.</p>
<p>Note that components defined in an inlined XML schema are not
automatically referenceable within the WSDL 2.0 document that
imported (using <code>wsdl:import</code>) the WSDL 2.0 document
that inlines the schema (see <a href="#imports"><strong>4.2
Importing Descriptions</strong></a> for more details). For this
reason, it is recommended that XML schema documents intended to be
shared across several WSDL 2.0 documents be placed in separate XML
schema documents and imported using <code>xs:import</code>, rather
than inlined inside a WSDL 2.0 document.</p>
<p>Inside an inlined XML schema, the <code>xs:import</code> and
<code>xs:include</code> <em>element information item</em>s MAY be
used to refer to other XML schemas inlined in the same or other
WSDL 2.0 document, provided that an appropriate value, such as a
fragment identifier (see [<cite><a href="#XMLSchemaP1">XML Schema:
Structures</a></cite>] 4.3.1) is specified for their
<code>schemaLocation</code> <em>attribute information item</em>s.
For <code>xs:import</code>, the <code>schemaLocation</code>
attribute is not required so long as the namespace has been
resolved in the current component model. The semantics of such
<em>element information item</em>s are governed solely by the XML
Schema specification [<cite><a href="#XMLSchemaP1">XML Schema:
Structures</a></cite>].</p>
<p>A WSDL 2.0 document MAY inline two or more schemas from the same
<code>targetNamespace</code>. For example, two or more inlined
schemas can have the same <code>targetNamespace</code> provided
that they do not define the same elements or types. <span id=
"Schema-1073" class="test-assertion-tr">A WSDL 2.0 document MUST
NOT define the same element or type in more than one inlined
schema.<sup><a href="#Schema-1073-summary" title=
"Link to assertion Schema-1073 summary">†</a></sup></span> Note
that it is the responsibility of the underlying XML Schema
processor to sort out a coherent set of schema components.</p>
<p>The <code>xs:schema</code> <em>element information item</em> has
the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of schema.</p>
</li>
<li>
<p>A [namespace name] of "http://www.w3.org/2001/XMLSchema".</p>
</li>
<li>
<p>Additional OPTIONAL <em>attribute information item</em>s as
specified for the <code>xs:schema</code> <em>element information
item</em> by the XML Schema specification.</p>
</li>
<li>
<p>Zero or more child <em>element information item</em>s as
specified for the <code>xs:schema</code> <em>element information
item</em> by the XML Schema specification.</p>
</li>
</ul>
</div>
<div class="div3">
<h4><a name="references-definitions" id=
"references-definitions"></a>3.1.3 References to Element
Declarations and Type Definitions</h4>
<p>Whether inlined or imported, the global element declarations
present in a schema are referenceable from an <a href=
"#component-InterfaceMessageReference">Interface Message
Reference</a> or <a href="#component-InterfaceFault">Interface
Fault</a> component. Similarly, regardless of whether they are
inlined or imported, the global type definitions present in a
schema are referenceable from other components.</p>
<p>A named, global <code>xs:element</code> declaration is
referenceable from the <code>element</code> <em>attribute
information item</em> of an <code>input</code>, <code>output</code>
(see <a href="#InterfaceMessageReference_XMLRep"><strong>2.5.2 XML
Representation of Interface Message Reference
Component</strong></a>) or <code>fault</code> <em>element
information item</em> (see <a href=
"#InterfaceFault_XMLRep"><strong>2.3.2 XML Representation of
Interface Fault Component</strong></a>). The QName of the element
declaration is constructed from the <code>targetNamespace</code> of
the schema and the value of the <code>name</code> <em>attribute
information item</em> of the <code>xs:element</code> <em>element
information item</em>. Note that the <code>element</code>
<em>attribute information item</em> cannot refer to a global
<code>xs:simpleType</code> or <code>xs:complexType</code>
definition, since these are in a different symbol space than global
element declarations. If the <code>element</code> <em>attribute
information item</em> erroneously contains the QName of a type
definition then this would result in a failure to resolve the
element declaration.</p>
</div>
</div>
<div class="div2">
<h3><a name="other-types" id="other-types"></a>3.2 Using Other
Schema Languages</h3>
<p>Since it is unreasonable to expect that a single schema language
can be used to describe all possible <a href=
"#component-InterfaceMessageReference">Interface Message
Reference</a> and <a href="#component-InterfaceFault">Interface
Fault</a> component contents and their constraints, WSDL 2.0 allows
alternate schema languages to be specified via extension elements.
An extension <em>element information item</em> MAY appear under the
<code>types</code> <em>element information item</em> to identify
the schema language employed, and to locate the schema instance
defining the grammar for <a href=
"#component-InterfaceMessageReference">Interface Message
Reference</a> and <a href="#component-InterfaceFault">Interface
Fault</a> components. Depending upon the schema language used, an
<em>element information item</em> MAY be defined to allow inlining,
if and only if the schema language can be expressed in XML.</p>
<p><span id="Types-1074" class="test-assertion-tr">A specification
of extension syntax for an alternative schema language MUST include
the declaration of an <em>element information item</em>, intended
to appear as a child of the <code>wsdl:types</code> <em>element
information item</em>, which references, names, and locates the
schema instance (an <code>import</code> <em>element information
item</em>).<sup><a href="#Types-1074-summary" title=
"Link to assertion Types-1074 summary">†</a></sup></span> The
extension specification SHOULD, if necessary, define additional
properties of the <a href="#component-Description">Description</a>
component (and extension attributes) to hold the components of the
referenced type system. It is expected that additional extension
attributes for <a href=
"#component-InterfaceMessageReference">Interface Message
Reference</a> and <a href="#component-InterfaceFault">Interface
Fault</a> components will also be defined, along with a mechanism
for resolving the values of those attributes to a particular
imported type system component.</p>
<p><span id="Schema-1075" class="test-assertion-tr">A specification
of extension syntax for an alternative schema language MUST use a
namespace that is different than the namespace of XML
Schema.<sup><a href="#Schema-1075-summary" title=
"Link to assertion Schema-1075 summary">†</a></sup></span> The
namespace of the alternative schema language is used for
<em>element information item</em>s that are children of the
<code>wsdl:types</code> <em>element information item</em> and for
any extension <em>attribute information item</em>s that appear on
other components. <span id="Schema-1076" class=
"test-assertion-tr">The namespace used for an alternate schema
language MUST be an absolute IRI.<sup><a href=
"#Schema-1076-summary" title=
"Link to assertion Schema-1076 summary">†</a></sup></span></p>
<p>See [<cite><a href="#WSDL2-OTHER-SCHEMA">WSDL 2.0 Alternative
Schema Languages Support</a></cite>] for examples of using other
schema languages. These examples reuse the {<a href=
"#property-Description.elementdeclarations">element
declarations</a>} property of the <a href=
"#component-Description">Description</a> component and the
<code>element</code> <em>attribute information item</em>s of the
<code>wsdl:input</code>, <code>wsdl:output</code> and
<code>wsdl:fault</code> <em>element information item</em>s.</p>
<div class="note">
<p class="prefix"><strong>Note:</strong></p>
<p>This specification does not define the behavior of a WSDL 2.0
document that uses multiple schema languages for describing type
system components simultaneously.</p>
</div>
</div>
<div class="div2">
<h3><a name="wsdlx-references" id="wsdlx-references"></a>3.3
Describing Messages that Refer to Services and Endpoints</h3>
<p>Web services can exchange messages that refer to other Web
services or Web service endpoints. If the interface or binding of
these referenced services or endpoints are known at description
time, then it may be useful to include this information in the WSDL
2.0 document that describes the Web service. WSDL 2.0 provides two
global <em>attribute information item</em>s,
<code>wsdlx:interface</code> and <code>wsdlx:binding</code> that
may be used to annotate XML Schema components or components from
other type description languages.</p>
<p>WSDL 2.0 defines the use of these global <em>attribute
information item</em>s to annotate XML Schema components that use
the <code>xs:anyURI</code> simple type in an <em>element
information item</em> or <em>attribute information item</em> for
endpoint addresses that correspond to the {<a href=
"#property-Endpoint.address">address</a>} property of the <a href=
"#component-Endpoint">Endpoint</a> component. However, the use of
these global <em>attribute information item</em>s is not limited to
simple types based on <code>xs:anyURI</code>. They may be used for
any other types that are used to refer to Web services or Web
service endpoints, e.g. a WS-Addressing Endpoint Reference
[<cite><a href="#WSA-Core">WSA 1.0 Core</a></cite>]. See the primer
[<cite><a href="#WSDL-PART0">WSDL 2.0 Primer</a></cite>] for more
information and examples.</p>
<div class="div3">
<h4><a name="wsdlx-interface-aii" id=
"wsdlx-interface-aii"></a>3.3.1 <code>wsdlx:interface</code>
<em>attribute information item</em></h4>
<p>WSDL 2.0 provides a global <em>attribute information item</em>
with the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>interface</code>.</p>
</li>
<li>
<p>A [namespace name] of " http://www.w3.org/ns/wsdl-extensions
".</p>
</li>
</ul>
<p><span id="Types-1077" class="test-assertion-tr">The type of the
<code>wsdlx:interface</code> <em>attribute information item</em> is
an <em>xs:QName</em> that specifies the {<a href=
"#property-Interface.name">name</a>} property of an <a href=
"#component-Interface">Interface</a> component.<sup><a href=
"#Types-1077-summary" title=
"Link to assertion Types-1077 summary">†</a></sup></span></p>
</div>
<div class="div3">
<h4><a name="wsdlx-binding-aii" id="wsdlx-binding-aii"></a>3.3.2
<code>wsdlx:binding</code> <em>attribute information item</em></h4>
<p>WSDL 2.0 provides a global <em>attribute information item</em>
with the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>binding</code>.</p>
</li>
<li>
<p>A [namespace name] of " http://www.w3.org/ns/wsdl-extensions
".</p>
</li>
</ul>
<p><span id="Types-1078" class="test-assertion-tr">The type of the
<code>wsdlx:binding</code> <em>attribute information item</em> is
an <em>xs:QName</em> that specifies the {<a href=
"#property-Binding.name">name</a>} property of a <a href=
"#component-Binding">Binding</a> component.<sup><a href=
"#Types-1078-summary" title=
"Link to assertion Types-1078 summary">†</a></sup></span></p>
</div>
<div class="div3">
<h4><a name="wsdlx-consistency" id="wsdlx-consistency"></a>3.3.3
<code>wsdlx:interface</code> and <code>wsdlx:binding</code>
Consistency</h4>
<p>The <code>wsdlx:interface</code> and <code>wsdlx:binding</code>
attributes may be used either independently or together. <span id=
"Schema-1079" class="test-assertion-tr">If
<code>wsdlx:interface</code> and <code>wsdlx:binding</code> are
used together then they MUST satisfy the same consistency rules
that apply to the {<a href=
"#property-Service.interface">interface</a>} property of a <a href=
"#component-Service">Service</a> component and the {<a href=
"#property-Endpoint.binding">binding</a>} property of a nested
<a href="#component-Endpoint">Endpoint</a> component, that is
either the binding refers the interface of the service or the
binding refers to no interface.<sup><a href="#Schema-1079-summary"
title=
"Link to assertion Schema-1079 summary">†</a></sup></span></p>
</div>
<div class="div3">
<h4><a name="wsdlx-xsanyuri" id="wsdlx-xsanyuri"></a>3.3.4 Use of
<code>wsdlx:interface</code> and <code>wsdlx:binding</code> with
<code>xs:anyURI</code></h4>
<p><code>wsdlx:interface</code> and <code>wsdlx:binding</code> are
used to describe <em>element information item</em>s and
<em>attribute information item</em>s whose type is
<code>xs:anyURI</code> or a restriction of it, as well messages
that contain the {<a href="#property-Endpoint.address">address</a>}
property of an <a href="#component-Endpoint">Endpoint</a>. This is
accomplished by including the <code>wsdlx:interface</code> and/or
<code>wsdlx:binding</code> <em>attribute information item</em> in
the <code>xs:element</code>, <code>xs:simpleType</code>, or
<code>xs:attribute</code> <em>element information item</em> of the
corresponding XML Schema component.</p>
</div>
</div>
</div>
<div class="div1">
<h2><a name="modularize" id="modularize"></a>4. Modularizing WSDL
2.0 descriptions</h2>
<p>WSDL 2.0 provides two mechanisms for modularizing WSDL 2.0
descriptions. These mechanisms help to make Web service
descriptions clearer by allowing separation of the various
components of a description. Such separation can be performed
according to the level of abstraction of a given set of components,
or according to the namespace affiliation required of a given set
of components or even according to some other grouping such as
application applicability.</p>
<p>Both mechanisms work at the level of WSDL 2.0 components and NOT
at the level of XML Information Sets or XML 1.0 serializations.</p>
<div class="div2">
<h3><a name="includes" id="includes"></a>4.1 Including
Descriptions</h3>
<div class="exampleInner">
<pre xml:space="preserve">
&lt;description&gt;
  &lt;<strong>include</strong>
        location="<em>xs:anyURI</em>" &gt;
    &lt;documentation /&gt;*
  &lt;/<strong>include</strong>&gt;
&lt;/description&gt;
</pre></div>
<p>The WSDL 2.0 <code>include</code> <em>element information
item</em> allows separating the different components of a service
definition, belonging to the same target namespace, into
independent WSDL 2.0 documents.</p>
<p>The WSDL 2.0 <code>include</code> <em>element information
item</em> is modeled after the XML Schema <code>include</code>
<em>element information item</em> (see [<cite><a href=
"#XMLSchemaP1">XML Schema: Structures</a></cite>], section 4.2.3
"References to schema components in the same namespace").
Specifically, it can be used to include components from WSDL 2.0
descriptions that share a target namespace with the including
description. Components in the transitive closure of the included
WSDL 2.0 documents become part of the <a href=
"#component-Description">Description</a> component of the including
WSDL 2.0 document. The included components can be referenced by
QName. Note that because all WSDL 2.0 descriptions have a target
namespace, no-namespace includes (sometimes known as “chameleon
includes”) never occur in WSDL 2.0.</p>
<p>A mutual include is the direct inclusion by one WSDL 2.0
document of another WSDL 2.0 document which includes the first
document. A circular include achieves the same effect with greater
indirection (for example, A includes B, B includes C, and C
includes A). Multiple inclusion of a single WSDL 2.0 document
resolves to a single set of components, as if the document was
included only once. Mutual, multiple, and circular includes are
explicitly permitted, and do not represent multiple redefinitions
of the same components.</p>
<p>The <code>include</code> <em>element information item</em>
has:</p>
<ul>
<li>
<p>A [local name] of <code>include</code>.</p>
</li>
<li>
<p>A [namespace name] of "http://www.w3.org/ns/wsdl".</p>
</li>
<li>
<p>One or more <em>attribute information item</em>s amongst its
[attributes] as follows:</p>
<ul>
<li>
<p>A REQUIRED <code>location</code> <em>attribute information
item</em> as described below in <a href=
"#include_location_attribute"><strong>4.1.1 location attribute
information item with include [owner element]</strong></a>.</p>
</li>
<li>
<p>Zero or more namespace qualified <em>attribute information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl".</p>
</li>
</ul>
</li>
<li>
<p>Zero or more <em>element information item</em> amongst its
[children], as follows:</p>
<ul>
<li>
<p>Zero or more <code>documentation</code> <em>element information
item</em>s (see <a href="#eii-documentation"><strong>5.
Documentation</strong></a>).</p>
</li>
<li>
<p>Zero or more namespace-qualified <em>element information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl".</p>
</li>
</ul>
</li>
</ul>
<div class="div3">
<h4><a name="include_location_attribute" id=
"include_location_attribute"></a>4.1.1 <code>location</code>
<em>attribute information item</em> with <code>include</code>
[owner element]</h4>
<p>The <code>location</code> <em>attribute information item</em>
has the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>location</code>.</p>
</li>
<li>
<p>A [namespace name] which has no value.</p>
</li>
</ul>
<p>A <code>location</code> <em>attribute information item</em> is
of type <code>xs:anyURI</code>. Its actual value is the location of
some information about the namespace identified by the
<code>targetNamespace</code> <em>attribute information item</em> of
the containing <code>description</code> <em>element information
item</em>.</p>
<p><span id="Include-1080" class="test-assertion-tr">The IRI
indicated by <code>location</code> MUST resolve to a WSDL 2.0
document.<sup><a href="#Include-1080-summary" title=
"Link to assertion Include-1080 summary">†</a></sup></span> (see
<a href="#wsdllocation"><strong>7. Locating WSDL 2.0
Documents</strong></a>)</p>
<p><span id="Include-1081" class="test-assertion-tr">The actual
value of the <code>targetNamespace</code> <em>attribute information
item</em> of the included WSDL 2.0 document MUST match the actual
value of the <code>targetNamespace</code> <em>attribute information
item</em> of the <code>description</code> <em>element information
item</em> which is the [parent] of the <code>include</code>
<em>element information item</em>.<sup><a href=
"#Include-1081-summary" title=
"Link to assertion Include-1081 summary">†</a></sup></span></p>
</div>
</div>
<div class="div2">
<h3><a name="imports" id="imports"></a>4.2 Importing
Descriptions</h3>
<div class="exampleInner">
<pre xml:space="preserve">
&lt;description&gt;
  &lt;<strong>import</strong>
        namespace="<em>xs:anyURI</em>" location="<em>xs:anyURI</em>"? &gt;
    &lt;documentation /&gt;*
  &lt;/<strong>import</strong>&gt;
&lt;/description&gt;
</pre></div>
<p>Every top-level WSDL 2.0 component is associated with a
namespace. Every WSDL 2.0 document carries a
<code>targetNamespace</code> <em>attribute information item</em> on
its <code>wsdl:description</code> <em>element information
item</em>. This attribute associates the document with a target
namespace, which consequently also becomes the namespace of each
top-level WSDL 2.0 component defined in that document. Any
namespace other than the document's target namespace is referred to
as a <em>foreign namespace</em>. Any component associated with a
foreign namespace is referred to as a <em>foreign component</em>.
This section describes the syntax and mechanisms by which
references may be made from within a WSDL 2.0 document to foreign
components. In addition to this syntax, there is an optional
facility for suggesting the IRI of a WSDL 2.0 document that
contains definitions of foreign components.</p>
<p>The WSDL 2.0 <code>import</code> <em>element information
item</em> is modeled after the XML Schema <code>import</code>
<em>element information item</em> (see [<cite><a href=
"#XMLSchemaP1">XML Schema: Structures</a></cite>], section 4.2.3
"References to schema components across namespaces"). Specifically,
it can be used to import WSDL 2.0 components from a foreign
namespace. The WSDL 2.0 <code>import</code> <em>element information
item</em> identifies a foreign namespace. The presence of a WSDL
2.0 <code>import</code> <em>element information item</em> signals
that the WSDL 2.0 document may contain references to foreign
components. The <code>wsdl:import</code> <em>element information
item</em> is therefore like a forward declaration for foreign
namespaces.</p>
<p><span id="Import-1082" class="test-assertion-tr">As with XML
schema, any WSDL 2.0 document that references a foreign component
MUST have a <code>wsdl:import</code> <em>element information
item</em> for the associated foreign namespace (but which does not
necessarily provide a <code>location</code> <em>attribute
information item</em> that identifies the WSDL 2.0 document in
which the referenced component is defined).<sup><a href=
"#Import-1082-summary" title=
"Link to assertion Import-1082 summary">†</a></sup></span> In other
respects, the visibility of components is pervasive: if two WSDL
2.0 documents import the same namespace, then they will have access
to the same components from the imported namespace (i.e. regardless
of which, if any, <code>location</code> <em>attribute information
item</em> values are provided on the respective
<code>wsdl:import</code> <em>element information item</em>s.)</p>
<p>Using the <code>wsdl:import</code> <em>element information
item</em> is a necessary condition for making foreign components
available to a WSDL 2.0 document. That is, a WSDL 2.0 document can
only refer to foreign components, if it contains an
<code>wsdl:import</code> <em>element information item</em> for the
associated foreign namespace.</p>
<p><span id="Import-1083" class="test-assertion-tr">If a WSDL 2.0
document contains more than one <code>wsdl:import</code>
<em>element information item</em> for a given value of the
<code>namespace</code> <em>attribute information item</em>, then
they MUST provide different values for the <code>location</code>
<em>attribute information item</em>.<sup><a href=
"#Import-1083-summary" title=
"Link to assertion Import-1083 summary">†</a></sup></span>
Repeating the <code>wsdl:import</code> <em>element information
item</em> for the same <code>namespace</code> value MAY be used as
a way to provide alternate locations to find information about a
given namespace.</p>
<p>Furthermore, this specification DOES NOT require the
<code>location</code> <em>attribute information item</em> to be
dereferencable. When it is not dereferencable, no information about
the imported namespace is provided by that <code>wsdl:import</code>
<em>element information item</em>. It is possible that such lack of
information can cause QNames in other parts of a WSDL 2.0 <a href=
"#component-Description">Description</a> component to become broken
references (see <a href="#qnameres"><strong>2.17 QName
resolution</strong></a>). Such broken references are not ascribed
to the <code>wsdl:import</code> <em>element information item</em>,
but rather are failures of the QName resolution requirements which
must be detected as described in <a href="#qnameres"><strong>2.17
QName resolution</strong></a>.</p>
<p>The <code>import</code> <em>element information item</em> has
the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>import</code>.</p>
</li>
<li>
<p>A [namespace name] of "http://www.w3.org/ns/wsdl".</p>
</li>
<li>
<p>One or more <em>attribute information item</em>s amongst its
[attributes] as follows:</p>
<ul>
<li>
<p>A REQUIRED <code>namespace</code> <em>attribute information
item</em> as described below in <a href=
"#import_namespace_attribute"><strong>4.2.1 namespace attribute
information item</strong></a>.</p>
</li>
<li>
<p>An OPTIONAL <code>location</code> <em>attribute information
item</em> as described below in <a href=
"#import_location_attribute"><strong>4.2.2 location attribute
information item with import [owner element]</strong></a>.</p>
</li>
<li>
<p>Zero or more namespace qualified <em>attribute information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl".</p>
</li>
</ul>
</li>
<li>
<p>Zero or more <em>element information item</em>s amongst its
[children], as follows:</p>
<ul>
<li>
<p>Zero or more <code>documentation</code> <em>element information
item</em>s (see <a href="#eii-documentation"><strong>5.
Documentation</strong></a>).</p>
</li>
<li>
<p>Zero or more namespace-qualified <em>element information
item</em>s whose [namespace name] is NOT
"http://www.w3.org/ns/wsdl".</p>
</li>
</ul>
</li>
</ul>
<div class="div3">
<h4><a name="import_namespace_attribute" id=
"import_namespace_attribute"></a>4.2.1 <code>namespace</code>
<em>attribute information item</em></h4>
<p>The <code>namespace</code> <em>attribute information item</em>
has the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>namespace</code>.</p>
</li>
<li>
<p>A [namespace name] which has no value.</p>
</li>
</ul>
<p>The <code>namespace</code> <em>attribute information item</em>
is of type <code>xs:anyURI</code>. Its actual value indicates that
the containing WSDL 2.0 document MAY contain qualified references
to WSDL 2.0 components in that namespace (via one or more prefixes
declared with namespace declarations in the normal way). <span id=
"Import-1084" class="test-assertion-tr">This value MUST NOT match
the actual value of <code>targetNamespace</code> <em>attribute
information item</em> in the enclosing WSDL 2.0
document.<sup><a href="#Import-1084-summary" title=
"Link to assertion Import-1084 summary">†</a></sup></span>&#160;
<span id="Import-1085" class="test-assertion-tr">If the location
attribute in the <code>import</code> <em>element information
item</em> is dereferencable, then it MUST reference a WSDL 2.0
document.<sup><a href="#Import-1085-summary" title=
"Link to assertion Import-1085 summary">†</a></sup></span>
<span id="Import-1086" class="test-assertion-tr">If the
<code>location</code> <em>attribute information item</em> of the
<code>import</code> <em>element information item</em> is
dereferencable, then the actual value of the <code>namespace</code>
<em>attribute information item</em> MUST be identical to the actual
value of the <code>targetNamespace</code> <em>attribute information
item</em> of the referenced WSDL 2.0 document (see <a href=
"#wsdllocation"><strong>7. Locating WSDL 2.0
Documents</strong></a>).<sup><a href="#Import-1086-summary" title=
"Link to assertion Import-1086 summary">†</a></sup></span></p>
</div>
<div class="div3">
<h4><a name="import_location_attribute" id=
"import_location_attribute"></a>4.2.2 <code>location</code>
<em>attribute information item</em> with <code>import</code> [owner
element]</h4>
<p>The <code>location</code> <em>attribute information item</em>
has the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>location</code>.</p>
</li>
<li>
<p>A [namespace name] which has no value.</p>
</li>
</ul>
<p>The <code>location</code> <em>attribute information item</em> is
of type <code>xs:anyURI</code>. Its actual value, if present, gives
a hint as to where a serialization of a WSDL 2.0 document with
definitions for the imported namespace can be found.</p>
<p>The <code>location</code> <em>attribute information item</em> is
optional. This allows WSDL 2.0 components to be constructed from
information other than an XML 1.0 serialization of a WSDL 2.0
document. It also allows the development of WSDL 2.0 processors
that have <em>a prior</em> (i.e., built-in) knowledge of certain
namespaces.</p>
</div>
</div>
<div class="div2">
<h3><a name="extensions-and-modules" id=
"extensions-and-modules"></a>4.3 Extensions</h3>
<p><span id="ImportInclude-1087" class="test-assertion-tr">The
semantics of an extension MUST NOT depend on how components are
brought into a component model instance via &lt;import&gt; or
&lt;include&gt;. <sup><a href="#ImportInclude-1087-summary" title=
"Link to assertion ImportInclude-1087 summary">†</a></sup></span>
That is, the components that are defined by a WSDL 2.0 document are
determined by the contents of the document, EXCEPT for the
resolution of references to other components that may be defined in
other documents, AND any further processing, as mandated by the
extension specification, that depends on such references having
been resolved to the actual components.</p>
<p>This restriction on the behavior of extensions permits WSDL 2.0
documents to be flexibly modularized and efficiently processed. In
contrast, note that the so-called chameleon include mechanism of
XML Schema, which allows a no-namespace schema to be included in a
schema document that has a namespace, violates this restriction
since the namespace of the included XML Schema components is
determined by the including XML Schema document (see 4.2.1
Assembling a schema for a single target namespace from multiple
schema definition documents in [<cite><a href="#XMLSchemaP1">XML
Schema: Structures</a></cite>]).</p>
</div>
</div>
<div class="div1">
<h2><a name="eii-documentation" id="eii-documentation"></a>5.
Documentation</h2>
<div class="exampleInner">
<pre xml:space="preserve">
&lt;<strong>documentation</strong>&gt;
  [<em>extension elements</em>]*
&lt;/<strong>documentation</strong>&gt;
</pre></div>
<p>WSDL 2.0 uses the optional <code>documentation</code>
<em>element information item</em> as a container for human readable
or machine processable documentation. The content of the
<em>element information item</em> is arbitrary <em>character
information items</em> and <em>element information item</em>s
("mixed" content in XML Schema [<cite><a href="#XMLSchemaP1">XML
Schema: Structures</a></cite>]). The <code>documentation</code>
<em>element information item</em> is allowed inside any WSDL 2.0
<em>element information item</em>.</p>
<p>Like other <em>element information item</em>s in the
"http://www.w3.org/ns/wsdl" namespace, the
<code>documentation</code> <em>element information item</em> allows
qualified <em>attribute information item</em>s whose [namespace
name] is not "http://www.w3.org/ns/wsdl". The <code>xml:lang</code>
attribute (see [<cite><a href="#XML10">XML 1.0</a></cite>]) MAY be
used to indicate the language used in the contents of the
<code>documentation</code> <em>element information item</em>.</p>
<p>The <code>documentation</code> <em>element information item</em>
has:</p>
<ul>
<li>
<p>A [local name] of <code>documentation</code>.</p>
</li>
<li>
<p>A [namespace name] of "http://www.w3.org/ns/wsdl".</p>
</li>
<li>
<p>Zero or more <em>attribute information item</em>s in its
[attributes] property.</p>
</li>
<li>
<p>Zero or more child <em>element information item</em>s in its
[children] property.</p>
</li>
<li>
<p>Zero or more <em>character information item</em>s in its
[children] property.</p>
</li>
</ul>
</div>
<div class="div1">
<h2><a name="language-extensibility" id=
"language-extensibility"></a>6. Language Extensibility</h2>
<p>The schema for WSDL 2.0 has a two-part extensibility model based
on namespace-qualified elements and attributes. An extension is
identified by the QName consisting of its namespace IRI and its
element or attribute name. <span id="Extension-1088" class=
"test-assertion-tr">The meaning of an extension SHOULD be defined
(directly or indirectly) in a document that is available at its
namespace IRI.<sup><a href="#Extension-1088-summary" title=
"Link to assertion Extension-1088 summary">†</a></sup></span></p>
<div class="div2">
<h3><a name="eii-extensibility" id="eii-extensibility"></a>6.1
Element-based Extensibility</h3>
<p>WSDL 2.0 allows extensions to be defined in terms of <em>element
information item</em>s. Where indicated herein, WSDL 2.0 allows
namespace-qualified <em>element information item</em>s whose
[namespace name] is NOT "http://www.w3.org/ns/wsdl" to appear among
the [children] of specific <em>element information item</em>s whose
[namespace name] is "http://www.w3.org/ns/wsdl". Such <em>element
information item</em>s MAY be used to annotate WSDL 2.0 constructs
such as interface, operation, etc.</p>
<p>It is expected that extensions will add to the existing
properties of components in the component model. The specification
for an extension <em>element information item</em> should include
definitions of any such properties and the mapping from the XML
representation of the extension to the properties in the component
model.</p>
<p>The WSDL 2.0 schema defines a base type for use by extension
elements. <a href="#exttype">Example 6-1</a> shows the type
definition. The use of this type as a base type is optional.</p>
<div class="exampleOuter">
<p style="text-align: left" class="exampleHead"><a name="exttype"
id="exttype"></a><em><span>Example 6-1.</span> Base type for
extension elements</em></p>
<div class="exampleInner">
<pre xml:space="preserve">
&lt;xs:complexType name='ExtensionElement' abstract='true' &gt;
  &lt;xs:attribute ref='wsdl:required' use='optional' /&gt;
&lt;/xs:complexType&gt;
          
          
</pre></div>
</div>
<p>Extension elements are commonly used to specify some
technology-specific binding. They allow innovation in the area of
network and message protocols without having to revise the base
WSDL 2.0 specification. WSDL 2.0 recommends that specifications
defining such protocols also define any necessary WSDL 2.0
extensions used to describe those protocols or formats.</p>
<div class="div3">
<h4><a name="mandatoryext" id="mandatoryext"></a>6.1.1 Mandatory
extensions</h4>
<p>Extension elements can be marked as mandatory by annotating them
with a <code>wsdl:required</code> <em>attribute information
item</em> (see <a href="#required-aii"><strong>6.1.2 required
attribute information item</strong></a>) with a value of "true". A
mandatory extension is an extension that MAY change the meaning of
the element to which it is attached, such that the meaning of that
element is no longer governed by this specification. Instead, the
meaning of an element containing a mandatory extension is governed
by the meaning of that extension. Thus, the definition of the
element's meaning is <em>delegated</em> to the specification that
defines the extension.</p>
<p><span id="Extensibility-1089" class="test-assertion-tr">An
extension that is NOT marked as mandatory MUST NOT invalidate the
meaning of any part of a WSDL 2.0 document.<sup><a href=
"#Extensibility-1089-summary" title=
"Link to assertion Extensibility-1089 summary">†</a></sup></span>
Thus, a NON-mandatory extension merely provides additional
description of capabilities of the service. This specification does
not provide a mechanism to mark extension attributes as being
required. Therefore, all extension attributes are
NON-mandatory.</p>
<div class="note">
<p class="prefix"><strong>Note:</strong></p>
<p>A mandatory extension is considered mandatory because it has the
ability to change the meaning of the element to which it is
attached. Thus, the meaning of the element may not be fully
understood without understanding the attached extension. A
NON-mandatory extension, on the other hand, can be safely ignored
without danger of misunderstanding the rest of the WSDL 2.0
document.</p>
</div>
<p><span id="Extensibility-1090" class="test-assertion-tr">If a
WSDL 2.0 document declares an extension as optional (i.e.,
NON-mandatory), then the Web service MUST NOT assume that the
client supports that extension <em>unless</em> the Web service
knows (through some other means) that the client has in fact
elected to engage and support that extension.<sup><a href=
"#Extensibility-1090-summary" title=
"Link to assertion Extensibility-1090 summary">†</a></sup></span></p>
<div class="note">
<p class="prefix"><strong>Note:</strong></p>
<p>A key purpose of an extension is to formally indicate (i.e., in
a machine-processable way) that a particular feature or convention
is supported or required. This enables toolkits that understand the
extension to engage it automatically, while toolkits that do not
yet understand a required extension can possibly bring it to the
attention of an operator for manual support.</p>
<p>If a Web service requires a client to follow a particular
convention that is likely to be automatable in WSDL 2.0 toolkits,
then that convention SHOULD be indicated in the WSDL 2.0 document
as a <code>wsdl:required</code> extension, rather than just being
conveyed out of band, even if that convention is not currently
implemented in WSDL 2.0 toolkits.</p>
<p>This practice will help prevent interoperability problems that
could arise if one toolkit requires a particular convention that is
not indicated in the WSDL 2.0 document, while another toolkit does
not realize that that convention is required. It will also help
facilitate future automatic processing by WSDL 2.0 toolkits.</p>
</div>
<p>On the other hand, a client MAY engage an extension that is
declared as optional in the WSDL 2.0 document. <span id=
"Extensibility-1091" class="test-assertion-tr">Therefore, the Web
service MUST support every extension that is declared as optional
in the WSDL 2.0 document, in addition to supporting every extension
that is declared as mandatory.<sup><a href=
"#Extensibility-1091-summary" title=
"Link to assertion Extensibility-1091 summary">†</a></sup></span></p>
<div class="note">
<p class="prefix"><strong>Note:</strong></p>
<p>If finer-grain, direction-sensitive control of extensions is
desired, then such extensions may be designed in a
direction-sensitive manner (from the client or from the Web
service) so that either direction may be separately marked required
or optional. For example, instead of defining a single extension
that governs both directions, two extensions could be defined -one
for each direction.</p>
</div>
<p>Validity of a WSDL 2.0 document can only be assessed within the
context of a set of supported extensions. A WSDL 2.0 document that
contains a required but unsupported extension is invalid with
respect to that set of supported extensions.</p>
</div>
<div class="div3">
<h4><a name="required-aii" id="required-aii"></a>6.1.2
<code>required</code> <em>attribute information item</em></h4>
<p>WSDL 2.0 provides a global <em>attribute information item</em>
with the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>required</code>.</p>
</li>
<li>
<p>A [namespace name] of "http://www.w3.org/ns/wsdl".</p>
</li>
</ul>
<p>The type of the <code>required</code> <em>attribute information
item</em> is <em>xs:boolean</em>. Its default value is "false"
(hence extensions are NOT required by default).</p>
</div>
</div>
<div class="div2">
<h3><a name="aii-extensibility" id="aii-extensibility"></a>6.2
Attribute-based Extensibility</h3>
<p>WSDL 2.0 allows qualified <em>attribute information item</em>s
whose [namespace name] is NOT "http://www.w3.org/ns/wsdl" to appear
on any <em>element information item</em> whose namespace name IS
"http://www.w3.org/ns/wsdl". Such <em>attribute information
item</em>s can be used to annotate WSDL 2.0 constructs such as
interfaces, bindings, etc.</p>
<p>WSDL 2.0 does not provide a mechanism for marking extension
<em>attribute information item</em>s as mandatory.</p>
</div>
<div class="div2">
<h3><a name="extensibility-semantics" id=
"extensibility-semantics"></a>6.3 Extensibility Semantics</h3>
<p>As indicated above, it is expected that the presence of
extension elements and attributes will result in additional
properties appearing in the component model.</p>
<p>The presence of an optional extension element or attribute MAY
therefore augment the semantics of a WSDL 2.0 document in ways that
do not invalidate the existing semantics. However, the presence of
a mandatory extension element MAY alter the semantics of a WSDL 2.0
document in ways that invalidate the existing semantics.</p>
<p>Extension elements SHOULD NOT alter the existing semantics in
ways that are likely to confuse users.</p>
<div class="note">
<p class="prefix"><strong>Note:</strong></p>
<p>Note that, however, once the client and service both know that
an optional extension has been engaged (because the service has
received a message explicitly engaging that extension, for
example), then the semantics of that extension supersede what the
WSDL 2.0 document indicated. For example, the WSDL 2.0 document may
have specified an XML message schema to be used, but also indicated
an optional security extension that encrypts the messages. If the
security extension is engaged, then the encrypted messages will no
longer conform to the specified message schema (until they are
decrypted).</p>
</div>
<div class="note">
<p class="prefix"><strong>Note:</strong></p>
<p>Authors of extension elements should make sure to include in the
specification of these elements a clear statement of the
requirements for document conformance (see <a href=
"#markup"><strong>1.3 Document Conformance</strong></a>).</p>
</div>
<div class="note">
<p class="prefix"><strong>Note:</strong></p>
<p>Authors of extension elements that may manifest as properties of
the <a href="#component-Description">Description</a> component
should be aware of the impact of imports on their extensions, or of
their extensions on imports. It is not possible, within the
component model, to define extensions that have an effective scope
equal to the scope of a containing file. Extensions that modify the
behavior of the components contained in a description may therefore
unexpectedly modify the behavior of components in imported
descriptions as well, unless proper care is taken.</p>
</div>
</div>
</div>
<div class="div1">
<h2><a name="wsdllocation" id="wsdllocation"></a>7. Locating WSDL
2.0 Documents</h2>
<p>A <em>WSDL 2.0 document</em> is a <code>description</code>
<em>element information item</em> that is either the document root
of an XML document or an element within an XML document. The
<em>location</em> of a WSDL 2.0 MAY therefore be specified by an
IRI for an XML resource whose document root is a
<code>description</code> <em>element information item</em> or an
IRI-reference for a <code>description</code> <em>element
information item</em> within an XML resource.</p>
<p>As an XML vocabulary, WSDL 2.0 documents, WSDL2.0 document
fragments or QName references to WSDL 2.0 components MAY appear
within other XML documents. This specification defines a global
attribute, <code>wsdlLocation</code>, to help with QName resolution
(see <a href="#qnameres"><strong>2.17 QName
resolution</strong></a>). This attribute allows an element that
contains such references to be annotated to indicate where the WSDL
2.0 documents for one or more namespaces can be found. In
particular, this attribute is expected to be useful when using
service references in message exchanges.</p>
<p>The <code>wsdlLocation</code> global attribute is defined in the
namespace "http://www.w3.org/ns/wsdl-instance" (hereafter referred
to as "wsdli:wsdlLocation", for brevity). This attribute MAY appear
on any XML element which allows attributes from other namespaces to
occur. <span id="Location-1092" class="test-assertion-tr">It MUST
NOT appear on a <code>wsdl:description</code> element or any of its
children/descendants.<sup><a href="#Location-1092-summary" title=
"Link to assertion Location-1092 summary">†</a></sup></span></p>
<p>A normative XML Schema [<cite><a href="#XMLSchemaP1">XML Schema:
Structures</a></cite>], [<cite><a href="#XMLSchemaP2">XML Schema:
Datatypes</a></cite>] document for the
"http://www.w3.org/ns/wsdl-instance" namespace can be found at
<a href=
"http://www.w3.org/ns/wsdl-instance">http://www.w3.org/ns/wsdl-instance</a>.</p>
<div class="div2">
<h3><a name="wsdlLocation-aii" id="wsdlLocation-aii"></a>7.1
<code>wsdli:wsdlLocation</code> <em>attribute information
item</em></h3>
<p>WSDL 2.0 provides a global <em>attribute information item</em>
with the following Infoset properties:</p>
<ul>
<li>
<p>A [local name] of <code>wsdlLocation</code>.</p>
</li>
<li>
<p>A [namespace name] of "http://www.w3.org/ns/wsdl-instance".</p>
</li>
</ul>
<p>The type of the <code>wsdlLocation</code> <em>attribute
information item</em> is a list <em>xs:anyURI</em>. <span id=
"Location-1093" class="test-assertion-tr">Its actual value MUST be
a list of pairs of IRIs; where the first IRI of a pair, which MUST
be an absolute IRI as defined in [<cite><a href="#RFC3987">IETF RFC
3987</a></cite>], indicates a WSDL 2.0 (or 1.1) namespace name,
and, the second a hint as to the location of a WSDL 2.0 document
defining WSDL 2.0 components (or WSDL 1.1 elements [<cite><a href=
"#WSDL11">WSDL 1.1</a></cite>]) for that namespace
name.<sup><a href="#Location-1093-summary" title=
"Link to assertion Location-1093 summary">†</a></sup></span> The
second IRI of a pair MAY be absolute or relative. <span id=
"Location-1094" class="test-assertion-tr">For each pair of IRIs, if
the location IRI of the pair is dereferencable, then it MUST
reference a WSDL 2.0 (or 1.1) document whose target namespace is
the namespace IRI of the pair.<sup><a href="#Location-1094-summary"
title=
"Link to assertion Location-1094 summary">†</a></sup></span></p>
</div>
</div>
<div class="div1">
<h2><a name="conformance" id="conformance"></a>8. Conformance</h2>
<p>This section describes how this specification conforms to other
specifications. This is limited, at present, to the XML Information
Set specification. Refer to <a href="#markup"><strong>1.3 Document
Conformance</strong></a> for a description of the criteria that Web
service description documents must satisfy in order to conform to
this specification.</p>
<div class="div2">
<h3><a name="infoset" id="infoset"></a>8.1 XML Information Set
Conformance</h3>
<p>This specification conforms to the [<cite><a href=
"#XMLInfoSet">XML Information Set</a></cite>]. The following
information items MUST be present in the input Infosets to enable
correct processing of WSDL 2.0 documents:</p>
<ul>
<li>
<p><em>Document Information Items</em> with [<em>children</em>] and
[<em>base URI</em>] properties.</p>
</li>
<li>
<p><em>Element Information Items</em> with [<em>namespace
name</em>], [<em>local name</em>], [<em>children</em>],
[<em>attributes</em>], [<em>base URI</em>] and [<em>parent</em>]
properties.</p>
</li>
<li>
<p><em>Attribute Information Items</em> with [<em>namespace
name</em>], [<em>local name</em>] and [<em>normalized value</em>]
properties.</p>
</li>
<li>
<p><em>Character Information Items</em> with [<em>character
code</em>], [<em>element content whitespace</em>] and
[<em>parent</em>] properties.</p>
</li>
</ul>
</div>
</div>
<div class="div1">
<h2><a name="Syntax-Summary" id="Syntax-Summary"></a>9. XML Syntax
Summary (Non-Normative)</h2>
<div class="exampleInner">
<pre xml:space="preserve">
&lt;description targetNamespace="<em>xs:anyURI</em>" &gt;
  &lt;documentation /&gt;*

  &lt;import namespace="<em>xs:anyURI</em>" location="<em>xs:anyURI</em>"? &gt;
    &lt;documentation /&gt;*
  &lt;/import&gt;*

  &lt;include location="<em>xs:anyURI</em>" &gt;
    &lt;documentation /&gt;*
  &lt;/include&gt;*

  &lt;types&gt;
    &lt;documentation /&gt;*
    
      [ &lt;xs:import namespace="<em>xs:anyURI</em>" schemaLocation="<em>xs:anyURI</em>"? /&gt; |
        &lt;xs:schema targetNamespace="<em>xs:anyURI</em>"? /&gt; |
        <em>other extension elements</em> ]*
  &lt;/types&gt;

  &lt;interface name="<em>xs:NCName</em>" extends="<em>list of xs:QName</em>"? styleDefault="<em>list of xs:anyURI</em>"? &gt;
    &lt;documentation /&gt;*

    &lt;fault name="<em>xs:NCName</em>" element="<em>union of xs:QName, xs:token</em>"? &gt;
      &lt;documentation /&gt;*
    &lt;/fault&gt;*

    &lt;operation name="<em>xs:NCName</em>" pattern="<em>xs:anyURI</em>"? style="<em>list of xs:anyURI</em>"? &gt;
      &lt;documentation /&gt;*

      &lt;input messageLabel="<em>xs:NCName</em>"? element="<em>union of xs:QName, xs:token</em>"? &gt;
        &lt;documentation /&gt;*
      &lt;/input&gt;*

      &lt;output messageLabel="<em>xs:NCName</em>"? element="<em>union of xs:QName, xs:token</em>"? &gt;
        &lt;documentation /&gt;*

      &lt;/output&gt;*

      &lt;infault ref="<em>xs:QName</em>" messageLabel="<em>xs:NCName</em>"? &gt;
        &lt;documentation /&gt;*
      &lt;/infault&gt;*

      &lt;outfault ref="<em>xs:QName</em>" messageLabel="<em>xs:NCName</em>"? &gt;
        &lt;documentation /&gt;*
      &lt;/outfault&gt;*

    &lt;/operation&gt;*

  &lt;/interface&gt;*

  &lt;binding name="<em>xs:NCName</em>" interface="<em>xs:QName</em>"? type="<em>xs:anyURI</em>" &gt;
    &lt;documentation /&gt;*

    &lt;fault ref="<em>xs:QName</em>" &gt;
      &lt;documentation /&gt;*
    &lt;/fault&gt;*

    &lt;operation ref="<em>xs:QName</em>" &gt;
      &lt;documentation /&gt;*

      &lt;input messageLabel="<em>xs:NCName</em>"? &gt;
        &lt;documentation /&gt;*
      &lt;/input&gt;*

      &lt;output messageLabel="<em>xs:NCName</em>"? &gt;
        &lt;documentation /&gt;*
      &lt;/output&gt;*

      &lt;infault ref="<em>xs:QName</em>" messageLabel="<em>xs:NCName</em>"? &gt;
        &lt;documentation /&gt;*
      &lt;/infault&gt;*

      &lt;outfault ref="<em>xs:QName</em>" messageLabel="<em>xs:NCName</em>"? &gt;
        &lt;documentation /&gt;*
      &lt;/outfault&gt;*

    &lt;/operation&gt;*

  &lt;/binding&gt;*

  &lt;service name="<em>xs:NCName</em>" interface="<em>xs:QName</em>" &gt;
    &lt;documentation /&gt;*

    &lt;endpoint name="<em>xs:NCName</em>" binding="<em>xs:QName</em>" address="<em>xs:anyURI</em>"? &gt;
      &lt;documentation /&gt;*
    &lt;/endpoint&gt;+

  &lt;/service&gt;*
&lt;/description&gt;
</pre></div>
</div>
<div class="div1">
<h2><a name="References" id="References"></a>10. References</h2>
<div class="div2">
<h3><a name="Normative-References" id=
"Normative-References"></a>10.1 Normative References</h3>
<dl>
<dt class="label"><a name="CHARMOD" id="CHARMOD"></a>[Character
Model for the WWW]</dt>
<dd><cite><a href=
"http://www.w3.org/TR/2005/REC-charmod-20050215/">Character Model
for the World Wide Web 1.0: Fundamentals</a></cite>, M. Dürst, F.
Yergeau, R. Ishida, M. Wolf, T. Texin, Editors. W3C Recommendation,
15 February 2005. Latest version available at
http://www.w3.org/TR/charmod/.</dd>
<dt class="label"><a name="RFC2119" id="RFC2119"></a>[IETF RFC
2119]</dt>
<dd><cite><a href="http://www.ietf.org/rfc/rfc2119.txt">Key words
for use in RFCs to Indicate Requirement Levels</a></cite>, S.
Bradner, Author. Internet Engineering Task Force, March 1997.
Available at http://www.ietf.org/rfc/rfc2119.txt.</dd>
<dt class="label"><a name="RFC3023" id="RFC3023"></a>[IETF RFC
3023]</dt>
<dd><cite><a href="http://www.ietf.org/rfc/rfc3023.txt">XML Media
Types</a></cite>, M. Murata, S. St. Laurent, D. Kohn, Authors.
Internet Engineering Task Force, January 2001. Available at
http://www.ietf.org/rfc/rfc3023.txt.</dd>
<dt class="label"><a name="RFC3986" id="RFC3986"></a>[IETF RFC
3986]</dt>
<dd><cite><a href="http://www.ietf.org/rfc/rfc3986.txt">Uniform
Resource Identifiers (URI): Generic Syntax</a></cite>, T.
Berners-Lee, R. Fielding, L. Masinter, Authors. Internet
Engineering Task Force, January 2005. Available at
http://www.ietf.org/rfc/rfc3986.txt.</dd>
<dt class="label"><a name="RFC3987" id="RFC3987"></a>[IETF RFC
3987]</dt>
<dd><cite><a href=
"http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource
Identifiers (IRIs)</a></cite>, M. Duerst, M. Suignard, Authors.
Internet Engineering Task Force, January 2005. Available at
http://www.ietf.org/rfc/rfc3987.txt.</dd>
<dt class="label"><a name="XLink" id="XLink"></a>[XLink 1.0]</dt>
<dd><cite><a href=
"http://www.w3.org/TR/2001/REC-xlink-20010627/">XML Linking
Language (XLink) Version 1.0</a></cite>, Steve DeRose, Eve Maler,
David Orchard, Editors. World Wide Web Consortium, 27 June 2001.
This version of the XLink Recommendation is
http://www.w3.org/TR/2001/REC-xlink-20010627/ The <a href=
"http://www.w3.org/TR/xlink/">latest version of XLink</a> is
available at http://www.w3.org/TR/xlink/.</dd>
<dt class="label"><a name="XML10" id="XML10"></a>[XML 1.0]</dt>
<dd><cite><a href=
"http://www.w3.org/TR/2006/REC-xml-20060816/">Extensible Markup
Language (XML) 1.0 (Fourth Edition)</a></cite>, T. Bray, J. Paoli,
C. M. Sperberg-McQueen, E. Maler, and F. Yergeau, Editors. World
Wide Web Consortium, 10 February 1998, revised 16 August 2006. This
version of the XML 1.0 Recommendation is
http://www.w3.org/TR/2006/REC-xml-20060816/. The <a href=
"http://www.w3.org/TR/REC-xml">latest version of "Extensible Markup
Language (XML) 1.0"</a> is available at
http://www.w3.org/TR/REC-xml.</dd>
<dt class="label"><a name="XMLNS" id="XMLNS"></a>[XML
Namespaces]</dt>
<dd><cite><a href=
"http://www.w3.org/TR/2006/REC-xml-names-20060816">Namespaces in
XML (Second Edition)</a></cite>, T. Bray, D. Hollander, A. Layman,
and R. Tobin, Editors. World Wide Web Consortium, 16 August 2006.
This version of the XML Information Set Recommendation is
http://www.w3.org/TR/2006/REC-xml-names-20060816. The <a href=
"http://www.w3.org/TR/REC-xml-names">latest version of Namespaces
in XML</a> is available at http://www.w3.org/TR/REC-xml-names.</dd>
<dt class="label"><a name="XMLInfoSet" id="XMLInfoSet"></a>[XML
Information Set]</dt>
<dd><cite><a href=
"http://www.w3.org/TR/2004/REC-xml-infoset-20040204">XML
Information Set (Second Edition)</a></cite>, J. Cowan and R. Tobin,
Editors. World Wide Web Consortium, 24 October 2001, revised 4
February 2004. This version of the XML Information Set
Recommendation is
http://www.w3.org/TR/2004/REC-xml-infoset-20040204. The <a href=
"http://www.w3.org/TR/xml-infoset">latest version of XML
Information Set</a> is available at
http://www.w3.org/TR/xml-infoset.</dd>
<dt class="label"><a name="XMLSchemaP1" id="XMLSchemaP1"></a>[XML
Schema: Structures]</dt>
<dd><cite><a href=
"http://www.w3.org/TR/2004/REC-xmlschema-1-20041028/">XML Schema
Part 1: Structures Second Edition</a></cite>, H. Thompson, D.
Beech, M. Maloney, and N. Mendelsohn, Editors. World Wide Web
Consortium, 2 May 2001, revised 28 October 2004. This version of
the XML Schema Part 1 Recommendation is
http://www.w3.org/TR/2004/REC-xmlschema-1-20041028. The <a href=
"http://www.w3.org/TR/xmlschema-1/">latest version of XML Schema
Part 1</a> is available at http://www.w3.org/TR/xmlschema-1.</dd>
<dt class="label"><a name="XMLSchemaP2" id="XMLSchemaP2"></a>[XML
Schema: Datatypes]</dt>
<dd><cite><a href=
"http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/">XML Schema
Part 2: Datatypes Second Edition</a></cite>, P. Byron and A.
Malhotra, Editors. World Wide Web Consortium, 2 May 2001, revised
28 October 2004. This version of the XML Schema Part 2
Recommendation is
http://www.w3.org/TR/2004/REC-xmlschema-2-20041028. The <a href=
"http://www.w3.org/TR/xmlschema-2/">latest version of XML Schema
Part 2</a> is available at http://www.w3.org/TR/xmlschema-2.</dd>
<dt class="label"><a name="WSDL-PART2" id="WSDL-PART2"></a>[WSDL
2.0 Adjuncts]</dt>
<dd><cite><a href=
"http://www.w3.org/TR/2007/REC-wsdl20-adjuncts-20070626">Web
Services Description Language (WSDL) Version 2.0 Part 2:
Adjuncts</a></cite> , R. Chinnici, H. Haas, A. Lewis, J-J. Moreau,
D. Orchard, S. Weerawarana, Editors. World Wide Web Consortium, 26
June 2007. This version of the "Web Services Description Language
(WSDL) Version 2.0 Part 2: Adjuncts" Recommendation is available at
http://www.w3.org/TR/2007/REC-wsdl20-adjuncts-20070626. The
<a href="http://www.w3.org/TR/wsdl20-adjuncts">latest version of
"Web Services Description Language (WSDL) Version 2.0 Part 2:
Adjuncts"</a> is available at
http://www.w3.org/TR/wsdl20-adjuncts.</dd>
</dl>
</div>
<div class="div2">
<h3><a name="Informative-References" id=
"Informative-References"></a>10.2 Informative References</h3>
<dl>
<dt class="label"><a name="RFC2045" id="RFC2045"></a>[IETF RFC
2045]</dt>
<dd><cite><a href=
"http://www.ietf.org/rfc/rfc2045.txt">Multipurpose Internet Mail
Extensions (MIME) Part One: Format of Internet Message
Bodies</a></cite>, N. Freed, N. Borenstein, Authors. Internet
Engineering Task Force, November 1996. Available at
http://www.ietf.org/rfc/rfc2045.txt.</dd>
<dt class="label"><a name="RFC2616" id="RFC2616"></a>[IETF RFC
2616]</dt>
<dd><cite><a href="http://www.ietf.org/rfc/rfc2616.txt">Hypertext
Transfer Protocol -- HTTP/1.1</a></cite>, R. Fielding, J. Gettys,
J. Mogul, H. Frystyk, L. Masinter, P. Leach, T. Berners-Lee,
Authors. Internet Engineering Task Force, June 1999. Available at
http://www.ietf.org/rfc/rfc2616.txt.</dd>
<dt class="label"><a name="WSA-Core" id="WSA-Core"></a>[WSA 1.0
Core]</dt>
<dd><cite><a href=
"http://www.w3.org/TR/2006/REC-ws-addr-core-20060509/">Web Services
Addressing 1.0 - Core</a></cite> , M. Gudgin, M. Hadley, T. Rogers,
Editors. World Wide Web Consortium, 9 May 2006. This version of Web
Services Addressing 1.0 - Core Recommendation is
http://www.w3.org/TR/2006/REC-ws-addr-core-20060509/ The latest
version of the "Web Services Addressing 1.0 - Core" document is
available from http://www.w3.org/TR/ws-addr-core.</dd>
<dt class="label"><a name="WSDL11" id="WSDL11"></a>[WSDL 1.1]</dt>
<dd><cite><a href=
"http://www.w3.org/TR/2001/NOTE-wsdl-20010315">Web Services
Description Language (WSDL) 1.1</a></cite>, E. Christensen, F.
Curbera, G. Meredith, and S. Weerawarana, Authors. World Wide Web
Consortium, 15 March 2002. This version of the Web Services
Description Language 1.1 Note is
http://www.w3.org/TR/2001/NOTE-wsdl-20010315. The <a href=
"http://www.w3.org/TR/wsdl">latest version of Web Services
Description Language 1.1</a> is available at
http://www.w3.org/TR/wsdl.</dd>
<dt class="label"><a name="WSDL-PART0" id="WSDL-PART0"></a>[WSDL
2.0 Primer]</dt>
<dd><cite><a href=
"http://www.w3.org/TR/2007/REC-wsdl20-primer-20070626">Web Services
Description Language (WSDL) Version 2.0 Part 0: Primer</a></cite> ,
D.Booth, C.K. Liu , Editors. World Wide Web Consortium, 26 June
2007. This version of the "Web Services Description Language (WSDL)
Version 2.0 Part 0: Primer" Recommendation is available at
http://www.w3.org/TR/2007/REC-wsdl20-primer-20070626. The <a href=
"http://www.w3.org/TR/wsdl20-primer">latest version of "Web
Services Description Language (WSDL) Version 2.0 Part 0:
Primer"</a> is available at
http://www.w3.org/TR/wsdl20-primer.</dd>
<dt class="label"><a name="WSDReqs" id="WSDReqs"></a>[WSDL 2.0
Requirements]</dt>
<dd><cite><a href=
"http://www.w3.org/TR/2002/WD-ws-desc-reqs-20021028">Web Services
Description Requirements</a></cite>, J. Schlimmer, Editor. World
Wide Web Consortium, 28 October 2002. This version of the Web
Services Description Requirements document is
http://www.w3.org/TR/2002/WD-ws-desc-reqs-20021028. The <a href=
"http://www.w3.org/TR/ws-desc-reqs/">latest version of Web Services
Description Requirements</a> is available at
http://www.w3.org/TR/ws-desc-reqs.</dd>
<dt class="label"><a name="WSDL2-OTHER-SCHEMA" id=
"WSDL2-OTHER-SCHEMA"></a>[WSDL 2.0 Alternative Schema Languages
Support]</dt>
<dd><cite><a href=
"http://www.w3.org/TR/2005/NOTE-wsdl20-altschemalangs-20050817/">Discussion
of Alternative Schema Languages and Type System Support in WSDL
2.0</a></cite>, A. Lewis, B. Parsia, Editors. World Wide Web
Consortium, 17 August 2005. This version of the "Discussion of
Alternative Schema Languages and Type System Support in WSDL 2.0"
Working Group Note is
http://www.w3.org/TR/2005/NOTE-wsdl20-altschemalangs-20050817/. The
<a href="http://www.w3.org/TR/wsdl20-altschemalangs">latest version
of "Discussion of Alternative Schema Languages and Type System
Support in WSDL 2.0"</a> is available at
http://www.w3.org/TR/wsdl20-altschemalangs.</dd>
<dt class="label"><a name="SOAP12-PART1" id=
"SOAP12-PART1"></a>[SOAP 1.2 Part 1: Messaging Framework (Second
Edition)]</dt>
<dd><cite><a href=
"http://www.w3.org/TR/2007/REC-soap12-part1-20070427/">SOAP Version
1.2 Part 1: Messaging Framework (Second Edition)</a></cite>, M.
Gudgin, et al., Editors. World Wide Web Consortium, 24 June 2003,
revised 27 April 2007. This version of the "SOAP Version 1.2 Part
1: Messaging Framework (Second Edition)" Recommendation is
http://www.w3.org/TR/2007/REC-soap12-part1-20070427/. The <a href=
"http://www.w3.org/TR/soap12-part1/">latest version of "SOAP
Version 1.2 Part 1: Messaging Framework"</a> is available at
http://www.w3.org/TR/soap12-part1/.</dd>
<dt class="label"><a name="XPTR" id="XPTR"></a>[XPointer]</dt>
<dd><cite><a href=
"http://www.w3.org/TR/2003/REC-xptr-framework-20030325/">XPointer
Framework</a></cite>, P. Grosso, E. Maler, J. Marsh, N. Walsh,
Editors. World Wide Web Consortium, 25 March 2003. This version of
the XPointer Framework Recommendation is
http://www.w3.org/TR/2003/REC-xptr-framework-20030325/ The <a href=
"http://www.w3.org/TR/xptr-framework/">latest version of XPointer
Framework</a> is available at
http://www.w3.org/TR/xptr-framework/.</dd>
<dt class="label"><a name="ZNotationReferenceManual" id=
"ZNotationReferenceManual"></a>[Z Notation Reference Manual]</dt>
<dd><cite><a href=
"http://spivey.oriel.ox.ac.uk/mike/zrm/index.html">The Z Notation:
A Reference Manual, Second Edition</a></cite>, J. M. Spivey,
Prentice Hall, 1992.</dd>
<dt class="label"><a name="Fuzz2000" id="Fuzz2000"></a>[Fuzz
2000]</dt>
<dd><cite><a href="http://spivey.oriel.ox.ac.uk/mike/fuzz/">Release
Notes For Fuzz 2000</a></cite>, J. M. Spivey.</dd>
</dl>
</div>
</div>
</div>
<div class="back">
<div class="div1">
<h2><a name="ietf-draft" id="ietf-draft"></a>A. The
application/wsdl+xml Media Type</h2>
<p>This appendix defines the "application/wsdl+xml" media type
which can be used to describe WSDL 2.0 documents serialized as
XML.</p>
<div class="div2">
<h3><a name="ietf-reg" id="ietf-reg"></a>A.1 Registration</h3>
<dl>
<dt class="label">MIME media type name:</dt>
<dd>
<p>application</p>
</dd>
<dt class="label">MIME subtype name:</dt>
<dd>
<p>wsdl+xml</p>
</dd>
<dt class="label">Required parameters:</dt>
<dd>
<p>none</p>
</dd>
<dt class="label">Optional parameters:</dt>
<dd>
<dl>
<dt class="label">charset</dt>
<dd>
<p>This parameter has identical semantics to the charset parameter
of the "application/xml" media type as specified in [<cite><a href=
"#RFC3023">IETF RFC 3023</a></cite>].</p>
</dd>
</dl>
</dd>
<dt class="label">Encoding considerations:</dt>
<dd>
<p>Identical to those of "application/xml" as described in
[<cite><a href="#RFC3023">IETF RFC 3023</a></cite>], section 3.2,
as applied to the WSDL document Infoset.</p>
</dd>
<dt class="label">Security considerations:</dt>
<dd>
<p>See section <a href="#ietf-sec"><strong>A.3 Security
considerations</strong></a>.</p>
</dd>
<dt class="label">Interoperability considerations:</dt>
<dd>
<p>There are no known interoperability issues.</p>
</dd>
<dt class="label">Published specifications:</dt>
<dd>
<p>This document and [<cite><a href="#WSDL-PART2">WSDL 2.0
Adjuncts</a></cite>].</p>
</dd>
<dt class="label">Applications which use this media type:</dt>
<dd>
<p>No known applications currently use this media type.</p>
</dd>
<dt class="label">Additional information:</dt>
<dd>
<dl>
<dt class="label">File extension:</dt>
<dd>
<p>wsdl</p>
</dd>
<dt class="label">Fragment identifiers:</dt>
<dd>
<p>Either a syntax identical to that of "application/xml" as
described in [<cite><a href="#RFC3023">IETF RFC 3023</a></cite>],
section 5 or the syntax defined in <a href="#frag-ids"><strong>A.2
Fragment Identifiers</strong></a>.</p>
</dd>
<dt class="label">Base URI:</dt>
<dd>
<p>As specified in [<cite><a href="#RFC3023">IETF RFC
3023</a></cite>], section 6.</p>
</dd>
<dt class="label">Macintosh File Type code:</dt>
<dd>
<p>WSDL</p>
</dd>
</dl>
</dd>
<dt class="label">Person and email address to contact for further
information:</dt>
<dd>
<p>World Wide Web Consortium &lt;web-human@w3.org&gt;</p>
</dd>
<dt class="label">Intended usage:</dt>
<dd>
<p>COMMON</p>
</dd>
<dt class="label">Author/Change controller:</dt>
<dd>
<p>The WSDL 2.0 specification set is a work product of the World
Wide Web Consortium's <a href="http://www.w3.org/2002/ws/desc/">Web
Service Description Working Group</a>. The W3C has change control
over these specifications.</p>
</dd>
</dl>
</div>
<div class="div2">
<h3><a name="frag-ids" id="frag-ids"></a>A.2 Fragment
Identifiers</h3>
<p>This section defines a fragment identifier syntax for
identifying components of a WSDL 2.0 document. This fragment
identifier syntax is compliant with the [<cite><a href=
"#XPTR">XPointer</a></cite>].</p>
<p>A WSDL 2.0 fragment identifier is an XPointer [<cite><a href=
"#XPTR">XPointer</a></cite>], augmented with WSDL 2.0 pointer parts
as defined below. Note that many of these parts require the
pre-appearance of one or more <code>xmlns</code> pointer parts (see
<em>3.4 Namespace Binding Context</em> in [<cite><a href=
"#XPTR">XPointer</a></cite>]). The pointer parts have a scheme name
that corresponds to one of the standard WSDL 2.0 component types,
and scheme data that is a path composed of names that identify the
components. The scheme names all begin with the prefix "wsdl." to
avoid name conflicts with other schemes. The names in the path are
of type either QName, NCName, IRI, URI, or Pointer Part depending
on the context. The scheme data for WSDL 2.0 extension components
is defined by the corresponding extension specification.</p>
<p><span id="FragId-1095" class="test-assertion-tr">For QNames, any
prefix MUST be defined by a preceding xmlns pointer
part.<sup><a href="#FragId-1095-summary" title=
"Link to assertion FragId-1095 summary">†</a></sup></span> If a
QName does not have a prefix then its namespace name is the target
namespace of the WSDL 2.0 document.</p>
<p>The fragment identifier is typically constructed from the
{<a href="#property-.name">name</a>} property of the component and
the {<a href="#property-.name">name</a>} properties of its
ancestors as a path according to <a href="#frag-ids-table">Table
A-1</a>. The first column of this table gives the name of the WSDL
2.0 component. Columns labeled 1 through 4 specify the identifiers
that uniquely identify the component within its context.
Identifiers are typically formed from the {<a href=
"#property-.name">name</a>} property, although in several cases
references to other components are used. These identifiers are then
used to construct the pointer part in the last column. <span id=
"FragId-1096" class="test-assertion-tr">The fragment identifier in
a WSDL 2.0 component IRI-reference MUST resolve to some component
as defined by the construction rules in <a href=
"#frag-ids-table">Table A-1</a>.<sup><a href="#FragId-1096-summary"
title=
"Link to assertion FragId-1096 summary">†</a></sup></span></p>
<a name="frag-ids-table" id="frag-ids-table"></a>
<table border="1">
<caption>Table A-1. Rules for determining pointer parts for WSDL
2.0 components</caption>
<col width="15%" span="1" />
<col width="10%" span="1" />
<col width="10%" span="1" />
<col width="10%" span="1" />
<col width="10%" span="1" />
<col width="45%" span="1" />
<tbody>
<tr>
<th rowspan="1" colspan="1">Component</th>
<th rowspan="1" colspan="1">1</th>
<th rowspan="1" colspan="1">2</th>
<th rowspan="1" colspan="1">3</th>
<th rowspan="1" colspan="1">4</th>
<th rowspan="1" colspan="1">Pointer Part</th>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-Description">Description</a></td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1"><code><a href=
"#wsdl.description">wsdl.description</a>()</code></td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-ElementDeclaration">Element Declaration</a></td>
<td rowspan="1" colspan="1"><code><em>element</em></code>
QName</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1"><code><a href=
"#wsdl.elementDeclaration">wsdl.elementDeclaration</a>(<em>element</em>)</code></td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-ElementDeclaration">Element Declaration</a></td>
<td rowspan="1" colspan="1"><code><em>element</em></code>
QName</td>
<td rowspan="1" colspan="1"><code><em>system</em></code> IRI</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1"><code><a href=
"#wsdl.elementDeclaration">wsdl.elementDeclaration</a>(<em>element</em>,<em>system</em>)</code></td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-TypeDefinition">Type Definition</a></td>
<td rowspan="1" colspan="1"><code><em>type</em></code> QName</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1"><code><a href=
"#wsdl.typeDefinition">wsdl.typeDefinition</a>(<em>type</em>)</code></td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-TypeDefinition">Type Definition</a></td>
<td rowspan="1" colspan="1"><code><em>type</em></code> QName</td>
<td rowspan="1" colspan="1"><code><em>system</em></code> IRI</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1"><code><a href=
"#wsdl.typeDefinition">wsdl.typeDefinition</a>(<em>type</em>,<em>system</em>)</code></td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-Interface">Interface</a></td>
<td rowspan="1" colspan="1"><code><em>interface</em></code>
NCName</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1"><code><a href=
"#wsdl.interface">wsdl.interface</a>(<em>interface</em>)</code></td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-InterfaceFault">Interface Fault</a></td>
<td rowspan="1" colspan="1"><code><em>interface</em></code>
NCName</td>
<td rowspan="1" colspan="1"><code><em>fault</em></code> NCName</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1"><code><a href=
"#wsdl.interfaceFault">wsdl.interfaceFault</a>(<em>interface</em>/<em>fault</em>)</code></td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-InterfaceOperation">Interface Operation</a></td>
<td rowspan="1" colspan="1"><code><em>interface</em></code>
NCName</td>
<td rowspan="1" colspan="1"><code><em>operation</em></code>
NCName</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1"><code><a href=
"#wsdl.interfaceOperation">wsdl.interfaceOperation</a>(<em>interface</em>/<em>operation</em>)</code></td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-InterfaceMessageReference">Interface Message
Reference</a></td>
<td rowspan="1" colspan="1"><code><em>interface</em></code>
NCName</td>
<td rowspan="1" colspan="1"><code><em>operation</em></code>
NCName</td>
<td rowspan="1" colspan="1"><code><em>message</em></code>
NCName</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1"><code><a href=
"#wsdl.interfaceMessageReference">wsdl.interfaceMessageReference</a>(<em>interface</em>/<em>operation</em>/<em>message</em>)</code></td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-InterfaceFaultReference">Interface Fault
Reference</a></td>
<td rowspan="1" colspan="1"><code><em>interface</em></code>
NCName</td>
<td rowspan="1" colspan="1"><code><em>operation</em></code>
NCName</td>
<td rowspan="1" colspan="1"><code><em>message</em></code>
NCName</td>
<td rowspan="1" colspan="1"><code><em>fault</em></code> QName</td>
<td rowspan="1" colspan="1"><code><a href=
"#wsdl.interfaceFaultReference">wsdl.interfaceFaultReference</a>(<em>interface</em>/<em>operation</em>/<em>message</em>/<em>fault</em>)</code></td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-Binding">Binding</a></td>
<td rowspan="1" colspan="1"><code><em>binding</em></code>
NCName</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1"><code><a href=
"#wsdl.binding">wsdl.binding</a>(<em>binding</em>)</code></td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-BindingFault">Binding Fault</a></td>
<td rowspan="1" colspan="1"><code><em>binding</em></code>
NCName</td>
<td rowspan="1" colspan="1"><code><em>fault</em></code> QName</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1"><code><a href=
"#wsdl.bindingFault">wsdl.bindingFault</a>(<em>binding</em>/<em>fault</em>)</code></td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-BindingOperation">Binding Operation</a></td>
<td rowspan="1" colspan="1"><code><em>binding</em></code>
NCName</td>
<td rowspan="1" colspan="1"><code><em>operation</em></code>
QName</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1"><code><a href=
"#wsdl.bindingOperation">wsdl.bindingOperation</a>(<em>binding</em>/<em>operation</em>)</code></td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-BindingMessageReference">Binding Message
Reference</a></td>
<td rowspan="1" colspan="1"><code><em>binding</em></code>
NCName</td>
<td rowspan="1" colspan="1"><code><em>operation</em></code>
QName</td>
<td rowspan="1" colspan="1"><code><em>message</em></code>
NCName</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1"><code><a href=
"#wsdl.bindingMessageReference">wsdl.bindingMessageReference</a>(<em>binding</em>/<em>operation</em>/<em>message</em>)</code></td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-BindingFaultReference">Binding Fault Reference</a></td>
<td rowspan="1" colspan="1"><code><em>binding</em></code>
NCName</td>
<td rowspan="1" colspan="1"><code><em>operation</em></code>
QName</td>
<td rowspan="1" colspan="1"><code><em>message</em></code>
NCName</td>
<td rowspan="1" colspan="1"><code><em>fault</em></code> QName</td>
<td rowspan="1" colspan="1"><code><a href=
"#wsdl.bindingFaultReference">wsdl.bindingFaultReference</a>(<em>binding</em>/<em>operation</em>/<em>message</em>/<em>fault</em>)</code></td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-Service">Service</a></td>
<td rowspan="1" colspan="1"><code><em>service</em></code>
NCName</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1"><code><a href=
"#wsdl.service">wsdl.service</a>(<em>service</em>)</code></td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-Endpoint">Endpoint</a></td>
<td rowspan="1" colspan="1"><code><em>service</em></code>
NCName</td>
<td rowspan="1" colspan="1"><code><em>endpoint</em></code>
NCName</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1"><code><a href=
"#wsdl.endpoint">wsdl.endpoint</a>(<em>service</em>/<em>endpoint</em>)</code></td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#Description">Extensions</a></td>
<td rowspan="1" colspan="1"><code><em>namespace</em></code>
URI</td>
<td rowspan="1" colspan="1"><code><em>identifier</em></code>
extension-specific-syntax</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1">n/a</td>
<td rowspan="1" colspan="1"><code><a href=
"#wsdl.extension">wsdl.extension</a>(<em>namespace</em>,<em>identifier</em>)</code></td>
</tr>
</tbody>
</table>

<br />
<p>Note that the above rules are defined in terms of component
properties rather than the XML Infoset representation of the
component model. The following sections specify in detail how the
pointer parts are constructed from the component model.</p>
<a name="zed-ComponentID" id="zed-ComponentID"></a><a name=
"zed-ComponentDesignator" id="zed-ComponentDesignator"></a><a name=
"zed-ComponentContext" id="zed-ComponentContext"></a><a name=
"zed-componentNamespace" id="zed-componentNamespace"></a><a name=
"zed-ExtensionIdentifier" id="zed-ExtensionIdentifier"></a><a name=
"zed-wsdlPointerPart" id="zed-wsdlPointerPart"></a><a name=
"zed-pointerPart" id="zed-pointerPart"></a><a name=
"zed-ComponentToDesignator" id="zed-ComponentToDesignator"></a>
<div class="div3">
<h4><a name="wsdl.description" id="wsdl.description"></a>A.2.1 The
Description Component</h4>
<p><code>wsdl.description()</code></p>
<a name="zed-wsdlDescription" id="zed-wsdlDescription"></a></div>
<div class="div3">
<h4><a name="wsdl.elementDeclaration" id=
"wsdl.elementDeclaration"></a>A.2.2 The Element Declaration
Component</h4>
<p><code>wsdl.elementDeclaration(<em>element</em>)</code></p>
<p>
<code>wsdl.elementDeclaration(<em>element</em>,<em>system</em>)</code></p>
<ol class="enumar">
<li>
<p><code><em>element</em></code> is the {<a href=
"#property-ElementDeclaration.name">name</a>} property of the
<a href="#component-ElementDeclaration">Element Declaration</a>
component.</p>
</li>
<li>
<p><code><em>system</em></code> is the namespace absolute IRI of
the extension type system used for the <a href=
"#component-ElementDeclaration">Element Declaration</a> component
(see <a href="#other-types"><strong>3.2 Using Other Schema
Languages</strong></a>). This parameter is absent if XML Schema is
the type system.</p>
</li>
</ol>
<a name="zed-xmlSchemaNamespaceURI" id=
"zed-xmlSchemaNamespaceURI"></a><a name="zed-ElementDeclArgs" id=
"zed-ElementDeclArgs"></a><a name="zed-ElementDeclDesignator" id=
"zed-ElementDeclDesignator"></a><a name=
"zed-wsdlElementDeclaration" id=
"zed-wsdlElementDeclaration"></a></div>
<div class="div3">
<h4><a name="wsdl.typeDefinition" id=
"wsdl.typeDefinition"></a>A.2.3 The Type Definition Component</h4>
<p><code>wsdl.typeDefinition(<em>type</em>)</code></p>
<p>
<code>wsdl.typeDefinition(<em>type</em>,<em>system</em>)</code></p>
<ol class="enumar">
<li>
<p><code><em>type</em></code> is the {<a href=
"#property-TypeDefinition.name">name</a>} property of the <a href=
"#component-TypeDefinition">Type Definition</a> component.</p>
</li>
<li>
<p><code><em>system</em></code> is the namespace absolute IRI of
the extension type system used for the <a href=
"#component-TypeDefinition">Type Definition</a> component (see
<a href="#other-types"><strong>3.2 Using Other Schema
Languages</strong></a>). This parameter is absent if XML Schema is
the type system.</p>
</li>
</ol>
<a name="zed-TypeDefArgs" id="zed-TypeDefArgs"></a><a name=
"zed-TypeDefDesignator" id="zed-TypeDefDesignator"></a><a name=
"zed-wsdlTypeDefinition" id="zed-wsdlTypeDefinition"></a></div>
<div class="div3">
<h4><a name="wsdl.interface" id="wsdl.interface"></a>A.2.4 The
Interface Component</h4>
<p><code>wsdl.interface(<em>interface</em>)</code></p>
<ol class="enumar">
<li>
<p><code><em>interface</em></code> is the local name of the
{<a href="#property-Interface.name">name</a>} property of the
<a href="#component-Interface">Interface</a> component.</p>
</li>
</ol>
<a name="zed-InterfaceArgs" id="zed-InterfaceArgs"></a><a name=
"zed-InterfaceDesignator" id="zed-InterfaceDesignator"></a><a name=
"zed-wsdlInterface" id="zed-wsdlInterface"></a></div>
<div class="div3">
<h4><a name="wsdl.interfaceFault" id=
"wsdl.interfaceFault"></a>A.2.5 The Interface Fault Component</h4>
<p>
<code>wsdl.interfaceFault(<em>interface</em>/<em>fault</em>)</code></p>
<ol class="enumar">
<li>
<p><code><em>interface</em></code> is the local name of the
{<a href="#property-Interface.name">name</a>} property of the
parent <a href="#component-Interface">Interface</a> component.</p>
</li>
<li>
<p><code><em>fault</em></code> is the local name of the {<a href=
"#property-InterfaceFault.name">name</a>} property of the <a href=
"#component-InterfaceFault">Interface Fault</a> component.</p>
</li>
</ol>
<a name="zed-InterfaceFaultArgs" id=
"zed-InterfaceFaultArgs"></a><a name="zed-InterfaceFaultDesignator"
id="zed-InterfaceFaultDesignator"></a><a name=
"zed-wsdlInterfaceFault" id="zed-wsdlInterfaceFault"></a></div>
<div class="div3">
<h4><a name="wsdl.interfaceOperation" id=
"wsdl.interfaceOperation"></a>A.2.6 The Interface Operation
Component</h4>
<p>
<code>wsdl.interfaceOperation(<em>interface</em>/<em>operation</em>)</code></p>
<ol class="enumar">
<li>
<p><code><em>interface</em></code> is the local name of the
{<a href="#property-Interface.name">name</a>} property of the
parent <a href="#component-Interface">Interface</a> component.</p>
</li>
<li>
<p><code><em>operation</em></code> is the local name of the
{<a href="#property-InterfaceOperation.name">name</a>} property of
the <a href="#component-InterfaceOperation">Interface Operation</a>
component.</p>
</li>
</ol>
<a name="zed-InterfaceOpArgs" id="zed-InterfaceOpArgs"></a><a name=
"zed-InterfaceOpDesignator" id=
"zed-InterfaceOpDesignator"></a><a name=
"zed-wsdlInterfaceOperation" id=
"zed-wsdlInterfaceOperation"></a></div>
<div class="div3">
<h4><a name="wsdl.interfaceMessageReference" id=
"wsdl.interfaceMessageReference"></a>A.2.7 The Interface Message
Reference Component</h4>
<p>
<code>wsdl.interfaceMessageReference(<em>interface</em>/<em>operation</em>/<em>message</em>)</code></p>
<ol class="enumar">
<li>
<p><code><em>interface</em></code> is the local name of the
{<a href="#property-Interface.name">name</a>} property of the
grandparent <a href="#component-Interface">Interface</a>
component.</p>
</li>
<li>
<p><code><em>operation</em></code> is the local name of the
{<a href="#property-InterfaceOperation.name">name</a>} property of
the parent <a href="#component-InterfaceOperation">Interface
Operation</a> component.</p>
</li>
<li>
<p><code><em>message</em></code> is the {<a href=
"#property-InterfaceMessageReference.messagelabel">message
label</a>} property of the <a href=
"#component-InterfaceMessageReference">Interface Message
Reference</a> component.</p>
</li>
</ol>
<a name="zed-InterfaceMessageRefArgs" id=
"zed-InterfaceMessageRefArgs"></a><a name=
"zed-InterfaceMessageRefDesignator" id=
"zed-InterfaceMessageRefDesignator"></a><a name=
"zed-wsdlInterfaceMessageReference" id=
"zed-wsdlInterfaceMessageReference"></a></div>
<div class="div3">
<h4><a name="wsdl.interfaceFaultReference" id=
"wsdl.interfaceFaultReference"></a>A.2.8 The Interface Fault
Reference Component</h4>
<p>
<code>wsdl.interfaceFaultReference(<em>interface</em>/<em>operation</em>/<em>message</em>/<em>fault</em>)</code></p>
<ol class="enumar">
<li>
<p><code><em>interface</em></code> is the local name of the
{<a href="#property-Interface.name">name</a>} property of the
grandparent <a href="#component-Interface">Interface</a>
component.</p>
</li>
<li>
<p><code><em>operation</em></code> is the local name of the
{<a href="#property-InterfaceOperation.name">name</a>} property of
the parent <a href="#component-InterfaceOperation">Interface
Operation</a> component.</p>
</li>
<li>
<p><code><em>message</em></code> is the {<a href=
"#property-InterfaceFaultReference.messagelabel">message label</a>}
property of the <a href=
"#component-InterfaceFaultReference">Interface Fault Reference</a>
component.</p>
</li>
<li>
<p><code><em>fault</em></code> is the {<a href=
"#property-InterfaceFault.name">name</a>} property of the <a href=
"#component-InterfaceFault">Interface Fault</a> component referred
to by the {<a href=
"#property-InterfaceFaultReference.interfacefault">interface
fault</a>} property of the <a href=
"#component-InterfaceFaultReference">Interface Fault Reference</a>
component.</p>
</li>
</ol>
<a name="zed-InterfaceFaultRefArgs" id=
"zed-InterfaceFaultRefArgs"></a><a name=
"zed-InterfaceFaultRefDesignator" id=
"zed-InterfaceFaultRefDesignator"></a><a name=
"zed-wsdlInterfaceFaultReference" id=
"zed-wsdlInterfaceFaultReference"></a></div>
<div class="div3">
<h4><a name="wsdl.binding" id="wsdl.binding"></a>A.2.9 The Binding
Component</h4>
<p><code>wsdl.binding(<em>binding</em>)</code></p>
<ol class="enumar">
<li>
<p><code><em>binding</em></code> is the local name of the {<a href=
"#property-Binding.name">name</a>} property of the <a href=
"#component-Binding">Binding</a> component.</p>
</li>
</ol>
<a name="zed-BindingArgs" id="zed-BindingArgs"></a><a name=
"zed-BindingDesignator" id="zed-BindingDesignator"></a><a name=
"zed-wsdlBinding" id="zed-wsdlBinding"></a><a name=
"zed-BindingInterfaceDesignator" id=
"zed-BindingInterfaceDesignator"></a></div>
<div class="div3">
<h4><a name="wsdl.bindingFault" id="wsdl.bindingFault"></a>A.2.10
The Binding Fault Component</h4>
<p>
<code>wsdl.bindingFault(<em>binding</em>/<em>fault</em>)</code></p>
<ol class="enumar">
<li>
<p><code><em>binding</em></code> is the local name of the {<a href=
"#property-Binding.name">name</a>} property of the parent <a href=
"#component-Binding">Binding</a> component.</p>
</li>
<li>
<p><code><em>fault</em></code> is the {<a href=
"#property-InterfaceFault.name">name</a>} property of the <a href=
"#component-InterfaceFault">Interface Fault</a> component referred
to by the {<a href=
"#property-BindingFault.interfacefault">interface fault</a>}
property of the <a href="#component-BindingFault">Binding Fault</a>
component.</p>
</li>
</ol>
<a name="zed-BindingFaultArgs" id=
"zed-BindingFaultArgs"></a><a name="zed-BindingFaultDesignator" id=
"zed-BindingFaultDesignator"></a><a name="zed-wsdlBindingFault" id=
"zed-wsdlBindingFault"></a></div>
<div class="div3">
<h4><a name="wsdl.bindingOperation" id=
"wsdl.bindingOperation"></a>A.2.11 The Binding Operation
Component</h4>
<p>
<code>wsdl.bindingOperation(<em>binding</em>/<em>operation</em>)</code></p>
<ol class="enumar">
<li>
<p><code><em>binding</em></code> is the local name of the {<a href=
"#property-Binding.name">name</a>} property of the parent <a href=
"#component-Binding">Binding</a> component.</p>
</li>
<li>
<p><code><em>operation</em></code> is the {<a href=
"#property-InterfaceOperation.name">name</a>} property of the
<a href="#component-InterfaceOperation">Interface Operation</a>
component referred to by the {<a href=
"#property-BindingOperation.interfaceoperation">interface
operation</a>} property of the <a href=
"#component-BindingOperation">Binding Operation</a> component.</p>
</li>
</ol>
<a name="zed-BindingOpArgs" id="zed-BindingOpArgs"></a><a name=
"zed-BindingOpDesignator" id="zed-BindingOpDesignator"></a><a name=
"zed-wsdlBindingOperation" id="zed-wsdlBindingOperation"></a></div>
<div class="div3">
<h4><a name="wsdl.bindingMessageReference" id=
"wsdl.bindingMessageReference"></a>A.2.12 The Binding Message
Reference Component</h4>
<p>
<code>wsdl.bindingMessageReference(<em>binding</em>/<em>operation</em>/<em>message</em>)</code></p>
<ol class="enumar">
<li>
<p><code><em>binding</em></code> is the local name of the {<a href=
"#property-Binding.name">name</a>} property of the grandparent
<a href="#component-Binding">Binding</a> component.</p>
</li>
<li>
<p><code><em>operation</em></code> is the {<a href=
"#property-InterfaceOperation.name">name</a>} property of the
<a href="#component-InterfaceOperation">Interface Operation</a>
component referred to by the {<a href=
"#property-BindingOperation.interfaceoperation">interface
operation</a>} property of the parent <a href=
"#component-BindingOperation">Binding Operation</a> component.</p>
</li>
<li>
<p><code><em>message</em></code> is the {<a href=
"#property-InterfaceMessageReference.messagelabel">message
label</a>} property of the <a href=
"#component-InterfaceMessageReference">Interface Message
Reference</a> component referred to by the {<a href=
"#property-BindingMessageReference.interfacemessagereference">interface
message reference</a>} property of the <a href=
"#component-BindingMessageReference">Binding Message Reference</a>
component.</p>
</li>
</ol>
<a name="zed-BindingMessageRefArgs" id=
"zed-BindingMessageRefArgs"></a><a name=
"zed-BindingMessageRefDesignator" id=
"zed-BindingMessageRefDesignator"></a><a name=
"zed-wsdlBindingMessageReference" id=
"zed-wsdlBindingMessageReference"></a></div>
<div class="div3">
<h4><a name="wsdl.bindingFaultReference" id=
"wsdl.bindingFaultReference"></a>A.2.13 The Binding Fault Reference
Component</h4>
<p>
<code>wsdl.bindingFaultReference(<em>binding</em>/<em>operation</em>/<em>message</em>/<em>fault</em>)</code></p>
<ol class="enumar">
<li>
<p><code><em>binding</em></code> is the local name of the {<a href=
"#property-Binding.name">name</a>} property of the grandparent
<a href="#component-Binding">Binding</a> component.</p>
</li>
<li>
<p><code><em>operation</em></code> is the {<a href=
"#property-InterfaceOperation.name">name</a>} property of the
<a href="#component-InterfaceOperation">Interface Operation</a>
component referred to by the {<a href=
"#property-BindingOperation.interfaceoperation">interface
operation</a>} property of the parent <a href=
"#component-BindingOperation">Binding Operation</a> component.</p>
</li>
<li>
<p><code><em>message</em></code> is the {<a href=
"#property-InterfaceFaultReference.messagelabel">message label</a>}
property of the <a href=
"#component-InterfaceFaultReference">Interface Fault Reference</a>
component referred to by the {<a href=
"#property-BindingFaultReference.interfacefaultreference">interface
fault reference</a>} property of the <a href=
"#component-BindingFaultReference">Binding Fault Reference</a>
component.</p>
</li>
<li>
<p><code><em>fault</em></code> is the {<a href=
"#property-InterfaceFault.name">name</a>} property of the <a href=
"#component-InterfaceFault">Interface Fault</a> component referred
to by the {<a href=
"#property-InterfaceFaultReference.interfacefault">interface
fault</a>} property of the <a href=
"#component-InterfaceFaultReference">Interface Fault Reference</a>
component referred to by the {<a href=
"#property-BindingFaultReference.interfacefaultreference">interface
fault reference</a>} property of the <a href=
"#component-BindingFaultReference">Binding Fault Reference</a>
component.</p>
</li>
</ol>
<a name="zed-BindingFaultRefArgs" id=
"zed-BindingFaultRefArgs"></a><a name=
"zed-BindingFaultRefDesignator" id=
"zed-BindingFaultRefDesignator"></a><a name=
"zed-wsdlBindingFaultReference" id=
"zed-wsdlBindingFaultReference"></a></div>
<div class="div3">
<h4><a name="wsdl.service" id="wsdl.service"></a>A.2.14 The Service
Component</h4>
<p><code>wsdl.service(<em>service</em>)</code></p>
<ol class="enumar">
<li>
<p><code><em>service</em></code> is the local name of the {<a href=
"#property-Service.name">name</a>} property of the <a href=
"#component-Service">Service</a> component.</p>
</li>
</ol>
<a name="zed-ServiceArgs" id="zed-ServiceArgs"></a><a name=
"zed-ServiceDesignator" id="zed-ServiceDesignator"></a><a name=
"zed-wsdlService" id="zed-wsdlService"></a></div>
<div class="div3">
<h4><a name="wsdl.endpoint" id="wsdl.endpoint"></a>A.2.15 The
Endpoint Component</h4>
<p>
<code>wsdl.endpoint(<em>service</em>/<em>endpoint</em>)</code></p>
<ol class="enumar">
<li>
<p><code><em>service</em></code> is the local name of the {<a href=
"#property-Service.name">name</a>} property of the parent <a href=
"#component-Service">Service</a> component.</p>
</li>
<li>
<p><code><em>endpoint</em></code> is the {<a href=
"#property-Endpoint.name">name</a>} property of the <a href=
"#component-Endpoint">Endpoint</a> component.</p>
</li>
</ol>
<a name="zed-EndpointArgs" id="zed-EndpointArgs"></a><a name=
"zed-EndpointDesignator" id="zed-EndpointDesignator"></a><a name=
"zed-wsdlEndpoint" id="zed-wsdlEndpoint"></a></div>
<div class="div3">
<h4><a name="wsdl.extension" id="wsdl.extension"></a>A.2.16
Extension Components</h4>
<p>WSDL 2.0 is extensible and it is possible for an extension to
define new components types. The XPointer Framework scheme for
extension components is:</p>
<p><code>wsdl.extension(<em>namespace</em>,
<em>identifier</em>)</code></p>
<ol class="enumar">
<li>
<p><code><em>namespace</em></code> is the namespace URI that
identifies the extension, e.g. for the WSDL 2.0 SOAP 1.2 Binding
the namespace is http://www.w3.org/ns/wsdl/soap.</p>
</li>
<li>
<p><code><em>identifier</em></code> is defined by the extension
using a syntax specific to the extension. The owner of the
extension must define any components contributed by the extension
and a syntax for identifying them.</p>
</li>
</ol>
<a name="zed-ExtensionArgs" id="zed-ExtensionArgs"></a><a name=
"zed-ExtensionDesignator" id="zed-ExtensionDesignator"></a><a name=
"zed-wsdlExtension" id="zed-wsdlExtension"></a></div>
</div>
<div class="div2">
<h3><a name="ietf-sec" id="ietf-sec"></a>A.3 Security
considerations</h3>
<p>This media type uses the "+xml" convention, it shares the same
security considerations as described in [<cite><a href=
"#RFC3023">IETF RFC 3023</a></cite>], section 10.</p>
</div>
</div>
<div class="div1">
<h2><a name="acknowledgments" id="acknowledgments"></a>B.
Acknowledgements (Non-Normative)</h2>
<p>This document is the work of the <a href=
"http://www.w3.org/2002/ws/desc/">W3C Web Service Description
Working Group</a>.</p>
<p>Members of the Working Group are (at the time of writing, and by
alphabetical order): Charlton Barreto (Adobe Systems, Inc), Allen
Brookes (Rogue Wave Softwave), Dave Chappell (Sonic Software),
Helen Chen (Agfa-Gevaert N. V.), Roberto Chinnici (Sun
Microsystems), Kendall Clark (University of Maryland), Glen Daniels
(Sonic Software), Paul Downey (British Telecommunications), Youenn
Fablet (Canon), Ram Jeyaraman (Microsoft), Tom Jordahl (Adobe
Systems), Anish Karmarkar (Oracle Corporation), Jacek Kopecky (DERI
Innsbruck at the Leopold-Franzens-Universität Innsbruck, Austria),
Amelia Lewis (TIBCO Software, Inc.), Philippe Le Hegaret (W3C),
Michael Liddy (Education.au Ltd.), Kevin Canyang Liu (SAP AG),
Jonathan Marsh (WSO2), Monica Martin (Sun Microsystems), Josephine
Micallef (SAIC - Telcordia Technologies), Jeff Mischkinsky (Oracle
Corporation), Dale Moberg (Cyclone Commerce), Jean-Jacques Moreau
(Canon), David Orchard (BEA Systems, Inc.), Gilbert Pilz (BEA
Systems, Inc.), Tony Rogers (Computer Associates), Arthur Ryman
(IBM), Adi Sakala (IONA Technologies), Michael Shepherd (Xerox),
Asir Vedamuthu (Microsoft Corporation), Sanjiva Weerawarana (WSO2),
Ümit Yalçınalp (SAP AG), Peter Zehler (Xerox).</p>
<p>Previous members were: Eran Chinthaka (WSO2), Mark Nottingham
(BEA Systems, Inc.), Hugo Haas (W3C), Vivek Pandey (Sun
Microsystems), Bijan Parsia (University of Maryland), Lily Liu
(webMethods, Inc.), Don Wright (Lexmark), Joyce Yang (Oracle
Corporation), Daniel Schutzer (Citigroup), Dave Solo (Citigroup),
Stefano Pogliani (Sun Microsystems), William Stumbo (Xerox),
Stephen White (SeeBeyond), Barbara Zengler (DaimlerChrysler
Research and Technology), Tim Finin (University of Maryland),
Laurent De Teneuille (L'Echangeur), Johan Pauhlsson (L'Echangeur),
Mark Jones (AT&amp;T), Steve Lind (AT&amp;T), Sandra Swearingen
(U.S. Department of Defense, U.S. Air Force), Philippe Le Hégaret
(W3C), Jim Hendler (University of Maryland), Dietmar Gaertner
(Software AG), Michael Champion (Software AG), Don Mullen (TIBCO
Software, Inc.), Steve Graham (Global Grid Forum), Steve Tuecke
(Global Grid Forum), Michael Mahan (Nokia), Bryan Thompson (Hicks
&amp; Associates), Ingo Melzer (DaimlerChrysler Research and
Technology), Sandeep Kumar (Cisco Systems), Alan Davies
(SeeBeyond), Jacek Kopecky (Systinet), Mike Ballantyne (Electronic
Data Systems), Mike Davoren (W. W. Grainger), Dan Kulp (IONA
Technologies), Mike McHugh (W. W. Grainger), Michael Mealling
(Verisign), Waqar Sadiq (Electronic Data Systems), Yaron Goland
(BEA Systems, Inc.), Ümit Yalçınalp (Oracle Corporation), Peter
Madziak (Agfa-Gevaert N. V.), Jeffrey Schlimmer (Microsoft
Corporation), Hao He (The Thomson Corporation), Erik Ackerman
(Lexmark), Jerry Thrasher (Lexmark), Prasad Yendluri (webMethods,
Inc.), William Vambenepe (Hewlett-Packard Company), David Booth
(W3C), Sanjiva Weerawarana (IBM), Asir Vedamuthu (webMethods,
Inc.), Igor Sedukhin (Computer Associates), Martin Gudgin
(Microsoft Corporation), Rebecca Bergersen (IONA Technologies), Ugo
Corda (SeeBeyond).</p>
<p>The people who have contributed to <a href=
"http://lists.w3.org/Archives/Public/www-ws-desc/">discussions on
www-ws-desc@w3.org</a> are also gratefully acknowledged.</p>
</div>
<div class="div1">
<h2><a name="wsdl-iri-references" id="wsdl-iri-references"></a>C.
IRI-References for WSDL 2.0 Components (Non-Normative)</h2>
<p>This appendix provides a syntax for IRI-references for all
components found in a WSDL 2.0 document. The IRI-references are
easy to understand and compare, while imposing no burden on the
WSDL 2.0 author.</p>
<div class="div2">
<h3><a name="wsdl-iris" id="wsdl-iris"></a>C.1 WSDL 2.0 IRIs</h3>
<p>There are two main cases for WSDL 2.0 IRIs:</p>
<ul>
<li>
<p>the IRI of a WSDL 2.0 document</p>
</li>
<li>
<p>the IRI of a WSDL 2.0 namespace</p>
</li>
</ul>
<p>The IRI of a WSDL 2.0 document can be dereferenced to give a
resource representation that contributes component definitions to a
single WSDL 2.0 namespace. If the media type is set to the WSDL 2.0
media type, then the fragment identifiers can be used to identify
the main components that are defined in the document.</p>
<p>However, in keeping with the recommendation in <a href=
"#Description_details"><strong>2.1.1 The Description
Component</strong></a> that the namespace URI be dereferencable to
a WSDL 2.0 document, this appendix specifies the use of the
namespace IRI with the WSDL 2.0 fragment identifiers to form an
IRI-reference.</p>
<p>The IRI in an IRI-reference for a WSDL 2.0 component is the
namespace name of the {<a href="#property-.name">name</a>} property
of either the component itself, in the case of <a href=
"#component-Interface">Interface</a> , <a href=
"#component-Binding">Binding</a> , and <a href=
"#component-Service">Service</a> components, or the {<a href=
"#property-.name">name</a>} property of the ancestor top-level
component. The IRI provided by the namespace name of the {<a href=
"#property-.name">name</a>} property is combined with a zero or
more <code>xmlns</code> pointer parts (see <em>3.4 Namespace
Binding Context</em> in [<cite><a href="#XPTR">XPointer</a></cite>]
) followed by a single WSDL 2.0 pointer part as defined in <a href=
"#frag-ids"><strong>A.2 Fragment Identifiers</strong></a> .</p>
</div>
<div class="div2">
<h3><a name="component-designator-canonical-form" id=
"component-designator-canonical-form"></a>C.2 Canonical Form for
WSDL 2.0 Component Designators</h3>
<p>The IRI-references described above MAY be used as WSDL 2.0
component designators. For ease of comparison, the fragment
identifier of WSDL 2.0 component designators SHOULD conform to the
following canonicalization rules:</p>
<ul>
<li>
<p><span id="CanonFragId-1097" class="test-assertion-tr">The
fragment identifier consists of a sequence zero or more
<code>xmlns()</code> pointer parts followed by exactly one
<code>wsdl.*()</code> pointer part. <sup><a href=
"#CanonFragId-1097-summary" title=
"Link to assertion CanonFragId-1097 summary">†</a></sup></span></p>
</li>
<li>
<p><span id="CanonFragId-1098" class="test-assertion-tr">Each
<code>xmlns()</code> pointer part that appears in the fragment
identifier defines a namespace that is referenced by the
<code>wsdl.*()</code> pointer part. <sup><a href=
"#CanonFragId-1098-summary" title=
"Link to assertion CanonFragId-1098 summary">†</a></sup></span></p>
</li>
<li>
<p><span id="CanonFragId-1099" class="test-assertion-tr">Each
<code>xmlns()</code> pointer part defines a unique namespace.
<sup><a href="#CanonFragId-1099-summary" title=
"Link to assertion CanonFragId-1099 summary">†</a></sup></span></p>
</li>
<li>
<p><span id="CanonFragId-1100" class="test-assertion-tr">The
<code>xmlns()</code> pointer parts define namespaces in the same
order as they are referenced in the <code>wsdl.*()</code> pointer
part. <sup><a href="#CanonFragId-1100-summary" title=
"Link to assertion CanonFragId-1100 summary">†</a></sup></span></p>
</li>
<li>
<p><span id="CanonFragId-1101" class="test-assertion-tr">The
namespace prefixes defined by the <code>xmlns()</code> pointer
parts are named <code>ns1</code> , <code>ns2</code> , etc., in the
order of their appearance. <sup><a href="#CanonFragId-1101-summary"
title=
"Link to assertion CanonFragId-1101 summary">†</a></sup></span></p>
</li>
<li>
<p><span id="CanonFragId-1102" class="test-assertion-tr">The
fragment identifier contains no optional whitespace. <sup><a href=
"#CanonFragId-1102-summary" title=
"Link to assertion CanonFragId-1102 summary">†</a></sup></span></p>
</li>
<li>
<p><span id="CanonFragId-1103" class="test-assertion-tr">No
<code>xmlns()</code> pointer part defines a namespace for the
targetNamespace of the WSDL 2.0 document. <sup><a href=
"#CanonFragId-1103-summary" title=
"Link to assertion CanonFragId-1103 summary">†</a></sup></span></p>
</li>
</ul>
</div>
<div class="div2">
<h3><a name="Iri-ref-ex" id="Iri-ref-ex"></a>C.3 Example</h3>
<p>Consider the following WSDL 2.0 document located at
http://example.org/TicketAgent.wsdl:</p>
<div class="exampleOuter">
<p style="text-align: left" class="exampleHead"><a name=
"iri-ref-example-wsdl" id=
"iri-ref-example-wsdl"></a><em><span>Example C-1.</span>
IRI-References - Example WSDL 2.0 Document</em></p>
<div class="exampleInner">
<pre xml:space="preserve">

&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;wsdl:description 
    targetNamespace="http://example.org/TicketAgent.wsdl20" 
    xmlns:xsTicketAgent="http://example.org/TicketAgent.xsd" 
    xmlns:wsdl="http://www.w3.org/ns/wsdl" 
    xmlns:xs="http://www.w3.org/2001/XMLSchema" 
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
    xsi:schemaLocation="http://www.w3.org/ns/wsdl http://www.w3.org/2007/06/wsdl/wsdl20.xsd"&gt;
        
    &lt;wsdl:types&gt;
        &lt;xs:import schemaLocation="TicketAgent.xsd" 
                   namespace="http://example.org/TicketAgent.xsd" /&gt;
    &lt;/wsdl:types&gt;
        
    &lt;wsdl:interface name="TicketAgent"&gt;
        &lt;wsdl:operation name="listFlights"
                        pattern="http://www.w3.org/ns/wsdl/in-out"&gt;
            &lt;wsdl:input element="xsTicketAgent:listFlightsRequest"/&gt;
            &lt;wsdl:output element="xsTicketAgent:listFlightsResponse"/&gt;
        &lt;/wsdl:operation&gt;
                
        &lt;wsdl:operation name="reserveFlight"
                        pattern="http://www.w3.org/ns/wsdl/in-out"&gt;
            &lt;wsdl:input element="xsTicketAgent:reserveFlightRequest"/&gt;
            &lt;wsdl:output element="xsTicketAgent:reserveFlightResponse"/&gt;
        &lt;/wsdl:operation&gt;
    &lt;/wsdl:interface&gt;
&lt;/wsdl:description&gt;

</pre></div>
</div>
<p>Its components have the following IRI-references which follow
the above canonicalization rules except for the presence of
optional whitespace that has been added in order to improve the
formatting:</p>
<div class="exampleOuter">
<p style="text-align: left" class="exampleHead"><a name=
"iri-ref-example-iris" id=
"iri-ref-example-iris"></a><em><span>Example C-2.</span>
IRI-References - Example IRIs</em></p>
<div class="exampleInner">
<pre xml:space="preserve">
http://example.org/TicketAgent.wsdl20#
  wsdl.description() 

http://example.org/TicketAgent.wsdl20#
  xmlns(ns1=http://example.org/TicketAgent.xsd)
  wsdl.elementDeclaration(ns1:listFlightsRequest) 

http://example.org/TicketAgent.wsdl20#
  xmlns(ns1=http://example.org/TicketAgent.xsd)
  wsdl.elementDeclaration(ns1:listFlightsResponse) 

http://example.org/TicketAgent.wsdl20#
  xmlns(ns1=http://example.org/TicketAgent.xsd)
  wsdl.elementDeclaration(ns1:reserveFlightRequest) 

http://example.org/TicketAgent.wsdl20#
  xmlns(ns1=http://example.org/TicketAgent.xsd)
  wsdl.elementDeclaration(ns1:reserveFlightResponse) 

http://example.org/TicketAgent.wsdl20#
  wsdl.interface(TicketAgent) 

http://example.org/TicketAgent.wsdl20#
  wsdl.interfaceOperation(TicketAgent/listFlights) 

http://example.org/TicketAgent.wsdl20#
  wsdl.interfaceMessageReference(TicketAgent/listFlights/In) 

http://example.org/TicketAgent.wsdl20#
  wsdl.interfaceMessageReference(TicketAgent/listFlights/Out) 

http://example.org/TicketAgent.wsdl20#
  wsdl.interfaceOperation(TicketAgent/reserveFlight)

http://example.org/TicketAgent.wsdl20#
  wsdl.interfaceMessageReference(TicketAgent/reserveFlight/In) 

http://example.org/TicketAgent.wsdl20#
  wsdl.interfaceMessageReference(TicketAgent/reserveFlight/Out) 
</pre></div>
</div>
</div>
</div>
<div class="div1">
<h2><a name="componentsummary" id="componentsummary"></a>D.
Component Summary (Non-Normative)</h2>
<p><a href="#component-summary">Table D-1</a> lists all the
components in the WSDL 2.0 abstract Component Model, and all their
properties. Note some properties have a generic definition that is
used in more than one component. In this case, the Component column
contains a "-" to indicate this generic definition of the
property.</p>
<a name="component-summary" id="component-summary"></a>
<table width="100%" border="1">
<caption>Table D-1. Summary of WSDL 2.0 Components and their
Properties</caption>
<col width="20%" span="1" />
<col width="80%" span="1" />
<tbody>
<tr>
<th rowspan="1" colspan="1">Component</th>
<th rowspan="1" colspan="1">Defined Properties</th>
</tr>
<tr>
<td rowspan="1" colspan="1">-</td>
<td rowspan="1" colspan="1">{<a href="#property-.name">name</a>},
{<a href="#property-.parent">parent</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-Binding">Binding</a></td>
<td rowspan="1" colspan="1">{<a href=
"#property-Binding.bindingfaults">binding faults</a>}, {<a href=
"#property-Binding.bindingoperations">binding operations</a>},
{<a href="#property-Binding.interface">interface</a>}, {<a href=
"#property-Binding.name">name</a>}, {<a href=
"#property-Binding.type">type</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-BindingFault">Binding Fault</a></td>
<td rowspan="1" colspan="1">{<a href=
"#property-BindingFault.interfacefault">interface fault</a>},
{<a href="#property-BindingFault.parent">parent</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-BindingFaultReference">Binding Fault Reference</a></td>
<td rowspan="1" colspan="1">{<a href=
"#property-BindingFaultReference.interfacefaultreference">interface
fault reference</a>}, {<a href=
"#property-BindingFaultReference.parent">parent</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-BindingMessageReference">Binding Message
Reference</a></td>
<td rowspan="1" colspan="1">{<a href=
"#property-BindingMessageReference.interfacemessagereference">interface
message reference</a>}, {<a href=
"#property-BindingMessageReference.parent">parent</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-BindingOperation">Binding Operation</a></td>
<td rowspan="1" colspan="1">{<a href=
"#property-BindingOperation.bindingfaultreferences">binding fault
references</a>}, {<a href=
"#property-BindingOperation.bindingmessagereferences">binding
message references</a>}, {<a href=
"#property-BindingOperation.interfaceoperation">interface
operation</a>}, {<a href=
"#property-BindingOperation.parent">parent</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-Description">Description</a></td>
<td rowspan="1" colspan="1">{<a href=
"#property-Description.bindings">bindings</a>}, {<a href=
"#property-Description.elementdeclarations">element
declarations</a>}, {<a href=
"#property-Description.interfaces">interfaces</a>}, {<a href=
"#property-Description.services">services</a>}, {<a href=
"#property-Description.typedefinitions">type definitions</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-ElementDeclaration">Element Declaration</a></td>
<td rowspan="1" colspan="1">{<a href=
"#property-ElementDeclaration.name">name</a>}, {<a href=
"#property-ElementDeclaration.system">system</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-Endpoint">Endpoint</a></td>
<td rowspan="1" colspan="1">{<a href=
"#property-Endpoint.address">address</a>}, {<a href=
"#property-Endpoint.binding">binding</a>}, {<a href=
"#property-Endpoint.name">name</a>}, {<a href=
"#property-Endpoint.parent">parent</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-Interface">Interface</a></td>
<td rowspan="1" colspan="1">{<a href=
"#property-Interface.extendedinterfaces">extended interfaces</a>},
{<a href="#property-Interface.interfacefaults">interface
faults</a>}, {<a href=
"#property-Interface.interfaceoperations">interface
operations</a>}, {<a href="#property-Interface.name">name</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-InterfaceFault">Interface Fault</a></td>
<td rowspan="1" colspan="1">{<a href=
"#property-InterfaceFault.elementdeclaration">element
declaration</a>}, {<a href=
"#property-InterfaceFault.messagecontentmodel">message content
model</a>}, {<a href="#property-InterfaceFault.name">name</a>},
{<a href="#property-InterfaceFault.parent">parent</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-InterfaceFaultReference">Interface Fault
Reference</a></td>
<td rowspan="1" colspan="1">{<a href=
"#property-InterfaceFaultReference.direction">direction</a>},
{<a href=
"#property-InterfaceFaultReference.interfacefault">interface
fault</a>}, {<a href=
"#property-InterfaceFaultReference.messagelabel">message
label</a>}, {<a href=
"#property-InterfaceFaultReference.parent">parent</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-InterfaceMessageReference">Interface Message
Reference</a></td>
<td rowspan="1" colspan="1">{<a href=
"#property-InterfaceMessageReference.direction">direction</a>},
{<a href=
"#property-InterfaceMessageReference.elementdeclaration">element
declaration</a>}, {<a href=
"#property-InterfaceMessageReference.messagecontentmodel">message
content model</a>}, {<a href=
"#property-InterfaceMessageReference.messagelabel">message
label</a>}, {<a href=
"#property-InterfaceMessageReference.parent">parent</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-InterfaceOperation">Interface Operation</a></td>
<td rowspan="1" colspan="1">{<a href=
"#property-InterfaceOperation.interfacefaultreferences">interface
fault references</a>}, {<a href=
"#property-InterfaceOperation.interfacemessagereferences">interface
message references</a>}, {<a href=
"#property-InterfaceOperation.messageexchangepattern">message
exchange pattern</a>}, {<a href=
"#property-InterfaceOperation.name">name</a>}, {<a href=
"#property-InterfaceOperation.parent">parent</a>}, {<a href=
"#property-InterfaceOperation.style">style</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-Service">Service</a></td>
<td rowspan="1" colspan="1">{<a href=
"#property-Service.endpoints">endpoints</a>}, {<a href=
"#property-Service.interface">interface</a>}, {<a href=
"#property-Service.name">name</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a href=
"#component-TypeDefinition">Type Definition</a></td>
<td rowspan="1" colspan="1">{<a href=
"#property-TypeDefinition.name">name</a>}, {<a href=
"#property-TypeDefinition.system">system</a>}</td>
</tr>
<tr>
<th rowspan="1" colspan="1">Property</th>
<th rowspan="1" colspan="1">Where Defined</th>
</tr>
<tr>
<td rowspan="1" colspan="1">address</td>
<td rowspan="1" colspan="1">Endpoint.{<a href=
"#property-Endpoint.address">address</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">binding</td>
<td rowspan="1" colspan="1">Endpoint.{<a href=
"#property-Endpoint.binding">binding</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">binding fault references</td>
<td rowspan="1" colspan="1">Binding Operation.{<a href=
"#property-BindingOperation.bindingfaultreferences">binding fault
references</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">binding faults</td>
<td rowspan="1" colspan="1">Binding.{<a href=
"#property-Binding.bindingfaults">binding faults</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">binding message references</td>
<td rowspan="1" colspan="1">Binding Operation.{<a href=
"#property-BindingOperation.bindingmessagereferences">binding
message references</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">binding operations</td>
<td rowspan="1" colspan="1">Binding.{<a href=
"#property-Binding.bindingoperations">binding operations</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">bindings</td>
<td rowspan="1" colspan="1">Description.{<a href=
"#property-Description.bindings">bindings</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">direction</td>
<td rowspan="1" colspan="1">Interface Fault Reference.{<a href=
"#property-InterfaceFaultReference.direction">direction</a>},
Interface Message Reference.{<a href=
"#property-InterfaceMessageReference.direction">direction</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">element declaration</td>
<td rowspan="1" colspan="1">Interface Fault.{<a href=
"#property-InterfaceFault.elementdeclaration">element
declaration</a>}, Interface Message Reference.{<a href=
"#property-InterfaceMessageReference.elementdeclaration">element
declaration</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">element declarations</td>
<td rowspan="1" colspan="1">Description.{<a href=
"#property-Description.elementdeclarations">element
declarations</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">endpoints</td>
<td rowspan="1" colspan="1">Service.{<a href=
"#property-Service.endpoints">endpoints</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">extended interfaces</td>
<td rowspan="1" colspan="1">Interface.{<a href=
"#property-Interface.extendedinterfaces">extended
interfaces</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">interface</td>
<td rowspan="1" colspan="1">Binding.{<a href=
"#property-Binding.interface">interface</a>}, Service.{<a href=
"#property-Service.interface">interface</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">interface fault</td>
<td rowspan="1" colspan="1">Binding Fault.{<a href=
"#property-BindingFault.interfacefault">interface fault</a>},
Interface Fault Reference.{<a href=
"#property-InterfaceFaultReference.interfacefault">interface
fault</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">interface fault reference</td>
<td rowspan="1" colspan="1">Binding Fault Reference.{<a href=
"#property-BindingFaultReference.interfacefaultreference">interface
fault reference</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">interface fault references</td>
<td rowspan="1" colspan="1">Interface Operation.{<a href=
"#property-InterfaceOperation.interfacefaultreferences">interface
fault references</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">interface faults</td>
<td rowspan="1" colspan="1">Interface.{<a href=
"#property-Interface.interfacefaults">interface faults</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">interface message reference</td>
<td rowspan="1" colspan="1">Binding Message Reference.{<a href=
"#property-BindingMessageReference.interfacemessagereference">interface
message reference</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">interface message references</td>
<td rowspan="1" colspan="1">Interface Operation.{<a href=
"#property-InterfaceOperation.interfacemessagereferences">interface
message references</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">interface operation</td>
<td rowspan="1" colspan="1">Binding Operation.{<a href=
"#property-BindingOperation.interfaceoperation">interface
operation</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">interface operations</td>
<td rowspan="1" colspan="1">Interface.{<a href=
"#property-Interface.interfaceoperations">interface
operations</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">interfaces</td>
<td rowspan="1" colspan="1">Description.{<a href=
"#property-Description.interfaces">interfaces</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">message content model</td>
<td rowspan="1" colspan="1">Interface Fault.{<a href=
"#property-InterfaceFault.messagecontentmodel">message content
model</a>}, Interface Message Reference.{<a href=
"#property-InterfaceMessageReference.messagecontentmodel">message
content model</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">message exchange pattern</td>
<td rowspan="1" colspan="1">Interface Operation.{<a href=
"#property-InterfaceOperation.messageexchangepattern">message
exchange pattern</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">message label</td>
<td rowspan="1" colspan="1">Interface Fault Reference.{<a href=
"#property-InterfaceFaultReference.messagelabel">message
label</a>}, Interface Message Reference.{<a href=
"#property-InterfaceMessageReference.messagelabel">message
label</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">name</td>
<td rowspan="1" colspan="1">.{<a href="#property-.name">name</a>},
Binding.{<a href="#property-Binding.name">name</a>}, Element
Declaration.{<a href="#property-ElementDeclaration.name">name</a>},
Endpoint.{<a href="#property-Endpoint.name">name</a>},
Interface.{<a href="#property-Interface.name">name</a>}, Interface
Fault.{<a href="#property-InterfaceFault.name">name</a>}, Interface
Operation.{<a href="#property-InterfaceOperation.name">name</a>},
Service.{<a href="#property-Service.name">name</a>}, Type
Definition.{<a href="#property-TypeDefinition.name">name</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">parent</td>
<td rowspan="1" colspan="1">.{<a href=
"#property-.parent">parent</a>}, Binding Fault.{<a href=
"#property-BindingFault.parent">parent</a>}, Binding Fault
Reference.{<a href=
"#property-BindingFaultReference.parent">parent</a>}, Binding
Message Reference.{<a href=
"#property-BindingMessageReference.parent">parent</a>}, Binding
Operation.{<a href="#property-BindingOperation.parent">parent</a>},
Endpoint.{<a href="#property-Endpoint.parent">parent</a>},
Interface Fault.{<a href=
"#property-InterfaceFault.parent">parent</a>}, Interface Fault
Reference.{<a href=
"#property-InterfaceFaultReference.parent">parent</a>}, Interface
Message Reference.{<a href=
"#property-InterfaceMessageReference.parent">parent</a>}, Interface
Operation.{<a href=
"#property-InterfaceOperation.parent">parent</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">services</td>
<td rowspan="1" colspan="1">Description.{<a href=
"#property-Description.services">services</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">style</td>
<td rowspan="1" colspan="1">Interface Operation.{<a href=
"#property-InterfaceOperation.style">style</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">system</td>
<td rowspan="1" colspan="1">Element Declaration.{<a href=
"#property-ElementDeclaration.system">system</a>}, Type
Definition.{<a href=
"#property-TypeDefinition.system">system</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">type</td>
<td rowspan="1" colspan="1">Binding.{<a href=
"#property-Binding.type">type</a>}</td>
</tr>
<tr>
<td rowspan="1" colspan="1">type definitions</td>
<td rowspan="1" colspan="1">Description.{<a href=
"#property-Description.typedefinitions">type definitions</a>}</td>
</tr>
</tbody>
</table>

<br /></div>
<h2><a name="assertionsummary" id="assertionsummary"></a>E.
Assertion Summary (Non-Normative)</h2>
<p>This appendix summarizes assertions about WSDL 2.0 documents and
components that are not enforced by the WSDL 2.0 schema. Each
assertion is assigned a unique identifier which WSDL 2.0 processors
may use to report errors.</p>
<a name="document-assertion-summary" id=
"document-assertion-summary"></a>
<table width="100%" border="1">
<caption>Table E-1. Summary of Assertions about WSDL 2.0
Documents</caption>
<col width="20%" span="1" />
<col width="80%" span="1" />
<tbody>
<tr>
<th rowspan="1" colspan="1">Id</th>
<th rowspan="1" colspan="1">Assertion</th>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Description-1004-summary"
href="#Description-1004" id=
"Description-1004-summary">Description-1004</a></td>
<td rowspan="1" colspan="1">If a WSDL 2.0 document is split into
multiple WSDL 2.0 documents (which may be combined as needed via
<a href="#includes"><strong>4.1 Including
Descriptions</strong></a>), then the <code>targetNamespace</code>
<em>attribute information item</em> SHOULD resolve to a master WSDL
2.0 document that includes all the WSDL 2.0 documents needed for
that service description.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Description-1005-summary"
href="#Description-1005" id=
"Description-1005-summary">Description-1005</a></td>
<td rowspan="1" colspan="1">Zero or more <em>element information
item</em>s amongst its [children], in order as follows:</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Description-1006-summary"
href="#Description-1006" id=
"Description-1006-summary">Description-1006</a></td>
<td rowspan="1" colspan="1">Its value MUST be an absolute IRI (see
[<cite><a href="#RFC3987">IETF RFC 3987</a></cite>]) and should be
dereferencable.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Import-1082-summary" href=
"#Import-1082" id="Import-1082-summary">Import-1082</a></td>
<td rowspan="1" colspan="1">As with XML schema, any WSDL 2.0
document that references a foreign component MUST have a
<code>wsdl:import</code> <em>element information item</em> for the
associated foreign namespace (but which does not necessarily
provide a <code>location</code> <em>attribute information item</em>
that identifies the WSDL 2.0 document in which the referenced
component is defined).</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Import-1083-summary" href=
"#Import-1083" id="Import-1083-summary">Import-1083</a></td>
<td rowspan="1" colspan="1">If a WSDL 2.0 document contains more
than one <code>wsdl:import</code> <em>element information item</em>
for a given value of the <code>namespace</code> <em>attribute
information item</em>, then they MUST provide different values for
the <code>location</code> <em>attribute information item</em>.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Import-1084-summary" href=
"#Import-1084" id="Import-1084-summary">Import-1084</a></td>
<td rowspan="1" colspan="1">This value MUST NOT match the actual
value of <code>targetNamespace</code> <em>attribute information
item</em> in the enclosing WSDL 2.0 document.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Import-1085-summary" href=
"#Import-1085" id="Import-1085-summary">Import-1085</a></td>
<td rowspan="1" colspan="1">If the location attribute in the
<code>import</code> <em>element information item</em> is
dereferencable, then it MUST reference a WSDL 2.0 document.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Import-1086-summary" href=
"#Import-1086" id="Import-1086-summary">Import-1086</a></td>
<td rowspan="1" colspan="1">If the <code>location</code>
<em>attribute information item</em> of the <code>import</code>
<em>element information item</em> is dereferencable, then the
actual value of the <code>namespace</code> <em>attribute
information item</em> MUST be identical to the actual value of the
<code>targetNamespace</code> <em>attribute information item</em> of
the referenced WSDL 2.0 document (see <a href=
"#wsdllocation"><strong>7. Locating WSDL 2.0
Documents</strong></a>).</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Include-1080-summary" href=
"#Include-1080" id="Include-1080-summary">Include-1080</a></td>
<td rowspan="1" colspan="1">The IRI indicated by
<code>location</code> MUST resolve to a WSDL 2.0 document.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Include-1081-summary" href=
"#Include-1081" id="Include-1081-summary">Include-1081</a></td>
<td rowspan="1" colspan="1">The actual value of the
<code>targetNamespace</code> <em>attribute information item</em> of
the included WSDL 2.0 document MUST match the actual value of the
<code>targetNamespace</code> <em>attribute information item</em> of
the <code>description</code> <em>element information item</em>
which is the [parent] of the <code>include</code> <em>element
information item</em>.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Interface-1012-summary" href=
"#Interface-1012" id=
"Interface-1012-summary">Interface-1012</a></td>
<td rowspan="1" colspan="1">Its value, if present, MUST contain
absolute IRIs (see [<cite><a href="#RFC3987">IETF RFC
3987</a></cite>]).</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="InterfaceFault-1017-summary"
href="#InterfaceFault-1017" id=
"InterfaceFault-1017-summary">InterfaceFault-1017</a></td>
<td rowspan="1" colspan="1">If the <code>element</code>
<em>attribute information item</em> has a value, then it MUST
resolve to an <a href="#component-ElementDeclaration">Element
Declaration</a> component from the {<a href=
"#property-Description.elementdeclarations">element
declarations</a>} property of the <a href=
"#component-Description">Description</a> component.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name=
"InterfaceFaultReference-1040-summary" href=
"#InterfaceFaultReference-1040" id=
"InterfaceFaultReference-1040-summary">InterfaceFaultReference-1040</a></td>
<td rowspan="1" colspan="1">The <code>messageLabel</code>
<em>attribute information item</em> MUST be present in the XML
representation of an <a href=
"#component-InterfaceFaultReference">Interface Fault Reference</a>
component with a given {<a href=
"#property-InterfaceFaultReference.direction">direction</a>}, if
the {<a href=
"#property-InterfaceOperation.messageexchangepattern">message
exchange pattern</a>} of the parent <a href=
"#component-InterfaceOperation">Interface Operation</a> component
has more than one fault with that direction.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name=
"InterfaceMessageReference-1036-summary" href=
"#InterfaceMessageReference-1036" id=
"InterfaceMessageReference-1036-summary">InterfaceMessageReference-1036</a></td>
<td rowspan="1" colspan="1">If the <code>element</code>
<em>attribute information item</em> has a value, then it MUST
resolve to an <a href="#component-ElementDeclaration">Element
Declaration</a> component from the {<a href=
"#property-Description.elementdeclarations">element
declarations</a>} property of the <a href=
"#component-Description">Description</a> component.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Location-1092-summary" href=
"#Location-1092" id="Location-1092-summary">Location-1092</a></td>
<td rowspan="1" colspan="1">It MUST NOT appear on a
<code>wsdl:description</code> element or any of its
children/descendants.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Location-1094-summary" href=
"#Location-1094" id="Location-1094-summary">Location-1094</a></td>
<td rowspan="1" colspan="1">For each pair of IRIs, if the location
IRI of the pair is dereferencable, then it MUST reference a WSDL
2.0 (or 1.1) document whose target namespace is the namespace IRI
of the pair.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="MessageLabel-1030-summary"
href="#MessageLabel-1030" id=
"MessageLabel-1030-summary">MessageLabel-1030</a></td>
<td rowspan="1" colspan="1">If the <code>messageLabel</code>
<em>attribute information item</em> of an interface message
reference <em>element information item</em> is present, then its
actual value MUST match the {<a href=
"#property-InterfaceMessageReference.messagelabel">message
label</a>} of some placeholder message with {<a href=
"#property-InterfaceMessageReference.direction">direction</a>}
equal to the message direction.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="MessageLabel-1031-summary"
href="#MessageLabel-1031" id=
"MessageLabel-1031-summary">MessageLabel-1031</a></td>
<td rowspan="1" colspan="1">If the <code>messageLabel</code>
<em>attribute information item</em> of an interface message
reference <em>element information item</em> is absent then there
MUST be a unique placeholder message with {<a href=
"#property-InterfaceMessageReference.direction">direction</a>}
equal to the message direction.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="MessageLabel-1032-summary"
href="#MessageLabel-1032" id=
"MessageLabel-1032-summary">MessageLabel-1032</a></td>
<td rowspan="1" colspan="1">If the local name is <code>input</code>
then the message exchange pattern MUST have at least one
placeholder message with direction "In".</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="MessageLabel-1033-summary"
href="#MessageLabel-1033" id=
"MessageLabel-1033-summary">MessageLabel-1033</a></td>
<td rowspan="1" colspan="1">If the local name is
<code>output</code> then the message exchange pattern MUST have at
least one placeholder message with direction "Out".</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="MessageLabel-1034-summary"
href="#MessageLabel-1034" id=
"MessageLabel-1034-summary">MessageLabel-1034</a></td>
<td rowspan="1" colspan="1">If the local name is
<code>infault</code> then the message exchange pattern MUST support
at least one fault in the "In" direction.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="MessageLabel-1035-summary"
href="#MessageLabel-1035" id=
"MessageLabel-1035-summary">MessageLabel-1035</a></td>
<td rowspan="1" colspan="1">If the local name is
<code>outfault</code> then the message exchange pattern MUST
support at least one fault in the "Out" direction.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="MessageLabel-1041-summary"
href="#MessageLabel-1041" id=
"MessageLabel-1041-summary">MessageLabel-1041</a></td>
<td rowspan="1" colspan="1">The <code>messageLabel</code>
<em>attribute information item</em> of an interface fault reference
<em>element information item</em> MUST be present if the message
exchange pattern has more than one placeholder message with
{<a href=
"#property-InterfaceMessageReference.direction">direction</a>}
equal to the message direction.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="MessageLabel-1042-summary"
href="#MessageLabel-1042" id=
"MessageLabel-1042-summary">MessageLabel-1042</a></td>
<td rowspan="1" colspan="1">If the <code>messageLabel</code>
<em>attribute information item</em> of an interface fault reference
<em>element information item</em> is present then its actual value
MUST match the {<a href=
"#property-InterfaceMessageReference.messagelabel">message
label</a>} of some placeholder message with {<a href=
"#property-InterfaceMessageReference.direction">direction</a>}
equal to the message direction.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="MessageLabel-1043-summary"
href="#MessageLabel-1043" id=
"MessageLabel-1043-summary">MessageLabel-1043</a></td>
<td rowspan="1" colspan="1">If the <code>messageLabel</code>
<em>attribute information item</em> of an interface fault reference
<em>element information item</em> is absent then there MUST be a
unique placeholder message with {<a href=
"#property-InterfaceMessageReference.direction">direction</a>}
equal to the message direction.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="MessageLabel-1053-summary"
href="#MessageLabel-1053" id=
"MessageLabel-1053-summary">MessageLabel-1053</a></td>
<td rowspan="1" colspan="1">If the <code>messageLabel</code>
<em>attribute information item</em> of a binding message reference
<em>element information item</em> is present then its actual value
MUST match the {<a href=
"#property-InterfaceMessageReference.messagelabel">message
label</a>} of some placeholder message with {<a href=
"#property-InterfaceMessageReference.direction">direction</a>}
equal to the message direction.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="MessageLabel-1054-summary"
href="#MessageLabel-1054" id=
"MessageLabel-1054-summary">MessageLabel-1054</a></td>
<td rowspan="1" colspan="1">If the <code>messageLabel</code>
<em>attribute information item</em> of a binding message reference
<em>element information item</em> is absent then there MUST be a
unique placeholder message with {<a href=
"#property-InterfaceMessageReference.direction">direction</a>}
equal to the message direction.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="MessageLabel-1056-summary"
href="#MessageLabel-1056" id=
"MessageLabel-1056-summary">MessageLabel-1056</a></td>
<td rowspan="1" colspan="1">The <code>messageLabel</code>
<em>attribute information item</em> of a binding fault reference
<em>element information item</em> MUST be present if the message
exchange pattern has more than one placeholder message with
{<a href=
"#property-InterfaceMessageReference.direction">direction</a>}
equal to the message direction.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="MessageLabel-1057-summary"
href="#MessageLabel-1057" id=
"MessageLabel-1057-summary">MessageLabel-1057</a></td>
<td rowspan="1" colspan="1">If the <code>messageLabel</code>
<em>attribute information item</em> of a binding fault reference
<em>element information item</em> is present then its actual value
MUST match the {<a href=
"#property-InterfaceMessageReference.messagelabel">message
label</a>} of some placeholder message with {<a href=
"#property-InterfaceMessageReference.direction">direction</a>}
equal to the message direction.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="MessageLabel-1058-summary"
href="#MessageLabel-1058" id=
"MessageLabel-1058-summary">MessageLabel-1058</a></td>
<td rowspan="1" colspan="1">If the <code>messageLabel</code>
<em>attribute information item</em> of a binding fault reference
<em>element information item</em> is absent then there MUST be a
unique placeholder message with {<a href=
"#property-InterfaceMessageReference.direction">direction</a>}
equal to the message direction.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="QName-resolution-1064-summary"
href="#QName-resolution-1064" id=
"QName-resolution-1064-summary">QName-resolution-1064</a></td>
<td rowspan="1" colspan="1">A <a href=
"#component-Description">Description</a> component MUST NOT have
such broken references.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Schema-1066-summary" href=
"#Schema-1066" id="Schema-1066-summary">Schema-1066</a></td>
<td rowspan="1" colspan="1">A WSDL 2.0 document MUST NOT refer to
XML Schema components in a given namespace UNLESS an
<code>xs:import</code> or <code>xs:schema</code> <em>element
information item</em> for that namespace is present OR the
namespace is the XML Schema namespace,
http://www.w3.org/2001/XMLSchema, which contains built-in types as
defined in XML Schema Part 2: Datatypes Second Edition
[<cite><a href="#XMLSchemaP2">XML Schema:
Datatypes</a></cite>].</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Schema-1069-summary" href=
"#Schema-1069" id="Schema-1069-summary">Schema-1069</a></td>
<td rowspan="1" colspan="1">The referenced schema MUST contain a
<code>targetNamespace</code> <em>attribute information item</em> on
its <code>xs:schema</code> <em>element information item</em>.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Schema-1070-summary" href=
"#Schema-1070" id="Schema-1070-summary">Schema-1070</a></td>
<td rowspan="1" colspan="1">The value of the
<code>targetNamespace</code> <em>attribute information item</em> of
the <code>xs:schema</code> <em>element information item</em> of an
imported schema MUST equal the value of the <code>namespace</code>
of the <code>import</code> <em>element information item</em> in the
importing WSDL 2.0 document.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Schema-1073-summary" href=
"#Schema-1073" id="Schema-1073-summary">Schema-1073</a></td>
<td rowspan="1" colspan="1">A WSDL 2.0 document MUST NOT define the
same element or type in more than one inlined schema.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Schema-1075-summary" href=
"#Schema-1075" id="Schema-1075-summary">Schema-1075</a></td>
<td rowspan="1" colspan="1">A specification of extension syntax for
an alternative schema language MUST use a namespace that is
different than the namespace of XML Schema.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Schema-1076-summary" href=
"#Schema-1076" id="Schema-1076-summary">Schema-1076</a></td>
<td rowspan="1" colspan="1">The namespace used for an alternate
schema language MUST be an absolute IRI.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Schema-1079-summary" href=
"#Schema-1079" id="Schema-1079-summary">Schema-1079</a></td>
<td rowspan="1" colspan="1">If <code>wsdlx:interface</code> and
<code>wsdlx:binding</code> are used together then they MUST satisfy
the same consistency rules that apply to the {<a href=
"#property-Service.interface">interface</a>} property of a <a href=
"#component-Service">Service</a> component and the {<a href=
"#property-Endpoint.binding">binding</a>} property of a nested
<a href="#component-Endpoint">Endpoint</a> component, that is
either the binding refers the interface of the service or the
binding refers to no interface.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Types-1074-summary" href=
"#Types-1074" id="Types-1074-summary">Types-1074</a></td>
<td rowspan="1" colspan="1">A specification of extension syntax for
an alternative schema language MUST include the declaration of an
<em>element information item</em>, intended to appear as a child of
the <code>wsdl:types</code> <em>element information item</em>,
which references, names, and locates the schema instance (an
<code>import</code> <em>element information item</em>).</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Types-1077-summary" href=
"#Types-1077" id="Types-1077-summary">Types-1077</a></td>
<td rowspan="1" colspan="1">The type of the
<code>wsdlx:interface</code> <em>attribute information item</em> is
an <em>xs:QName</em> that specifies the {<a href=
"#property-Interface.name">name</a>} property of an <a href=
"#component-Interface">Interface</a> component.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Types-1078-summary" href=
"#Types-1078" id="Types-1078-summary">Types-1078</a></td>
<td rowspan="1" colspan="1">The type of the
<code>wsdlx:binding</code> <em>attribute information item</em> is
an <em>xs:QName</em> that specifies the {<a href=
"#property-Binding.name">name</a>} property of a <a href=
"#component-Binding">Binding</a> component.</td>
</tr>
</tbody>
</table>

<br />
<a name="component-assertion-summary" id=
"component-assertion-summary"></a>
<table width="100%" border="1">
<caption>Table E-2. Summary of Assertions about WSDL 2.0
Components</caption>
<col width="20%" span="1" />
<col width="80%" span="1" />
<tbody>
<tr>
<th rowspan="1" colspan="1">Id</th>
<th rowspan="1" colspan="1">Assertion</th>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Binding-1044-summary" href=
"#Binding-1044" id="Binding-1044-summary">Binding-1044</a></td>
<td rowspan="1" colspan="1">If a <a href=
"#component-Binding">Binding</a> component specifies any
operation-specific binding details (by including <a href=
"#component-BindingOperation">Binding Operation</a> components) or
any fault binding details (by including <a href=
"#component-BindingFault">Binding Fault</a> components), then it
MUST specify an interface the <a href=
"#component-Binding">Binding</a> component applies to, so as to
indicate which interface the operations come from.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Binding-1045-summary" href=
"#Binding-1045" id="Binding-1045-summary">Binding-1045</a></td>
<td rowspan="1" colspan="1">A <a href=
"#component-Binding">Binding</a> component that defines bindings
for an <a href="#component-Interface">Interface</a> component MUST
define bindings for all the operations of that <a href=
"#component-Interface">Interface</a> component.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Binding-1046-summary" href=
"#Binding-1046" id="Binding-1046-summary">Binding-1046</a></td>
<td rowspan="1" colspan="1">Similarly, whenever a reusable <a href=
"#component-Binding">Binding</a> component (i.e. one that does not
specify an <a href="#component-Interface">Interface</a> component)
is applied to a specific <a href=
"#component-Interface">Interface</a> component in the context of an
<a href="#component-Endpoint">Endpoint</a> component (see <a href=
"#Endpoint_details"><strong>2.13.1 The Endpoint
Component</strong></a>), the <a href=
"#component-Binding">Binding</a> component MUST define bindings for
each <a href="#component-InterfaceOperation">Interface
Operation</a> and <a href="#component-InterfaceFault">Interface
Fault</a> component of the <a href=
"#component-Interface">Interface</a> component, via a combination
of properties defined on the <a href=
"#component-Binding">Binding</a> component itself and default
binding rules specific to its binding type.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Binding-1047-summary" href=
"#Binding-1047" id="Binding-1047-summary">Binding-1047</a></td>
<td rowspan="1" colspan="1">A <a href=
"#component-Binding">Binding</a> component that defines bindings
for an <a href="#component-Interface">Interface</a> component MUST
define bindings for all the faults of that <a href=
"#component-Interface">Interface</a> component that are referenced
from any of the operations in that <a href=
"#component-Interface">Interface</a> component.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Binding-1048-summary" href=
"#Binding-1048" id="Binding-1048-summary">Binding-1048</a></td>
<td rowspan="1" colspan="1">This <em>xs:anyURI</em> MUST be an
absolute IRI as defined by [<cite><a href="#RFC3987">IETF RFC
3987</a></cite>].</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Binding-1049-summary" href=
"#Binding-1049" id="Binding-1049-summary">Binding-1049</a></td>
<td rowspan="1" colspan="1">For each <a href=
"#component-Binding">Binding</a> component in the {<a href=
"#property-Description.bindings">bindings</a>} property of a
<a href="#component-Description">Description</a> component, the
{<a href="#property-Binding.name">name</a>} property MUST be
unique.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="BindingFault-1050-summary"
href="#BindingFault-1050" id=
"BindingFault-1050-summary">BindingFault-1050</a></td>
<td rowspan="1" colspan="1">For each <a href=
"#component-BindingFault">Binding Fault</a> component in the
{<a href="#property-Binding.bindingfaults">binding faults</a>}
property of a <a href="#component-Binding">Binding</a> component,
the {<a href="#property-BindingFault.interfacefault">interface
fault</a>} property MUST be unique.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name=
"BindingFaultReference-1055-summary" href=
"#BindingFaultReference-1055" id=
"BindingFaultReference-1055-summary">BindingFaultReference-1055</a></td>
<td rowspan="1" colspan="1">For each <a href=
"#component-BindingFaultReference">Binding Fault Reference</a>
component in the {<a href=
"#property-BindingOperation.bindingfaultreferences">binding fault
references</a>} property of a <a href=
"#component-BindingOperation">Binding Operation</a> component, the
{<a href=
"#property-BindingFaultReference.interfacefaultreference">interface
fault reference</a>} property MUST be unique.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name=
"BindingFaultReference-1059-summary" href=
"#BindingFaultReference-1059" id=
"BindingFaultReference-1059-summary">BindingFaultReference-1059</a></td>
<td rowspan="1" colspan="1">There MUST be an <a href=
"#component-InterfaceFaultReference">Interface Fault Reference</a>
component in the {<a href=
"#property-InterfaceOperation.interfacefaultreferences">interface
fault references</a>} of the <a href=
"#component-InterfaceOperation">Interface Operation</a> being bound
with {<a href=
"#property-InterfaceFaultReference.messagelabel">message label</a>}
equal to the effective message label and with {<a href=
"#property-InterfaceFaultReference.interfacefault">interface
fault</a>} equal to an <a href=
"#component-InterfaceFault">Interface Fault</a> component with
{<a href="#property-InterfaceFault.name">name</a>} equal to the
actual value of the <code>ref</code> <em>attribute information
item</em>.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name=
"BindingMessageReference-1052-summary" href=
"#BindingMessageReference-1052" id=
"BindingMessageReference-1052-summary">BindingMessageReference-1052</a></td>
<td rowspan="1" colspan="1">For each <a href=
"#component-BindingMessageReference">Binding Message Reference</a>
component in the {<a href=
"#property-BindingOperation.bindingmessagereferences">binding
message references</a>} property of a <a href=
"#component-BindingOperation">Binding Operation</a> component, the
{<a href=
"#property-BindingMessageReference.interfacemessagereference">interface
message reference</a>} property MUST be unique.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="BindingOperation-1051-summary"
href="#BindingOperation-1051" id=
"BindingOperation-1051-summary">BindingOperation-1051</a></td>
<td rowspan="1" colspan="1">For each <a href=
"#component-BindingOperation">Binding Operation</a> component in
the {<a href="#property-Binding.bindingoperations">binding
operations</a>} property of a <a href=
"#component-Binding">Binding</a> component, the {<a href=
"#property-BindingOperation.interfaceoperation">interface
operation</a>} property MUST be unique.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="CanonFragId-1097-summary"
href="#CanonFragId-1097" id=
"CanonFragId-1097-summary">CanonFragId-1097</a></td>
<td rowspan="1" colspan="1">The fragment identifier consists of a
sequence zero or more <code>xmlns()</code> pointer parts followed
by exactly one <code>wsdl.*()</code> pointer part.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="CanonFragId-1098-summary"
href="#CanonFragId-1098" id=
"CanonFragId-1098-summary">CanonFragId-1098</a></td>
<td rowspan="1" colspan="1">Each <code>xmlns()</code> pointer part
that appears in the fragment identifier defines a namespace that is
referenced by the <code>wsdl.*()</code> pointer part.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="CanonFragId-1099-summary"
href="#CanonFragId-1099" id=
"CanonFragId-1099-summary">CanonFragId-1099</a></td>
<td rowspan="1" colspan="1">Each <code>xmlns()</code> pointer part
defines a unique namespace.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="CanonFragId-1100-summary"
href="#CanonFragId-1100" id=
"CanonFragId-1100-summary">CanonFragId-1100</a></td>
<td rowspan="1" colspan="1">The <code>xmlns()</code> pointer parts
define namespaces in the same order as they are referenced in the
<code>wsdl.*()</code> pointer part.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="CanonFragId-1101-summary"
href="#CanonFragId-1101" id=
"CanonFragId-1101-summary">CanonFragId-1101</a></td>
<td rowspan="1" colspan="1">The namespace prefixes defined by the
<code>xmlns()</code> pointer parts are named <code>ns1</code> ,
<code>ns2</code> , etc., in the order of their appearance.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="CanonFragId-1102-summary"
href="#CanonFragId-1102" id=
"CanonFragId-1102-summary">CanonFragId-1102</a></td>
<td rowspan="1" colspan="1">The fragment identifier contains no
optional whitespace.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="CanonFragId-1103-summary"
href="#CanonFragId-1103" id=
"CanonFragId-1103-summary">CanonFragId-1103</a></td>
<td rowspan="1" colspan="1">No <code>xmlns()</code> pointer part
defines a namespace for the targetNamespace of the WSDL 2.0
document.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Compare-URI-IRI-1065-summary"
href="#Compare-URI-IRI-1065" id=
"Compare-URI-IRI-1065-summary">Compare-URI-IRI-1065</a></td>
<td rowspan="1" colspan="1">When such absolute URIs and IRIs are
being compared to determine equivalence (see <a href=
"#compequiv"><strong>2.15 Equivalence of Components</strong></a>),
they MUST be compared character-by-character as indicated in
[<cite><a href="#RFC3987">IETF RFC 3987</a></cite>].</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Description-1001-summary"
href="#Description-1001" id=
"Description-1001-summary">Description-1001</a></td>
<td rowspan="1" colspan="1">The value of the
<code>targetNamespace</code> <em>attribute information item</em>
SHOULD be dereferencable.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Description-1002-summary"
href="#Description-1002" id=
"Description-1002-summary">Description-1002</a></td>
<td rowspan="1" colspan="1">It SHOULD resolve to a human or machine
processable document that directly or indirectly defines the
intended semantics of those components.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Description-1003-summary"
href="#Description-1003" id=
"Description-1003-summary">Description-1003</a></td>
<td rowspan="1" colspan="1">It MAY resolve to a WSDL 2.0 document
that provides service description information for that
namespace.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Description-1067-summary"
href="#Description-1067" id=
"Description-1067-summary">Description-1067</a></td>
<td rowspan="1" colspan="1">For each component in the imported
namespace, a corresponding <a href=
"#component-ElementDeclaration">Element Declaration</a> component
or <a href="#component-TypeDefinition">Type Definition</a>
component MUST appear in the {<a href=
"#property-Description.elementdeclarations">element
declarations</a>} or {<a href=
"#property-Description.typedefinitions">type definitions</a>}
property respectively of the <a href=
"#component-Description">Description</a> component corresponding to
the WSDL document that imports the schema, or that imports directly
or indirectly a WSDL document that imports the schema.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Description-1068-summary"
href="#Description-1068" id=
"Description-1068-summary">Description-1068</a></td>
<td rowspan="1" colspan="1">Schema components not in an imported
namespace MUST NOT appear in the {<a href=
"#property-Description.elementdeclarations">element
declarations</a>} or {<a href=
"#property-Description.typedefinitions">type definitions</a>}
properties.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Description-1071-summary"
href="#Description-1071" id=
"Description-1071-summary">Description-1071</a></td>
<td rowspan="1" colspan="1">For each component defined and declared
in the inlined schema document or included by
<code>xs:include</code>, a corresponding <a href=
"#component-ElementDeclaration">Element Declaration</a> component
or <a href="#component-TypeDefinition">Type Definition</a>
component MUST appear in the {<a href=
"#property-Description.elementdeclarations">element
declarations</a>} property or {<a href=
"#property-Description.typedefinitions">type definitions</a>}
property respectively of the <a href=
"#component-Description">Description</a> component corresponding to
the WSDL document that contains the schema, or that imports
directly or indirectly a WSDL document that contains the
schema.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Description-1072-summary"
href="#Description-1072" id=
"Description-1072-summary">Description-1072</a></td>
<td rowspan="1" colspan="1">Schema components not defined or
declared in the inlined schema document or included by
<code>xs:include</code> MUST NOT appear in the {<a href=
"#property-Description.elementdeclarations">element
declarations</a>} or {<a href=
"#property-Description.typedefinitions">type definitions</a>}
properties.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Endpoint-1061-summary" href=
"#Endpoint-1061" id="Endpoint-1061-summary">Endpoint-1061</a></td>
<td rowspan="1" colspan="1">This <em>xs:anyURI</em> MUST be an
absolute IRI as defined by [<cite><a href="#RFC3987">IETF RFC
3987</a></cite>].</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Endpoint-1062-summary" href=
"#Endpoint-1062" id="Endpoint-1062-summary">Endpoint-1062</a></td>
<td rowspan="1" colspan="1">For each <a href=
"#component-Endpoint">Endpoint</a> component in the {<a href=
"#property-Service.endpoints">endpoints</a>} property of a <a href=
"#component-Service">Service</a> component, the {<a href=
"#property-Endpoint.binding">binding</a>} property MUST either be a
<a href="#component-Binding">Binding</a> component with an
unspecified {<a href="#property-Binding.interface">interface</a>}
property or a <a href="#component-Binding">Binding</a> component
with an {<a href="#property-Binding.interface">interface</a>}
property equal to the {<a href=
"#property-Service.interface">interface</a>} property of the
<a href="#component-Service">Service</a> component.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Equivalence-1063-summary"
href="#Equivalence-1063" id=
"Equivalence-1063-summary">Equivalence-1063</a></td>
<td rowspan="1" colspan="1">Extension properties which are not
string values, sets of strings or references MUST describe their
values' equivalence rules.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Extensibility-1089-summary"
href="#Extensibility-1089" id=
"Extensibility-1089-summary">Extensibility-1089</a></td>
<td rowspan="1" colspan="1">An extension that is NOT marked as
mandatory MUST NOT invalidate the meaning of any part of a WSDL 2.0
document.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Extensibility-1090-summary"
href="#Extensibility-1090" id=
"Extensibility-1090-summary">Extensibility-1090</a></td>
<td rowspan="1" colspan="1">If a WSDL 2.0 document declares an
extension as optional (i.e., NON-mandatory), then the Web service
MUST NOT assume that the client supports that extension
<em>unless</em> the Web service knows (through some other means)
that the client has in fact elected to engage and support that
extension.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Extensibility-1091-summary"
href="#Extensibility-1091" id=
"Extensibility-1091-summary">Extensibility-1091</a></td>
<td rowspan="1" colspan="1">Therefore, the Web service MUST support
every extension that is declared as optional in the WSDL 2.0
document, in addition to supporting every extension that is
declared as mandatory.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Extension-1088-summary" href=
"#Extension-1088" id=
"Extension-1088-summary">Extension-1088</a></td>
<td rowspan="1" colspan="1">The meaning of an extension SHOULD be
defined (directly or indirectly) in a document that is available at
its namespace IRI.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="FragId-1095-summary" href=
"#FragId-1095" id="FragId-1095-summary">FragId-1095</a></td>
<td rowspan="1" colspan="1">For QNames, any prefix MUST be defined
by a preceding xmlns pointer part.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="FragId-1096-summary" href=
"#FragId-1096" id="FragId-1096-summary">FragId-1096</a></td>
<td rowspan="1" colspan="1">The fragment identifier in a WSDL 2.0
component IRI-reference MUST resolve to some component as defined
by the construction rules in <a href="#frag-ids-table">Table
A-1</a>.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="ImportInclude-1087-summary"
href="#ImportInclude-1087" id=
"ImportInclude-1087-summary">ImportInclude-1087</a></td>
<td rowspan="1" colspan="1">The semantics of an extension MUST NOT
depend on how components are brought into a component model
instance via &lt;import&gt; or &lt;include&gt;.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Interface-1009-summary" href=
"#Interface-1009" id=
"Interface-1009-summary">Interface-1009</a></td>
<td rowspan="1" colspan="1">To avoid circular definitions, an
interface MUST NOT appear in the set of interfaces it extends,
either directly or indirectly.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Interface-1010-summary" href=
"#Interface-1010" id=
"Interface-1010-summary">Interface-1010</a></td>
<td rowspan="1" colspan="1">For each <a href=
"#component-Interface">Interface</a> component in the {<a href=
"#property-Description.interfaces">interfaces</a>} property of a
<a href="#component-Description">Description</a> component, the
{<a href="#property-Interface.name">name</a>} property MUST be
unique.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Interface-1011-summary" href=
"#Interface-1011" id=
"Interface-1011-summary">Interface-1011</a></td>
<td rowspan="1" colspan="1">The list of <em>xs:QName</em> in an
<code>extends</code> <em>attribute information item</em> MUST NOT
contain duplicates.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="InterfaceFault-1013-summary"
href="#InterfaceFault-1013" id=
"InterfaceFault-1013-summary">InterfaceFault-1013</a></td>
<td rowspan="1" colspan="1">An <em>xs:token</em> with one of the
values <em>#any</em>, <em>#none</em>, <em>#other</em>, or
<em>#element</em>.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="InterfaceFault-1014-summary"
href="#InterfaceFault-1014" id=
"InterfaceFault-1014-summary">InterfaceFault-1014</a></td>
<td rowspan="1" colspan="1">When the {<a href=
"#property-InterfaceFault.messagecontentmodel">message content
model</a>} property has the value <em>#any</em> or <em>#none</em>
the {<a href="#property-InterfaceFault.elementdeclaration">element
declaration</a>} property MUST be empty.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="InterfaceFault-1015-summary"
href="#InterfaceFault-1015" id=
"InterfaceFault-1015-summary">InterfaceFault-1015</a></td>
<td rowspan="1" colspan="1">In cases where, due to an interface
extending one or more other interfaces, two or more <a href=
"#component-InterfaceFault">Interface Fault</a> components have the
same value for their {<a href=
"#property-InterfaceFault.name">name</a>} property, then the
component models of those <a href=
"#component-InterfaceFault">Interface Fault</a> components MUST be
equivalent (see <a href="#compequiv"><strong>2.15 Equivalence of
Components</strong></a>).</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="InterfaceFault-1016-summary"
href="#InterfaceFault-1016" id=
"InterfaceFault-1016-summary">InterfaceFault-1016</a></td>
<td rowspan="1" colspan="1">For the above reason, it is considered
good practice to ensure, where necessary, that the local name of
the {<a href="#property-InterfaceFault.name">name</a>} property of
<a href="#component-InterfaceFault">Interface Fault</a> components
within a namespace SHOULD be unique, thus allowing such derivation
to occur without inadvertent error.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name=
"InterfaceFaultReference-1037-summary" href=
"#InterfaceFaultReference-1037" id=
"InterfaceFaultReference-1037-summary">InterfaceFaultReference-1037</a></td>
<td rowspan="1" colspan="1">The value of this property MUST match
the name of a placeholder message defined by the message exchange
pattern.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name=
"InterfaceFaultReference-1038-summary" href=
"#InterfaceFaultReference-1038" id=
"InterfaceFaultReference-1038-summary">InterfaceFaultReference-1038</a></td>
<td rowspan="1" colspan="1">The direction MUST be consistent with
the direction implied by the fault propagation ruleset used in the
message exchange pattern of the operation.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name=
"InterfaceFaultReference-1039-summary" href=
"#InterfaceFaultReference-1039" id=
"InterfaceFaultReference-1039-summary">InterfaceFaultReference-1039</a></td>
<td rowspan="1" colspan="1">For each <a href=
"#component-InterfaceFaultReference">Interface Fault Reference</a>
component in the {<a href=
"#property-InterfaceOperation.interfacefaultreferences">interface
fault references</a>} property of an <a href=
"#component-InterfaceOperation">Interface Operation</a> component,
the combination of its {<a href=
"#property-InterfaceFaultReference.interfacefault">interface
fault</a>} and {<a href=
"#property-InterfaceFaultReference.messagelabel">message label</a>}
properties MUST be unique.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name=
"InterfaceMessageReference-1025-summary" href=
"#InterfaceMessageReference-1025" id=
"InterfaceMessageReference-1025-summary">InterfaceMessageReference-1025</a></td>
<td rowspan="1" colspan="1">An <em>xs:token</em> with one of the
values <em>in</em> or <em>out</em>, indicating whether the message
is coming to the service or going from the service,
respectively.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name=
"InterfaceMessageReference-1026-summary" href=
"#InterfaceMessageReference-1026" id=
"InterfaceMessageReference-1026-summary">InterfaceMessageReference-1026</a></td>
<td rowspan="1" colspan="1">The direction MUST be the same as the
direction of the message identified by the {<a href=
"#property-InterfaceMessageReference.messagelabel">message
label</a>} property in the {<a href=
"#property-InterfaceOperation.messageexchangepattern">message
exchange pattern</a>} of the <a href=
"#component-InterfaceOperation">Interface Operation</a> component
this is contained within.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name=
"InterfaceMessageReference-1027-summary" href=
"#InterfaceMessageReference-1027" id=
"InterfaceMessageReference-1027-summary">InterfaceMessageReference-1027</a></td>
<td rowspan="1" colspan="1">An <em>xs:token</em> with one of the
values <em>#any</em>, <em>#none</em>, <em>#other</em>, or
<em>#element</em>.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name=
"InterfaceMessageReference-1028-summary" href=
"#InterfaceMessageReference-1028" id=
"InterfaceMessageReference-1028-summary">InterfaceMessageReference-1028</a></td>
<td rowspan="1" colspan="1">When the {<a href=
"#property-InterfaceMessageReference.messagecontentmodel">message
content model</a>} property has the value <em>#any</em> or
<em>#none</em>, the {<a href=
"#property-InterfaceMessageReference.elementdeclaration">element
declaration</a>} property MUST be empty.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name=
"InterfaceMessageReference-1029-summary" href=
"#InterfaceMessageReference-1029" id=
"InterfaceMessageReference-1029-summary">InterfaceMessageReference-1029</a></td>
<td rowspan="1" colspan="1">For each <a href=
"#component-InterfaceMessageReference">Interface Message
Reference</a> component in the {<a href=
"#property-InterfaceOperation.interfacemessagereferences">interface
message references</a>} property of an <a href=
"#component-InterfaceOperation">Interface Operation</a> component,
its {<a href=
"#property-InterfaceMessageReference.messagelabel">message
label</a>} property MUST be unique.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name=
"InterfaceOperation-1018-summary" href="#InterfaceOperation-1018"
id=
"InterfaceOperation-1018-summary">InterfaceOperation-1018</a></td>
<td rowspan="1" colspan="1">This <em>xs:anyURI</em> MUST be an
absolute IRI (see [<cite><a href="#RFC3987">IETF RFC
3987</a></cite>]).</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name=
"InterfaceOperation-1019-summary" href="#InterfaceOperation-1019"
id=
"InterfaceOperation-1019-summary">InterfaceOperation-1019</a></td>
<td rowspan="1" colspan="1">These <em>xs:anyURI</em>s MUST be
absolute IRIs (see [<cite><a href="#RFC3986">IETF RFC
3986</a></cite>]).</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name=
"InterfaceOperation-1020-summary" href="#InterfaceOperation-1020"
id=
"InterfaceOperation-1020-summary">InterfaceOperation-1020</a></td>
<td rowspan="1" colspan="1">In cases where, due to an interface
extending one or more other interfaces, two or more <a href=
"#component-InterfaceOperation">Interface Operation</a> components
have the same value for their {<a href=
"#property-InterfaceOperation.name">name</a>} property, then the
component models of those Interface Operation components MUST be
equivalent (see <a href="#compequiv"><strong>2.15 Equivalence of
Components</strong></a>).</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name=
"InterfaceOperation-1021-summary" href="#InterfaceOperation-1021"
id=
"InterfaceOperation-1021-summary">InterfaceOperation-1021</a></td>
<td rowspan="1" colspan="1">For the above reason, it is considered
good practice to ensure, where necessary, that the {<a href=
"#property-InterfaceOperation.name">name</a>} property of <a href=
"#component-InterfaceOperation">Interface Operation</a> components
within a namespace SHOULD be unique, thus allowing such derivation
to occur without inadvertent error.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name=
"InterfaceOperation-1023-summary" href="#InterfaceOperation-1023"
id=
"InterfaceOperation-1023-summary">InterfaceOperation-1023</a></td>
<td rowspan="1" colspan="1">An <a href=
"#component-InterfaceOperation">Interface Operation</a> component
MUST satisfy the specification defined by each operation style
identified by its {<a href=
"#property-InterfaceOperation.style">style</a>} property.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Location-1093-summary" href=
"#Location-1093" id="Location-1093-summary">Location-1093</a></td>
<td rowspan="1" colspan="1">Its actual value MUST be a list of
pairs of IRIs; where the first IRI of a pair, which MUST be an
absolute IRI as defined in [<cite><a href="#RFC3987">IETF RFC
3987</a></cite>], indicates a WSDL 2.0 (or 1.1) namespace name,
and, the second a hint as to the location of a WSDL 2.0 document
defining WSDL 2.0 components (or WSDL 1.1 elements [<cite><a href=
"#WSDL11">WSDL 1.1</a></cite>]) for that namespace name.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="MEP-1022-summary" href=
"#MEP-1022" id="MEP-1022-summary">MEP-1022</a></td>
<td rowspan="1" colspan="1">A message exchange pattern is itself
uniquely identified by an absolute IRI, which is used as the value
of the {<a href=
"#property-InterfaceOperation.messageexchangepattern">message
exchange pattern</a>} property of the <a href=
"#component-InterfaceOperation">Interface Operation</a> component,
and which specifies the fault propagation ruleset that its faults
obey.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="MessageLabel-1024-summary"
href="#MessageLabel-1024" id=
"MessageLabel-1024-summary">MessageLabel-1024</a></td>
<td rowspan="1" colspan="1">The value of this property MUST match
the name of a placeholder message defined by the message exchange
pattern.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Service-1060-summary" href=
"#Service-1060" id="Service-1060-summary">Service-1060</a></td>
<td rowspan="1" colspan="1">For each <a href=
"#component-Service">Service</a> component in the {<a href=
"#property-Description.services">services</a>} property of a
<a href="#component-Description">Description</a> component, the
{<a href="#property-Service.name">name</a>} property MUST be
unique.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Types-1007-summary" href=
"#Types-1007" id="Types-1007-summary">Types-1007</a></td>
<td rowspan="1" colspan="1">Each XML Schema element declaration
MUST have a unique QName.</td>
</tr>
<tr>
<td rowspan="1" colspan="1"><a name="Types-1008-summary" href=
"#Types-1008" id="Types-1008-summary">Types-1008</a></td>
<td rowspan="1" colspan="1">Each XML Schema type definition MUST
have a unique QName.</td>
</tr>
</tbody>
</table>

<br /></div>
</body>
</html>