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
|
<pre>Internet Architecture Board (IAB) J. Hildebrand, Ed.
Request for Comments: 7992 Mozilla
Category: Informational P. Hoffman
ISSN: 2070-1721 ICANN
December 2016
<span class="h1">HTML Format for RFCs</span>
Abstract
In order to meet the evolving needs of the Internet community, the
canonical format for RFCs is changing from a plain-text, ASCII-only
format to an XML format that will, in turn, be rendered into several
publication formats. This document defines the HTML format that will
be rendered for an RFC or Internet-Draft.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for informational purposes.
This document is a product of the Internet Architecture Board (IAB)
and represents information that the IAB has deemed valuable to
provide for permanent record. It represents the consensus of the
Internet Architecture Board (IAB). Documents approved for
publication by the IAB are not a candidate for any level of Internet
Standard; see <a href="./rfc7841#section-2">Section 2 of RFC 7841</a>.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
<a href="http://www.rfc-editor.org/info/rfc7992">http://www.rfc-editor.org/info/rfc7992</a>.
Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
Provisions Relating to IETF Documents
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document.
<span class="grey">Hildebrand & Hoffman Informational [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
Table of Contents
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
<a href="#section-2">2</a>. Requirements for the HTML Format . . . . . . . . . . . . . . <a href="#page-5">5</a>
<a href="#section-2.1">2.1</a>. Requirements for Accessibility . . . . . . . . . . . . . <a href="#page-6">6</a>
<a href="#section-3">3</a>. HTML Version . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-4">4</a>. HTML Syntax . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
<a href="#section-5">5</a>. Common Items . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-5.1">5.1</a>. IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-5.2">5.2</a>. Pilcrows . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
<a href="#section-6">6</a>. Front Matter . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-6.1">6.1</a>. DOCTYPE . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-6.2">6.2</a>. Root Element . . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-6.3">6.3</a>. <head> Element . . . . . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-6.3.1">6.3.1</a>. Charset Declaration . . . . . . . . . . . . . . . . . <a href="#page-9">9</a>
<a href="#section-6.3.2">6.3.2</a>. Document Title . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-6.3.3">6.3.3</a>. Document Metadata . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-6.3.4">6.3.4</a>. Link to XML Source . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-6.3.5">6.3.5</a>. Link to License . . . . . . . . . . . . . . . . . . . <a href="#page-10">10</a>
<a href="#section-6.3.6">6.3.6</a>. Style . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
<a href="#section-6.3.7">6.3.7</a>. Links . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-11">11</a>
<a href="#section-6.4">6.4</a>. Page Headers and Footers . . . . . . . . . . . . . . . . <a href="#page-12">12</a>
<a href="#section-6.5">6.5</a>. Document Information . . . . . . . . . . . . . . . . . . <a href="#page-13">13</a>
<a href="#section-6.6">6.6</a>. Table of Contents . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
<a href="#section-7">7</a>. Main Body . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
<a href="#section-8">8</a>. Back Matter . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
<a href="#section-8.1">8.1</a>. Index . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-14">14</a>
<a href="#section-8.1.1">8.1.1</a>. Index Contents . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
<a href="#section-8.1.2">8.1.2</a>. Index Letters . . . . . . . . . . . . . . . . . . . . <a href="#page-15">15</a>
<a href="#section-8.1.3">8.1.3</a>. Index Items . . . . . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
<a href="#section-8.1.4">8.1.4</a>. Index Subitems . . . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
<a href="#section-8.2">8.2</a>. Authors' Addresses Section . . . . . . . . . . . . . . . <a href="#page-17">17</a>
<a href="#section-8.3">8.3</a>. Document Information . . . . . . . . . . . . . . . . . . <a href="#page-18">18</a>
<a href="#section-9">9</a>. Elements . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-18">18</a>
<a href="#section-9.1">9.1</a>. <abstract> . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-18">18</a>
<a href="#section-9.2">9.2</a>. <address> . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-19">19</a>
<a href="#section-9.3">9.3</a>. <annotation> . . . . . . . . . . . . . . . . . . . . . . <a href="#page-19">19</a>
<a href="#section-9.4">9.4</a>. <area> . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-19">19</a>
<a href="#section-9.5">9.5</a>. <artwork> . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-20">20</a>
<a href="#section-9.5.1">9.5.1</a>. Text Artwork . . . . . . . . . . . . . . . . . . . . <a href="#page-20">20</a>
<a href="#section-9.5.2">9.5.2</a>. SVG Artwork . . . . . . . . . . . . . . . . . . . . . <a href="#page-20">20</a>
<a href="#section-9.5.3">9.5.3</a>. Other Artwork . . . . . . . . . . . . . . . . . . . . <a href="#page-21">21</a>
<a href="#section-9.6">9.6</a>. <aside> . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-21">21</a>
<a href="#section-9.7">9.7</a>. <author> . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-21">21</a>
<a href="#section-9.7.1">9.7.1</a>. Authors in Document Information . . . . . . . . . . . <a href="#page-22">22</a>
<a href="#section-9.7.2">9.7.2</a>. Authors of This Document . . . . . . . . . . . . . . <a href="#page-22">22</a>
<a href="#section-9.7.3">9.7.3</a>. Authors of References . . . . . . . . . . . . . . . . <a href="#page-24">24</a>
<a href="#section-9.8">9.8</a>. <back> . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-24">24</a>
<span class="grey">Hildebrand & Hoffman Informational [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<a href="#section-9.9">9.9</a>. <<a href="https://www.rfc-editor.org/bcp/bcp14">bcp14</a>> . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-25">25</a>
<a href="#section-9.10">9.10</a>. <blockquote> . . . . . . . . . . . . . . . . . . . . . . <a href="#page-25">25</a>
<a href="#section-9.11">9.11</a>. <boilerplate> . . . . . . . . . . . . . . . . . . . . . . <a href="#page-26">26</a>
<a href="#section-9.12">9.12</a>. <br> . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-26">26</a>
<a href="#section-9.13">9.13</a>. <city> . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-26">26</a>
<a href="#section-9.14">9.14</a>. <code> . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-26">26</a>
<a href="#section-9.15">9.15</a>. <country> . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-26">26</a>
<a href="#section-9.16">9.16</a>. <cref> . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-27">27</a>
<a href="#section-9.17">9.17</a>. <date> . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-27">27</a>
<a href="#section-9.18">9.18</a>. <dd> . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-27">27</a>
<a href="#section-9.19">9.19</a>. <displayreference> . . . . . . . . . . . . . . . . . . . <a href="#page-27">27</a>
<a href="#section-9.20">9.20</a>. <dl> . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-27">27</a>
<a href="#section-9.21">9.21</a>. <dt> . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-27">27</a>
<a href="#section-9.22">9.22</a>. <em> . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-28">28</a>
<a href="#section-9.23">9.23</a>. <email> . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-28">28</a>
<a href="#section-9.24">9.24</a>. <eref> . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-28">28</a>
<a href="#section-9.25">9.25</a>. <figure> . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-28">28</a>
<a href="#section-9.26">9.26</a>. <front> . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-28">28</a>
<a href="#section-9.27">9.27</a>. <iref> . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-29">29</a>
<a href="#section-9.28">9.28</a>. <keyword> . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-29">29</a>
<a href="#section-9.29">9.29</a>. <li> . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-29">29</a>
<a href="#section-9.30">9.30</a>. <link> . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-29">29</a>
<a href="#section-9.31">9.31</a>. <middle> . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-29">29</a>
<a href="#section-9.32">9.32</a>. <name> . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-29">29</a>
<a href="#section-9.33">9.33</a>. <note> . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-30">30</a>
<a href="#section-9.34">9.34</a>. <ol> . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-30">30</a>
<a href="#section-9.34.1">9.34.1</a>. Percent Styles . . . . . . . . . . . . . . . . . . . <a href="#page-30">30</a>
<a href="#section-9.34.2">9.34.2</a>. Standard Styles . . . . . . . . . . . . . . . . . . <a href="#page-30">30</a>
<a href="#section-9.35">9.35</a>. <organization> . . . . . . . . . . . . . . . . . . . . . <a href="#page-31">31</a>
<a href="#section-9.36">9.36</a>. <phone> . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-31">31</a>
<a href="#section-9.37">9.37</a>. <postal> . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-31">31</a>
<a href="#section-9.38">9.38</a>. <postalLine> . . . . . . . . . . . . . . . . . . . . . . <a href="#page-32">32</a>
<a href="#section-9.39">9.39</a>. <refcontent> . . . . . . . . . . . . . . . . . . . . . . <a href="#page-32">32</a>
<a href="#section-9.40">9.40</a>. <reference> . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-33">33</a>
<a href="#section-9.41">9.41</a>. <referencegroup> . . . . . . . . . . . . . . . . . . . . <a href="#page-33">33</a>
<a href="#section-9.42">9.42</a>. <references> . . . . . . . . . . . . . . . . . . . . . . <a href="#page-34">34</a>
<a href="#section-9.43">9.43</a>. <region> . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-34">34</a>
<a href="#section-9.44">9.44</a>. <relref> . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-35">35</a>
<a href="#section-9.44.1">9.44.1</a>. displayFormat='of' . . . . . . . . . . . . . . . . . <a href="#page-35">35</a>
<a href="#section-9.44.2">9.44.2</a>. displayFormat='comma' . . . . . . . . . . . . . . . <a href="#page-35">35</a>
<a href="#section-9.44.3">9.44.3</a>. displayFormat='parens' . . . . . . . . . . . . . . . <a href="#page-36">36</a>
<a href="#section-9.44.4">9.44.4</a>. displayFormat='bare' . . . . . . . . . . . . . . . . <a href="#page-36">36</a>
<a href="#section-9.45">9.45</a>. <rfc> . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-37">37</a>
<a href="#section-9.46">9.46</a>. <section> . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-37">37</a>
<a href="#section-9.47">9.47</a>. <seriesInfo> . . . . . . . . . . . . . . . . . . . . . . <a href="#page-37">37</a>
<a href="#section-9.48">9.48</a>. <sourcecode> . . . . . . . . . . . . . . . . . . . . . . <a href="#page-38">38</a>
<a href="#section-9.49">9.49</a>. <street> . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-38">38</a>
<a href="#section-9.50">9.50</a>. <strong> . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-38">38</a>
<span class="grey">Hildebrand & Hoffman Informational [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<a href="#section-9.51">9.51</a>. <sub> . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-38">38</a>
<a href="#section-9.52">9.52</a>. <sup> . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-38">38</a>
<a href="#section-9.53">9.53</a>. <t> . . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-38">38</a>
<a href="#section-9.54">9.54</a>. <table> . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-39">39</a>
<a href="#section-9.55">9.55</a>. <tbody> . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-39">39</a>
<a href="#section-9.56">9.56</a>. <td> . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-39">39</a>
<a href="#section-9.57">9.57</a>. <tfoot> . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-39">39</a>
<a href="#section-9.58">9.58</a>. <th> . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-39">39</a>
<a href="#section-9.59">9.59</a>. <thead> . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-39">39</a>
<a href="#section-9.60">9.60</a>. <title> . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-39">39</a>
<a href="#section-9.61">9.61</a>. <tr> . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-39">39</a>
<a href="#section-9.62">9.62</a>. <tt> . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-40">40</a>
<a href="#section-9.63">9.63</a>. <ul> . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-40">40</a>
<a href="#section-9.64">9.64</a>. <uri> . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-40">40</a>
<a href="#section-9.65">9.65</a>. <workgroup> . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-40">40</a>
<a href="#section-9.66">9.66</a>. <xref> . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-40">40</a>
<a href="#section-9.67">9.67</a>. <svg xmlns='http://www.w3.org/2000/svg'> . . . . . . . . <a href="#page-41">41</a>
<a href="#section-10">10</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-41">41</a>
<a href="#section-11">11</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-41">41</a>
<a href="#section-11.1">11.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-41">41</a>
<a href="#section-11.2">11.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-42">42</a>
IAB Members at the Time of Approval . . . . . . . . . . . . . . . <a href="#page-43">43</a>
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-43">43</a>
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-43">43</a>
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
As described in [<a href="./rfc7990" title=""RFC Format Framework"">RFC7990</a>], the RFC Series is changing. One of those
changes includes the RFC Editor publishing a non-canonical HTML
version of RFCs.
This document describes the HTML format that will be used as one of
the publication formats for the RFC Series. It defines a strict
subset of HTML appropriate for RFC Series documents. The visual
layout of the document will be defined through a cascading style
sheet (CSS) [<a href="#ref-W3C.REC-CSS2-20110607">W3C.REC-CSS2-20110607</a>]. The CSS will be included in the
HTML file but will be described in [<a href="./rfc7993" title=""Cascading Style Sheets (CSS) Requirements for RFCs"">RFC7993</a>].
The details (particularly any vocabularies) described in this
document are expected to change based on experience gained in
implementing the new publication toolsets. Revised documents will be
published capturing those changes as the toolsets are completed.
Other implementers must not expect those changes to remain backwards
compatible with the details described in this document.
<span class="grey">Hildebrand & Hoffman Informational [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Requirements for the HTML Format</span>
This section lists the design requirements used to create the HTML
format described in this document. These requirements build on those
found in [<a href="./rfc6949" title=""RFC Series Format Requirements and Future Development"">RFC6949</a>]. Many of these requirements are naturally
fulfilled by using the output of the preparation tool [<a href="./rfc7998" title=""xml2rfc"">RFC7998</a>].
o The HTML has to render correctly on a list of browser versions
that the RFC Editor will keep up to date outside of this document.
o The format will consist of a subset of HTML deemed to be widely
implemented by common browsers at the time the specification is
created, likely to continue to be widely implemented, and unlikely
to cause security issues. This will maximize the chances that
future HTML renderers (such as new web browsers) will continue to
produce readable text from the HTML format without the format
needing to be changed frequently.
o These requirements are expected to change in the future to reflect
the expectation that HTML rendering will be required for current
versions of browsers and platforms, while ideally continuing to
render correctly on recent versions of those browsers.
o The HTML documents from the RFC Editor or Internet-Drafts
directory may be re-rendered from the canonical XML format in the
future to ensure the ongoing readability of the documents. The
intent is that any re-rendering would be due to exceptional
circumstances rather than for minor annoyances.
o The HTML must display adequately in at least one text-based
browser. Some consumers of the RFC Series can only access the
documents on text-based terminals.
o The HTML document will be self-contained, without requiring
external files for images, CSS, JavaScript, or the like. This
will allow the HTML file to be moved over various non-HTTP
transports (such as email, FTP, and rsync) without breakage.
o JavaScript will be supported on a limited basis. It will not be
permitted to overwrite or change any text present in the rendered
HTML. It may, on a limited basis, add additional text that
provides post-publication metadata or pointers if warranted. All
such text will be clearly marked as additional.
o The HTML document will allow easy local override of the default
CSS formatting. This will allow users who have a different visual
style that they prefer to make RFCs display with that style
without having to alter the contents of the HTML document. This
<span class="grey">Hildebrand & Hoffman Informational [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
might also be valuable for allowing people with specific
accessibility needs to use a customized CSS.
o HTML tags in documents will rarely have attributes whose only
purpose is to affect the rendered styling, and those will only be
used if it would not be possible to specify that styling in a CSS.
No such attributes are known at this time.
o Both user-defined and auto-generated anchors must be supported and
linkable, with user-defined anchors appearing in an "id"
attribute. Auto-generated anchors will be generated for every
heading, paragraph, and so on, not just those that do not have
user-defined anchors. User-defined anchors may, and auto-
generated anchors will, appear next to paragraphs, figures,
tables, blockquotes, and section titles.
o All sections, subsections, figures, and paragraphs should have
stable numbered link anchors. Additionally, anchors expressed in
the source XML should be exposed as anchors in the HTML output as
well.
o The HTML must make it easy to separate sections along with all of
their subsections into separate files. This will make creating
EPUB documents easier in the future.
o The HTML produced for Internet-Drafts will differ from that
produced by the RFC Editor due to differences in the output from
the prep tool.
o The abstract must be marked up or tagged in a way that popular
search engines will extract it as a summary.
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Requirements for Accessibility</span>
o Normative information must be easily accessible to the following
consumers:
* People with impaired vision, including those that use large
fonts and those that use screen readers
* People with difficulty distinguishing between colors
* People who use devices with small screens, such as cell phones
o Specific instances where goals for accessibility are important in
the design choices of the format have been called out in the text.
<span class="grey">Hildebrand & Hoffman Informational [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
o Note: designing for these consumers does not preclude the use of
features they cannot use, but it does require that key semantic
data not be lost when read using the tools and settings that are
required by a given constituency.
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. HTML Version</span>
The RFC Editor will periodically determine which version of the HTML
specification will be referenced for tools generating the format
defined in this document. The starting version will be that defined
in [<a href="#ref-W3C.REC-html5-20141028">W3C.REC-html5-20141028</a>], commonly known as "HTML5". Although the
HTML specification mandates several of the syntax and structure rules
described in this document, they are called out here for emphasis.
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. HTML Syntax</span>
The processor emitting HTML from the XML source will follow these
rules:
o The HTML output is encoded as UTF-8, as specified in [<a href="./rfc3629" title=""UTF-8, a transformation format of ISO 10646"">RFC3629</a>].
o The document is valid HTML.
o Double quotes (U+0022 QUOTATION MARK: ") are used to quote
attribute values unless the HTML specification forbids quoting a
particular attribute.
o Each logical line is terminated solely with a \n (U+000A: LINE
FEED), otherwise known as "Unix-style" line endings.
o Code points below (U+0020: SPACE) or character entity references
that generate them (e.g. &#9;), other than (U+000A: LINE FEED) may
not be used. Note: this rule explicitly forbids \t (U+0009:
CHARACTER TABULATION), \f (U+000C: FORM FEED), and \r (U+000D:
CARRIAGE RETURN) from appearing in the HTML output.
o Comments in the source XML, if any, will not be copied into the
HTML.
o The HTML output will be pretty-printed, using whatever consistent
rules are deemed best by the developers of the HTML production
tools.
Note: none of these rules affect the rendered output of the HTML, but
they are intended to increase the chance that text comparison tools
(e.g., "diff") that operate on the HTML output are easier to write.
<span class="grey">Hildebrand & Hoffman Informational [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Common Items</span>
This section lists items that are common across multiple parts of the
HTML document.
<span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a>. IDs</span>
HTML elements that are generated from XML elements that include an
"anchor" attribute will use the value of the "anchor" attribute as
the value of the "id" attribute of the corresponding HTML element.
The prep tool produces XML with "anchor" attributes in all elements
that need them. Some HTML constructs (such as <section>) will use
multiple instances of these identifiers.
<span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a>. Pilcrows</span>
Each paragraph, artwork, or sourcecode segment outside of a <figure>
or <table> element will be appended with a space and a "pilcrow"
(U+00B6: PILCROW SIGN), otherwise known as a "paragraph sign". For
the purposes of clarity in ASCII renderings of this document, in this
document pilcrows are rendered as "&para;". The pilcrow will be
linked to the "id" attribute on the XML entity to which it is
associated using an <a> element of class "pilcrow". For example:
<p id="s-1.1-1">
Some paragraph text. <a class="pilcrow" href="#s-1.1-1">&para;</a>
</p>
The pilcrow will normally be invisible unless the element it is
attached to is moused over. The pilcrow will be surrounded by a link
that points to the element it is attached to.
Pilcrows are never included inside a <table> or <figure> element,
since the figure number or table number serves as an adequate link
target.
Elements that might otherwise contain a pilcrow do not get marked
with a pilcrow if they contain one or more child elements that are
marked with a pilcrow. For example:
<blockquote id="s-1.2-1">
<p id="s-1.2-2">Four score and seven years ago our fathers brought
forth on this continent, a new nation, conceived in Liberty, and
dedicated to the proposition that all men are created equal.
<a href="#s-1.2-2" class="pilcrow">&para;</a></p>
<!-- NO pilcrow here -->
</blockquote>
<span class="grey">Hildebrand & Hoffman Informational [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Front Matter</span>
The front matter of the HTML format contains processing information,
metadata of various types, and styling information that applies to
the document as a whole. This section describes HTML that is not
necessarily a direct transform from the XML format. For more details
on each of the tags that generate content in this section, see
<a href="#section-9">Section 9</a>.
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. DOCTYPE</span>
The DOCTYPE of the document is "html", which declares that the
document is compliant with HTML5. The document will start with
exactly this string:
<!DOCTYPE html>
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Root Element</span>
The root element of the document is <html>. This element includes a
"lang" attribute, whose value is a language tag, as discussed in
[<a href="./rfc5646" title=""Tags for Identifying Languages"">RFC5646</a>], that describes the natural language of the document. The
language tag to be included is "en". The class of the <html> element
will be copied verbatim from the XML <rfc> element's <front>
element's <seriesInfo> element's "name" attributes (separated by
spaces; see <a href="./rfc7991#section-2.47.3">Section 2.47.3 of [RFC7991]</a>), allowing CSS to style RFCs
and Internet-Drafts differently from one another (if needed):
<html lang="en" class="RFC">
<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>. <head> Element</span>
The root <html> will contain a <head> element that contains the
following elements, as needed.
<span class="h4"><a class="selflink" id="section-6.3.1" href="#section-6.3.1">6.3.1</a>. Charset Declaration</span>
In order to be correctly processed by browsers that load the HTML
using a mechanism that does not provide a valid content-type or
charset (such as from a local file system using a "file:" URL), the
HTML <head> element contains a <meta> element, whose "charset"
attribute value is "utf-8":
<meta charset="utf-8">
<span class="grey">Hildebrand & Hoffman Informational [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h4"><a class="selflink" id="section-6.3.2" href="#section-6.3.2">6.3.2</a>. Document Title</span>
The contents of the <title> element from the XML source will be
placed inside an HTML <title> element in the header.
<span class="h4"><a class="selflink" id="section-6.3.3" href="#section-6.3.3">6.3.3</a>. Document Metadata</span>
The following <meta> elements will be included:
o author - one each for the each of the "fullname"s and
"asciiFullname"s of all of the <author>s from the <front> of the
XML source
o description - the <abstract> from the XML source
o generator - the name and version number of the software used to
create the HTML
o keywords - comma-separated <keyword>s from the XML source
For example:
<meta name="author" content="Joe Hildebrand">
<meta name="author" content="JOE HILDEBRAND">
<meta name="author" content="Heather Flanagan">
<meta name="description" content="This document defines...">
<meta name="generator" content="xmljade v0.2.4">
<meta name="keywords" content="html,css,rfc">
Note: the HTML <meta> tag does not contain a closing slash.
<span class="h4"><a class="selflink" id="section-6.3.4" href="#section-6.3.4">6.3.4</a>. Link to XML Source</span>
The <head> element contains a <link> tag, with "rel" attribute of
"alternate", "type" attribute of "application/rfc+xml", and "href"
attribute pointing to the prepared XML source that was used to
generate this document.
<link rel="alternate" type="application/rfc+xml" href="source.xml">
<span class="h4"><a class="selflink" id="section-6.3.5" href="#section-6.3.5">6.3.5</a>. Link to License</span>
The <head> element contains a <link> tag, with "rel" attribute of
"license" and "href" attribute pointing to the an appropriate
copyright license for the document.
<link rel="license"
href="https://trustee.ietf.org/trust-legal-provisions.html">
<span class="grey">Hildebrand & Hoffman Informational [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h4"><a class="selflink" id="section-6.3.6" href="#section-6.3.6">6.3.6</a>. Style</span>
The <head> element contains an embedded CSS in a <style> element.
The styles in the style sheet are to be set consistently between
documents by the RFC Editor, according to the best practices of the
day.
To ensure consistent formatting, individual style attributes should
not be used in the main portion of the document.
Different readers of a specification will desire different formatting
when reading the HTML versions of RFCs. To facilitate this, the
<head> element also includes a <link> to a style sheet in the same
directory as the HTML file, named "rfc-local.css". Any formatting in
the linked style sheet will override the formatting in the included
style sheet. For example:
<style>
body {}
...
</style>
<link rel="stylesheet" type="text/css" href="rfc-local.css">
<span class="h4"><a class="selflink" id="section-6.3.7" href="#section-6.3.7">6.3.7</a>. Links</span>
Each <link> element from the XML source is copied into the HTML
header. Note: the HTML <link> element does not include a closing
slash.
<span class="grey">Hildebrand & Hoffman Informational [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h3"><a class="selflink" id="section-6.4" href="#section-6.4">6.4</a>. Page Headers and Footers</span>
In order to simplify printing by HTML renderers that implement
[<a href="#ref-W3C.WD-css3-page-20130314">W3C.WD-css3-page-20130314</a>], a hidden HTML <table> tag of class
"ears" is added at the beginning of the HTML <body> tag, containing
HTML <thead> and <tfoot> tags, each of which contains an HTML <tr>
tag, which contains three HTML <td> tags with class "left", "center",
and "right", respectively.
The <thead> corresponds to the top of the page, the <tfoot> to the
bottom. The string "[Page]" can be used as a placeholder for the
page number. In practice, this must always be in the <tfoot>'s right
<td>, and no control of the formatting of the page number is implied.
<table class="ears">
<thead>
<tr>
<td class="left">Internet-Draft</td>
<td class="center">HTML RFC</td>
<td class="right">March 2016</td>
</tr>
</thead>
<tfoot>
<tr>
<td class="left">Hildebrand</td>
<td class="center">Expires September 2, 2016</td>
<td class="right">[Page]</td>
</tr>
</tfoot>
</table>
<span class="grey">Hildebrand & Hoffman Informational [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h3"><a class="selflink" id="section-6.5" href="#section-6.5">6.5</a>. Document Information</span>
Information about the document as a whole will appear as the first
child of the HTML <body> element, embedded in an HTML <dl> element
with id="identifiers". The defined terms in the definition list are
"Workgroup:", "Series:", "Status:", "Published:", and "Author:" or
"Authors:" (as appropriate). For example:
<dl id="identifiers">
<dt>Workgroup:</dt>
<dd class="workgroup">rfc-interest</dd>
<dt>Series:</dt>
<dd class="series">Internet-Draft</dd>
<dt>Status:</dt>
<dd class="status">Informational</dd>
<dt>Published:</dt>
<dd><time datetime="2014-10-25"
class="published">2014-10-25</time></dd>
<dt>Authors:</dt>
<dd class="authors">
<div class="author">
<span class="initial">J.</span>
<span class="surname">Hildebrand</span>
(<span class="organization">Cisco Systems, Inc.</span>)
<span class="editor">Ed.</span>
</div>
<div class="author">
<span class="initial">H.</span>
<span class="surname">Flanagan</span>
(<span class="organization">RFC Editor</span>)
</div>
</dd>
</dl>
<span class="grey">Hildebrand & Hoffman Informational [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h3"><a class="selflink" id="section-6.6" href="#section-6.6">6.6</a>. Table of Contents</span>
The table of contents will follow the boilerplate if the XML's <rfc>
element's "tocInclude" attribute has the value "true". An HTML <h2>
heading containing the text "Table of Contents" will be followed by a
<nav> element that contains a <ul> element for each depth of the
section hierarchy. Each section will be represented by a <li>
element containing links by the section number (from the "pn"
attribute) and by the name (from the "slugifiedName" attribute of the
<name> child element). Each <nav>, <ul>, and <li> element will have
the class "toc".
For example:
<h2 id="toc">Table of Contents</h2>
<nav class="toc">
<ul class="toc">
<li class="toc">
<a href="s-1">1</a>. <a href="n-introduction">Introduction</a>
</li>
<ul class="toc">
<li class="toc">
<a href="s-1.1">1.1</a>. <a href="n-sub-intro">Sub Intro</a>
</li>
...
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Main Body</span>
The main body of the HTML document is processed according to the
rules in <a href="#section-9">Section 9</a>.
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Back Matter</span>
The back matter of the HTML document includes an index (if
generated), information about the authors, and further information
about the document itself.
<span class="h3"><a class="selflink" id="section-8.1" href="#section-8.1">8.1</a>. Index</span>
The index will be produced as dictated by the RFC Editor's Style
Guide [<a href="#ref-RFC-STYLE">RFC-STYLE</a>] if and only if the XML document's <rfc> element has
an "indexInclude" attribute with the value "true" and there is one or
more <iref> elements in the document.
<span class="grey">Hildebrand & Hoffman Informational [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h4"><a class="selflink" id="section-8.1.1" href="#section-8.1.1">8.1.1</a>. Index Contents</span>
The index section will start with an <h2> heading containing the text
"Index", followed by links to each of the lettered portions of the
index. Links are not generated for letters that do not occur as the
first letter of an index item.
For example:
<h2>Index</h2>
<div class="index">
<div class="indexIndex">
<a href="#rfc.index.C">C</a>
<a href="#rfc.index.P">P</a>
</div>
...
<span class="h4"><a class="selflink" id="section-8.1.2" href="#section-8.1.2">8.1.2</a>. Index Letters</span>
The index letter is followed by a <ul> tag that contains an <li> tag
for each first letter represented in the index. This <li> tag has
the class "indexChar" and contains an <a> tag with the id pointed to
by the index letter as well as an "href" attribute to itself. The
<li> tag also includes a <ul> tag that will contain the index items.
For example:
<ul>
<li class="indexChar">
<a href="#rfc.index.C" id="rfc.index.C">C</a>
<ul>
<!-- items go here -->
</ul>
</li>
...
<span class="grey">Hildebrand & Hoffman Informational [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h4"><a class="selflink" id="section-8.1.3" href="#section-8.1.3">8.1.3</a>. Index Items</span>
Each index item can have multiple <iref> elements to point to, all
with the same item attribute. Each index item is represented by an
<li> tag of class "indexItem" containing a <span> of class "irefItem"
for the item text and one of class "irefRefs" for the generated
references (if there is at least one reference to the item not having
a subitem). Each generated reference contains an <a> tag containing
the section number where the <iref> is found, with an "href"
attribute pointing to the "irefid" attribute of the <iref> element
from the XML document. If the primary attribute of the <iref>
element has the value "true", the <a> element in the HTML document
will have the class "indexPrimary". Commas may be used to separate
the generated references.
For example:
<li class="indexItem">
<span class="irefItem">Bullets</span>
<span class="irefRefs">
<a class="indexPrimary" href="#s-Bullets-1">2</a>,
<a href="#s-Bullets-2">2</a>
</span>
<!-- subitems go here -->
</li>
...
<span class="h4"><a class="selflink" id="section-8.1.4" href="#section-8.1.4">8.1.4</a>. Index Subitems</span>
If an index item has at least one subitem, the <li> of that item will
contain a <ul>, with one <li> for each subitem, of class
"indexSubItem". The format for each subitem is similar to that used
for items, except the class of the first <span> tag is "irefSubItem".
For example:
<ul>
<li class="indexSubItem">
<span class="irefSubItem">Ordered</span>
<span class="irefRefs">
<a href="#s-Bullets-Ordered-1">2</a>
</span>
</li>
</ul>
...
<span class="grey">Hildebrand & Hoffman Informational [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h3"><a class="selflink" id="section-8.2" href="#section-8.2">8.2</a>. Authors' Addresses Section</span>
At the end of the document, author information will be included
inside an HTML <section> element whose "id" attribute is "author-
addresses". The class names of the constituent HTML tags have been
chosen to match the class names in [<a href="#ref-HCARD" title=""hCard 1.0"">HCARD</a>].
The information for each author will be separated by an HTML <hr>
element with class "addr".
<section id="author-addresses">
<h2>
<a class="selfRef" href="#author-addresses">
Authors' Addresses
</a>
</h2>
<address class="vcard">
<div class="nameRole"><span class="fn">Joe Hildebrand</span>
(<span class="role">editor</span>)</div>
<div class="org">Cisco Systems, Inc.</div>
</address>
<hr class="addr">
<address class="vcard">
<div class="nameRole"><span class="fn">Heather Flanagan</span>
(<span class="role">editor</span>)</div>
<div class="org">RFC Series Editor</div>
</address>
</section>
<span class="grey">Hildebrand & Hoffman Informational [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h3"><a class="selflink" id="section-8.3" href="#section-8.3">8.3</a>. Document Information</span>
A few bits of metadata about the document that are less important to
most readers are included after the author information. These are
gathered together into a <div> of class "docInfo".
The finalized time is copied from the <rfc> element's "prepTime"
attribute. The rendered time is the time that this HTML was
generated.
For example:
<div class="docInfo">
<span class="finalized">
Finalized: <time
datetime="2015-04-29T18:59:08Z">2015-04-29T18:59:08Z</time>
</span>
<span class="rendered">
Rendered: <time
datetime="2015-04-29T18:59:10Z">2015-04-29T18:59:10Z</time>
</span>
</div>
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Elements</span>
This section describes how each of the XML elements from [<a href="./rfc7991" title=""The "">RFC7991</a>] is
rendered to HTML. Many of the descriptions have examples to clarify
how elements will be rendered.
<span class="h3"><a class="selflink" id="section-9.1" href="#section-9.1">9.1</a>. <abstract></span>
The abstract is rendered in a similar fashion to a <section> with
anchor="abstract" and <name>Abstract</name>, but without a section
number.
<section id="abstract">
<h2><a href="#abstract" class="selfRef">Abstract</a></h2>
<p id="s-abstract-1">This document defines...
<a href="#s-abstract-1" class="pilcrow">&para;</a>
</p>
</section>
<span class="grey">Hildebrand & Hoffman Informational [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h3"><a class="selflink" id="section-9.2" href="#section-9.2">9.2</a>. <address></span>
This element is used in the Authors' Addresses section. It is
rendered as an HTML <address> tag of class "vcard". If none of the
descendant XML elements has an "ascii" attribute, the <address> HTML
tag includes the HTML rendering of each of the descendant XML
elements. Otherwise, the <address> HTML tag includes an HTML <div>
tag of class "ascii" (containing the HTML rendering of the ASCII
variants of each of the descendant XML elements), an HTML <div> tag
of class "alternative-contact", (containing the text "Alternate
contact information:"), and an HTML <div> tag of class "non-ascii"
(containing the HTML rendering of the non-ASCII variants of each of
the descendant XML elements).
Note: the following example shows some ASCII equivalents that are the
same as their nominal equivalents for clarity; normally, the ASCII
equivalents would not be included for these cases.
<address class="vcard">
<div class="ascii">
<div class="nameRole"><span class="fn">Joe Hildebrand</span>
(<span class="role">editor</span>)</div>
<div class="org">Cisco Systems, Inc.</div>
</div>
<div class="alternative-contact">
Alternate contact information:
</div>
<div class="non-ascii">
<div class="nameRole"><span class="fn">Joe Hildebrand</span>
(<span class="role">editor</span>)</div>
<div class="org">Cisco Systems, Inc.</div>
</div>
</address>
<span class="h3"><a class="selflink" id="section-9.3" href="#section-9.3">9.3</a>. <annotation></span>
This element is rendered as the text ", " (a comma and a space)
followed by a <span> of class "annotation" at the end of a
<reference> element, the <span> containing appropriately transformed
elements from the children of the <annotation> tag.
<span class="annotation">Some <em>thing</em>.</span>
<span class="h3"><a class="selflink" id="section-9.4" href="#section-9.4">9.4</a>. <area></span>
Not currently rendered to HTML.
<span class="grey">Hildebrand & Hoffman Informational [Page 19]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h3"><a class="selflink" id="section-9.5" href="#section-9.5">9.5</a>. <artwork></span>
Artwork can consist of either inline text or SVG. If the artwork is
not inside a <figure> element, a pilcrow (<a href="#section-5.2">Section 5.2</a>) is included.
Inside a <figure> element, the figure title serves the purpose of the
pilcrow. If the "align" attribute has the value "right", the CSS
class "alignRight" will be added. If the "align" attribute has the
value "center", the CSS class "alignCenter" will be added.
<span class="h4"><a class="selflink" id="section-9.5.1" href="#section-9.5.1">9.5.1</a>. Text Artwork</span>
Text artwork is rendered inside an HTML <pre> element, which is
contained by a <div> element for consistency with SVG artwork. Note
that CDATA blocks are not a part of HTML, so angle brackets and
ampersands (i.e., <, >, and &) must be escaped as &lt;, &gt;, and
&amp;, respectively.
The <div> element will have CSS classes of "artwork", "art-text", and
"art-" prepended to the value of the <artwork> element's "type"
attribute, if it exists.
<div class="artwork art-text art-ascii-art" id="s-1-2">
<pre>
______________
&lt; hello, world &gt;
--------------
\ ^__^
\ (oo)\_______
(__)\ )\/\
||----w |
|| ||
</pre>
<a class="pilcrow" href="#s-1-2">&para;</a>
</div>
<span class="h4"><a class="selflink" id="section-9.5.2" href="#section-9.5.2">9.5.2</a>. SVG Artwork</span>
SVG artwork will be included inline. The SVG is wrapped in a <div>
element with CSS classes "artwork" and "art-svg".
If the SVG "artwork" element is a child of <figure> and the artwork
is specified as align="right", an empty HTML <span> element is added
directly after the <svg> element, in order to get right alignment to
work correctly in HTML rendering engines that do not support the
flex-box model.
Note: the "alt" attribute of <artwork> is not currently used for SVG;
instead, the <title> and <desc> tags are used in the SVG.
<span class="grey">Hildebrand & Hoffman Informational [Page 20]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<div class="artwork art-svg" id="s-2-17">
<svg width="100" height="100" xmlns="http://www.w3.org/2000/svg">
<desc>Alt text here</desc>
<circle
cx="50" cy="50" r="40"
stroke="green" stroke-width="4" fill="yellow" />
</svg>
<a href="#s-2-17" class="pilcrow">&para;</a>
</div>
<span class="h4"><a class="selflink" id="section-9.5.3" href="#section-9.5.3">9.5.3</a>. Other Artwork</span>
Other artwork will have a "src" attribute that uses the "data" URI
scheme defined in [<a href="./rfc2397" title=""The "">RFC2397</a>]. Such artwork is rendered in an HTML
<img> element. Note: the HTML <img> element does not have a closing
slash.
Note: such images are not yet allowed in RFCs even though the format
supports them. A limited set of "data:" mediatypes for artwork may
be allowed in the future.
<div class="artwork art-logo" id="s-2-58">
<img alt="IETF logo"
src="data:image/gif;charset=utf-8;base64,...">
<a class="pilcrow" href="#s-2-58">&para;</a>
</div>
<span class="h3"><a class="selflink" id="section-9.6" href="#section-9.6">9.6</a>. <aside></span>
This element is rendered as an HTML <aside> element, with all child
content appropriately transformed.
<aside id="s-2.1-2">
<p id="s-2.1-2.1">
A little more than kin, and less than kind.
<a class="pilcrow" href="#s-2.1-2.1">&para;</a>
</p>
</aside>
<span class="h3"><a class="selflink" id="section-9.7" href="#section-9.7">9.7</a>. <author></span>
The <author> element is used in several places in the output.
Different rendering is used for each.
<span class="grey">Hildebrand & Hoffman Informational [Page 21]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h4"><a class="selflink" id="section-9.7.1" href="#section-9.7.1">9.7.1</a>. Authors in Document Information</span>
As seen in the Document Information at the beginning of the HTML,
each document author is rendered as an HTML <div> tag of class
"author".
Inside the <div class="author"> HTML tag, the author's initials and
surname (or the fullname, if it exists and the others do not) will be
rendered in an HTML <div> tag of class "author-name". If the
<author> contains "asciiInitials" and "asciiSurname" attributes, or
contains as "asciiFullname" attribute, the author's name is rendered
twice, with the first being the non-ASCII version, wrapped in an HTML
<span> tag of class "non-ascii", followed by the ASCII version
wrapped in an HTML <span> tag of class "ascii", wrapped in
parentheses. If the <author> has a "role" attribute of "editor", the
<div class="author-name"> will also contain the text ", " (comma,
space), followed by an HTML <span> tag of class "editor", which
contains the text "Ed.".
If the <author> element contains an <organization> element, it is
also rendered inside the <div class="author"> HTML tag.
<div class="author">
<div class="author-name">
H. Flanagan,
<span class="editor">Ed.</span></div>
<div class="org">Test Org</div>
</div>
<div class="author">
<div class="author-name">
<span class="non-ascii">Hildebrand</span>
(<span class="ascii">HILDEBRAND</span>)
</div>
<div class="org">
<span class="non-ascii">Test Org</span>
(<span class="ascii">TEST ORG</span>)
</div>
</div>
<span class="h4"><a class="selflink" id="section-9.7.2" href="#section-9.7.2">9.7.2</a>. Authors of This Document</span>
As seen in the Authors' Addresses section, at the end of the HTML,
each document author is rendered into an HTML <address> element with
the CSS class "vcard".
The HTML <address> element will contain an HTML <div> with CSS class
"nameRole". That div will contain an HTML <span> element with CSS
class "fn" containing the value of the "fullname" attribute of the
<span class="grey">Hildebrand & Hoffman Informational [Page 22]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<author> XML element and an HTML <span> element with CSS class "role"
containing the value of the "role" attribute of the <author> XML
element (if there is a role). Parentheses will surround the <span
class="role">, if it exists.
<address class="vcard">
<div class="nameRole">
<span class="fn">Joe Hildebrand</span>
(<span class="role">editor</span>)
</div>
...
After the name, the <organization> and <address> child elements of
the author are rendered inside the HTML <address> tag.
When the <author> element, or any of its descendant elements, has any
attribute that starts with "ascii", all of the author information is
displayed twice. The first version is wrapped in an HTML <div> tag
with class "ascii"; this version prefers the ASCII version of
information, such as "asciiFullname", but falls back on the non-ASCII
version if the ASCII version doesn't exist. The second version is
wrapped in an HTML <div> tag with class "non-ascii"; this version
prefers the non-ASCII version of information, such as "fullname", but
falls back on the ASCII version if the non-ASCII version does not
exist. Between these two HTML <div>s, a third <div> is inserted,
with class "alternative-contact", containing the text "Alternate
contact information:".
<address class="vcard">
<div class="ascii">
<div class="nameRole">
<span class="fn">The ASCII name</span>
</div>
</div>
<div class="alternative-contact">
Alternate contact information:
</div>
<div class="non-ascii">
<div class="nameRole">
<span class="fn">The non-ASCII name</span>
(<span class="role">editor</span>)
</div>
</div>
</address>
<span class="grey">Hildebrand & Hoffman Informational [Page 23]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h4"><a class="selflink" id="section-9.7.3" href="#section-9.7.3">9.7.3</a>. Authors of References</span>
In the output generated from a reference element, author tags are
rendered inside an HTML <span> element with CSS class "refAuthor".
See <a href="./rfc7322#section-4.8.6.2">Section 4.8.6.2 of [RFC7322]</a> for guidance on how author names are
to appear.
<span class="refAuthor">Flanagan, H.</span> and
<span class="refAuthor">N. Brownlee</span>
<span class="h3"><a class="selflink" id="section-9.8" href="#section-9.8">9.8</a>. <back></span>
If there is exactly one <references> child, render that child in a
similar way to a <section>. If there are more than one <references>
children, render as a <section> whose name is "References",
containing a <section> for each <references> child.
After any <references> sections, render each <section> child of
<back> as an appendix.
<section id="n-references">
<h2 id="s-2">
<a class="selfRef" href="#s-2">2.</a>
<a class="selfRef" href="#n-references">References</a>
</h2>
<section id="n-normative">
<h3 id="s-2.1">
<a class="selfRef" href="#s-2.1">2.1.</a>
<a class="selfRef" href="#n-normative">Normative</a>
</h3>
<dl class="reference"></dl>
</section>
<section id="n-informational">
<h3 id="s-2.2">
<a class="selfRef" href="#s-2.2">2.2.</a>
<a class="selfRef" href="#n-informational">Informational</a>
</h3>
<dl class="reference"></dl>
</section>
</section>
<section id="n-unimportant">
<h2 id="s-A">
<a class="selfRef" href="#s-A">Appendix A.</a>
<a class="selfRef" href="#n-unimportant">Unimportant</a>
</h2>
</section>
<span class="grey">Hildebrand & Hoffman Informational [Page 24]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h3"><a class="selflink" id="section-9.9" href="#section-9.9">9.9</a>. <<a href="https://www.rfc-editor.org/bcp/bcp14">bcp14</a>></span>
This element marks up words like MUST and SHOULD [<a href="#ref-BCP14" title=""Key words for use in RFCs to Indicate Requirement Levels"">BCP14</a>] with an HTML
<span> element with the CSS class "<a href="https://www.rfc-editor.org/bcp/bcp14">bcp14</a>".
You <span class="<a href="https://www.rfc-editor.org/bcp/bcp14">bcp14</a>">MUST</span> be joking.
<span class="h3"><a class="selflink" id="section-9.10" href="#section-9.10">9.10</a>. <blockquote></span>
This element renders in a way similar to the HTML <blockquote>
element. If there is a "cite" attribute, it is copied to the HTML
"cite" attribute. If there is a "quoteFrom" attribute, it is placed
inside a <cite> element at the end of the quote, with an <a> element
surrounding it (if there is a "cite" attribute), linking to the cited
URL.
If the <blockquote> does not contain another element that gets a
pilcrow (<a href="#section-5.2">Section 5.2</a>), a pilcrow is added.
Note that the "&mdash;" at the beginning of the <cite> element should
be a proper emdash, which is difficult to show in the display of the
current format.
<blockquote id="s-1.2-1"
cite="http://...">
<p id="s-1.2-2">Four score and seven years ago our fathers
brought forth on this continent, a new nation, conceived
in Liberty, and dedicated to the proposition that all men
are created equal.
<a href="#s-1.2-2" class="pilcrow">&para;</a>
</p>
<cite>&mdash; <a href="http://...">Abraham Lincoln</a></cite>
</blockquote>
<span class="grey">Hildebrand & Hoffman Informational [Page 25]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h3"><a class="selflink" id="section-9.11" href="#section-9.11">9.11</a>. <boilerplate></span>
The Status of This Memo and the Copyright statement, together
commonly referred to as the document boilerplate, appear after the
Abstract. The children of the input <boilerplate> element are
treated in a similar fashion to unnumbered sections.
<section id="status-of-this-memo">
<h2 id="s-boilerplate-1">
<a href="#status-of-this-memo" class="selfRef">
Status of this Memo</a>
</h2>
<p id="s-boilerplate-1-1">This Internet-Draft is submitted in full
conformance with the provisions of <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.
<a href="#s-boilerplate-1-1" class="pilcrow">&para;</a>
</p>
...
<span class="h3"><a class="selflink" id="section-9.12" href="#section-9.12">9.12</a>. <br></span>
This element is directly rendered as its HTML counterpart. Note: in
HTML, <br> does not have a closing slash.
<span class="h3"><a class="selflink" id="section-9.13" href="#section-9.13">9.13</a>. <city></span>
This element is rendered as a <span> element with CSS class
"locality".
<span class="locality">Guilford</span>
<span class="h3"><a class="selflink" id="section-9.14" href="#section-9.14">9.14</a>. <code></span>
This element is rendered as a <span> element with CSS class "postal-
code".
<span class="postal-code">GU16 7HF<span>
<span class="h3"><a class="selflink" id="section-9.15" href="#section-9.15">9.15</a>. <country></span>
This element is rendered as a <div> element with CSS class "country-
name".
<div class="country-name">England</div>
<span class="grey">Hildebrand & Hoffman Informational [Page 26]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h3"><a class="selflink" id="section-9.16" href="#section-9.16">9.16</a>. <cref></span>
This element is rendered as a <span> element with CSS class "cref".
Any anchor is copied to the "id" attribute. If there is a source
given, it is contained inside the "cref" <span> element with another
<span> element of class "crefSource".
<span class="cref" id="crefAnchor">Just a brief comment
about something that we need to remember later.
<span class="crefSource">--life</span></span>
<span class="h3"><a class="selflink" id="section-9.17" href="#section-9.17">9.17</a>. <date></span>
This element is rendered as the HTML <time> element. If the "year",
"month", or "day" attribute is included on the XML element, an
appropriate "datetime" element will be generated in HTML.
If this date is a child of the document's <front> element, it gets
the CSS class "published".
If this date is inside a <reference> element, it gets the CSS class
"refDate".
<time datetime="2014-10" class="published">October 2014</time>
<span class="h3"><a class="selflink" id="section-9.18" href="#section-9.18">9.18</a>. <dd></span>
This element is directly rendered as its HTML counterpart.
<span class="h3"><a class="selflink" id="section-9.19" href="#section-9.19">9.19</a>. <displayreference></span>
This element does not affect the HTML output, but it is used in the
generation of the <reference>, <referencegroup>, <relref>, and <xref>
elements.
<span class="h3"><a class="selflink" id="section-9.20" href="#section-9.20">9.20</a>. <dl></span>
This element is directly rendered as its HTML counterpart.
If the hanging attribute is "false", add the "dlParallel" class, else
add the "dlHanging" class.
If the spacing attribute is "compact", add the "dlCompact" class.
<span class="h3"><a class="selflink" id="section-9.21" href="#section-9.21">9.21</a>. <dt></span>
This element is directly rendered as its HTML counterpart.
<span class="grey">Hildebrand & Hoffman Informational [Page 27]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h3"><a class="selflink" id="section-9.22" href="#section-9.22">9.22</a>. <em></span>
This element is directly rendered as its HTML counterpart.
<span class="h3"><a class="selflink" id="section-9.23" href="#section-9.23">9.23</a>. <email></span>
This element is rendered as an HTML <div> containing the string
"Email:" and an HTML <a> element with the "href" attribute set to the
equivalent "mailto:" URI, a CSS class of "email", and the contents
set to the email address. If this is the version of the address with
ASCII, the "ascii" attribute is preferred to the element text.
<div>
<span>Email:</span>
<a class="email" href="mailto:joe@example.com">joe@example.com</a>
</div>
<span class="h3"><a class="selflink" id="section-9.24" href="#section-9.24">9.24</a>. <eref></span>
This element is rendered as an HTML <a> element, with the "href"
attribute set to the value of the "target" attribute and the CSS
class of "eref".
<a href="https://..." class="eref">the text</a>
<span class="h3"><a class="selflink" id="section-9.25" href="#section-9.25">9.25</a>. <figure></span>
This element renders as the HTML <figure> element, containing the
artwork or sourcecode indicated and an HTML <figcaption> element.
The <figcaption> element will contain an <a> element around the
figure number. It will also contain another <a> element with CSS
class "selfRef" around the figure name, if a name was given.
<figure id="f-1">
...
<figcaption>
<a href="#f-1">Figure 1.</a>
<a href="#n-it-figures" id="n-it-figures" class="selfRef">
It figures
</a>
</figcaption>
</figure>
<span class="h3"><a class="selflink" id="section-9.26" href="#section-9.26">9.26</a>. <front></span>
See "Document Information" (<a href="#section-6.5">Section 6.5</a>) for information on this
element.
<span class="grey">Hildebrand & Hoffman Informational [Page 28]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h3"><a class="selflink" id="section-9.27" href="#section-9.27">9.27</a>. <iref></span>
This element is rendered as an empty <> tag of class "iref", with an
"id" attribute consisting of the <iref> element's "irefid" attribute:
<span class="iref" id="s-Paragraphs-first-1"/>
<span class="h3"><a class="selflink" id="section-9.28" href="#section-9.28">9.28</a>. <keyword></span>
Each <keyword> element renders its text into the <meta> keywords in
the document's header, separated by commas.
<meta name="keywords" content="html,css,rfc">
<span class="h3"><a class="selflink" id="section-9.29" href="#section-9.29">9.29</a>. <li></span>
This element is rendered as its HTML counterpart. However, if there
is no contained element that has a pilcrow (<a href="#section-5.2">Section 5.2</a>) attached, a
pilcrow is added.
<li id="s-2-7">Item <a href="#s-2-7" class="pilcrow">&para;</a></li>
<span class="h3"><a class="selflink" id="section-9.30" href="#section-9.30">9.30</a>. <link></span>
This element is rendered as its HTML counterpart, in the HTML header.
<span class="h3"><a class="selflink" id="section-9.31" href="#section-9.31">9.31</a>. <middle></span>
This element does not add any direct output to HTML.
<span class="h3"><a class="selflink" id="section-9.32" href="#section-9.32">9.32</a>. <name></span>
This element is never rendered directly; it is only rendered when
considering a parent element, such as <figure>, <references>,
<section>, or <table>.
<span class="grey">Hildebrand & Hoffman Informational [Page 29]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h3"><a class="selflink" id="section-9.33" href="#section-9.33">9.33</a>. <note></span>
This element is rendered like a <section> element, but without a
section number and with the CSS class of "note". If the
"removeInRFC" attribute is set to "yes", the generated <div> element
will also include the CSS class "rfcEditorRemove".
<section id="s-note-1" class="note rfcEditorRemove">
<h2>
<a href="#n-editorial-note" class="selfRef">Editorial Note</a>
</h2>
<p id="s-note-1-1">
Discussion of this draft takes place...
<a href="#s-note-1-1" class="pilcrow">&para;</a>
</p>
</section>
<span class="h3"><a class="selflink" id="section-9.34" href="#section-9.34">9.34</a>. <ol></span>
The output created from an <ol> element depends upon the "style"
attribute.
If the "spacing" attribute has the value "compact", a CSS class of
"olCompact" will be added.
The group attribute is not copied; the input XML should have start
values added by a prep tool for all grouped <ol> elements.
<span class="h4"><a class="selflink" id="section-9.34.1" href="#section-9.34.1">9.34.1</a>. Percent Styles</span>
If the style attribute includes the character "%", the output is a
<dl> tag with the class "olPercent". Each contained <li> element is
emitted as a <dt>/<dd> pair, with the generated label in the <dt> and
the contents of the <li> in the <dd>.
<dl class="olPercent">
<dt>Requirement xviii:</dt>
<dd>Wheels on a big rig</dd>
</dl>
<span class="h4"><a class="selflink" id="section-9.34.2" href="#section-9.34.2">9.34.2</a>. Standard Styles</span>
For all other styles, an <ol> tag is emitted, with any "style"
attribute turned into the equivalent HTML attribute.
<ol class="compact" type="I" start="18">
<li>Wheels on a big rig</li>
</ol>
<span class="grey">Hildebrand & Hoffman Informational [Page 30]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h3"><a class="selflink" id="section-9.35" href="#section-9.35">9.35</a>. <organization></span>
This element is rendered as an HTML <div> tag with CSS class "org".
If the element contains the "ascii" attribute, the organization name
is rendered twice: once with the non-ASCII version wrapped in an HTML
<span> tag of class "non-ascii" and then as the ASCII version wrapped
in an HTML <span> tag of class "ascii" wrapped in parentheses.
<div class="org">
<span class="non-ascii">Test Org</span>
(<span class="ascii">TEST ORG</span>)
</div>
<span class="h3"><a class="selflink" id="section-9.36" href="#section-9.36">9.36</a>. <phone></span>
This element is rendered as an HTML <div> tag containing the string
"Phone:" (wrapped in a span), an HTML <a> tag with CSS class "tel"
containing the phone number (and an href with a corresponding "tel:"
URI), and an HTML <span> with CSS class "type" containing the string
"VOICE".
<div>
<span>Phone:</span>
<a class="tel" href="tel:+1-720-555-1212">+1-720-555-1212</a>
<span class="type">VOICE</span>
</div>
<span class="h3"><a class="selflink" id="section-9.37" href="#section-9.37">9.37</a>. <postal></span>
This element renders as an HTML <div> with CSS class "adr", unless it
contains one or more <postalLine> child elements; in which case, it
renders as an HTML <pre> element with CSS class "label".
When there is no <postalLine> child, the following child elements are
rendered into the HTML:
o Each <street> is rendered
o A <div> that includes:
* The rendering of all <city> elements
* A comma and a space: ", "
* The rendering of all <region> elements
<span class="grey">Hildebrand & Hoffman Informational [Page 31]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
* Whitespace
* The rendering of all <code> elements
o The rendering of all <country> elements
<div class="adr">
<div class="street-address">1 Main Street</div>
<div class="street-address">Suite 1</div>
<div>
<span class="city">Denver</span>,
<span class="region">CO</span>
<span class="postal-code">80212</span>
</div>
<div class="country-name">United States of America</div>
</div>
<span class="h3"><a class="selflink" id="section-9.38" href="#section-9.38">9.38</a>. <postalLine></span>
This element renders as the text contained by the element, followed
by a newline. However, the last <postalLine> in a given <postal>
element should not be followed by a newline. For example:
<postal>
<postalLine>In care of:</postalLine>
<postalLine>Computer Sciences Division</postalLine>
</postal>
Would be rendered as:
<pre class="label">In care of:
Computer Sciences Division</pre>
<span class="h3"><a class="selflink" id="section-9.39" href="#section-9.39">9.39</a>. <refcontent></span>
This element renders as an HTML <span> with CSS class "refContent".
<span class="refContent">Self-published pamphlet</span>
<span class="grey">Hildebrand & Hoffman Informational [Page 32]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h3"><a class="selflink" id="section-9.40" href="#section-9.40">9.40</a>. <reference></span>
If the parent of this element is not a <referencegroup>, this element
will render as a <dt> <dd> pair with the defined term being the
reference "anchor" attribute surrounded by square brackets and the
definition including the correct set of bibliographic information as
specified by [<a href="./rfc7322" title=""RFC Style Guide"">RFC7322</a>]. The <dt> element will have an "id" attribute
of the reference anchor.
<dl class="reference">
<dt id="<a href="./rfc5646">RFC5646</a>">[<a href="./rfc5646" title=""Tags for Identifying Languages"">RFC5646</a>]</dt>
<dd>
<span class="refAuthor">Phillips, A.</span>
<span>and</span>
<span class="refAuthor">M. Davis</span>
<span class="refTitle">"Tags for Identifying Languages"</span>,
...
</dd>
</dl>
If the child of a <referencegroup>, this element renders as a <div>
of class "refInstance" whose "id" attribute is the value of the
<source> element's "anchor" attribute.
<div class="refInstance" id="<a href="./rfc5730">RFC5730</a>">
...
</div>
<span class="h3"><a class="selflink" id="section-9.41" href="#section-9.41">9.41</a>. <referencegroup></span>
A <referencegroup> is translated into a <dt> <dd> pair, with the
defined term being the referencegroup "anchor" attribute surrounded
by square brackets, and the definition containing the translated
output of all of the child <reference> elements.
<dt id="STD69">[STD69]</dt>
<dd>
<div class="refInstance" id="<a href="./rfc5730">RFC5730</a>">
<span class="refAuthor">Hollenbeck, S.</span>
...
</div>
<div class="refInstance" id="<a href="./rfc5731">RFC5731</a>">
<span class="refAuthor">Hollenbeck, S.</span>
...
</div>
...
</dd>
<span class="grey">Hildebrand & Hoffman Informational [Page 33]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-34" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h3"><a class="selflink" id="section-9.42" href="#section-9.42">9.42</a>. <references></span>
If there is at exactly one <references> element, a section is added
to the document, continuing with the next section number after the
last top-level <section> in <middle>. The <name> element of the
<references> element is used as the section name.
<section id="n-my-references">
<h2 id="s-3">
<a href="#s-3" class="selfRef">3.</a>
<a href="#n-my-references class="selfRef">My References</a>
</h2>
...
</section>
If there is more than one <references> element, an HTML <section>
element is created to contain a subsection for each of the
<references>. The section number will be the next section number
after the last top-level <section> in <middle>. The name of this
section will be "References", and its "id" attribute will be
"n-references".
<section id="n-references">
<h2 id="s-3">
<a href="#s-3" class="selfRef">3.</a>
<a href="#n-references" class="selfRef">References</a>
</h2>
<section id="n-informative-references">
<h3 id="s-3.1">
<a href="#s-3.1" class="selfRef">3.1.</a>
<a href="#n-informative-references" class="selfRef">
Informative References</a></h3>
<dl class="reference">...
</dl>
</section>
...
</section>
<span class="h3"><a class="selflink" id="section-9.43" href="#section-9.43">9.43</a>. <region></span>
This element is rendered as a <span> tag with CSS class "region".
<span class="region">Colorado</span>
<span class="grey">Hildebrand & Hoffman Informational [Page 34]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-35" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h3"><a class="selflink" id="section-9.44" href="#section-9.44">9.44</a>. <relref></span>
This element is rendered as an HTML <a> tag with CSS class "relref"
and "href" attribute of the "derivedLink" attribute of the element.
Different values of the "displayFormat" attribute cause the text
inside that HTML <a> tag to change and cause extra text to be
generated. Some values of the "displayFormat" attribute also cause
another HTML <a> tag to be rendered with CSS class "xref" and an
"href" of "#" and the "target" attribute (modified by any applicable
<displayreference> XML element) and text inside of the "target"
attribute (modified by any applicable <displayreference> XML
element). When used, this <a class='xref'> HTML tag is always
surrounded by square brackets, for example, "[<a class='xref'
href='#foo'>foo</a>]".
<span class="h4"><a class="selflink" id="section-9.44.1" href="#section-9.44.1">9.44.1</a>. displayFormat='of'</span>
The output is an <a class='relref'> HTML tag, with contents of
"Section " and the value of the "section" attribute. This is
followed by the word "of" (surrounded by whitespace). This is
followed by the <a class='xref'> HTML tag (surrounded by square
brackets).
For example, with an input of:
See <relref section="2.3" target="<a href="./rfc9999">RFC9999</a>" displayFormat="of"
derivedLink="http://www.rfc-editor.org/info/rfc9999#s-2.3"/>
for an overview.
The HTML generated will be:
See <a class="relref"
href="http://www.rfc-editor.org/info/rfc9999#s-2.3"><a href="#section-2.3">Section</a>
<a href="#section-2.3">2.3</a></a> of [<a class="xref" href="#<a href="./rfc9999">RFC9999</a>"><a href="./rfc9999">RFC9999</a></a>]
for an overview.
<span class="h4"><a class="selflink" id="section-9.44.2" href="#section-9.44.2">9.44.2</a>. displayFormat='comma'</span>
The output is an <a class='xref'> HTML tag (wrapped by square
brackets), followed by a comma (","), followed by whitespace,
followed by an <a class='relref'> HTML tag, with contents of
"Section " and the value of the "section" attribute.
For example, with an input of:
See <relref section="2.3" target="<a href="./rfc9999">RFC9999</a>" displayFormat="comma"
derivedLink="http://www.rfc-editor.org/info/rfc9999#s-2.3"/>,
for an overview.
<span class="grey">Hildebrand & Hoffman Informational [Page 35]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-36" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
The HTML generated will be:
See [<a class="xref" href="#<a href="./rfc9999">RFC9999</a>"><a href="./rfc9999">RFC9999</a></a>], <a class="relref"
href="http://www.rfc-editor.org/info/rfc9999#s-2.3"><a href="#section-2.3">Section 2.3</a></a>,
for an overview.
<span class="h4"><a class="selflink" id="section-9.44.3" href="#section-9.44.3">9.44.3</a>. displayFormat='parens'</span>
The output is an <a> element with "href" attribute whose value is the
value of the "target" attribute prepended by "#", and whose content
is the value of the "target" attribute; the entire element is wrapped
in square brackets. This is followed by whitespace. This is
followed by an <a> element whose "href" attribute is the value of the
"derivedLink" attribute and whose content is the value of the
"derivedRemoteContent" attribute; the entire element is wrapped in
parentheses.
For example, if <a href="./rfc9999#section-2.3">Section 2.3 of RFC 9999</a> has the title "Protocol
Overview", for an input of:
See <relref section="2.3" target="<a href="./rfc9999">RFC9999</a>" displayFormat="parens"
derivedLink="http://www.rfc-editor.org/info/rfc9999#s-2.3"
derivedRemoteContent="<a href="#section-2.3">Section 2.3</a>"/> for an overview.
The HTML generated will be:
See [<a class="relref" href="#<a href="./rfc9999">RFC9999</a>"><a href="./rfc9999">RFC9999</a></a>]
(<a class="relref"
href="http://www.rfc-editor.org/info/rfc9999#s-2.3"><a href="#section-2.3">Section</a>
<a href="#section-2.3">2.3</a></a>) for an overview.
<span class="h4"><a class="selflink" id="section-9.44.4" href="#section-9.44.4">9.44.4</a>. displayFormat='bare'</span>
The output is an <a> element whose "href" attribute is the value of
the "derivedLink" attribute and whose content is the value of the
"derivedRemoteContent" attribute.
For this input:
See <relref section="2.3" target="<a href="./rfc9999">RFC9999</a>" displayFormat="bare"
derivedLink="http://www.rfc-editor.org/info/rfc9999#s-2.3"
derivedRemoteContent="<a href="#section-2.3">Section 2.3</a>"/> and ...
The HTML generated will be:
See <a class="relref"
href="http://www.rfc-editor.org/info/rfc9999#s-2.3"><a href="#section-2.3">Section</a>
<a href="#section-2.3">2.3</a></a> and ...
<span class="grey">Hildebrand & Hoffman Informational [Page 36]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-37" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h3"><a class="selflink" id="section-9.45" href="#section-9.45">9.45</a>. <rfc></span>
Various attributes of this element are represented in different parts
of the HTML document.
<span class="h3"><a class="selflink" id="section-9.46" href="#section-9.46">9.46</a>. <section></span>
This element is rendered as an HTML <section> element, containing an
appropriate level HTML heading element (<h2>-<h6>). That heading
element contains an <a> element around the part number (pn), if
applicable (for instance, <abstract> does not get a section number).
Another <a> element is included with the section's name.
<section id="intro">
<h2 id="s-1">
<a href="#s-1" class="selfRef">1.</a>
<a href="#intro" class="selfRef">Introduction</a>
</h2>
<p id="s-1-1">Paragraph <a href="#s-1-1" class="pilcrow">&para;</a>
</p>
</section>
<span class="h3"><a class="selflink" id="section-9.47" href="#section-9.47">9.47</a>. <seriesInfo></span>
This element is rendered in an HTML <span> element with CSS name
"seriesInfo".
<span class="seriesInfo"><a href="./rfc5646">RFC 5646</a></span>
<span class="grey">Hildebrand & Hoffman Informational [Page 37]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-38" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h3"><a class="selflink" id="section-9.48" href="#section-9.48">9.48</a>. <sourcecode></span>
This element is rendered in an HTML <pre> element with a CSS class of
"sourcecode". Note that CDATA blocks do not work consistently in
HTML, so all <, >, and & must be escaped as &lt;, &gt;, and &amp;,
respectively. If the input XML has a "type" attribute, another CSS
class of "lang-" and the type is added.
If the sourcecode is not inside a <figure> element, a pilcrow
(<a href="#section-5.2">Section 5.2</a>) is included. Inside a <figure> element, the figure
title serves the purpose of the pilcrow.
<pre class="sourcecode lang-c">
#include &lt;stdio.h&gt;
int main(void)
{
printf(&quot;hello, world\n&quot;);
return 0;
}
</pre>
<span class="h3"><a class="selflink" id="section-9.49" href="#section-9.49">9.49</a>. <street></span>
This element renders as an HTML <div> element with CSS class "street-
address".
<div class="street-address">1899 Wynkoop St, Suite 600</div>
<span class="h3"><a class="selflink" id="section-9.50" href="#section-9.50">9.50</a>. <strong></span>
This element is directly rendered as its HTML counterpart.
<span class="h3"><a class="selflink" id="section-9.51" href="#section-9.51">9.51</a>. <sub></span>
This element is directly rendered as its HTML counterpart.
<span class="h3"><a class="selflink" id="section-9.52" href="#section-9.52">9.52</a>. <sup></span>
This element is directly rendered as its HTML counterpart.
<span class="h3"><a class="selflink" id="section-9.53" href="#section-9.53">9.53</a>. <t></span>
This element is rendered as an HTML <p> element. A pilcrow
(<a href="#section-5.2">Section 5.2</a>) is included.
<p id="s-1-1">A paragraph.
<a href="#s-1-1" class="pilcrow">&para;</a></p>
<span class="grey">Hildebrand & Hoffman Informational [Page 38]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-39" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h3"><a class="selflink" id="section-9.54" href="#section-9.54">9.54</a>. <table></span>
This element is directly rendered as its HTML counterpart.
<span class="h3"><a class="selflink" id="section-9.55" href="#section-9.55">9.55</a>. <tbody></span>
This element is directly rendered as its HTML counterpart.
<span class="h3"><a class="selflink" id="section-9.56" href="#section-9.56">9.56</a>. <td></span>
This element is directly rendered as its HTML counterpart.
<span class="h3"><a class="selflink" id="section-9.57" href="#section-9.57">9.57</a>. <tfoot></span>
This element is directly rendered as its HTML counterpart.
<span class="h3"><a class="selflink" id="section-9.58" href="#section-9.58">9.58</a>. <th></span>
This element is directly rendered as its HTML counterpart.
<span class="h3"><a class="selflink" id="section-9.59" href="#section-9.59">9.59</a>. <thead></span>
This element is directly rendered as its HTML counterpart.
<span class="h3"><a class="selflink" id="section-9.60" href="#section-9.60">9.60</a>. <title></span>
The title of the document appears in a <title> element in the <head>
element, as described in <a href="#section-6.3.2">Section 6.3.2</a>.
The title also appears in an <h1> element and follows directly after
the Document Information. The <h1> element has an "id" attribute
with value "title".
<h1 id="title">HyperText Markup Language Request For
Comments Format</h1>
Inside a reference, the title is rendered as an HTML <span> tag with
CSS class "refTitle". The text is surrounded by quotes inside the
<span>.
<span class="refTitle">"Tags for Identifying Languages"</span>
<span class="h3"><a class="selflink" id="section-9.61" href="#section-9.61">9.61</a>. <tr></span>
This element is directly rendered as its HTML counterpart.
<span class="grey">Hildebrand & Hoffman Informational [Page 39]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-40" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h3"><a class="selflink" id="section-9.62" href="#section-9.62">9.62</a>. <tt></span>
This element is rendered as an HTML <code> element.
<span class="h3"><a class="selflink" id="section-9.63" href="#section-9.63">9.63</a>. <ul></span>
This element is directly rendered as its HTML counterpart. If the
"spacing" attribute has the value "compact", a CSS class of
"ulCompact" will be added. If the "empty" attribute has the value
"true", a CSS class of "ulEmpty" will be added.
<span class="h3"><a class="selflink" id="section-9.64" href="#section-9.64">9.64</a>. <uri></span>
This element is rendered as an HTML <div> containing the string
"URI:" and an HTML <a> element with the "href" attribute set to the
linked URI, CSS class of "url" (note that the value is "url", not
"uri" as one might expect), and the contents set to the linked URI.
<div>URI:
<a href="http://www.example.com"
class="url">http://www.example.com</a>
</div>
<span class="h3"><a class="selflink" id="section-9.65" href="#section-9.65">9.65</a>. <workgroup></span>
This element does not add any direct output to HTML.
<span class="h3"><a class="selflink" id="section-9.66" href="#section-9.66">9.66</a>. <xref></span>
This element is rendered as an HTML <a> element containing an
appropriate local link as the "href" attribute. The value of the
"href" attribute is taken from the "target" attribute, prepended by
"#". The <a> element generated will have class "xref". The contents
of the <a> element are the value of the "derivedContent" attribute.
If the "format" attribute has the value "default", and the "target"
attribute points to a <reference> or <referencegroup> element, then
the generated <a> element is surrounded by square brackets in the
output.
<a class="xref" href="#target">Table 2</a>
or
[<a class="xref" href="#<a href="./rfc1234">RFC1234</a>"><a href="./rfc1234">RFC1234</a></a>]
<span class="grey">Hildebrand & Hoffman Informational [Page 40]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-41" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
<span class="h3"><a class="selflink" id="section-9.67" href="#section-9.67">9.67</a>. <svg xmlns='http://www.w3.org/2000/svg'></span>
This element is rendered as part of the <artwork> element. The
"xmlns='http://www.w3.org/2000/svg'" namespace declaration should be
included, and the SVG should be serialized as well-formed XML, even
for tags that would otherwise not need closing in HTML5.
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Security Considerations</span>
Since RFCs are sometimes exchanged outside the normal Web sandboxing
mechanism (such as using the "rsync" program to a mirror site) then
loaded from a local file, more care must be taken with the HTML than
is ordinary on the web.
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. References</span>
<span class="h3"><a class="selflink" id="section-11.1" href="#section-11.1">11.1</a>. Normative References</span>
[<a id="ref-BCP14">BCP14</a>] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997,
<<a href="http://www.rfc-editor.org/info/bcp14">http://www.rfc-editor.org/info/bcp14</a>>.
[<a id="ref-RFC2397">RFC2397</a>] Masinter, L., "The "data" URL scheme", <a href="./rfc2397">RFC 2397</a>,
DOI 10.17487/RFC2397, August 1998,
<<a href="http://www.rfc-editor.org/info/rfc2397">http://www.rfc-editor.org/info/rfc2397</a>>.
[<a id="ref-RFC3629">RFC3629</a>] Yergeau, F., "UTF-8, a transformation format of ISO
10646", STD 63, <a href="./rfc3629">RFC 3629</a>, DOI 10.17487/RFC3629, November
2003, <<a href="http://www.rfc-editor.org/info/rfc3629">http://www.rfc-editor.org/info/rfc3629</a>>.
[<a id="ref-RFC5646">RFC5646</a>] Phillips, A., Ed. and M. Davis, Ed., "Tags for Identifying
Languages", <a href="https://www.rfc-editor.org/bcp/bcp47">BCP 47</a>, <a href="./rfc5646">RFC 5646</a>, DOI 10.17487/RFC5646,
September 2009, <<a href="http://www.rfc-editor.org/info/rfc5646">http://www.rfc-editor.org/info/rfc5646</a>>.
[<a id="ref-RFC7322">RFC7322</a>] Flanagan, H. and S. Ginoza, "RFC Style Guide", <a href="./rfc7322">RFC 7322</a>,
DOI 10.17487/RFC7322, September 2014,
<<a href="http://www.rfc-editor.org/info/rfc7322">http://www.rfc-editor.org/info/rfc7322</a>>.
[<a id="ref-RFC7991">RFC7991</a>] Hoffman, P., "The "xml2rfc" Version 3 Vocabulary",
<a href="./rfc7991">RFC 7991</a>, DOI 10.17487/RFC7991, December 2016,
<<a href="http://www.rfc-editor.org/info/rfc7991">http://www.rfc-editor.org/info/rfc7991</a>>.
[<a id="ref-RFC7993">RFC7993</a>] Flanagan, H., "Cascading Style Sheets (CSS) Requirements
for RFCs", <a href="./rfc7993">RFC 7993</a>, DOI 10.17487/RFC7993, December 2016,
<<a href="http://www.rfc-editor.org/info/rfc7993">http://www.rfc-editor.org/info/rfc7993</a>>.
<span class="grey">Hildebrand & Hoffman Informational [Page 41]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-42" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
[<a id="ref-W3C.REC-CSS2-20110607">W3C.REC-CSS2-20110607</a>]
Bos, B., Celik, T., Hickson, I., and H. Lie, "Cascading
Style Sheets Level 2 Revision 1 (CSS 2.1) Specification",
World Wide Web Consortium Recommendation
REC-CSS2-20110607, June 2011,
<<a href="http://www.w3.org/TR/2011/REC-CSS2-20110607">http://www.w3.org/TR/2011/REC-CSS2-20110607</a>>.
[<a id="ref-W3C.REC-html5-20141028">W3C.REC-html5-20141028</a>]
Hickson, I., Berjon, R., Faulkner, S., Leithead, T.,
Navara, E., O'Connor, T., and S. Pfeiffer, "HTML5", World
Wide Web Consortium Recommendation
REC-html5-20141028, October 2014,
<<a href="http://www.w3.org/TR/2014/REC-html5-20141028">http://www.w3.org/TR/2014/REC-html5-20141028</a>>.
<span class="h3"><a class="selflink" id="section-11.2" href="#section-11.2">11.2</a>. Informative References</span>
[<a id="ref-HCARD">HCARD</a>] Celik, T., "hCard 1.0", 2015,
<<a href="http://microformats.org/wiki/hcard">http://microformats.org/wiki/hcard</a>>.
[<a id="ref-RFC-STYLE">RFC-STYLE</a>]
RFC Editor, "Style Guide",
<<a href="https://www.rfc-editor.org/styleguide/">https://www.rfc-editor.org/styleguide/</a>>.
[<a id="ref-RFC6949">RFC6949</a>] Flanagan, H. and N. Brownlee, "RFC Series Format
Requirements and Future Development", <a href="./rfc6949">RFC 6949</a>,
DOI 10.17487/RFC6949, May 2013,
<<a href="http://www.rfc-editor.org/info/rfc6949">http://www.rfc-editor.org/info/rfc6949</a>>.
[<a id="ref-RFC7990">RFC7990</a>] Flanagan, H., "RFC Format Framework", <a href="./rfc7990">RFC 7990</a>,
DOI 10.17487/RFC7990, December 2016,
<<a href="http://www.rfc-editor.org/info/rfc7990">http://www.rfc-editor.org/info/rfc7990</a>>.
[<a id="ref-RFC7998">RFC7998</a>] Hoffman, P. and J. Hildebrand, ""xml2rfc" Version 3
Preparation Tool Description", <a href="./rfc7998">RFC 7998</a>,
DOI 10.17487/RFC7998, December 2016,
<<a href="http://www.rfc-editor.org/info/rfc7998">http://www.rfc-editor.org/info/rfc7998</a>>.
[<a id="ref-W3C.WD-css3-page-20130314">W3C.WD-css3-page-20130314</a>]
Grant, M., Etemad, E., Lie, H., and S. Sapin, "CSS Paged
Media Module Level 3", World Wide Web Consortium
WD WD-css3-page-20130314, March 2013,
<<a href="http://www.w3.org/TR/2013/WD-css3-page-20130314">http://www.w3.org/TR/2013/WD-css3-page-20130314</a>>.
<span class="grey">Hildebrand & Hoffman Informational [Page 42]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-43" ></span>
<span class="grey"><a href="./rfc7992">RFC 7992</a> HTML for RFCs December 2016</span>
IAB Members at the Time of Approval
The IAB members at the time this memo was approved were (in
alphabetical order):
Jari Arkko
Ralph Droms
Ted Hardie
Joe Hildebrand
Russ Housley
Lee Howard
Erik Nordmark
Robert Sparks
Andrew Sullivan
Dave Thaler
Martin Thomson
Brian Trammell
Suzanne Woolf
Acknowledgments
Heather Flanangan was an early coauthor of this document and helped
its formation. The authors gratefully acknowledge the contributions
of: Patrick Linskey and the members of the RFC Format Design Team
(Nevil Brownlee (ISE), Tony Hansen, Ted Lemon, Julian Reschke, Adam
Roach, Alice Russo, Robert Sparks (Tools Team liaison), and Dave
Thaler).
Authors' Addresses
Joe Hildebrand (editor)
Mozilla
Email: joe-ietf@cursive.net
Paul Hoffman
ICANN
Email: paul.hoffman@icann.org
Hildebrand & Hoffman Informational [Page 43]
</pre>
|