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
|
<!-- ============================================================= -->
<!-- MODULE: Common (Shared) Elements Module -->
<!-- VERSION: 2.0 -->
<!-- DATE: August 2004 -->
<!-- -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- PUBLIC DOCUMENT TYPE DEFINITION -->
<!-- TYPICAL INVOCATION -->
<!--
"-//NLM//DTD Archiving and Interchange DTD Suite Common (Shared) Elements Module v2.0 20040830//EN"
Delivered as file "common.ent" -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- SYSTEM: Archiving and Interchange DTD Suite -->
<!-- -->
<!-- PURPOSE: Defines the common parameter entities, calls the -->
<!-- shared modules (such as special characters and -->
<!-- notations) and provides declarations for elements -->
<!-- that do not properly fit into one class, since -->
<!-- they can be used at more than one structural level-->
<!-- -->
<!-- CONTAINS: 1) Default classes for elements defined in this -->
<!-- module. May be overridden by values in the -->
<!-- DTD's Customization Module -->
<!-- 2) Parameter Entities for attribute values -->
<!-- 3) Parameter Entities for content models -->
<!-- 4) Parameter Entities for attribute lists -->
<!-- 5) Elements used in many modules/classes -->
<!-- - Address elements -->
<!-- - Date elements -->
<!-- - Personal name elements -->
<!-- - Common metadata elements (shared by both -->
<!-- article metadata and bibliographic -->
<!-- reference metadata -->
<!-- -->
<!-- MODULES REQUIRED: -->
<!-- 1) Standard XML Special Characters Module -->
<!-- (%xmlspecchars.ent;) -->
<!-- 2) Custom XML Special Characters (%chars.ent;) -->
<!-- 3) Notation Declarations (%notat.ent;) -->
<!-- -->
<!-- CREATED FOR: -->
<!-- Digital archives and publishers who wish to -->
<!-- create a custom XML DTD for original markup of -->
<!-- journal literature, books, and related material, -->
<!-- or for archiving and transferring such material -->
<!-- between archives. -->
<!-- -->
<!-- This DTD is in the public domain. An organization -->
<!-- that wishes to create its own DTD from the suite -->
<!-- may do so without permission from NLM. -->
<!-- -->
<!-- The suite has been set up to be extended using a -->
<!-- new DTD file and a new DTD-specific customization -->
<!-- module to redefine the many Parameter Entities. -->
<!-- Do not modify the suite directly or redistribute -->
<!-- modified versions of the suite. -->
<!-- -->
<!-- In the interest of maintaining consistency and -->
<!-- clarity for potential users, NLM requests: -->
<!-- -->
<!-- 1. If you create a DTD from the Archiving and -->
<!-- Interchange DTD Suite and intend to stay -->
<!-- compatible with the suite, then please include -->
<!-- the following statement as a comment in all of -->
<!-- your DTD modules: -->
<!-- "Created from, and fully compatible with, -->
<!-- the Archiving and Interchange DTD Suite." -->
<!-- -->
<!-- 2. If you alter one or more modules of the suite, -->
<!-- then please rename your version and all its -->
<!-- modules to avoid any confusion with the -->
<!-- original suite. Also, please include the -->
<!-- following statement as a comment in all your -->
<!-- DTD modules: -->
<!-- "Based in part on, but not fully compatible -->
<!-- with, the Archiving and Interchange DTD -->
<!-- Suite." -->
<!-- -->
<!-- Suggestions for refinements and enhancements to -->
<!-- the DTD suite should be sent in email to: -->
<!-- archive-dtd@ncbi.nlm.nih.gov -->
<!-- -->
<!-- ORIGINAL CREATION DATE: -->
<!-- December 2002 -->
<!-- -->
<!-- CREATED BY: Jeff Beck (NCBI) -->
<!-- Deborah Lapeyre (Mulberry Technologies, Inc.) -->
<!-- Bruce Rosenblum (Inera Inc.) -->
<!-- -->
<!-- NLM thanks the Harvard University Libraries, both -->
<!-- for proposing that a draft archiving NLM DTD for -->
<!-- life sciences journals be extended to accommodate -->
<!-- journals in all disciplines and for sponsoring -->
<!-- Bruce Rosenblum's collaboration with other DTD -->
<!-- authors in completing Version 1.0. The Andrew W. -->
<!-- Mellon Foundation provided support for these -->
<!-- important contributions. -->
<!-- -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- DTD VERSION/CHANGE HISTORY -->
<!-- ============================================================= -->
<!--
=============================================================
Version Reason/Occasion (who) vx.x (yyyy-mm-dd)
=============================================================
Version 2.0 (DAL/BTU) v2.0 (2004-08-30)
Major requirement changes led to the new release, producing
DTD version "2.0":
a) The splitting of the Archival and Interchange Tag Set
DTDs into three DTDs from two: an authoring DTD, an
archive regularization and interchange DTD (the
current Blue Publishing DTD), and a preservationist
archive DTD (the current Green Archiving and Interchange
DTD).
b) AIT Working Group suggestions from the June 04 meeting
and June/July 2004 followup discussions
c) Suite remodularization to meet new (and newly articulated)
modularization requirements
d) New or renamed classes and mixes to make modifications
easier and more consistent
29. NEW ELEMENT <x> GENERATED TEXT AND PUNCTUATION
Added a container element to hold punctuation or other
generated text, typically when 1) an archive decides not
to have any text generated and thus to pre-generate such
things as commas or semicolons between keywords or 2)
when an archive receives text with <x> tags embedded and
wishes to retain them.
28. PUBLISHER - Moved element here from %journalmeta.ent;
module since Book DTD also needed it and was not including
that module.
27. PAGE ELEMENT ATTRIBUTES
a. Made an Parameter Entity for:
- %fpage-atts;
- %elocation-id-atts;
b. Gave %elocation-id-atts" the attribute "seq"
26. PUB ID TYPES - Added the new attribute values to the
Parameter Entity %pub-id-types;, which is used on <article>
and other elements. New values: pmcid and art-access-id
25. CUSTOM METADATA - Added the new <custom-meta> element, its
components, and its wrapper. This element is used to insert
name/value pairs for metadata elements that are in source
material but were never envisioned by this DTD. Allowed this
element at the end of <article-meta>.
24. DATES
a. Made a new Parameter Entity %string-date-elements; to
hold all the elements that may be mixed with #PCDATA
inside a <string-date>
b. Also used %date-parts.class; and %x.class; in
the new PE %string-date-elements;
23. COMPLETE MODELS WHEN OVER-RIDING A MODEL
(for all Parameter Entities suffixed "-model")
### Customization Alert ###
Made all the model over-rides consistent. Some included
the outer parentheses, some did not. They all do now,
as this is the most flexible system, allowing for
#PCDATA, mixed, or element content. (This is in direct
contrast to the "-element" suffixed models, which are
designed to prohibit element content and permit only
#PCDATA or mixed content.) Added parentheses to Parameter
Entity and removed them from the Element Declaration.
- %custom-meta-model;
- %custom-meta-wrap-model;
- %def-model;
- %sec-model;
- %sec-opt-title-model;
- Removed parentheses from <notes>, <ack>, <address>, <date>
22. CITATION MODEL / COPYRIGHT STATEMENT MODEL
### Customization Alert ###
a. Replaced the Parameter Entity %copyright-statement-model;
with the OR list Parameter Entity
%copyright-statement-elements; and used that
within the content model of <copyright-statement>
b. Citation - In the PE %citation-elements; also
changed the PE -%ext-links.class; ==> -%address-links.class;
(Changed the content model of citation to match.)
c. In -%copyright-statement-elements;, replaced the mix
-%rendition-plus; with its constituent classes
d. In -%citation-elements;, replaced the mix -%simple-text;
with its constituent classes (with exception of
%address-link.class;).
21. RELATED ARTICLE
### Customization Alert ###
- Renamed
-%related-article-model; ==> -%related-article-elements;
(To match the DTD naming convention that full content
models are named with a "-model" suffix and groups of
elements to be added to #PCDATA for a particular
content model are named "-elements".)
- Started "-related-article-elements" PE with an OR Bar
- Deleted "ext-links.class", because these elements are
already in the %references.class; (no model change)
20. INLINE MATH - <inline-formula> added to:
- %label-elements;
19. RELATED ARTICLE ATTRIBUTES - Added the following attributes
to the element <related-article>:
a. "id" - to provide a unique identifier
b. "alternate-form-of", which works (similarly to the same
attribute when used on a <graphic> element) to point to
another <related-article> element within the same document
as an alternate form of the related article.
18. ISSUE TITLE <issue-title> - Created new element for a theme or
special issue title
- Defined here in the common module
- Added to <article-meta>
- Added to %references.class; (therefore to <citation>,
<product>, and <related-article>
- Created new Parameter Entities %issue-title-elements;
which hold the OR-group of elements that may be mixed with
#PCDATA inside the content model
17. ATTRIBUTION
- Moved <attrib> and its Parameter Entities from the paragraph
module to here, as it is numerous elements, such as <array>,
<boxed-text>, <fig>, <table-wrap>, etc., in the Archival DTD.
16. CUSTOM METADATA - Added the new <custom-meta> element, its
components, and its wrapper. This element is used to insert
name/value pairs for metadata elements that are in source
material but were never envisioned by this DTD. Allowed this
element at the end of <article-meta> and <journal-meta>.
15. EMAIL- Considered to be just another type of external link, as
<ext-link> is, so added to:
- %collab-elements;
- %copyright-statement-elements;
14. DATES
a. Added new class %date-parts.class; to hold all the
potential components of date, such as <year>, <day>,
etc.
b. Made a new Parameter Entity %string-date-elements; to
hold all the elements that may be mixed with #PCDATA
inside a <string-date>
c. Used %date-parts.class; in that model.
13. ROLE ELEMENT - Was added to the model for <citation>, thus
moved to this module from the article metadata module.
12. NEW IDENTIFICATION ELEMENTS - in view of the larger role that
some publishers are giving to DOIs:
a. OBJECT ID - Added a new class Parameter Entity
%id.class; to hold the new element <object-id> Object
Identifier. The <object-id> element is used to capture any
publisher's or archive's ID, such as a DOI. This was modeled
as an element (rather than as an attribute) to allow for
multiple IDs. New PE used in:
- %references.class (therefore inside <citation>,
<related-article>, and <product>)
- metadata objects such as <abstract>
- display objects such as <figure>.
Added PE %object-id-atts; to hold the element's attributes
b. ISSUE ID <issue-id> - new element for an identifier such
as a DOI associated with a journal issue (as opposed to the
existing element <issue>, which is defined as the issue
number)
- Defined here in the common module
- Added to <article-meta>
- Added to %references.class; (therefore to <citation>,
<product>, and <related-article>
- Created PE %issue-id-atts; to hold the attributes.
c. VOLUME ID <volume-id> - new element for an identifier such
as a DOI associated with a volume of a journal (as opposed
to the existing element <volume>, which is defined as the
volume number)
- Defined here in the common module
- Added to <article-meta>
- Added to %references.class; (therefore to <citation>,
<product>, and <related-article>
- Created new Parameter Entities %volume-id-elements;
which hold the OR-group of elements that may be mixed with
#PCDATA inside the content model
- Added PE %volume-id-atts; to hold the attributes.
Note: All ID attributes for these new identification
elements was set to use the "pub-id-type" attribute,
which is for Archival (Green) set as a CDATA attribute.
11. NAME CLASS / STRING NAME / PERSON NAME CLASS
a. Created a new element <string-name> for names that
do not follow the former, strict personal name model.
<string-name> holds any combination of #PCDATA and any of
the known personal-name elements such as <surname>.
- Used a new Parameter Entity %string-name-elements;
in the content model
b. Created a new class %name.class; to hold all the ways
to name people: <name>, <string-name>, and <collab>
who produce products or articles.
c. Allowed <string-name> to be used anywhere <name> is
used. Inside
- citation (by adding to %references.class;)
- product (by adding to %references.class;)
d. Added new attribute "initials" to the personal name
components: <surname> and <given-names>. This provides
a way to preserve the initials, for matching services
that prefer initials to full names. Since there are
many cases in which the initials cannot be determined
programmatically, we merely provide a bucket to record
them.
e. Added new Parameter Entities %given-name-atts; and
%surname-atts; to hold the new "initials" attribute.
10. ATTRIBUTE VALUE LISTS - The Green (Archival) DTD needed to
change all explicit attribute value lists in the DTD to CDATA.
In the future, explicit list types will be a feature of the
Blue (Publishing) and new Authoring DTDs. Therefore, added
Parameter entities to hold the following attributes:
- date-type
9. RELATED ARTICLE ATTRIBUTES - Added the following attributes
to the element <related-article>:
- "id ID #IMPLIED" attribute, so the related-article
can be referenced.
- "ext-link-type" - to indicate the type of link used to
point to the related article. Attribute was used with
exactly the same content (CDATA) and suggested values
as when used with the element <ext-link>.
- "issue" - used (along with "vol", "page", and "journal-id")
to provide metadata concerning the related article
- "journal-id"- used (along with "vol", "page", and "issue")
to provide metadata concerning the related article.
- "journal-id-type" - Performs the same function that this
attribute performs for the element <journal-id>. The
"journal-id" values are the same as those for existing
journal identifiers plus "issn".
- "alternate-form-of", which works (similarly to the same
attribute when used on a <graphic> element) to point to
another <related-article> element within the same document
as an alternate form of the related article.
8. PARAMETER ENTITY CLEANUP AND REGULARIZATION
a. RENAME ELEMENT MIXES NOT TO END IN "-elements", since that
suffix is reserved for mixes that are added to #PCDATA in
a particular element
### Customization Alert ###
Names ending in "-elements" saved for element-specific mixes
that will be added to #PCDATA for one element
- %sec-back-matter-elements; ==> %sec-back-matter-mix;
(Used in -%sec-model; and -%sec-opt-title-model;)
b. NEW CLASSES - Largely for classing and modification reasons,
the following new classes were added:
- %date.class;
- %def.class;
- %degree.class;
- %id.class;
- Removed duplicate %person-name.class;
c. NEW MIXES - To correct potential classing problems, new
Parameter Entities were created. The following content
models were changed to use these new entities.
- <etal> -%etal-elements;
- <ext-link> -%ext-link-elements;
- <fax> -%fax-elements;
- <given-names> -%given-names-elements;
- <issn> -%issn-elements;
- <issue> -%issue-elements;
- <label> -%label-elements;
- <long-desc> -%long-desc-elements;
- <phone> -%phone-elements;
- <prefix> -%prefix-elements;
- <publisher-name> -%publisher-name-elements;
- <role> -%role-elements;
- <suffix> -%suffix-elements;
- <surname> -%surname-elements;
- <uri> -%uri-elements;
- <volume> -%volume-elements;
- <volume-id> -%volume-id-elements;
- <bio> %bio-model; (which uses %just-para.class;)
- <def> %def-model;
- <def> %just-para.class;
d. RENAME CLASSES
### Customization Alert ###
Not all classes ended in the ".class" suffix. Changed the
following to add the class suffix:
- %address-elements; (renamed -%address.class;) used in
- %aff-elements;
- %publisher-loc-elements;
- %address-model;
- %inline-math.class; used in -%label-elements;
e. PE %attrib-elements;
### Customization Alert ###
Uses %emphasized-text; which now starts with an OR bar, so
removed the OR bar from this PE.
f. LINK CLASSES
- In %aff-elements;, replaced %link.class; with
the following classes (via use of %all-phrase;)
(no DTD change):
- %address-link.class; (external used in addresses)
- %simple-link.class; (the internal links, same)
- %article-link.class; (for journal articles)
- In -%collab-elements;
- Replaced -%ext-links.class; with the following class
(via use of %all-phrase;)
(no DTD change):
- address-link.class; (external used in addresses)
- Deleted -%inpara-address;
(No model change, %address-link.class; covers it.)
- In %copyright-statement-elements;, replaced
-%inpara-address; with -%address-link.class;
(via use of %all-phrase;)
7. DEFAULT CLASSES - Were moved from this module to
%default-classes.ent;
6. Updated public identifier to "v2.0 20040830"
=============================================================
Version 1.1 (TRG) v1.1 (2003-11-01)
5. Made <copyright-statement> model into a parameter entity in
order to add <ext-link> to the content model.
Rationale: Permit linkage between copyright statement and
copyright holder's site.
4. Added attribute "content-type" to element <ack>.
Rationale: To identify and preserve the semantic intent of
semantically rich source documents.
3. Added ID attribute to the following elements:
- <ack>
- <address>
- <alt-text>
- <ext-link> (by modifying %ext-link-atts;)
- <institution>
- <long-desc>
- <notes> (by modifying parameter entity %notes-atts;)
Rationale: Provide unique identifier so these elements can be
linked to.
2. Added element <label> to content model of <aff> (by adding
-%label.class; to parameter -%aff-elements;)
Rationale: To provide <label> when needed for format
over-ride.
=============================================================
Version 1.0 Changes Before Public Release
(Lapeyre) v1.0 (2002-12-25)
1. ETAL - Changed the content model of <etal> to replace the
entire content model with a Parameter Entity, not just name
some elements that may mix with #PCDATA. Rationale: The
Authoring DTD would like to make <etal> EMPTY.
-->
<!-- ============================================================= -->
<!-- PARAMETER ENTITY DEPENDENCIES
Requires the following parameter entities
be defined before calling this module,
usually accomplished in the Customization
Module for the specific DTD:
- %address.class;
- %break.class;
- %emphasis.class;
- %inline-display.class;
- %just-rendition;
- %label.class;
- %para-level;
- %references.class;
- %rendition-plus;
- %sec-back-matter-mix;
- %sec-level;
- %sec-opt-title-model;
- %simple-link.class;
- %simple-phrase;
- %simple-text;
- %subsup.class;
- %might-link-atts; -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- PARAMETER ENTITIES FOR ATTRIBUTE VALUES -->
<!-- ============================================================= -->
<!-- HISTORY DATE TYPES -->
<!-- The <history> element contains one or more
<date> elements that record events in the
life of a publication.
date-type Attribute should only be used if the date
is one of the known types; otherwise omit
the attribute.
Values are:
accepted - Date manuscript was
accepted
received - Date manuscript received
rev-request - Date revisions were
requested or manuscript
was returned
rev-recd - Date revised manuscript
was received -->
<!ENTITY % date-types "accepted | received | rev-request |
rev-recd" >
<!-- ARTICLE/PUBLICATION IDENTIFIER TYPES -->
<!-- The "pub-id-type" attribute names the
type of identifier, or the organization or
system that defined this identifier for the
identifier of the journal article or a
cited publication.
Used on the <article-id> element, which
holds an identifier for the entire article.
Also used on the <pub-id> element, which
is an identifier for a publication cited in
a bibliographic reference (citation).
Valid Types include:
art-access-id
- Generic article accession id for
interchange and retrieval between
archives
coden - Obsolete PDB/CCDC identifier (may
be present on older articles)
be present on older articles)
doi - Digital Object Identifier for
the article
medline- NLM Medline identifier
other - None of the named identifiers
pii - Publisher Item Identifier, see
/epub/piius.htm
pmcid - PubMed Central identifier
pmid - PubMed ID (see
www.ncbi.nlm.nih.gov/entrez/
query.fcgi?db=PubMed)
publisher-id -
Publisher's identifying number
such as an 'article-id', 'artnum',
'identifier', 'article- number',
etc.
sici - Serial Item and Contribution
Identifier (SICI). A journal
article may have more than one
SICI, one for a print version and
one for an electronic version. -->
<!ENTITY % pub-id-types "art-access-id | coden | doi | medline |
other | pii | pmcid | pmid |
publisher-id | sici" >
<!-- ============================================================= -->
<!-- PARAMETER ENTITIES FOR COMMENT MODELS -->
<!-- ============================================================= -->
<!-- DATE ELEMENTS MODEL -->
<!-- The content models for elements that describe
dates, such as Publication Date <pub-date>
and History Dates <date>. The <string-date>
element holds dates for which months and
years are not given, for example "first
quarter", "spring", etc. -->
<!ENTITY % date-model "( ( (day?, month?) | season)?,
year?, string-date?)" >
<!-- CONTENT MODEL FOR A STRUCTURAL SECTION -->
<!-- The model for a section that requires that a
section title be present, used for elements
such as Section and Appendix. -->
<!ENTITY % sec-model "(label?, title, (%para-level;)*,
(%sec-level;)*,
(%sec-back-matter-mix;)* )" >
<!-- CONTENT MODEL FOR AN UNTITLED SECTION -->
<!-- The model for a section-like structure that
may or may not have an initial title -->
<!ENTITY % sec-opt-title-model
"(label?, title?, (%para-level;)*,
(%sec-level;)*,
(%sec-back-matter-mix;)* )" >
<!-- LINK ELEMENTS -->
<!-- Elements for use in the linking elements
such as <xref>, <target>, and <ext-link> -->
<!ENTITY % link-elements
"| %emphasis.class; | %subsup.class;" >
<!-- TITLE ELEMENTS -->
<!-- Elements for use in all the title elements
such as <title>, <subtitle>, <trans-title>,
etc.
DESIGN NOTE: All inline mixes begin with an
OR bar, but since %simple-phrase; is an
inline mix, the OR bar is already there. -->
<!ENTITY % title-elements
"%simple-phrase; | %break.class;" >
<!-- ============================================================= -->
<!-- PARAMETER ENTITIES FOR LINKING ATTRIBUTES -->
<!-- ============================================================= -->
<!-- XLINK LINK ATTRIBUTES -->
<!-- Used for elements that are a link by
definition, such as the <xref> element.
xlink:href Provides an address or identifier of the
object to which the link points, for
example a URI or a filename
xlink:role Provides a URI reference pointing to some
resource that describes the role or function
of this link
xlink:title
Describes the meaning of the link in a
human-readable and displayable fashion
xlink:show Describes the requested presentation when
the link is traversed.
Values are:
embed Load the new presentation in the
place of the link
new Load a new window, frame, pane, or
other presentation
none No clue for the application
other Look to other markup for a clue
replace Load the new resource in the same
window, frame, pane, or other
presentation context as the link
started in
xlink:actuate
When is the link traversed, and under whose
control.
Values are:
none No clue for the application
onLoad Traverse the link immediately
upon loading the link
onRequest
User or software requests that the
link be traversed
other Look to other markup for a clue
-->
<!ENTITY % link-atts
"xmlns:xlink CDATA #FIXED
'http://www.w3.org/1999/xlink'
xlink:type (simple) #FIXED 'simple'
xlink:href CDATA #REQUIRED
xlink:role CDATA #IMPLIED
xlink:title CDATA #IMPLIED
xlink:show (embed | new | none | other | replace)
#IMPLIED
xlink:actuate
(none | onLoad | onRequest | other)
#IMPLIED" >
<!-- MIGHT LINK XLINK ATTRIBUTES -->
<!-- Used for elements which may need to link to
external sources or other objects within
the document, but may not necessarily act
as a link at all. The attribute
"xlink:href" identifies the object to which
the link points. -->
<!ENTITY % might-link-atts
"xmlns:xlink CDATA #FIXED
'http://www.w3.org/1999/xlink'
xlink:type (simple) #FIXED 'simple'
xlink:href CDATA #IMPLIED
xlink:role CDATA #IMPLIED
xlink:title CDATA #IMPLIED
xlink:show (embed | new | none | other | replace)
#IMPLIED
xlink:actuate
(none | onLoad | onRequest | other)
#IMPLIED" >
<!-- ============================================================= -->
<!-- PARAMETER ENTITIES FOR ATTRIBUTES LISTS -->
<!-- (ALPHABETICAL ORDER) -->
<!-- ============================================================= -->
<!-- AFFILIATION ATTRIBUTES -->
<!-- Attributes for the Affiliation <aff>
element -->
<!ENTITY % aff-atts
"id ID #IMPLIED
rid IDREFS #IMPLIED" >
<!-- BIOGRAPHY ATTRIBUTES -->
<!-- Attributes for <bio> element
id Unique identifier so the element may be
referenced
rid Points to the identifier of an author or
authors
xlink:href Provides an address or identifier of the
object to which the link points, for
example a URI or a filename. -->
<!ENTITY % bio-atts
"id ID #IMPLIED
rid IDREFS #IMPLIED
%might-link-atts;" >
<!-- COLLABORATION ATTRIBUTES -->
<!-- Attributes for <collab> -->
<!-- collab-type
The type or role of the collaborators,
what function did they play in the
publication.
Suggested values include:
assignee
- Group or company to whom a patent
is awarded
authors - Content creators
editors - Content editors
compilers
- Put together a composite work
from multiple sources
guest-editors
- A group of editors that have been
invited to edit all or part of a
work
inventors
- Idea, software, or machine
creators
translators
- Translated the cited work from
one language into another
id Unique identifier so that the collaboration
can be referenced
xlink:href Provides an address or identifier of the
object to which the link points, for
example a URI or a filename -->
<!ENTITY % collab-atts
"collab-type
CDATA #IMPLIED
id ID #IMPLIED
%might-link-atts;" >
<!-- EXTERNAL LINK ATTRIBUTES -->
<!-- Attribute list for external links
ext-link-type
Type of external link. Use this attribute
if the type of external link is one of the
ones below or another named type.
Suggested values include:
aoi Astronomical Object Identifier
doi Digital Object Identifier
ec Enzyme nomenclature - see
http://www.chem.qmw.ac.uk/iubmb/enzyme/
ftp File transfer protocol
email An email address
gen GenBank identifier
genpept Translated Protein-encoding
sequence Database
highwire HighWire press intrajournal
pmid PubMed identifier
pdb Protein data bank. See
http://www.rcsb.org/pdb/
pgr Plant gene register. See
http://www.tarweed.com/pgr/
pir Protein Information Resource
see http://pir.georgetown.edu
pirdb Protein Information Resource
see http://pir.georgetown.edu
pmc PubMedCentral identifier
sprot Swiss-Prot. See
http://www.ebi.ac.uk/swissprot/
uri Website or web service
id Unique identifier so the element may be
referenced
xlink:href Provides an address or identifier of the
object to which the link points, for
example a URI or a filename -->
<!ENTITY % ext-link-atts
"ext-link-type
CDATA #IMPLIED
id ID #IMPLIED
%might-link-atts;" >
<!-- CITATION ATTRIBUTES -->
<!-- Attributes for <citation>
citation-type
Defines the type of work being referenced.
Suggested values include:
book Book
conf-proceedings
Conference proceedings
discussion Discussion among a group in
some forum - public, private,
or electronic, which may or
may not be moderated
gov Government publication
journal Journal article
list Listserv
other None of the listed types
patent Patent or patent application
personal-communication
Informal or personal
communication, such as a
phone call or an email
message
standard Standards document issued by
a recognized standards body,
such as ISO, ANSI, IEEE,
OASIS, etc.
thesis Work written as part of the
completion of an advanced
degree
web Website
id Unique identifier so the element may be
referenced
xlink:href Provides an address or identifier of the
object to which the link points, for
example a URI or a filename -->
<!ENTITY % citation-atts
"citation-type
CDATA #IMPLIED
id ID #IMPLIED
%might-link-atts;" >
<!-- DATE (HISTORICAL) ATTRIBUTES -->
<!-- date-type Attribute should only be used if the date
is one of the known types, otherwise omit
the attribute. Values are:
accepted - Date manuscript was
accepted
received - Date manuscript received
rev-request - Date revisions were
requested or manuscript
was returned
rev-recd - Date revised manuscript
was received -->
<!ENTITY % date-atts
"date-type (%date-types;) #IMPLIED" >
<!-- GIVEN NAMES ATTRIBUTES -->
<!-- initials The initial(s) for the given names of the
person. Particularly useful in those cases
that cannot be algorithmically determined. -->
<!ENTITY % given-names-atts
"initials CDATA #IMPLIED" >
<!-- ISSN ATTRIBUTES -->
<!-- Attribute list for <issn> -->
<!-- Used to record the type of publication, for
example, a print-only publication versus
an electronic-only publication, in any of
several life stages.
Suggested values include:
epub - Electronic publication
ppub - Print publication
epub-ppub - Published in both print and
electronic form
epreprint - Electronic preprint
dissemination
ppreprint - Print preprint dissemination
ecorrected - Corrected in electronic
pcorrected - Corrected in print
eretracted - Retracted in electronic
pretracted - Retracted in print -->
<!ENTITY % issn-atts
"pub-type CDATA #IMPLIED" >
<!-- ISSUE IDENTIFIER ATTRIBUTES -->
<!-- Attributes for the <issue-id> element
pub-id-type
Publication (article) Identifier Type
Names the type of identifier, or the
organization or system that defined this
identifier for the identifier of the journal
article or a cited publication. This is an
optional CDATA attribute that should be used
whenever the type is known.
Used on the <article-id> element, which
holds an identifier for the entire article.
Also used on the <pubid> element, which
is an identifier for a publication cited in
a bibliographic reference (citation).
Suggested values include:
coden - Obsolete PDB/CCDC identifier (may
be present on older articles)
doi - Digital Object Identifier
medline- NLM Medline identifier
other - None of the named identifiers
pii - Publisher Item Identifier, see
http://pubs.acs.org/epub/piius.htm
or
http://www.aip.org/epub/piipr.html
pmid - PubMed Central identifier (see
www.ncbi.nlm.nih.gov/entrez/
query.fcgi?db=PubMed)
publisher-id
- Publisher's identifier such
as an 'article-id', 'artnum',
'identifier', 'article- number',
'pub-id', etc.
sici - Serial Item and Contribution
Identifier (SICI). A journal
article may have more than one
SICI, one for a print version and
one for an electronic version. -->
<!ENTITY % issue-id-atts
"pub-id-type
CDATA #IMPLIED" >
<!-- NOTE ATTRIBUTES -->
<!-- Attribute list for <note> -->
<!-- notes-type To identify the type of note, if the type
can be/has been identified, for example,
"note-in-proof"
id Unique identifier so the element may be
referenced -->
<!ENTITY % notes-atts
"id ID #IMPLIED
notes-type CDATA #IMPLIED" >
<!-- OBJECT IDENTIFIER ATTRIBUTES -->
<!-- Attributes for the <object-id> element
pub-id-type
Publication (article) Identifier Type
Names the type of identifier, or the
organization or system that defined this
identifier for the identifier of the journal
article or a cited publication. This is an
optional CDATA attribute that should be used
whenever the type is known.
Used on the <article-id> element, which
holds an identifier for the entire article.
Also used on the <pubid> element, which
is an identifier for a publication cited in
a bibliographic reference (citation).
Suggested values include:
coden - Obsolete PDB/CCDC identifier (may
be present on older articles)
doi - Digital Object Identifier
medline- NLM Medline identifier
other - None of the named identifiers
pii - Publisher Item Identifier, see
http://pubs.acs.org/epub/piius.htm
or
http://www.aip.org/epub/piipr.html
pmid - PubMed Central identifier (see
www.ncbi.nlm.nih.gov/entrez/
query.fcgi?db=PubMed)
publisher-id
- Publisher's identifier such
as an 'article-id', 'artnum',
'identifier', 'article- number',
'pub-id', etc.
sici - Serial Item and Contribution
Identifier (SICI). A journal
article may have more than one
SICI, one for a print version and
one for an electronic version. -->
<!ENTITY % object-id-atts
"pub-id-type
CDATA #IMPLIED" >
<!-- RELATED ARTICLE ATTRIBUTES -->
<!-- Attributes for <related-article>
id Unique identifier so the element may be
referenced
alt-form-of
Exactly like the "alt-form-of" attribute
used with <graphic>, this is an IDREF
attribute which points to the ID of another
<related-article> in the same document
rather than to an external file.
related-article-type
addendum Additional material for an
article, generated too late
to be added to the main text
commentary-article
Used in an commentary or
editorial to link to the
article on which it is
commenting
companion Used in an article to link
to a companion (related
or sibling) article
corrected-article
Used in a correction to link
to the article being
corrected. Sometimes called
erratum.
in-this-issue Related article in the same
journal issue
letter A letter to the publication
or a reply to such a
letter
commentary Used in an article to link
to its associated commentary
or editorial
correction-forward
Used in an article to link
forward to its associated
correction (rarely used)
retracted-article
Used in a retraction to link
to the article being retracted
retraction-forward
Used in an article to link
forward to its associated
retraction (rare)
ext-link-type
Type of external link used to point to the
related article. Use this attribute
if the type of external link is one of the
ones below or another named type.
Suggested values include:
aoi Astronomical Object Identifier
doi Digital Object Identifier
ec Enzyme nomenclature - see
http://www.chem.qmw.ac.uk/iubmb/enzyme/
ftp File transfer protocol
email An email address
gen GenBank identifier
genpept Translated Protein-encoding
sequence Database
highwire HighWire press intrajournal
pdb Protein data bank. See
http://www.rcsb.org/pdb/
pgr Plant gene register. See
http://www.tarweed.com/pgr/
pir Protein Information Resource
see http://pir.georgetown.edu
pirdb Protein Information Resource
see http://pir.georgetown.edu
pmc PubMed Central identifier
pmid PubMed identifier
sprot Swiss-Prot. See
http://www.ebi.ac.uk/swissprot/
uri Website or web service
The next five attributes are used to identify the
journal in which the related article was published.
vol Volume of the journal in which the related
article exists. It is best practice to
limit the scope to the current journal,
the one in which the current article
resides.
page Page number of the related article. It is
best practice to limit the scope to the
current journal, the one in which the
current article resides. The values for this
attribute should be a first page or a page
range.
issue Issue number of the related article.
journal-id Identifier for the journal which contains the
related article.
journal-id-type
Indicates whose identifier this is, for
example, "pub-id" for a publisher's
identifier or "pmc" for PubMed Central.
Suggested values include:
archive Identifier assigned by an archive
or other repository
aggregator
Identifier assigned by a data
aggregator
doi Digital Object Identifier for the
entire journal, not just for the
article (rare)
index Identifier assigned by an
abstracting or indexing service
issn International Standard Serial Number
of the journal in which the related
article was published
pmc Identifier assigned by PubMed Central
for example, the pmc journal
abbreviation such as "pnas", "mbc",
"nar", "molcellb", which may be the
same as the abbreviated journal
title
publisher-id
Identifier assigned by the content
publisher, for example, "MOLEC",
"MOLCEL"
nlm-ta Identifier assigned by the
PubMed/Medline, and is typically
the journal abbreviation, for
example, "Mol Biol Cell", "Nucleic
Acids Res", which may be the
same as the abbreviated journal
title.
xlink:href Provides an address or identifier of the
object to which the link points, for
example a URI or a filename. -->
<!ENTITY % related-article-atts
"id ID #IMPLIED
alternate-form-of
IDREF #IMPLIED
related-article-type
CDATA #REQUIRED
ext-link-type
CDATA #IMPLIED
vol CDATA #IMPLIED
page CDATA #IMPLIED
issue CDATA #IMPLIED
journal-id
CDATA #IMPLIED
journal-id-type
CDATA #IMPLIED
%might-link-atts;" >
<!-- SURNAME ATTRIBUTES -->
<!-- initials The initial(s) for the given names of the
person. Particularly useful in those cases
that cannot be algorithmically determined. -->
<!ENTITY % surname-atts
"initials CDATA #IMPLIED" >
<!-- VOLUME IDENTIFIER ATTRIBUTES -->
<!-- Attributes for the <issue-id> element
pub-id-type
Publication (article) Identifier Type
Names the type of identifier, or the
organization or system that defined this
identifier for the identifier of the journal
article or a cited publication. This is an
optional CDATA attribute that should be used
whenever the type is known.
Used on the <article-id> element, which
holds an identifier for the entire article.
Also used on the <pubid> element, which
is an identifier for a publication cited in
a bibliographic reference (citation).
Suggested values include:
coden - Obsolete PDB/CCDC identifier (may
be present on older articles)
doi - Digital Object Identifier
medline- NLM Medline identifier
other - None of the named identifiers
pii - Publisher Item Identifier, see
http://pubs.acs.org/epub/piius.htm
or
http://www.aip.org/epub/piipr.html
pmid - PubMed Central identifier (see
www.ncbi.nlm.nih.gov/entrez/
query.fcgi?db=PubMed)
publisher-id
- Publisher's identifier such
as an 'article-id', 'artnum',
'identifier', 'article- number',
'pub-id', etc.
sici - Serial Item and Contribution
Identifier (SICI). A journal
article may have more than one
SICI, one for a print version and
one for an electronic version. -->
<!ENTITY % volume-id-atts
"pub-id-type
CDATA #IMPLIED" >
<!-- ============================================================= -->
<!-- ELEMENT USED BY MORE THAN ONE CLASS -->
<!-- ============================================================= -->
<!-- ============================================================= -->
<!-- COMMON METADATA/BIBLIOGRAPHIC ELEMENTS -->
<!-- ============================================================= -->
<!-- ARTICLE TITLE -->
<!-- The title of the article in the language
in which the article was originally
published
Remarks: The related element Translated Title
<trans-title> should be used for a
translation of the article into another
language, for example, to hold the English
version of a Japanese article title. -->
<!ELEMENT article-title
(#PCDATA %title-elements;)* >
<!-- xml:lang The language in which the value of the
element is expressed. Recommended best
practice is to use values as defined in
RFC 1766, typically 2-letter language
codes such as "FR" (French), "EN" (English),
and "DE" (German). These values are NOT
case sensitive, so "EN" = "en". The values
may include hyphenated differentiations such
as "EN-AU" (Australian English) and "EN-US"
(United States English). -->
<!ATTLIST article-title
xml:lang NMTOKEN #IMPLIED >
<!-- AFFILIATION ELEMENTS -->
<!-- Elements for use in the <aff> element -->
<!ENTITY % aff-elements "| %address.class; | %address-link.class; |
%article-link.class; | %break.class; |
%emphasis.class; | %label.class; |
%simple-link.class; | %subsup.class;" >
<!-- AFFILIATION -->
<!-- Name of a institution or organization such as
a university or corporation.
Authoring and Conversion Note: In a typical
case, the "id" attribute will be pointed to
by one or more contributors.
Conversion Note: Any explicitly tagged numbers
or symbols for author linkages should be
discarded, as the linkage will be recreated
from the "id" connection.
Authoring Note: While this element
contains an optional Label element, the
Label element should be included only in
those circumstances where a formatting
override is needed; Label should NOT
be used in the ordinary course of
tagging. -->
<!ELEMENT aff (#PCDATA %aff-elements;)* >
<!-- id Unique identifier so that the affiliated
institution may be referenced, for example
by a contributor
rid May be used to point to affiliation-related
information within the document
-->
<!ATTLIST aff
%aff-atts; >
<!-- COLLABORATIVE (GROUP) AUTHOR ELEMENTS -->
<!-- Elements for use in the <collab> element
DESIGN NOTE: All inline mixes begin with an
OR bar, but since %simple-text; is an inline
mix, the OR bar is already there.
DESIGN NOTE: All inline mixes begin with an
OR bar, but since %simple-text; is an inline
mix, the OR bar is already there. -->
<!ENTITY % collab-elements
"%simple-text; | %address-link.class; |
%simple-link.class;" >
<!-- COLLABORATIVE (GROUP) AUTHOR -->
<!-- Used for groups of authors credited under
one name, either as a collaboration in the
strictest sense, or when an organization,
institution, or corporation is the group.
Remarks: When an author is an organization
rather than a person, use the <collab>
element rather than <surname>, for
example:
<collab>Aardvark Institute</collab>
-->
<!ELEMENT collab (#PCDATA %collab-elements;)* >
<!-- collab-type
The type or role of the collaborators,
what function did they play in the
publication.
Suggested values include:
assignee
- Group or company to whom a patent
is awarded
authors - Content creators
editors - Content editors
compilers
- Put together a composite work
from multiple sources
guest-editors
- A group of editors that have been
invited to edit all or part of a
work
inventors
- Idea, software, or machine
creators
translators
- Translated the cited work from
one language into another
one language into another
id unique identifier so that the collaboration
can be referenced
xlink:href Provides an address or identifier of the
object to which the link points, for
example a URI or a filename. -->
<!ATTLIST collab
%collab-atts; >
<!-- CONFERENCE DATE ELEMENTS -->
<!-- Elements for use in the <conf-date> element-->
<!ENTITY % conf-date-elements
" " >
<!-- CONFERENCE DATE -->
<!-- The date(s) on which the conference was held.
Conference dates in journal headers are
traditionally stored in one of two forms:
as a single date ("May 1906") or as the
first day and last day of the conference.
Both types should be stored in this element;
the dates that come from separate first and
last elements should be combined:
<conf-start>August 4, 2002</conf-start>
<conf-end>August 9, 2002<conf-end>
should become:
<conf-date>August 4, 2002 - August 9,
2002</conf-date>
-->
<!ELEMENT conf-date (#PCDATA %conf-date-elements;)* >
<!-- CONFERENCE LOCATION ELEMENTS -->
<!-- Elements for use in the <conf-loc> element
DESIGN NOTE: All inline mixes begin with an
OR bar, but since %simple-text; is an inline
mix, the OR bar is already there. -->
<!ENTITY % conf-loc-elements
"%simple-text;" >
<!-- CONFERENCE LOCATION -->
<!-- The physical location(s) of the conference.
This may include a city, a country, or a
campus or organization location if that is
the only location available.
Authoring and Conversion Note: If the
conference is in the United States, the
state should also be provided. A specific
venue or address (e.g. conference hotel)
should not be provided unless there is no
other location information. -->
<!ELEMENT conf-loc (#PCDATA %conf-loc-elements;)* >
<!-- CONFERENCE NAME ELEMENTS -->
<!-- Elements for use in the <conf-name> element.
DESIGN NOTE: All inline mixes begin with an
OR bar, but since %simple-text; is an inline
mix, the OR bar is already there. -->
<!ENTITY % conf-name-elements
"%simple-text;" >
<!-- CONFERENCE NAME -->
<!-- The full name of the conference, including any
qualifiers such as "43rd Annual". When the
name includes the year of the conference,
(e.g. "Extreme 2002"), the year should appear
in both the conference Name and the Conference
Date elements. -->
<!ELEMENT conf-name (#PCDATA %conf-name-elements;)* >
<!-- COPYRIGHT STATEMENT MODEL -->
<!-- Content model for <copyright-statement> -->
<!ENTITY % copyright-statement-elements
"| %address-link.class;| %emphasis.class; |
%subsup.class;" >
<!-- COPYRIGHT STATEMENT -->
<!-- Copyright notice or statement, suitable for
printing or display. Within the statement the
copyright year should be identified, if
expected to be displayed. -->
<!ELEMENT copyright-statement
(#PCDATA %copyright-statement-elements;)* >
<!-- OBJECT IDENTIFIER -->
<!-- Used to record an identifier such as a DOI
for an interior element such as an <abstract>
or <figure>.
Remarks: Such an identifier may be created
by a publisher or archive, and there is no
requirement that identifiers be unique. -->
<!ELEMENT object-id (#PCDATA) >
<!-- id-type Indicates what type of identifier this is or
who assigned the identifier, for example,
"pub-id" for a publisher's non-DOI
identifier or "DOI" for a Digital Object
Identifier.
In Archival this is a CDATA attribute but
suggested values include:
archive Identifier assigned by an archive
or other repository
aggregator
Assigned by a data aggregator
doi Digital Object Identifier
index Assigned by an abstracting or
indexing service
pmc Assigned by PubMed Central
publisher-id
Non-DOI Identifier assigned by
the content publisher -->
<!ATTLIST object-id
%object-id-atts; >
<!-- JOURNAL IDENTIFIER ATTRIBUTES -->
<!-- Attribute list for journal identifier
<journal-id> element -->
<!-- Indicates whose identifier this is, for
example, "pub-id" for a publisher's
identifier or "pmc" for PubMed Central.
Suggested values include:
archive Identifier assigned by an archive
or other repository
aggregator
Identifier assigned by a data
aggregator
doi Digital Object Identifier for the
entire journal, not just for the
article (rare)
index Identifier assigned by an
abstracting or indexing service
pmc Identifier assigned by PubMed Central
for example, the pmc journal
abbreviation such as "pnas", "mbc",
"nar", "molcellb", which may be the
same as the abbreviated journal
title
publisher-id
Identifier assigned by the content
publisher, for example, "MOLEC",
"MOLCEL"
nlm-ta Identifier assigned by the
PubMed/Medline, and is typically
the journal abbreviation, for
example, "Mol Biol Cell", "Nucleic
Acids Res", which may be the
same as the abbreviated journal
title. -->
<!ENTITY % journal-id-atts
"journal-id-type
CDATA #IMPLIED " >
<!-- ISSUE TITLE ELEMENTS -->
<!-- Elements for use with data characters inside
the model for the <issue> element -->
<!ENTITY % issn-elements
" " >
<!-- ISSN -->
<!-- International Standard Serial Number -->
<!ELEMENT issn (#PCDATA %issn-elements;) >
<!-- Used to record the type of publication, for
which this ISSN was issued, for example,
a print-only publication versus
an electronic-only publication, in any of
several life stages.
Suggested values include:
epub - Electronic publication
ppub - Print publication
epub-ppub - Published in both print and
electronic form
epreprint - Electronic preprint
dissemination
ppreprint - Print preprint dissemination
ecorrected - Corrected in electronic
pcorrected - Corrected in print
eretracted - Retracted in electronic
pretracted - Retracted in print
-->
<!ATTLIST issn
%issn-atts; >
<!-- ISSUE TITLE ELEMENTS -->
<!-- Elements for use with data characters inside
the model for the <issue> element -->
<!ENTITY % issue-elements
"%just-rendition;" >
<!-- ISSUE NUMBER -->
<!-- NEW DEFINITION FOR RELEASE 2.0:
The issue number, issue name, or other
identifier of an issue of a journal that
is displayed or printed with the issue.
This is not the machine-readable internal
identifier such as a DOI or SICI, that is
the related element <issue-id> -->
<!ELEMENT issue (#PCDATA %issue-elements;)* >
<!-- ISSUE IDENTIFIER -->
<!-- Used to record an identifier such as a DOI
that describes an entire issue of a
journal -->
<!ELEMENT issue-id (#PCDATA) >
<!-- pub-id-type
Indicates what type of identifier this is or
who assigned the identifier, for example,
"pub-id" for a publisher's non-DOI
identifier or "DOI" for a Digital Object
Identifier.
In Archival this is a CDATA attribute but
suggested values include:
archive Identifier assigned by an archive
or other repository
aggregator
Assigned by a data aggregator
doi Digital Object Identifier
index Assigned by an abstracting or
indexing service
pmc Assigned by PubMed Central
publisher-id
Non-DOI Identifier assigned by
the content publisher -->
<!ATTLIST issue-id
%issue-id-atts; >
<!-- ISSUE TITLE ELEMENTS -->
<!-- Elements for use in the <issue-title> element
-->
<!ENTITY % issue-title-elements
"" >
<!-- ISSUE TITLE -->
<!-- Used to record the theme or special issue
title for an issue of the journal -->
<!ELEMENT issue-title (#PCDATA %issue-title-elements;)* >
<!-- ROLE ELEMENTS -->
<!-- The elements that can be included along with
data characters inside the content model of
a <role>
DESIGN NOTE: All inline mixes begin with an
OR bar; since %rendition-plus; is an
inline mix, the OR bar is already there. -->
<!ENTITY % role-elements
"%rendition-plus;" >
<!-- ROLE OR FUNCTION TITLE OF CONTRIBUTOR -->
<!-- A title or the role of a contributor
(such as an author) in this work. For example,
Editor-in-Chief, Contributor, Chief
Scientist, Photographer, Research Associate,
etc.
Remarks: Information on the role or type of
contribution is collected in two places,
in the "contrib-type" attribute on the
Contributor element and in the Role element.
For example, the Contributor attribute might
have a value of "editor", while the content
of the role element could be "Associate
Editor". As another example, the contributor
attribute might be "author" and the role
element might be "Principle Author".
The <role> element is also more likely to
appear on screen or in print than the
contributor attribute value. -->
<!ELEMENT role (#PCDATA %role-elements;)* >
<!-- VOLUME NUMBER ELEMENTS -->
<!-- The elements that can be included along with
data characters inside the content model of
a <volume> -->
<!ENTITY % volume-elements
"%just-rendition; " >
<!-- VOLUME NUMBER -->
<!-- NEW DEFINITION FOR RELEASE 2.0:
The volume number, volume name, or other
identifier of an volume of a journal that
is displayed or printed with the volume.
This is not the machine-readable internal
identifier such as a DOI or SICI, that is
the related element <volume-id> -->
<!ELEMENT volume (#PCDATA %volume-elements;)* >
<!-- TRANSLATED TITLE -->
<!-- An alternate version of the title that has
been translated into a language other than
that of the article title <article-title>
Remarks: The related element Article Title
<article-title> should be used for the title
of the article in the original language in
which it was published, this element used
for a translation of that title, for example
the English version of a Japanese article. -->
<!ELEMENT trans-title (#PCDATA %title-elements;)* >
<!-- xml:lang The language in which the value of the
element is expressed. Recommended best
practice is to use values as defined in
RFC 1766, typically 2-letter language
codes such as "FR" (French), "EN" (English),
and "DE" (German). These values are NOT
case sensitive, so "EN" = "en". The values
may include hyphenated differentiations such
as "EN-AU" (Australian English) and "EN-US"
(United States English).
Authoring and Conversion Note: For the
Translated Title element, the xml:lang
attribute should always be set if the
value is known. The only reason the
attribute was not made #REQUIRED was that
there may be cases where the language is
not known. -->
<!ATTLIST trans-title
xml:lang NMTOKEN #IMPLIED >
<!-- VOLUME IDENTIFIER ELEMENTS -->
<!-- The elements that can be included along with
data characters inside the content model of
a <volume-id> -->
<!ENTITY % volume-id-elements
"%just-rendition; " >
<!-- VOLUME IDENTIFIER -->
<!-- Used to record an identifier such as a DOI
that describes an entire volume of a
journal.
REMARKS: The related elements <volume>
holds the volume number as published
with the journal. -->
<!ELEMENT volume-id (#PCDATA %volume-id-elements;)* >
<!-- pub-id-type
Indicates what type of identifier this is or
who assigned the identifier, for example,
"pub-id" for a publisher's non-DOI
identifier or "DOI" for a Digital Object
Identifier.
In Archival this is a CDATA attribute but
suggested values include:
archive Identifier assigned by an archive
or other repository
aggregator
Assigned by a data aggregator
doi Digital Object Identifier
index Assigned by an abstracting or
indexing service
pmc Assigned by PubMed Central
publisher-id
Non-DOI Identifier assigned by
the content publisher -->
<!ATTLIST volume-id
%volume-id-atts; >
<!-- ============================================================= -->
<!-- COMMON METADATA ELEMENTS CONTINUED -->
<!-- PUBLISHER IDENTIFICATION ELEMENTS -->
<!-- (COMMON ARTICLE METADATA/BIBLIOGRAPHIC) -->
<!-- Used in article metadata and also inside -->
<!-- a bibliographic reference (citation) -->
<!-- ============================================================= -->
<!-- ET AL ELEMENTS -->
<!-- The elements that can be included along with
data characters inside the content model of
an <etal> -->
<!ENTITY % etal-elements
"%just-rendition; " >
<!-- ET AL CONTENT MODEL -->
<!-- The content model for the <etal> element -->
<!ENTITY % etal-model "(#PCDATA %etal-elements;)*" >
<!-- ET AL -->
<!-- Although most journals modeled this as an
EMPTY element, typically used to generate
the text "et al." in a stylesheet, some
journal DTDs (Blackwell's, for example) expect
content for this element, with such text as
"Associates, coworkers, and colleagues". -->
<!ELEMENT etal %etal-model; >
<!-- PUBLISHER -->
<!-- Who published the work -->
<!ELEMENT publisher (publisher-name, publisher-loc?) >
<!-- PUBLISHER'S NAME ELEMENTS -->
<!-- The elements that can be included along with
data characters inside the content model of
a <publisher-name>
DESIGN NOTE: All inline mixes begin with an
OR bar; since %just-rendition; is an
inline mix, the OR bar is already there -->
<!ENTITY % publisher-name-elements
"%just-rendition; " >
<!-- PUBLISHER'S NAME -->
<!-- Name of the publisher of the work -->
<!ELEMENT publisher-name
(#PCDATA %publisher-name-elements;)* >
<!-- PUBLISHER'S LOCATION ELEMENTS -->
<!-- Elements for use in the Publisher Location
<publisher-loc> element -->
<!ENTITY % publisher-loc-elements
"| %address.class; | %address-link.class; |
%emphasis.class; | %subsup.class;" >
<!-- PUBLISHER'S LOCATION -->
<!-- Place of publication, usually a city such
as New York or London -->
<!ELEMENT publisher-loc
(#PCDATA %publisher-loc-elements;)* >
<!-- ============================================================= -->
<!-- COMMON METADATA ELEMENTS CONTINUED -->
<!-- PAGE NUMBERING ELEMENTS -->
<!-- ============================================================= -->
<!-- FIRST PAGE ATTRIBUTES -->
<!-- seq Used for sequence number or letter for
journals (such as continuous makeup journals)
with more than one article starting on the
same page -->
<!ENTITY % fpage-atts
"seq CDATA #IMPLIED" >
<!-- FIRST PAGE -->
<!-- The page number on which the article starts,
for print journals that have page numbers -->
<!ELEMENT fpage (#PCDATA) >
<!-- seq Used for sequence number or letter for
journals (such as continuous makeup journals)
with more than one article starting on the
same page -->
<!ATTLIST fpage
%fpage-atts; >
<!-- LAST PAGE -->
<!-- The page number on which the article ends,
for print journals that have page numbers -->
<!ELEMENT lpage (#PCDATA) >
<!-- PAGE RANGES -->
<!-- A container element for additional page
information (TO BE USED TO SUPPLEMENT AND
NOT TO REPLACE <fpage> and <lpage>) to record
discontinuous pages ranges such as
"8-11, 14-19, 40"
meaning that the article begins on page
8, runs 8 through 11, skips to pages 14
through 19, and concludes on page 40. -->
<!ELEMENT page-range (#PCDATA) >
<!-- ELECTRONIC LOCATION IDENTIFIER ATTRIBUTES -->
<!-- seq Used for sequence number or letter for
journals (such as continuous makeup journals)
so that the publisher's sequence of articles
can be preserved, even for electronic
publications. -->
<!ENTITY % elocation-id-atts
"seq CDATA #IMPLIED" >
<!-- ELECTRONIC LOCATION IDENTIFIER -->
<!-- Used to identify an article that
does not have traditional page numbers.
For a printed article, when citations are
sent through the Medline matcher to be turned
into live links or when the metadata about an
article is collected for complete
identification, the first page number (and
sometimes also the last page number) of the
article is recorded to help indicate which
article is being referenced. Electronic only
journals have no page numbers, so this
element is used as the equivalent identifier,
the "electronic page number" that helps to
identify the article. The value could be an
article identifier, a doi, etc., for
example, "E70".
Remarks: This element is more accurately an
electronic identifier, and it was considered
renaming this element to that. The purpose
of the name is to be a parallel with the
<fpage>...<lpage> model. When neither first
page or last page is appropriate, because
the electronic journal has no pages, the
<elocation-id> element is used instead. -->
<!ELEMENT elocation-id (#PCDATA) >
<!-- seq Used for sequence number or letter for
journals (such as continuous makeup journals)
with more than one article starting on the
same page -->
<!ATTLIST elocation-id
%elocation-id-atts; >
<!-- ============================================================= -->
<!-- CITATION (BIBLIOGRAPHIC REFERENCE) -->
<!-- ============================================================= -->
<!-- CITATION ELEMENTS -->
<!-- Content model for the <citation> element.
DESIGN NOTE: All inline mixes begin with an
OR bar. -->
<!ENTITY % citation-elements
"| %emphasis.class; | %inline-display.class; |
%inline-math.class; | %label.class; |
%phrase.class; | %references.class; |
%subsup.class;" >
<!-- CITATION -->
<!-- A citation is a description of a work, such
as a journal article, book, or personal
communication, that is cited in the text of
the article. Although the DTD does not
enforce it, a citation to a journal article
*should* be tagged with as many as possible
of the following, so that PubMed Central or
other matching processing can make the
citation into a live link:
source The MEDLINE abbreviation of the
journal name
article-title
Title of the article
volume Volume of the journal
issue Issue of the journal
fpage Page number on which the article
starts
name Of an author or editor
year Year of publication
month Month of publication (if present)
day Date of publication (if present)
The other elements may be tagged if
desired. The <title> element may be used
for titles of books, conference proceedings,
etc.
Authoring and Conversion Note: In order to
make citations into live links, as much
of the author and date information as is
available should be preserved. The most
important date tag is year, and it should
always be tagged if possible:
<year>2003</year>
The <day> and <month> tags will be used
more rarely; they are provided because some
of the citation matching services can use
the month and the day if they are available.
-->
<!ELEMENT citation (#PCDATA %citation-elements;)* >
<!-- citation-type
Defines the type of work being referenced.
Suggested values include:
book Book
personal-communication
Informal or personal
communication, such as a
phone call or an email
message
conf-proceedings
Conference proceedings
discussion Discussion among a group in
some forum - public, private,
or electronic, which may or
may not be moderated
gov Government publication
journal Journal article
list Listserv
other None of the listed types
patent Patent or patent application
thesis Work written as part of the
completion of an advanced
degree
web Website
id Unique identifier so the element may be
referenced
xlink:href Provides an address or identifier of the
object to which the link points, for
example a URI or a filename -->
<!ATTLIST citation
%citation-atts; >
<!-- ============================================================= -->
<!-- ADDRESS ELEMENTS (BIBLIOGRAPHIC) -->
<!-- ============================================================= -->
<!-- ADDRESS MODEL -->
<!-- Content model for the <address> element -->
<!ENTITY % address-model
"(%address.class; | %address-link.class;)*" >
<!-- ADDRESS/CONTACT INFORMATION -->
<!-- Wrapper element for contact information such
as address, phone, fax, email, url, country,
etc. -->
<!ELEMENT address %address-model; >
<!-- id Unique identifier so the element may be
referenced -->
<!ATTLIST address
id ID #IMPLIED >
<!-- ADDRESS LINE ELEMENTS -->
<!-- Elements for use in the <addr-line> element-->
<!ENTITY % addr-line-elements
"%simple-text;" >
<!-- ADDRESS LINE -->
<!-- One line in an address -->
<!-- Conversion Note: If the address is
undifferentiated data characters, the entire
address may be inside one of these elements.
-->
<!ELEMENT addr-line (#PCDATA %addr-line-elements;)* >
<!-- COUNTRY: IN AN ADDRESS -->
<!ELEMENT country (#PCDATA) >
<!-- EMAIL ADDRESS ELEMENTS -->
<!-- Elements to be mixed with #PCDATA inside the
<email> element -->
<!ENTITY % email-elements
" " >
<!-- EMAIL ADDRESS -->
<!ELEMENT email (#PCDATA %email-elements;)* >
<!-- xlink:href Provides an address or identifier of the
object to which the link points, for
example a URI or a filename -->
<!ATTLIST email
%might-link-atts; >
<!-- FAX NUMBER ELEMENTS -->
<!-- The elements that can be included along with
data characters inside the content model of
a <fax> -->
<!ENTITY % fax-elements
"%just-rendition; " >
<!-- FAX NUMBER: IN AN ADDRESS -->
<!ELEMENT fax (#PCDATA %fax-elements;)* >
<!-- INSTITUTION NAME ELEMENTS -->
<!-- Elements for use in the <institution>
element -->
<!ENTITY % institution-elements
"| %break.class; | %emphasis.class; |
%subsup.class;" >
<!-- INSTITUTION NAME: IN AN ADDRESS -->
<!-- Name of a institution or organization such as
a university or corporation -->
<!ELEMENT institution (#PCDATA %institution-elements;)* >
<!-- id Unique identifier so the element may be
referenced
xlink:href Provides an address or identifier of the
object to which the link points, for
example a URI or a filename -->
<!ATTLIST institution
id ID #IMPLIED
%might-link-atts; >
<!-- PHONE NUMBER ELEMENTS -->
<!-- The elements that can be included along with
data characters inside the content model of
a <phone number>
DESIGN NOTE: All inline mixes begin with an
OR bar, but since %just-rendition; is an
inline mix, the OR bar is already there. -->
<!ENTITY % phone-elements
"%just-rendition;" >
<!-- PHONE NUMBER: IN AN ADDRESS -->
<!-- A callable phone number in some telephone or
wireless system somewhere in the world.
Typically includes area code; may include
country extension, especially for non-US. -->
<!ELEMENT phone (#PCDATA %phone-elements;)* >
<!-- URI ELEMENTS -->
<!-- The elements that can be included along with
data characters inside the content model of
a <uri>
Design Note: This PE begins with an OR
bar because %just-rendition; begins with an
OR bar. -->
<!ENTITY % uri-elements
"%just-rendition;" >
<!-- URI -->
<!-- URI such as a URL that may be used as a
live link, typically naming a website, such
as:
<url>http://www.mulberrytech.com</url>
Alternatively the element content may name
the URL, e.g., "Mulberry's Website" and the
"xlink:href" attribute may hold the real
URL.
<url xlink:href="http://www.mulberrytech.
com">Mulberry's Website</url>
Related Elements: A URI used outside the
context of an address of contributor should
be tagged as an External Link <ext-link> -->
<!ELEMENT uri (#PCDATA %uri-elements;)* >
<!ATTLIST uri
%might-link-atts; >
<!-- ============================================================= -->
<!-- DATE ELEMENTS (PUBLICATION HISTORY) -->
<!-- ============================================================= -->
<!-- DATE -->
<!-- The elements <day>, <month>, and <year> should
ALWAYS be numeric values. The date may be
represented as a string in <string-date>, but
the numeric values should be present whenever
possible. -->
<!ELEMENT date %date-model; >
<!-- date-type Attribute should only be used if the date
is one of the known types, otherwise omit
the attribute. Values are:
accepted - Date manuscript was
accepted
received - Date manuscript received
rev-request - Date revisions were
requested or manuscript
was returned
rev-recd - Date revised manuscript
was received -->
<!ATTLIST date
date-type (%date-types;) #IMPLIED >
<!-- DAY -->
<!-- The numeric value of a day of the month, used
in both article metadata and inside a citation,
in two digits as it would be stated in the "DD"
in an international date format YYYY-MM-DD, for
example "03", "25". -->
<!ELEMENT day (#PCDATA) >
<!-- MONTH -->
<!-- Names one of the months of the year. Used in
both article metadata and inside a citation,
this element may contain a full month
"December", an abbreviation "Dec", or,
preferably, a numeric month such as "12".
Authoring and Conversion Note: For ease in
comparisons and searching, many archives
prefer that months be converted to numeric
Suggested values:
1 = January
2 = February
3 = March, etc. -->
<!ELEMENT month (#PCDATA) >
<!-- SEASON -->
<!-- Season of publication, such as "Spring".
Used in both article metadata and inside a
citation -->
<!ELEMENT season (#PCDATA) >
<!-- YEAR -->
<!-- Year of publication, which should be expressed
as a 4-digit number: "1776" or "1924" -->
<!ELEMENT year (#PCDATA) >
<!-- STRING DATE ELEMENTS -->
<!-- The elements that can be included along with
data characters inside the content model of
the <string-date> element -->
<!ENTITY % string-date-elements
" | %date-parts.class;" >
<!-- DATE AS A STRING -->
<!-- This is a representation of the date as a
string. Usually used for dates for which
months and years are not given, but may be
used for any date as a string (i.e., "January,
2001" "Fall 2001" "March 11, 2001".
It is better practice to tag the year
and month as numbers with a date such
as "January, 2001" or "March 11, 2001". -->
<!ELEMENT string-date (#PCDATA %string-date-elements;)* >
<!-- ============================================================= -->
<!-- PERSON'S NAME ELEMENTS (BIBLIOGRAPHIC) -->
<!-- ============================================================= -->
<!-- STRING NAME ELEMENTS -->
<!-- The elements that can be included along with
data characters inside the content model of
the <string-name> element -->
<!ENTITY % string-name-elements
" | %person-name.class;" >
<!-- NAME OF PERSON (UNSTRUCTURED) -->
<!-- Wrapper element for personal names where the
stricter format of the <name> element cannot
be followed. This is a very loose element,
allowing data characters, generated text,
and any or all of the naming elements.
Authoring or Conversion Note: Use this
element if the name parts are unknown or
untagged. -->
<!ELEMENT string-name (#PCDATA %string-name-elements;)* >
<!-- NAME OF PERSON (STRUCTURED) -->
<!-- Wrapper element for personal names.
Authoring or Conversion Note: If the name
parts are unknown or untagged, names should
be placed within the <string-name> element.
-->
<!ELEMENT name (surname, given-names?, prefix?, suffix?) >
<!-- name-style Used for choosing an inversion algorithm or
for sorting or other processing functions. The
three values and approximate meanings are:
Value Display Sort/Inversion
western given family family given
eastern family given family given
islensk given patronymic given, patronymic
-->
<!ATTLIST name
name-style (western | eastern | islensk) "western" >
<!-- SURNAME ELEMENTS -->
<!-- The elements that can be included along with
data characters inside the content model of
a <surname>
Design Note: This PE begins with an OR
bar because %just-rendition; begins with an
OR bar. -->
<!ENTITY % surname-elements
"%just-rendition; " >
<!-- SURNAME -->
<!-- The surname of an individual. If there is
only one name, for example, "Cher" or
"Pele", that is considered to be a surname
for consistency purposes. -->
<!ELEMENT surname (#PCDATA %surname-elements;)* >
<!ATTLIST surname
%surname-atts; >
<!-- GIVEN (FIRST) NAMES ELEMENTS -->
<!-- The elements that can be included along with
data characters inside the content model of
a <given-names> -->
<!ENTITY % given-names-elements
"%just-rendition;" >
<!-- GIVEN (FIRST) NAMES -->
<!-- Includes all given names for a person, such
as the first name, middle names, maiden
name if used as part of the married name,
etc.) -->
<!ELEMENT given-names (#PCDATA %given-names-elements;)* >
<!ATTLIST given-names
%given-names-atts; >
<!-- PREFIX ELEMENTS -->
<!-- The elements that can be included along with
data characters inside the content model of
a <prefix>
Design Note: This PE begins with an OR
bar because %just-rendition; begins with an
OR bar. -->
<!ENTITY % prefix-elements
"%just-rendition;" >
<!-- PREFIX -->
<!-- Honorifics or other qualifiers that usually
precede the surname, for example, Professor,
Rev., President, Senator, Dr., Sir, The
Honorable, et al. -->
<!ELEMENT prefix (#PCDATA %prefix-elements;)* >
<!-- SUFFIX ELEMENTS -->
<!-- The elements that can be included along with
data characters inside the content model of
a <suffix>
Design Note: This PE begins with an OR bar,
it is inside %just-rendition; -->
<!ENTITY % suffix-elements
"%just-rendition;" >
<!-- SUFFIX -->
<!-- Text used as a suffix to a person's name, for
example: Sr. Jr. III, 3rd -->
<!ELEMENT suffix (#PCDATA %suffix-elements;)* >
<!-- ============================================================= -->
<!-- EXTERNAL LINK ELEMENTS -->
<!-- ============================================================= -->
<!-- EXTERNAL LINK ELEMENTS -->
<!-- The elements that can be included along with
data characters inside the content model of
an <ext-link>
DESIGN NOTE: All inline mixes begin with an
OR bar, but since %link-elements; is an inline
mix, the OR bar is already there. -->
<!ENTITY % ext-link-elements
"%link-elements;" >
<!-- EXTERNAL LINK -->
<!-- Link to an external file, such as Medline,
Genbank, etc. Linking may be accomplished
using the XLink linking attributes. -->
<!ELEMENT ext-link (#PCDATA %ext-link-elements;)* >
<!-- ext-link-type
Type of external link. Use this attribute
if the type of external link is one of the
ones below or another named type.
Suggested values include:
aoi Astronomical Object Identifier
doi Digital Object Identifier
ec Enzyme nomenclature - see
http://www.chem.qmw.ac.uk/iubmb/enzyme/
email An email message
ftp File transfer protocol
gen GenBank identifier
genpept Translated Protein-encoding
sequence Database
highwire HighWire press intrajournal
medline Medline or pubmed id
pdb Protein data bank. See
http://www.rcsb.org/pdb/
pgr Plant gene register. See
http://www.tarweed.com/pgr/
pir Protein Information Resource
see http://pir.georgetown.edu
pirdb Protein Information Resource
see http://pir.georgetown.edu
pmc Used to link between articles
in PubMed Central access is
PMID
sprot Swiss-Prot. See
http://www.ebi.ac.uk/swissprot/
uri Website or web service
id Unique identifier so the element may be
referenced
xlink:href Provides an address or identifier of the
object to which the link points, for
example a URI or a filename -->
<!ATTLIST ext-link
%ext-link-atts; >
<!-- ============================================================= -->
<!-- STRUCTURAL ELEMENTS -->
<!-- ============================================================= -->
<!-- ATTRIBUTION ELEMENTS -->
<!-- The elements that can be included along with
data characters inside the content model of
an attribution
DESIGN NOTE: All inline mixes begin with an
OR bar, but since %simple-phrase; is an
inline mix, the OR bar is already there. -->
<!ENTITY % attrib-elements
"%emphasized-text;" >
<!-- ATTRIBUTION -->
<!-- Source, author, formal thanks, or other
information (other than copyright material)
concerning the origins of an extract, a poem
<verse-group> or similar element.
Formatting Note: Typically displayed on
a separate line (or lines, following the
material it concerns, inheriting that
material's margins. -->
<!ELEMENT attrib (#PCDATA %attrib-elements;)* >
<!-- STRUCTURAL TITLE ELEMENTS -->
<!-- The elements that can be included along with
data characters inside the content model of
the <title> element
DESIGN NOTE: All inline mixes begin with an
OR bar, but since %simple-phrase; is an
inline mix, the OR bar is already there. -->
<!ENTITY % struct-title-elements
"%simple-phrase; | %break.class;" >
<!-- TITLE -->
<!-- Heading or title for a structural element
such as a Section, Figure, Boxed Text, etc.-->
<!ELEMENT title (#PCDATA %struct-title-elements;)* >
<!-- LABEL ELEMENTS -->
<!-- The elements that can be included along with
data characters inside the content model of
the <label> element -->
<!ENTITY % label-elements
"| %emphasis.class; | %inline-display.class; |
%inline-math.class; | %subsup.class;" >
<!-- LABEL OF A FIGURE, REFERENCE, ETC. -->
<!-- The number and any prefix word that comes
before, for example, the caption of a Figure,
such as "Figure 3." or "Exhibit 2.". This
element can be used to preserve the prefix
number or label of an element, for example
for a reference or citation "25." or
"[Lapeyre 2002]". This can be useful when
reconstructing untagged cross references. -->
<!ELEMENT label (#PCDATA %label-elements;)* >
<!-- ============================================================= -->
<!-- RELATED ARTICLE ELEMENTS -->
<!-- ============================================================= -->
<!-- RELATED ARTICLE ELEMENTS -->
<!-- Elements allowed inside <related-article> -->
<!ENTITY % related-article-elements
"| %emphasis.class; |%references.class; |
%subsup.class;" >
<!-- RELATED ARTICLE INFORMATION -->
<!-- Wrapper element, used as a container for
text links to a related article, possibly
accompanied by a very brief description
such as "errata (correction)".
Remarks: This element is slightly overloaded
in that it has 2 uses, one inside the article
metadata to name one or more related articles
and as part of the link class, which can
occur many places in textual content.
This allows all such references, to
companion articles within the same journal,
to a previous part of a multi-part article,
to a news item that summarizes the article,
to the article for which this article is
a correction or addendum, etc. wherever
these occur in the article. -->
<!ELEMENT related-article
(#PCDATA %related-article-elements;)* >
<!-- id Unique identifier so the element may be
referenced
alt-form-of
Exactly like the "alt-form-of" attribute
used with <graphic>, this is an IDREF
attribute which points to the ID of another
<related-article> in the same document
rather than to an external file.
related-article-type
addendum Additional material for an
article, generated too late
to be added to the main text
commentary-article
Used in an commentary or
editorial to link to the
article on which it is
commenting
companion Used in an article to link
to a companion (related
or sibling article)
corrected-article
Used in a correction to link
to the article being
corrected. Sometimes called
erratum.
in-this-issue Related article in the same
journal issue
letter A letter to the publication
or a reply to such a
letter
commentary Used in an article to link
to its associated commentary
or editorial
correction-forward
Used in an article to link
forward to its associated
correction (rarely used)
retracted-article
Used in a retraction to link
to the article being retracted
retraction-forward
Used in an article to link
forward to its associated
retraction (rare)
vol Volume of the journal in which the related
article exists. The scope is limited to
the journal; in which the current article
resides.
page Page number of the related article. Scope
is limited to the volume of the journal in
which the current article resides. The
values should be a first page or a page
range.
xlink:href Provides an address or identifier of the
object to which the link points, for
example a URI or a filename. -->
<!ATTLIST related-article
%related-article-atts; >
<!-- ============================================================= -->
<!-- FRONT MATTER/BACK MATTER ELEMENTS -->
<!-- ============================================================= -->
<!-- ACKNOWLEDGMENTS MODEL -->
<!-- Content model for the <ack> element -->
<!ENTITY % ack-model "%sec-opt-title-model;" >
<!-- ACKNOWLEDGMENTS -->
<!ELEMENT ack %ack-model; >
<!-- id Unique identifier so the element may be
referenced
content-type
Identification of the subject, type of
content, or reason that this word or phrase
is considered semantically special, as a
means of preserving the semantic intent of
the original tagging. -->
<!ATTLIST ack
id ID #IMPLIED
content-type
CDATA #IMPLIED >
<!-- BIOGRAPHY MODEL -->
<!-- Content model for the <bio> element -->
<!ENTITY % bio-model "(title?, (%just-para.class;)+ ) " >
<!-- BIOGRAPHY -->
<!-- Sort biography of a person, usually the
author
Authoring Note: The "xlink:href" attribute
may be used to point to a graphic of the
author or to his/her website, etc. -->
<!ELEMENT bio %bio-model; >
<!-- id Unique identifier so the element may be
referenced
rid Points to the identifier of an author or
authors
xlink:href Provides an address or identifier of the
object to which the link points, for
example a URI or a filename. -->
<!ATTLIST bio
%bio-atts; >
<!-- NOTES MODEL -->
<!-- Content model for the <notes> element -->
<!ENTITY % notes-model "%sec-opt-title-model;" >
<!-- NOTES -->
<!-- A container element for the notes that may
appear at the end of an Article or at the
end of a Table. For example, a typical
end-of-article note is a "Note in Proof".
A Note in Proof contains late-breaking news
items or other material produced while the
article was being typeset or was otherwise
in production, that therefore happened too
late to be included in the text of the
article. This is typically NOT peer-reviewed
content and citations to other material is
usually just integrated into the text, not
listed separately in a References List. -->
<!ELEMENT notes %notes-model; >
<!-- id Unique identifier so the element may be
referenced
notes-type To identify the type of note, if the type can
be/has been identified, for example,
"note-in-proof" -->
<!ATTLIST notes
%notes-atts; >
<!-- ============================================================= -->
<!-- ACCESSIBILITY ELEMENTS -->
<!-- ============================================================= -->
<!-- ALTERNATE TITLE TEXT FOR A FIGURE, ETC. -->
<!-- Short phrase used to display or pronounce
as an alternative to providing the full
graphic for accessibility display or
graphic-limited websites or devices. For
example, <alt-text> may be used to display
"behind" a figure or graphic.
Authoring and Conversion Note: Not to be used
as a replacement for <caption>. -->
<!ELEMENT alt-text (#PCDATA) >
<!-- id Unique identifier so the element may be
referenced
xml:lang The language in which the value of the
element is expressed. Recommended best
practice is to use values as defined in
RFC 1766, typically 2-letter language
codes such as "FR" (French), "EN" (English),
and "DE" (German). These values are NOT
case sensitive, so "EN" = "en". The values
may include hyphenated differentiations such
as "EN-AU" (Australian English) and "EN-US"
(United States English). -->
<!ATTLIST alt-text
id ID #IMPLIED
xml:lang NMTOKEN #IMPLIED >
<!-- LONG DESCRIPTION ELEMENTS -->
<!-- Elements to be mixed with data characters
inside the <long-desc> element -->
<!ENTITY % long-desc-elements
" " >
<!-- LONG DESCRIPTION -->
<!-- Description or summary of the content of a
graphical object, table, or textual object
such as a text box, used by some systems to
make the object accessible, even to people
or systems that cannot read/see/display the
object.
Authoring and Conversion Note: Not to be used
as a replacement for <caption>. -->
<!ELEMENT long-desc (#PCDATA %long-desc-elements;) >
<!-- id Unique identifier so the element may be
referenced
xml:lang The language in which the value of the
element is expressed. Recommended best
practice is to use values as defined in
RFC 1766, typically 2-letter language
codes such as "FR" (French), "EN" (English),
and "DE" (German). These values are NOT
case sensitive, so "EN" = "en". The values
may include hyphenated differentiations such
as "EN-AU" (Australian English) and "EN-US"
(United States English). -->
<!ATTLIST long-desc
id ID #IMPLIED
xml:lang NMTOKEN #IMPLIED >
<!-- DEFINITION LIST: DEFINITION MODEL -->
<!-- Content model for the <def> element -->
<!ENTITY % def-model "((%just-para.class;)+ )" >
<!-- DEFINITION LIST: DEFINITION -->
<!-- Used in two senses:
1) The definition, description, or other
explanation of the word, phrase, or picture
of a 2-part or definition list
2) The definition or expansion of an
abbreviation or acronym <abbrev> -->
<!ELEMENT def %def-model; >
<!-- id Unique identifier so the element may be
referenced
rid Points to the identifier of a term,
so that a term and definition may be linked
-->
<!ATTLIST def
rid IDREFS #IMPLIED
id ID #IMPLIED >
<!-- ============================================================= -->
<!-- CUSTOMIZED METADATA ELEMENTS -->
<!-- ============================================================= -->
<!-- CUSTOMIZED METADATA WRAPPER MODEL -->
<!-- Content model for the <custom-meta-wrap>
element -->
<!ENTITY % custom-meta-wrap-model
"(custom-meta+)" >
<!-- METADATA DATA NAME FOR CUSTOM METADATA -->
<!-- Some DTDs and schemas allow for metadata
above and beyond that which can be specified
by this DTD. This element is a wrapper
element used to contain all these additional
metadata elements. -->
<!ELEMENT custom-meta-wrap
%custom-meta-wrap-model; >
<!-- CUSTOMIZED METADATA MODEL -->
<!-- Content model for the <custom-meta> element-->
<!ENTITY % custom-meta-model
"(meta-name, meta-value)" >
<!-- CUSTOM METADATA -->
<!-- Some DTDs and schemas allow for metadata
above and beyond that which can be specified
by this DTD. This element is used to capture
metadata elements that have not been defined
explicitly in the models for this DTD, so
that the intellectual content will not be lost.
REMARKS: The <custom-meta> element allows
for an infinite number of name/value pairs,
with few constraints on the length or
content of the value. This element will
probably be used for special cases, product-
specific material, or other unusual
metadata, for example the journal-history
information preserved in at least one
publisher's DTD. -->
<!ELEMENT custom-meta %custom-meta-model; >
<!-- METADATA DATA NAME ELEMENTS -->
<!-- Elements that may be used, along with data
characters, inside the <meta-name> element
DESIGN NOTE: All inline mixes begin with an
OR bar, but since %simple-phrase; is an
inline mix, the OR bar is already there. -->
<!ENTITY % meta-name-elements
"%simple-phrase;" >
<!-- METADATA DATA NAME FOR CUSTOM METADATA -->
<!-- Some DTDs and schemas allow for metadata
above and beyond that which can be specified
by this DTD. The <custom-meta> element
allow for an infinite number of name/value
pairs, with few constraints on the length or
content of the value. This element contains
the name of the metadata field. -->
<!ELEMENT meta-name (#PCDATA %meta-name-elements;)* >
<!-- METADATA DATA VALUE ELEMENTS -->
<!-- Elements that may be used, along with data
characters, inside the <meta-value> element
DESIGN NOTE: All inline mixes begin with an
OR bar, but since %simple-phrase; is an
inline mix, the OR bar is already there. -->
<!ENTITY % meta-value-elements
"%simple-phrase;" >
<!-- METADATA DATA NAME FOR CUSTOM METADATA -->
<!-- Some DTDs and schemas allow for metadata
above and beyond that which can be specified
by this DTD. The <custom-meta> element
allow for an infinite number of name/value
pairs, with few constraints on the length or
content of the value. This element contains
the value of the metadata field that is named
by the <meta-name> element. -->
<!ELEMENT meta-value (#PCDATA %meta-value-elements;)* >
<!-- ============================================================= -->
<!-- GENERATED TEXT OR PUNCTUATION -->
<!-- ============================================================= -->
<!-- X ELEMENTS -->
<!-- Elements for use inside the <x> element -->
<!ENTITY % x-elements " " >
<!-- X - GENERATED TEXT AND PUNCTUATION -->
<!-- A container element to hold punctuation or
other generated text, typically when 1) an
archive decides not to have any text
generated and thus to pre-generate such
things as commas or semicolons between
keywords or 2) when an archive receives text
with <x> tags embedded and wishes to retain
them.
Remarks: This element is called "x" for
historical reasons, since DTDs that use an
element for generated punctuation have
typically called it that. -->
<!ELEMENT x (#PCDATA %x-elements;)* >
<!-- ================== End Common (Shared) Elements Module ====== -->
|