discontinued / server · Files

issues.html?type=1 316 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 
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8" /><title>TAG Issues List</title><link id="normalLink" href="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/issues.css" media="screen" rel="stylesheet" title="Normal view" type="text/css" /><link id="directorLink" href="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/director.css" rel="alternate stylesheet" media="screen" title="Director view" type="text/css" /><link id="wgLink" href="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/wg.css" rel="alternate stylesheet" media="screen" title="Working Group view" type="text/css" /><link id="closedLink" href="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/closed.css" rel="alternate stylesheet" media="screen" title="closed issues" type="text/css" /><link id="deadlineLink" href="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/deadline.css" rel="alternate stylesheet" media="screen" title="deadlines" type="text/css" /><link id="categoriesLink" href="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/categories.css" rel="alternate stylesheet" media="screen" title="categories" type="text/css" /><link id="typeLink" href="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/type.css" rel="alternate stylesheet" media="screen" title="types" type="text/css" /><link id="actionLink" href="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/action.css" rel="alternate stylesheet" media="screen" title="actions" type="text/css" /><link id="decisionLink" href="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/decision.css" rel="alternate stylesheet" media="screen" title="decisions" type="text/css" /><link id="requestLink" href="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/request.css" rel="alternate stylesheet" media="screen" title="requests" type="text/css" /><link id="proposalLink" href="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/proposal.css" rel="alternate stylesheet" media="screen" title="proposals" type="text/css" /><link id="errorLink" href="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/error.css" rel="alternate stylesheet" media="screen" title="errors" type="text/css" /><link id="clarificationLink" href="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/clarification.css" rel="alternate stylesheet" media="screen" title="clarifications" type="text/css" /><link id="editorialLink" href="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/editorial.css" rel="alternate stylesheet" media="screen" title="editorials" type="text/css" /><link id="expertLink" href="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/expertMode.css" rel="alternate stylesheet" media="screen" title="expert" type="text/css" /><link id="stateAgreedLink" href="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/stateAgreedMode.css" rel="alternate stylesheet" media="screen" title="stateAgreed" type="text/css" /><link id="stateDeclinedLink" href="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/stateDeclinedMode.css" rel="alternate stylesheet" media="screen" title="stateDeclined" type="text/css" /><link id="stateNoDecisionLink" href="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/stateNoDecisionMode.css" rel="alternate stylesheet" media="screen" title="stateNoDecision" type="text/css" /><link id="stateSubsumedLink" href="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/stateSubsumedMode.css" rel="alternate stylesheet" media="screen" title="stateSubsumed" type="text/css" /><link id="ackAgreedLink" href="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/ackAgreedMode.css" rel="alternate stylesheet" media="screen" title="stateAgreed" type="text/css" /><link id="ackReplyUnaddressedLink" href="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/ackReplyUnaddressedMode.css" rel="alternate stylesheet" media="screen" title="stateReplyUnaddressed" type="text/css" /><link id="ackNoReplyLink" href="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/ackNoReplyMode.css" rel="alternate stylesheet" media="screen" title="stateNoReply" type="text/css" /><link href="local.css" rel="stylesheet" media="screen" type="text/css" /><script type="text/javascript" src="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/view.js"> </script><script type="text/javascript" src="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/view-summary.js"> </script></head><body onload="init()"><!-- ################################################# --><!-- THIS PAGE HAS BEEN GENERATED! DO NOT EDIT! --><!-- ################################################# --><h1><a href="http://www.w3.org/" title="W3C Home"><img alt="W3C" height="48" src="http://www.w3.org/Icons/w3c_home" width="72" border="0" /></a> TAG Issues List</h1><map id="insidenav"><p>
	  Inside: <a href="#summaryList">Issue summary</a> 
	  | <a href="#state">State description</a> 
	  | <a href="#decision">Decision cycle description</a> 
	  | <a href="#detailsList">Issue details</a>
            (<a href="http://www.w3.org/2001/03/webdata/xsv?docAddrs=http://www.w3.org/2001/tag/issues.xml&amp;warnings=on&amp;keepGoing=on&amp;style=xsl">Validate data</a>)
	</p></map><p>
				This is the list of general issues the TAG has
				considered
			</p><h2>Status of this Document</h2><p><em>
					As of 28 Aug 2007 the TAG has transitioned its
					issues list and action item tracking to
					<a href="http://www.w3.org/2005/06/tracker/">
						Tracker
					</a>
					.
				</em></p><p style="background-color: #fdd; font-size: 200%; margin: 4em; border: solid black 0.1em; border-radius:  1em; padding: 3em">
				This list remains as a HISTORICAL REFERENCE ONLY.
                                The issues list actually used by the TAG is its
				<a href="http://www.w3.org/2001/tag/group/track/">
					Tracker Page
				</a>
				.
			</p><p>
				Tracker page URIs for TAG issues are of the form
				<a href="http://www.w3.org/2001/tag/group/track/issues/">
					http://www.w3.org/2001/tag/group/track/issues/&lt;number&gt;
				</a>
				where &lt;number&gt; is the numeric value at the end of
				each issues' nick name. For example, the tracker page
				for
				<a href="http://www.w3.org/2001/tag/issues#httpRange-14">
					httpRange-14
				</a>
				is
				<a href="http://www.w3.org/2001/tag/group/track/issues/14">
					http://www.w3.org/2001/tag/group/track/issues/14
				</a>
				.
			</p><p>
				See the
				<a href="issues-about">
					TAG issue tracking policy
				</a>
				(and
				<a href="/2001/tag/Overview#tag-attn">tips</a>
				for getting the TAG's attention). See also
				<a href="http://lists.w3.org/Archives/Member/tag/2003Jul/0054">
					Dan Connolly suggested tactics for addressing new
					issues
				</a>
				.
			</p><p>
				For more information about the TAG, refer to the
				<a href="http://www.w3.org/2001/tag/">
					TAG Home Page
				</a>
				.
			</p><div class="summary"><h2><a id="summaryList" name="summaryList">Issue summary</a>
	(56 issues)
      </h2><form id="form" method="get" action="issues.html"><fieldset><legend accesskey="4">Reformat summary with options</legend><label title="Select a view" for="view">Highlight for</label>:
	  <select name="view" id="view"><option value="normal" id="normalOption">Normal</option><option value="director" id="directorOption">Director</option><option value="wg" id="wgOption">Working group</option></select><input type="submit" value="Reformat" title="Reformat" /><div><label title="closed issues"><input type="checkbox" value="1" name="closed" id="closedCheckbox" /> Show open issues only</label><label title="Expert mode"><input type="checkbox" value="1" name="expert" id="expertCheckbox" /> Expert mode</label></div><fieldset class="expertMode"><legend accesskey="5">Expert mode options</legend><div>
	      Hide columns:
	      <label title="deadline"><input type="checkbox" value="1" name="deadline" id="deadlineCheckbox" />deadline</label><label title="categories"><input type="checkbox" value="1" name="categories" id="categoriesCheckbox" />categories</label><label title="type"><input type="checkbox" value="1" name="type" id="typeCheckbox" />type</label><label title="action"><input type="checkbox" value="1" name="action" id="actionCheckbox" />action</label><label title="action"><input type="checkbox" value="1" name="decision" id="decisionCheckbox" />ack.</label></div><div id="TypeOptions">
	      Hide issues by type:
	      <label title="editorial"><input type="checkbox" value="1" name="editorial" id="editorialCheckbox" />editorial</label><label title="clarification"><input type="checkbox" value="1" name="clarification" id="clarificationCheckbox" />clarification</label><label title="error"><input type="checkbox" value="1" name="error" id="errorCheckbox" />error</label><label title="proposal"><input type="checkbox" value="1" name="proposal" id="proposalCheckbox" />proposal</label><label title="request"><input type="checkbox" value="1" name="request" id="requestCheckbox" />request</label></div><div id="StateOptions">
	      Hide issues by state:
	      <label title="state-agreed"><input type="checkbox" value="1" name="stateAgreed" id="stateAgreedCheckbox" />agreed</label><label title="state-declined"><input type="checkbox" value="1" name="stateDeclined" id="stateDeclinedCheckbox" />declined</label><label title="state-subsumed"><input type="checkbox" value="1" name="stateSubsumed" id="stateSubsumedCheckbox" />subsumed</label><label title="state-nodecision"><input type="checkbox" value="1" name="stateNoDecision" id="stateNoDecisionCheckbox" />no decision</label></div><div id="AckOptions">
	      Hide issues by acknowledgment:
	      <label title="ack-agreed"><input type="checkbox" value="1" name="ackAgreed" id="ackAgreedCheckbox" />agreed</label><label title="ack-replyunaddressed"><input type="checkbox" value="1" name="ackReplyUnaddressed" id="ackReplyUnaddressed" />reply unaddressed</label><label title="ack-noreply"><input type="checkbox" value="1" name="ackNoReply" id="ackNoReplyCheckbox" />no reply from reviewer</label></div></fieldset></fieldset></form><map id="outsidenav"><p>
	  Other views: <a href="graph_types.svg">types</a> | <a href="graph_states.svg">states</a> | <a href="concerning.html">concerning</a> | <a href="originators.html">reviewers</a> | 
	    <a href="actions.html">open actions</a></p></map><form method="get" action="http://www.w3.org/2000/06/webdata/xslt"><p>Changes between dates (YYYY-MM-DD) <input type="text" size="10" name="sd" /> and <input type="text" size="10" name="ed" /> [Optional] <input type="submit" value="Changes" /><input type="hidden" name="xslfile" value="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/changes.xsl" /><input type="hidden" name="xmlfile" value="http://www.w3.org/2001/tag/issues.xml" /><input type="hidden" name="uri-to-issues-xml" value="http://www.w3.org/2001/tag/issues.xml" /><input type="hidden" name="relativeURI" value="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/" /></p></form><map id="creationnav"><p>
          For maintainers: <a href="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/create.html">new issue data</a> |
                  <a href="http://dev.w3.org/cvsweb/~checkout~/2002/issues/xsl/new_list.html">new issues list data</a></p></map><p class="legend">Color key: 
                    <span class="key error">error</span> <span class="key warning">warning</span> <span class="key note">note</span></p><table><tbody><tr><th class="title">
                    Id:Title
                  </th><th class="state"><a href="state_sort.html">State</a></th><th class="type"><a href="type_sort.html">Type</a></th><th class="categories">Category</th><th class="action">Open actions</th><th class="decision"><a href="ack_sort.html">Ack.</a></th></tr><tr class="issue open request state-nodecision"><td class="title"><a href="#w3cMediaType-1">w3cMediaType-1</a> :
    Should W3C WGs define their own media types?</td><td class="state accepted">no decision<br />(accepted)</td><td class="type">request</td><td class="categories"></td><td class="action"><!--empty--></td><td class="decision"><!--empty--></td></tr><tr class="issue closed request state-agreed ack-noreply"><td class="title"><a href="#customMediaType-2">customMediaType-2</a> :
    
				What commonality should there be among W3C media types?
			</td><td class="state decided agreed">agreed</td><td class="type">request</td><td class="categories"></td><td class="action"><!--empty--></td><td class="decision agreed noreply">No reply from reviewer</td></tr><tr class="issue closed request state-subsumed"><td class="title"><a href="#nsMediaType-3">nsMediaType-3</a> :
    
				Relationship between media types and namespaces?
			</td><td class="state decided subsumed">subsumed<br />[<a href="#mixedNamespaceMeaning-13">mixedNamespaceMeaning-13</a>]</td><td class="type">request</td><td class="categories"></td><td class="action"><!--empty--></td><td class="decision"><!--empty--></td></tr><tr class="issue closed request state-declined ack-noreply"><td class="title"><a href="#xformsReview-4">xformsReview-4</a> :
    Request to review XForms Last Call document</td><td class="state decided declined">declined</td><td class="type">request</td><td class="categories"></td><td class="action"><!--empty--></td><td class="decision declined noreply">No reply from reviewer</td></tr><tr class="issue closed request state-declined ack-noreply"><td class="title"><a href="#uncefactLiaison-5">uncefactLiaison-5</a> :
    
				Invitation to create liaison with UN/CEFACT ebTWG
				Architecture Group
			</td><td class="state decided declined">declined</td><td class="type">request</td><td class="categories"></td><td class="action"><!--empty--></td><td class="decision declined noreply">No reply from reviewer</td></tr><tr class="issue closed request state-agreed ack-agreement"><td class="title"><a href="#rdfmsQnameUriMapping-6">rdfmsQnameUriMapping-6</a> :
    Algorithm for creating a URI from a QName?</td><td class="state decided agreed">agreed</td><td class="type">request</td><td class="categories"></td><td class="action"><!--empty--></td><td class="decision acknowledged agreement">Agreement</td></tr><tr class="issue open request state- ack-"><td class="title"><a href="#whenToUseGet-7">whenToUseGet-7</a> :
    
				(1) GET should be encouraged, not deprecated, in XForms
				(2) How to handle safe queries (New POST-like method?
				GET plus a body?)
			</td><td class="state decided accepted">accepted</td><td class="type">request</td><td class="categories"></td><td class="action"><!--empty--></td><td class="decision noresponse">No response to reviewer</td></tr><tr class="issue open request state-nodecision"><td class="title"><a href="#namespaceDocument-8">namespaceDocument-8</a> :
    
				What should a "namespace document" look like?
			</td><td class="state accepted">no decision<br />(accepted)</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><ol><li title="track progress of #int bug 1974 in the XML Schema namespace document in the XML Schema WG. Confirmed 5 Oct 2006 ." class="proposal">
						HT
					 proposal</li><li title="Provide a set of test cases of ways in which RDDL is actually used." class="proposal">NW proposal</li><li title="Start an ontology including docns/documentElementNamespace." class="proposal">
						DC
					 proposal</li></ol></td><td class="decision"><!--empty--></td></tr><tr class="issue closed request state-agreed ack-noreply"><td class="title"><a href="#uriMediaType-9">uriMediaType-9</a> :
    Why does the Web use mime types and not URIs?</td><td class="state decided agreed">agreed</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><!--empty--></td><td class="decision agreed noreply">No reply from reviewer</td></tr><tr class="issue closed request state-declined ack-noreply"><td class="title"><a href="#xmlSW-10">xmlSW-10</a> :
    
				Should next version of XML be XML 1.0 - DTDs +
				namespaces + xml:base + the infoset?
			</td><td class="state decided declined">declined</td><td class="type">request</td><td class="categories"></td><td class="action"><!--empty--></td><td class="decision declined noreply">No reply from reviewer</td></tr><tr class="issue closed request state-declined ack-noreply"><td class="title"><a href="#soapRPCURI-11">soapRPCURI-11</a> :
    
				What is the appropriate relationship between SOAP RPC
				and the Web's reliance on URIs?
			</td><td class="state decided declined">declined</td><td class="type">request</td><td class="categories"></td><td class="action"><!--empty--></td><td class="decision declined noreply">No reply from reviewer</td></tr><tr class="issue closed request state-declined ack-noreply"><td class="title"><a href="#xmlAsText-12">xmlAsText-12</a> :
    
				Do proposed changes to XML 1.1 ignore Unicode
				constraints?
			</td><td class="state decided declined">declined</td><td class="type">request</td><td class="categories"></td><td class="action"><!--empty--></td><td class="decision declined noreply">No reply from reviewer</td></tr><tr class="issue closed request state-subsumed"><td class="title"><a href="#mixedNamespaceMeaning-13">mixedNamespaceMeaning-13</a> :
    
				What is the meaning of a document composed of content in
				mixed namespaces?
			</td><td class="state decided subsumed">subsumed<br />[<a href="#mixedUIXMLNamespace-33">mixedUIXMLNamespace-33</a>, <a href="#xmlFunctions-34">xmlFunctions-34</a>, <a href="#RDFinXHTML-35">RDFinXHTML-35</a>]</td><td class="type">request</td><td class="categories"></td><td class="action"><!--empty--></td><td class="decision"><!--empty--></td></tr><tr class="issue open request state-agreed ack-noreply"><td class="title"><a href="#httpRange-14">httpRange-14</a> :
    
				What is the range of the HTTP dereference function?
			</td><td class="state decided agreed">agreed</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><ol><li title="Rhys to revise Dereferencing HTTP URIs finding in response to F2F discussion. Continued: 9 July 2007" class="proposal">
						RL
					 proposal</li></ol></td><td class="decision agreed noreply">No reply from reviewer</td></tr><tr class="issue closed request state-agreed ack-agreement"><td class="title"><a href="#URIEquivalence-15">URIEquivalence-15</a> :
    
				When are two URI variants considered equivalent?
			</td><td class="state decided agreed">agreed</td><td class="type">request</td><td class="categories"></td><td class="action"><!--empty--></td><td class="decision acknowledged agreement">Agreement</td></tr><tr class="issue open request state-nodecision"><td class="title"><a href="#HTTPSubstrate-16">HTTPSubstrate-16</a> :
    
				Should HTTP be used as a substrate protocol? Does W3C
				agree with RFC 3205?
			</td><td class="state deferred">no decision<br />(deferred)</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><!--empty--></td><td class="decision"><!--empty--></td></tr><tr class="issue closed request state-agreed ack-noreply"><td class="title"><a href="#charmodReview-17">charmodReview-17</a> :
    
				Request to review "Character Model for the
				Web" Last Call document
			</td><td class="state decided agreed">agreed</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><!--empty--></td><td class="decision agreed noreply">No reply from reviewer</td></tr><tr class="issue closed request state-agreed ack-agreement"><td class="title"><a href="#qnameAsId-18">qnameAsId-18</a> :
    Is it ok to use Qnames as Identifiers?</td><td class="state decided agreed">agreed</td><td class="type">request</td><td class="categories"></td><td class="action"><!--empty--></td><td class="decision acknowledged agreement">Agreement</td></tr><tr class="issue closed request state-agreed ack-noreply"><td class="title"><a href="#formattingProperties-19">formattingProperties-19</a> :
    
				Reuse existing formatting properties/names, coordinate
				new ones
			</td><td class="state decided agreed">agreed</td><td class="type">request</td><td class="categories"></td><td class="action"><!--empty--></td><td class="decision agreed noreply">No reply from reviewer</td></tr><tr class="issue closed request state-agreed ack-agreement"><td class="title"><a href="#errorHandling-20">errorHandling-20</a> :
    
				What should specifications say about error handling?
			</td><td class="state decided agreed">agreed</td><td class="type">request</td><td class="categories"></td><td class="action"><!--empty--></td><td class="decision acknowledged agreement">Agreement</td></tr><tr class="issue closed request state-agreed ack-noreply"><td class="title"><a href="#RFC3023Charset-21">RFC3023Charset-21</a> :
    
				Do all "shoulds" of RFC 3023 section 7.1
				apply?
			</td><td class="state decided agreed">agreed</td><td class="type">request</td><td class="categories"></td><td class="action"><!--empty--></td><td class="decision agreed noreply">No reply from reviewer</td></tr><tr class="issue closed request state-agreed ack-agreement"><td class="title"><a href="#augmentedInfoset-22">augmentedInfoset-22</a> :
    Infoset augmentation outside of PSVI?</td><td class="state decided agreed">agreed</td><td class="type">request</td><td class="categories"></td><td class="action"><!--empty--></td><td class="decision acknowledged agreement">Agreement</td></tr><tr class="issue open request state-agreed ack-"><td class="title"><a href="#xlinkScope-23">xlinkScope-23</a> :
    What is the scope of using XLink?</td><td class="state decided agreed">agreed</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><!--empty--></td><td class="decision noresponse">No response to reviewer</td></tr><tr class="issue closed request state-agreed ack-agreement"><td class="title"><a href="#contentTypeOverride-24">contentTypeOverride-24</a> :
    
				Can a specification include rules for overriding HTTP
				content type parameters?
			</td><td class="state decided agreed">agreed</td><td class="type">request</td><td class="categories"></td><td class="action"><!--empty--></td><td class="decision acknowledged agreement">Agreement</td></tr><tr class="issue closed request state-agreed ack-agreement"><td class="title"><a href="#deepLinking-25">deepLinking-25</a> :
    
				What to say in defense of principle that deep linking is
				not an illegal act?
			</td><td class="state decided agreed">agreed</td><td class="type">request</td><td class="categories"></td><td class="action"><!--empty--></td><td class="decision acknowledged agreement">Agreement</td></tr><tr class="issue open request state-agreed ack-"><td class="title"><a href="#contentPresentation-26">contentPresentation-26</a> :
    
				Separation of semantic and presentational markup, to the
				extent possible, is architecturally sound.
			</td><td class="state decided agreed">agreed</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><!--empty--></td><td class="decision noresponse">No response to reviewer</td></tr><tr class="issue open request state-nodecision"><td class="title"><a href="#IRIEverywhere-27">IRIEverywhere-27</a> :
    
				Should W3C specifications start promoting IRIs?
			</td><td class="state accepted">no decision<br />(accepted)</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><ol><li title="TimBL to clarify http://www.w3.org/2003/04/iri , perhaps by using N3" class="proposal">
						TBL
					 proposal</li></ol></td><td class="decision"><!--empty--></td></tr><tr class="issue open request state-agreed ack-"><td class="title"><a href="#fragmentInXML-28">fragmentInXML-28</a> :
    Use of fragment identifiers in XML</td><td class="state decided agreed">agreed</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><!--empty--></td><td class="decision noresponse">No response to reviewer</td></tr><tr class="issue closed request state-agreed ack-noreply"><td class="title"><a href="#xmlProfiles-29">xmlProfiles-29</a> :
    
				When, whither and how to profile W3C specifications in
				the XML Family
			</td><td class="state decided agreed">agreed</td><td class="type">request</td><td class="categories"></td><td class="action"><!--empty--></td><td class="decision agreed noreply">No reply from reviewer</td></tr><tr class="issue open request state-nodecision"><td class="title"><a href="#binaryXML-30">binaryXML-30</a> :
    Standardize a "binary XML" format?</td><td class="state deferred">no decision<br />(deferred)</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><!--empty--></td><td class="decision"><!--empty--></td></tr><tr class="issue closed request state-agreed ack-noreply"><td class="title"><a href="#metadataInURI-31">metadataInURI-31</a> :
    
				Should metadata (e.g., versioning information) be
				encoded in URIs?
			</td><td class="state decided agreed">agreed</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><!--empty--></td><td class="decision agreed noreply">No reply from reviewer</td></tr><tr class="issue open request state-agreed ack-"><td class="title"><a href="#xmlIDSemantics-32">xmlIDSemantics-32</a> :
    
				How should the problem of identifying ID semantics in
				XML languages be addressed in the absence of a DTD?
			</td><td class="state decided agreed">agreed</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><!--empty--></td><td class="decision noresponse">No response to reviewer</td></tr><tr class="issue open request state-nodecision"><td class="title"><a href="#mixedUIXMLNamespace-33">mixedUIXMLNamespace-33</a> :
    
				Composability for user interface-oriented XML namespaces
			</td><td class="state deferred">no decision<br />(deferred)</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><!--empty--></td><td class="decision"><!--empty--></td></tr><tr class="issue open request state-nodecision"><td class="title"><a href="#xmlFunctions-34">xmlFunctions-34</a> :
    
				XML Transformation and composability (e.g., XSLT,
				XInclude, Encryption)
			</td><td class="state accepted">no decision<br />(accepted)</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><ol><li title="summarize history of DTD/namespace/mimetype version practice, including XHTML, SOAP, and XSLT. Confirmed on 11 Dec 2006 ." class="proposal">
						TVR
					 proposal</li><li title="Henry to prepare new draft of xmlFunctions-34 by mid-July" class="proposal">
						HT
					 proposal</li></ol></td><td class="decision"><!--empty--></td></tr><tr class="issue open request state-nodecision"><td class="title"><a href="#RDFinXHTML-35">RDFinXHTML-35</a> :
    
				Syntax and semantics for embedding RDF in XHTML
			</td><td class="state deferred">no decision<br />(deferred)</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><ol><li title="DanC to ask Mimasa and Mark Birbeck about feasability of using substitution groups in XHTML modularization, cc public-xml-versioning" class="proposal">
						DC
					 proposal</li></ol></td><td class="decision"><!--empty--></td></tr><tr class="issue open request state-nodecision"><td class="title"><a href="#siteData-36">siteData-36</a> :
    
				Web site metadata improving on robots.txt, w3c/p3p and
				favicon etc.
			</td><td class="state accepted">no decision<br />(accepted)</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><!--empty--></td><td class="decision"><!--empty--></td></tr><tr class="issue open request state-nodecision"><td class="title"><a href="#abstractComponentRefs-37">abstractComponentRefs-37</a> :
    
				Definition of abstract components with namespace names
				and frag ids
			</td><td class="state accepted">no decision<br />(accepted)</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><!--empty--></td><td class="decision"><!--empty--></td></tr><tr class="issue closed request state-agreed ack-noreply"><td class="title"><a href="#putMediaType-38">putMediaType-38</a> :
    
				Relation of HTTP PUT to GET, and whether client headers
				to server are authoritative
			</td><td class="state decided agreed">agreed</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><!--empty--></td><td class="decision agreed noreply">No reply from reviewer</td></tr><tr class="issue open request state-nodecision"><td class="title"><a href="#rdfURIMeaning-39">rdfURIMeaning-39</a> :
    Meaning of URIs in RDF documents</td><td class="state accepted">no decision<br />(accepted)</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><!--empty--></td><td class="decision"><!--empty--></td></tr><tr class="issue open request state-nodecision"><td class="title"><a href="#URIGoodPractice-40">URIGoodPractice-40</a> :
    What are good practices for URI construction?</td><td class="state accepted">no decision<br />(accepted)</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><!--empty--></td><td class="decision"><!--empty--></td></tr><tr class="issue open request state-nodecision"><td class="title"><a href="#XMLVersioning-41">XMLVersioning-41</a> :
    
				What are good practices for designing extensible XML
				languages and for handling versioning?
			</td><td class="state accepted">no decision<br />(accepted)</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><ol><li title="Review definitions of partial understanding, backward compatible, and forward compatible. Progress report , confirmed 5 Oct 2006 , 9 July 2007 ." class="proposal">
						DC
					 proposal</li><li title="NM to draft a blog item for review and, pending creation of a TAG blog mechanism, post it. Continued: 9 July 2007 ." class="proposal">
						NM
					 proposal</li><li title="NM to write up his paper comments on extensibility and versioning Continued: 9 July 2007 ." class="proposal">
						NM
					 proposal</li></ol></td><td class="decision"><!--empty--></td></tr><tr class="issue open request state-nodecision"><td class="title"><a href="#ultimateQuestion-42">ultimateQuestion-42</a> :
    
				What is the answer to life, the universe, and
				everything.
			</td><td class="state accepted">no decision<br />(accepted)</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><ol><li title="Noah to revise Self-Describing Web finding in response to F2F discussion." class="proposal">
						NM
					 proposal</li><li title="NM to contact Don Brutzman to query about possible contacts about naming in V-Ws and integration with the Web." class="proposal">
						NM
					 proposal</li></ol></td><td class="decision"><!--empty--></td></tr><tr class="issue open request state-nodecision"><td class="title"><a href="#DerivedResources-43">DerivedResources-43</a> :
    How are secondary resources derived?</td><td class="state accepted">no decision<br />(accepted)</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><!--empty--></td><td class="decision"><!--empty--></td></tr><tr class="issue closed request state-agreed ack-noreply"><td class="title"><a href="#xmlChunk-44">xmlChunk-44</a> :
    Chunk of XML - Canonicalization and equality</td><td class="state decided agreed">agreed</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><!--empty--></td><td class="decision agreed noreply">No reply from reviewer</td></tr><tr class="issue open request state-nodecision"><td class="title"><a href="#mediaTypeManagement-45">mediaTypeManagement-45</a> :
    
				What is the appropriate level of granularity of the
				media type mechanism?
			</td><td class="state accepted">no decision<br />(accepted)</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><!--empty--></td><td class="decision"><!--empty--></td></tr><tr class="issue open request state-nodecision"><td class="title"><a href="#xml11Names-46">xml11Names-46</a> :
    
				Impact of changes to XML 1.1 on other XML Specifications
			</td><td class="state accepted">no decision<br />(accepted)</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><!--empty--></td><td class="decision"><!--empty--></td></tr><tr class="issue open request state-nodecision"><td class="title"><a href="#endPointRefs-47">endPointRefs-47</a> :
    
				WS-Addressing SOAP binding &amp; app protocols
			</td><td class="state accepted">no decision<br />(accepted)</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><!--empty--></td><td class="decision"><!--empty--></td></tr><tr class="issue closed request state-agreed ack-noreply"><td class="title"><a href="#nameSpaceState-48">nameSpaceState-48</a> :
    Adding terms to a namespace</td><td class="state decided agreed">agreed</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><!--empty--></td><td class="decision agreed noreply">No reply from reviewer</td></tr><tr class="issue open request state-nodecision"><td class="title"><a href="#schemeProtocols-49">schemeProtocols-49</a> :
    
				Relationship of URI schemes to protocols and operations
			</td><td class="state accepted">no decision<br />(accepted)</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><!--empty--></td><td class="decision"><!--empty--></td></tr><tr class="issue open request state-nodecision"><td class="title"><a href="#URNsAndRegistries-50">URNsAndRegistries-50</a> :
    URIs, URNs, "location independent" naming systems and associated registries for naming on the Web</td><td class="state accepted">no decision<br />(accepted)</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><ol><li title="DO to explore the space of external registries and to post to the tag member list." class="proposal">
						DO
					 proposal</li><li title="Henry to revise URNsAndRegistries-50 finding in response to F2F discussion." class="proposal">
						HT
					 proposal</li></ol></td><td class="decision"><!--empty--></td></tr><tr class="issue open request state-nodecision"><td class="title"><a href="#standardizedFieldValues-51">standardizedFieldValues-51</a> :
    
				Squatting on link relationship names, x-tokens,
				registries, and URI-based extensibility
			</td><td class="state accepted">no decision<br />(accepted)</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><!--empty--></td><td class="decision"><!--empty--></td></tr><tr class="issue open request state-nodecision"><td class="title"><a href="#passwordsInTheClear-52">passwordsInTheClear-52</a> :
    Sending passwords in the clear</td><td class="state accepted">no decision<br />(accepted)</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><!--empty--></td><td class="decision"><!--empty--></td></tr><tr class="issue closed request state-agreed ack-noreply"><td class="title"><a href="#genericResources-53">genericResources-53</a> :
    Generic resources</td><td class="state decided agreed">agreed</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><!--empty--></td><td class="decision agreed noreply">No reply from reviewer</td></tr><tr class="issue open request state-nodecision"><td class="title"><a href="#TagSoupIntegration-54">TagSoupIntegration-54</a> :
    Tag soup integration</td><td class="state accepted">no decision<br />(accepted)</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><!--empty--></td><td class="decision"><!--empty--></td></tr><tr class="issue open request state-nodecision"><td class="title"><a href="#utf7Encoding-55">utf7Encoding-55</a> :
    Security issues with incorrect metadata</td><td class="state accepted">no decision<br />(accepted)</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><!--empty--></td><td class="decision"><!--empty--></td></tr><tr class="issue open request state-nodecision"><td class="title"><a href="#abbreviatedURIs-56">abbreviatedURIs-56</a> :
    Abbreviating URIs in Web Languages</td><td class="state accepted">no decision<br />(accepted)</td><td class="type">request</td><td class="categories"><!--empty--></td><td class="action"><ol><li title="Look at the difference between QNAME in XML and SPARQL [Aside theses are the closest references the chair was able to find to the transfer of this action item]" class="proposal">SW proposal</li></ol></td><td class="decision"><!--empty--></td></tr></tbody></table></div><div class="documentation"><div class="state"><h2><a id="state" name="state">State description</a></h2><ul><li><a id="state_raised" name="state_raised">Raised</a>:
	  Initial state; The group has not accepted the issue yet.
	</li><li><a id="state_accepted" name="state_accepted">Accepted</a>:
	  Initial state; The group has agreed to address the issue.
	</li><li><a id="state_deferred" name="state_deferred">Deferred</a>:
	  The Group has not reached a decision on this issue, but does
	  not intend to work on it further without new input.
	</li><li><a id="state_agreed" name="state_agreed">agreed</a>:
	  The Group has made a decision and decided to follow the
	  suggestion.
	</li><li><a id="state_declined" name="state_declined">Declined</a>:
	  The Group has decided not to address this issue.
	</li><li><a id="state_moved" name="state_moved">Moved</a>: 
	  The issue was moved in an other group. The Group does not
	  intent to resolve this issue. 
	</li><li><a id="state_subsumed" name="state_subsumed">Subsumed</a>: 
	  The issue has been subsumed by an other issue. A link to the
	  other issue is given.
	</li></ul></div><div class="decision"><h2><a name="decision" id="decision">Decision cycle description</a></h2><ul><li><a id="decision_announced" name="decision_announced">Announced</a>:
	  Initial decision cycle; The group has announced his decision.
	</li><li><a id="decision_agreement" name="decision_agreement">Agreement</a>:
	   The group received an agreement to refine his decision.
	</li><li><a id="decision_proposal" name="decision_proposal">Proposal</a>:
	   The group received a proposal to refine his decision.
	</li><li><a id="decision_objection" name="decision_objection">Objection</a>:
	   The group received an objection to his decision.
	</li><li><a id="decision_accepted" name="decision_accepted">Accepted</a>:
	   The group reopened an issue to reconsider his decision after received an objection
	   or proposal. A link to the new issue is given.
	</li><li><a id="decision_maintained" name="decision_maintained">Maintained</a>:
	   The group maintained its decision after received an objection
	   or proposal.
	</li></ul></div><div class="categories"><h2><a name="categories" id="categories">Categories description</a></h2></div></div><div class="detail"><h2><a id="detailsList" name="detailsList">Issue details</a></h2><div class="issue"><h3><a id="w3cMediaType-1" name="w3cMediaType-1">w3cMediaType-1</a>: Should W3C WGs define their own media types? [<a href="issues.html#w3cMediaType-1">link to this issue</a>]</h3><p>
							What are the general guidelines or policies
							(if any) for W3C working groups in defining
							their own media types? Should they be
							defining them at all?
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><a href="http://www.w3.org/TR/NOTE-rdfarch">
						W3C Data Formats
					</a></dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2002/04/22-tag-summary#Draft">22 Apr 2002</a>, <a href="http://www.w3.org/2002/04/29-tag-summary#Status">29 Apr 2002</a>, <a href="http://www.w3.org/2002/05/20-tag-summary#mediaTypeFinding">20 May 2002</a>, <a href="http://www.w3.org/2002/06/17-tag-summary">17 Jun 2002</a>, <a href="http://www.w3.org/2002/07/08-tag-summary#media-types">8 Jul 2002</a>, <a href="http://www.w3.org/2006/07/25-tagmem-minutes#item02a">25 Jul 2006</a></dd><dt>Categories</dt><dd></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jan/0063">raised</a> on 9 Jan 2002 by 
						Mark Baker
					, on behalf of <a href="http://www.w3.org/2000/xp/">
						XML Protocol WG
					</a></dt><dd></dd><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jan/0174">accepted</a> on 21 Jan 2002</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jan/0078">
										Tim Bray comments on the
										architecture doc
									</a>
									about namespaces and media types.
								</li><li>
									Message from Joseph Reagle about
									<a href="http://lists.w3.org/Archives/Public/www-tag/2002Jan/0085">
										three bits on MediaTypes and
										IANA
									</a>
									.
								</li><li>
									Comments from Mark Baker on
									<a href="http://lists.w3.org/Archives/Public/www-tag/2002Jan/0113">
										XSLT and namespace dispatch
									</a>
									.
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jan/0179">
										Forward from Simon St. Laurent
										about ID: MediaFeature xmlns
									</a>
									.
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jan/0198">
										Heads-up from Mark Nottingham
									</a>
									about XForms document in last call
									and relation to media types issues.
								</li><li><a href="/2002/06/registering-mediatype">
										How to Register an IANA Media
										Type
									</a>
									, Joseph Reagle
								</li><li>
									18 Dec 2004:
									<a href="https://datatracker.ietf.org/public/pidtracker.cgi?command=view_id&amp;dTag=10042&amp;rfc_flag=0">
										IETF approves new media type
										registration process
									</a>
									.
								</li><li>
									25 Feb 2004:
									<a href="http://lists.w3.org/Archives/Member/tag/2004Feb/0160">
										New registration process
										description
									</a>
									from Martin Duerst
								</li></ul></dd></dl></div><div class="issue"><h3><a id="customMediaType-2" name="customMediaType-2">customMediaType-2</a>: 
				What commonality should there be among W3C media types?
			 [<a href="issues.html#customMediaType-2">link to this issue</a>]</h3><p>
							For example, should all these custom XML
							types being registered be required to use
							the RFC 3023 +xml convention? If so, should
							all the SHOULDs of section 7.1 be followed?
							etc.. The question isn't restricted to RFC
							3023 issues though. There may be value to
							other common features between types.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><a href="http://www.w3.org/TR/NOTE-rdfarch">
						W3C Data Formats
					</a></dd><dt>Categories</dt><dd></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jan/0063">raised</a> on 9 Jan 2002 by 
						Mark Baker
					, on behalf of <a href="http://www.w3.org/2000/xp/">
						XML Protocol WG
					</a></dt><dd></dd><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jan/0175">accepted</a> on 21 Jan 2002</dt><dd></dd><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jun/0019">agreed</a> on 3 Jun 2002</dt><dd><p>
							See resolution for
							<a href="#w3cMediaType-1">
								w3cMediaType-1
							</a>
							. See
							<a href="http://lists.w3.org/Archives/Public/www-tag/2002Jul/0323">
								changes from Chris Lilley regarding RFC
								3023
							</a>
							.
						</p><h5>Acknowledgment cycle</h5><dl><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jun/0019">announced by group  on 3 Jun 2002</a></dt></dl></dd></dl></div><div class="issue"><h3><a id="nsMediaType-3" name="nsMediaType-3">nsMediaType-3</a>: 
				Relationship between media types and namespaces?
			 [<a href="issues.html#nsMediaType-3">link to this issue</a>]</h3><p>
							What is, or what should be, the relationship
							between a media type and an XML namespace?
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><ul><li><a href="http://www.w3.org/TR/REC-xml-names/">
						Namespaces in XML
					</a></li><li><a href="http://www.ietf.org/rfc/rfc3023.txt">
						RFC3023
					</a></li></ul></dd><dt>Categories</dt><dd></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jan/0063">raised</a> on 9 Jan 2002 by 
						Mark Baker
					, on behalf of <a href="http://www.w3.org/2000/xp/">
						XML Protocol WG
					</a></dt><dd></dd><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jan/0174">accepted</a> on 21 Jan 2002</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="http://www.ietf.org/internet-drafts/draft-stlaurent-feature-xmlns-01.txt">
										ID: xmlns Media Feature Tag
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jan/0118">
										message from Larry Masinter
									</a></li><li>
									See
									<a href="http://lists.w3.org/Archives/Public/www-tag/2002Jan/0177">
										TB's proposal
									</a></li></ul></dd><dt><a href="http://www.w3.org/2002/04/22-tag-summary#Draft">Subsumed </a> by issue(s) <a href="#mixedNamespaceMeaning-13">mixedNamespaceMeaning-13</a> on 22 Apr 2002</dt><dd><p>
							Cf. issue
							<a href="#mixedNamespaceMeaning-13">
								mixedNamespaceMeaning-13
							</a>
							.
						</p></dd></dl></div><div class="issue"><h3><a id="xformsReview-4" name="xformsReview-4">xformsReview-4</a>: Request to review XForms Last Call document [<a href="issues.html#xformsReview-4">link to this issue</a>]</h3><p>
							Broad request to review XForms Last Call
							document.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><a href="http://www.w3.org/TR/2002/WD-xforms-20020118/">
						XForms 1.0
					</a></dd><dt>Categories</dt><dd></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jan/0172">raised</a> on 18 Jan 2002 by 
						Art Barstow
					, on behalf of <a href="http://www.w3.org/MarkUp/Forms/">
						XForms WG
					</a></dt><dd></dd><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jan/0209">declined</a> on 28 Jan 2002</dt><dd><p>
							In general, the TAG does not expect to
							review documents on the W3C Recommendation
							Track, unless specific issues are brought to
							their attention.
						</p><h5>Acknowledgment cycle</h5><dl><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jan/0209">announced by group  on 28 Jan 2002</a></dt></dl></dd></dl></div><div class="issue"><h3><a id="uncefactLiaison-5" name="uncefactLiaison-5">uncefactLiaison-5</a>: 
				Invitation to create liaison with UN/CEFACT ebTWG
				Architecture Group
			 [<a href="issues.html#uncefactLiaison-5">link to this issue</a>]</h3><p>
							There are several architectural issues in
							UN/CEFACT and ebXML which should probably be
							solved by the W3C group. The needs are not
							specific to ebXML and several other
							"Registry" and XML vocabulary
							groups may have similar requirements.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><ul><li><a href="http://www.unece.org/cefact/">
						UN/CEFACT
					</a></li><li><a href="http://www.ebxml.org/">ebXML</a></li></ul></dd><dt>Categories</dt><dd></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jan/0021">raised</a> on 3 Jan 2002 by 
						Duane Nickull
					, on behalf of <a href="http://xml.coverpages.org/ni2001-09-20-b.html">
						UN/CEFACT ebTWG Architecture Group
					</a></dt><dd></dd><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Feb/0043">declined</a> on 8 Feb 2002</dt><dd><p>
							TAG suggests that request be redirected to
							new Web Services Architecture Working Group
						</p><h5>Acknowledgment cycle</h5><dl><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Feb/0043">announced by group  on 8 Feb 2002</a></dt></dl></dd></dl></div><div class="issue"><h3><a id="rdfmsQnameUriMapping-6" name="rdfmsQnameUriMapping-6">rdfmsQnameUriMapping-6</a>: Algorithm for creating a URI from a QName? [<a href="issues.html#rdfmsQnameUriMapping-6">link to this issue</a>]</h3><p>
							"It seems to me that the RDFCore and
							XMLSchema WGs (at the very least) ought to
							develop a common, reasonably acceptable
							convention as to the mapping between QNames
							and URIs. Perhaps this is an issue that the
							TAG ought to consider (because it is a
							really basic architectural issue)."
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><ul><li><a href="http://www.w3.org/TR/rdf-mt/">
						RDF Model Theory
					</a></li><li><a href="http://www.w3.org/TR/xmlschema-2/">
						XML Schema Part 2: Datatypes
					</a></li></ul></dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2001/tag/2002/0505-agenda">5 May 2002</a>, <a href="http://www.w3.org/2002/09/24-tag-summary#rdfmsQnameUriMapping-6">24 Sep 2002</a>, <a href="http://www.w3.org/2002/11/25-tag-summary">25 Nov 2002</a>, <a href="http://www.w3.org/2003/02/06-tag-summary#rdfmsQnameUriMapping-6">6 Feb 2003</a>, <a href="http://www.w3.org/2003/06/23-tag-summary#issues">23 Jun 2003</a>, <a href="http://www.w3.org/2003/11/15-tag-summary">15 Nov 2003</a>, <a href="http://www.w3.org/2003/12/04-tag-summary">5 Dec 2002</a>, <a href="http://www.w3.org/2004/01/05-tag-summary#rdfmsQnameUriMapping-6">5 Jan 2004</a>, <a href="http://www.w3.org/2004/01/26-tag-summary#qnameAsId-18">26 Jan 2004</a>, <a href="http://www.w3.org/2004/02/09-tag-summary#rdfmsQnameURIMapping-6">9 Feb 2004</a>, <a href="http://www.w3.org/2004/03/02-tag-summary#qnames">2 Mar 2004</a></dd><dt>Categories</dt><dd></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jan/0178">raised</a> on 22 Jan 2002 by 
						Jonathan Borden
					</dt><dd></dd><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jan/0221">accepted</a> on 29 Jan 2002</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="http://lists.w3.org/Archives/Public/www-webont-wg/2002Feb/0028">
										URIs for terms: motivation [was:
										Requirements Document]
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002May/0048">
										Discussion started by TB
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-xml-schema-comments/2002OctDec/thread">
										Thread within XML Schema WG
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Nov/0153">
										rdfmsQnameUriMapping-6 affects
										WSDL too
									</a>
									from DanC. See input from Jonathan
									Marsh (
									<a href="http://lists.w3.org/Archives/Public/www-tag/2003Feb/0207">
										forwarded by Paul Cotton
									</a>
									)
								</li></ul></dd><dt><a href="http://www.w3.org/2003/11/15-tag-summary">agreed</a> on 15 Nov 2003</dt><dd><p>
							The use of Qnames as identifiers without
							providing a mapping to URIs is inconsistent
							with Web Architecture. See the TAG finding
							<a href="http://www.w3.org/2001/tag/doc/qnameids">
								Using Qualified Names (QNames) as
								Identifiers in Content
							</a>
							.
						</p><h5>Acknowledgment cycle</h5><dl><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2003Dec/0037">announced by group  on 2 Dec 2003</a></dt><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2003Dec/0192"> agreement by reviewer  on 16 Dec 2003</a></dt><dd><p>Accepts the situation</p></dd></dl></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						DC
					</h5><ul><li><a href="http://www.w3.org/2003/02/06-tag-summary">accepted on 6 Feb 2003</a><br /><p>
									Propose TAG response to XML Schema
									desideratum (
									<a href="http://www.w3.org/TR/2003/WD-xmlschema-11-req-20030121/#N400183">
										RQ-23
									</a>
									)
								</p></li><li><a href="http://www.w3.org/2003/12/04-tag-summary">dropped on 4 Dec 2003</a><br /><p>
									Henry Thompson is aware of this
									issue.
								</p></li></ul></div><div class="details-action decided"><h5>NW</h5><ul><li><a href="http://www.w3.org/2003/10/06-tag-summary">accepted on 6 Oct 2003</a><br /><p>
									Revise Qname finding to say (1) if
									you use qnames, provide a mapping to
									URIs and (2) don't define an
									attribute that can take either a URI
									or a Qname since they are not
									syntactically distinguishable.
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Nov/0010">proposal on 4 Nov 2003</a><br /><p>
									Proposed revision of finding.
									However, as discussed at
									<a href="http://www.w3.org/2004/01/05-tag-summary#rdfmsQnameUriMapping-6">
										5 Jan 2004 teleconf
									</a>
									, NW expects to produce a new
									revision based on other input.
								</p></li><li><a href="http://www.w3.org/2004/01/12-tag-summary#qnameAsId-18">subsumed on 12 Jan 2004</a><br /><p>
									Subsumed by action for revision
									related to
									<a href="#qnameAsId-18">
										qnameAsId-18
									</a>
									.
								</p></li></ul></div><div class="details-action decided"><h5>
						DO
					</h5><ul><li><a href="http://www.w3.org/2003/11/15-tag-summary">accepted on 15 Nov 2003</a><br /><p>
									Point WSDL WG to resolution of issue
									6.
								</p></li><li><a href="http://www.w3.org/2004/02/09-tag-summary#qnameAsId-18">completed on 15 Nov 2003</a></li></ul></div><div class="details-action decided"><h5>
						DO
					</h5><ul><li><a href="http://www.w3.org/2003/11/15-tag-summary">accepted on 15 Nov 2003</a><br /><p>
									Propose some extra text for section
									4.5 that hypertext agents often
									follow an IGNORE rule and this often
									results in incompatible behavior.
									Ignore applied to fragid
									interpretation.
								</p></li><li><a href="http://www.w3.org/2004/01/05-tag-summary#rdfmsQnameUriMapping-6">dropped on 5 Jan 2004</a><br /><p>
									This was too late for Last Call Arch
									Doc.
								</p></li></ul></div></div></div><div class="issue"><h3><a id="whenToUseGet-7" name="whenToUseGet-7">whenToUseGet-7</a>: 
				(1) GET should be encouraged, not deprecated, in XForms
				(2) How to handle safe queries (New POST-like method?
				GET plus a body?)
			 [<a href="issues.html#whenToUseGet-7">link to this issue</a>]</h3><p>
							See
							<a href="http://lists.w3.org/Archives/Public/www-forms/2002Jan/0081">
								comments from Paul Prescod
							</a>
							to
							<a href="">Forms WG</a>
							"I know you've recently been asked
							about PUT. During that discussion it arose
							that HTTP GET is deprecated in the
							specification. Does this mean that XForms
							would be incompatible with an application
							like Google that uses a form to generate a
							GET URL?"
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><ul><li><a href="http://www.w3.org/TR/2002/WD-xforms-20020118/">
						XForms 1.0
					</a></li><li><a href="http://www.w3.org/DesignIssues/Axioms#state">
						Design Issues
					</a></li></ul></dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2002/02/04-tagmem-irc">4 Feb 2002</a>, <a href="http://www.w3.org/2002/04/08-tag-summary#When">8 Apr 2002</a>, <a href="http://www.w3.org/2002/04/15-tag-summary#get-ws">15 Apr 2002</a>, <a href="http://www.w3.org/2002/04/22-tag-summary#When">22 Apr 2002</a>, <a href="http://www.w3.org/2002/04/29-tag-summary#Status1">29 Apr 2002</a>, <a href="http://www.w3.org/2001/tag/2002/0505-agenda">5 May 2002</a>, <a href="http://www.w3.org/2002/05/20-tag-summary#whenToUseGet">20 May 2002</a>, <a href="http://lists.w3.org/Archives/Public/www-tag/2002Jun/0019">3 Jun 2002</a>, <a href="http://www.w3.org/2002/06/10-tag-summary">10 Jun 2002</a>, <a href="http://www.w3.org/2002/07/08-tag-summary#get">8 Jul 2002</a>, <a href="http://www.w3.org/2002/11/25-tag-summary">25 Nov 2002</a>, <a href="http://www.w3.org/2003/02/06-tag-summary#whenToUseGet-7">6 Feb 2003</a>, <a href="http://www.w3.org/2003/05/05-tag-summary#whenToUseGet-7">5 May 2003</a>, <a href="http://www.w3.org/2003/06/23-tag-summary#whenToUseGet-7">23 Jun 2003</a>, <a href="http://www.w3.org/2003/07/07-tag-summary#whenToUseGet-7">7 Jul 2003</a>, <a href="http://www.w3.org/2003/09/15-tag-summary#whenToUseGet-7">15 Sep 2003</a>, <a href="http://www.w3.org/2003/10/06-tag-summary#whenToUseGet-7">8 Oct 2003</a>, <a href="http://www.w3.org/2003/12/04-tag-summary">5 Dec 2002</a>, <a href="http://www.w3.org/2004/01/05-tag-summary#whenoUseGet-7">5 Jan 2004</a>, <a href="http://www.w3.org/2004/02/09-tag-summary#whenToUseGet-7">9 Feb 2004</a>, <a href="http://lists.w3.org/Archives/Public/www-ws-desc/2003Dec/0006">2 Mar 2004</a>, <a href="http://lists.w3.org/Archives/Public/www-tag/2006Oct/att-0053/10-tagmem-minutes#item03">10 Oct 2006</a>, <a href="http://www.w3.org/2006/10/17-tagmem-minutes#item08">17 Oct 2006</a>, <a href="http://www.w3.org/2006/10/24-tagmem-minutes#item03">24 Oct 2006</a>, <a href="http://www.w3.org/2001/tag/2006/12/11-minutes#item04">11 Dec 2006</a>, <a href="http://www.w3.org/2001/tag/2006/12/11-minutes#item08">11 Dec 2006</a>, <a href="http://www.w3.org/2007/01/09-tagmem-minutes#item03">9 Jan 2007</a>, <a href="http://www.w3.org/2001/tag/2007/02/26-minutes#item06">26 Feb 2007</a></dd><dt>Categories</dt><dd></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jan/0182">raised</a> on 23 Jan 2002 by 
						Dan Connolly
					, on behalf of <a href="http://www.w3.org/2001/tag/">
						TAG
					</a></dt><dd></dd><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jan/0223">accepted</a> on 29 Jan 2002</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jan/0199">
										Background information from
										Micha Dubinko
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jan/0204">
										Martin Duerst comments
									</a>
									on using GET with a message body.
								</li><li><a href="http://www.w3.org/2001/tag/doc/ws-uri">
										Draft SOAP HTTP GET binding
									</a>
									(DO)
								</li><li><a href="http://lists.w3.org/Archives/Member/tag/2003Feb/0108">
										Additional comments from Dan
										Connolly
									</a>
									regarding some security issues (to
									TAG).
								</li><li>
									See
									<a href="http://lists.w3.org/Archives/Public/www-tag/2003Sep/0160">
										comments from Noah
									</a>
									, however.
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2006Oct/0061">
										WS-Transfer and HTTP, re TAG
										Issues whenToUseGet-7 &amp;
										endPointRefs-47
									</a></li></ul></dd><dt><a href="http://www.w3.org/2002/11/25-tag-summary">agreed</a> on 25 Nov 2002</dt><dd><p><a href="http://www.w3.org/2001/tag/doc/whenToUseGet">
								URIs, Addressability, and the use of
								HTTP GET
							</a>
							.
						</p><h5>Acknowledgment cycle</h5><dl><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2003Sep/0147">announced by group  on 22 Sep 2003</a></dt><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2003Sep/0147"> agreement by reviewer  on 22 Sep 2003</a></dt><dd><p>
									Acknowledged by DanC by virtue of WG
									agreement
								</p></dd></dl></dd><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2006Oct/att-0053/10-tagmem-minutes#item03">raised</a> on 10 Oct 2006</dt><dd><p>
							Reopening the issue as an umbrella (together
							with issue
							<a href="#endPointRefs-47">
								endPointRefs-47
							</a>
							) for discussing
							<a href="http://www.w3.org/Submission/2006/08/">
								submission WS-Transfer
							</a>
							.
						</p><h5>Acknowledgment cycle</h5><dl><dt>Not started</dt></dl></dd><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2006Oct/att-0053/10-tagmem-minutes#item03">accepted</a> on 10 Oct 2006</dt><dd><h5>Acknowledgment cycle</h5><dl><dt>Not started</dt></dl></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						DC
					</h5><ul><li><a href="http://www.w3.org/2003/09/15-tag-summary">accepted on 15 Sep 2003</a><br /><p>
									Provide TAG with pointers into WS
									specs where issue of safe operations
									is manifest.
								</p></li><li><a href="http://www.w3.org/2004/03/02-tag-summary#whenToUseGet-7">completed on 2 Mar 2004</a><br /><p>
									See WSDL WG's
									<a href="http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/issues/wsd-issues.html#x117">
										issue 117
									</a>
									.
								</p></li></ul></div><div class="details-action decided"><h5>
						DO
					</h5><ul><li><a href="http://www.w3.org/2003/09/15-tag-summary">accepted on 15 Sep 2003</a><br /><p>
									Ask WSDL WG to look at finding; ask
									them if marking operations as safe
									in WSDL is one of their
									requirements.
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-ws-desc/2003Dec/0006">proposal on 3 Dec 2003</a><br /><p>
									Request to WS Desc WG Chair to
									ensure that this on their WG's
									issues list.
								</p></li><li><a href="http://www.w3.org/2004/03/02-tag-summary#whenToUseGet-7">completed on 2 Mar 2004</a><br /><p>
									See WSDL WG's
									<a href="http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/issues/wsd-issues.html#x117">
										issue 117
									</a>
									and
									<a href="http://lists.w3.org/Archives/Public/www-tag/2004Apr/0012">
										decision from WSDL WG
									</a></p></li></ul></div><div class="details-action decided"><h5>SW</h5><ul><li><a href="http://www.w3.org/2004/04/26-tag-summary">accepted on 26 Apr 2004</a><br /><p>
									Thank the WSDL for what they've done
									so far, ask them to explain a bit
									about what can go wrong, encourage
									them to put it in the test suite
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2004May/0025">proposal on 11 May 2004</a><br /><p>See email to WSDL WG</p></li><li><a href="http://www.w3.org/2004/05/24-tag-summary">completed on 24 May 2004</a><br /><p>Completed</p></li></ul></div><div class="details-action decided"><h5>
						NM
					</h5><ul><li><a href="http://www.w3.org2001/tag/2006/12/11-minutes#action08">accepted on 11 Dec 2006</a><br /><p>
									Noah and Dave to write a position
									paper outline for the TAG by the
									18th of Dec. 2006.
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2006Dec/0038">completed on 19 Dec 2006</a><br /><p>Completed</p></li></ul></div><div class="details-action decided"><h5>SW</h5><ul><li><a href="http://www.w3.org/2007/02/26-tagmem-minutes#action01">accepted on 26 Feb 2007</a><br /><p>
									Stuart to respond to Jacek and
									Jonathan wrt whenToUseGet-7 and
									WSDL.
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2007Feb/0032">completed on 27 Feb 2007</a></li></ul></div></div></div><div class="issue"><h3><a id="namespaceDocument-8" name="namespaceDocument-8">namespaceDocument-8</a>: 
				What should a "namespace document" look like?
			 [<a href="issues.html#namespaceDocument-8">link to this issue</a>]</h3><p>
							The
							<a href="/DesignIssues/Architecture#Namespaces">
								section on namespaces
							</a>
							in
							<a href="http://www.w3.org/DesignIssues/Architecture">
								Web Architecture from 50,000 feet
							</a>
							states: "The namespace document (with
							the namespace URI) is a place for the
							language publisher to keep definitive
							material about a namespace. Schema languages
							are ideal for this." Tim Bray
							disagrees.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><a href="http://www.w3.org/DesignIssues/Architecture">
						Web Architecture from 50,000 feet
					</a></dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2002/03/25-tag-summary">25 Mar 2002</a>, <a href="/2002/04/01-tag-summary#issue-8">1 Apr 2002</a>, <a href="http://www.w3.org/2002/04/01-tag-summary#issue-8">8 Apr 2002</a>, <a href="http://www.w3.org/2001/tag/2002/0505-agenda">5 May 2002</a>, <a href="http://www.w3.org/2002/09/24-tag-summary#namespaceDocument-8">24 Sep 2002</a>, <a href="http://www.w3.org/2002/09/24-tag-summary#namespaces">25 Sep 2002</a>, <a href="http://www.w3.org/2002/11/18-tag-summary#RDDL">18 Nov 2002</a>, <a href="http://www.w3.org/2002/12/09-tag-summary#namespaceDocument-8">9 Dec 2002</a>, <a href="http://www.w3.org/2002/12/16-tag-summary#namespaceDocument-8">16 Dec 2002</a>, <a href="http://www.w3.org/2003/01/06-tag-summary#namespaceDocument-8">6 Jan 2003</a>, <a href="http://www.w3.org/2003/01/13-tag-summary#namespaceDocument-8">13 Jan 2003</a>, <a href="http://www.w3.org/2003/02/06-tag-summary#namespaceDocument-8">6 Feb 2003</a>, <a href="http://www.w3.org/2003/02/17-tag-summary#namespaceDocument-8">17 Feb 2003</a>, <a href="http://www.w3.org/2003/02/24-tag-summary#namespaceDocument-8">24 Feb 2003</a>, <a href="http://www.w3.org/2003/03/24-tag-summary#namespaceDocument-8">24 Mar 2003</a>, <a href="http://www.w3.org/2003/04/07-tag-summary#namespaceDocument-8">7 Apr 2003</a>, <a href="http://www.w3.org/2003/04/14-tag-summary#namespaceDocument-8">14 Apr 2003</a>, <a href="http://www.w3.org/2003/06/23-tag-summary#issues">23 Jun 2003</a>, <a href="http://www.w3.org/2003/09/08-tag-summary#namespaceDocument-8">8 Sep 2003</a>, <a href="http://www.w3.org/2003/09/15-tag-summary#namespaceDocument-8">15 Sep 2003</a>, <a href="http://www.w3.org/2003/12/04-tag-summary">5 Dec 2002</a>, <a href="http://www.w3.org/2004/01/26-tag-summary#namespaceDocument-8">26 Jan 2004</a>, <a href="http://www.w3.org/2004/03/02-tag-summary#namespaceDocument-8">2 Mar 2004</a>, <a href="http://www.w3.org/2004/05/14-tag-summary#namespaceDocument-8">14 May 2004</a>, <a href="http://www.w3.org/2005/04/05-tagmem-minutes#item03">5 Apr 2005</a>, <a href="http://www.w3.org/2001/tag/2005/06/14-16-minutes#item032">16 Jun 2005</a>, <a href="http://www.w3.org/2001/tag/2005/07/12-minutes#item01">12 Jul 2005</a>, <a href="http://www.w3.org/2005/08/30-tagmem-minutes#item04">30 Aug 2005</a>, <a href="http://www.w3.org/2005/09/22-tagmem-minutes#item03">22 Sep 2005</a>, <a href="http://www.w3.org/2005/10/11-tagmem-minutes#item06">11 Oct 2005</a>, <a href="http://www.w3.org/2005/11/01-tagmem-minutes#item12">1 Nov 2005</a>, <a href="http://www.w3.org/2001/tag/2005/11/08-tagmem-minutes#item03">8 Nov 2005</a>, <a href="http://www.w3.org/2001/tag/2005/12/06-Afternoon-minutes#item02">6 Dec 2005</a>, <a href="http://lists.w3.org/Archives/Member/tag/2006Jan/att-0003/Jan102005#item03">10 Jan 2006</a>, <a href="http://www.w3.org/2006/02/21-tagmem-minutes#item09">21 Feb 2006</a>, <a href="http://www.w3.org/2006/05/02-tagmem-minutes#item05">2 May 2006</a>, <a href="http://www.w3.org/2001/tag/2006/06/14-minutes#item08">14 Jun 2006</a>, <a href="http://www.w3.org/2001/tag/2006/10/05-afternoon-minutes#item03">5 Oct 2006</a>, <a href="http://www.w3.org/2001/tag/2006/11/14-tagmem-minutes#item03">14 Nov 2006</a>, <a href="http://www.w3.org/2001/tag/2006/12/13-morning-minutes#item02">13 Dec 2006</a>, <a href="http://www.w3.org/2001/tag/2007/03/07-morning-minutes#item01">6 Mar 2007</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jan/0078">raised</a> on 14 Jan 2002 by 
						Tim Bray
					, on behalf of <a href="http://www.w3.org/2001/tag/">
						TAG
					</a></dt><dd></dd><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Feb/0019">accepted</a> on 4 Feb 2002</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="/TR/xmlschema-1/">
										XML Schema Part 1: Structures
									</a></li><li>
									See
									<a href="http://lists.w3.org/Archives/Public/www-tag/2002Feb/0022">
										comments from Patrick Stickler
									</a>
									that "namespaces are strictly
									punctuation." and
									<a href="http://lists.w3.org/Archives/Public/www-tag/2002Feb/0025">
										reply from Larry Masinter
									</a>
									.
								</li><li>
									See
									<a href="http://lists.w3.org/Archives/Public/www-tag/2002Feb/0093">
										14 Theses
									</a>
									from Tim Bray
								</li><li>
									See
									<a href="http://lists.w3.org/Archives/Public/www-tag/2002Apr/0069">
										thread on RDF and RDDL
									</a>
									from Stuart Williams.
								</li><li>
									See
									<a href="http://www.w3.org/2002/04/htmlrdf">
										RDF in HTML
									</a>
									from Tim Berners-Lee
								</li><li>
									Emails (
									<a href="http://lists.xml.org/archives/xml-dev/200206/msg00274.html">
										1
									</a>
									,
									<a href="http://lists.xml.org/archives/xml-dev/200206/msg00275.html">
										2
									</a>
									) from James Clark to xml-dev about
									schemas, as
									<a href="http://lists.w3.org/Archives/Public/www-tag/2002Jun/0063">
										suggested by Tim Bray
									</a>
									. See also
									<a href="http://www.imc.org/ietf-xml-use/mail-archive/msg00217.html">
										Email from James about Relax NG
										and W3C XML Schema
									</a></li><li><a href="http://www.imc.org/ietf-xml-use/xml-guidelines-07.txt">
										Guidelines for the Use of XML
										within IETF Protocols
									</a>
									, section 4.9. See also
									<a href="http://www.imc.org/ietf-xml-use/index.html">
										ietf-xml-use mailing list
									</a>
									in case the document disappears.
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Nov/0147">
										RDDL Challenge
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Dec/0048">
										RDDL Proposal from Tim Bray
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Dec/0056">
										RDDL Proposal from Chris Wilper
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Dec/0099">
										RDDL Proposal from Jonathan
										Borden
									</a></li><li><a href="http://www.w3.org/2002/11/rddl/">
										Examples of RDDL in RDF
									</a>
									from TBL
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Dec/0180">
										RDDL Proposal from Micah Dubinko
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Dec/0232">
										RDDL proposal from Sandro Hawke
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Jan/0004">
										Summary by Norm
									</a>
									of RDDL Proposals.
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Jan/0223">
										RDDL Proposal from Garrett
										Wilson
									</a></li><li><a href="http://www.tbray.org/tag/rddl/rddl3.html">
										1 Jun 2003 draft of RDDL
									</a></li><li>
									Namespace URIs should be
									dereferencable (to find useful
									explanatory material) (
									<a href="http://www.w3.org/2002/02/12-tagmem-irc">
										12 Feb ftf meeting
									</a>
									)
								</li><li>
									Refer to draft TAG
									<a href="http://lists.w3.org/Archives/Public/www-tag/2003Jun/0003">
										opinion from Tim Bray
									</a>
									on the use of URNs for namespace
									names.
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2004Jan/0045">
										RDDL2 Background
									</a>
									from Tim Bray.
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2004Jan/0026">
										grokRDDL.xsl mapping to RDF
									</a>
									from Dan Connolly.
								</li><li><a href="http://www.w3.org/2001/tag/2005/06/23-rddl/">
										namespaceDocument-8 Notes
									</a>
									from Norm Walsh (24 June 2005)
								</li><li><a href="http://www.w3.org/2001/tag/doc/nsDocuments/">
										Associating Resources with
										Namespaces
									</a>
									from Norm Walsh
								</li><li><a href="http://www.w3.org/TR/grddl/">
										Gleaning Resource Descriptions
										from Dialects of Languages
										(GRDDL)
									</a></li></ul></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						PC
					</h5><ul><li><a href="http://www.w3.org/2003/04/07-tag-summary">accepted on 7 Apr 2003</a><br /><p>
									Prepare finding to answer this
									issue, pointing to the RDDL Note.
									See
									<a href="http://lists.w3.org/Archives/Member/tag/2003Apr/0046">
										comments from Paul
									</a>
									regarding TB theses. Per
									<a href="http://www.w3.org/2004/02/23-tag-summary#namespaceDocument-8">
										23 Feb 2004 teleconf
									</a>
									, modified into an action to produce
									a bulleted list of points.
								</p></li><li><a href="http://lists.w3.org/Archives/Member/tag/2006Jan/att-0003/Jan102005#item02">dropped on 10 Jan 2006</a></li></ul></div><div class="details-action decided"><h5>
						TB
					</h5><ul><li><a href="http://www.w3.org/2003/09/15-tag-summary">accepted on 15 Sep 2003</a><br /><p>
									Add "Hello World" example to next
									draft of RDDL Spec (i.e., to edited
									version of
									<a href="http://www.tbray.org/tag/rddl4.html">
										RDDL draft 4
									</a>
									). See also
									<a href="http://lists.w3.org/Archives/Public/www-tag/2004Jan/0026">
										Proposal for RDDL to RDF mapping
										from DC
									</a></p></li><li><a href="http://lists.w3.org/Archives/Member/tag/2006Jan/att-0003/Jan102005#item02">completed on 10 Jan 2006</a></li></ul></div><div class="details-action decided"><h5>
						TB
					</h5><ul><li><a href="">accepted on 15 Sep 2003</a><br /><p>
									Produce schemaware for RDDL spec
									once TAG has consensus on the
									syntax.
								</p></li><li><a href="http://lists.w3.org/Archives/Member/tag/2006Jan/att-0003/Jan102005#item02">dropped on 10 Jan 2006</a></li></ul></div><div class="details-action decided"><h5>
						TB
					</h5><ul><li><a href="http://www.w3.org/2004/02/23-tag-summary#namespaceDocument-8">accepted on 23 Feb 2004</a><br /><p>
									Continue working on draft and to get
									statement from Jonathan re:
									persistence at rddl.org
								</p></li><li><a href="http://www.w3.org/2006/02/21-tagmem-minutes#item09">completed on 21 Feb 2006</a></li></ul></div><div class="details-action decided"><h5>
						TB
					</h5><ul><li><a href="http://www.w3.org/2004/02/23-tag-summary#namespaceDocument-8">accepted on 23 Feb 2004</a><br /><p>
									Add pointer to previous syntax in
									the Note
								</p></li><li><a href="http://lists.w3.org/Archives/Member/tag/2006Jan/att-0003/Jan102005#item02">dropped on 10 Jan 2006</a></li></ul></div><div class="details-action decided"><h5>NW</h5><ul><li><a href="http://www.w3.org/2001/tag/2005/07/12-minutes#action01">accepted on 12 Jul 2005</a><br /><p>
									follow up on noah's
									<a href="http://lists.w3.org/Archives/Public/www-tag/2005Jun/0067">
										message
									</a>
									on ns name. Reconfirmed on
									<a href="http://lists.w3.org/Archives/Member/tag/2006Jan/att-0003/Jan102005#action01">
										10 Jan 2006
									</a>
									.
								</p></li><li><a href="http://www.w3.org/2001/tag/2006/11/14-tagmem-minutes#action05">dropped on 14 Nov 2006</a></li></ul></div><div class="details-action decided"><h5>
						DC
					</h5><ul><li><a href="http://www.w3.org/2005/08/30-tagmem-minutes#action03">accepted on 30 Aug 2005</a><br /><p>
									draft a section on using XHTML 1.x
									(not RDDL) with GRDDL and relax-ng
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2005Oct/0010">completed on 7 Oct 2005</a><br /><p>
									DanC has sent a note "a usps
									namespace document using plain XHTML
									and GRDDL".
								</p></li></ul></div><div class="details-action"><h5>
						HT
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2005/09/06-minutes#action04">accepted on 6 Sep 2005</a><br /><p>
									track progress of
									<a href="http://www.w3.org/Bugs/Public/show_bug.cgi?id=1974">
										#int bug 1974
									</a>
									in the XML Schema namespace document
									in the XML Schema WG. Confirmed
									<a href="http://www.w3.org/2001/tag/2006/10/05-afternoon-minutes#PENDING7">
										5 Oct 2006
									</a>
									.
								</p></li><li><a href="http://www.w3.org/2001/tag/group/track/actions/23">proposal on 24 Aug 2007</a><br /><p>
									Tracking transferred to tracker
									<a href="http://www.w3.org/2001/tag/group/track/actions/23">
										ACTION-23
									</a></p></li></ul></div><div class="details-action decided"><h5>
						DC
					</h5><ul><li><a href="http://www.w3.org/2005/09/22-tagmem-minutes#action02">accepted on 22 Sep 2005</a><br /><p>
									ask for "default nature" to be
									changed to "implicit nature" in RDDL
									spec
								</p></li><li><a href="http://lists.w3.org/Archives/Member/tag/2006Jan/att-0003/Jan102005#action01">completed on 10 Jan 2006</a><br /><p>
									The RDDL spec
									<a href="http://lists.w3.org/Archives/Public/www-tag/2006Jan/0036">
										was fixed
									</a>
									.
								</p></li></ul></div><div class="details-action decided"><h5>NW</h5><ul><li><a href="http://lists.w3.org/Archives/Member/tag/2006Jan/att-0003/Jan102005#item03">accepted on 10 Jan 2006</a><br /><p>
									propose to Jonathan Borden that he
									changes to using a file of Natures.
									Confirmed on
									<a href="http://www.w3.org/2001/tag/2006/11/14-tagmem-minutes#action06">
										14 Nov 2006
									</a>
									.
								</p></li><li><a href="http://www.w3.org/2001/tag/2006/12/13-morning-minutes#item02">completed on 13 Dec 2006</a></li></ul></div><div class="details-action"><h5>NW</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/12/13-morning-minutes#action03">accepted on 13 Dec 2006</a><br /><p>
									Provide a set of test cases of ways
									in which RDDL is actually used.
								</p></li><li><a href="http://www.w3.org/2001/tag/group/track/actions/21">proposal on 24 Aug 2007</a><br /><p>
									Tracking transferred to tracker
									<a href="http://www.w3.org/2001/tag/group/track/actions/21">
										ACTION-21
									</a></p></li></ul></div><div class="details-action"><h5>
						DC
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/12/13-morning-minutes#action04">accepted on 13 Dec 2006</a><br /><p>
									Start an ontology including
									docns/documentElementNamespace.
								</p></li><li><a href="http://www.w3.org/2001/tag/group/track/actions/22">proposal on 24 Aug 2007</a><br /><p>
									Tracking transferred to tracker
									<a href="http://www.w3.org/2001/tag/group/track/actions/22">
										ACTION-22
									</a></p></li></ul></div></div></div><div class="issue"><h3><a id="uriMediaType-9" name="uriMediaType-9">uriMediaType-9</a>: Why does the Web use mime types and not URIs? [<a href="issues.html#uriMediaType-9">link to this issue</a>]</h3><p>
							Media types are not first-class objects on
							the Web, or are they?
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references">General</dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2002/04/08-tag-summary#Findings">8 Apr 2002</a>, <a href="http://www.w3.org/2002/04/15-tag-summary#uri-mime">15 Apr 2002</a>, <a href="http://www.w3.org/2002/07/22-tag-summary#L3983">22 Jul 2002</a>, <a href="http://www.w3.org/2002/08/12-tag-summary#arch-doc">12 Aug 2002</a>, <a href="http://www.w3.org/2002/08/30-tag-summary#uriMediaType-9">30 Aug 2002</a>, <a href="http://www.w3.org/2002/12/09-tag-summary#uriMediaType-9">9 Dec 2002</a>, <a href="http://www.w3.org/2003/02/06-tag-summary#uriMediaType-9">6 Feb 2003</a>, <a href="http://www.w3.org/2003/05/05-tag-summary#uriMediaType-9">5 May 2003</a>, <a href="http://www.w3.org/2003/06/23-tag-summary#issues">23 Jun 2003</a>, <a href="http://www.w3.org/2003/12/15-tag-summary#uriMediaType-9">15 Dec 2003</a>, <a href="http://www.w3.org/2004/05/14-tag-summary#uriMediaType-9">14 May 2004</a>, <a href="http://www.w3.org/2001/tag/2005/07/12-minutes#item03">12 Jul 2005</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2001Dec/0015">raised</a> on 17 Dec 2001 by 
						Aaron Swartz
					</dt><dd></dd><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Feb/0020">accepted</a> on 4 Feb 2002</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="http://www.ietf.org/rfc/rfc2046.txt">
										RFC2046
									</a></li><li><a href="http://www.ietf.org/internet-drafts/draft-eastlake-cturi-03.txt">
										Proposal by Don Eastlake:
										draft-eastlake-cturi-03
									</a>
									and
									<a href="http://lists.w3.org/Archives/Public/uri/2001Jan/0006">
										commentary from Larry Masinter
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002May/0138">
										Email from TBL to IETF
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jun/0050">
										Response from Larry Masinter
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Feb/0302">
										Layout of MIME Media Types pages
									</a></li><li>
									IANA appears to have responded to
									the spirit of this draft (see
									<a href="http://lists.w3.org/Archives/Public/www-tag/2003Feb/0302">
										email from Chris Lilley
									</a>
									).
								</li><li><a href="http://lists.w3.org/Archives/Member/tag/2003Dec/0062">
										XMLP WG request for revision of
										uriMediaType-9 issue and related
										finding
									</a></li></ul></dd><dt><a href="/2002/10/21-tag-summary">agreed</a> on 21 Oct 2002</dt><dd><p><a href="2002/01-uriMediaType-9">
								TAG Finding: Mapping between URIs and
								Internet Media Types
							</a>
							. The TAG has not resolved this issue since
							the loop has not been closed with the IETF.
							See Internet Draft
							<a href="http://www.ietf.org/internet-drafts/draft-connolly-w3c-accessible-registries-00.txt">
								A Registry of Assignments using
								Ubiquitous Technologies and Careful
								Policies
							</a>
							by D. Connolly and M. Baker.
						</p><h5>Acknowledgment cycle</h5><dl><dt><a href="http://www.w3.org/2002/10/21-tag-summary">announced by group  on 21 Oct 2002</a></dt></dl></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						CL
					</h5><ul><li><a href="http://www.w3.org/2003/05/05-tag-summary">accepted on 5 May 2003</a><br /><p>
									Propose CL's three changes to
									registration process to Ned Freed.
								</p></li><li><a href="http://lists.w3.org/Archives/Member/tag/2003Oct/0082">proposal on 27 Oct 2003</a><br /><p>
									See
									<a href="http://lists.w3.org/Archives/Member/tag/2003Oct/0079">
										Email to IANA Webmaster
									</a></p></li><li><a href="http://www.w3.org/2004/05/14-tag-summary#uriMediaType-9">completed on 14 May 2004</a></li></ul></div></div></div><div class="issue"><h3><a id="xmlSW-10" name="xmlSW-10">xmlSW-10</a>: 
				Should next version of XML be XML 1.0 - DTDs +
				namespaces + xml:base + the infoset?
			 [<a href="issues.html#xmlSW-10">link to this issue</a>]</h3><p>
							Should next version of XML be XML 1.0 - DTDs
							+ namespaces + xml:base + the infoset?
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><ul><li><a href="http://www.w3.org/TR/REC-xml">
						XML 1.0 Second Edition
					</a></li><li><a href="http://www.w3.org/TR/xmlbase/">
						XBase
					</a></li><li><a href="http://www.w3.org/TR/REC-xml-names">
						XML Namespaces
					</a></li><li><a href="http://www.w3.org/TR/xml-infoset">
						XML Information set
					</a></li></ul></dd><dt>Categories</dt><dd></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Feb/0031">raised</a> on 6 Feb 2002 by 
						Tim Bray
					, on behalf of <a href="http://www.w3.org/2001/tag/">
						TAG
					</a></dt><dd></dd><dt><a href="http://www.w3.org/2002/02/12-tagmem-irc">declined</a> on 12 Feb 2002</dt><dd><p>
							Forward this to the XML Coordination Group
						</p><h5>Acknowledgment cycle</h5><dl><dt><a href="http://www.w3.org/2002/02/12-tagmem-irc">announced by group  on 12 Feb 2002</a></dt></dl></dd></dl></div><div class="issue"><h3><a id="soapRPCURI-11" name="soapRPCURI-11">soapRPCURI-11</a>: 
				What is the appropriate relationship between SOAP RPC
				and the Web's reliance on URIs?
			 [<a href="issues.html#soapRPCURI-11">link to this issue</a>]</h3><p>
							What is the appropriate relationship between
							SOAP RPC and the Web's reliance on URIs?
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><a href="http://www.w3.org/TR/soap12-part1/">
						SOAP 1.2
					</a></dd><dt>Categories</dt><dd></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Feb/0044">raised</a> on 8 Feb 2002 by 
						Paul Prescod
					</dt><dd></dd><dt><a href="http://www.w3.org/2002/02/12-tagmem-irc">declined</a> on 12 Feb 2002</dt><dd><p>Forward to XML Protocol WG</p><h5>Acknowledgment cycle</h5><dl><dt><a href="http://www.w3.org/2002/02/12-tagmem-irc">announced by group  on 12 Feb 2002</a></dt></dl></dd></dl></div><div class="issue"><h3><a id="xmlAsText-12" name="xmlAsText-12">xmlAsText-12</a>: 
				Do proposed changes to XML 1.1 ignore Unicode
				constraints?
			 [<a href="issues.html#xmlAsText-12">link to this issue</a>]</h3><p>
							Do proposed changes to XML 1.1 ignore
							Unicode constraints?
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><a href="http://www.w3.org/TR/xml11/">
						XML 1.1
					</a></dd><dt>Categories</dt><dd></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Feb/0054">raised</a> on 11 Feb 2002 by 
						Rick Jelliffe
					</dt><dd></dd><dt><a href="http://www.w3.org/2002/02/12-tagmem-irc">declined</a> on 12 Feb 2002</dt><dd><p>
							XML Core WG is aware of these issues. Refer
							to
							<a href="http://lists.w3.org/Archives/Public/www-tag/2002Feb/0065">
								draft response from David Orchard
							</a></p><h5>Acknowledgment cycle</h5><dl><dt><a href="http://www.w3.org/2002/02/12-tagmem-irc">announced by group  on 12 Feb 2002</a></dt></dl></dd></dl></div><div class="issue"><h3><a id="mixedNamespaceMeaning-13" name="mixedNamespaceMeaning-13">mixedNamespaceMeaning-13</a>: 
				What is the meaning of a document composed of content in
				mixed namespaces?
			 [<a href="issues.html#mixedNamespaceMeaning-13">link to this issue</a>]</h3><p>
							This was raised in the light of lack of
							consensus result from the workshop, and
							specifically prompted by a question,
							occurring as XEncryption made its way to
							Candidate Recommendation status in W3C,
							about the relationship of XEncryption to
							other specs, and TAG discussion of XSLT
							"templates" as an apparent corner
							case in XML processing.
						</p><p>
							Second issue: namespace-based dispatching.
							From TAG draft finding on issues *-{1,2,3},
							the following draft text was removed for
							discussion as part of this issue:
						</p><p>
							When processing XML documents, it is
							appropriate for Web applications to dispatch
							elements to modules for processing based on
							the namespace of the element type.
						</p><p>
							Correct dispatching and processing requires
							context - in general it is not reasonable
							nor safe to do namespace-based processing
							without knowledge of the namespace of
							ancestor elements. Because of this, the
							namespace of the root element of an XML
							document has special status and serves
							naturally as a basis for top-level software
							dispatching in the case where the dispatch
							information is not externally supplied.
						</p><p>
							It is acknowledged that there are exceptions
							to this rule, for example XSLT documents
							whose root element's namespace depends on
							the desired output from application of the
							XSLT.
						</p><p>
							It should be noticed that in the case of
							certain sort of element including some in
							XSLT, XInclude, XEncryption namespaces, that
							a system conforming to the specification
							will regcognize them at any point in a
							document and elaborate them in place,
							typically producing more XML which replaces
							the element instance in the tree.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><ul><li>XML</li><li>XSLT</li></ul></dd><dt>Discussion history</dt><dd><a href="http://lists.w3.org/Archives/Public/www-tag/2002Mar/0034">11 Mar 2002</a>, <a href="http://www.w3.org/2002/04/22-tag-summary#Draft">22 Apr 2002</a>, <a href="http://www.w3.org/2001/tag/2002/0505-agenda">5 May 2002</a>, <a href="http://www.w3.org/2002/09/24-tag-summary#namespaces">25 Sep 2002</a>, <a href="http://www.w3.org/2003/02/06-tag-summary#mixedNamespaceMeaning-13">6 Feb 2003</a>, <a href="http://www.w3.org/2004/02/09-tag-summary#RDFinXHTML-35">9 Feb 2004</a>, <a href="http://www.w3.org/2005/04/05-tagmem-minutes#item03">5 Apr 2005</a></dd><dt>Categories</dt><dd></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://www.w3.org/2002/04/22-tag-summary">raised</a> on 22 Apr 2002 by 
						Tim Berners-Lee
					, on behalf of <a href="http://www.w3.org/2001/tag/">
						TAG
					</a></dt><dd></dd><dt><a href="http://www.w3.org/2002/04/22-tag-summary">accepted</a> on 22 Apr 2002</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="http://www.w3.org/DesignIssues/XML">
										Discussion by Tim Berners-Lee
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002May/0051">
										Background of the XHTML Media
										Types Note
									</a>
									from Masayasu Ishikawa
								</li></ul></dd><dt><a href="http://www.w3.org/2003/02/06-tag-summary#mixedNamespaceMeaning-13">Subsumed </a> by issue(s) <a href="#mixedUIXMLNamespace-33">mixedUIXMLNamespace-33</a>, <a href="#xmlFunctions-34">xmlFunctions-34</a>, <a href="#RDFinXHTML-35">RDFinXHTML-35</a> on 6 Feb 2003</dt><dd><p>
							Split into three smaller issues:
							<a href="#mixedUIXMLNamespace-33">
								mixedUIXMLNamespace-33
							</a>
							,
							<a href="#xmlFunctions-34">
								xmlFunctions-34
							</a>
							, and
							<a href="#RDFinXHTML-35">
								RDFinXHTML-35
							</a></p></dd></dl></div><div class="issue"><h3><a id="httpRange-14" name="httpRange-14">httpRange-14</a>: 
				What is the range of the HTTP dereference function?
			 [<a href="issues.html#httpRange-14">link to this issue</a>]</h3><p>
							TBL's argument the HTTP URIs (without
							"#") should be understood as
							referring to documents, not cars.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><ul><li>HTTP</li><li>URI</li></ul></dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2002/07/01-tag-summary#arch-doc">1 Jul 2002</a>, <a href="http://www.w3.org/2002/07/15-tag-summary#L3330">15 Jul 2002</a>, <a href="http://www.w3.org/2002/07/22-tag-summary#L3974">22 Jul 2002</a>, <a href="http://www.w3.org/2002/07/29-tag-summary#httpRange-14">29 Jul 2002</a>, <a href="http://lists.w3.org/Archives/Public/www-tag/2002Sep/0127">16 Sep 2002</a>, <a href="http://www.w3.org/2002/09/24-tag-summary#httpRange-14">24 Sep 2002</a>, <a href="http://www.w3.org/2003/01/06-tag-summary#httpRange-14">6 Jan 2003</a>, <a href="http://www.w3.org/2003/01/27-tag-summary#httpRange-14">27 Jan 2003</a>, <a href="http://www.w3.org/2003/02/06-tag-summary#httpRange-14">6 Feb 2003</a>, <a href="http://www.w3.org/2004/06/07-tag-summary#httpRange-14">7 Jun 2003</a>, <a href="http://www.w3.org/2003/06/23-tag-summary#issues">23 Jun 2003</a>, <a href="http://www.w3.org/2003/07/21-tag-summary#july22">22 Jul 2003</a>, <a href="http://www.w3.org/2003/07/28-tag-summary#httpRange-14">28 Jul 2003</a>, <a href="http://www.w3.org/2004/05/14-tag-summary#httpRange-14-1">12 May 2004</a>, <a href="http://www.w3.org/2005/02/07-tagmem-minutes#item04">7 Feb 2005</a>, <a href="http://lists.w3.org/Archives/Public/www-tag/2005Mar/att-0056/March152005#item08">15 Mar 2005</a>, <a href="http://www.w3.org/2005/03/29-tagmem-minutes#item06">29 Mar 2005</a>, <a href="http://lists.w3.org/Archives/Public/www-tag/2005May/att-0033/03-tagmem-irc#action01">3 May 2005</a>, <a href="http://www.w3.org/2005/05/31-tagmem-minutes#item05">31 May 2005</a>, <a href="http://www.w3.org/2001/tag/2005/06/14-16-minutes#item023">15 Jun 2005</a>, <a href="http://www.w3.org/2001/tag/2006/02/27_minutes#L311">27 Feb 2006</a>, <a href="http://www.w3.org/2001/tag/2006/02/07-tagmem-minutes#xmlFunctions">27 Feb 2006</a>, <a href="http://www.w3.org/2007/02/26-tagmem-minutes#item09">26 Feb 2007</a>, <a href="http://www.w3.org/2001/tag/2007/05/30-minutes#item04">30 May 2007</a>, <a href="http://www.w3.org/2001/tag/2007/05/31-tagmem-minutes#item03">31 May 2007</a>, <a href="http://www.w3.org/2001/tag/2007/06/11-minutes#item06">11 Jun 2007</a>, <a href="http://www.w3.org/2007/06/18-tagmem-minutes.html#item06">18 Jun 2007</a>, <a href="http://www.w3.org/2001/tag/2007/07/02-minutes#item03">2 Jul 2007</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Mar/0273">raised</a> on 25 Mar 2002 by 
						Tim Berners-Lee
					, on behalf of <a href="http://www.w3.org/2001/tag/">
						TAG
					</a></dt><dd></dd><dt><a href="http://www.w3.org/2003/02/06-tag-summary#httpRange-14">accepted</a> on 6 Feb 2003</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="http://www.w3.org/DesignIssues/Axioms">
										Axioms of Web Architecture
									</a>
									, by Tim Berners-Lee
								</li><li><a href="/DesignIssues/HTTP-URI">
										What do HTTP URIs Identify?
									</a>
									by TimBL
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jul/0253">
										History of Fragment Identifiers
									</a>
									by Roy Fielding.
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Sep/0132">
										Moby Dick example and summary
									</a>
									from TB.
								</li><li>
									Namespace v. Namespace Document is
									an example of this issue as
									evidenced by
									<a href="http://lists.w3.org/Archives/Public/www-tag/2003Jul/0085">
										this thread
									</a>
									.
								</li><li>
									See discussion of
									<a href="http://lists.w3.org/Archives/Public/www-tag/2003Jul/0377">
										information resources
									</a></li><li>
									See discussion of phrase "on
									the Web" at
									<a href="http://www.w3.org/2003/07/28-tag-summary#httpRange-14">
										22 Jul 2003 teleconference
									</a>
									and subsequent threads
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Jul/0317">
										Summary and proposal from NW
									</a></li><li><a href="http://esw.w3.org/topic/GoodURIs">
										GoodURIs
									</a></li></ul></dd><dt><a href="http://www.w3.org/2001/tag/2005/06/14-16-minutes#item023">agreed</a> on 15 Jun 2005</dt><dd><p>
							The TAG provides advice to the community
							that they may mint "http" URIs for any
							resource provided that they follow this
							simple rule for the sake of removing
							ambiguity:
						</p><ul><li>
									If an "http" resource responds to a
									GET request with a 2xx response,
									then the resource identified by that
									URI is an information resource;
								</li><li>
									If an "http" resource responds to a
									GET request with a 303 (See Other)
									response, then the resource
									identified by that URI could be any
									resource;
								</li><li>
									If an "http" resource responds to a
									GET request with a 4xx (error)
									response, then the nature of the
									resource is unknown.
								</li></ul><h5>Acknowledgment cycle</h5><dl><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2005Jun/0039">announced by group  on 18 Jun 2005</a></dt></dl></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						TBL
					</h5><ul><li><a href="http://www.w3.org/2004/05/14-tag-summary#httpRange-14-2">accepted on 13 May 2004</a><br /><p>
									Write up a summary position to close
									httpRange-14, text for document.s
								</p></li><li><a href="http://www.w3.org/2004/05/HTTPRange14.txt">proposal on 14 May 2004</a><br /><p>
									Proposed text, resolution, new issue
								</p></li><li><a href="http://www.w3.org/2001/tag/2005/06/14-16-minutes#item023">dropped on 15 Jun 2005</a></li></ul></div><div class="details-action decided"><h5>
						RF
					</h5><ul><li><a href="http://www.w3.org/2004/05/14-tag-summary#httpRange-14-2">accepted on 13 May 2004</a><br /><p>
									Write up a summary position to close
									httpRange-14, text for document.s
								</p></li><li><a href="http://lists.w3.org/Archives/Member/tag/2004May/0049">proposal on 14 May 2004</a><br /><p>
									Proposed text, resolution, new issue
								</p></li><li><a href="http://www.w3.org/2001/tag/2005/06/14-16-minutes#item023">dropped on 15 Jun 2005</a></li></ul></div><div class="details-action decided"><h5>
						RL
					</h5><ul><li><a href="http://www.w3.org/2007/02/26-tagmem-minutes#action03">accepted on 26 Feb 2007</a><br /><p>
									Rhys to consider and draft a finding
									around the issues raised by
									httpRange-14.
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2007May/0049.html">proposal on 27 May 2007</a><br /><p>
									Email announcing first public draft
									from Rhys
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2007May/0049.html">completed on 27 May 2007</a></li></ul></div><div class="details-action"><h5>
						RL
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2007/06/11-minutes#action03">accepted on 11 Jun 2007</a><br /><p>
									Rhys to revise Dereferencing HTTP
									URIs finding in response to F2F
									discussion. Continued:
									<a href="http://www.w3.org/2001/tag/2007/07/09-tagmem-minutes#action06">
										9 July 2007
									</a></p></li><li><a href="http://www.w3.org/2001/tag/group/track/actions/6">proposal on 24 Aug 2007</a><br /><p>
									Tracking transferred to tracker
									<a href="http://www.w3.org/2001/tag/group/track/actions/6">
										ACTION-6
									</a>
									and to issue
									<a href="http://www.w3.org/2001/tag/group/track/issues/57">
										HttpRedirections-57
									</a></p></li></ul></div><div class="details-action decided"><h5>SW</h5><ul><li><a href="http://www.w3.org/2001/tag/2007/06/11-minutes#action05">accepted on 11 Jun 2007</a><br /><p>
									Stuart to review
									<a href="http://www.dfki.uni-kl.de/~sauermann/2006/11/cooluris/">
										"Cool URIs for the Semantic Web"
									</a></p></li><li><a href="http://www.w3.org/2001/tag/2007/07/09-tagmem-minutes#action04">completed on 9 Jul 2007</a><br /><p>
									Review posted to
									<a href="http://lists.w3.org/Archives/Public/www-tag/2007Jun/0075">
										www-tag
									</a>
									.
								</p></li></ul></div><div class="details-action decided"><h5>NW</h5><ul><li><a href="http://www.w3.org/2001/tag/2007/06/11-minutes#action05">accepted on 11 Jun 2007</a><br /><p>
									Norm to review
									<a href="http://www.dfki.uni-kl.de/~sauermann/2006/11/cooluris/">
										"Cool URIs for the Semantic Web"
									</a></p></li><li><a href="http://www.w3.org/2001/tag/2007/07/09-tagmem-minutes#action03">dropped on 9 Jul 2007</a></li></ul></div></div></div><div class="issue"><h3><a id="URIEquivalence-15" name="URIEquivalence-15">URIEquivalence-15</a>: 
				When are two URI variants considered equivalent?
			 [<a href="issues.html#URIEquivalence-15">link to this issue</a>]</h3><p>From Joseph Reagle:</p><p>
							Stephen [Farrell] has asked an interesting
							question below that I expect will be
							important to any activity that uses URIs as
							identifiers in the context of a
							semantic/security application: when are two
							URI variants considered identical?
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><ul><li>URI</li><li>XML Namespaces</li></ul></dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2002/07/22-tag-summary#L4009">22 Jul 2002</a>, <a href="http://www.w3.org/2002/07/29-tag-summary#URIEquivalence-15">29 Jul 2002</a>, <a href="http://www.w3.org/2002/08/30-tag-summary#URIEquivalence-15">30 Aug 2002</a>, <a href="http://www.w3.org/2002/11/18-tag-summary#URIEquivalence-15">18 Nov 2002</a>, <a href="http://www.w3.org/2002/12/16-tag-summary#URIEquivalence-15">16 Dec 2002</a>, <a href="http://www.w3.org/2003/01/20-tag-summary#URIEquivalence-15">20 Jan 2003</a>, <a href="http://www.w3.org/2003/02/06-tag-summary#URIEquivalence-15">7 Feb 2003</a>, <a href="http://www.w3.org/2003/03/24-tag-summary#URIEquivalence-15">24 Mar 2003</a>, <a href="http://www.w3.org/2003/03/31-tag-summary#URIEquivalence-15">31 Mar 2003</a>, <a href="http://www.w3.org/2003/04/14-tag-summary#URIEquivalence-15">14 Apr 2003</a>, <a href="http://lists.w3.org/Archives/Public/www-tag/2003Apr/0121">28 Apr 2003</a>, <a href="http://www.w3.org/2003/06/30-tag-summary#issues-walkthrough">30 Jun 2003</a>, <a href="http://www.w3.org/2003/12/04-tag-summary">5 Dec 2002</a>, <a href="http://www.w3.org/2004/01/05-tag-summary#URIEquivalence-15">5 Jan 2004</a>, <a href="http://www.w3.org/2004/03/02-tag-summary">2 Mar 2004</a>, <a href="http://www.w3.org/2004/03/22-tag-summary#webarch">22 Mar 2004</a>, <a href="http://www.w3.org/2004/05/14-tag-summary#URIEquivalence-15">14 May 2004</a></dd><dt>Categories</dt><dd></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Feb/0129">raised</a> on 19 Feb 2002 by 
						Joseph Reagle
					</dt><dd></dd><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Apr/0017">accepted</a> on 1 Apr 2002</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="http://www.w3.org/TR/REC-xml-names/">
										XML Namespaces
									</a></li><li><a href="http://www.w3.org/International/2002/draft-duerst-iri-01.txt">
										Internationalized Resource
										Identifiers (IRI)
									</a></li><li><a href="http://www.w3.org/TR/2002/WD-charmod-20020430/">
										Character Model for the Web
									</a>
									, notably
									<a href="http://www.w3.org/TR/charmod/#sec-Normalization">
										Chapter 4
									</a>
									and
									<a href="http://www.w3.org/TR/charmod/#sec-URIs">
										Chapter 8
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002May/0113">
										Email from Misha Wolf
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002May/0161">
										Input from Martin Duerst
									</a>
									on IRIs
								</li><li>
									See text from TimBL on
									<a href="http://www.w3.org/DesignIssues/Axioms#canonicalization">
										URI canonicalization
									</a>
									.
								</li><li>
									Assigned initially to Dan Connolly
									(at
									<a href="http://www.w3.org/2002/08/30-tag-summary#URIEquivalence-15">
										30 Aug 2002 teleconf
									</a>
									). See
									<a href="http://lists.w3.org/Archives/Public/www-tag/2002Sep/0050">
										Proposal from DanC
									</a></li><li>
									Email from Larry Masinter proposing
									<a href="http://lists.w3.org/Archives/Public/www-tag/2003Feb/0090">
										A simpler solution to %7e vs %7E
										vs ~ in namespace comparison
									</a></li><li><a href="http://www.w3.org/mid/OFA2836785.248B04E4-ON85256CCA.0052F484@lotus.com">
										Proposal from Noah M
									</a>
									to say "Hex-escapes aren't
									allowed [in xml namespace names]
									Don't use them."
								</li><li>
									Email from TBL about
									<a href="http://lists.w3.org/Archives/Public/uri/2003Jan/0005">
										Rationalizing the term URI
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Mar/0063">
										Email from Larry Masinter
									</a>
									about
									<a href="http://lists.w3.org/Archives/Public/uri/2003Mar/0043">
										URI BOF minutes from IETF56
									</a></li></ul></dd><dt><a href="http://www.w3.org/2003/04/14-tag-summary#URIEquivalence-15">agreed</a> on 14 Apr 2003</dt><dd><p>
							Draft finding:

								URI Comparison
(link not maintained but see RFC3986).
							. This has been integrated into RFC2396bis (
							<a href="http://cvs.apache.org/viewcvs.cgi/ietf-uri/rev-2002/">
								CVS repository
							</a>
							); the TAG expects to follow the progress of
							RFC2396bis. Commentary and resolution should
							happen through the IETF process.
						</p><h5>Acknowledgment cycle</h5><dl><dt><a href="http://www.w3.org/2003/04/14-tag-summary#URIEquivalence-15">announced by group  on 14 Apr 2002</a></dt><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2003Dec/0187"> agreement by reviewer  on 12 Dec 2002</a></dt></dl></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>SW</h5><ul><li><a href="http://www.w3.org/2003/06/30-tag-summary#issues-walkthrough">accepted on 30 Jun 2003</a><br /><p>
									Track RFC2396bis where
										Tim Bray text
									
									has been integrated. Comment within
									the IETF process.
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2004May/0038">proposal on 18 May 2004</a><br /><p>
									SW believes RFC2396 largely
									incorporates the necessary text; see
									his email for details.
								</p></li><li><a href="http://www.w3.org/2004/05/24-tag-summary">completed on 24 May 2004</a><br /><p>
									TB's text successfully incorporated.
								</p></li></ul></div><div class="details-action decided"><h5>
						TBL
					</h5><ul><li><a href="http://www.w3.org/2004/01/05-tag-summary#URIEquivalence-15">accepted on 5 Jan 2004</a> (due 2004-02-06)
            <br /><p>
									Review RFC2396 bis (current Editor's
									Draft) in preparation for IETF/W3C
									coordination meeting 6 Feb.
								</p></li><li><a href="http://www.w3.org/2004/03/22-tag-summary#webarch">completed on 22 Mar 2004</a><br /><p>
									TBL reported that he sent comments
									to RF about the RFC and Roy
									acknowledged having received them.
								</p></li></ul></div></div></div><div class="issue"><h3><a id="HTTPSubstrate-16" name="HTTPSubstrate-16">HTTPSubstrate-16</a>: 
				Should HTTP be used as a substrate protocol? Does W3C
				agree with RFC 3205?
			 [<a href="issues.html#HTTPSubstrate-16">link to this issue</a>]</h3><p>From Mark Nottingham:</p><p>
							The IETF has recently published RFC3205,
							"On the use of HTTP as a
							Substrate" [1] as Best Current
							Practice.
						</p><p>
							This document makes a number of
							recommendations regarding the use of HTTP.
							Some are reasonable, such as guidelines
							about what kinds of scenarios the HTTP is
							most useful in, how to use media types and
							methods to extend the HTTP, etc. However, it
							also bases a number of recommendations on a
							fuzzily-defined concept of 'traditional use'
							of the HTTP. These directives may seriously
							limit the future potential of the Web,
							effectively freezing its capability to
							common practice in 2001."
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><a href="http://www.ietf.org/rfc/rfc3205.txt">
						RFC3205
					</a></dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2003/06/30-tag-summary#issues-walkthrough">30 Jun 2003</a>, <a href="http://www.w3.org/2004/05/14-tag-summary#HTTPSubstrate-16">12 May 2004</a>, <a href="http://www.w3.org/2005/02/07-tagmem-minutes#item05">7 Feb 2005</a>, <a href="http://www.w3.org/2005/09/21-tagmem-minutes#item02">21 Sep 2005</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Mar/0182">raised</a> on 24 Mar 2002 by 
						Mark Nottingham
					</dt><dd></dd><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Apr/0019">accepted</a> on 1 Apr 2002</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="http://lists.w3.org/Archives/Public/xml-dist-app/2000Dec/0061">
										Response from Randy Hall to IETF
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Apr/0221">
										Message from Roy Fielding
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Feb/0083">
										Propoposed criticsm of RFC3205
									</a>
									from TBL.
								</li><li><a href="http://www.w3.org/mid/20030208173857.E15554@www.markbaker.ca">
										Email from Mark Baker
									</a>
									on tunneling as a property of the
									application.
								</li><li>
									See
									<a href="http://lists.w3.org/Archives/Public/www-tag/2003Feb/0208">
										message from Larry Masinter
									</a>
									w.r.t. Web services.
								</li></ul></dd><dt><a href="http://www.w3.org/2004/05/14-tag-summary#HTTPSubstrate-16">deferred</a> on 12 May 2004</dt><dd><p>
							The TAG decided to defer this issue pending
							any attempt to enforce RFC3205.
						</p></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						RF
					</h5><ul><li><a href="http://www.w3.org/2003/02/06-tag-summary">accepted on 6 Feb 2003</a><br /><p>
									Write a response to IESG asking
									whether the Web services example in
									the SOAP 1.2 primer is intended to
									be excluded from RFC 3205
								</p></li><li><a href="http://www.w3.org/2004/05/14-tag-summary#HTTPSubstrate-16">dropped on 12 May 2004</a><br /><p>Closed as issue is deferred.</p></li></ul></div><div class="details-action decided"><h5>
						RF
					</h5><ul><li><a href="http://www.w3.org/2004/05/14-tag-summary#HTTPSubstrate-16">accepted on 12 May 2003</a><br /><p>
									Write descriptive paragraph
									explaining this issue's state.
								</p></li><li><a href="http://www.w3.org/2004/08/10-tagmem-irc">dropped on 10 Aug 2004</a><br /><p>
									Roy reported on his discussion at
									the IETF meeting.
								</p></li></ul></div></div></div><div class="issue"><h3><a id="charmodReview-17" name="charmodReview-17">charmodReview-17</a>: 
				Request to review "Character Model for the
				Web" Last Call document
			 [<a href="issues.html#charmodReview-17">link to this issue</a>]</h3><p>
							Request to review "Character Model for
							the Web" Last Call document
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><a href="http://www.w3.org/TR/charmod/">
						Character Model for the Web 1.0
					</a></dd><dt>Discussion history</dt><dd><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jun/0019">3 Jun 2002</a>, <a href="http://www.w3.org/2002/06/24-tag-summary">24 Jun 2002</a>, <a href="http://www.w3.org/2003/07/14-tag-summary#charmod">14 Jul 2003</a>, <a href="http://www.w3.org/2003/09/08-tag-summary#charmodReview-17">8 Sep 2003</a>, <a href="http://www.w3.org/2003/10/06-tag-summary#charmodReview-17">8 Oct 2003</a>, <a href="http://www.w3.org/2004/02/02-tag-summary#i18n">2 Feb 2004</a>, <a href="http://www.w3.org/2004/03/15-tag-summary">15 Mar 2004</a>, <a href="http://www.w3.org/2004/03/22-tag-summary#charmodReview-17">22 Mar 2004</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Member/chairs/2002AprJun/0018">raised</a> on 16 Apr 2002 by 
						Misha Wolf
					, on behalf of <a href="/International">
						I18N WG
					</a></dt><dd></dd><dt><a href="http://www.w3.org/2002/04/29-tag-summary#issue:">accepted</a> on 29 Apr 2002</dt><dd></dd><dt><a href="http://www.w3.org/2002/06/24-tag-summary">agreed</a> on 24 Jun 2002</dt><dd><p><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jun/0020">
								Comments sent by Norm to the I18N
								comments list
							</a>
							and
							<a href="http://lists.w3.org/Archives/Member/tag/2003Jul/0052">
								reminder from Dan Connolly
							</a>
							. See also
							<a href="http://lists.w3.org/Archives/Public/www-tag/2002May/0164">
								Comments from CL
							</a>
							. See other TAG resolutions regarding this
							issue in
							<a href="http://lists.w3.org/Archives/Public/www-tag/2002Jun/0019">
								3 Jun minutes
							</a>
							.
						</p><h5>Acknowledgment cycle</h5><dl><dt><a href="http://www.w3.org/2002/06/24-tag-summary">announced by group  on 24 Jun 2002</a></dt></dl></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>SW</h5><ul><li><a href="http://www.w3.org/2003/10/06-tag-summary">accepted on 8 Oct 2003</a><br /><p>
									Follow up with I18N folks on status
									of TAG's charmod comments. See
									<a href="http://lists.w3.org/Archives/Member/tag/2003Sep/0019">
										Mail from DC to I18N WG in light
										of new Charmod draft
									</a></p></li><li><a href="http://www.w3.org/2003/11/03-tag-summary">proposal on 3 Nov 2003</a><br /><p>
									SW has discussed this with new I18N
									chair. SW invited I18N reps to
									participate in a TAG teleconf,
									probably in Dec 2003. At
									<a href="http://www.w3.org/2004/03/15-tag-summary">
										15 March 2004 teleconf
									</a>
									, SW took an additional action to
									request a two-week extension for TAG
									comments.
								</p></li><li><a href="http://www.w3.org/2004/03/22-tag-summary#charmodReview-17">completed on 22 Mar 2004</a><br /><p>
									SW's action, by virtue of the TAG
									agreeing to proposals from CL and
									DC, seems to have been completed.
								</p></li></ul></div><div class="details-action decided"><h5>
						TB
					</h5><ul><li><a href="http://www.w3.org/2004/01/26-tag-summary#i18n">accepted on 26 Jan 2004</a><br /><p>
									Review charmod language re:
									reference to Unicode std.
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2004Mar/0007">proposal on 4 Mar 2004</a><br /><p>Review from Tim Bray</p></li><li><a href="http://lists.w3.org/Archives/Member/tag/2004Jul/0007">subsumed on 8 Jul 2004</a></li></ul></div><div class="details-action decided"><h5>
						CL
					</h5><ul><li><a href="http://www.w3.org/2004/01/26-tag-summary#i18n">accepted on 26 Jan 2004</a> (due 2004-02-02)
            <br /><p>
									Pull out items from I18N WG response
									to TAG issues for meeting
									discussion.
								</p></li><li><a href="http://lists.w3.org/Archives/Member/tag/2004Feb/0008">proposal on 2 Feb 2004</a><br /><p>
									Summary of position on I18N WG
									replies.
								</p></li><li><a href="http://www.w3.org/2004/02/02-tag-summary#i18n">completed on 2 Feb 2004</a><br /><p>
									CL to respond to I18N WG per his
									proposal.
								</p></li></ul></div><div class="details-action decided"><h5>
						CL
					</h5><ul><li><a href="http://www.w3.org/2004/01/26-tag-summary#i18n">accepted on 2 Feb 2004</a><br /><p>
									Respond to I18N WG per previous
									proposal.
								</p></li><li><a href="http://www.w3.org/2004/03/22-tag-summary#charmodReview-17">completed on 22 Mar 2004</a><br /><p>
									This action has been completed and
									replaced by an action assigned 22
									March.
								</p></li></ul></div><div class="details-action decided"><h5>
						DC
					</h5><ul><li><a href="http://www.w3.org/2004/01/26-tag-summary#i18n">accepted on 26 Jan 2004</a><br /><p>
									Look at
									<a href="http://www.w3.org/International/Group/2002/charmod-lc/SortByGroup#C127">
										I18N issue C127
									</a>
									: "Say that the IRI form is used in
									the document instance and the
									hexified URI form when it goes over
									the wire"
								</p></li><li><a href="http://www.w3.org/2004/06/28-tag-summary">subsumed on 28 Jun 2004</a></li></ul></div><div class="details-action decided" id="cl1-20040322"><h5>
						CL
					</h5><ul><li><a href="http://www.w3.org/2004/03/22-tag-summary#charmodReview-17">accepted on 22 Mar 2004</a><br /><p>
									Suggest wording to I18N WG regarding
									C068.
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2004Mar/0069">proposal on 29 Mar 2004</a></li><li><a href="http://www.w3.org/2004/06/28-tag-summary">subsumed on 28 Jun 2004</a></li></ul></div><div class="details-action decided"><h5>
						CL
					</h5><ul><li><a href="http://www.w3.org/2004/03/22-tag-summary#charmodReview-17">accepted on 22 Mar 2004</a><br /><p>
									Write up TAG's complete LC comments
									and send them to the I18N WG (cc'ing
									www-tag).
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2004Mar/0069">proposal on 29 Mar 2004</a></li><li><a href="http://www.w3.org/2004/06/28-tag-summary">subsumed on 28 Jun 2004</a></li></ul></div></div></div><div class="issue"><h3><a id="qnameAsId-18" name="qnameAsId-18">qnameAsId-18</a>: Is it ok to use Qnames as Identifiers? [<a href="issues.html#qnameAsId-18">link to this issue</a>]</h3><p>Is it ok to use Qnames as Identifiers?</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><a href="http://www.w3.org/TR/1999/REC-xml-names-19990114/#ns-qualnames">
						Namespaces in XML, section 3
					</a></dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2002/05/20-tag-summary#qnameAsID">20 May 2002</a>, <a href="http://www.w3.org/2002/06/10-tag-summary">10 Jun 2002</a>, <a href="http://www.w3.org/2002/06/17-tag-summary">17 Jun 2002</a>, <a href="http://www.w3.org/2002/06/24-tag-summary">24 Jun 2002</a>, <a href="http://www.w3.org/2002/07/15-tag-summary#Qnames">15 Jul 2002</a>, <a href="http://www.w3.org/2003/12/15-tag-summary#qnameAsId-18">15 Dec 2003</a>, <a href="http://www.w3.org/2004/01/12-tag-summary#qnameAsId-18">12 Jan 2004</a>, <a href="http://www.w3.org/2004/02/09-tag-summary#qnameAsId-18">9 Feb 2004</a>, <a href="http://www.w3.org/2004/02/23-tag-summary#qnameAsId-18">23 Feb 2004</a>, <a href="http://www.w3.org/2004/03/02-tag-summary#qnameAsId-18">2 Mar 2004</a>, <a href="http://www.w3.org/2004/03/15-tag-summary">15 Mar 2004</a></dd><dt>Categories</dt><dd></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Apr/0204">raised</a> on 19 Apr 2002 by 
						Joseph Reagle
					, on behalf of <a href="http://www.w3.org/2001/XKMS/">
						XKMS WG
					</a></dt><dd></dd><dt><a href="http://www.w3.org/2002/04/29-tag-summary#issue:">accepted</a> on 29 Apr 2002</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jun/0183">
										A radical finding on Using
										Qualified Names (QNames) as
										Identifiers in Content
									</a>
									from Norm Walsh
								</li></ul></dd><dt><a href="http://www.w3.org/2002/07/22-tag-summary#Update">agreed</a> on 22 Jul 2002</dt><dd><p>
							Finding:
							<a href="/2001/tag/doc/qnameids">
								Using QNames as Identifiers
							</a></p><h5>Acknowledgment cycle</h5><dl><dt><a href="http://www.w3.org/2002/07/22-tag-summary#Update">announced by group  on 22 Jul 2002</a></dt><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2003Dec/0187"> agreement by reviewer  on 12 Dec 2002</a></dt></dl></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>NW</h5><ul><li><a href="http://www.w3.org/2004/01/12-tag-summary#qnameAsId-18">accepted on 12 Jan 2004</a><br /><p>
									Ask the Schema WG to review the
									draft finding.
								</p></li><li><a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-wg/2004Feb/0082">proposal on 27 Feb 2004</a><br /><p>
									Ask the Schema WG to review the
									draft finding.
								</p></li><li><a href="">completed on 15 Mar 2004</a><br /><p>
									See revised finding
									<a href="/2001/tag/doc/qnameids">
										Using QNames as Identifiers
									</a>
									.
								</p></li></ul></div><div class="details-action decided"><h5>NW</h5><ul><li><a href="http://www.w3.org/2004/01/12-tag-summary#qnameAsId-18">accepted on 12 Jan 2004</a><br /><p>
									Revise
									<a href="http://www.w3.org/2001/tag/doc/qnameids-2004-01-06">
										6 Jan 2004 draft finding
									</a>
									for review and possible approval by
									TAG.
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2004Jan/0021">proposal on 14 Jan 2004</a><br /><ul><li><a href="http://www.w3.org/2001/tag/doc/qnameids">
											27 Feb 2004 Draft
										</a></li><li>
										Additional revisions expected
										per
										<a href="http://www.w3.org/2004/02/23-tag-summary#qnameAsId-18">
											23 Feb teleconf
										</a>
										.
									</li><li>
										Revised draft for 19 Jan
										teleconf.
									</li></ul></li><li><a href="http://www.w3.org/2004/03/15-tag-summary">completed on 15 Mar 2004</a><br /><p>
									See revised finding
									<a href="/2001/tag/doc/qnameids">
										Using QNames as Identifiers
									</a>
									.
								</p></li></ul></div><div class="details-action decided"><h5>
						DC
					</h5><ul><li><a href="http://www.w3.org/2004/01/26-tag-summary">accepted on 26 Jan 2004</a><br /><p>
									Review 14 Jan draft of
									<a href="http://www.w3.org/2001/tag/doc/qnameids-2004-01-14">
										Qname Finding
									</a>
									.
								</p></li><li><a href="http://www.w3.org/2004/03/15-tag-summary#qnameAsId-18">dropped on 15 Mar 2004</a><br /><p>Dropped and finding accepted.</p></li></ul></div><div class="details-action decided"><h5>
						TB
					</h5><ul><li><a href="http://www.w3.org/2004/01/26-tag-summary">accepted on 26 Jan 2004</a><br /><p>
									Review 14 Jan draft of
									<a href="http://www.w3.org/2001/tag/doc/qnameids-2004-01-14">
										Qname Finding
									</a>
									.
								</p></li><li><a href="http://www.w3.org/2004/03/15-tag-summary#qnameAsId-18">dropped on 15 Mar 2004</a><br /><p>Dropped and finding accepted.</p></li></ul></div><div class="details-action decided"><h5>
						TBL
					</h5><ul><li><a href="http://www.w3.org/2004/01/26-tag-summary">accepted on 26 Jan 2004</a><br /><p>
									Review 14 Jan draft of
									<a href="http://www.w3.org/2001/tag/doc/qnameids-2004-01-14">
										Qname Finding
									</a>
									.
								</p></li><li><a href="http://www.w3.org/2004/03/15-tag-summary#qnameAsId-18">completed on 15 Mar 2004</a><br /><p>
									TBL's comments taken into account
									and finding accepted.
								</p></li></ul></div></div></div><div class="issue"><h3><a id="formattingProperties-19" name="formattingProperties-19">formattingProperties-19</a>: 
				Reuse existing formatting properties/names, coordinate
				new ones
			 [<a href="issues.html#formattingProperties-19">link to this issue</a>]</h3><p>
							Reuse existing formatting properties/names,
							coordinate new ones
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references">CSS3</dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2002/06/17-tag-summary">17 Jun 2002</a>, <a href="http://www.w3.org/2002/07/08-tag-summary#formatting">8 Jul 2002</a>, <a href="http://www.w3.org/2002/07/15-tag-summary#Consistenc">15 Jul 2002</a>, <a href="http://www.w3.org/2003/12/04-tag-summary">5 Dec 2002</a></dd><dt>Categories</dt><dd></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002May/0042">raised</a> on 8 May 2002 by 
						Steve Zilles
					</dt><dd></dd><dt><a href="http://www.w3.org/2002/05/20-tag-summary#formattingProperties">accepted</a> on 20 May 2002</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li>CSS2</li><li>XSLT</li><li>HTML CG Work</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jun/0126">
										Proposed changes from Rick
										Jeliffe
									</a></li></ul></dd><dt><a href="http://www.w3.org/2002/07/22-tag-summary#Update">agreed</a> on 22 Jul 2002</dt><dd><p>
							Finding:
							<a href="http://www.w3.org/2001/tag/doc/formatting-properties">
								Consistency of Formatting Property
								Names, Values, and Semantics
							</a></p><h5>Acknowledgment cycle</h5><dl><dt><a href="http://www.w3.org/2002/07/22-tag-summary#Update">announced by group  on 22 Jul 2002</a></dt></dl></dd></dl></div><div class="issue"><h3><a id="errorHandling-20" name="errorHandling-20">errorHandling-20</a>: 
				What should specifications say about error handling?
			 [<a href="issues.html#errorHandling-20">link to this issue</a>]</h3><p>
							What should specifications say about error
							handling?
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><a href="http://www.w3.org/TR/">
						W3C specifications
					</a></dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2002/05/27-tag-summary#newissue1">27 May 2002</a>, <a href="http://lists.w3.org/Archives/Public/www-tag/2002Jun/0019">3 Jun 2002</a>, <a href="http://www.w3.org/2003/02/06-tag-summary#errorHandling-20">6 Feb 2003</a>, <a href="http://www.w3.org/2003/06/30-tag-summary#issues-walkthrough">30 Jun 2003</a>, <a href="http://www.w3.org/2003/11/15-tag-summary">15 Nov 2003</a>, <a href="http://www.w3.org/2004/01/05-tag-summary#errorHandling-20">5 Jan 2004</a>, <a href="http://www.w3.org/2004/03/02-tag-summary#error-handling">2 Mar 2004</a></dd><dt>Categories</dt><dd></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002May/0124">raised</a> on 22 May 2002 by 
						Rob Lanphier
					</dt><dd></dd><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jun/0019">accepted</a> on 3 Jun 2002</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="http://www.w3.org/QA/WG/qawg-issues-html#x51">
										QAWG issue 51
									</a></li></ul></dd><dt><a href="http://www.w3.org/2003/11/15-tag-summary">agreed</a> on 15 Nov 2003</dt><dd><p>
							The TAG believes it has addressed a majority
							of points about the issue in the 11 Nov 2003
							draft, with pointers to relevant sections
							3.4 and 1.2.2, as well as the section on
							versioning and extensibility. The TAG
							declines at this time to handle the
							following questions raised by the reviewer:
							(1) Extension of XML. Answer: Application
							dependent. (2) Handling of deprecated
							elements.
						</p><h5>Acknowledgment cycle</h5><dl><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2003Dec/0044">announced by group  on 2 Dec 2003</a></dt><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2003Dec/0183"> agreement by reviewer  on 12 Dec 2003</a></dt></dl></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						CL
					</h5><ul><li><a href="http://www.w3.org/2003/11/15-tag-summary#eh">accepted on 15 Nov 2003</a><br /><p>
									Write text to reviewer about the
									TAG's decision on this issue.
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Dec/0044">proposal on 2 Dec 2003</a><br /><p>Email sent to reviewer.</p></li><li><a href="http://www.w3.org/2004/01/05-tag-summary#errorHandling-20">completed on 5 Jan 2004</a><br /><p>
									See
									<a href="http://lists.w3.org/Archives/Public/www-tag/2003Dec/0183">
										reply from Rob Lanphier
									</a></p></li></ul></div></div></div><div class="issue"><h3><a id="RFC3023Charset-21" name="RFC3023Charset-21">RFC3023Charset-21</a>: 
				Do all "shoulds" of RFC 3023 section 7.1
				apply?
			 [<a href="issues.html#RFC3023Charset-21">link to this issue</a>]</h3><p>
							Do all "shoulds" of RFC 3023
							section 7.1 apply?
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><ul><li><a href="http://www.w3.org/TR/NOTE-rdfarch">
						W3C Data Formats
					</a></li><li><a href="http://www.ietf.org/rfc/rfc3023.txt">
						RFC3023
					</a></li></ul></dd><dt>Discussion history</dt><dd><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jun/0019">3 Jun 2002</a>, <a href="http://www.w3.org/2002/08/26-tag-summary#RFC3023Charset-21">26 Aug 2002</a>, <a href="http://lists.w3.org/Archives/Public/www-tag/2002Sep/0085">9 Sep 2002</a></dd><dt>Categories</dt><dd></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jan/0063">raised</a> on 9 Jan 2002 by 
						Mark Baker
					, on behalf of <a href="http://www.w3.org/2000/xp/">
						XML Protocol WG
					</a></dt><dd></dd><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jun/0019">accepted</a> on 3 Jun 2002</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li>
									This issue was split off from issue
									<a href="#w3cMediaType-1">
										w3cMediaType-1
									</a></li></ul></dd><dt><a href="http://www.w3.org/2002/10/07-tag-summary#RFC3023Charset-21">agreed</a> on 7 Oct 2002</dt><dd><p><a href="http://www.w3.org/2001/tag/2002/0129-mime">
								TAG Finding: Internet Media Type
								registration, consistency of use
							</a></p><h5>Acknowledgment cycle</h5><dl><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Oct/0155">announced by group  on 8 Oct 2003</a></dt></dl></dd></dl></div><div class="issue"><h3><a id="augmentedInfoset-22" name="augmentedInfoset-22">augmentedInfoset-22</a>: Infoset augmentation outside of PSVI? [<a href="issues.html#augmentedInfoset-22">link to this issue</a>]</h3><p>
							So I recommend a TAG finding along the
							following lines:
						</p><ol><li>
									Type-augmented XML is a good thing
									and a recommendation should be
									prepared describing it both at the
									infoset and syntax level. (I gather
									there is already some work along
									these lines in XML Schema?). Serious
									consideration should be given to
									80/20 points rather than simply
									re-using the plethora of primitive
									types from XML Schema.
								</li><li>
									Type-augmented XML has nothing to
									say about default values created in
									any schema.
								</li><li>
									Any software can create and/or use
									type-augmented XML, whether or not
									any validation is being performed.
								</li><li>
									Work on XQuery and other things that
									require a Type-Augmented Infoset
									must not depend on schema
									processing, and should not have
									normative linkages to any schema
									language specifications.
								</li></ol><dl><dt class="references">Request
	      concerning</dt><dd class="references"><a href="http://www.w3.org/TR/xmlschema-1/">
						XML Schema Part 1: Structures
					</a></dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2002/06/17-tag-summary">17 Jun 2002</a>, <a href="http://www.w3.org/2002/07/08-tag-summary#infoset">8 Jul 2002</a>, <a href="http://www.w3.org/2002/08/26-tag-summary#augmentedInfoset-22">26 Aug 2002</a></dd><dt>Categories</dt><dd></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jun/0085">raised</a> on 12 Jun 2002 by 
						Tim Bray
					, on behalf of <a href="http://www.w3.org/2001/tag/">
						TAG
					</a></dt><dd></dd><dt><a href="http://www.w3.org/2002/06/17-tag-summary">accepted</a> on 17 Jun 2002</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-wg/2002Jun/0035">
										Email from Noah Mendelsohn
									</a></li><li><a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-wg/2002Jun/0039">
										Email from Mary Holstege
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jun/0146">
										Summary, proposals from Tim Bray
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jun/0149">
										Proposal from Rick Jeliffe
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jul/0159">
										Request from Tim Bray to
										"unraise"
									</a>
									. See thread for pushback.
								</li></ul></dd><dt><a href="http://www.w3.org/2002/08/26-tag-summary#augmentedInfoset-22">agreed</a> on 26 Aug 2002</dt><dd><p>
							For now, the TAG has decided the issue by
							withdrawing it. From TB: "I learned
							that while there are linkages between xquery
							and xml schema, they are non-normative; you
							can implement xquery with other schema
							languages; so I don't see an architecture
							issue at the moment. I submitted a large
							comment to the xquery process that there
							does remain too much intermingling with xml
							schema that could easily go away. If the two
							specs aren't made sufficiently independent,
							I expect to come back to the TAG."
						</p><h5>Acknowledgment cycle</h5><dl><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Aug/0320">announced by group  on 26 Aug 2002</a></dt><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Aug/0320"> agreement by reviewer  on 26 Aug 2003</a></dt><dd><p>
									Acknowledged by TB by virtue of WG
									agreement
								</p></dd></dl></dd></dl></div><div class="issue"><h3><a id="xlinkScope-23" name="xlinkScope-23">xlinkScope-23</a>: What is the scope of using XLink? [<a href="issues.html#xlinkScope-23">link to this issue</a>]</h3><p>
							For me this questions depends on whether the
							document type is a human-readable hypertext
							document, when generic hypertext xml tools
							would benefit from knowing what is a link,
							and whether significance of the URI in
							question is a hypertext link or something
							different.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><a href="http://www.w3.org/TR/xlink/">
						XML Linking Language (XLINK)
					</a></dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2002/06/17-tag-summary">17 Jun 2002</a>, <a href="http://www.w3.org/2002/07/01-tag-summary#xlinkScope-23">1 Jul 2002</a>, <a href="http://www.w3.org/2002/08/26-tag-summary#xlinkScope-23">26 Aug 2002</a>, <a href="http://www.w3.org/2002/08/30-tag-summary#xlinkScope-23">30 Aug 2002</a>, <a href="http://lists.w3.org/Archives/Public/www-tag/2002Sep/0127">16 Sep 2002</a>, <a href="http://www.w3.org/2002/09/24-tag-summary#xlinkScope-23">24 Sep 2002</a>, <a href="http://www.w3.org/2002/10/07-tag-summary#xlinkScope-23">7 Oct 2002</a>, <a href="http://www.w3.org/2002/10/21-tag-summary#xlinkScope-23">21 Oct 2002</a>, <a href="http://www.w3.org/2002/11/11-tag-summary#xlinkScope-23">11 Nov 2002</a>, <a href="http://www.w3.org/2002/11/18-tag-summary#xlinkScope-23">18 Nov 2002</a>, <a href="http://lists.w3.org/Archives/Public/www-tag/2003Jan/0263">16 Jan 2003</a>, <a href="http://www.w3.org/2003/01/20-tag-summary#xlinkScope-23">20 Jan 2003</a>, <a href="http://www.w3.org/2003/02/06-tag-summary#xlinkScope-23">6 Feb 2003</a>, <a href="http://www.w3.org/2003/03/17-tag-summary#xlinkScope-23">17 Mar 2003</a>, <a href="http://www.w3.org/2003/06/30-tag-summary#issues-walkthrough">30 Jun 2003</a>, <a href="http://www.w3.org/2004/03/02-tag-summary#xlinkScope-23">2 Mar 2003</a>, <a href="http://www.w3.org/2004/05/14-tag-summary#xlinkScope-23">14 May 2004</a>, <a href="http://www.w3.org/2001/tag/2004/10/05-07-tag#htxl">6 Oct 2004</a>, <a href="http://www.w3.org/2005/02/07-tagmem-minutes#item06">7 Feb 2005</a>, <a href="http://www.w3.org/2005/03/22-tagmem-minutes#item09">22 Mar 2005</a>, <a href="http://www.w3.org/2005/09/21-tagmem-minutes#item03">21 Sep 2005</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jun/0116">raised</a> on 14 Jun 2002 by 
						Tim Berners-Lee
					, on behalf of <a href="http://www.w3.org/2001/tag/">
						TAG
					</a></dt><dd></dd><dt><a href="http://www.w3.org/2002/06/17-tag-summary">accepted</a> on 17 Jun 2002</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jul/0158">
										Steven Pemberton (for HTML WG)
									</a></li><li><a href="http://www.w3.org/MarkUp/Group/2002/WD-hlink-20020531">
										HLink Working Draft
									</a>
									(Member-only)
								</li><li><a href="http://lists.w3.org/Archives/Member/tag/2002Aug/0008">
										Background from Mimasa
									</a>
									(TAG-only)
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Aug/0308">
										SVG and non-XLink attributes
									</a>
									.
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Sep/0246">
										Tech arguments from Steven
										Pemberton
									</a></li><li><a href="http://lists.w3.org/Archives/Member/w3c-xml-cg/2002Oct/0035">
										Notes from 22 Oct 2002 XML CG
										call
									</a>
									(Member-only).
								</li><li><a href="http://www.w3.org/DesignIssues/XLink">
										When to use XLink
									</a>
									from TBL.
								</li><li><a href="http://www.w3.org/2001/tag/2002/1028-XLink-HLink">
										Summary of technical discussion
									</a>
									from Stuart Williams.
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Jan/0020">
										SkunkLink: a skunkworks XML
										linking proposal
									</a>
									from Micah Dubinko
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Jan/0349">
										Summary of reqs
									</a>
									from Lloyd Rutledge.
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Jan/0373">
										Proposal for kind of xlink basic
									</a>
									from TB.
								</li><li>
									See
									<a href="http://lists.w3.org/Archives/Member/tag/2003Mar/0094">
										draft
									</a>
									, and
									<a href="http://lists.w3.org/Archives/Member/tag/2003Mar/0104">
										SW message
									</a>
									to CG chairs.
								</li><li><a href="http://www.w3.org/TR/xlink11/">
										XML Linking Language (XLink)
										Version 1.1
									</a></li></ul></dd><dt><a href="http://www.w3.org/2005/09/21-tagmem-minutes#item03">agreed</a> on 21 Sep 2005</dt><dd><p>
							Paragraph
							<a href="http://www.w3.org/TR/2004/REC-webarch-20041215/#xml-links">
								4.5.2 of Web Architecture
							</a>
							closes the issue. See also draft of
							<a href="http://www.w3.org/TR/xlink11/">
								XML Linking Language (XLink) Version 1.1
							</a>
							.
						</p><h5>Acknowledgment cycle</h5><dl><dt>Not started</dt></dl></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						CL
					</h5><ul><li><a href="http://www.w3.org/2003/06/30-tag-summary">accepted on 30 Jun 2003</a><br /><p>
									Ping the chairs of those groups
									asking for an update on
									xlinkScope-23.
								</p></li><li><a href="http://lists.w3.org/Archives/Member/tag/2003Oct/0076">proposal on 27 Oct 2003</a><br /><p>
									Sent emails to chairs of HTML WG and
									XML CG.
								</p></li><li><a href="http://www.w3.org/2004/05/14-tag-summary#xlinkScope-23">completed on 14 May 2004</a></li></ul></div></div></div><div class="issue"><h3><a id="contentTypeOverride-24" name="contentTypeOverride-24">contentTypeOverride-24</a>: 
				Can a specification include rules for overriding HTTP
				content type parameters?
			 [<a href="issues.html#contentTypeOverride-24">link to this issue</a>]</h3><p>
							For me this questions depends on whether the
							document type is a human-readable hypertext
							document, when generic hypertext xml tools
							would benefit from knowing what is a link,
							and whether significance of the URI in
							question is a hypertext link or something
							different.
						</p><p>
							Maybe a compromise is to only allow the link
							to specify the content-type when the server
							is FTP (or something else with no
							content-type control) or the HTTP server
							returns text/plain or octet-steam, which
							seem to be used for "don't know"
							types.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><ul><li><a href="http://www.w3.org/TR/speech-grammar/#S2.2.2">
						Speech Recognition Grammar Specification Version
						1.0
					</a></li><li>HTTP/1.1</li></ul></dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2003/02/06-tag-summary#contentTypeOverride-24">6 Feb 2003</a>, <a href="http://www.w3.org/2003/03/24-tag-summary#contentTypeOverride-24">24 Mar 2003</a>, <a href="http://www.w3.org/2003/04/07-tag-summary#contentTypeOverride-24">7 Apr 2003</a>, <a href="http://www.w3.org/2003/05/05-tag-summary#contentTypeOverride-24">5 May 2003</a>, <a href="http://www.w3.org/2003/05/12-tag-summary#contentTypeOverride-24">12 May 2003</a>, <a href="http://www.w3.org/2003/06/16-tag-summary#contentTypeOverride-24">16 Jun 2003</a>, <a href="http://www.w3.org/2003/06/23-tag-summary#contentTypeOverride-24">23 Jun 2003</a>, <a href="http://www.w3.org/2003/06/30-tag-summary#contentTypeOverride-24">30 Jun 2003</a>, <a href="http://www.w3.org/2003/07/07-tag-summary#contentTypeOverride-24">7 Jul 2003</a>, <a href="http://www.w3.org/2003/10/06-tag-summary#contentTypeOverride-24">8 Oct 2003</a>, <a href="http://www.w3.org/2003/12/04-tag-summary">5 Dec 2002</a>, <a href="http://www.w3.org/2003/12/15-tag-summary#contentTypeOverride-24">15 Dec 2003</a>, <a href="http://www.w3.org/2004/01/26-tag-summary#contentTypeOverride-24">26 Jan 2004</a></dd><dt>Categories</dt><dd></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jun/0117">raised</a> on 14 Jun 2002 by 
						Tim Berners-Lee
					, on behalf of <a href="http://www.w3.org/2001/tag/">
						TAG
					</a></dt><dd></dd><dt><a href="http://www.w3.org/2002/07/22-tag-summary">accepted</a> on 22 Jul 2002</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Feb/0085">
										Link metadata cannot override
										server media type
									</a>
									from DanC
								</li><li><a href="http://lists.w3.org/Archives/Member/tag/2003Feb/0066">
										Email from Chris
									</a>
									to TAG about SMIL 2.0, and
									<a href="http://lists.w3.org/Archives/Member/tag/2003Feb/0076">
										rationale
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Apr/0030">
										Email from Chris Lilley
									</a>
									on MSDN documentation on
									MIME-sniffing in Internet Explorer
									(FindMimeFromData method)
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Apr/0034">
										Email from Chris on MIME types
										and encoding
									</a></li><li><a href="http://lists.w3.org/Archives/Member/tag/2003May/0012">
										Scott McGlashan email to TAG
									</a>
									with links to Voice WG points.
								</li><li><a href="http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23421">
										Bug filed by Martin Duerst
									</a>
									regarding default charset setting in
									Apache conf file
								</li><li>
									Draft Finding
									<a href="http://www.w3.org/2001/tag/doc/mime-respect">
										"Client Handling of
										Authoritative metadata"
									</a></li><li>
									Approved Finding
									<a href="http://www.w3.org/2001/tag/doc/mime-respect-20060412">
										Authoritative Metadata
									</a></li></ul></dd><dt><a href="http://www.w3.org/2003/12/04-tag-summary">agreed</a> on 4 Dec 2003</dt><dd><p>
							The
							<a href="/2001/tag/2003/webarch-20031203/">
								3 Dec 2003 Editor's Draft of the
								Architecture Document
							</a>
							accurately represents the TAG's position on
							the authoritative nature of server messages.
						</p><h5>Acknowledgment cycle</h5><dl><dt><a href="http://www.w3.org/2003/12/04-tag-summary">announced by group  on 4 Dec 2002</a></dt><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Aug/0320"> agreement by reviewer  on 4 Dec 2003</a></dt><dd><p>
									Acknowledged by TBL by virtue of WG
									agreement
								</p></dd></dl></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						IJ
					</h5><ul><li><a href="http://www.w3.org/2003/10/06-tag-summary">accepted on 8 Oct 2003</a><br /><p>
									Produce a new draft of the finding
									that takes into account comments
									from reviewers on MIME finding.
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Dec/0174">proposal on 10 Dec 2003</a><br /><p><a href="http://www.w3.org/2001/tag/doc/mime-respect-20031210">
										10 Dec 2003 Draft
									</a>
									,
									<a href="http://www.w3.org/2001/tag/doc/mime-respect-20040127">
										27 Jan 2004 Draft
									</a>
									. See
									<a href="http://lists.w3.org/Archives/Public/www-tag/2004Feb/0007">
										comments from Stuart
									</a>
									. See
									<a href="http://www.w3.org/2001/tag/doc/mime-respect-20040218">
										18 Feb 2004 Draft
									</a></p></li><li><a href="http://www.w3.org/2004/02/23-tag-summary#contentTypeOverride-24">completed on 23 Feb 2004</a><br /><p>
									TAG accepted 18 Feb 2004 draft. IJ
									will publish as accepted finding.
								</p></li></ul></div></div></div><div class="issue"><h3><a id="deepLinking-25" name="deepLinking-25">deepLinking-25</a>: 
				What to say in defense of principle that deep linking is
				not an illegal act?
			 [<a href="issues.html#deepLinking-25">link to this issue</a>]</h3><p>Strawman from Tim Bray:</p><p>
							The architecture of the World Wide Web does
							not support the notion of a "home
							page" or a "gateway page",
							and any effort in law to pretend otherwise
							is therefore bad policy. The publication of
							a Uniform Resource Identifier is, in the
							architecture of the Web, a statement that a
							resource is available for retrieval. The
							technical protocols which are used for Web
							interaction provide a variety of means for
							site operators to control access, including
							password protection and the requirement that
							users take a particular route to a page. It
							would be appropriate to bring the law to
							bear against those who violate these
							protocols. It is not appropriate to use it
							in the case where information consumers are
							using the Web according to its published
							rules of operation.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><a href="http://slashdot.org/articles/02/07/05/1431249.shtml?tid=95">
						Slashdot article on court ruling in Denmark
					</a></dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2002/08/30-tag-summary#deepLinking-25">30 Aug 2002</a>, <a href="http://lists.w3.org/Archives/Public/www-tag/2002Sep/0085">9 Sep 2002</a>, <a href="http://www.w3.org/2003/02/06-tag-summary#deepLinking-25">7 Feb 2003</a>, <a href="http://www.w3.org/2003/02/17-tag-summary#deepLinking-25">17 Feb 2003</a>, <a href="http://www.w3.org/2003/09/15-tag-summary">15 Sep 2003</a>, <a href="http://www.w3.org/2003/10/06-tag-summary#deepLinking-25">8 Oct 2003</a>, <a href="http://www.w3.org/2003/11/03-tag-summary">3 Nov 2003</a>, <a href="http://www.w3.org/2003/11/15-tag-summary">15 Nov 2003</a></dd><dt>Categories</dt><dd></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Jul/0118">raised</a> on 5 Jul 2002 by 
						Tim Bray
					, on behalf of <a href="http://www.w3.org/2001/tag/">
						TAG
					</a></dt><dd></dd><dt><a href="http://www.w3.org/2002/07/22-tag-summary">accepted</a> on 22 Jul 2002</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Sep/0181">
										Summary from Henrik Frystyk
										Nielsen
									</a>
									of Danish Court case (TAG only)
								</li></ul></dd><dt><a href="http://www.w3.org/2003/02/06-tag-summary#deepLinking-25">agreed</a> on 7 Feb 2003</dt><dd><p>
							Accepted
							<a href="http://www.textuality.com/tag/DeepLinking.html">
								Draft finding from TB
							</a></p><h5>Acknowledgment cycle</h5><dl><dt><a href="http://www.w3.org/2003/02/06-tag-summary#deepLinking-25">announced by group  on 7 Feb 2003</a></dt><dt><a href="http://www.w3.org/2003/02/06-tag-summary#deepLinking-25"> agreement by reviewer  on 7 Feb 2003</a></dt><dd><p>
									Acknowledged by TB by virtue of WG
									agreement
								</p></dd></dl></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						IJ
					</h5><ul><li><a href="http://www.w3.org/2003/09/15-tag-summary#deepLinking-25">accepted on 15 Sep 2003</a><br /><p>
									Take back to Comm Team publicity of
									this finding.
								</p></li><li><a href="http://www.w3.org/2003/10/06-tag-summary#findings">dependent on 8 Oct 2003</a><br />on 
              <a href="http://www.w3.org/Press/">
								W3C Communications Team
							</a></li><li><a href="http://www.w3.org/2003/11/03-tag-summary">completed on 15 Nov 2003</a><br /><p>
									TAG discussed this issue with Janet
									Daly at ftf meeting in Japan.
								</p></li></ul></div></div></div><div class="issue"><h3><a id="contentPresentation-26" name="contentPresentation-26">contentPresentation-26</a>: 
				Separation of semantic and presentational markup, to the
				extent possible, is architecturally sound.
			 [<a href="issues.html#contentPresentation-26">link to this issue</a>]</h3><p><a href="http://lists.w3.org/Archives/Public/www-tag/2002Aug/0191">
								Strawman from Tim Bray
							</a>
							:
						</p><p>
							I would however, support an assertion in the
							architecture document that important
							information SHOULD be stored and
							(optionally) delivered with markup that is
							as semantically rich as achievable, and that
							separation of semantic and presentational
							markup, to the extent possible, is
							architecturally sound.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><ul><li>XML</li><li>CSS</li><li>XSL-FO</li><li><a href="/TR/xag/">
						XML Accessibility Guidelines
					</a></li></ul></dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2002/09/24-tag-summary#contentPresentation-26">24 Sep 2002</a>, <a href="http://www.w3.org/2003/02/06-tag-summary#contentPresentation-26">6 Feb 2003</a>, <a href="http://www.w3.org/2003/07/21-tag-summary#contentPresentation-26">21 Jul 2003</a>, <a href="http://www.w3.org/2003/10/06-tag-summary#contentPresentation-26">8 Oct 2003</a>, <a href="http://www.w3.org/2004/05/14-tag-summary#contentPresentation-26">14 May 2004</a>, <a href="http://www.w3.org/2005/02/07-tagmem-minutes#item07">7 Feb 2005</a>, <a href="http://www.w3.org/2005/09/21-tagmem-minutes#item04">21 Sep 2005</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Aug/0162">raised</a> on 15 Aug 2002 by 
						Dan Connolly
					, on behalf of <a href="http://www.w3.org/2001/tag/">
						TAG
					</a></dt><dd></dd><dt><a href="http://www.w3.org/2002/08/26-tag-summary#contentPresentation-26">accepted</a> on 26 Aug 2002</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Aug/0286">
										Email from Kynn Bartlett
									</a>
									on separation of content from
									presentation.
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Aug/0164">
										Email from Sean Palmer
									</a>
									about WAI PF work in this area.
								</li><li>
									Draft finding from CL:
									<a href="http://www.w3.org/2001/tag/doc/contentPresentation-26">
										Separation of semantic and
										presentational markup, to the
										extent possible, is
										architecturally sound
									</a>
									(
									<a href="http://lists.w3.org/Archives/Member/tag/2005Oct/0003">
										Historical document
									</a>
									)
								</li></ul></dd><dt><a href="http://www.w3.org/2005/09/21-tagmem-minutes#item04">agreed</a> on 21 Sep 2005</dt><dd><p>
							Section
							<a href="http://www.w3.org/TR/2004/REC-webarch-20041215/#pci">
								4.3 of Web Architecture
							</a>
							closes the issue.
						</p><h5>Acknowledgment cycle</h5><dl><dt>Not started</dt></dl></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						CL
					</h5><ul><li><a href="http://www.w3.org/2003/10/06-tag-summary">accepted on 8 Oct 2003</a><br /><p>
									Talk with others about aspects of
									this finding and revise it.
								</p></li><li><a href="http://www.w3.org/2004/05/14-tag-summary#contentPresentation-26">completed on 14 May 2004</a></li></ul></div></div></div><div class="issue"><h3><a id="IRIEverywhere-27" name="IRIEverywhere-27">IRIEverywhere-27</a>: 
				Should W3C specifications start promoting IRIs?
			 [<a href="issues.html#IRIEverywhere-27">link to this issue</a>]</h3><p>
							The XML Core WG would like TAG input on
							whether the desirability of adopting IRIs
							into the web infrastructure early outweighs
							the anticipated disruption of legacy
							systems.
						</p><p>
							The XML Core WG would also like TAG input on
							the wisdom of early adoption given the
							<a href="http://www.w3.org/International/iri-edit/">
								"Internet Draft" status of the
								IRI draft
							</a>
							. So far adoption has relied on "copy
							and paste", but there is potential for
							these definitions to get out of sync.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><ul><li>XML</li><li>XML 1.1</li><li><a href="http://www.w3.org/International/iri-edit/">
						[Internet Draft] IRI draft
					</a></li></ul></dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2002/08/26-tag-summary#contentPresentation-26">28 Oct 2002</a>, <a href="http://www.w3.org/2002/11/11-tag-summary#IRIEverywhere-27">11 Nov 2002</a>, <a href="http://www.w3.org/2002/11/18-tag-summary#IRIEverywhere-27">18 Nov 2002</a>, <a href="http://www.w3.org/2003/01/27-tag-summary#IRIEverywhere-27">27 Jan 2003</a>, <a href="http://www.w3.org/2003/02/06-tag-summary#IRIEverywhere-27">6 Feb 2003</a>, <a href="http://www.w3.org/2003/03/31-tag-summary#IRIEverywhere-27">31 Mar 2003</a>, <a href="http://www.w3.org/2003/04/07-tag-summary#IRIEverywhere-27">7 Apr 2003</a>, <a href="http://www.w3.org/2003/04/14-tag-summary#IRIEverywhere-27">14 Apr 2003</a>, <a href="http://lists.w3.org/Archives/Public/www-tag/2003Apr/0121">28 Apr 2003</a>, <a href="http://www.w3.org/2004/05/14-tag-summary#IRIEverywhere-27">14 May 2004</a>, <a href="http://www.w3.org/2005/09/21-tagmem-minutes#item05">21 Sep 2005</a>, <a href="http://www.w3.org/2001/tag/2005/12/13-tagmem-minutes#item05">13 Dec 2005</a>, <a href="http://www.w3.org/2001/tag/2007/01/23-tagmem-minutes#item06">23 Jan 2007</a>, <a href="http://www.w3.org/2001/tag/2007/02/12-tagmem-minutes#item04">12 Feb 2007</a>, <a href="http://www.w3.org/2001/tag/2007/03/26-minutes#item05">26 Mar 2007</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Oct/0186">raised</a> on 9 Oct 2002 by 
						Jonathan Marsh
					, on behalf of <a href="http://www.w3.org/XML/Core/">
						XML Core WG
					</a></dt><dd></dd><dt><a href="http://www.w3.org/2002/08/26-tag-summary#contentPresentation-26">accepted</a> on 28 Oct 2002</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="#URIEquivalence-15">
										URIEquivalence-15
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Mar/0063">
										Email from Larry Masinter
									</a>
									about
									<a href="http://lists.w3.org/Archives/Public/uri/2003Mar/0043">
										URI BOF minutes from IETF56
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Apr/0122">
										Summary email from Tim Bray
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Apr/0139">
										Comments from Ray Whitmer
									</a>
									about IRIs in the DOM (see same
									email
									<a href="http://lists.w3.org/Archives/Public/www-tag/2003Apr/0140">
										with inclusion
									</a>
									. See
									<a href="http://www.w3.org/2003/05/WD-DOM-Level-3-Core-20030507/core#domURIs">
										1.3.2 DOM URIs
									</a>
									in 7 May 2003 DOM 3 Core draft
								</li><li><a href="http://www.ietf.org/rfc/rfc3490.txt">
										RFC3490: Internationalizing
										Domain Names in Applications
										(IDNA)
									</a></li><li>
									See TB's
									<a href="http://lists.w3.org/Archives/Public/www-tag/2003Apr/0090">
										proposed step forward on IRI 27.
									</a></li><li><a href="http://www.ietf.org/rfc/rfc3987.txt">
										RFC 3987
									</a>
									is a Proposed Standard
								</li></ul></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						CL
					</h5><ul><li><a href="http://www.w3.org/2003/04/07-tag-summary">accepted on 7 Apr 2003</a><br /><p>
									Revise position statement on use of
									IRIs.
								</p></li><li><a href="http://www.w3.org/2004/03/22-tag-summary#charmodReview-17">completed on 22 Mar 2004</a><br /><p>
									This action has been completed and
									replaced by virtue of the
									<a href="#20040322-cl1">
										action assigned to CL on 22
										March
									</a>
									.
								</p></li></ul></div><div class="details-action decided"><h5>
						TBL
					</h5><ul><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Apr/0121">accepted on 28 Apr 2003</a><br /><p>
									Explain how existing specifications
									that handle IRIs are inconsistent.
									<a href="http://lists.w3.org/Archives/Member/tag/2003Apr/0074">
										TBL draft
									</a>
									not yet available on www-tag.
								</p></li><li><a href="http://www.w3.org/2001/tag/group/track/actions/24">dropped on 24 Aug 2007</a><br /><p>
									Merged into tracker
									<a href="http://www.w3.org/2001/tag/group/track/actions/24">
										ACTION-24
									</a></p></li></ul></div><div class="details-action decided"><h5>
						HT
					</h5><ul><li><a href="http://www.w3.org/2005/09/21-tagmem-minutes#action02">accepted on 21 Sep 2005</a><br /><p>
									with Norm report the
									Namespaces/URI/IRI discussion to XML
									Core.
								</p></li><li><a href="http://www.w3.org/2001/tag/2007/01/23-tagmem-minutes#action05">completed on 23 Jan 2007</a></li></ul></div><div class="details-action decided"><h5>
						DC
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2007/01/23-tagmem-minutes#action06">accepted on 23 Jan 2007</a><br /><p>
									DanC to ask TimBL whether XQuery and
									XML Namespaces 1.1 address
									IRIEverywhere to his satisfaction,
									noting
									<a href="http://www.w3.org/2003/04/iri">
										Mappings and identity in URIs
										and IRIs
									</a>
									.
								</p></li><li><a href="http://www.w3.org/2001/tag/2007/03/26-minutes#ActionSummary">completed on 26 Mar 2007</a></li></ul></div><div class="details-action"><h5>
						TBL
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2007/03/26-minutes#ActionSummary">accepted on 26 Mar 2007</a><br /><p>
									TimBL to clarify
									<a href="http://www.w3.org/2003/04/iri">
										http://www.w3.org/2003/04/iri
									</a>
									, perhaps by using N3
								</p></li><li><a href="http://www.w3.org/2001/tag/group/track/actions/24">proposal on 24 Aug 2007</a><br /><p>
									Tracking transferred to tracker
									<a href="http://www.w3.org/2001/tag/group/track/actions/24">
										ACTION-24
									</a></p></li></ul></div></div></div><div class="issue"><h3><a id="fragmentInXML-28" name="fragmentInXML-28">fragmentInXML-28</a>: Use of fragment identifiers in XML [<a href="issues.html#fragmentInXML-28">link to this issue</a>]</h3><p>
							Do fragment identifiers refer to a
							syntactice element (at least for XML
							content), or can they refer to abstractions?
						</p><p>
							Example from
							<a href="http://www.w3.org/TR/2001/REC-SVG-20010904/linking#FragmentIdentifiersSVG">
								17.2.2 SVG fragment identifiers
							</a>
							:
						</p><p>
							MyDrawing.svg#svgView(viewBox(0,200,1000,1000))
						</p><p>
							The SVG spec states "This form of
							addressing specifies the desired view of the
							document (e.g., the region of the document
							to view, the initial zoom level) completely
							within the SVG fragment specification."
						</p><p>From Dan Connolly:</p><p>
							Do you consider the quoted paragraph above
							in error?
						</p><p>
							Or do you disagree with my interpretation of
							it, i.e. that
							MyDrawing.svg#svgView(viewBox(0,200,1000,1000))
							identifes a view of the drawing, and not any
							particular XML element (nor other syntactic
							structure) in the document.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references">XML</dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2004/05/14-tag-summary#fragmentInXML-28">12 May 2004</a>, <a href="http://www.w3.org/2005/02/07-tagmem-minutes#item09">7 Feb 2005</a>, <a href="http://www.w3.org/2005/05/10-tagmem-minutes#item08">10 May 2005</a>, <a href="http://www.w3.org/2005/05/31-tagmem-minutes#item04">31 May 2005</a>, <a href="http://www.w3.org/2005/11/01-tagmem-minutes#item12">1 Nov 2005</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Oct/0325">raised</a> on 31 Oct 2002 by 
						Dan Connolly
					, on behalf of <a href="http://www.w3.org/2001/tag/">
						TAG
					</a></dt><dd></dd><dt><a href="http://www.w3.org/2002/11/04-tag-summary#frags">accepted</a> on 4 Nov 2002</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="#httpRange-14">
										httpRange-14
									</a>
									,
									<a href="#rdfmsQnameUriMapping-6">
										rdfmsQnameUriMapping-6
									</a>
									(since the WSDL WG is asking us how
									they should do nearly exactly what
									we want the XML Schema WG to do e.g.
									provide URIs for "schema"
									components)
								</li><li><a href="http://www.imc.org/ietf-xml-use/xml-guidelines-07.txt">
										Guidelines for the Use of XML
										within IETF Protocols
									</a>
									. See also
									<a href="http://www.imc.org/ietf-xml-use/index.html">
										ietf-xml-use mailing list
									</a>
									in case the document disappears.
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Dec/0268">
										SemWeb use case
									</a>
									from Sandro Hawke.
								</li><li>
									Per
									<a href="http://www.w3.org/2003/01/13-tag-summary">
										13 Jan 2003 teleconf
									</a>
									, note that the TAG considers
									<a href="http://lists.w3.org/Archives/Public/www-tag/2002Dec/0237">
										XInclude issues raised by M.
										Murata
									</a>
									to be related to this issue. Which
									media type should be used for
									interpreting fragment identifiers?
									Section 2.4 in the architecture
									document says the media type of the
									retrieval result, but Sections 4.2
									and 4.3 in the XInclude CR says
									text/xml or text/plain.
								</li><li>
									See
									<a href="http://lists.w3.org/Archives/Public/www-tag/2003Feb/0207">
										email from Paul Cotton
									</a>
									about WSDL component designators.
								</li><li>
									Also related: Content negotiation?
									Opacity of URIs?
								</li></ul></dd><dt><a href="http://www.w3.org/2004/05/14-tag-summary#fragmentInXML-28">agreed</a> on 12 May 2004</dt><dd><ul><li>
									In general, the fragment part of a
									URI may be used to refer to
									abstractions as well as syntactic
									fragments of a representation; the
									media type identifies a
									specification, which explains the
									semantics.
								</li></ul><h5>Acknowledgment cycle</h5><dl><dt>Not started</dt></dl></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						CL
					</h5><ul><li><a href="http://www.w3.org/2004/05/14-tag-summary#fragmentInXML-28">accepted on 12 May 2004</a><br /><p>Summarize resolution.</p></li><li><a href="">dropped on 21 May 2007</a><br /><p>Well past sell by date</p></li></ul></div><div class="details-action decided"><h5>
						HT
					</h5><ul><li><a href="http://www.w3.org/2005/02/07-tagmem-minutes#action12">accepted on 7 Feb 2005</a><br /><p>
									monitor and bring back up when time
									is appropriate
								</p></li><li><a href="">dropped on 24 Aug 2007</a><br /><p>dropped by chair</p></li></ul></div></div></div><div class="issue"><h3><a id="xmlProfiles-29" name="xmlProfiles-29">xmlProfiles-29</a>: 
				When, whither and how to profile W3C specifications in
				the XML Family
			 [<a href="issues.html#xmlProfiles-29">link to this issue</a>]</h3><p>
							When, whither and how to profile W3C
							specifications in the XML Family
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references">XML family of specifications</dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2002/12/02-tag-summary#xml-subset">2 Dec 2002</a>, <a href="http://www.w3.org/2002/12/09-tag-summary#xmlProfiles-29">9 Dec 2002</a>, <a href="http://www.w3.org/2002/12/16-tag-summary#xmlProfiles-29">16 Dec 2002</a>, <a href="http://www.w3.org/2003/01/06-tag-summary#xmlProfiles-29">6 Jan 2003</a>, <a href="http://www.w3.org/2003/01/13-tag-summary#xmlProfiles-29">13 Jan 2003</a>, <a href="http://www.w3.org/2003/01/27-tag-summary#xmlProfiles-29">27 Jan 2003</a>, <a href="http://www.w3.org/2003/02/06-tag-summary#xmlProfiles-29">6 Feb 2003</a>, <a href="http://www.w3.org/2003/09/15-tag-summary#contentTypeOverride-29">15 Sep 2003</a>, <a href="http://www.w3.org/2003/12/04-tag-summary">5 Dec 2002</a>, <a href="http://www.w3.org/2005/07/05-tagmem-minutes#item02">5 Jul 2005</a></dd><dt>Categories</dt><dd></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Nov/0156">raised</a> on 25 Nov 2002 by 
						Paul Grosso
					</dt><dd></dd><dt><a href="http://www.w3.org/2002/12/02-tag-summary#xml-subset">accepted</a> on 2 Dec 2002</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="http://www.w3.org/TR/2002/WD-soap12-part0-20020626">
										SOAP 1.2, 26 Jun 2002 draft
									</a>
									makes use of an XML format that does
									not permit any internal subset,
									despite the fact that XML 1.0 does
									not define such a profile/subset of
									XML. See
									<a href="http://lists.w3.org/Archives/Public/www-tag/2002Dec/0119">
										rationale from David Fallside
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Jan/0025">
										Options for dealing with ID
									</a>
									, from Chris Lilley
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Jan/0212">
										Web services arch WG position
									</a>
									from Mike Champion
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Feb/0222">
										Glenn Adams email
									</a>
									on the existence of a number of
									standards in the television domain
									that: (1) disallow internal
									declaration subsets; (2) require
									standalone="no"; (3)
									require a document type declaration,
									with a specifically enumerated set
									of public FPIs to be supported;
								</li><li><a href="http://www.jabber.org/ietf/draft-ietf-xmpp-core-06.html">
										Extensible Messaging and
										Presence Protocol (XMPP) Core,
										draft-ietf-xmpp-core-06
									</a>
									.
									<a href="http://lists.w3.org/Archives/Public/www-tag/2003Mar/0068">
										From Chris Lilley
									</a>
									: "XMPP dissalows PIs,
									commnents, and both internal and
									external TD subsets."
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Apr/0019">
										Henry Thompson proposal
									</a>
									for "minimal" conformance
									class.
								</li></ul></dd><dt><a href="http://www.w3.org/2003/01/27-tag-summary#xmlProfiles-29">agreed</a> on 27 Jan 2003</dt><dd><p><a href="http://lists.w3.org/Archives/Public/www-tag/2003Jan/0418">
								TAG recommendation for work on subset of
								XML 1.1
							</a>
							. See
							<a href="http://lists.w3.org/Archives/Member/w3c-ac-members/2003AprJun/0041">
								followup to AC (Member-only)
							</a>
							. Work is being carried out in the XML Core
							WG.
						</p><h5>Acknowledgment cycle</h5><dl><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2003Jan/0418">announced by group  on 30 Jan 2003</a></dt></dl></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						VQ
					</h5><ul><li><a href="http://www.w3.org/2005/07/05-tagmem-minutes#action02">accepted on 5 Jul 2005</a><br /><p>
									check status of XMLProfiles-29 with
									Paul Grosso
								</p></li><li><a href="">dropped on 8 Jun 2007</a><br /><p>
									Dropped by chair (overtaken bye
									events)
								</p></li></ul></div></div></div><div class="issue"><h3><a id="binaryXML-30" name="binaryXML-30">binaryXML-30</a>: Standardize a "binary XML" format? [<a href="issues.html#binaryXML-30">link to this issue</a>]</h3><p>
							Given that binary infosets (currently,
							<a href="http://expway.tv/graph/Bin-XMLTechnical%20White%20Paper.pdf">
								binary PSVIs
							</a>
							) is what I work on daily and that I am
							currently investigating ways in which they
							could fit naturally into the web
							(content-coding registration for instance),
							I would be very interested in knowing what
							-- if anything at this point -- the TAG
							thinks of them and of how they could best
							fit in.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references">XML</dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2002/12/02-tag-summary#binary-xml">2 Dec 2002</a>, <a href="http://www.w3.org/2003/01/13-tag-summary#binaryXML-30">13 Jan 2003</a>, <a href="http://www.w3.org/2003/01/27-tag-summary#binaryXML-30">27 Jan 2003</a>, <a href="http://www.w3.org/2003/02/06-tag-summary#binaryXML-30">6 Feb 2003</a>, <a href="http://www.w3.org/2003/02/17-tag-summary#binaryXML-30">17 Feb 2003</a>, <a href="http://www.w3.org/2004/05/14-tag-summary#binaryXML-30">12 May 2004</a>, <a href="http://www.w3.org/2005/02/07-tagmem-minutes#item10">7 Feb 2005</a>, <a href="http://www.w3.org/2001/tag/2005/02/28-minutes#item09">28 Feb 2005</a>, <a href="http://lists.w3.org/Archives/Public/www-tag/2005Mar/att-0056/March152005#item06">15 Mar 2005</a>, <a href="http://www.w3.org/2005/04/05-tagmem-minutes#item06">5 Apr 2005</a>, <a href="http://lists.w3.org/Archives/Public/www-tag/2005Apr/att-0068/April122005">12 Apr 2005</a>, <a href="http://www.w3.org/2001/tag/2005/04/26-minutes#item08">26 Apr 2005</a>, <a href="http://lists.w3.org/Archives/Public/www-tag/2005May/att-0033/03-tagmem-irc#item01">3 May 2005</a>, <a href="http://www.w3.org/2005/05/10-tagmem-minutes#item05">10 May 2005</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Oct/0187">raised</a> on 9 Oct 2002 by 
						Robin Berjon
					</dt><dd></dd><dt><a href="http://www.w3.org/2002/12/02-tag-summary#binary-xml">accepted</a> on 2 Dec 2002</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li>
									See
									<a href="http://lists.w3.org/Archives/Public/www-tag/2002Dec/0022">
										explanation scenario from DC
									</a>
									; a typical conversation about
									binary XML.
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2002Dec">
										Rationale from Robin Berjon
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003May/0014">
										XML binary compression progress:
										X3D, XFSP project
									</a>
									from Don Brutzman.
								</li><li>
									OGC is another customer for binary
									XML.
								</li><li><a href="http://www.w3.org/2003/08/binary-interchange-workshop/">
										Binary XML Workshop Minutes
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Feb/0224">
										Summary from Chris
									</a>
									.
								</li><li><a href="http://www.w3.org/TR/xbc-use-cases/">
										XML Binary Characterization Use
										Cases
									</a>
									.
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2005May/0044">
										TAG opinion on XML Binary Format
									</a>
									, 24 May 2005.
								</li></ul></dd><dt><a href="http://www.w3.org/2004/05/14-tag-summary#binaryXML-30">deferred</a> on 12 May 2004</dt><dd><p>
							W3C has chartered the
							<a href="http://www.w3.org/XML/Binary/">
								XML Binary Characterization Working
								Group
							</a>
							to address this issue. The TAG anticipates
							reviewing the WG's deliverables in this
							area.
						</p></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						TB
					</h5><ul><li><a href="http://www.w3.org/2003/02/17-tag-summary">accepted on 17 Feb 2003</a><br /><p>
									Write to www-tag with his thoughts
									on adding to survey.
								</p></li><li><a href="http://www.w3.org/2003/12/04-tag-summary">dropped on 4 Dec 2003</a><br /><p>
									TB said he had nothing to add to the
									survey.
								</p></li></ul></div></div></div><div class="issue"><h3><a id="metadataInURI-31" name="metadataInURI-31">metadataInURI-31</a>: 
				Should metadata (e.g., versioning information) be
				encoded in URIs?
			 [<a href="issues.html#metadataInURI-31">link to this issue</a>]</h3><p>
							The TAG's preliminary response is that URIs
							should not include metadata. The TAG
							accepted this issue to provide guidance on
							addressing the issues raised.
						</p><p>From Ossi:</p><p>
							To outline the following text, I'm actually
							suggesting (asking comments for) two rather
							practical things:
						</p><ol><li>
									There should be a uniform way to
									declare version history of web
									resources (recommended by W3C)?, and
									more importantly
								</li><li>
									There should be a "clean",
									uniform way to refer to (and thus
									access) the metadata of web
									resources?
								</li></ol><dl><dt class="references">Request
	      concerning</dt><dd class="references"><ul><li>Architecture Document</li><li>URI</li></ul></dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2002/12/02-tag-summary#metadata-uri">2 Dec 2002</a>, <a href="http://www.w3.org/2003/02/06-tag-summary#metadataInURI-31">6 Feb 2003</a>, <a href="http://www.w3.org/2003/07/07-tag-summary">7 Jul 2003</a>, <a href="http://www.w3.org/2003/07/21-tag-summary#metadataInURI-31">21 Jul 2003</a>, <a href="http://www.w3.org/2003/10/06-tag-summary#metadataInURI-31">8 Oct 2003</a>, <a href="http://www.w3.org/2004/05/14-tag-summary#metadataInURI-31">14 May 2004</a>, <a href="http://www.w3.org/2005/02/07-tagmem-minutes#item11">7 Feb 2005</a>, <a href="http://www.w3.org/2005/09/21-tagmem-minutes#item06">21 Sep 2005</a>, <a href="http://www.w3.org/2001/tag/2005/12/13-tagmem-minutes#item06">13 Dec 2005</a>, <a href="http://www.w3.org/2006/03/21-tagmem-minutes#item04">21 Mar 2006</a>, <a href="http://www.w3.org/2006/05/02-tagmem-minutes#item03">2 May 2006</a>, <a href="http://www.w3.org/2006/05/16-tagmem-minutes#item02">16 May 2006</a>, <a href="http://www.w3.org/2006/05/30-tagmem-minutes#action05">30 May 2006</a>, <a href="http://www.w3.org/2001/tag/2006/06/14-minutes#item01">14 Jun 2006</a>, <a href="http://www.w3.org/2006/07/25-tagmem-minutes#item05">25 Jul 2006</a>, <a href="http://www.w3.org/2001/tag/2006/08/15-minutes#item04">8 Aug 2006</a>, <a href="http://www.w3.org/2001/tag/2006/09/19-minutes#item04">19 Sep 2006</a>, <a href="http://www.w3.org/2001/tag/2006/10/04-tagmem-minutes#item02">4 Oct 2006</a>, <a href="http://www.w3.org/2001/tag/2006/11/07-minutes#item04">7 Nov 2006</a>, <a href="http://www.w3.org/2001/tag/2006/11/14-tagmem-minutes#item02">14 Nov 2006</a>, <a href="http://www.w3.org/2001/tag/2006/12/11-minutes#item06">11 Dec 2006</a>, <a href="http://www.w3.org/2001/tag/2007/01/02-minutes#item02">2 Jan 2007</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2002Nov/0149">raised</a> on 25 Nov 2002 by 
						Ossi Nykänen
					</dt><dd></dd><dt><a href="http://www.w3.org/2002/12/02-tag-summary#metadata-uri">accepted</a> on 2 Dec 2002</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li>
									See
									<a href="http://www.w3.org/TR/webarch/#pr-use-uris">
										Arch Doc
									</a></li><li>
									See
									<a href="http://lists.w3.org/Archives/Public/www-tag/2003Apr/0151">
										Tim Bray mail on Apple Music
										Store
									</a>
									.
								</li><li><a href="http://www.w3.org/2001/tag/doc/metaDataInURI-31">
										Fnding
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Aug/0079">
										Email from Tony Hammond
									</a>
									on
									<a href="http://library.caltech.edu/openurl/PubComDocs/StdDocs/Part1-PC-20030513.pdf">
										The OpenURL Framework
									</a>
									(PDF)
								</li><li>
									On the topic of URI fragility, see
									the section entitled
									<a href="http://www.w3.org/DesignIssues/NameMyth#Why">
										Why Names Change
									</a>
									in TBL's
									<a href="http://www.w3.org/DesignIssues/NameMyth">
										The Myth of Names and Addresses
									</a></li><li><a href="http://www.w3.org/mid/000d01c385e1$b36ae9d0$6401a8c0@MasinterT40">
										Comments from Larry Masinter
									</a>
									on draft finding
								</li><li>
									See comments from
									<a href="http://lists.w3.org/Archives/Public/www-tag/2003Aug/0048">
										Mark Nottingham
									</a>
									and
									<a href="http://lists.w3.org/Archives/Public/www-tag/2003Aug/0055">
										followup from Noah M.
									</a></li><li><a href="http://www.w3.org/2001/tag/2006/02/metadatainURI31Roadmap">
										Guide to Feedback and
										Outstanding Issues
									</a>
									by Noah M.
								</li></ul></dd><dt><a href="http://www.w3.org/2001/tag/2006/12/11-minutes#item06">agreed</a> on 11 Dec 2006</dt><dd><p>
							See
							<a href="http://www.w3.org/2001/tag/2006/12/11-minutes#item06">
								resolution
							</a>
							.
						</p><h5>Acknowledgment cycle</h5><dl><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2007Jan/0004">announced by group  on 3 Jan 2007</a></dt></dl></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>SW</h5><ul><li><a href="http://www.w3.org/2003/07/21-tag-summary">accepted on 21 Jul 2003</a><br /><p>
									Produce a revision of this finding
									based on Vancouver ftf meeting
									discussion.
								</p></li><li><a href="http://www.w3.org/2001/tag/2006/01/24-minutes#item04">dropped on 24 Jan 2006</a></li></ul></div><div class="details-action decided"><h5>
						DO
					</h5><ul><li><a href="http://www.w3.org/2003/07/21-tag-summary">accepted on 21 Jul 2003</a><br /><p>
									Send rationale about why WSDL WG
									wants to peek inside the URI.
								</p></li><li><a href="http://www.w3.org/2001/tag/2006/06/14-minutes#item04">dropped on 14 Jun 2006</a></li></ul></div><div class="details-action decided"><h5>
						RF
					</h5><ul><li><a href="http://www.w3.org/2005/09/21-tagmem-minutes#action03">accepted on 21 Sep 2005</a><br /><p>
									Make progress on metadataInURI-31
									with Noah
								</p></li><li><a href="http://www.w3.org/2001/tag/2006/01/24-minutes#item04">dropped on 24 Jan 2006</a></li></ul></div><div class="details-action decided"><h5>ER</h5><ul><li><a href="http://www.w3.org/2006/03/21-tagmem-minutes#action02">accepted on 21 Mar 2006</a><br /><p>
									ER and TVR to review draft finding
									on Authoritative Metadata
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2006Mar/0052">completed on 27 Mar 2006</a></li></ul></div><div class="details-action decided"><h5>
						NM
					</h5><ul><li><a href="http://www.w3.org/2006/05/30-tagmem-minutes#action06">accepted on 30 May 2006</a><br /><p>
									produce new version of
									<a href="http://www.w3.org/2001/tag/doc/metaDataInURI-31">
										The use of Metadata in URIs
									</a></p></li><li><a href="http://www.w3.org/2001/tag/2006/06/14-minutes#item04">completed on 14 Jun 2006</a></li></ul></div><div class="details-action decided"><h5>
						NM
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/06/14-minutes#action01">accepted on 14 Jun 2006</a><br /><p>
									Noah to produce final draft of
									metadataInURI-31 by 11 August 2006
								</p></li><li><a href="http://www.w3.org/2001/tag/doc/alternatives-discovery-20060915">completed on 15 Sep 2006</a></li></ul></div><div class="details-action decided"><h5>
						NM
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/09/19-minutes#action02">accepted on 19 Sep 2006</a><br /><p>
									Add security section on risks of
									serving executables as .jpeg to
									metadataInURI draft. Confirmed on
									<a href="http://www.w3.org/2001/tag/2006/10/04-tagmem-minutes#action01">
										4 Oct 2006
									</a>
									.
								</p></li><li><a href="http://www.w3.org/2001/tag/2006/11/07-minutes#item04">completed on 7 Nov 2006</a></li></ul></div><div class="details-action decided"><h5>ER</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/10/04-tagmem-minutes#action02">accepted on 4 Oct 2006</a><br /><p>
									Review security section on risks of
									serving executables as .jpeg to
									metadataInURI draft.
								</p></li><li><a href="http://www.w3.org/2001/tag/2006/11/14-tagmem-minutes#action03">completed on 14 Nov 2006</a></li></ul></div><div class="details-action decided"><h5>
						DC
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/10/04-tagmem-minutes#action03">accepted on 4 Oct 2006</a><br /><p>
									Review security section on risks of
									serving executables as .jpeg to
									metadataInURI draft. Confirmed on
									<a href="http://www.w3.org/2001/tag/2006/11/14-tagmem-minutes#action04">
										14 Nov 2006
									</a>
									.
								</p></li><li><a href="http://www.w3.org/2001/tag/2006/12/11-minutes#item06">completed on 11 Dec 2006</a></li></ul></div><div class="details-action decided"><h5>
						NM
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/11/14-tagmem-minutes#action01">accepted on 14 Nov 2006</a><br /><p>
									Rework metadataInURI 1st example to
									be more explicit as per Tim's
									suggestion, and update GPN per Dan's
									suggestion.
								</p></li><li><a href="http://www.w3.org/2001/tag/2006/12/11-minutes#item06">completed on 11 Dec 2006</a></li></ul></div><div class="details-action decided"><h5>
						HT
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/11/14-tagmem-minutes#action02">accepted on 14 Nov 2006</a><br /><p>
									Seek a copy of the official court
									record of the UK case on ../../ etc.
								</p></li><li><a href="http://www.w3.org/2001/tag/2006/12/11-minutes#item06">completed on 11 Dec 2006</a></li></ul></div><div class="details-action decided"><h5>
						NM
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/12/11-minutes#action04">accepted on 11 Dec 2006</a><br /><p>
									Noah to update status to make
									metadataInURI an approved finding.
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2007Jan/0004">completed on 3 Jan 2007</a></li></ul></div><div class="details-action decided"><h5>
						VQ
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/12/11-minutes#action05">accepted on 11 Dec 2006</a><br /><p>
									announce metadataInURI draft once
									it's in final form.
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2007Jan/0004">completed on 3 Jan 2007</a></li></ul></div></div></div><div class="issue"><h3><a id="xmlIDSemantics-32" name="xmlIDSemantics-32">xmlIDSemantics-32</a>: 
				How should the problem of identifying ID semantics in
				XML languages be addressed in the absence of a DTD?
			 [<a href="issues.html#xmlIDSemantics-32">link to this issue</a>]</h3><p>
							I would like to raise a new issue to the
							TAG. The issue is how to determine ID
							attributes in any new work on XML, such as a
							new profile or subset as dealt within issue
							<a href="#xmlProfiles-29">
								xmlProfiles-29
							</a>
							. I understand that this issue will be
							normatively referred to in any
							communications on issue #29.
						</p><p>
							Chris Lilley has started an
							<a href="http://lists.w3.org/Archives/Public/www-tag/2003Jan/0025">
								excellent discussion
							</a>
							on the various options for ID attributes, so
							I won't duplicate that work. A number of
							responders have said they are quite
							supportive of providing a definition of IDs
							as part of any new work on XMLProfiles, such
							as the Web Services Architecture Working
							Group. There is also some pushback, so it
							seems worthy to have a continued discussion,
							and the TAG should attempt to quickly reach
							consensus.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references">XML 1.1</dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2003/01/27-tag-summary#xmlProfiles-29">27 Jan 2003</a>, <a href="http://www.w3.org/2003/02/06-tag-summary#xmlIDSemantics-32">6 Feb 2003</a>, <a href="http://www.w3.org/2003/04/14-tag-summary#xmlIDSemantics-32">14 Apr 2003</a>, <a href="http://www.w3.org/2003/06/30-tag-summary#xmlIdSemantics-32">30 Jun 2003</a>, <a href="http://www.w3.org/2003/10/06-tag-summary#xmlIdSemantics-32">8 Oct 2003</a>, <a href="http://www.w3.org/2004/01/12-tag-summary#xmlIDSemantics-32">12 Jan 2004</a>, <a href="http://www.w3.org/2005/02/07-tagmem-minutes#item12">7 Feb 2004</a>, <a href="http://www.w3.org/2004/05/14-tag-summary#findings">12 May 2004</a>, <a href="http://www.w3.org/2001/tag/2005/04/19-minutes#item05">19 Apr 2005</a>, <a href="http://www.w3.org/2005/09/21-tagmem-minutes#item07">21 Sep 2005</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2003Jan/0416">raised</a> on 30 Jan 2003 by 
						David Orchard
					, on behalf of <a href="http://www.w3.org/2001/tag/">
						TAG
					</a></dt><dd></dd><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2003Jan/0416">accepted</a> on 30 Jan 2003</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li>
									Offshoot of
									<a href="#xmlProfiles-29">
										xmlProfiles-29
									</a>
									. This issue was raised on request
									from the TAG at their
									<a href="http://www.w3.org/2003/01/27-tag-summary#xmlProfiles-29">
										27 Jan 2003
									</a>
									teleconference.
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Jan/0025">
										Options for dealing with IDs
									</a>
									from Chris Lilley
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Jan/0212">
										Web Services Architecture WG
										position on XML profiling/subset
										ting
									</a>
									from Mike Champion
								</li><li><a href="http://www.w3.org/2001/tag/doc/xmlIDsemantics-32">
										Finding
									</a>
									from Chris Lilley: Approved by TAG
									<a href="http://www.w3.org/2004/05/14-tag-summary#findings">
										12 May 2004
									</a></li><li><a href="http://www.w3.org/TR/xml-id-req">
										xml:id Requirements
									</a>
									from the
									<a href="http://www.w3.org/XML/Core/">
										W3C XML Core Working Group
									</a></li><li>
									See
									<a href="http://lists.w3.org/Archives/Public/www-tag/2003Nov/0027">
										Comments from Henry Thompson
									</a>
									on the XPointer Framework definition
									of Shorthand Pointer.
								</li></ul></dd><dt><a href="http://www.w3.org/2004/05/14-tag-summary#findings">deferred</a> on 12 May 2004</dt><dd><p>
							At their 12 May 2004 ftf meeting, the TAG
							accepted the proposed finding "How should
							the problem of identifying ID semantics in
							XML languages be addressed in the absence of
							a DTD?". The issue is deferred while the XML
							Core WG continues work on this issue.
						</p></dd><dt><a href="http://www.w3.org/2005/09/21-tagmem-minutes#item07">agreed</a> on 21 Sep 2005</dt><dd><p><a href="http://www.w3.org/TR/xml-id/">
								xml:id Version 1.0
							</a>
							is a Recommendation
						</p><h5>Acknowledgment cycle</h5><dl><dt>Not started</dt></dl></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>NW</h5><ul><li><a href="http://www.w3.org/2003/05/05-tag-summary">accepted on 5 May 2003</a><br /><p>
									Point Core WG to CL finding once
									made public.
								</p></li><li><a href="http://www.w3.org/2003/06/30-tag-summary">dependent on 30 Jun 2003</a><br />on 
              <a href="http://www.w3.org/XML/Core/">
								XML Core WG progress
							</a></li><li><a href="http://lists.w3.org/Archives/Member/tag/2004Jan/0037">proposal on 12 Jan 2004</a><br /><p>
									NW: I can find no record of having
									completed this action, but I believe
									that I did and cite[2] the pointer
									from the XML Core WG home page as
									evidence that I did.
								</p></li><li><a href="http://www.w3.org/2004/01/12-tag-summary#xmlIDSemantics-32">completed on 12 Jan 2004</a></li></ul></div></div></div><div class="issue"><h3><a id="mixedUIXMLNamespace-33" name="mixedUIXMLNamespace-33">mixedUIXMLNamespace-33</a>: 
				Composability for user interface-oriented XML namespaces
			 [<a href="issues.html#mixedUIXMLNamespace-33">link to this issue</a>]</h3><p>
							Raised by the TAG as an offshoot of
							<a href="#mixedNamespaceMeaning-13">
								mixedNamespaceMeaning-13
							</a>
							.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><ul><li>XHTML</li><li>MathML</li><li>SVG</li><li>XForms</li><li>SMIL</li><li>
					other user interface-oriented applications
				</li></ul></dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2003/02/06-tag-summary#xmlIDSemantics-32">6 Feb 2003</a>, <a href="http://www.w3.org/2004/03/02-tag-summary#mixed-markup">2 Mar 2004</a>, <a href="http://www.w3.org/2005/02/07-tagmem-minutes#item13">7 Feb 2005</a>, <a href="http://www.w3.org/2005/09/21-tagmem-minutes#item08">21 Sep 2005</a>, <a href="http://www.w3.org/2005/11/01-tagmem-minutes#item07">1 Nov 2005</a>, <a href="http://lists.w3.org/Archives/Member/tag/2006Jan/att-0003/Jan102005#item04">10 Jan 2006</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://www.w3.org/2003/02/06-tag-summary#mixedNamespaceMeaning-13">raised</a> on 6 Feb 2003 by TAG, on behalf of <a href="http://www.w3.org/2001/tag/">
						TAG
					</a></dt><dd></dd><dt><a href="http://www.w3.org/2003/02/06-tag-summary#mixedNamespaceMeaning-13">accepted</a> on 6 Feb 2003</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li>
									Offshoot of
									<a href="#mixedNamespaceMeaning-13">
										mixedNamespaceMeaning-13
									</a></li><li><a href="http://www.w3.org/TR/XHTMLplusMathMLplusSVG/">
										An XHTML + MathML + SVG Profile
									</a></li><li><a href="http://www.w3.org/2004/04/webapps-cdf-ws/summary">
										W3C Workshop on Web Applications
										and Compound Documents
									</a></li><li><a href="http://www.w3.org/2004/CDF/">
										W3C Compound Document Formats
										Working Group
									</a></li></ul></dd><dt><a href="http://www.w3.org/2005/11/01-tagmem-minutes#item07">deferred</a> on 1 Nov 2005</dt><dd><p>
							Pend this issue until significant progress
							is made by the
							<a href="http://www.w3.org/2004/CDF/">
								W3C Compound Document Formats Working
								Group
							</a>
							in a public working draft.
						</p></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						NM
					</h5><ul><li><a href="http://www.w3.org/2005/09/21-tagmem-minutes#action05">accepted on 21 Sep 2003</a><br /><p>
									Review CDF requirements and report
									back.
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2005Oct/0040">completed on 18 Oct 2005</a></li></ul></div><div class="details-action decided"><h5>
						TBL
					</h5><ul><li><a href="/2005/09/21-tagmem-minutes#action04">accepted on 21 Sep 2005</a><br /><p>
									review CDF requirements and report
									back
								</p></li><li><a href="http://lists.w3.org/Archives/Member/tag/2006Jan/att-0003/Jan102005#item04">dropped on 10 Jan 2006</a></li></ul></div></div></div><div class="issue"><h3><a id="xmlFunctions-34" name="xmlFunctions-34">xmlFunctions-34</a>: 
				XML Transformation and composability (e.g., XSLT,
				XInclude, Encryption)
			 [<a href="issues.html#xmlFunctions-34">link to this issue</a>]</h3><p>
							Raised by the TAG as an offshoot of
							<a href="#mixedNamespaceMeaning-13">
								mixedNamespaceMeaning-13
							</a>
							.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><ul><li>XSLT</li><li>XInclude</li><li>Encryption</li><li>
					other specifications that involve transformations of
					XML content
				</li></ul></dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2003/02/06-tag-summary#xmlIDSemantics-32">6 Feb 2003</a>, <a href="http://www.w3.org/2005/09/21-tagmem-minutes#item09">21 Sep 2005</a>, <a href="http://www.w3.org/2006/01/31-tagmem-minutes#item04">31 Jan 2006</a>, <a href="http://www.w3.org/2001/tag/2006/02/07-tagmem-minutes#item05">7 Feb 2006</a>, <a href="http://www.w3.org/2006/04/18-tagmem-minutes#item05">18 Apr 2006</a>, <a href="http://www.w3.org/2001/tag/2006/04/25-tagmem-minutes#item02">25 Apr 2006</a>, <a href="http://www.w3.org/2001/tag/2006/12/11-minutes#item07">11 Dec 2006</a>, <a href="http://www.w3.org/2007/01/30-tagmem-minutes">30 Jan 2007</a>, <a href="http://www.w3.org/2001/tag/2007/06/11-minutes#action06">11 Jun 2007</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://www.w3.org/2003/02/06-tag-summary#mixedNamespaceMeaning-13">raised</a> on 6 Feb 2003 by TAG, on behalf of <a href="http://www.w3.org/2001/tag/">
						TAG
					</a></dt><dd></dd><dt><a href="http://www.w3.org/2003/02/06-tag-summary#mixedNamespaceMeaning-13">accepted</a> on 6 Feb 2003</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li>
									Offshoot of
									<a href="#mixedNamespaceMeaning-13">
										mixedNamespaceMeaning-13
									</a></li><li><a href="http://www.w3.org/DesignIssues/XML">
										The Interpretation of XML
										documents
									</a>
									from TBL.
								</li><li><a href="http://www.w3.org/2001/tag/doc/elabInfoset">
										The elaborated infoset: A
										proposal
									</a></li></ul></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>NW</h5><ul><li><a href="http://www.w3.org/2001/tag/2005/12/06-Morning-minutes#action03">accepted on 6 Dec 2005</a><br /><p>
									with help from HT, produce a draft
									finding on XML functions in January
								</p></li><li><a href="http://www.w3.org/2001/tag/2006/12/11-minutes#action06">dropped on 11 Dec 2006</a></li></ul></div><div class="details-action"><h5>
						TVR
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/02/27-tagmem-minutes-2.htm#action01">accepted on 27 Feb 2006</a><br /><p>
									summarize history of
									DTD/namespace/mimetype version
									practice, including XHTML, SOAP, and
									XSLT. Confirmed on
									<a href="http://www.w3.org/2001/tag/2006/12/11-minutes#action07">
										11 Dec 2006
									</a>
									.
								</p></li><li><a href="http://www.w3.org/2001/tag/group/track/actions/25">proposal on 24 Aug 2007</a><br /><p>
									Tracking transferred to tracker
									<a href="http://www.w3.org/2001/tag/group/track/actions/25">
										ACTION-25
									</a></p></li></ul></div><div class="details-action decided"><h5>
						TBL
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/02/27-tagmem-minutes-2.htm#action02">accepted on 27 Feb 2006</a><br /><p>
									write a short email to make his
									point so we capture this for future
								</p></li><li><a href="http://www.w3.org/2001/tag/2006/12/11-minutes#action06">completed on 11 Dec 2006</a></li></ul></div><div class="details-action decided"><h5>
						HT
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/12/11-minutes#action06">accepted on 11 Dec 2006</a><br /><p>
									create a draft finding on
									xmlFunctions-34 to the working group
									by the 8th of Feb. 2007.
								</p></li><li><a href="http://www.w3.org/2007/01/30-tagmem-minutes">completed on 30 Jan 2007</a><br /><p>
									See
									<a href="http://www.w3.org/2001/tag/doc/elabInfoset">
										The elaborated infoset: A
										proposal
									</a></p></li></ul></div><div class="details-action decided"><h5>NW</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/12/11-minutes#action07">accepted on 11 Dec 2006</a><br /><p>review Henry's draft.</p></li><li><a href="http://www.w3.org/2001/tag/2007/07/16-minutes#item03">dropped on 16 Jul 2007</a><br /><p>Withdrawn pending a new draft.</p></li></ul></div><div class="details-action decided"><h5>
						TBL
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/12/11-minutes#action07">accepted on 11 Dec 2006</a><br /><p>review Henry's draft.</p></li><li><a href="http://www.w3.org/2001/tag/2007/07/16-minutes#item03">dropped on 16 Jul 2007</a><br /><p>Withdrawn pending a new draft.</p></li></ul></div><div class="details-action decided"><h5>SW</h5><ul><li><a href="http://www.w3.org/2001/tag/2007/03/26-minutes#ActionSummary">accepted on 26 Mar 2007</a><br /><p>
									SKW to send comments on
									urnsAndRegistries draft
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2007Mar/0036">completed on 28 Mar 2007</a><br /><p>Email review sent</p></li></ul></div><div class="details-action"><h5>
						HT
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2007/06/11-minutes#action06">accepted on 11 Jun 2007</a><br /><p>
									Henry to prepare new draft of
									xmlFunctions-34 by mid-July
								</p></li><li><a href="http://www.w3.org/2001/tag/group/track/actions/26">proposal on 24 Aug 2007</a><br /><p>
									Tracking transferred to tracker
									<a href="http://www.w3.org/2001/tag/group/track/actions/26">
										ACTION-26
									</a></p></li></ul></div></div></div><div class="issue"><h3><a id="RDFinXHTML-35" name="RDFinXHTML-35">RDFinXHTML-35</a>: 
				Syntax and semantics for embedding RDF in XHTML
			 [<a href="issues.html#RDFinXHTML-35">link to this issue</a>]</h3><p>
							Raised by the TAG as an offshoot of
							<a href="#mixedNamespaceMeaning-13">
								mixedNamespaceMeaning-13
							</a>
							.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><ul><li>RDF</li><li>XHTML</li></ul></dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2003/02/06-tag-summary#xmlIDSemantics-32">6 Feb 2003</a>, <a href="http://www.w3.org/2004/05/14-tag-summary#RDFinXHTML-35">14 May 2004</a>, <a href="http://www.w3.org/2005/02/22-tagmem-minutes#item10">22 Feb 2005</a>, <a href="http://www.w3.org/2001/tag/2005/02/28-minutes#item10">28 Feb 2005</a>, <a href="http://www.w3.org/2001/tag/2005/12/13-tagmem-minutes#item07">13 Dec 2005</a>, <a href="http://www.w3.org/2001/tag/2006/06/14-minutes#item07">14 Jun 2006</a>, <a href="http://www.w3.org/2001/tag/2006/12/13-morning-minutes#item04">13 Dec 2006</a>, <a href="http://www.w3.org/2001/tag/2007/02/12-tagmem-minutes#item02">12 Feb 2007</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://www.w3.org/2003/02/06-tag-summary#mixedNamespaceMeaning-13">raised</a> on 6 Feb 2003 by TAG, on behalf of <a href="http://www.w3.org/2001/tag/">
						TAG
					</a></dt><dd></dd><dt><a href="http://www.w3.org/2003/02/06-tag-summary#mixedNamespaceMeaning-13">accepted</a> on 6 Feb 2003</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li>
									Offshoot of
									<a href="#mixedNamespaceMeaning-13">
										mixedNamespaceMeaning-13
									</a></li><li><a href="#namespaceDocument-8">
										namespaceDocument-8
									</a></li><li><a href="http://www.w3.org/TR/2003/WD-rdf-syntax-grammar-20030123/#section-rdf-in-HTML">
										Using RDF/XML with HTML and
										XHTML
									</a></li><li><a href="http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2003Feb/0103">
										Some discussion about approaches
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Mar/0019">
										"Crisp" statement of
										the problem
									</a>
									from Dan Connolly
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Mar/0038">
										Email from M. Ishikawa
									</a>
									on using modular namespaces (MNS)
								</li><li><a href="http://www.w3.org/2002/04/htmlrdf">
										RDF in XHTML
									</a>
									summary by TBL.
								</li><li><a href="http://www.w3.org/TR/grddl/">
										GRDDL: Gleaning Resource
										Descriptions from Dialects of
										Languages
									</a>
									by Dan Connolly and Dominique
									Hazael-Massieux.
								</li></ul></dd><dt><a href="http://www.w3.org/2001/tag/2006/12/13-morning-minutes#item04">deferred</a> on 13 Dec 2006</dt><dd><p>
							The TAG decided to defer this issue pending
							work by the GRDDL WG and/or the
							RDFa/HTML/SemWeb-deployment WGs.
						</p></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						TBL
					</h5><ul><li><a href="http://www.w3.org/2003/02/06-tag-summary">accepted on 6 Feb 2003</a><br /><p>
									State the issue with a reference to
									XML Core work. See
									<a href="http://lists.w3.org/Archives/Public/www-tag/2003Feb/0309">
										email from TimBL
									</a>
									capturing some of the issues.
								</p></li><li><a href="http://www.w3.org/2004/05/14-tag-summary#RDFinXHTML-35">dropped on 14 May 2004</a></li></ul></div><div class="details-action"><h5>
						DC
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2007/02/12-tagmem-minutes#action01">accepted on 12 Feb 2007</a><br /><p>
									DanC to ask Mimasa and Mark Birbeck
									about feasability of using
									substitution groups in XHTML
									modularization, cc
									public-xml-versioning
								</p></li><li><a href="http://www.w3.org/2001/tag/group/track/actions/27">proposal on 24 Aug 2007</a><br /><p>
									Tracking transferred to tracker
									<a href="http://www.w3.org/2001/tag/group/track/actions/27">
										ACTION-27
									</a>
									and moved under
									<a href="http://www.w3.org/2001/tag/group/track/issues/41">
										XMLVersioning-41
									</a></p></li></ul></div></div></div><div class="issue"><h3><a id="siteData-36" name="siteData-36">siteData-36</a>: 
				Web site metadata improving on robots.txt, w3c/p3p and
				favicon etc.
			 [<a href="issues.html#siteData-36">link to this issue</a>]</h3><p>
							The architecture of the web is that the
							space of identifiers on an http web site is
							owned by the owner of the domain name. The
							owner, "publisher", is free to
							allocate identifiers and define how they are
							served.
						</p><p>
							Any variation from this breaks the web. The
							problem is that there are some conventions
							for the identifies on websites, that
						</p><ul><li>
									/robots.txt is a file controlling
									robot access
								</li><li>
									/w3c/p3p is where you put a privacy
									policy
								</li><li>
									/favico is an icon representative of
									the web site
								</li></ul><p>
							and who knows what others. There is of
							course no list available of the assumptions
							different groups and manufacturers have
							used.
						</p><p>
							More in the
							<a href="http://lists.w3.org/Archives/Public/www-tag/2003Feb/0093">
								original message from TBL
							</a>
							.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references">URI space</dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2003/02/24-tag-summary">24 Feb 2003</a>, <a href="http://www.w3.org/2003/10/06-tag-summary#siteData-36">8 Oct 2003</a>, <a href="http://www.w3.org/2004/01/05-tag-summary#siteData-36">5 Jan 2004</a>, <a href="http://www.w3.org/2004/01/12-tag-summary#siteData-36">12 Jan 2004</a>, <a href="http://www.w3.org/2005/02/22-tagmem-minutes#item11">22 Feb 2005</a>, <a href="http://www.w3.org/2001/tag/2005/12/13-tagmem-minutes#item08">13 Dec 2005</a>, <a href="http://www.w3.org/2006/05/02-tagmem-minutes#item02">2 May 2006</a>, <a href="http://www.w3.org/2007/01/09-tagmem-minutes#item05">9 Jan 2007</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2003Feb/0093">raised</a> on 10 Feb 2003 by 
						Tim Berners-Lee
					, on behalf of <a href="http://www.w3.org/2001/tag/">
						TAG
					</a></dt><dd></dd><dt><a href="http://www.w3.org/2003/02/24-tag-summary">accepted</a> on 24 Feb 2003</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li>
									Note:
									<a href="http://www.tbray.org/ongoing/When/200x/2004/01/08/WebSite36">
										Defining a Web Site
									</a>
									.
								</li><li><a href="http://www.sitemaps.org/">
										Sitemap protocol
									</a>
									.
								</li></ul></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						TB
					</h5><ul><li><a href="http://www.w3.org/2003/10/06-tag-summary">accepted on 8 Oct 2003</a> (due 2004-01-08)
            <br /><p>
									Refine strawman based on 8 Oct 2003
									meeting and draft new finding.
									Reconfirmed at
									<a href="http://www.w3.org/2004/01/05-tag-summary#siteData-36">
										5 Jan 2004 teleconf with due
										date 7 Jan.
									</a>
									. Agreed to add use cases to finding
									at
									<a href="http://www.w3.org/2004/01/12-tag-summary#siteData-36">
										12 Jan 2004 teleconf
									</a>
									.
								</p></li><li><a href="http://www.tbray.org/ongoing/When/200x/2004/01/08/WebSite36">proposal on 12 Jan 2003</a><br /><p>Proposal</p></li><li><a href="http://www.w3.org/2006/05/02-tagmem-minutes#item02">dropped on 2 May 2006</a></li></ul></div><div class="details-action decided"><h5>
						DC
					</h5><ul><li><a href="http://www.w3.org/2004/01/12-tag-summary#siteData-36">accepted on 12 Jan 2003</a><br /><p>
									Propose an example of a site
									description.
								</p></li><li><a href="http://www.w3.org/2007/01/09-tagmem-minutes#item05">dropped on 9 Jan 2007</a></li></ul></div></div></div><div class="issue"><h3><a id="abstractComponentRefs-37" name="abstractComponentRefs-37">abstractComponentRefs-37</a>: 
				Definition of abstract components with namespace names
				and frag ids
			 [<a href="issues.html#abstractComponentRefs-37">link to this issue</a>]</h3><p>
							Is it wise to use fragment IDs for
							identifying abstract components within a
							namespace, even though it is the most
							natural and convenient mechanism? Is there
							another mechanism that would be preferable?
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><ul><li><a href="http://www.w3.org/TR/REC-xml-names">
						Namespaces in XML
					</a></li><li><a href="http://www.w3.org/TR/wsdl12">
						WSDL
					</a></li></ul></dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2003/03/24-tag-summary#abstractComponentRefs-37">24 Mar 2003</a>, <a href="http://www.w3.org/2003/04/14-tag-summary#abstractComponentRefs-37">14 Apr 2003</a>, <a href="http://www.w3.org/2003/05/05-tag-summary#abstractComponentRefs-37">5 May 2003</a>, <a href="http://www.w3.org/2003/06/23-tag-summary#abstractComponentRefs-37">23 Jun 2003</a>, <a href="http://www.w3.org/2003/10/06-tag-summary#abstractComponentRefs-37">8 Oct 2003</a>, <a href="http://www.w3.org/2003/10/20-tag-summary#abstractComponentRefs-37">20 Oct 2003</a>, <a href="http://www.w3.org/2004/03/02-tag-summary#abstractComponentRefs-37">2 Mar 2004</a>, <a href="http://www.w3.org/2005/02/22-tagmem-minutes#item12">22 Feb 2005</a>, <a href="http://lists.w3.org/Archives/Public/www-tag/2005May/att-0033/03-tagmem-irc#item02">3 May 2005</a>, <a href="http://www.w3.org/2001/tag/2005/06/14-16-minutes#item031">16 Jun 2005</a>, <a href="http://www.w3.org/2005/09/21-tagmem-minutes#item14">21 Sep 2005</a>, <a href="http://www.w3.org/2005/10/25-tagmem-minutes#item03">25 Oct 2005</a>, <a href="http://www.w3.org/2005/11/01-tagmem-minutes#item13">1 Nov 2005</a>, <a href="http://www.w3.org/2006/05/16-tagmem-minutes#item04">16 May 2006</a>, <a href="http://www.w3.org/2001/tag/2006/06/14-minutes#item05">14 Jun 2006</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2003Feb/0042">raised</a> on 3 Feb 2003 by 
						Jonathan Marsh
					, on behalf of <a href="http://www.w3.org/2002/ws/desc/">
						WSD WG
					</a></dt><dd></dd><dt><a href="http://www.w3.org/2003/03/24-tag-summary#abstractComponentRefs-37">accepted</a> on 24 Mar 2003</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="#rdfmsQnameUriMapping-6">
										rdfmsQnameUriMapping-6
									</a>
									,
									<a href="#namespaceDocument-8">
										namespaceDocument-8
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Mar/0064">
										Email from Tim Bray
									</a>
									about relation to RDDL.
								</li><li><a href="">
										Email from Paul Cotton
									</a>
									about Schema WG response to the WSD
									WG questions about Schema Component
									Designators
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Apr/0081">
										Email from Noah Mendelsohn
									</a>
									about distinction between schema
									components and schema documents.
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Apr/0115">
										Email from Larry Masinter
									</a>
									on relation to WebDAV to providing
									access to metadata.
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Jun/0054">
										Summary of options from David
										Orchard
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Jun/0054">
										Draft summary
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2004Jan/0007">
										Comments from MSM on behalf of
										Schema WG
									</a></li><li><a href="http://www.w3.org/TR/xmlschema-ref/">
										"XML Schema: Component
										Designators"
									</a>
									specification published by the W3C
									XML Schema WG.
								</li><li>
									Draft finding
									<a href="http://www.w3.org/2001/tag/doc/abstractComponentRefs">
										Abstract Component References
									</a></li></ul></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						DO
					</h5><ul><li><a href="http://www.w3.org/2003/10/06-tag-summary">accepted on 8 Oct 2003</a><br /><p>
									Write up resolution from 8 Oct 2003
									meeting and include in revised
									finding on this topic.
								</p></li><li><a href="http://www.w3.org/2003/10/20-tag-summary#abstractComponentRefs-37">completed on 20 Oct 2003</a></li></ul></div><div class="details-action decided"><h5>
						DO
					</h5><ul><li><a href="http://www.w3.org/2003/10/20-tag-summary#abstractComponentRefs-37">accepted on 20 Oct 2003</a><br /><p>
									Revise draft finding based on
									comments at 20 Oct teleconf.
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Nov/0008">proposal on 3 Nov 2003</a><br /><p>
									IJ published this from material sent
									by DO to IJ privately on 30 Oct
									2003.
								</p></li><li><a href="http://www.w3.org/2001/tag/2006/06/14-minutes#item05">completed on 14 Jun 2006</a></li></ul></div><div class="details-action decided"><h5>
						DC
					</h5><ul><li><a href="http://www.w3.org/2005/09/21-tagmem-minutes#action09">accepted on 21 Sep 2005</a><br /><p>
									seek clarification about
									http://example.org/TicketAgent.wsdl20#wsdl.interface(TicketAgent)
								</p></li><li><a href="http://lists.w3.org/Archives/Public/public-ws-desc-comments/2005Sep/0056">completed on 27 Sep 2005</a></li></ul></div></div></div><div class="issue"><h3><a id="putMediaType-38" name="putMediaType-38">putMediaType-38</a>: 
				Relation of HTTP PUT to GET, and whether client headers
				to server are authoritative
			 [<a href="issues.html#putMediaType-38">link to this issue</a>]</h3><p>Some scenarios that this issue concerns:</p><ul><li>
									Client PUTs representation to server
									without content type information;
									what is proper server behavior?
								</li><li>
									Client PUTs representation to server
									with content type information, but
									server ignores. Is this
									architecturally incorrect?
								</li><li>
									Client PUTs representation to server
									with detectably inconsistent content
									type information. What is proper
									server behavior (e.g., signal error
									and not silently ignoring)?
								</li></ul><dl><dt class="references">Request
	      concerning</dt><dd class="references">Authority of client headers</dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2003/06/16-tag-summary#contentTypeOverride-24">16 Jun 2003</a>, <a href="http://www.w3.org/2005/02/22-tagmem-minutes#item13">22 Feb 2005</a>, <a href="http://www.w3.org/2001/tag/2005/04/26-minutes#item09">26 Apr 2005</a>, <a href="http://lists.w3.org/Archives/Public/www-tag/2005May/att-0033/03-tagmem-irc">3 May 2005</a>, <a href="http://www.w3.org/2005/09/21-tagmem-minutes#item10">21 Sep 2005</a>, <a href="http://www.w3.org/2001/tag/2005/12/06-Morning-minutes#item03">6 Dec 2005</a>, <a href="http://www.w3.org/2006/03/28-tagmem-minutes#item03">28 Mar 2006</a>, <a href="http://www.w3.org/2001/tag/2006/04/11-tagmem-minutes#item08">11 Apr 2006</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2003May/0024">raised</a> on 6 May 2003 by 
						Julian Reschke
					</dt><dd></dd><dt><a href="http://www.w3.org/2003/06/16-tag-summary#contentTypeOverride-24">accepted</a> on 16 Jun 2003</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="#contentTypeOverride-24">
										contentTypeOverride-24
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003May/0047">
										"PUT semantics and MIME
										header handling"
									</a></li><li><a href="http://www.w3.org/2001/tag/doc/mime-respect-20040225">
										First version of approved
										finding "Authoritative Metadata"
									</a>
									(25 Feb. 2004)
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2005May/0001">
										Reopening discussion
									</a></li><li>
									New version of approved finding
									<a href="http://www.w3.org/2001/tag/doc/mime-respect-20060412">
										Authoritative Metadata
									</a>
									(12 April 2006)
								</li></ul></dd><dt><a href="http://www.w3.org/2006/04/18-tagmem-minutes#item07">agreed</a> on 18 Apr 2006</dt><dd><p>
							Approved TAG finding
							<a href="http://www.w3.org/2001/tag/doc/mime-respect-20060412">
								Authoritative Metadata
							</a>
							.
						</p><h5>Acknowledgment cycle</h5><dl><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2006Apr/0022">announced by group  on 19 Apr 2006</a></dt></dl></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						RF
					</h5><ul><li><a href="http://www.w3.org/2005/02/22-tagmem-minutes#action07">accepted on 22 Feb 2005</a><br /><p>
									prepare putMediaType-38 for further
									discussion
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2005May/0001">completed on 3 May 2005</a><br /><p>reopening discussion.</p></li></ul></div><div class="details-action decided"><h5>
						RF
					</h5><ul><li><a href="http://www.w3.org/2005/09/21-tagmem-minutes#action06">accepted on 21 Sep 2005</a><br /><p>
									update
									<a href="http://www.w3.org/2001/tag/doc/mime-respect">
										Authoritative Metadata
									</a>
									finding to include resolution of
									putMediaType-38. Reconfirmed
									<a href="http://www.w3.org/2001/tag/2005/11/08-tagmem-minutes#action06">
										8 Nov 2005
									</a>
									.
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2006Mar/0009">completed on 7 Mar 2006</a><br /><p><a href="http://www.w3.org/2001/tag/doc/mime-respect-20060307">
										Authoritative Metadata finding
									</a>
									updated.
								</p></li></ul></div><div class="details-action decided"><h5>
						RF
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2005/12/06-Morning-minutes#action04">accepted on 6 Dec 2005</a><br /><p>
									produce a new version of the finding
									<a href="http://www.w3.org/2001/tag/doc/mime-respect">
										Authoritative Metadata
									</a>
									by the end of the year
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2006Mar/0009">completed on 7 Mar 2006</a><br /><p><a href="http://www.w3.org/2001/tag/doc/mime-respect-20060307">
										Authoritative Metadata finding
									</a>
									updated.
								</p></li></ul></div><div class="details-action decided"><h5>ER</h5><ul><li><a href="http://www.w3.org/2006/03/28-tagmem-minutes#action03">accepted on 28 Mar 2006</a><br /><p>
									Propose disclaimer and discuss with
									Roy.
								</p></li><li><a href="http://www.w3.org/2001/tag/2006/04/11-tagmem-minutes#item08">dropped on 11 Apr 2006</a></li></ul></div></div></div><div class="issue"><h3><a id="rdfURIMeaning-39" name="rdfURIMeaning-39">rdfURIMeaning-39</a>: Meaning of URIs in RDF documents [<a href="issues.html#rdfURIMeaning-39">link to this issue</a>]</h3><p>TBL: "The community needs:</p><ol><li>
									A concise statement of the above
									architectural elements from
									different specs in one place,
									written in terms which the ontology
									community will understand, with
									pointers to the relevant
									specifications.
								</li><li>
									Some outline guidance on specific
									questions brought up in email
									questions.
								</li></ol><p>This includes:</p><ul><li>
									Is a given inference engine expected
									to take into account a given
									document under given circumstances?
								</li><li>
									how does one avoid having to commit
									to things one does not trust?
								</li></ul><p>
							There may be some need to clarify frequent
							misunderstandings by making some things
							clear."
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><ul><li>URI</li><li>RDF</li><li>OWL</li><li>HTTP</li></ul></dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2003/08/18-tagmem-irc">18 Aug 2003</a>, <a href="http://www.w3.org/2003/09/15-tag-summary#rdfURIMeaning-39">15 Sep 2003</a>, <a href="http://www.w3.org/2005/02/22-tagmem-minutes#item14">22 Feb 2003</a>, <a href="http://www.w3.org/2005/09/21-tagmem-minutes#item11">21 Sep 2005</a>, <a href="http://www.w3.org/2001/tag/2005/12/13-tagmem-minutes#item09">13 Dec 2005</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2003Jul/0022">raised</a> on 13 Jul 2003 by 
						Tim Berners-Lee
					, on behalf of <a href="http://www.w3.org/2001/sw/CG/">
						Semantic Web CG
					</a></dt><dd></dd><dt><a href="http://www.w3.org/2003/08/18-tagmem-irc">accepted</a> on 18 Aug 2003</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li>
									Some
									<a href="http://lists.w3.org/Archives/Public/www-tag/2003Jul/0127">
										background summarized by DanC
									</a></li><li>
									Mailing list for discussions on this
									issue: public-sw-meaning (
									<a href="http://lists.w3.org/Archives/Public/public-sw-meaning/">
										archive
									</a>
									)
								</li></ul></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						DC
					</h5><ul><li><a href="http://www.w3.org/2005/09/21-tagmem-minutes#action07">accepted on 21 Sep 2005</a><br /><p>
									Notify the SW CG that we talked
									about rdfURIMeaning-39 and didn't
									decide to do anything now
								</p></li><li><a href="http://www.w3.org/2002/02/mid/1127840294.6446.156.camel@dirk;list=w3c-semweb-cg">completed on 27 Sep 2005</a><br /><p>
									Mail sent to Semantic Web
									Coordination Group.
								</p></li></ul></div></div></div><div class="issue"><h3><a id="URIGoodPractice-40" name="URIGoodPractice-40">URIGoodPractice-40</a>: What are good practices for URI construction? [<a href="issues.html#URIGoodPractice-40">link to this issue</a>]</h3><p>Some issues:</p><ul><li>Fragment identifier syntax</li><li>Related issue: URI Squatting?</li></ul><dl><dt class="references">Request
	      concerning</dt><dd class="references">URI</dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2003/10/20-tag-summary#abstractComponentRefs-37">20 Oct 2003</a>, <a href="http://www.w3.org/2004/05/14-tag-summary#URIGoodPractice-40">14 May 2004</a>, <a href="http://www.w3.org/2005/02/22-tagmem-minutes#item15">22 Feb 2005</a>, <a href="http://www.w3.org/2005/09/21-tagmem-minutes#item12">21 Sep 2005</a>, <a href="http://www.w3.org/2001/tag/2005/12/13-tagmem-minutes#item10">13 Dec 2005</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Member/tag/2003Oct/0059">raised</a> on 16 Oct 2003 by 
						David Orchard
					, on behalf of <a href="http://www.w3.org/2001/tag/">
						TAG
					</a></dt><dd></dd><dt><a href="http://www.w3.org/2003/10/20-tag-summary#abstractComponentRefs-37">accepted</a> on 20 Oct 2003</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="#abstractComponentRefs-37">
										abstractComponentRefs-37
									</a></li><li><a href="http://www.mikeschinkel.com/blog/welldesignedurlsarebeautiful.aspx">
										Well Designed URLs are
										Beautiful!
									</a></li></ul></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						RF
					</h5><ul><li><a href="http://www.w3.org/2003/10/20-tag-summary">accepted on 20 Oct 2003</a><br /><p>
									Draft a finding for this issue.
									Reconfirmed
									<a href="http://www.w3.org/2005/09/21-tagmem-minutes#action08">
										21 Sep 2005
									</a>
									.
								</p></li><li><a href="http://www.w3.org/2001/tag/2006/01/24-minutes#item04">dropped on 24 Jan 2006</a></li></ul></div><div class="details-action decided"><h5>
						RF
					</h5><ul><li><a href="http://www.w3.org/2005/09/21-tagmem-minutes#action10">accepted on 21 Sep 2005</a><br /><p>
									consider noting in finding on good
									uri practices that gooduri#xmlname
									is a useful pattern because it can
									be used easily in RDF
								</p></li><li><a href="http://www.w3.org/2001/tag/2006/01/24-minutes#item04">dropped on 24 Jan 2006</a></li></ul></div></div></div><div class="issue"><h3><a id="XMLVersioning-41" name="XMLVersioning-41">XMLVersioning-41</a>: 
				What are good practices for designing extensible XML
				languages and for handling versioning?
			 [<a href="issues.html#XMLVersioning-41">link to this issue</a>]</h3><p>
							What are good practices for designing
							extensible XML languages and for handling
							versioning?
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references">XML</dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2003/11/03-tag-summary">3 Nov 2003</a>, <a href="http://www.w3.org/2003/11/10-tag-summary">10 Nov 2003</a>, <a href="http://www.w3.org/2003/11/15-tag-summary">15 Nov 2003</a>, <a href="http://www.w3.org/2004/03/02-tag-summary#xmlVersioning-41">2 Mar 2003</a>, <a href="http://www.w3.org/2004/05/14-tag-summary#XMLVersioning-41">14 May 2004</a>, <a href="http://www.w3.org/2005/02/14-tagmem-minutes#item09">14 Feb 2005</a>, <a href="http://www.w3.org/2005/09/21-tagmem-minutes#item15">21 Sep 2005</a>, <a href="http://www.w3.org/2005/09/22-tagmem-minutes#item02">22 Sep 2005</a>, <a href="http://www.w3.org/2001/tag/2005/11/08-tagmem-minutes#item05">8 Nov 2005</a>, <a href="http://www.w3.org/2001/tag/2005/12/05-tagmem-minutes#item09">5 Dec 2005</a>, <a href="http://www.w3.org/2001/tag/2006/02/14-tagmem-minutes#item05">14 Feb 2006</a>, <a href="http://www.w3.org/2001/tag/2006/02/27-tagmem-minutes-2.htm#XMLVersion">27 Feb 2006</a>, <a href="http://www.w3.org/2001/tag/2006/03/03-tagmem-minutes#item01">3 Mar 2006</a>, <a href="http://www.w3.org/2001/tag/2006/06/12-tagmem-minutes#item04">12 Jun 2006</a>, <a href="http://www.w3.org/2001/tag/2006/07/18-minutes#item07">18 Jul 2006</a>, <a href="http://www.w3.org/2006/07/25-tagmem-minutes#item03">25 Jul 2006</a>, <a href="http://lists.w3.org/Archives/Public/www-tag/2006Aug/att-0068/08-tagmem-minutes#item03">8 Aug 2006</a>, <a href="http://www.w3.org/2006/08/29-tagmem-minutes#item04">29 Aug 2006</a>, <a href="http://lists.w3.org/Archives/Public/www-tag/2006Sep/att-0028/01-part">5 Sep 2006</a>, <a href="http://www.w3.org/2001/tag/2006/10/04-tagmem-minutes#item05">4 Oct 2006</a>, <a href="http://www.w3.org/2001/tag/2006/10/05-morning-minutes#item01">5 Oct 2006</a>, <a href="http://www.w3.org/2001/tag/2006/10/05-afternoon-minutes#item01">5 Oct 2006</a>, <a href="http://www.w3.org/2001/tag/2006/12/12-tagmem-minutes#item01">12 Dec 2006</a>, <a href="http://www.w3.org/2001/tag/2006/12/12-tagmem-minutes#item04">12 Dec 2006</a>, <a href="http://www.w3.org/2001/tag/2007/04/16-minutes#item02">16 Apr 2007</a>, <a href="http://www.w3.org/2001/tag/2007/04/23-minutes#item02">23 Apr 2007</a>, <a href="http://www.w3.org/2001/tag/2007/04/30-minutes#item05">30 Apr 2007</a>, <a href="http://www.w3.org/2001/tag/2007/05/14-minutes#item10">14 May 2007</a>, <a href="http://www.w3.org/2001/tag/2007/05/30-minutes#item04">30 May 2007</a>, <a href="http://www.w3.org/2001/tag/2007/05/30-minutes#item06">30 May 2007</a>, <a href="http://www.w3.org/2001/tag/2007/05/31-tagmem-minutes#item04">31 May 2007</a>, <a href="http://www.w3.org/2001/tag/2007/06/25-minutes#item05">25 Jun 2007</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2003Jun/0086">raised</a> on 27 Jun 2003 by 
						David Orchard
					, on behalf of <a href="http://www.w3.org/2001/tag/">
						TAG
					</a></dt><dd></dd><dt><a href="http://www.w3.org/2003/11/03-tag-summary">accepted</a> on 3 Nov 2003</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li>
									Draft finding from DO and NW
									<a href="http://lists.w3.org/Archives/Public/www-tag/2004Nov/att-0071/versioning-part1">
										part 1
									</a>
									,
									<a href="http://lists.w3.org/Archives/Public/www-tag/2004Nov/att-0071/versioning-part2">
										part 2
									</a></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2003Oct/0137">
										Text proposed by DO and NW for
										Arch Doc
									</a></li><li><a href="http://www.w3.org/2001/tag/2005/09/22-diagram1.png">
										Instance diagram
									</a></li></ul></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>IJ</h5><ul><li><a href="http://www.w3.org/2003/11/03-tag-summary">accepted on 3 Nov 2003</a><br /><p>
									Propose shortened version of DO/NW
									proposed text
								</p></li><li><a href="http://lists.w3.org/Archives/Member/tag/2003Nov/0021">proposal on 7 Nov 2003</a><br /><p>Revised text</p></li><li><a href="http://www.w3.org/2003/11/10-tag-summary">completed on 10 Nov 2003</a></li></ul></div><div class="details-action decided"><h5>IJ/DO/NW</h5><ul><li><a href="http://www.w3.org/2003/11/10-tag-summary">accepted on 10 Nov 2003</a><br /><p>
									Propose revision of IJ proposal that
									better addresses NW and DO concerns.
								</p></li><li><a href="http://www.w3.org/2001/tag/2003/webarch-20031111/">proposal on 11 Nov 2003</a><br /><p>
									Part of
									<a href="http://www.w3.org/2001/tag/2003/webarch-20031111/">
										11 Nov 2003 Editor's Draft
									</a></p></li><li><a href="http://www.w3.org/2003/11/15-tag-summary">completed on 15 Nov 2003</a><br /><p>
									Text reviewed, edited at FTF meeting
									in Japan.
								</p></li></ul></div><div class="details-action decided"><h5>
						TBL
					</h5><ul><li><a href="http://www.w3.org/2003/07/14-tag-summary">accepted on 14 Jul 2003</a><br /><p>
									Suggest changes to section about
									extensibility related to "when to
									tunnel".
								</p></li><li><a href="http://www.w3.org/2004/05/14-tag-summary#XMLVersioning-41">dropped on 14 May 2004</a></li></ul></div><div class="details-action decided"><h5>
						DO
					</h5><ul><li><a href="http://lists.w3.org/Archives/Member/w3c-xml-schema-wg/2005Mar/att-0006/xml-schema-f2f-minutes-2005-03-03#p219">accepted on 3 Mar 2005</a><br /><p>
									contextualize his scenarios, such as
									more on what is happening with SOAP
									and WSDL.
								</p></li><li><a href="http://www.w3.org/2001/tag/2006/02/14-tagmem-minutes#action04">completed on 14 Feb 2006</a></li></ul></div><div class="details-action decided"><h5>
						DO
					</h5><ul><li><a href="http://www.w3.org/2005/09/22-tagmem-minutes#action01">accepted on 22 Sep 2005</a><br /><p>Update finding with ext/vers</p></li><li><a href="http://www.w3.org/2001/tag/2006/06/12-tagmem-minutes#action03">dropped on 12 Jun 2006</a></li></ul></div><div class="details-action decided"><h5>
						DO
					</h5><ul><li><a href="http://www.w3.org/2005/09/22-tagmem-minutes#action05">accepted on 22 Sep 2005</a><br /><p>
									with NM continue and extrapolate the
									versioning work DO et al have been
									doing already, updating the
									terminology section. Reconfirmed
									<a href="http://www.w3.org/2005/12/05-tagmem-minutes#action03">
										5 Dec 2005
									</a>
									,
									<a href="http://www.w3.org/2001/tag/2006/02/14-tagmem-minutes#action05">
										14 Feb 2006
									</a>
									,
									<a href="http://www.w3.org/2001/tag/2006/06/12-tagmem-minutes#action04">
										12 Jun 2006
									</a>
									.
								</p></li><li><a href="http://www.w3.org/2001/tag/2006/10/05-afternoon-minutes#PENDING">completed on 5 Oct 2006</a></li></ul></div><div class="details-action decided"><h5>
						DC
					</h5><ul><li><a href="http://www.w3.org/2005/09/22-tagmem-minutes#action03">accepted on 22 Sep 2005</a><br /><p>
									derive RDF/RDFS/OWL version of
									terminology from whiteboard /
									<a href="http://www.w3.org/2001/tag/2005/09/22-diagram1.png">
										diagram
									</a>
									. Reconfirmed
									<a href="http://www.w3.org/2001/tag/2005/11/08-tagmem-minutes#action04">
										8 Nov 2005
									</a></p></li><li><a href="http://lists.w3.org/Archives/Public/public-xml-versioning/2006Feb/0003">completed on 14 Feb 2006</a></li></ul></div><div class="details-action decided"><h5>
						HT
					</h5><ul><li><a href="http://www.w3.org/2005/09/22-tagmem-minutes#action04">accepted on 22 Sep 2005</a><br /><p>
									make sure that what he is doing with
									ontology of XML infoset fits with
									what DanC is doing on ontology of
									Language etc. Reconfirmed on
									<a href="http://www.w3.org/2001/tag/2006/06/12-tagmem-minutes#action02">
										12 Jun 2006
									</a></p></li><li><a href="http://www.w3.org/2001/tag/2006/10/05-afternoon-minutes#PENDING1">dropped on 5 Oct 2006</a></li></ul></div><div class="details-action decided"><h5>
						DO
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2005/10/04-minutes#action07">accepted on 4 Oct 2005</a><br /><p>
									update extensibility finding with
									the result of Edinburgh F2F
									discussion and related diagrams.
									Reconfirmed
									<a href="http://www.w3.org/2001/tag/2005/11/08-tagmem-minutes#action05">
										8 Nov 2005
									</a></p></li><li><a href="http://www.w3.org/2006/02/21-tagmem-minutes#item08">completed on 21 Feb 2006</a></li></ul></div><div class="details-action decided"><h5>
						DO
					</h5><ul><li><a href="http://www.w3.org/2005/12/05-tagmem-minutes#action03">accepted on 5 Dec 2005</a><br /><p>
									produce a new draft of his
									versioning finding by the end of the
									year
								</p></li><li><a href="http://www.w3.org/2001/tag/2006/06/12-tagmem-minutes#action03">dropped on 12 Jun 2006</a></li></ul></div><div class="details-action decided"><h5>
						DO
					</h5><ul><li><a href="http://www.w3.org/2006/02/21-tagmem-minutes#action01">accepted on 21 Feb 2006</a><br /><p>
									provide two diagrams: one
									XML-ignorant, one XML-aware
								</p></li><li><a href="http://www.w3.org/2001/tag/2006/06/12-tagmem-minutes#action05">completed on 12 Jun 2006</a></li></ul></div><div class="details-action decided"><h5>
						VQ
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/03/03-tagmem-minutes#action02">accepted on 3 Mar 2006</a><br /><p>
									Write to www-tag about CSS
									versioning being a problem "levels".
									Reconfirmed
									<a href="http://www.w3.org/2001/tag/2006/06/12-tagmem-minutes#action06">
										12 Jun 2006
									</a>
									,
									<a href="http://www.w3.org/2001/tag/2006/10/05-afternoon-minutes#PENDING2">
										5 Oct 2006
									</a></p></li><li><a href="">dropped on 21 May 2007</a></li></ul></div><div class="details-action decided"><h5>
						DC
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/03/03-tagmem-minutes#action03">accepted on 3 Mar 2006</a><br /><p>
									Look at the document and see if it
									is good for informing on this SMIL
									problem of multiple namespaces.
									Reconfirmed
									<a href="http://www.w3.org/2001/tag/2006/06/12-tagmem-minutes#action07">
										12 Jun 2006
									</a></p></li><li><a href="http://www.w3.org/2001/tag/2006/10/05-afternoon-minutes#PENDING3">dropped on 12 Jun 2006</a></li></ul></div><div class="details-action"><h5>
						DC
					</h5><ul><li><a href="http://lists.w3.org/Archives/Public/www-tag/2006Aug/att-0068/08-tagmem-minutes#action01">accepted on 8 Aug 2006</a><br /><p>
									Review definitions of partial
									understanding, backward compatible,
									and forward compatible.
									<a href="http://lists.w3.org/Archives/Public/www-tag/2006Aug/0084">
										Progress report
									</a>
									, confirmed
									<a href="http://www.w3.org/2001/tag/2006/10/05-afternoon-minutes#PENDING4">
										5 Oct 2006
									</a>
									,
									<a href="http://www.w3.org/2001/tag/2007/07/09-tagmem-minutes#action01">
										9 July 2007
									</a>
									.
								</p></li><li><a href="http://www.w3.org/2001/tag/group/track/actions/4">proposal on 24 Aug 2007</a><br /><p>
									Tracking transferred to tracker
									<a href="http://www.w3.org/2001/tag/group/track/actions/4">
										ACTION-4
									</a></p></li></ul></div><div class="details-action decided"><h5>
						HT
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/10/05-afternoon-minutes#action01">accepted on 5 Oct 2006</a><br /><p>
									Henry to extend his paper to a
									definition of monotonicity and its
									relevance to our versioning finding.
								</p></li><li><a href="http://www.w3.org/2001/tag/2007/07/09-tagmem-minutes#item02">dropped on 9 Jul 2007</a></li></ul></div><div class="details-action decided"><h5>
						DC
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/10/05-afternoon-minutes#action02">accepted on 5 Oct 2006</a><br /><p>
									Capture UML diagram for the minutes.
								</p></li><li><a href="">dropped on 21 May 2007</a></li></ul></div><div class="details-action decided"><h5>NW</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/12/12-tagmem-minutes#action01">accepted on 12 Dec 2006</a><br /><p>
									Produce some information about NVDL
									for the finding. Continued
									<a href="http://www.w3.org/2001/tag/2007/07/09-tagmem-minutes#action03">
										9 July 2007
									</a></p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2007Jul/0041">proposal on 12 Jul 2007</a><br /><p>Email about NVDL and versioning.</p></li><li><a href="http://www.w3.org/2001/tag/2007/08/20-minutes#item07">completed on 20 Aug 2007</a></li></ul></div><div class="details-action decided"><h5>
						HT
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2007/04/23-minutes#action01">accepted on 23 Apr 2007</a><br /><p>
									Henry to unearth thread in which he
									and Robin Berjon discussed XML
									versioning
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2007May/0037.html">completed on 21 May 2007</a></li></ul></div><div class="details-action decided"><h5>
						DO
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2007/04/23-minutes#action02">accepted on 23 Apr 2007</a><br /><p>
									Dave Orchard to draft discussion of
									using substitution groups for
									examples like HTML &lt;p&gt; mixed
									content and/or &lt;td&gt; content.
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2007May/0001.html">proposal on 2 May 2007</a><br /><p>
									Email from David Orchard "Use of
									Substitution Groups" take 2
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2007May/0002.html">proposal on 2 May 2007</a><br /><p>
									Email from David Orchard "Use of
									Substitution Groups" take 2.1
								</p></li><li><a href="http://www.w3.org/2001/tag/2007/05/14-minutes#item10">completed on 14 May 2007</a></li></ul></div><div class="details-action decided"><h5>NW</h5><ul><li><a href="http://www.w3.org/2001/tag/2007/04/23-minutes#action04">accepted on 23 Apr 2007</a><br /><p>
									Norm to review
									<a href="http://www.w3.org/2001/tag/doc/versioning-xml">
										http://www.w3.org/2001/tag/doc/versioning-xml
									</a>
									for discussion on 14 May telcon.
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2007May/0008.html">proposal on 11 May 2007</a><br /><p>
									Email from Norm "(Partial) review of
									Versioning XML"
								</p></li><li><a href="http://www.w3.org/2001/tag/2007/05/14-minutes#item10">completed on 14 May 2007</a></li></ul></div><div class="details-action decided"><h5>
						DO
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2007/05/14-minutes#action05">accepted on 14 May 2007</a><br /><p>
									dorchard to produce revised
									Versioning-part1 and Versioning-XML
									for May 18th
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2007May/0028.html">completed on 17 May 2007</a><br /><p>
									Email from Dave announcing new
									drafts.
								</p></li></ul></div><div class="details-action decided"><h5>NW</h5><ul><li><a href="http://www.w3.org/2001/tag/2007/05/31-tagmem-minutes#action01">accepted on 31 May 2007</a><br /><p>
									NDW to note a problem near
									webarch/#pr-version-info in the
									errata. Continued:
									<a href="http://www.w3.org/2001/tag/2007/07/09-agenda">
										9 July 2007
									</a>
									.
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2007Jul/0038">proposal on 12 Jul 2007</a><br /><p>Errata message from Norm</p></li><li><a href="http://www.w3.org/2001/tag/2007/07/16-minutes#item03">completed on 16 Jul 2007</a></li></ul></div><div class="details-action"><h5>
						NM
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2007/05/31-tagmem-minutes#action02">accepted on 31 May 2007</a><br /><p>
									NM to draft a blog item for review
									and, pending creation of a TAG blog
									mechanism, post it. Continued:
									<a href="http://www.w3.org/2001/tag/2007/07/09-agenda">
										9 July 2007
									</a>
									.
								</p></li><li><a href="http://www.w3.org/2001/tag/group/track/actions/28">proposal on 24 Aug 2007</a><br /><p>
									Tracking transferred to tracker
									<a href="http://www.w3.org/2001/tag/group/track/actions/28">
										ACTION-28
									</a></p></li></ul></div><div class="details-action"><h5>
						NM
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2007/05/31-tagmem-minutes#action03">accepted on 30 May 2007</a><br /><p>
									NM to write up his paper comments on
									extensibility and versioning
									Continued:
									<a href="http://www.w3.org/2001/tag/2007/07/09-agenda">
										9 July 2007
									</a>
									.
								</p></li><li><a href="http://www.w3.org/2001/tag/group/track/actions/29">proposal on 24 Aug 2007</a><br /><p>
									Tracking transferred to tracker
									<a href="http://www.w3.org/2001/tag/group/track/actions/29">
										ACTION-29
									</a></p></li></ul></div><div class="details-action decided"><h5>
						DO
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2007/06/11-minutes#action04">accepted on 11 Jun 2007</a><br /><p>
									Dave Orchard to revise Versioning
									Findings in response to F2F
									discussions.
								</p></li><li><a href="http://www.w3.org/2001/tag/2007/06/25-minutes#action02">proposal on 25 Jun 2007</a><br /><p>
									Continuation:David to update all 3
									documents in versioning finding (by
									mid-July2007)
								</p></li><li><a href="http://www.w3.org/2001/tag/2007/07/09-tagmem-minutes#item02">completed on 9 Jul 2007</a></li></ul></div></div></div><div class="issue"><h3><a id="ultimateQuestion-42" name="ultimateQuestion-42">ultimateQuestion-42</a>: 
				What is the answer to life, the universe, and
				everything.
			 [<a href="issues.html#ultimateQuestion-42">link to this issue</a>]</h3><p>
							This "issue" collects all discussions
							relevant to Web architecture that are not
							directly related to any other issue.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><a href="http://en.wikipedia.org/wiki/The_Hitchhiker%27s_Guide_to_the_Galaxy">
						The Hitch Hiker's Guide to the Galaxy
					</a></dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2003/11/15-tag-summary#uq">15 Nov 2003</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://www.w3.org/2003/11/15-tag-summary">raised</a> on 15 Nov 2003 by 
						Tim Berners-Lee
					, on behalf of <a href="http://www.w3.org/2001/tag/">
						TAG
					</a></dt><dd></dd><dt><a href="http://www.w3.org/2003/11/15-tag-summary#uq">accepted</a> on 15 Nov 2003</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="http://en.wikipedia.org/wiki/The_Answer_to_Life,_the_Universe,_and_Everything">
										Wikipedia entry on issue 42
									</a></li><li><a href="http://www.google.com/help/features.html#calculator">
										Google Calculator; cf 6*9
									</a></li><li>- - - - - - - - - -</li><li>
									Semantic Web Architecture:
									<a href="http://www.w3.org/2001/tag/2005/06/14-16-minutes#item022">
										16 Jun 2005
									</a>
									,
									<a href="http://www.w3.org/2001/tag/2005/09/22-tagmem-minutes#item04">
										22 Sep 2005
									</a>
									,
									<a href="http://www.w3.org/2001/tag/2006/12/13-morning-minutes#item01">
										13 Dec 2006
									</a></li><li>
									Self-describing Web:
									<a href="http://www.w3.org/2001/tag/2005/12/06-Morning-minutes#item02">
										06 Dec 2005
									</a>
									,
									<a href="http://www.w3.org/2001/tag/2006/02/27_minutes#L311">
										27 Feb 2006
									</a>
									,
									<a href="http://www.w3.org/2001/tag/2007/03/06-minutes#item08">
										6 Mar 2007
									</a>
									,
									<a href="http://www.w3.org/2001/tag/2007/06/01-minutes#item02">
										1 Jun 2007
									</a>
									.
								</li><li><a href="http://www.w3.org/2001/tag/doc/state">
										State in Web application design
									</a>
									:
									<a href="http://www.w3.org/2006/02/21-tagmem-minutes#item07">
										21 Feb 2006
									</a>
									,
									<a href="http://www.w3.org/2006/03/28-tagmem-minutes#item04">
										28 Mar 2006
									</a>
									,
									<a href="http://www.w3.org/2001/tag/2006/04/25-tagmem-minutes#item04">
										25 Apr 2006
									</a>
									,
									<a href="http://www.w3.org/2006/05/09-tagmem-minutes#item03">
										9 May 2006
									</a>
									,
									<a href="http://www.w3.org/2001/tag/2006/06/06-tagmem-minutes#item06">
										6 June 2006
									</a>
									,
									<a href="http://www.w3.org/2001/tag/2006/06/13-morning-minutes#item03">
										13 June 2006
									</a>
									,
									<a href="http://www.w3.org/2001/tag/2006/09/26-tagmem-minutes#item05">
										26 Sep 2006
									</a></li><li>
									Security/Authentication:
									<a href="http://www.w3.org/2001/tag/2005/06/14-16-minutes#item025">
										15 Jun 2005
									</a>
									,
									<a href="http://www.w3.org/2005/07/05-tagmem-minutes#item04">
										5 Jul 2005
									</a>
									,
									<a href="http://www.w3.org/2001/tag/2005/09/20PM-minutes#item02">
										20 Sep 2005
									</a>
									,
									<a href="http://www.w3.org/2001/tag/2005/11/08-tagmem-minutes#item04">
										8 Nov 2005
									</a>
									,
									<a href="http://www.w3.org/2001/tag/2006/01/24-minutes#item02">
										24 Jan 2006
									</a>
									,
									<a href="http://www.w3.org/2006/03/21-tagmem-minutes#item02">
										21 Mar 2006
									</a>
									,
									<a href="http://www.w3.org/2001/tag/2006/04/11-tagmem-minutes#item09">
										11 Apr 2006
									</a>
									,
									<a href="http://www.w3.org/2001/tag/2006/04/25-tagmem-minutes#item05">
										25 Apr 2006
									</a>
									,
									<a href="http://www.w3.org/2001/tag/2006/06/13-afternoon-minutes">
										13 Jun 2006
									</a></li><li>
									CURIEs:
									<a href="http://www.w3.org/2006/05/30-tagmem-minutes#item03">
										30 May 2006
									</a>
									,
									<a href="http://www.w3.org/2001/tag/2006/06/14-minutes#item02">
										13 Jun 2006
									</a>
									,
									<a href="http://www.w3.org/2001/tag/2006/06/27-minutes#item03">
										27 Jun 2006
									</a>
									,
									<a href="http://www.w3.org/2007/02/26-tagmem-minutes#item08">
										26 Feb 2007
									</a>
									,
									<a href="http://www.w3.org/2007/03/19-tagmem-minutes#item03">
										19 Mar 2007
									</a>
									,
									<a href="http://www.w3.org/2007/04/02-tagmem-minutes#item01">
										2 Apr 2007
									</a>
									.
								
									See
									<a href="#abbreviatedURIs-56">
										abbreviatedURIs-56
									</a>
									for continuing discussion.
								</li><li>
									Device description repositories:
									<a href="http://www.w3.org/2001/tag/2006/06/06-tagmem-minutes#item05">
										6 Jun 2006
									</a>
									,
									<a href="http://www.w3.org/2001/tag/2006/06/27-minutes#item05">
										27 Jun 2006
									</a></li><li>
									New and changing media types:
									<a href="http://www.w3.org/2001/tag/2006/07/18-minutes#item05">
										18 Jul 2006
									</a>
									,
									<a href="http://www.w3.org/2006/07/25-tagmem-minutes#item02">
										25 Jul 2006
									</a>
									.
								</li><li>
									Naming and Virtual Worlds
									<a href="http://www.w3.org/2007/06/18-tagmem-minutes#item02">
										18 June 2007
									</a></li></ul></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						HT
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2005/06/14-16-minutes#action031">accepted on 16 Jun 2005</a><br /><p>
									HT, VQ to review the
									<a href="http://www.w3.org/2000/10/swap/Primer">
										primer
									</a>
									(getting into RDF &amp; Semantic Web
									using N3)
								</p></li><li><a href="">dropped on 24 Aug 2007</a><br /><p>Dropped by chair</p></li></ul></div><div class="details-action decided"><h5>
						TBL
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2005/06/14-16-minutes#action041">accepted on 16 Jun 2005</a><br /><p>
									Revise
									<a href="http://www.w3.org/DesignIssues/HTTP-URI">
										http://www.w3.org/DesignIssues/HTTP-URI
									</a></p></li><li><a href="">dropped on 24 Aug 2007</a><br /><p>Dropped by chair</p></li></ul></div><div class="details-action decided"><h5>
						HT
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2005/06/14-16-minutes#action051">accepted on 16 Jun 2005</a><br /><p>
									Recommend intro to Dretske thought
								</p></li><li><a href="">dropped on 24 Aug 2007</a><br /><p>Dropped by chair</p></li></ul></div><div class="details-action decided"><h5>
						TBL
					</h5><ul><li><a href="http://www.w3.org/2005/09/22-tagmem-minutes#action06">accepted on 22 Sep 2005</a><br /><p>
									TBL and NW to write a draft of Nadia
									and Dirk first semantic web book
								</p></li><li><a href="">dropped on 24 Aug 2007</a><br /><p>dropped by chair</p></li></ul></div><div class="details-action decided"><h5>
						DC
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2005/06/14-16-minutes#action042">accepted on 15 Jun 2005</a><br /><p>
									Write a report on the state of the
									art authentication in the web.
								</p></li><li><a href="http://www.w3.org/2001/tag/2005/09/20PM-minutes#item02">proposal on 20 Sep 2005</a><br /><p>
									Presentation at Edinburgh f2f, see
									also
									<a href="http://www.w3.org/2005/07/05-tagmem-minutes#item04">
										minutes of 5 Jul 05
									</a></p></li><li><a href="http://www.w3.org/2006/03/21-tagmem-minutes#item02">dropped on 21 Mar 2006</a><br /><p>
									Withdrawn as of DC's report on the
									<a href="http://www.w3.org/2005/Security/usability-ws/">
										W3C workshop on security
									</a>
									.
								</p></li></ul></div><div class="details-action decided"><h5>
						DC
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2005/06/14-16-minutes#action052">accepted on 15 Jun 2005</a><br /><p>
									Draft "Dont use passwords in the
									clear". See
									<a href="http://www.w3.org/2005/07/05-tagmem-minutes#item04">
										minutes of 5 Jul 05
									</a></p></li><li><a href="http://www.w3.org/2006/04/18-tagmem-minutes#action01">dropped on 18 Apr 2006</a><br /><p>
									Obsoleted in favor of Ed's action of
									18 Apr 06 under
									<a href="#passwordsInTheClear-52">
										passwordsInTheClear-52
									</a>
									.
								</p></li></ul></div><div class="details-action decided"><h5>NW</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/04/25-tagmem-minutes#action05">accepted on 25 Apr 2006</a><br /><p>
									Review draft state finding for 9
									May.
								</p></li><li><a href="http://www.w3.org/2001/tag/2007/07/16-minutes#item03">dropped on 16 Jul 2007</a></li></ul></div><div class="details-action decided"><h5>
						DC
					</h5><ul><li><a href="http://www.w3.org/2006/05/30-tagmem-minutes#action07">accepted on 30 May 2006</a><br /><p>
									Contact Misha to follow up on f2f
									discussion on CURIEs at AC meeting
								</p></li><li><a href="http://lists.w3.org/Archives/Member/tag/2006Jul/0009">completed on 14 Jul 2006</a></li></ul></div><div class="details-action decided"><h5>
						VQ
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/06/06-tagmem-minutes#action02">accepted on 6 Jun 2006</a><br /><p>
									Invite a DD WG person to a TAG
									meeting to discuss DDR requirements
								</p></li><li><a href="">dropped on 8 Jun 2007</a><br /><p>
									Dropped by chair (overtaken bye
									events)
								</p></li></ul></div><div class="details-action decided"><h5>
						DO
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/06/13-morning-minutes#action01">accepted on 13 Jun 2006</a><br /><p>
									Revise CSCP (Cookies, Shopping
									Carts, Personalization, etc) in
									State finding. Confirmed
									<a href="http://www.w3.org/2001/tag/2006/09/26-tagmem-minutes#action05">
										26 Sep 2006
									</a>
									.
								</p></li><li><a href="">dropped on 24 Aug 2007</a><br /><p>Dropped by chair</p></li></ul></div><div class="details-action decided"><h5>NW</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/06/13-morning-minutes#action02">accepted on 13 Jun 2006</a><br /><p>
									Review new version of state finding
									when it comes out. Confirmed
									<a href="http://www.w3.org/2001/tag/2006/09/26-tagmem-minutes#action06">
										26 Sep 2006
									</a>
									.
								</p></li><li><a href="http://www.w3.org/2001/tag/2007/07/16-minutes#item03">dropped on 16 Jul 2007</a><br /><p>Withdrawn pending a new draft.</p></li></ul></div><div class="details-action decided"><h5>
						NM
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/06/13-morning-minutes#action02">accepted on 13 Jun 2006</a><br /><p>
									Review new version of state finding
									when it comes out
								</p></li><li><a href="http://www.w3.org/2001/tag/2007/07/16-minutes#item03">dropped on 16 Jul 2007</a><br /><p>Withdrawn pending a new draft.</p></li></ul></div><div class="details-action decided"><h5>
						NM
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/07/18-minutes#action02">accepted on 18 Jul 2006</a><br /><p>
									draft a very short email suggesting
									that in general its good [using
									media types that aren't yet
									registered but used]
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2006Jul/0027">completed on 21 Jul 2006</a></li></ul></div><div class="details-action decided"><h5>
						NM
					</h5><ul><li><a href="http://www.w3.org/2006/07/25-tagmem-minutes#action01">accepted on 25 Jul 2006</a><br /><p>
									Redraft [position on unregistered
									mime types], forward to AB unless
									unresolved negative comments from
									TAG members
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2006Aug/0012">completed on 4 Aug 2006</a></li></ul></div><div class="details-action decided"><h5>
						TBL
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/10/05-afternoon-minutes#ACTION">accepted on 5 Oct 2006</a><br /><p>
									With Norm, draft semantic web
									architecture stories and such.
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-archive/2006Dec/att-0010/SEMWEB">completed on 13 Dec 2006</a></li></ul></div><div class="details-action decided"><h5>ER</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/12/13-morning-minutes#action01">accepted on 13 Dec 2006</a><br /><p>
									Will try to outline or sketch a
									story.
								</p></li><li><a href="">dropped on 24 Aug 2007</a><br /><p>dropped by chair</p></li></ul></div><div class="details-action decided"><h5>
						TBL
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/12/13-morning-minutes#action02">accepted on 13 Dec 2006</a><br /><p>
									Tim and Norm to produce a new draft
									of "Data on the Web" by end of
									January 2007.
								</p></li><li><a href=""> on 24 Aug 2007</a><br /><p>droppped by chair</p></li></ul></div><div class="details-action decided"><h5>SW</h5><ul><li><a href="http://www.w3.org/2007/02/26-tagmem-minutes#action02">accepted on 26 Feb 2007</a><br /><p>
									Stuart to contact the Semantic Web
									Deployment and HTML WG chairs for an
									update on the status of this
									document and to encourage them to
									make it public.
								</p></li><li><a href="http://lists.w3.org/Archives/Member/tag/2007Feb/0084">proposal on 27 Feb 2007</a><br /><p>
									Email to HTML-WG and SWD-WG chairs
									and team-contacts requesting
									visibility of CURIE WD
								</p></li><li><a href="http://www.w3.org/News/2007#item44">completed on 7 Mar 2007</a></li></ul></div><div class="details-action decided"><h5>
						HT
					</h5><ul><li><a href="http://www.w3.org/2007/03/19-tagmem-minutes#action01">accepted on 19 Mar 2007</a><br /><p>
									HST to circulate a candidate
									description to tag@w3.org [to frame
									a distinct topic/issue on CURIE].
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2007Mar/0037.html">completed on 30 Mar 2007</a></li></ul></div><div class="details-action decided"><h5>
						NM
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2007/04/30-minutes#action01">accepted on 30 Apr 2007</a><br /><p>
									Noah to create a new draft on
									self-describing Web by 23rd for
									review at F2F
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2007May/0050.html">completed on 24 May 2007</a></li></ul></div><div class="details-action"><h5>
						NM
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2007/06/11-minutes#action01">accepted on 11 Jun 2007</a><br /><p>
									Noah to revise Self-Describing Web
									finding in response to F2F
									discussion.
								</p></li><li><a href="http://www.w3.org/2001/tag/group/track/actions/30">proposal on 24 Aug 2007</a><br /><p>
									Tracking transferred to tracker
									<a href="http://www.w3.org/2001/tag/group/track/actions/30">
										ACTION-30
									</a></p></li></ul></div><div class="details-action"><h5>
						NM
					</h5><ul><li><a href="http://www.w3.org/2007/06/18-tagmem-minutes.html#action01">accepted on 18 Jun 2007</a><br /><p>
									NM to contact Don Brutzman to query
									about possible contacts about naming
									in V-Ws and integration with the
									Web.
								</p></li><li><a href="http://www.w3.org/2001/tag/group/track/actions/2">proposal on 24 Aug 2007</a><br /><p>
									Tracking transferred to tracker
									<a href="http://www.w3.org/2001/tag/group/track/actions/2">
										ACTION-2
									</a></p></li></ul></div></div></div><div class="issue"><h3><a id="DerivedResources-43" name="DerivedResources-43">DerivedResources-43</a>: How are secondary resources derived? [<a href="issues.html#DerivedResources-43">link to this issue</a>]</h3><p>
							How are secondary resources derived? The TAG
							discussed the case of parse='xml' and
							fragment identifiers in XInclude.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references">XInclude</dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2003/11/15-tag-summary">15 Nov 2003</a>, <a href="http://www.w3.org/2004/05/14-tag-summary#DerivedResources-43">12 May 2004</a>, <a href="http://www.w3.org/2005/09/21-tagmem-minutes#item13">21 Sep 2005</a>, <a href="http://www.w3.org/2006/01/31-tagmem-minutes#item05">31 Jan 2006</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://www.w3.org/2003/11/15-tag-summary#xincl">raised</a> on 15 Nov 2003 by 
						David Orchard
					, on behalf of <a href="http://www.w3.org/2001/tag/">
						TAG
					</a></dt><dd></dd><dt><a href="http://www.w3.org/2003/11/15-tag-summary#xincl">accepted</a> on 15 Nov 2003</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="http://www.w3.org/XML/Group/2000/03/xinclude-issues">
										XInclude issues list
									</a></li></ul></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>NW</h5><ul><li><a href="http://www.w3.org/2004/05/14-tag-summary#DerivedResources-43">accepted on 12 May 2004</a><br /><p>
									Write to David Orchard saying that
									XInclude no longer uses frag ids and
									the TAG is unable to construct from
									its meeting record what the issue
									was. We will discuss this further if
									we get help, but otherwise expect to
									close without action.
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2004Jun/0025">proposal on 28 Jun 2004</a><br /><p>
									NW reports that he has sent mail;
									awaiting reply.
								</p></li><li><a href="http://www.w3.org/2006/01/31-tagmem-minutes#item06">completed on 31 Jan 2006</a></li></ul></div></div></div><div class="issue"><h3><a id="xmlChunk-44" name="xmlChunk-44">xmlChunk-44</a>: Chunk of XML - Canonicalization and equality [<a href="issues.html#xmlChunk-44">link to this issue</a>]</h3><p>
							The XML architecture has tended to be built
							according to a motto that all kinds of
							things are possible, and the application has
							to be able to chose the features it needs.
							This is fine when there are simply the XML
							toolset and a single "application". However,
							real life is more complicated, and things
							are connected together in all kinds of ways.
							I think the XML design needs to be more
							constraining: to offer a consistent idea of
							what a chunk of XML is across all the
							designs, so that the value of that chunk can
							be preserved as invariant across a complex
							system. Digital Signature and RDF transport
							are just intermediate parts of the design
							which need to be transparent. This required
							a notion of equality, and a related
							canonical serialization.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references">XML</dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2004/02/02-tag-summary">2 Feb 2004</a>, <a href="http://www.w3.org/2004/03/02-tag-summary#xmlChunk-44">2 Mar 2004</a>, <a href="http://www.w3.org/2004/05/14-tag-summary#xmlChunk-44">12 May 2004</a>, <a href="http://www.w3.org/2006/04/18-tagmem-minutes#item09">18 Apr 2006</a>, <a href="http://www.w3.org/2001/tag/2007/02/12-tagmem-minutes#item04">12 Feb 2007</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2004Jan/0013">raised</a> on 12 Jan 2004 by 
						TBL
					, on behalf of <a href="http://www.w3.org/2001/tag/">
						TAG
					</a></dt><dd></dd><dt><a href="http://www.w3.org/2004/02/02-tag-summary#xmlChunk-44">accepted</a> on 2 Feb 2004</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li>
									1 Mar 2004: XML Core WG discussion
									of issue
								</li></ul></dd><dt><a href="http://www.w3.org/2001/tag/2007/03/07-afternoon-minutes#item02">agreed</a> on 7 Mar 2007</dt><dd><p>
							xmlChunk-44 was an attempt to tackle deep
							equals for XML. The
							<a href="http://www.w3.org/2001/tag/2007/03/07-afternoon-minutes#item02">
								TAG now think
							</a>
							we can't do better than XML Functions and
							Operators.
						</p><h5>Acknowledgment cycle</h5><dl><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2007Jul/0039">announced by group  on 12 Jul 2007</a></dt></dl></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>NW</h5><ul><li><a href="http://www.w3.org/2004/02/02-tag-summary#xmlChunk-44">accepted on 2 Feb 2003</a><br /><p>
									Summarize xmlChunk-44, solicit input
									from www-tag.
								</p></li><li><a href="http://www.w3.org/2004/02/02-tag-summary#xmlChunk-44">proposal on 18 Feb 2003</a><br /><p>
									The xmlChunk-44 problem statement
									(resend)
								</p></li><li><a href="http://lists.w3.org/Archives/Member/tag/2004Apr/0017">completed on 13 Apr 2004</a><br /><p>Chair declared closed.</p></li></ul></div><div class="details-action decided"><h5>NW</h5><ul><li><a href="http://www.w3.org/2004/02/02-tag-summary#xmlChunk-44">accepted on 2 Feb 2003</a><br /><p>
									Coordinate joint meeting with XML
									Core, notably around xmlChunk-44.
								</p></li><li><a href="http://lists.w3.org/Archives/Member/tag/2004Feb/0179">proposal on 18 Feb 2003</a><br /><p>
									Tuesday, 4 March
									<a href="http://www.w3.org/2001/tag/2004/02/TAG-Liasons">
										liaison with XML Core
									</a>
									.
								</p></li><li><a href="http://lists.w3.org/Archives/Member/tag/2004Apr/0017">completed on 13 Apr 2004</a><br /><p>Chair declared closed.</p></li></ul></div><div class="details-action decided"><h5>NW</h5><ul><li><a href="http://www.w3.org/2004/05/14-tag-summary#xmlChunk-44">accepted on 12 May 2004</a><br /><p>
									Write up a named equivalence
									function based on today's discussion
									(e.g., based on infoset, augmented
									with xml:lang/xml:base, not
									requiring prefixes, etc.).: Write up
									a named equivalence function based
									on today's discussion (e.g., based
									on infoset, augmented with
									xml:lang/xml:base, not requiring
									prefixes, etc.).
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2004Jun/0026">proposal on 28 Jun 2004</a><br /><p>
									See email for details of proposal.
								</p></li><li><a href="http://www.w3.org/2001/tag/2007/07/16-minutes#item03">dropped on 16 Jul 2007</a><br /><p>Overtaken by closure of issue.</p></li></ul></div><div class="details-action decided"><h5>NW</h5><ul><li><a href="http://www.w3.org/2001/tag/2007/02/12-tagmem-minutes#action02">accepted on 12 Feb 2007</a><br /><p>
									Norm to review draft finding on
									xmlChunk-44 to see whether issue can
									be closed and finding approved.
								</p></li><li><a href="http://www.w3.org/2001/tag/2007/07/16-minutes#item03">dropped on 16 Jul 2007</a><br /><p>Overtaken by closure of issue.</p></li></ul></div><div class="details-action decided"><h5>NW</h5><ul><li><a href="http://www.w3.org/2001/tag/2007/03/07-afternoon-minutes#ActionSummary">accepted on 7 Mar 2007</a><br /><p>
									Norm to mark as abandoned the
									finding on deep equals and announce
									xmlChunk-44 is being closed without
									further action, with reason
								</p></li><li><a href="http://www.w3.org/2001/tag/2007/07/16-minutes#item03">completed on 16 Jul 2007</a><br /><p>
									Details in
									<a href="http://www.w3.org/2001/tag/2007/07/16-agenda">
										agenda
									</a>
									.
								</p></li></ul></div></div></div><div class="issue"><h3><a id="mediaTypeManagement-45" name="mediaTypeManagement-45">mediaTypeManagement-45</a>: 
				What is the appropriate level of granularity of the
				media type mechanism?
			 [<a href="issues.html#mediaTypeManagement-45">link to this issue</a>]</h3><p>
							The TAG raised this issue to discuss issues
							such as paramterization of media type
							strings to provide additional granularity
							for different format versions.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><a href="http://www.ietf.org/rfc/rfc2045.txt">
						RFC 2045
					</a></dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2004/05/14-tag-summary#diwg4">14 May 2004</a>, <a href="http://www.w3.org/2001/tag/2005/10/04-minutes#item03">4 Oct 2005</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://www.w3.org/2004/05/14-tag-summary#diwg4">raised</a> on 14 May 2004 by 
						TBL
					, on behalf of <a href="http://www.w3.org/2001/tag/">
						TAG
					</a></dt><dd></dd><dt><a href="http://www.w3.org/2004/05/14-tag-summary#diwg4">accepted</a> on 14 May 2004</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li>
									See also issue
									<a href="http://www.w3.org/2001/tag/issues?type=1#uriMediaType-9">
										uriMediaType-9
									</a></li><li>
									See also
									<a href="http://www.w3.org/2004/CDF/Group/">
										Compound Document Formats WG
									</a>
									.
								</li></ul></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						CL
					</h5><ul><li><a href="http://www.w3.org/2004/05/14-tag-summary#diwg4">accepted on 14 May 2004</a><br /><p>
									Write draft finding on this issue.
								</p></li><li><a href="http://www.w3.org/2006/10/31-tagmem-minutes#item03">dropped on 31 Oct 2006</a></li></ul></div><div class="details-action decided"><h5>
						VQ
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2005/10/04-minutes#action04">accepted on 4 Oct 2005</a><br /><p>
									check with CDF WG to see how they
									have solved media type issue(s) and
									if they have more details
								</p></li><li><a href="">dropped on 8 Jun 2007</a><br /><p>
									Dropped by chair (overtaken bye
									events)
								</p></li></ul></div></div></div><div class="issue"><h3><a id="xml11Names-46" name="xml11Names-46">xml11Names-46</a>: 
				Impact of changes to XML 1.1 on other XML Specifications
			 [<a href="issues.html#xml11Names-46">link to this issue</a>]</h3><p>
							XML 1.1 makes essentially four changes to
							XML 1.0:
						</p><ul><li>
									It increases the number of
									characters that may legally appear
									in Names.
								</li><li>
									Adds several new characters that may
									appear in text if they are encoded
									as numeric character references (C0
									controls except NUL).
								</li><li>
									Removes several characters so that
									they may not appear in text if they
									are not encoded as numeric character
									references (C1 controls).
								</li><li>Adds as a line-end character.</li></ul><p>
							XML Schema 1.0 normatively refers to XML
							Namespaces 1.0 for the definition of QName
							and XML Namespaces 1.0 normatively refers to
							XML 1.0 for the definition of Name and XML
							1.0 has fewer Name characters than XML 1.1.
						</p><p>
							That means that by a strict interpretation
							of the Recommendations, it is impossible to
							write an XML Schema for a document that uses
							the "new" Name characters. And by extension,
							it is impossible for an XPath expression or
							a protocol document to use XML 1.1.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><a href="http://www.w3.org/TR/xml11">
						XML 1.1
					</a></dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2004/06/07-tag-summary#httpRange-14">7 Jun 2004</a>, <a href="http://www.w3.org/2004/06/28-tag-summary">28 Jun 2004</a>, <a href="http://www.w3.org/2001/tag/2005/10/04-minutes#item04">4 Oct 2005</a>, <a href="http://www.w3.org/2006/01/31-tagmem-minutes#item08">31 Jan 2006</a>, <a href="http://www.w3.org/2001/tag/2006/12/13-morning-minutes#item05">13 Dec 2006</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2004May/0039">raised</a> on 19 May 2004 by 
						Mark Nottingham
					, on behalf of <a href="http://www.w3.org/2000/xp/Group/">
						XML Protocol WG
					</a></dt><dd></dd><dt><a href="http://www.w3.org/2004/06/07-tag-summary#httpRange-14">accepted</a> on 7 Jun 2004</dt><dd></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>NW</h5><ul><li><a href="http://www.w3.org/2004/06/14-tag-summary">accepted on 14 Jun 2004</a><br /><p>
									Forward
									<a href="http://lists.w3.org/Archives/Public/www-tag/2004Jun/0004">
										proposal
									</a>
									to the XML CG.
								</p></li><li><a href="http://www.w3.org/2004/06/28-tag-summary">dependent on 28 Jun 2004</a><br />on 
              <a href="http://www.w3.org/XML/Group/">
								XML CG
							</a></li><li><a href="http://lists.w3.org/Archives/Member/w3c-xml-cg/2006May/0005">completed on 3 May 2006</a><br /><p>
									See section 5.4 of the
									<a href="http://lists.w3.org/Archives/Member/w3c-xml-cg/2006May/0005">
										XML CG minutes
									</a>
									.
								</p></li></ul></div><div class="details-action decided"><h5>NW</h5><ul><li><a href="http://www.w3.org/2001/tag/2005/10/04-minutes#action05">accepted on 4 Oct 2005</a><br /><p>
									check on current status of issue
									xml11Names-46 with XML CG
								</p></li><li><a href="http://www.w3.org/2001/tag/2006/12/13-morning-minutes#action07">dropped on 13 Dec 2006</a></li></ul></div><div class="details-action decided"><h5>
						HT
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/02/07-tagmem-minutes#action01">accepted on 7 Feb 2006</a><br /><p>
									bring us back to xml11Names-46 after
									the XML Schema WG publishes its
									expected Last Call WD.
								</p></li><li><a href="http://www.w3.org/2001/tag/2006/12/13-morning-minutes#action08">completed on 13 Dec 2006</a></li></ul></div><div class="details-action decided"><h5>NW</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/12/13-morning-minutes#action06">accepted on 13 Dec 2006</a><br /><p>
									Find a test case; reminds self to
									check with Henry for the Ice Cream
									example.
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2007Jul/0040">proposal on 12 Jul 2007</a><br /><p>Test case email from Norm</p></li><li><a href="http://www.w3.org/2001/tag/2007/08/20-minutes#item08">completed on 20 Aug 2007</a></li></ul></div></div></div><div class="issue"><h3><a id="endPointRefs-47" name="endPointRefs-47">endPointRefs-47</a>: 
				WS-Addressing SOAP binding &amp; app protocols
			 [<a href="issues.html#endPointRefs-47">link to this issue</a>]</h3><p>
							From the commenters
							<a href="http://lists.w3.org/Archives/Public/www-tag/2005Jan/0000">
								email
							</a>
							:
						</p><p>
							"In a nutshell, it [
							<a href="http://www.w3.org/TR/2004/WD-ws-addr-soap-20041208/">
								WS-Addressing - SOAP Binding
							</a>
							] requires that the URI in the "Address"
							component of a WS-Addressing EPR be
							serialized into a wsa:To SOAP header,
							independent of the underlying protocol. IMO,
							a Web-architecture consistent means of doing
							this would be to serialize it to the
							Request-URI when using SOAP with HTTP, or
							the "RCPT TO:" value when using SOAP with
							SMTP, etc.."
						</p><p>
							The issue has been raised with the relevant
							<a href="http://lists.w3.org/Archives/Public/public-ws-addressing/2004Dec/0119">
								WG
							</a>
							and
							<a href="http://lists.w3.org/Archives/Public/public-ws-addressing/2005Jan/0001">
								declined
							</a>
							.
						</p><p>
							The
							<a href="http://www.w3.org/TR/2005/CR-ws-addr-soap-20050817/">
								WS-Addressing SOAP Binding CR
							</a>
							of 17 Aug 2005 still has this problem.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><a href="http://www.w3.org/TR/2004/WD-ws-addr-soap-20041208/">
						Web Services Addressing - SOAP Binding
					</a></dd><dt>Discussion history</dt><dd><a href="http://lists.w3.org/Archives/Public/www-tag/2005Jan/att-0021/tag-20050124#item10">24 Jan 2005</a>, <a href="http://www.w3.org/2005/03/29-tagmem-minutes#item03">29 Mar 2005</a>, <a href="http://www.w3.org/2005/04/05-tagmem-minutes#item07">5 Apr 2005</a>, <a href="http://www.w3.org/2001/tag/2005/04/19-minutes#item08">19 Apr 2005</a>, <a href="http://www.w3.org/2005/09/22-tagmem-minutes#item04">22 Sep 2005</a>, <a href="http://www.w3.org/2001/tag/2005/10/04-minutes#item02">4 Oct 2005</a>, <a href="http://www.w3.org/2005/10/11-tagmem-minutes#item03">11 Oct 2005</a>, <a href="http://www.w3.org/2001/tag/2005/10/18-minutes#item05">18 Oct 2005</a>, <a href="http://www.w3.org/2005/10/25-tagmem-minutes#item01">25 Oct 2005</a>, <a href="http://www.w3.org/2005/11/01-tagmem-minutes#item09">1 Nov 2005</a>, <a href="http://www.w3.org/2001/tag/2005/11/22-minutes#item04">22 Nov 2005</a>, <a href="http://www.w3.org/2001/tag/2005/12/06-Afternoon-minutes#item05">6 Dec 2005</a>, <a href="http://www.w3.org/2001/tag/2006/01/24-minutes#item03">24 Jan 2006</a>, <a href="http://www.w3.org/2006/03/28-tagmem-minutes#item02">28 Mar 2006</a>, <a href="http://www.w3.org/2001/tag/2006/06/14-minutes#item06">14 Jun 2006</a>, <a href="http://www.w3.org/2006/10/24-tagmem-minutes#item03">24 Oct 2006</a>, <a href="http://www.w3.org/2001/tag/2006/12/11-minutes#item04">11 Dec 2006</a>, <a href="http://www.w3.org/2001/tag/2006/12/12-tagmem-minutes#item02">12 Dec 2006</a>, <a href="http://www.w3.org/2007/01/09-tagmem-minutes#item03">9 Jan 2007</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2005Jan/0000">raised</a> on 3 Jan 2005 by 
						Mark Baker
					</dt><dd></dd><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2005Jan/att-0021/tag-20050124#item10">accepted</a> on 24 Jan 2005</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="http://lists.w3.org/Archives/Public/www-tag/2005Jan/0017">
										decision
									</a>
									by the WS-Addressing WG
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2005Nov/att-0008/eprExample">
										A Worked Example
									</a>
									, by H. Thompson
								</li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2006Oct/0061">
										WS-Transfer and HTTP, re TAG
										Issues whenToUseGet-7 &amp;
										endPointRefs-47
									</a></li></ul></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>SW</h5><ul><li><a href="http://lists.w3.org/Archives/Public/www-tag/2005Jan/att-0021/tag-20050124#item10">accepted on 24 Jan 2005</a><br /><p>
									Inform WS-Addressing WG Chair (
									<a href="mailto:mark.nottingham@bea.com">
										Mark Nottingham
									</a>
									) that we added a new issue and that
									we would like to discuss it.
								</p></li><li><a href="http://lists.w3.org/Archives/Member/tag/2005Jan/0042">completed on 25 Jan 2005</a></li></ul></div><div class="details-action decided"><h5>
						DO
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2005/10/04-minutes#action02">accepted on 4 Oct 2005</a><br /><p>
									draft something indicating the
									issues with EPR and potential
									solutions
								</p></li><li><a href="http://www.w3.org/2001/tag/2006/06/14-minutes#item06">dropped on 14 Jun 2006</a></li></ul></div><div class="details-action decided"><h5>
						VQ
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2005/12/06-Afternoon-minutes#action02">accepted on 6 Dec 2005</a><br /><p>
									invite Mark Baker to future telcon
									to discuss his concern
								</p></li><li><a href="http://www.w3.org/2001/tag/2006/03/28-agenda#Issue">completed on 28 Mar 2006</a></li></ul></div></div></div><div class="issue"><h3><a id="nameSpaceState-48" name="nameSpaceState-48">nameSpaceState-48</a>: Adding terms to a namespace [<a href="issues.html#nameSpaceState-48">link to this issue</a>]</h3><p>
							The question is about the identity of a
							namespace, in particular, the xml:
							namespace. One perspective is that the xml:
							namespace consists of xml:space, xml:lang,
							and xml:base (and no other names) because
							there was a point in time in which those
							where the only three names from that
							namespace that had a defined meaning.
							Another perspective is that the xml:
							namespace consists of all possible local
							names and that only a finite (but flexible)
							number of them are defined at any given
							point in time.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references">XML</dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2005/02/22-tagmem-minutes#item08">22 Feb 2005</a>, <a href="http://www.w3.org/2005/03/08-tagmem-minutes#item02">8 Mar 2005</a>, <a href="http://www.w3.org/2005/09/22-tagmem-minutes#item06">22 Sep 2005</a>, <a href="http://www.w3.org/2001/tag/2005/12/06-Afternoon-minutes#item04">6 Dec 2005</a>, <a href="http://www.w3.org/2001/tag/2005/12/13-tagmem-minutes#item03">13 Dec 2005</a>, <a href="http://www.w3.org/2001/tag/2005/12/20-minutes#item03">20 Dec 2005</a>, <a href="http://www.w3.org/2006/04/18-tagmem-minutes#item08">18 Apr 2006</a>, <a href="http://www.w3.org/2001/tag/2006/04/25-tagmem-minutes#item03">25 Apr 2006</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2005Feb/0015">raised</a> on 9 Feb 2005 by 
						Norman Walsh
					, on behalf of <a href="http://www.w3.org/XML/Core/">
						XML Core WG and XML Coordination Group
					</a></dt><dd></dd><dt><a href="http://www.w3.org/2005/02/22-tagmem-minutes#item08">accepted</a> on 22 Feb 2005</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="http://www.w3.org/2001/tag/doc/namespaceState">
										Draft finding from NW
									</a></li><li><a href="http://www.w3.org/2001/tag/doc/namespaceState">
										Approved finding
									</a></li><li><a href="http://www.w3.org/TR/namespaceState/">
										TR version
									</a>
									of the approved finding
								</li></ul></dd><dt><a href="http://www.w3.org/2001/tag/2006/04/25-tagmem-minutes#action04">agreed</a> on 25 Apr 2006</dt><dd><p>
							Approved TAG finding
							<a href="http://www.w3.org/2001/tag/doc/namespaceState-2006-01-09">
								The Disposition of Names in an XML
								Namespace
							</a>
							.
						</p><h5>Acknowledgment cycle</h5><dl><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2006May/0006">announced by group  on 5 May 2006</a></dt></dl></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>NW</h5><ul><li><a href="http://www.w3.org/2005/02/22-tagmem-minutes#action03">accepted on 22 Feb 2005</a><br /><p>
									NW to announce TAG's acknolwedgement
									of issue nameSpaceState-48
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2005Mar/0030">completed on 9 Mar 2005</a></li></ul></div><div class="details-action decided"><h5>NW</h5><ul><li><a href="http://www.w3.org/2005/02/22-tagmem-minutes#action04">accepted on 22 Feb 2005</a><br /><p>
									NW to work with HT, DO on
									namespaceState-48
								</p></li><li><a href="http://www.w3.org/2001/tag/doc/namespaceState">completed on 13 Sep 2005</a></li></ul></div><div class="details-action decided"><h5>
						TBL
					</h5><ul><li><a href="http://www.w3.org/2005/03/08-tagmem-minutes#action04">accepted on 8 Mar 2005</a><br /><p>
									provide a draft of new namespace
									policy doc (
									<a href="http://www.w3.org/1999/10/nsuri">
										http://www.w3.org/1999/10/nsuri
									</a>
									) and start discussion on www-tag
								</p></li><li><a href="http://www.w3.org/2001/tag/2006/04/25-tagmem-minutes#action03">completed on 25 Apr 2006</a><br /><p>
									New
									<a href="http://www.w3.org/2005/07/13-nsuri">
										namespace policy document
									</a>
									published.
								</p></li></ul></div><div class="details-action decided"><h5>NW</h5><ul><li><a href="http://www.w3.org/2001/tag/2005/12/06-Afternoon-minutes#action01">accepted on 6 Dec 2005</a><br /><p>
									apply changes to nameSpaceState-48
									document and recirculate for
									comments
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2005Dec/0086">completed on 16 Dec 2005</a><br /><p>
									NW has published a
									<a href="http://www.w3.org/2001/tag/doc/namespaceState-2005-12-16">
										revised finding
									</a>
									.
								</p></li></ul></div><div class="details-action decided"><h5>NW</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/01/03-minutes#action01">accepted on 3 Jan 2006</a><br /><p>
									make the changes, publish
									<a href="http://www.w3.org/2001/tag/doc/namespaceState">
										the finding
									</a>
									, and post to www-tag
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2006Jan/0032">completed on 9 Jan 2006</a><br /><p>
									NW has updated and published
									<a href="http://www.w3.org/2001/tag/doc/namespaceState">
										The Disposition of Names in an
										XML Namespace
									</a>
									.
								</p></li></ul></div></div></div><div class="issue"><h3><a id="schemeProtocols-49" name="schemeProtocols-49">schemeProtocols-49</a>: 
				Relationship of URI schemes to protocols and operations
			 [<a href="issues.html#schemeProtocols-49">link to this issue</a>]</h3><p>
							There are many situations in which there
							appeared to be confusion in the Web
							community regarding the architectural
							relationship between URI schemes and network
							protocols.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references">URI</dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2005/05/31-tagmem-minutes#item04">31 May 2005</a>, <a href="http://www.w3.org/2001/tag/2005/06/14-16-minutes#item013">15 Jun 2005</a>, <a href="http://www.w3.org/2005/06/28-tagmem-minutes#item05">28 Jun 2005</a>, <a href="http://www.w3.org/2001/tag/2005/10/04-minutes#item05">4 Oct 2005</a>, <a href="http://www.w3.org/2001/tag/2005/12/05-tagmem-minutes#item06">5 Dec 2005</a>, <a href="http://www.w3.org/2001/tag/2006/09/26-tagmem-minutes#item03">26 Sep 2006</a>, <a href="http://www.w3.org/2001/tag/2007/01/23-tagmem-minutes#item05">23 Jan 2007</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2005Feb/0013">raised</a> on 7 Feb 2005 by 
						Noah Mendelsohn
					</dt><dd></dd><dt><a href="http://www.w3.org/2005/03/08-tagmem-minutes#item02">accepted</a> on 22 Feb 2005</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="http://www.w3.org/2001/tag/doc/SchemeProtocols">
										URI Schemes and Web Protocols
									</a>
									from Noah Mendelsohn
								</li></ul></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						NM
					</h5><ul><li><a href="http://www.w3.org/2005/03/08-tagmem-minutes#action03">accepted on 8 Mar 2005</a><br /><p>
									Noah to send announcment note to
									www-tag to announce
									SchemesProtocols-49 issue and gather
									feedback
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2005Mar/0043">completed on 14 Mar 2005</a></li></ul></div><div class="details-action decided"><h5>
						NM
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2005/08/Aug232005#item10">accepted on 23 Aug 2005</a><br /><p>
									Noah to figure out what to do next
									on SchemesProtocols-49
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2005Nov/0030">completed on 21 Nov 2005</a></li></ul></div><div class="details-action decided"><h5>
						NM
					</h5><ul><li><a href="http://www.w3.org/2005/12/05-tagmem-minutes#action01">accepted on 5 Dec 2005</a><br /><p>
									produce a new version of
									<a href="http://www.w3.org/2001/tag/doc/SchemeProtocols">
										URI Schemes and Web Protocols
									</a>
									. Confirmed
									<a href="http://www.w3.org/2001/tag/2006/09/26-tagmem-minutes#action03">
										26 Sep 2006
									</a>
									.
								</p></li><li><a href="http://www.w3.org/2001/tag/2007/01/23-tagmem-minutes#action04">dropped on 23 Jan 2007</a></li></ul></div></div></div><div class="issue"><h3><a id="URNsAndRegistries-50" name="URNsAndRegistries-50">URNsAndRegistries-50</a>: URIs, URNs, "location independent" naming systems and associated registries for naming on the Web [<a href="issues.html#URNsAndRegistries-50">link to this issue</a>]</h3><p>
							This issue covers a) URIs for namespace
							names b) URNs and other proposed systems for
							"location independent" names c) XML and
							other registries, and perhaps centralized
							vs. decentralized vocabulary tracking.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><ul><li>URI</li><li><a href="http://ietfreport.isoc.org/idref/rfc3688/">
						RFC 3688
					</a></li></ul></dd><dt>Discussion history</dt><dd><a href="http://lists.w3.org/Archives/Public/www-tag/2005Mar/att-0056/March152005#item07">15 Mar 2005</a>, <a href="http://www.w3.org/2005/03/29-tagmem-minutes#item09">22 Mar 2005</a>, <a href="http://www.w3.org/2005/03/22-tagmem-minutes#item05">29 Mar 2005</a>, <a href="http://www.w3.org/2005/04/05-tagmem-minutes#item05">5 Apr 2005</a>, <a href="http://www.w3.org/2001/tag/2005/04/26-minutes">26 Apr 2005</a>, <a href="http://www.w3.org/2005/05/10-tagmem-minutes#item07">10 May 2005</a>, <a href="http://www.w3.org/2001/tag/2005/10/04-minutes#item06">4 Oct 2005</a>, <a href="http://www.w3.org/2005/10/11-tagmem-minutes#item04">11 Oct 2005</a>, <a href="http://www.w3.org/2001/tag/2005/12/06-Afternoon-minutes#item03">6 Dec 2005</a>, <a href="http://www.w3.org/2006/04/18-tagmem-minutes#item10">18 Apr 2006</a>, <a href="http://www.w3.org/2001/tag/2006/06/06-tagmem-minutes#item07">6 Jun 2006</a>, <a href="http://www.w3.org/2001/tag/2006/06/12-tagmem-minutes#item06">12 Jun 2006</a>, <a href="http://www.w3.org/2001/tag/2006/06/13-morning-minutes#item02">13 Jun 2006</a>, <a href="http://www.w3.org/2006/07/25-tagmem-minutes#item04">25 Jul 2006</a>, <a href="http://www.w3.org/2001/tag/2006/08/15-minutes#item03">15 Aug 2006</a>, <a href="http://www.w3.org/2006/08/29-tagmem-minutes#item03">29 Aug 2006</a>, <a href="http://www.w3.org/2001/tag/2006/09/26-tagmem-minutes#item02">26 Sep 2006</a>, <a href="http://www.w3.org/2001/tag/2006/10/05-afternoon-minutes#item02">5 Oct 2006</a>, <a href="http://www.w3.org/2001/tag/2007/01/23-tagmem-minutes#item04">23 Jan 2007</a>, <a href="http://www.w3.org/2001/tag/2007/04/30-minutes#item04">30 Apr 2007</a>, <a href="http://www.w3.org/2001/tag/2007/05/14-minutes#item09">14 May 2007</a>, <a href="http://www.w3.org/2001/tag/2007/05/30-minutes#item03">30 May 2007</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2005Mar/0046">raised</a> on 15 Mar 2005 by 
						Henry Thompson
					</dt><dd></dd><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2005Mar/att-0056/March152005#item07">accepted</a> on 15 Mar 2005</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li>
									29 Mar 2005:
									<a href="http://www.w3.org/2001/tag/doc/URNsAndRegistries-50.xml">
										Draft finding
									</a></li></ul></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						HT
					</h5><ul><li><a href="http://www.w3.org/2005/03/15-tagmem-minutes#action07">accepted on 15 Mar 2005</a><br /><p>
									Note to www-tag to announce
									URNsAndRegistries-50
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2005Mar/0081">completed on 21 Mar 2005</a></li></ul></div><div class="details-action decided"><h5>
						HT
					</h5><ul><li><a href="http://lists.w3.org/Archives/Public/www-tag/2005Mar/att-0056/March152005.html#action03">accepted on 15 Mar 2005</a><br /><p>
									Henry and David to draft initial
									finding on URNsAndRegistries-50
								</p></li><li><a href="http://www.w3.org/2001/tag/doc/URNsAndRegistries-50.xml">completed on 29 Mar 2005</a></li></ul></div><div class="details-action decided"><h5>
						HT
					</h5><ul><li><a href="http://www.w3.org/2006/04/18-tagmem-minutes#item10">accepted on 18 Apr 2006</a><br /><p>
									Henry and David to update draft
									finding
									<a href="http://www.w3.org/2001/tag/doc/URNsAndRegistries-50.xml">
										URNs, Namespaces and Registries
									</a>
									. Confirmed
									<a href="http://www.w3.org/2001/tag/2006/09/26-tagmem-minutes#action02">
										26 Sep 2006
									</a>
									,
									<a href="http://www.w3.org/2001/tag/2006/10/05-afternoon-minutes#PENDING5">
										5 Oct 2006
									</a>
									,
									<a href="http://www.w3.org/2001/tag/2007/01/23-tagmem-minutes#action03">
										23 Jan 2007
									</a>
									.
								</p></li><li><a href="http://lists.w3.org/Archives/Member/tag/2007Jun/0029.html">completed on 18 Jun 2007</a><br /><p>
									DO done and HT overtaken by more
									recent actions ie.
									<a href="http://www.w3.org/2001/tag/2007/06/11-minutes#action02">
										action to revise
									</a>
									from May 2007 F2F.
								</p></li></ul></div><div class="details-action decided"><h5>
						DC
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/09/26-tagmem-minutes#action01">accepted on 26 Sep 2006</a><br /><p>
									DanC to find timbl's draft, give it
									to Ivan Herman in preparation for
									HCLSIG meeting in Amsterdam.
								</p></li><li><a href="http://www.w3.org/2001/tag/2006/10/05-afternoon-minutes#PENDING6">completed on 5 Oct 2006</a></li></ul></div><div class="details-action decided"><h5>
						DC
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2007/01/23-tagmem-minutes#action02">accepted on 23 Jan 2007</a><br /><p>
									DanC to look for an example of
									commercial motivation for
									alternatives to DNS.
								</p></li><li><a href="http://www.w3.org/2001/tag/2007/04/30-minutes.html#item04">completed on 30 Apr 2007</a></li></ul></div><div class="details-action"><h5>
						DO
					</h5><ul><li><a href="">accepted on 30 Apr 2007</a><br /><p>
									DO to explore the space of external
									registries and to post to the tag
									member list.
								</p></li><li><a href="http://lists.w3.org/Archives/Member/tag/2007May/0008.html">proposal on 1 May 2007</a><br /><p>
									"XRI Business environment"
									<a href="http://lists.w3.org/Archives/Member/tag/2007May/0008.html">
										email
									</a>
									from David.
								</p></li><li><a href="http://www.w3.org/2001/tag/group/track/actions/32">proposal on 24 Aug 2007</a><br /><p>
									Tracking transferred to tracker
									<a href="http://www.w3.org/2001/tag/group/track/actions/32">
										ACTION-32
									</a></p></li></ul></div><div class="details-action"><h5>
						HT
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2007/06/11-minutes#action02">accepted on 11 Jun 2007</a><br /><p>
									Henry to revise URNsAndRegistries-50
									finding in response to F2F
									discussion.
								</p></li><li><a href="http://www.w3.org/2001/tag/group/track/actions/33">proposal on 24 Aug 2007</a><br /><p>
									Tracking transferred to tracker
									<a href="http://www.w3.org/2001/tag/group/track/actions/33">
										ACTION-33
									</a></p></li></ul></div></div></div><div class="issue"><h3><a id="standardizedFieldValues-51" name="standardizedFieldValues-51">standardizedFieldValues-51</a>: 
				Squatting on link relationship names, x-tokens,
				registries, and URI-based extensibility
			 [<a href="issues.html#standardizedFieldValues-51">link to this issue</a>]</h3><p>
							Since short strings are scarce resources
							shared by the global community, fair and
							open processes should be used to manage
							them. A pattern that I'd like to see more of
							is
						</p><ol><li>start with a URI for a new term,</li><li>
									if it picks up steam, introduce a
									synonym that is a short string thru
									a fair/open process.
								</li></ol><p>Lately I'm seeing quite the opposite.</p><p>Nearby issues:</p><ul><li><a href="#uriMediaType-9">
										uriMediaType-9
									</a></li><li><a href="#URNsAndRegistries-50">
										URNsAndRegistries-50
									</a></li><li><a href="#XMLVersioning-41">
										XMLVersioning-41
									</a></li><li><a href="#nameSpaceState-48">
										nameSpaceState-48
									</a></li></ul><dl><dt class="references">Request
	      concerning</dt><dd class="references"><ul><li>URI</li><li>namespace</li></ul></dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2005/05/10-tagmem-minutes#item08">10 May 2005</a>, <a href="http://www.w3.org/2006/01/31-tagmem-minutes#item09">31 Jan 2006</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2005Apr/0033">raised</a> on 6 Apr 2005 by 
						Dan Connolly
					</dt><dd></dd><dt><a href="http://www.w3.org/2001/tag/2005/04/19-minutes#item04">accepted</a> on 19 Apr 2005</dt><dd></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						DC
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2005/04/19-minutes#action01">accepted on 19 Apr 2005</a><br /><p>
									DanC to introduce new issue
									standardizedFieldValues-51
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2005May/0032">completed on 11 May 2005</a></li></ul></div><div class="details-action decided"><h5>
						DC
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2005/09/06-minutes#action02">accepted on 6 Sep 2005</a><br /><p>
									write an update on issue
									standardizedFieldValues-51 and
									microformat
								</p></li><li><a href="http://www.w3.org/2006/01/31-tagmem-minutes#item09">dropped on 31 Jan 2006</a></li></ul></div></div></div><div class="issue"><h3><a id="passwordsInTheClear-52" name="passwordsInTheClear-52">passwordsInTheClear-52</a>: Sending passwords in the clear [<a href="issues.html#passwordsInTheClear-52">link to this issue</a>]</h3><p>
							Many applications send passwords in the
							clear. This raises obvious security issues.
							The TAG should recommend not to send
							passwords in the clear and propose
							alternatives.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><ul><li>Security</li><li>Authentication</li></ul></dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2001/tag/2005/06/14-16-minutes#item025">15 Jun 2005</a>, <a href="http://www.w3.org/2001/tag/2005/09/20PM-minutes#item02">20 Sep 2005</a>, <a href="http://www.w3.org/2006/04/18-tagmem-minutes#item06">18 Apr 2006</a>, <a href="http://www.w3.org/2001/tag/2006/06/13-morning-minutes#item04">13 Jun 2006</a>, <a href="http://www.w3.org/2001/tag/2006/09/26-tagmem-minutes#item04">26 Sep 2006</a>, <a href="http://www.w3.org/2001/tag/2006/10/04-tagmem-minutes#item04">4 Oct 2006</a>, <a href="http://lists.w3.org/Archives/Public/www-tag/2006Oct/att-0053/10-tagmem-minutes#item02">10 Oct 2006</a>, <a href="http://www.w3.org/2006/11/21-tagmem-minutes#item02">21 Nov 2006</a>, <a href="http://www.w3.org/2001/tag/2006/12/11-minutes#item05">11 Dec 2006</a>, <a href="http://www.w3.org/2007/01/09-tagmem-minutes#item04">9 Jan 2007</a>, <a href="http://www.w3.org/2001/tag/2007/01/23-tagmem-minutes#item03">23 Jan 2007</a>, <a href="http://www.w3.org/2001/tag/2007/06/25-minutes#item03">25 Jun 2007</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://www.w3.org/2006/04/18-tagmem-minutes#item06">raised</a> on 18 Apr 2006 by 
						Dan Connolly
					</dt><dd></dd><dt><a href="http://www.w3.org/2006/04/18-tagmem-minutes#item06">accepted</a> on 18 Apr 2006</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li>
									Discussions at
									<a href="http://www.w3.org/2001/tag/2005/09/20PM-minutes#item02">
										Sept. 2005 TAG f2f
									</a></li><li><a href="http://www.w3.org/2005/Security/usability-ws/">
										W3C Workshop on Transparency and
										Usability of Web Authentication
									</a></li><li><a href="http://lists.w3.org/Archives/Public/public-usable-authentication/">
										public-usable-authentication
									</a>
									mailing list
								</li><li>
									Draft finding
									<a href="http://www.w3.org/2001/tag/doc/passwordsInTheClear-52">
										Passwords in the Clear
									</a></li></ul></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>ER</h5><ul><li><a href="http://www.w3.org/2006/04/18-tagmem-minutes#action01">accepted on 18 Apr 2006</a><br /><p>
									Ed to communicate new issue and
									produce first draft finding.
									Reconfirmed
									<a href="http://www.w3.org/2001/tag/2006/07/18-minutes#action03">
										18 Jul 2006
									</a>
									: publish "No passwords in the
									clear" by Aug 8th 2006. Confirmed
									<a href="http://www.w3.org/2001/tag/2006/09/26-tagmem-minutes#action04">
										26 Sep 2006
									</a>
									.
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2006Oct/0003">completed on 2 Oct 2006</a></li></ul></div><div class="details-action decided"><h5>
						VQ
					</h5><ul><li><a href="http://www.w3.org/2006/04/18-tagmem-minutes#action02">accepted on 18 Apr 2006</a><br /><p>
									Vincent to open the issue on the
									issues list
								</p></li><li><a href="#passwordsInTheClear-52">completed on 19 Apr 2006</a></li></ul></div><div class="details-action decided"><h5>ER</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/10/04-tagmem-minutes#action06">accepted on 18 Apr 2006</a><br /><p>
									revise "passwords in the clear" in
									light of Vancouver discussion.
								</p></li><li><a href="http://www.w3.org/2001/tag/doc/passwordsInTheClear-52-20061009">completed on 9 Oct 2006</a></li></ul></div><div class="details-action decided"><h5>ER</h5><ul><li><a href="http://lists.w3.org/Archives/Public/www-tag/2006Oct/att-0053/10-tagmem-minutes#action01">accepted on 10 Oct 2006</a><br /><p>
									publish update in one week for
									discussion in two weeks 31st Oct 06.
								</p></li><li><a href="http://www.w3.org/2001/tag/doc/passwordsInTheClear-52-20061113">completed on 13 Nov 2006</a></li></ul></div><div class="details-action decided"><h5>ER</h5><ul><li><a href="http://www.w3.org/2006/11/21-tagmem-minutes#action01">accepted on 21 Nov 2006</a><br /><p>
									Produce a new version with these
									changes.
								</p></li><li><a href="http://www.w3.org/2001/tag/doc/passwordsInTheClear-52-20061211">completed on 11 Dec 2006</a></li></ul></div><div class="details-action decided"><h5>ER</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/12/11-minutes#action03">accepted on 11 Dec 2006</a><br /><p>
									Alert Web Security Context Working
									Group (chair Mary Ellen Zurko) to
									content of passords in clear draft,
									to negotiate a review by them, and
									to the fact that we are working
									toward publication.
								</p></li><li><a href="http://lists.w3.org/Archives/Member/tag/2007Jan/0001">completed on 2 Jan 2007</a></li></ul></div><div class="details-action decided"><h5>
						HT
					</h5><ul><li><a href="http://www.w3.org/2007/01/09-tagmem-minutes#action01">accepted on 9 Jan 2007</a><br /><p>
									Send email about onsubmit hooking
									via javascript and its impact on
									PWintheclear to www-tag.
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2007Jan/0021">completed on 23 Jan 2007</a></li></ul></div><div class="details-action decided"><h5>SW</h5><ul><li><a href="http://www.w3.org/2001/tag/2007/06/25-minutes#action01">accepted on 25 Jun 2007</a><br /><p>
									Stuart to summarize discussion to
									MEZ and make plans for further
									progress.
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2007Jun/0130">completed on 27 Jun 2007</a></li></ul></div></div></div><div class="issue"><h3><a id="genericResources-53" name="genericResources-53">genericResources-53</a>: Generic resources [<a href="issues.html#genericResources-53">link to this issue</a>]</h3><p>
							A generic resource is a conceptual resource
							which may stand for something which has
							different versions over time, different
							translations, and/or different content-type
							representations. How should one indicate the
							relationship between these?
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references">Web resources</dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2006/05/09-tagmem-minutes#item04">9 May 2006</a>, <a href="http://www.w3.org/2006/05/30-tagmem-minutes#item04">30 May 2006</a>, <a href="http://www.w3.org/2001/tag/2006/06/12-tagmem-minutes#item03">12 Jun 2006</a>, <a href="http://www.w3.org/2001/tag/2006/07/18-minutes#item04">18 Jul 2006</a>, <a href="http://www.w3.org/2006/08/29-tagmem-minutes#item02">29 Aug 2006</a>, <a href="http://www.w3.org/2001/tag/2006/09/19-minutes#item03">19 Sep 2006</a>, <a href="http://www.w3.org/2001/tag/2006/10/04-tagmem-minutes#item03">4 Oct 2006</a>, <a href="http://www.w3.org/2006/10/31-tagmem-minutes#item01">31 Oct 2006</a>, <a href="http://www.w3.org/2001/tag/2006/11/07-minutes#item05">7 Nov 2006</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Member/tag/2006May/0011">raised</a> on 4 May 2006 by 
						T. V. Raman
					</dt><dd></dd><dt><a href="http://www.w3.org/2006/05/30-tagmem-minutes#item04">accepted</a> on 30 May 2006</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="http://www.w3.org/DesignIssues/Generic">
										Generic Resources
									</a>
									in Design Issues
								</li><li><a href="http://www.w3.org/2001/tag/doc/alternatives-discovery">
										On Linking Alternative Formats
										To Enable Discovery And
										Publishing
									</a></li></ul></dd><dt><a href="http://www.w3.org/2006/10/31-tagmem-minutes#item01">agreed</a> on 31 Oct 2006</dt><dd><p>
							See TAG finding
							<a href="http://www.w3.org/2001/tag/doc/alternatives-discovery">
								On Linking Alternative Representations
								To Enable Discovery And Publishing
							</a>
							.
						</p><h5>Acknowledgment cycle</h5><dl><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2006Nov/0003">announced by group  on 31 Oct 2006</a></dt></dl></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						TVR
					</h5><ul><li><a href="http://www.w3.org/2006/05/09-tagmem-minutes#item04">accepted on 9 May 2006</a><br /><p>
									Draft a rough finding on Single URI,
									Multiple content for review at the
									June f2f.
								</p></li><li><a href="http://lists.w3.org/Archives/Member/tag/2006Jun/0003">completed on 2 Jun 2006</a></li></ul></div><div class="details-action decided"><h5>
						TVR
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/06/12-tagmem-minutes#action01">accepted on 12 Jun 2006</a><br /><p>
									Revise genericResources draft,
									incorporating
									resource/representation, complete
									2.4.x story better, emphasize
									discoverability, incorporate DO's
									comments, attempt best practice
									draft 3.
								</p></li><li><a href="http://www.w3.org/2001/tag/doc/alternatives-discovery-20060620">completed on 20 Jun 2006</a></li></ul></div><div class="details-action decided"><h5>
						TVR
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/07/18-minutes#action01">accepted on 18 Jul 2006</a><br /><p>
									Publish new version of Generic
									Resources by Aug 8th 2006
								</p></li><li><a href="http://www.w3.org/2001/tag/doc/alternatives-discovery">completed on 1 Aug 2006</a></li></ul></div><div class="details-action decided"><h5>
						TVR
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/07/18-minutes#action01">accepted on 29 Aug 2006</a><br /><p>
									Produce a new revision of
									generic-Resources-53 by 15 Sep 2006
								</p></li><li><a href="http://www.w3.org/2001/tag/doc/alternatives-discovery-20060915">completed on 15 Sep 2006</a></li></ul></div><div class="details-action decided"><h5>
						TVR
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/09/19-minutes#action01">accepted on 19 Sep 2006</a><br /><p>
									Produce proposed final
									genericResources draft for approval
									at Vancouver F2F
								</p></li><li><a href="http://www.w3.org/2001/tag/2006/10/04-tagmem-minutes#action05">completed on 4 Oct 2006</a></li></ul></div><div class="details-action decided"><h5>
						TVR
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2006/10/04-tagmem-minutes#action04">accepted on 4 Oct 2006</a><br /><p>
									Update Abstract of genericResource
									draft, add item about search,
									address the rel='generic' question,
									deal with the media type issue as
									discussed in Vancouver.
								</p></li><li><a href="http://www.w3.org/2006/10/31-tagmem-minutes#item01">completed on 31 Oct 2006</a></li></ul></div></div></div><div class="issue"><h3><a id="TagSoupIntegration-54" name="TagSoupIntegration-54">TagSoupIntegration-54</a>: Tag soup integration [<a href="issues.html#TagSoupIntegration-54">link to this issue</a>]</h3><p>
							Is the indefinite persistence of 'tag soup'
							HTML consistent with a sound architecture
							for the Web? If so, what changes, if any, to
							fundamental Web technologies are necessary
							to integrate 'tag soup' with SGML-valid HTML
							and well-formed XML?
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references">Web resources</dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2006/10/24-tagmem-minutes#item04">24 Oct 2006</a>, <a href="http://www.w3.org/2006/10/31-tagmem-minutes#item02">31 Oct 2006</a>, <a href="http://www.w3.org/2001/tag/2006/11/07-minutes#item08">7 Nov 2006</a>, <a href="http://www.w3.org/2001/tag/2006/12/11-minutes#item09">11 Dec 2006</a>, <a href="http://www.w3.org/2001/tag/2006/12/12-tagmem-minutes#item03">12 Dec 2006</a>, <a href="http://www.w3.org/mid/17863.30606.404312.106814@retriever.corp.google.com">5 Feb 2007</a>, <a href="http://www.w3.org/2001/tag/2007/03/07-morning-minutes#item02">7 Mar 2007</a>, <a href="http://www.w3.org/2001/tag/2007/03/07-afternoon-minutes#item01">7 Mar 2007</a>, <a href="http://www.w3.org/2007/03/19-tagmem-minutes#item04">19 Mar 2007</a>, <a href="http://www.w3.org/2001/tag/2007/03/26-minutes#item04">26 Mar 2007</a>, <a href="http://www.w3.org/2001/tag/2007/04/16-minutes#item02">16 Apr 2007</a>, <a href="http://www.w3.org/2001/tag/2007/04/23-minutes#item02">23 Apr 2007</a>, <a href="http://www.w3.org/2001/tag/2007/05/31-tagmem-minutes#item05">31 May 2007</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://www.w3.org/2006/10/17-tagmem-minutes#item09">raised</a> on 17 Oct 2006 by TAG</dt><dd></dd><dt><a href="http://www.w3.org/2006/10/24-tagmem-minutes#resolution">accepted</a> on 24 Oct 2006</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="http://lists.w3.org/Archives/Public/www-tag/2006Oct/0062">
										Description of new TAG issue
									</a></li></ul></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						HT
					</h5><ul><li><a href="http://www.w3.org/2006/10/24-tagmem-minutes#action01">accepted on 24 Oct 2006</a><br /><p>
									Propose description of
									TagSoupIntegration-54
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2006Oct/0062">completed on 24 Oct 2006</a></li></ul></div><div class="details-action decided"><h5>
						TVR
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2007/03/07-afternoon-minutes#ActionSummary">accepted on 7 Mar 2007</a><br /><p>
									T.V. Raman to draft initial
									discussion material on tag soup for
									discussion on 26 March, draft on the
									19th or so.
								</p></li><li><a href="http://www.w3.org/2001/tag/doc/tag-soup-integration">proposal on 20 Aug 2007</a><br /><p>
									Wroking
									<a href="http://www.w3.org/2001/tag/doc/tag-soup-integration">
										document
									</a>
									from Boston F2F.
								</p></li><li><a href="http://www.w3.org/2001/tag/2007/08/20-minutes#item09">completed on 20 Aug 2007</a></li></ul></div></div></div><div class="issue"><h3><a id="utf7Encoding-55" name="utf7Encoding-55">utf7Encoding-55</a>: Security issues with incorrect metadata [<a href="issues.html#utf7Encoding-55">link to this issue</a>]</h3><p>
							Security concerns with browsers sniffing
							unlabelled UTF7 encoding
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><ul><li>Security</li><li>Metadata</li></ul></dd><dt>Discussion history</dt><dd><a href="http://www.w3.org/2001/tag/2007/01/02-minutes#item03">2 Jan 2007</a>, <a href="http://www.w3.org/2007/01/09-tagmem-minutes#item02">9 Jan 2007</a>, <a href="http://www.w3.org/2001/tag/2007/02/12-tagmem-minutes#item03">12 Feb 2007</a></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2006Dec/0029">raised</a> on 14 Dec 2006 by 
						Roy Fielding
					</dt><dd></dd><dt><a href="http://www.w3.org/2001/tag/2007/01/02-minutes#item03">accepted</a> on 2 Jan 2007</dt><dd><h5>Background, proposals, threads, notes</h5><ul><li><a href="http://archives.neohapsis.com/archives/fulldisclosure/2006-10/0296">
										A description of the problem
									</a></li><li>
									See also
									<a href="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-5442">
										CVE-2006-5442
									</a></li></ul></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						VQ
					</h5><ul><li><a href="http://www.w3.org/2001/tag/2007/01/02-minutes#action03">accepted on 2 Jan 2007</a><br /><p>
									Create issue in list and announce
									it.
								</p></li><li><a href="http://lists.w3.org/Archives/Public/www-tag/2007Jan/0006">completed on 4 Jan 2007</a></li></ul></div></div></div><div class="issue"><h3><a id="abbreviatedURIs-56" name="abbreviatedURIs-56">abbreviatedURIs-56</a>: Abbreviating URIs in Web Languages [<a href="issues.html#abbreviatedURIs-56">link to this issue</a>]</h3><p>
							Do the expected benefits of
							<a href="http://www.w3.org/TR/curie/">
								CURIEs
							</a>
							outweigh the potential costs in introducing
							a
							<em>third</em>
							syntax for identifiers into the languages of
							the Web?
						</p><p>
							This issue continues a thread of discussion
							that originated under
							<a href="#ultimateQuestion-42">
								ultimateQuestion-42
							</a>
							.
						</p><dl><dt class="references">Request
	      concerning</dt><dd class="references"><ul><li><a href="http://www.w3.org/TR/2007/WD-curie-20070307/">
						CURIE WD 7th March 2007
					</a></li><li>
					Henry Thompson's
					<a href="http://lists.w3.org/Archives/Public/www-tag/2007Mar/0037">
						email
					</a>
					framing the issue.
				</li></ul></dd></dl><h4>Transition history</h4><dl class="transitions"><dt><a href="http://lists.w3.org/Archives/Public/www-tag/2007Mar/0037">raised</a> on 30 Mar 2007 by 
						TAG
					</dt><dd></dd><dt><a href="http://www.w3.org/2007/04/02-tagmem-minutes#item01">accepted</a> on 2 Apr 2007</dt><dd></dd></dl><h4>Action history</h4><div class="action-history"><div class="details-action decided"><h5>
						DC
					</h5><ul><li><a href="http://www.w3.org/2007/04/02-tagmem-minutes#action01">accepted on 2 Apr 2007</a><br /><p>
									DC to respond to
									<a href="http://lists.w3.org/Archives/Public/www-tag/2007Mar/0037">
										http://lists.w3.org/Archives/Public/www-tag/2007Mar/0037
									</a>
									with SPARQL QNames and other
									details.
								</p></li><li><a href="">completed on 2 Apr 2007</a><br /><p>Transferred to Stuart</p></li></ul></div><div class="details-action"><h5>SW</h5><ul><li><a href="http://www.w3.org/2007/04/02-tagmem-minutes#item01">accepted on 2 Apr 2007</a><br /><p>
									Look at the difference between QNAME
									in XML and SPARQL
								</p><p>
									[Aside theses are the closest
									references the chair was able to
									find to the transfer of this action
									item]
								</p></li><li><a href="http://www.w3.org/2001/tag/group/track/actions/34">proposal on 24 Aug 2007</a><br /><p>
									Tracking transferred to tracker
									<a href="http://www.w3.org/2001/tag/group/track/actions/34">
										ACTION-34
									</a></p></li></ul></div></div></div></div><hr /><address><small>Maintained by <a href="http://www.w3.org/2001/tag">W3C Technical Architecture Group</a>.</small></address><p>Last update: $Date: 2011/08/19 20:30:05 $</p><hr /><p>This page was generated as part of the
<a href="http://www.w3.org/2003/12/exit/">Extensible Issue
Tracking System (ExIT)</a></p><p class="copyright"><a rel="Copyright" href="/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
2003, 2004
<a href="/"><acronym title="World Wide Web Consortium">W3C</acronym></a><sup>®</sup> (<a href="http://www.lcs.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="/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>, <a rel="Copyright" href="/Consortium/Legal/copyright-documents">document
use</a> and <a rel="Copyright" href="/Consortium/Legal/copyright-software">software licensing</a>
rules apply. Your interactions with this site are in accordance with
our <a href="/Consortium/Legal/privacy-statement#Public">public</a> and
<a href="/Consortium/Legal/privacy-statement#Members">Member</a>
privacy statements.</p></body></html>