index.html
116 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
<!DOCTYPE html PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN' 'http://www.w3.org/TR/html4/loose.dtd'>
<html lang="en" dir="ltr">
<head>
<title>HTML+RDFa 1.1</title>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8">
<!--
=== NOTA BENE ===
For the three scripts below, if your spec resides on dev.w3 you can check them
out in the same tree and use relative links so that they'll work offline,
-->
<style type="text/css">code { font-family: monospace; }
span.hilite { color: red; /* font-weight: bold */ }
li p { margin-top: 0.3em;
margin-bottom: 0.3em; }
div.explanation { background-color: #ADD8E6;
width: 80%;
margin: 12px; padding: 8px; }
div.explanation li { margin-top: 8px; }
div.explanation dd { margin: 4px; }
.adef {
font-family: monospace;
font-weight: bold;
color: #ff4500;
}
.aref {
font-family: monospace;
font-weight: bold;
color: #ff4500;
}
a.tref {
font-family: monospace;
font-weight: bold;
color: #4500ff;
}
span.entity { color: red; }
span.element { color: green; }
</style><link href="respec.css" rel="stylesheet" type="text/css" charset="utf-8"><link href="http://www.w3.org/StyleSheets/TR/W3C-WD" rel="stylesheet" type="text/css" charset="utf-8"></head><body style="display: inherit; "><div class="head"><p><a href="http://www.w3.org/"><img width="72" height="48" src="http://www.w3.org/Icons/w3c_home" alt="W3C"></a></p><h1 class="title" id="title">HTML+RDFa 1.1</h1><h2 id="subtitle">Support for RDFa in HTML4 and HTML5</h2><h2 id="w3c-working-draft-24-june-2010"><acronym title="World Wide Web Consortium">W3C</acronym> Working Draft 24 June 2010</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2010/WD-rdfa-in-html-20100624/">http://www.w3.org/TR/2010/WD-rdfa-in-html-20100624/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/rdfa-in-html/">http://www.w3.org/TR/rdfa-in-html/</a></dd><dt>Latest editor's draft:</dt><dd><a href="http://dev.w3.org/html5/rdfa/">http://dev.w3.org/html5/rdfa/</a></dd><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2010/WD-rdfa-in-html-20100304/">http://www.w3.org/TR/2010/WD-rdfa-in-html-20100304/</a></dd><dt>Editors:</dt><dd><a href="mailto:msporny@digitalbazaar.com">Manu Sporny</a>, <a href="http://blog.digitalbazaar.com">Digital Bazaar, Inc.</a></dd><dd><a href="mailto:shane@aptest.com">Shane McCarron</a>, <a href="http://www.aptest.com/">Applied Testing and Technology, Inc.</a></dd><dt>Authors:</dt><dd>Ben Adida, <a href="http://creativecommons.org/">Creative Commons</a></dd><dd>Mark Birbeck, <a href="http://webbackplane.com/">Backplane Ltd.</a></dd><dd>Steven Pemberton, <a href="http://www.cwi.nl/">CWI</a></dd></dl><p>This document is also available in this non-normative format: <a href="diff-20100304.html">Changes since previous Working Draft</a>.</p><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> © 2009-2010 <a href="http://www.w3.org/"><acronym title="World Wide Web Consortium"><acronym title="World Wide Web Consortium">W3C</acronym></acronym></a><sup>®</sup> (<a href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of Technology"><acronym title="Massachusetts Institute of Technology">MIT</acronym></acronym></a>, <a href="http://www.ercim.eu/"><acronym title="European Research Consortium for Informatics and Mathematics"><acronym title="European Research Consortium for Informatics and Mathematics">ERCIM</acronym></acronym></a>, <a href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. <acronym title="World Wide Web Consortium">W3C</acronym> <a href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="http://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.</p><hr></div>
<div id="abstract" class="introductory section"><h2>Abstract</h2>
<p>This specification defines rules and guidelines for adapting the RDFa Core
1.1 specification for use in HTML5 and XHTML5. The rules defined in this
specification not only apply to HTML5 documents in non-XML and XML mode,
but also to HTML4 and XHTML documents interpreted through the HTML5 parsing
rules.</p>
</div><div id="sotd" class="introductory section"><h2>Status of This Document</h2><p><em>This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current <acronym title="World Wide Web Consortium">W3C</acronym> publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/"><acronym title="World Wide Web Consortium">W3C</acronym> technical reports index</a> at http://www.w3.org/TR/.</em></p>
<!-- <p>This document has been reviewed by W3C Members, by software
developers, and by other W3C groups and interested parties, and is
endorsed by the Director as a W3C Recommendation. It is a stable
document and may be used as reference material or cited from another
document. W3C's role in making the Recommendation is to draw attention
to the specification and to promote its widespread deployment. This
enhances the functionality and interoperability of the Web.</p> -->
<p>There are a number of substantive differences between this version and its
predecessor, including:</p>
<ol>
<li>Inheritance of basic processing rules from RDFa 1.1 [<a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a>], instead of
XHTML+RDFa 1.0 [<a class="bibref" rel="biblioentry" href="#bib-RDFA-SYNTAX">RDFA-SYNTAX</a>].</li>
<li>Inclusion of the HTML Default Vocabulary Terms, which mirror the XHTML
Default Vocabulary Terms, for the purpose of HTML/XHTML interoperability.</li>
<li>Inclusion of a HTML 4.01 + RDFa 1.1 DTD for validation purposes.</li>
<li>Added normative definition of @version attribute.</li>
</ol>
<p>The latest stable version of the editor's draft of this specification is
always available on <a href="http://dev.w3.org/html5/rdfa/">the <acronym title="World Wide Web Consortium">W3C</acronym> CVS
server</a>.
<!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING LIST TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- status of document, group responsible (required) -->
</p><p>This specification has been jointly developed by the <a href="http://www.w3.org/2010/02/rdfa/">RDFa Working Group</a> and the
<a href="http://www.w3.org/html/wg/">HTML Working Group</a> and is
currently being published by the <a href="http://www.w3.org/html/wg/">HTML
Working Group</a> to further discussions on HTML and RDFa integration.</p>
<!-- UNDER NO CIRCUMSTANCES IS THE FOLLOWING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- UNDER NO CIRCUMSTANCES IS THE PRECEDING PARAGRAPH TO BE REMOVED OR EDITED WITHOUT TALKING TO IAN FIRST --><!-- context and rationale (required) -->
<p>This specification is an extension to the HTML5 language. All normative
content in the HTML5 specification, unless specifically overridden by this
specification, is intended to be the basis for this specification.</p>
<p>A <a href="http://rdfa.digitalbazaar.com/rdfa-test-harness/">sample
test harness</a> is available. This set of tests is
not intended to be exhaustive. Users may find the tests to
be useful examples of RDFa usage.
A community-maintained
<a href="http://rdfa.info/rdfa-implementations/">Wiki page</a> includes
subsequent updates.</p>
<p>This document was published by the <a href="http://www.w3.org/html/wg">HTML Working Group</a> as a Working Draft. This document is intended to become a <acronym title="World Wide Web Consortium">W3C</acronym> Recommendation. If you wish to make comments regarding this document, please send them to <a href="mailto:public-rdfa-wg@w3.org">public-rdfa-wg@w3.org</a> (<a href="mailto:public-rdfa-wg-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-rdfa-wg/">archives</a>). All feedback is welcome.</p><p>Publication as a Working Draft does not imply endorsement by the <acronym title="World Wide Web Consortium">W3C</acronym> Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.</p><p>This document was produced by a group operating under the <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/">5 February 2004 <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>. <acronym title="World Wide Web Consortium">W3C</acronym> maintains a <a href="http://www.w3.org/2004/01/pp-impl/40318/status" rel="disclosure">public list of any patent disclosures</a> made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#def-essential">Essential Claim(s)</a> must disclose the information in accordance with <a href="http://www.w3.org/Consortium/Patent-Policy-20040205/#sec-Disclosure">section 6 of the <acronym title="World Wide Web Consortium">W3C</acronym> Patent Policy</a>.</p>
<p>Also available is a <a href="http://www.w3.org/2004/01/pp-impl/44350/status">public list of any patent disclosures</a>
for the <a href="http://www.w3.org/2010/02/rdfa/">RDFa Working Group</a>.</p>
</div>
<div id="toc" class="section"><h2 class="introductory">Table of Contents</h2><ul class="toc"><li class="tocline"><a href="#introduction" class="tocxref"><span class="secno">1. </span>Introduction</a></li><li class="tocline"><a href="#conformance" class="tocxref"><span class="secno">2. </span>Conformance</a><ul class="toc"><li class="tocline"><a href="#document-conformance" class="tocxref"><span class="secno">2.1 </span>Document Conformance</a></li><li class="tocline"><a href="#rdfa-processor-conformance" class="tocxref"><span class="secno">2.2 </span>RDFa Processor Conformance</a></li><li class="tocline"><a href="#user-agent-conformance" class="tocxref"><span class="secno">2.3 </span>User Agent Conformance</a></li></ul></li><li class="tocline"><a href="#extensions-to-rdfa-core-1.1" class="tocxref"><span class="secno">3. </span>Extensions to RDFa Core 1.1</a><ul class="toc"><li class="tocline"><a href="#additional-rdfa-processing-rules" class="tocxref"><span class="secno">3.1 </span>Additional RDFa Processing Rules</a></li><li class="tocline"><a href="#modifying-the-input-document" class="tocxref"><span class="secno">3.2 </span>Modifying the Input Document</a></li><li class="tocline"><a href="#specifying-the-language-for-a-literal" class="tocxref"><span class="secno">3.3 </span>Specifying the language for a literal</a></li><li class="tocline"><a href="#invalid-xmlliteral-values" class="tocxref"><span class="secno">3.4 </span>Invalid XMLLiteral values</a></li><li class="tocline"><a href="#xmlns--prefixed-attributes" class="tocxref"><span class="secno">3.5 </span><code>xmlns:</code>-Prefixed Attributes</a></li></ul></li><li class="tocline"><a href="#extensions-to-the-html5-syntax" class="tocxref"><span class="secno">4. </span>Extensions to the HTML5 Syntax</a><ul class="toc"><li class="tocline"><a href="#the-rdfa-attributes-and-valid-values" class="tocxref"><span class="secno">4.1 </span>The RDFa Attributes and Valid Values</a><ul class="toc"><li class="tocline"><a href="#the-version-attribute" class="tocxref"><span class="secno">4.1.1 </span>The version Attribute</a></li></ul></li><li class="tocline"><a href="#conformance-criteria-for-xmlns--prefixed-attributes" class="tocxref"><span class="secno">4.2 </span>Conformance Criteria for <code>xmlns:</code>-Prefixed Attributes</a></li><li class="tocline"><a href="#preserving-namespaces-via-coercion-to-infoset" class="tocxref"><span class="secno">4.3 </span>Preserving Namespaces via Coercion to Infoset</a></li><li class="tocline"><a href="#infoset-based-processors" class="tocxref"><span class="secno">4.4 </span>Infoset-based Processors</a><ul class="toc"><li class="tocline"><a href="#extracting-uri-mappings-from-infosets" class="tocxref"><span class="secno">4.4.1 </span>Extracting URI Mappings from Infosets</a></li><li class="tocline"><a href="#processing-rdfa-attributes" class="tocxref"><span class="secno">4.4.2 </span>Processing RDFa Attributes</a></li></ul></li><li class="tocline"><a href="#dom-level-2-based-processors" class="tocxref"><span class="secno">4.5 </span>DOM Level 2-based Processors</a><ul class="toc"><li class="tocline"><a href="#extracting-uri-mappings-from-doms" class="tocxref"><span class="secno">4.5.1 </span>Extracting URI Mappings from DOMs</a></li><li class="tocline"><a href="#processing-rdfa-attributes-1" class="tocxref"><span class="secno">4.5.2 </span>Processing RDFa Attributes</a></li></ul></li></ul></li><li class="tocline"><a href="#html-default-vocabulary-terms" class="tocxref"><span class="secno">A. </span>HTML Default Vocabulary Terms</a></li><li class="tocline"><a href="#validation" class="tocxref"><span class="secno">B. </span>Validation</a><ul class="toc"><li class="tocline"><a href="#the-html-4.01---rdfa-1.1-dtd" class="tocxref"><span class="secno">B.1 </span>The HTML 4.01 + RDFa 1.1 DTD</a></li></ul></li><li class="tocline"><a href="#about-this-document" class="tocxref"><span class="secno">C. </span>About this Document</a><ul class="toc"><li class="tocline"><a href="#history" class="tocxref"><span class="secno">C.1 </span>History</a></li><li class="tocline"><a href="#change-history" class="tocxref"><span class="secno">C.2 </span>Change History</a></li><li class="tocline"><a href="#acknowledgments" class="tocxref"><span class="secno">C.3 </span>Acknowledgments</a></li></ul></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">D. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">D.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">D.2 </span>Informative references</a></li></ul></li></ul></div>
<div class="informative section" id="introduction">
<!--OddPage--><h2><span class="secno">1. </span>Introduction</h2><p><em>This section is non-normative.</em></p>
<p>Today's web is built predominantly for human consumption. Even as
machine-readable data begins to permeate the web, it is typically
distributed in a separate file, with a separate format, and very limited
correspondence between the human and machine versions. As a result, web
browsers can provide only minimal assistance to humans in parsing and
processing web data: browsers only see presentation information. RDFa is
intended to solve the problem of machine-readable data in HTML documents.
RDFa provides a set of HTML attributes to augment visual data with
machine-readable hints. Using RDFa, authors may turn their existing
human-visible text and links into machine-readable data without repeating
content.</p>
</div>
<div id="conformance" class="section"><!--OddPage--><h2><span class="secno">2. </span>Conformance</h2><p>As well as sections marked as non-normative, all authoring guidelines, diagrams, examples, and notes in this specification are non-normative. Everything else in this specification is normative.</p>
<p>The key words <em class="rfc2119" title="must">must</em>, <em class="rfc2119" title="must not">must not</em>, <em class="rfc2119" title="required">required</em>, <em class="rfc2119" title="should">should</em>, <em class="rfc2119" title="should not">should not</em>, <em class="rfc2119" title="recommended">recommended</em>, <em class="rfc2119" title="may">may</em>, and <em class="rfc2119" title="optional">optional</em> in this specification are to be interpreted as described in [<a class="bibref" rel="biblioentry" href="#bib-RFC2119">RFC2119</a>].</p>
<div id="document-conformance" class="section">
<h3><span class="secno">2.1 </span>Document Conformance</h3>
<p>In order for a document to claim that it is a conforming HTML+RDFa
document, it <em class="rfc2119" title="must">must</em> provide the facilities described as mandatory in this
section. The document conformance criteria are listed below, of which only
a subset are mandatory:</p>
<ul>
<li>All document conformance requirements stated as mandatory in the
HTML5 specification <em class="rfc2119" title="must">must</em> be met.</li>
<li>All
<a href="#extensions-to-the-html5-syntax">Extensions to the HTML5 Syntax</a>,
as described in this document, <em class="rfc2119" title="must">must</em> be considered valid and conforming in
a HTML+RDFa 1.1 document.</li>
<li>All HTML5 elements and attributes <em class="rfc2119" title="should">should</em> be used in a way that is
conformant with [<a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a>]. All RDFa attributes <em class="rfc2119" title="should">should</em> be used in a way that
is conformant with [<a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a>] and this document.</li>
<li>There <em class="rfc2119" title="should">should</em> be a <code>version</code> attribute on the
<code>html</code> element. The value of the <code>version</code>
attribute <em class="rfc2119" title="should">should</em> be "HTML+RDFa 1.1" if the document is a non-XML mode
document, or "XHTML+RDFa 1.1" if the document is a XML mode
document.</li>
<li>If HTML4 is the target language, the document <em class="rfc2119" title="should">should</em> conform to the
constraints expressed in the
<a href="#html-rdfa-dtd">HTML 4.01 + RDFa 1.1 Document Type Definition</a>
located in the Appendix.
</li>
</ul>
<p>An example of a conforming HTML+RDFa document:</p>
<pre class="example" title="Example of an HTML+RDFa 1.1 document"><<span class="hilite">html</span> <span class="hilite">version="HTML+RDFa 1.1"</span> lang="en">
<head>
<title>Example Document</title>
</head>
<body>
<p>Moved to <a href="http://example.org/">example.org</a>.</p>
</body>
</html></pre>
<p>Non-XML mode HTML+RDFa 1.1 documents <em class="rfc2119" title="should">should</em> be labeled with the Internet Media Type
"text/html" as defined in [<a class="bibref" rel="biblioentry" href="#bib-RFC3236">RFC3236</a>].
</p>
</div>
<div id="rdfa-processor-conformance" class="section">
<h3><span class="secno">2.2 </span>RDFa Processor Conformance</h3>
<p>The RDFa Processor conformance criteria are listed below, all of
which are mandatory:</p>
<ul>
<li>An RDFa Processor <em class="rfc2119" title="must">must</em> implement all of the mandatory features
specified in the RDFa Core 1.1 specification [<a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a>].</li>
<li>An RDFa Processor <em class="rfc2119" title="must">must</em> support any mandatory features described in this
specification.</li>
</ul>
</div>
<div id="user-agent-conformance" class="section">
<h3><span class="secno">2.3 </span>User Agent Conformance</h3>
<p>A User Agent is considered to be a type of RDFa Processor when the
User Agent stores or processes RDFa attributes and their values. The
reason there are separate <em>RDFa Processor Conformance</em> and a
<em>User Agent Conformance</em> sections is because one can be a valid
HTML5 RDFa Processor but not a valid HTML5 User Agent (for example, by only
providing a very small subset of rendering functionality).
</p>
<p>The User Agent conformance criteria are listed below, all of which are
mandatory:</p>
<ul>
<li>A User Agent <em class="rfc2119" title="must">must</em> conform to all requirements listed in the
<span>Conformance requirements</span> section of the HTML5 specification.
</li>
<li>A User Agent <em class="rfc2119" title="must">must</em> implement all of the features required by this
specification.</li>
<li>A User Agent <em class="rfc2119" title="must">must</em> implement all of the features required in the RDFa
Core 1.1 specification, excluding those features which are specifically
overridden by this specification as detailed in the <a href="#extensions-to-rdfa-core-1.1">Extensions to RDFa Core 1.1</a>.</li>
</ul>
</div>
</div>
<div id="extensions-to-rdfa-core-1.1" class="section">
<!--OddPage--><h2><span class="secno">3. </span>Extensions to RDFa Core 1.1</h2>
<p>The RDFa Core 1.1 [<a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a>] specification is the base document on
which this specification builds.
RDFa Core 1.1 specifies the attributes and syntax, in <a href="http://www.w3.org/TR/rdfa-core#s_syntax">Section 5: Attributes and
Syntax</a>, and processing model, in <a href="http://www.w3.org/TR/rdfa-core/#s_model">Section 7: Processing
Model</a>, for extracting RDF from a Web document. This section
specifies changes to the attributes and processing model defined in
RDFa Core 1.1 in order to support extracting RDF from HTML documents.</p>
<p>The requirements and rules, as specified in RDFa Core and further
extended in this document, apply to all HTML5 documents. The RDFa Processor
operating on HTML and XHTML documents, specifically the resulting DOMs or
Infosets, <em class="rfc2119" title="must">must</em> apply the same processing rules for HTML4, HTML5 and XHTML5
serializations, DOMs and/or Infosets.</p>
<div id="additional-rdfa-processing-rules" class="section">
<h3><span class="secno">3.1 </span>Additional RDFa Processing Rules</h3>
<p>Documents conforming to the rules in this specification are processed
according to [<a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a>] with the following extensions:</p>
<ul>
<li>The <a class="tref" title="default_vocabulary_URI">default vocabulary URI</a> is <code>http://www.w3.org/1999/xhtml/vocab#</code>.</li>
<li>The <a class="tref" title="default_collection_of_terms">default collection of terms</a> is defined in
<a href="#html-default-vocabulary-terms">HTML Default Vocabulary Terms</a>.</li>
<li>The <a class="tref" title="base">base</a> can be set using the <code>base</code> element.</li>
<li>The <a class="tref" title="current_language">current language</a> can be set using either the
<span class="aref">@lang</span> or <span class="aref">@xml:lang</span> attributes.</li>
<li>In
<a href="http://www.w3.org/TR/rdfa-core/#sequence">Section 7.5: Sequence</a>,
processing step 6, if no URI is provided by a resource attribute, then
first check to see if the element is the <code>head</code> or
<code>body</code> element. If it is, then act as if there is an empty <span class="aref">@about</span> present,
and process it according to the rule for <span class="aref">@about</span>.</li>
<li>In
<a href="http://www.w3.org/TR/rdfa-core/#sequence">Section 7.5: Sequence</a>,
processing step 7, if no URI is provided, then
first check to see if the element is the <code>head</code> or
<code>body</code> element. If it is, then act as if there is an empty <span class="aref">@about</span> present,
and process it according to the rule for <span class="aref">@about</span>.</li>
</ul>
</div>
<div id="modifying-the-input-document" class="section">
<h3><span class="secno">3.2 </span>Modifying the Input Document</h3>
<p>RDFa's tree-based processing rules, outlined in <a href="http://www.w3.org/TR/rdfa-core#sequence">Section 7.5: Sequence</a> of
the RDFa Core 1.1 specification [<a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a>], allow an input document to be
automatically corrected, cleaned-up, re-arranged, or modified in any way that
is approved by the host language prior to processing. Element nesting issues
in HTML documents <em class="rfc2119" title="should">should</em> be corrected before the input document is
translated into the DOM, a valid tree-based model, on which the RDFa
processing rules will operate.</p>
<p>Any mechanism that generates a data structure equivalent to the HTML5 or
XHTML5 DOM, such as the html5lib library, <em class="rfc2119" title="may">may</em> be used as the mechanism to
construct the tree-based model provided as input to the RDFa processing
rules.</p>
</div>
<div id="specifying-the-language-for-a-literal" class="section">
<h3><span class="secno">3.3 </span>Specifying the language for a literal</h3>
<p>RDFa Core 1.1 allows for the
<a class="tref" title="current_language" href="http://www.w3.org/TR/rdfa-core#dfn-current_language">current language</a>
to be specified by the Host Language. In order for RDFa Processors to conform
to this specification, they <em class="rfc2119" title="must">must</em> use the mechanism described in
<em>The lang and xml:lang attributes</em> section of the [<a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a>]
specification to determine the
<a class="tref" title="language" href="http://www.w3.org/TR/html5/Overview.html#language">language</a>
of a node.</p>
<p>If an author is editing an HTML fragment and is unsure of the final
encapsulating MIME type for their markup, it is suggested that the author
specify both <code>lang</code> and <code>xml:lang</code> where the value in
both attributes is exactly the same.</p>
</div>
<div id="invalid-xmlliteral-values" class="section">
<h3><span class="secno">3.4 </span>Invalid XMLLiteral values</h3>
<p>When generating literals of type XMLLiteral, the processor <em class="rfc2119" title="must">must</em> ensure
that the output XMLLiteral is a namespace well-formed XML fragment. A
namespace well-formed XML fragment has the following properties:</p>
<ul>
<li>The XML fragment, when placed inside of a single root element, <em class="rfc2119" title="must">must</em>
validate as well-formed XML. The normative language that describes a
well-formed XML document is specified in <a href="http://www.w3.org/TR/REC-xml/#sec-well-formed">Section 2.1 "Well-Formed
XML Documents"</a> of the XML specification.</li>
<li>The XML fragment, when placed inside of a single root element, <em class="rfc2119" title="must">must</em>
retain all active namespace information. The currently active attributes
declared using <code>xmlns</code> and <code>xmlns:</code> stored in the
RDFa Processor's current
<a class="tref" title="evaluation_context" href="http://www.w3.org/TR/rdfa-core#dfn-evaluation_context">evaluation context</a>
in the
<a class="tref" title="list_of_URI_mappings" href="http://www.w3.org/TR/rdfa-core#dfn-list_of_uri_mappings">list of URI mappings</a>
<em class="rfc2119" title="must">must</em> be preserved in the generated XMLLiteral. The <em>PREFIX</em> value for
<code>xmlns:PREFIX</code> <em class="rfc2119" title="must">must</em> be transformed to all lower-case characters
when preserving the value in the XMLLiteral. All active namespaces declared
via <code>xmlns</code> and <code>xmlns:</code> <em class="rfc2119" title="must">must</em> be placed in each
top-level element in the generated XMLLiteral, taking care to not overwrite
pre-existing namespace values.</li>
</ul>
<p>An RDFa Processor that transforms the XML fragment <em class="rfc2119" title="must">must</em> use the <a href="http://www.w3.org/TR/html5/Overview.html#coercing-an-html-dom-into-an-infoset">
Coercing an HTML DOM into an Infoset</a> algorithm, as specified in the HTML5
specification, followed by the algorithm defined in the <a href="http://www.w3.org/TR/html5/Overview.html#serializing-xhtml-fragments">Serializing
XHTML Fragments</a> section of the HTML5 specification. If an error or
exception occurs at any point during the transformation, the triple containing
the XMLLiteral <em class="rfc2119" title="must not">must not</em> be generated.</p>
<p>Transformation to a namespace well-formed XML fragment is required
because an application that consumes XMLLiteral data expects that data to
be a namespace well-formed XML fragment.</p>
<p>The transformation requirement does not apply to input data that are
text-only, such as literals that contain a <code>datatype</code> attribute
with an empty value (<code>""</code>), or input data that that contain only
text nodes.</p>
<p>An example transformation demonstrating the preservation of namespace
values is provided below. The → symbol is used to denote that the line
is a continuation of the previous line and is included purely for the
purposes of readability:</p>
<pre class="example" title="Namespace preservation markup"><p xmlns:ex="http://example.org/vocab#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
Two rectangles (the example markup for them are stored in a triple):
<svg <span class="hilite">xmlns</span>="<span class="hilite">http://www.w3.org/2000/svg</span>" property="ex:markup" datatype="rdf:XMLLiteral">
→<rect width="300" height="100" style="fill:rgb(0,0,255);stroke-width:1; stroke:rgb(0,0,0)">
→<rect width="50" height="50" style="fill:rgb(255,0,0);stroke-width:2;stroke:rgb(0,0,0)"></rect></rect></svg>
</p></pre>
<p>The markup above <em class="rfc2119" title="should">should</em> produce the following triple, which preserves the
xmlns declaration in the markup by injecting the <code>xmlns</code> attribute
in the <code>rect</code> elements:</p>
<pre class="example" title="Namespace preservation triple"><>
<http://example.org/vocab#markup>
"<rect <span class="hilite">xmlns=\"http://www.w3.org/2000/svg\"</span> width=\"300\"
→height=\"100\" style=\"fill:rgb(0,0,255);stroke-width:1; stroke:rgb(0,0,0)\"/>
→<rect <span class="hilite">xmlns=\"http://www.w3.org/2000/svg\"</span> width=\"50\"
→height=\"50\" style=\"fill:rgb(255,0,0);stroke-width:2;
→stroke:rgb(0,0,0)\"/>"^^http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral .</pre>
<p>Since the <code>ex</code> and <code>rdf</code>
namespaces are not used in either <code>rect</code> element, they are not
preserved in the XMLLiteral.
</p>
<p>Similarly, compound document elements that reside in different
namespaces must have their namespaces declarations preserved:</p>
<pre class="example" title="Namespace preservation for compound document elements"><p xmlns:ex="http://example.org/vocab#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<span class="hilite">xmlns:fb="http://www.facebook.com/2008/fbml"</span>
This is how you markup a user in FBML:
<span property="ex:markup" datatype="rdf:XMLLiteral">
→<p><fb:user uid="12345">The User</fb:user></p>
→</span>
</p></pre>
<p>The markup above <em class="rfc2119" title="should">should</em> produce the following triple, which preserves the
<code>fb</code> namespace in the corresponding triple:</p>
<pre class="example" title="Namespace element preservation triple"><>
<http://example.org/vocab#markup>
"<p <span class="hilite">xmlns:fb="http://www.facebook.com/2008/fbml"</span>>
→<fb:user uid="12345">
→</p>"^^http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral .</pre>
<p></p>
</div>
<div id="xmlns--prefixed-attributes" class="section">
<h3><span class="secno">3.5 </span><code>xmlns:</code>-Prefixed Attributes</h3>
<p class="issue">While this section outlines xmlns: processing in RDFa, the
support for distributed extensibility in non-XML mode HTML5 (using xmlns
and xmlns:) is still an open issue. This section may be further modified
before Last Call based on progress made on the distributed extensibility
issue.</p>
<p>CURIE prefix mappings specified using attributes prepended with
<code>xmlns:</code> <em class="rfc2119" title="must">must</em> be processed using the algorithm defined in
section 4.4.1:
<a href="#extracting-uri-mappings-from-infosets">Extracting URI Mappings from Infosets</a>
for Infoset-based processors, or section 4.5.1:
<a href="#extracting-uri-mappings-from-doms">Extracting URI Mappings from DOMs</a>
for DOM Level 2-based processors. For CURIE prefix mappings using the
<code>prefix</code> attribute,
<a href="http://www.w3.org/TR/rdfa-core/#sequence">Section 7.5: Sequence</a>,
step #4 <em class="rfc2119" title="must">must</em> be used to process namespace values.</p>
<p>Since CURIE prefix mappings have been specified using
<code>xmlns:</code>, and since HTML attribute names are case-insensitive,
CURIE prefix names declared using the <code>xmlns:</code>attribute-name
pattern <code>xmlns:<PREFIX>="<URI>"</code> <em class="rfc2119" title="should">should</em> be specified
using only lower-case characters. For example, the text
"<code>xmlns:</code>" and the text in <code>"<PREFIX>"</code> <em class="rfc2119" title="should">should</em>
be lower-case only. This is to ensure that prefix mappings are interpreted
in the same way between HTML (case-insensitive attribute names) and XHTML
(case-sensitive attribute names) document types.</p>
</div>
</div>
<div id="extensions-to-the-html5-syntax" class="section">
<!--OddPage--><h2><span class="secno">4. </span>Extensions to the HTML5 Syntax</h2>
<p class="issue"><b>Status:</b> <a href="http://www.w3.org/html/wg/tracker/issues/41">ISSUE-41</a> (decentralized extensibility) blocks progress to Last Call</p>
<p>There are a few extensions to the HTML5 specification that are required in
order to fully support RDFa. The following sub-sections outline the
necessary extensions to the base HTML5 specification.</p>
<div id="the-rdfa-attributes-and-valid-values" class="section">
<h3><span class="secno">4.1 </span>The RDFa Attributes and Valid Values</h3>
<p>All RDFa attributes and valid values (including CURIEs), as listed in
<a href="http://www.w3.org/TR/rdfa-core/#rdfa-attributes">Section 2.1:
The RDFa Attributes</a>, are conforming when used in an HTML5 or XHTML5
document.</p>
<div id="the-version-attribute" class="section">
<h4><span class="secno">4.1.1 </span>The version Attribute</h4>
<p>The <code>@version</code> attribute is an <em class="rfc2119" title="optional">optional</em> attribute that is
allowed on the <code>html</code> element. It specifies the HTML5 language
features that are enabled for the current document. The value <em class="rfc2119" title="must">must</em> contain at
least one non-<strong>space character</strong>. The value must conform to a
<strong>set of space-separated tokens</strong>, as defined in
[<a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a>], Space-separated tokens.
</p>
</div>
</div>
<div id="conformance-criteria-for-xmlns--prefixed-attributes" class="section">
<h3><span class="secno">4.2 </span>Conformance Criteria for <code>xmlns:</code>-Prefixed Attributes</h3>
<p class="issue">While this section outlines xmlns: conformance criteria for
HTML+RDFa, the support for distributed extensibility in non-XML mode HTML5
(using xmlns and xmlns:) is still an open issue. This section may be
further modified before Last Call based on progress made on the distributed
extensibility issue.</p>
<p>Since RDFa uses attributes starting with <code>xmlns:</code> to specify
CURIE prefixes, any attribute starting with a case-insensitive match on the
text string "<code>xmlns:</code>" <em class="rfc2119" title="must">must</em> be preserved in the DOM or other
tree-like model that is passed to the RDFa Processor.
For documents conforming to this specification, attributes with
names that have a case insensitive prefix matching "<code>xmlns:</code>"
<em class="rfc2119" title="must">must</em> be considered conforming. Conformance checkers <em class="rfc2119" title="must">must</em>
accept attribute names that have a case insensitive prefix matching
"<code>xmlns:</code>" as conforming.
</p>
<p>All attributes starting with a case insensitive prefix matching
"<code>xmlns:</code>" <em class="rfc2119" title="must">must</em> conform to the production rules outlined in
Namespaces in XML [<a class="bibref" rel="biblioentry" href="#bib-XML-NAMES11">XML-NAMES11</a>],
<a href="http://www.w3.org/TR/xml-names11#ns-decl">Section 3: Declaring Namespaces</a>.
Documents that contain <code>xmlns:</code> attributes that do not conform to
Namespaces in XML <em class="rfc2119" title="must not">must not</em> be accepted as conforming.
</p>
</div>
<div id="preserving-namespaces-via-coercion-to-infoset" class="section">
<h3><span class="secno">4.3 </span>Preserving Namespaces via Coercion to Infoset</h3>
<p class="issue">This section needs feedback from the user agent vendors to
ensure that this feature does not conflict with user agent architecture and
has no technical reason that it cannot be implemented.</p>
<p>RDFa is uses the <code>xmlns:</code> pattern to
declare prefix mappings, it is important that namespace information that
is declared in non-XML mode HTML5 documents are mapped to an Infoset
correctly. In order to ensure this mapping is performed correctly, the
"Coercing an HTML DOM into an infoset" rules defined in [<a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a>]
must be extended to include the following rule:</p>
<p>If the XML API is namespace-aware, the tool must ensure that
([<a href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">namespace
name</a>], [<a href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">local name</a>],
[<a href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">normalized
value</a>]) namespace tuples are created when converting the non-XML mode
DOM into an Infoset. Given a standard <code>xmlns:</code> definition,
<code>xmlns:foo="http://example.org/bar#"</code>, the [namespace name]
is <code>http://www.w3.org/2000/xmlns/</code>,
the [local name] is <code>foo</code>, and the
[normalized value] is <code>http://example.org/bar#</code>, thus the
namespace tuple would be (<code>http://www.w3.org/2000/xmlns/</code>,
<code>foo</code>, <code>http://example.org/bar#</code>).</p>
<p>For example, given the following input text:</p>
<pre class="example"><div xmlns:audio="http://purl.org/media/audio#"></pre>
<p>
The <code>div</code> element above, when coerced from an HTML DOM into
an Infoset, should contain an attribute in the [<a href="http://www.w3.org/TR/xml-infoset/#infoitem.element">namespace
attributes</a>] list with a [namespace name] set to
"<code>http://www.w3.org/2000/xmlns/</code>", a [local name] set to
<code>audio</code>, and a [normalized value] of
"<code>http://purl.org/media/audio#</code>".
</p>
</div>
<div id="infoset-based-processors" class="section">
<h3><span class="secno">4.4 </span>Infoset-based Processors</h3>
<p>While the intent of the RDFa processing instructions were to provide a
set of rules that are as language and toolchain agnostic as possible, for
the sake of clarity, detailed methods of extracting RDFa content from
processors operating on an XML Information Set are provided below.</p>
<div id="extracting-uri-mappings-from-infosets" class="section">
<h4><span class="secno">4.4.1 </span>Extracting URI Mappings from Infosets</h4>
<p>Extracting URI Mappings declared via <code>xmlns:</code>
while operating from within an Infoset-based RDFa processor can be achieved
using the following algorithm:</p>
<p>While processing an element as described in [<a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a>],
<a href="http://www.w3.org/TR/rdfa-core#sequence">Section 7.5: Sequence</a>,
Step #2:</p>
<ol>
<li>For each attribute in the [<a href="http://www.w3.org/TR/xml-infoset/#infoitem.element">namespace
attributes</a>] list that has a [<a href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">prefix</a>] value,
create a [<a href="http://www.w3.org/TR/rdfa-core/#dfn-uri_mapping">URI
mapping</a>] by storing the [prefix] as the value to be mapped, and the
[<a href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">normalized
value</a>] as the value to map.</li>
<li>For each attribute in the [<a href="http://www.w3.org/TR/xml-infoset/#infoitem.element">attributes</a>] list
that has no value for [<a href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">prefix</a>] and a
[<a href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">local
name</a>] that starts with <code>xmlns:</code>, create a [<a href="http://www.w3.org/TR/rdfa-core/#dfn-uri_mapping">URI mapping</a>] by
storing the [local name] part with the <code>xmlns:</code> characters
removed as the value to be mapped, and the [<a href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">normalized
value</a>] as the value to map.
<p class="note">This step is unnecessary if the Infoset coercion
rules preserve namespaces specified in non-XML mode.</p></li>
</ol>
<p>For example, assume that the following markup is processed by an
Infoset-based RDFa processor:</p>
<pre class="example"><div xmlns:audio="http://purl.org/media/audio#" ...</pre>
<p>After the markup is processed, there should exist a [URI mapping] in
the [local list of URI mappings] that contains a mapping from
<code>audio</code> to <code>http://purl.org/media/audio#</code>.
</p>
</div>
<div id="processing-rdfa-attributes" class="section">
<h4><span class="secno">4.4.2 </span>Processing RDFa Attributes</h4>
<p>There are a number of non-prefixed attributes that are associated with
RDFa Processing in HTML5. If an XML Information Set based RDFa processor is
used to process these attributes, the following algorithm should be used to
detect and extract the values of the attributes.</p>
<p>While processing Infoset Attribute Information Items in Element Information
Items as described in [<a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a>],
<a href="http://www.w3.org/TR/rdfa-core#sequence">Section 7.5: Sequence</a>,
Step #4 through Step #9:</p>
<ol>
<li>For each Attribute Information Item specific to RDFa in the Infoset
[<a href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">attributes</a>]
list that has a [<a href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">prefix</a>] with
no value, extract and use the [<a href="http://www.w3.org/TR/xml-infoset/#infoitem.attribute">normalized
value</a>].</li>
</ol>
</div>
</div>
<div id="dom-level-2-based-processors" class="section">
<h3><span class="secno">4.5 </span>DOM Level 2-based Processors</h3>
<p class="issue">This mechanism should be double-checked against all of the
RDFa Javascript implementations to ensure correctness.</p>
<p>While the intent of the RDFa processing instructions were to provide a
set of rules that are as language and toolchain agnostic as possible, for
the sake of clarity, detailed methods of extracting RDFa content from
processors operating in a DOM2 environment are provided below.</p>
<div id="extracting-uri-mappings-from-doms" class="section">
<h4><span class="secno">4.5.1 </span>Extracting URI Mappings from DOMs</h4>
<p>Extracting URI Mappings declared via <code>xmlns:</code> while operating
from within a DOM Level 2 based RDFa processor can be achieved using the
following algorithm:</p>
<p>While processing each DOM2 [<a href="http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-745549614">Element</a>]
as described in [<a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a>],
<a href="http://www.w3.org/TR/rdfa-core#sequence">Section 7.5: Sequence</a>,
Step #2:</p>
<ol>
<li>For each [<a href="http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-745549614">Attr</a>]
in the [<a href="http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-1950641247">Node.attributes</a>]
list that has a [<a href="http://www.w3.org/TR/DOM-Level-2-Core/glossary.html#dt-namespaceprefix">namespace
prefix</a>] value of <code>xmlns</code>, create a [<a href="http://www.w3.org/TR/rdfa-core/#dfn-uri_mapping">URI mapping</a>] by
storing the [<a href="http://www.w3.org/TR/DOM-Level-2-Core/glossary.html#dt-localname">local
name</a>] as the value to be mapped, and the [<a href="http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-F68D080">Node.nodeValue</a>]
as the value to map.</li>
<li>For each [<a href="http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-745549614">Attr</a>]
in the [<a href="http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-1950641247">Node.attributes</a>]
list that has a [<a href="http://www.w3.org/TR/DOM-Level-2-Core/glossary.html#dt-namespaceprefix">namespace
prefix</a>] value of null and a [<a href="http://www.w3.org/TR/DOM-Level-2-Core/glossary.html#dt-localname">local
name</a>] that starts with <code>xmlns:</code>, create a [<a href="http://www.w3.org/TR/rdfa-core/#dfn-uri_mapping">URI mapping</a>] by
storing the [local name] part with the <code>xmlns:</code> characters
removed as the value to be mapped, and the [<a href="http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-F68D080">Node.nodeValue</a>]
as the value to map.
<p class="note">This step is unnecessary if the XML and non-XML
mode DOMs are namespace consistent.</p></li>
</ol>
<p>For example, assume that the following markup is processed by a
DOM2-based RDFa processor:</p>
<pre class="example"><div xmlns:audio="http://purl.org/media/audio#" ...</pre>
<p>After the markup is processed, there should exist a [URI mapping] in
the [local list of URI mappings] that contains a mapping from
<code>audio</code> to <code>http://purl.org/media/audio#</code>.
</p>
</div>
<div id="processing-rdfa-attributes-1" class="section">
<h4><span class="secno">4.5.2 </span>Processing RDFa Attributes</h4>
<p>There are a number of non-prefixed attributes that are associated with
RDFa processing in HTML5. If an DOM2-based RDFa processor is used to
process these attributes, the following algorithm should be used to detect
and extract the values of the attributes.</p>
<p>While processing an element as described in [<a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a>],
<a href="http://www.w3.org/TR/rdfa-core/#sequence">Section 5.5: Sequence</a>,
Step #4 through Step #9:</p>
<ol>
<li>For each RDFa attribute in the [<a href="http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-1950641247">Node.attributes</a>]
list that has a [<a href="http://www.w3.org/TR/DOM-Level-2-Core/glossary.html#dt-namespaceprefix">namespace
prefix</a>] that is null, extract and use [<a href="http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-F68D080">Node.nodeValue</a>]
as the value.</li>
</ol>
</div>
</div>
</div>
<div class="appendix section" id="html-default-vocabulary-terms">
<!--OddPage--><h2><span class="secno">A. </span>HTML Default Vocabulary Terms</h2>
<p class="issue">Note that the values defined in this section
may be removed from this document and placed in an external
'RDFa Profile' so that they can be maintained independent of the
specification.</p>
<p>The terms defined in this section <em class="rfc2119" title="must">must</em> be mapped to
lower case by an RDFa Processor. The vocabulary terms are:</p>
<dl>
<dt>alternate</dt>
<dd>Designates alternate versions for a resource.</dd>
<dt>appendix</dt>
<dd>Refers to a resource serving as an appendix in a collection.</dd>
<dt>bookmark</dt>
<dd>Refers to a bookmark. A bookmark is a link to a key entry point within an
extended document. The
<span class="aref">@title</span> attribute may be used, for example, to
label the bookmark. Note that several bookmarks may be defined for a
document.</dd>
<dt>cite</dt>
<dd>
<p>Refers to a resource that defines a citation.
In the following example, the <code>cite</code> is used to
reference the book from which the quotation is taken:</p>
<pre class="example" title="cite as book reference">As Gandalf the White said in
<span <span class="hilite">rel="cite"</span> resource="http://www.example.com/books/the_two_towers">
The Two Towers
</span>,
<quote xml:lang="en">"The hospitality of
your hall is somewhat lessened of late, Theoden King."</quote></pre>
<p>which would generate the following triples:</p>
<pre class="example"><> xhv:cite <http://www.example.com/books/the_two_towers> .</pre>
<code>cite</code> is also useful for referencing specifications:
<pre class="example" title="cite to reference another specification">More information can be found in
<span <span class="hilite">rel="cite"</span> resource="http://www.w3.org/TR/REC-xml">[XML]</cite>.</pre>
<p>which would generate the following triples:</p>
<pre class="example"><> xhv:cite <http://www.w3.org/TR/REC-xml> .</pre>
</dd>
<dt>chapter</dt>
<dd>Refers to a resource serving as a chapter in a collection.</dd>
<dt>contents</dt>
<dd>Refers to a resource serving as a table of contents.</dd>
<dt>copyright</dt>
<dd>Refers to a copyright statement for the resource.</dd>
<dt>first</dt>
<dd>Refers to the first item in a collection (see also start and top).</dd>
<dt>glossary</dt>
<dd>Refers to a resource providing a glossary of terms.</dd>
<dt>help</dt>
<dd>Refers to a resource offering help (more information, links to other sources of information, etc.)</dd>
<dt>icon</dt>
<dd>Refers to a resource that represents an icon.
</dd>
<dt>index</dt>
<dd>Refers to a resource providing an index.</dd>
<dt>last</dt>
<dd>Refers to the last resource in a collection of resources.</dd>
<dt>license</dt>
<dd>Refers to a resource that defines the license associated with a resource.</dd>
<dt>meta</dt>
<dd>Refers to a resource that provides metadata, for instance in RDF.
</dd>
<dt>next</dt>
<dd>Refers to the next resource (after the current one) in an
ordered collection.</dd>
<dt>p3pv1</dt>
<dd>Refers to a P3P Policy Reference File. See [[!P3P1.0]].</dd>
<dt>prev</dt>
<dd>Refers to the previous resource (before the current one)
in an ordered collection.</dd>
<dt>role</dt>
<dd>
Indicates the purpose of the resource. For some possible values, see
[<a class="bibref" rel="biblioentry" href="#bib-XHTML-VOCAB">XHTML-VOCAB</a>].</dd>
<dt>section</dt>
<dd>Refers to a resource serving as a section in a collection.</dd>
<dt>stylesheet</dt>
<dd>Refers to a resource acting as a stylesheet for a resource.</dd>
<dt>subsection</dt>
<dd>Refers to a resource serving as a subsection in a collection.</dd>
<dt>start</dt>
<dd>Refers to the first resource in a collection of resources. A
typical use case might be a collection of chapters in a book.
</dd>
<dt>top</dt>
<dd>Synonym for start.</dd>
<dt>up</dt>
<dd>Refers to the resource "above" in a hierarchically structured set.</dd>
</dl>
</div>
<div class="appendix section" id="validation">
<!--OddPage--><h2><span class="secno">B. </span>Validation</h2>
<p>Documents written using the markup language defined in
this specification <em class="rfc2119" title="may">may</em> be validated using the
DTD defined in this section. If a document author wants
to facilitate such validation, they <em class="rfc2119" title="may">may</em> include the following
declaration at the top of their document:</p>
<pre class="example"><!DOCTYPE html PUBLIC "-//<acronym title="World Wide Web Consortium">W3C</acronym>//DTD HTML+RDFa 1.1//EN"
"http://www.w3.org/MarkUp/DTD/html401-rdfa11-1.dtd"></pre>
<div id="the-html-4.01---rdfa-1.1-dtd" class="section">
<h3 id="html-rdfa-dtd"><span class="secno">B.1 </span>The HTML 4.01 + RDFa 1.1 DTD</h3>
<div><p>You can download this version of this file from <a href="DTD/html401-rdfa11-1.dtd">DTD/html401-rdfa11-1.dtd</a>. The latest version is available at <a href="http://www.w3.org/MarkUp/DTD/html401-rdfa11-1.dtd">http://www.w3.org/MarkUp/DTD/html401-rdfa11-1.dtd</a>.</p><pre class="dtd"><!--
This is the HTML 4.01 + RDFa 1.1 DTD, which includes
presentation attributes and elements that <acronym title="World Wide Web Consortium">W3C</acronym> expects to phase out
as support for style sheets matures. This DTD should be considered as
a Transitional doctype with respect to content, but as a Strict doctype with
respect to rendering mode.
HTML 4 includes mechanisms for style sheets, scripting,
embedding objects, improved support for right to left and mixed
direction text, and enhancements to forms for improved
accessibility for people with disabilities.
Draft: $Date: 2010/06/25 17:33:34 $
Editors:
Shane McCarron <shane@aptest.com>
Manu Sporny <msporny@digitalbazaar.com>
Original Authors:
Dave Raggett <dsr@w3.org>
Arnaud Le Hors <lehors@w3.org>
Ian Jacobs <ij@w3.org>
Further information about RDFa is available at:
http://www.w3.org/TR/rdfa-core
Further information about HTML 4.01 is available at:
http://www.w3.org/TR/1999/REC-html401-19991224
Further information about HTML+RDFa is available at:
http://www.w3.org/TR/rdfa-in-html
The HTML 4.01 specification includes additional
syntactic constraints that cannot be expressed within
the DTDs.
-->
<!ENTITY <span class="entity">% HTML.Version</span> "-//<acronym title="World Wide Web Consortium">W3C</acronym>//DTD HTML 4.01+RDFa 1.1//EN"
-- Typical usage:
<!DOCTYPE HTML PUBLIC "-//<acronym title="World Wide Web Consortium">W3C</acronym>//DTD HTML 4.01+RDFa 1.1//EN"
"http://www.w3.org/MarkUp/DTD/html401-rdfa11-1.dtd">
<html>
<head>
...
</head>
<body>
...
</body>
</html>
The URI used as a system identifier with the public identifier allows
the user agent to download the DTD and entity sets as needed.
-->
<!--================== Imported Names ====================================-->
<!-- Feature Switch for frameset documents -->
<!ENTITY <span class="entity">% HTML.Frameset</span> "IGNORE">
<!ENTITY <span class="entity">% ContentType</span> "CDATA"
-- media type, as per [RFC2045]
-->
<!ENTITY <span class="entity">% ContentTypes</span> "CDATA"
-- comma-separated list of media types, as per [RFC2045]
-->
<!ENTITY <span class="entity">% Charset</span> "CDATA"
-- a character encoding, as per [RFC2045]
-->
<!ENTITY <span class="entity">% Charsets</span> "CDATA"
-- a space-separated list of character encodings, as per [RFC2045]
-->
<!ENTITY <span class="entity">% LanguageCode</span> "NAME"
-- a language code, as per [RFC1766]
-->
<!ENTITY <span class="entity">% Character</span> "CDATA"
-- a single character from [ISO10646]
-->
<!ENTITY <span class="entity">% LinkTypes</span> "CDATA"
-- space-separated list of link types
-->
<!ENTITY <span class="entity">% MediaDesc</span> "CDATA"
-- single or comma-separated list of media descriptors
-->
<!ENTITY <span class="entity">% URI</span> "CDATA"
-- a Uniform Resource Identifier,
see [URI]
-->
<!ENTITY <span class="entity">% Datetime</span> "CDATA" -- date and time information. ISO date format -->
<!ENTITY <span class="entity">% Script</span> "CDATA" -- script expression -->
<!ENTITY <span class="entity">% StyleSheet</span> "CDATA" -- style sheet data -->
<!ENTITY <span class="entity">% FrameTarget</span> "CDATA" -- render in this frame -->
<!ENTITY <span class="entity">% Text</span> "CDATA">
<!-- Parameter Entities -->
<!ENTITY <span class="entity">% head.misc</span> "SCRIPT|STYLE|META|LINK|OBJECT" -- repeatable head elements -->
<!ENTITY <span class="entity">% heading</span> "H1|H2|H3|H4|H5|H6">
<!ENTITY <span class="entity">% list</span> "UL | OL | DIR | MENU">
<!ENTITY <span class="entity">% preformatted</span> "PRE">
<!ENTITY <span class="entity">% Color</span> "CDATA" -- a color using sRGB: #RRGGBB as Hex values -->
<!-- There are also 16 widely known color names with their sRGB values:
Black = #000000 Green = #008000
Silver = #C0C0C0 Lime = #00FF00
Gray = #808080 Olive = #808000
White = #FFFFFF Yellow = #FFFF00
Maroon = #800000 Navy = #000080
Red = #FF0000 Blue = #0000FF
Purple = #800080 Teal = #008080
Fuchsia= #FF00FF Aqua = #00FFFF
-->
<!ENTITY <span class="entity">% bodycolors</span> "
bgcolor %Color; #IMPLIED -- document background color --
text %Color; #IMPLIED -- document text color --
link %Color; #IMPLIED -- color of links --
vlink %Color; #IMPLIED -- color of visited links --
alink %Color; #IMPLIED -- color of selected links --
">
<!--================ Character mnemonic entities =========================-->
<!ENTITY <span class="entity">% HTMLlat1</span> PUBLIC
"-//<acronym title="World Wide Web Consortium">W3C</acronym>//ENTITIES Latin1//EN//HTML"
"http://www.w3.org/TR/html401/HTMLlat1.ent">
%HTMLlat1;
<!ENTITY <span class="entity">% HTMLsymbol</span> PUBLIC
"-//<acronym title="World Wide Web Consortium">W3C</acronym>//ENTITIES Symbols//EN//HTML"
"http://www.w3.org/TR/html401/HTMLsymbol.ent">
%HTMLsymbol;
<!ENTITY <span class="entity">% HTMLspecial</span> PUBLIC
"-//<acronym title="World Wide Web Consortium">W3C</acronym>//ENTITIES Special//EN//HTML"
"http://www.w3.org/TR/html401/HTMLspecial.ent">
%HTMLspecial;
<!--=================== Generic Attributes ===============================-->
<!ENTITY <span class="entity">% coreattrs</span>
"id ID #IMPLIED -- document-wide unique id --
class CDATA #IMPLIED -- space-separated list of classes --
style %StyleSheet; #IMPLIED -- associated style info --
title %Text; #IMPLIED -- advisory title --
>
<!ENTITY <span class="entity">% i18n</span>
"lang %LanguageCode; #IMPLIED -- language code --
dir (ltr|rtl) #IMPLIED -- direction for weak/neutral text --"
>
<!ENTITY <span class="entity">% events</span>
"onclick %Script; #IMPLIED -- a pointer button was clicked --
ondblclick %Script; #IMPLIED -- a pointer button was double clicked--
onmousedown %Script; #IMPLIED -- a pointer button was pressed down --
onmouseup %Script; #IMPLIED -- a pointer button was released --
onmouseover %Script; #IMPLIED -- a pointer was moved onto --
onmousemove %Script; #IMPLIED -- a pointer was moved within --
onmouseout %Script; #IMPLIED -- a pointer was moved away --
onkeypress %Script; #IMPLIED -- a key was pressed and released --
onkeydown %Script; #IMPLIED -- a key was pressed down --
onkeyup %Script; #IMPLIED -- a key was released --"
>
<!ENTITY <span class="entity">% TERMorURIorCURIE</span> "CDATA" >
<!ENTITY <span class="entity">% TERMorURIorCURIEs</span> "CDATA" >
<!ENTITY <span class="entity">% URIorCURIE</span> "CDATA" >
<!ENTITY <span class="entity">% URIs</span> "CDATA" >
<!ENTITY <span class="entity">% metainformation</span>
"about %URIorCURIE; #IMPLIED -- RDFa - specifies subject --
content CDATA #IMPLIED -- RDFa - specifies object override --
datatype %TERMorURIorCURIE; #IMPLIED -- RDFa - specifies object datatype --
typeof %TERMorURIorCURIEs; #IMPLIED -- RDFa - bnode or rdf:type triple --
prefix CDATA #IMPLIED -- RDFa - specifies prefix mappings --
profile %URIs; #IMPLIED -- RDFa - specifies term document --
property %TERMorURIorCURIEs; #IMPLIED -- RDFa - specifies predicate --
rel %TERMorURIorCURIEs; #IMPLIED -- relationship for linked resource --
rev %TERMorURIorCURIEs; #IMPLIED -- reverse relationship for linked resource --
href %URI; #IMPLIED -- URI for linked resource --
resource %URIorCURIE; #IMPLIED -- RDFa - like href, but overrides it --
vocab %URI; #IMPLIED -- RDFa - specifies default vocabulary"
>
<!-- Reserved Feature Switch -->
<!ENTITY <span class="entity">% HTML.Reserved</span> "IGNORE">
<!-- The following attributes are reserved for possible future use -->
<![ %HTML.Reserved; [
<!ENTITY <span class="entity">% reserved</span>
"datasrc %URI; #IMPLIED -- a single or tabular Data Source --
datafld CDATA #IMPLIED -- the property or column name --
dataformatas (plaintext|html) plaintext -- text or html --"
>
]]>
<!ENTITY <span class="entity">% reserved</span> "">
<!ENTITY <span class="entity">% attrs</span> "%coreattrs; %i18n; %events; %metainformation;">
<!ENTITY <span class="entity">% align</span> "align (left|center|right|justify) #IMPLIED"
-- default is left for ltr paragraphs, right for rtl --
>
<!--=================== Text Markup ======================================-->
<!ENTITY <span class="entity">% fontstyle</span>
"TT | I | B | U | S | STRIKE | BIG | SMALL">
<!ENTITY <span class="entity">% phrase</span> "EM | STRONG | DFN | CODE |
SAMP | KBD | VAR | CITE | ABBR | ACRONYM" >
<!ENTITY <span class="entity">% special</span>
"A | IMG | APPLET | OBJECT | FONT | BASEFONT | BR | SCRIPT |
MAP | Q | SUB | SUP | SPAN | BDO | IFRAME">
<!ENTITY <span class="entity">% formctrl</span> "INPUT | SELECT | TEXTAREA | LABEL | BUTTON">
<!-- %inline; covers inline or "text-level" elements -->
<!ENTITY <span class="entity">% inline</span> "#PCDATA | %fontstyle; | %phrase; | %special; | %formctrl; ">
<!ELEMENT <span class="element">(%fontstyle;|%phrase;)</span> - - (%inline;)*>
<!ATTLIST (%fontstyle;|%phrase;)
%attrs; -- %coreattrs, %i18n, %events --
>
<!ELEMENT <span class="element">(SUB|SUP)</span> - - (%inline;)* -- subscript, superscript -->
<!ATTLIST (SUB|SUP)
%attrs; -- %coreattrs, %i18n, %events --
>
<!ELEMENT <span class="element">SPAN</span> - - (%inline;)* -- generic language/style container -->
<!ATTLIST SPAN
%attrs; -- %coreattrs, %i18n, %events --
%reserved; -- reserved for possible future use --
>
<!ELEMENT <span class="element">BDO</span> - - (%inline;)* -- I18N BiDi over-ride -->
<!ATTLIST BDO
%coreattrs; -- id, class, style, title --
lang %LanguageCode; #IMPLIED -- language code --
dir (ltr|rtl) #<em class="rfc2119" title="required">required</em> -- directionality --
>
<!ELEMENT <span class="element">BASEFONT</span> - O EMPTY -- base font size -->
<!ATTLIST BASEFONT
id ID #IMPLIED -- document-wide unique id --
size CDATA #<em class="rfc2119" title="required">required</em> -- base font size for FONT elements --
color %Color; #IMPLIED -- text color --
face CDATA #IMPLIED -- comma-separated list of font names --
>
<!ELEMENT <span class="element">FONT</span> - - (%inline;)* -- local change to font -->
<!ATTLIST FONT
%coreattrs; -- id, class, style, title --
%i18n; -- lang, dir --
size CDATA #IMPLIED -- [+|-]nn e.g. size="+1", size="4" --
color %Color; #IMPLIED -- text color --
face CDATA #IMPLIED -- comma-separated list of font names --
>
<!ELEMENT <span class="element">BR</span> - O EMPTY -- forced line break -->
<!ATTLIST BR
%coreattrs; -- id, class, style, title --
clear (left|all|right|none) none -- control of text flow --
>
<!--================== HTML content models ===============================-->
<!--
HTML has two basic content models:
%inline; character level elements and text strings
%block; block-like elements e.g. paragraphs and lists
-->
<!ENTITY <span class="entity">% block</span>
"P | %heading; | %list; | %preformatted; | DL | DIV | CENTER |
NOSCRIPT | NOFRAMES | BLOCKQUOTE | FORM | ISINDEX | HR |
TABLE | FIELDSET | ADDRESS">
<!ENTITY <span class="entity">% flow</span> "%block; | %inline;">
<!--=================== Document Body ====================================-->
<!ELEMENT <span class="element">BODY</span> O O (%flow;)* +(INS|DEL) -- document body -->
<!ATTLIST BODY
%attrs; -- %coreattrs, %i18n, %events --
onload %Script; #IMPLIED -- the document has been loaded --
onunload %Script; #IMPLIED -- the document has been removed --
background %URI; #IMPLIED -- texture tile for document
background --
%bodycolors; -- bgcolor, text, link, vlink, alink --
>
<!ELEMENT <span class="element">ADDRESS</span> - - ((%inline;)|P)* -- information on author -->
<!ATTLIST ADDRESS
%attrs; -- %coreattrs, %i18n, %events --
>
<!ELEMENT <span class="element">DIV</span> - - (%flow;)* -- generic language/style container -->
<!ATTLIST DIV
%attrs; -- %coreattrs, %i18n, %events --
%align; -- align, text alignment --
%reserved; -- reserved for possible future use --
>
<!ELEMENT <span class="element">CENTER</span> - - (%flow;)* -- shorthand for DIV align=center -->
<!ATTLIST CENTER
%attrs; -- %coreattrs, %i18n, %events --
>
<!--================== The Anchor Element ================================-->
<!ENTITY <span class="entity">% Shape</span> "(rect|circle|poly|default)">
<!ENTITY <span class="entity">% Coords</span> "CDATA" -- comma-separated list of lengths -->
<!ELEMENT <span class="element">A</span> - - (%inline;)* -(A) -- anchor -->
<!ATTLIST A
%attrs; -- %coreattrs, %i18n, %events --
charset %Charset; #IMPLIED -- char encoding of linked resource --
type %ContentType; #IMPLIED -- advisory content type --
name CDATA #IMPLIED -- named link end --
hreflang %LanguageCode; #IMPLIED -- language code --
target %FrameTarget; #IMPLIED -- render in this frame --
accesskey %Character; #IMPLIED -- accessibility key character --
shape %Shape; rect -- for use with client-side image maps --
coords %Coords; #IMPLIED -- for use with client-side image maps --
tabindex NUMBER #IMPLIED -- position in tabbing order --
onfocus %Script; #IMPLIED -- the element got the focus --
onblur %Script; #IMPLIED -- the element lost the focus --
>
<!--================== Client-side image maps ============================-->
<!-- These can be placed in the same document or grouped in a
separate document although this isn't yet widely supported -->
<!ELEMENT <span class="element">MAP</span> - - ((%block;) | AREA)+ -- client-side image map -->
<!ATTLIST MAP
%attrs; -- %coreattrs, %i18n, %events --
name CDATA #<em class="rfc2119" title="required">required</em> -- for reference by usemap --
>
<!ELEMENT <span class="element">AREA</span> - O EMPTY -- client-side image map area -->
<!ATTLIST AREA
%attrs; -- %coreattrs, %i18n, %events --
shape %Shape; rect -- controls interpretation of coords --
coords %Coords; #IMPLIED -- comma-separated list of lengths --
target %FrameTarget; #IMPLIED -- render in this frame --
nohref (nohref) #IMPLIED -- this region has no action --
alt %Text; #<em class="rfc2119" title="required">required</em> -- short description --
tabindex NUMBER #IMPLIED -- position in tabbing order --
accesskey %Character; #IMPLIED -- accessibility key character --
onfocus %Script; #IMPLIED -- the element got the focus --
onblur %Script; #IMPLIED -- the element lost the focus --
>
<!--================== The LINK Element ==================================-->
<!--
Relationship values can be used in principle:
a) for document specific toolbars/menus when used
with the LINK element in document head e.g.
start, contents, previous, next, index, end, help
b) to link to a separate style sheet (rel=stylesheet)
c) to make a link to a script (rel=script)
d) by stylesheets to control how collections of
html nodes are rendered into printed documents
e) to make a link to a printable version of this document
e.g. a postscript or pdf version (rel=alternate media=print)
-->
<!ELEMENT <span class="element">LINK</span> - O EMPTY -- a media-independent link -->
<!ATTLIST LINK
%attrs; -- %coreattrs, %i18n, %events --
charset %Charset; #IMPLIED -- char encoding of linked resource --
hreflang %LanguageCode; #IMPLIED -- language code --
type %ContentType; #IMPLIED -- advisory content type --
media %MediaDesc; #IMPLIED -- for rendering on these media --
target %FrameTarget; #IMPLIED -- render in this frame --
>
<!--=================== Images ===========================================-->
<!-- Length defined in strict DTD for cellpadding/cellspacing -->
<!ENTITY <span class="entity">% Length</span> "CDATA" -- nn for pixels or nn% for percentage length -->
<!ENTITY <span class="entity">% MultiLength</span> "CDATA" -- pixel, percentage, or relative -->
<![ %HTML.Frameset; [
<!ENTITY <span class="entity">% MultiLengths</span> "CDATA" -- comma-separated list of MultiLength -->
]]>
<!ENTITY <span class="entity">% Pixels</span> "CDATA" -- integer representing length in pixels -->
<!ENTITY <span class="entity">% IAlign</span> "(top|middle|bottom|left|right)" -- center? -->
<!-- To avoid problems with text-only UAs as well as
to make image content understandable and navigable
to users of non-visual UAs, you need to provide
a description with ALT, and avoid server-side image maps -->
<!ELEMENT <span class="element">IMG</span> - O EMPTY -- Embedded image -->
<!ATTLIST IMG
%attrs; -- %coreattrs, %i18n, %events --
src %URI; #<em class="rfc2119" title="required">required</em> -- URI of image to embed --
alt %Text; #<em class="rfc2119" title="required">required</em> -- short description --
longdesc %URI; #IMPLIED -- link to long description
(complements alt) --
name CDATA #IMPLIED -- name of image for scripting --
height %Length; #IMPLIED -- override height --
width %Length; #IMPLIED -- override width --
usemap %URI; #IMPLIED -- use client-side image map --
ismap (ismap) #IMPLIED -- use server-side image map --
align %IAlign; #IMPLIED -- vertical or horizontal alignment --
border %Pixels; #IMPLIED -- link border width --
hspace %Pixels; #IMPLIED -- horizontal gutter --
vspace %Pixels; #IMPLIED -- vertical gutter --
>
<!-- USEMAP points to a MAP element which may be in this document
or an external document, although the latter is not widely supported -->
<!--==================== OBJECT ======================================-->
<!--
OBJECT is used to embed objects as part of HTML pages
PARAM elements should precede other content. SGML mixed content
model technicality precludes specifying this formally ...
-->
<!ELEMENT <span class="element">OBJECT</span> - - (PARAM | %flow;)*
-- generic embedded object -->
<!ATTLIST OBJECT
%attrs; -- %coreattrs, %i18n, %events --
declare (declare) #IMPLIED -- declare but don't instantiate flag --
classid %URI; #IMPLIED -- identifies an implementation --
codebase %URI; #IMPLIED -- base URI for classid, data, archive--
data %URI; #IMPLIED -- reference to object's data --
type %ContentType; #IMPLIED -- content type for data --
codetype %ContentType; #IMPLIED -- content type for code --
archive CDATA #IMPLIED -- space-separated list of URIs --
standby %Text; #IMPLIED -- message to show while loading --
height %Length; #IMPLIED -- override height --
width %Length; #IMPLIED -- override width --
usemap %URI; #IMPLIED -- use client-side image map --
name CDATA #IMPLIED -- submit as part of form --
tabindex NUMBER #IMPLIED -- position in tabbing order --
align %IAlign; #IMPLIED -- vertical or horizontal alignment --
border %Pixels; #IMPLIED -- link border width --
hspace %Pixels; #IMPLIED -- horizontal gutter --
vspace %Pixels; #IMPLIED -- vertical gutter --
%reserved; -- reserved for possible future use --
>
<!ELEMENT <span class="element">PARAM</span> - O EMPTY -- named property value -->
<!ATTLIST PARAM
id ID #IMPLIED -- document-wide unique id --
%metainformation; -- metadata attributes --
name CDATA #<em class="rfc2119" title="required">required</em> -- property name --
value CDATA #IMPLIED -- property value --
valuetype (DATA|REF|OBJECT) DATA -- How to interpret value --
type %ContentType; #IMPLIED -- content type for value
when valuetype=ref --
>
<!--=================== Java APPLET ==================================-->
<!--
One of code or object attributes must be present.
Place PARAM elements before other content.
-->
<!ELEMENT <span class="element">APPLET</span> - - (PARAM | %flow;)* -- Java applet -->
<!ATTLIST APPLET
%coreattrs; -- id, class, style, title --
%metainformation; -- metadata attributes --
codebase %URI; #IMPLIED -- optional base URI for applet --
archive CDATA #IMPLIED -- comma-separated archive list --
code CDATA #IMPLIED -- applet class file --
object CDATA #IMPLIED -- serialized applet file --
alt %Text; #IMPLIED -- short description --
name CDATA #IMPLIED -- allows applets to find each other --
width %Length; #<em class="rfc2119" title="required">required</em> -- initial width --
height %Length; #<em class="rfc2119" title="required">required</em> -- initial height --
align %IAlign; #IMPLIED -- vertical or horizontal alignment --
hspace %Pixels; #IMPLIED -- horizontal gutter --
vspace %Pixels; #IMPLIED -- vertical gutter --
>
<!--=================== Horizontal Rule ==================================-->
<!ELEMENT <span class="element">HR</span> - O EMPTY -- horizontal rule -->
<!ATTLIST HR
%attrs; -- %coreattrs, %i18n, %events --
align (left|center|right) #IMPLIED
noshade (noshade) #IMPLIED
size %Pixels; #IMPLIED
width %Length; #IMPLIED
>
<!--=================== Paragraphs =======================================-->
<!ELEMENT <span class="element">P</span> - O (%inline;)* -- paragraph -->
<!ATTLIST P
%attrs; -- %coreattrs, %i18n, %events --
%align; -- align, text alignment --
>
<!--=================== Headings =========================================-->
<!--
There are six levels of headings from H1 (the most important)
to H6 (the least important).
-->
<!ELEMENT <span class="element">(%heading;)</span> - - (%inline;)* -- heading -->
<!ATTLIST (%heading;)
%attrs; -- %coreattrs, %i18n, %events --
%align; -- align, text alignment --
>
<!--=================== Preformatted Text ================================-->
<!-- excludes markup for images and changes in font size -->
<!ENTITY <span class="entity">% pre.exclusion</span> "IMG|OBJECT|APPLET|BIG|SMALL|SUB|SUP|FONT|BASEFONT">
<!ELEMENT <span class="element">PRE</span> - - (%inline;)* -(%pre.exclusion;) -- preformatted text -->
<!ATTLIST PRE
%attrs; -- %coreattrs, %i18n, %events --
width NUMBER #IMPLIED
>
<!--===================== Inline Quotes ==================================-->
<!ELEMENT <span class="element">Q</span> - - (%inline;)* -- short inline quotation -->
<!ATTLIST Q
%attrs; -- %coreattrs, %i18n, %events --
cite %URI; #IMPLIED -- URI for source document or msg --
>
<!--=================== Block-like Quotes ================================-->
<!ELEMENT <span class="element">BLOCKQUOTE</span> - - (%flow;)* -- long quotation -->
<!ATTLIST BLOCKQUOTE
%attrs; -- %coreattrs, %i18n, %events --
cite %URI; #IMPLIED -- URI for source document or msg --
>
<!--=================== Inserted/Deleted Text ============================-->
<!-- INS/DEL are handled by inclusion on BODY -->
<!ELEMENT <span class="element">(INS|DEL)</span> - - (%flow;)* -- inserted text, deleted text -->
<!ATTLIST (INS|DEL)
%attrs; -- %coreattrs, %i18n, %events --
cite %URI; #IMPLIED -- info on reason for change --
datetime %Datetime; #IMPLIED -- date and time of change --
>
<!--=================== Lists ============================================-->
<!-- definition lists - DT for term, DD for its definition -->
<!ELEMENT <span class="element">DL</span> - - (DT|DD)+ -- definition list -->
<!ATTLIST DL
%attrs; -- %coreattrs, %i18n, %events --
compact (compact) #IMPLIED -- reduced interitem spacing --
>
<!ELEMENT <span class="element">DT</span> - O (%inline;)* -- definition term -->
<!ELEMENT <span class="element">DD</span> - O (%flow;)* -- definition description -->
<!ATTLIST (DT|DD)
%attrs; -- %coreattrs, %i18n, %events --
>
<!-- Ordered lists (OL) Numbering style
1 arablic numbers 1, 2, 3, ...
a lower alpha a, b, c, ...
A upper alpha A, B, C, ...
i lower roman i, ii, iii, ...
I upper roman I, II, III, ...
The style is applied to the sequence number which by default
is reset to 1 for the first list item in an ordered list.
This can't be expressed directly in SGML due to case folding.
-->
<!ENTITY <span class="entity">% OLStyle</span> "CDATA" -- constrained to: "(1|a|A|i|I)" -->
<!ELEMENT <span class="element">OL</span> - - (LI)+ -- ordered list -->
<!ATTLIST OL
%attrs; -- %coreattrs, %i18n, %events --
type %OLStyle; #IMPLIED -- numbering style --
compact (compact) #IMPLIED -- reduced interitem spacing --
start NUMBER #IMPLIED -- starting sequence number --
>
<!-- Unordered Lists (UL) bullet styles -->
<!ENTITY <span class="entity">% ULStyle</span> "(disc|square|circle)">
<!ELEMENT <span class="element">UL</span> - - (LI)+ -- unordered list -->
<!ATTLIST UL
%attrs; -- %coreattrs, %i18n, %events --
type %ULStyle; #IMPLIED -- bullet style --
compact (compact) #IMPLIED -- reduced interitem spacing --
>
<!ELEMENT <span class="element">(DIR|MENU)</span> - - (LI)+ -(%block;) -- directory list, menu list -->
<!ATTLIST DIR
%attrs; -- %coreattrs, %i18n, %events --
compact (compact) #IMPLIED -- reduced interitem spacing --
>
<!ATTLIST MENU
%attrs; -- %coreattrs, %i18n, %events --
compact (compact) #IMPLIED -- reduced interitem spacing --
>
<!ENTITY <span class="entity">% LIStyle</span> "CDATA" -- constrained to: "(%ULStyle;|%OLStyle;)" -->
<!ELEMENT <span class="element">LI</span> - O (%flow;)* -- list item -->
<!ATTLIST LI
%attrs; -- %coreattrs, %i18n, %events --
type %LIStyle; #IMPLIED -- list item style --
value NUMBER #IMPLIED -- reset sequence number --
>
<!--================ Forms ===============================================-->
<!ELEMENT <span class="element">FORM</span> - - (%flow;)* -(FORM) -- interactive form -->
<!ATTLIST FORM
%attrs; -- %coreattrs, %i18n, %events --
action %URI; #<em class="rfc2119" title="required">required</em> -- server-side form handler --
method (GET|POST) GET -- HTTP method used to submit the form--
enctype %ContentType; "application/x-www-form-urlencoded"
accept %ContentTypes; #IMPLIED -- list of MIME types for file upload --
name CDATA #IMPLIED -- name of form for scripting --
onsubmit %Script; #IMPLIED -- the form was submitted --
onreset %Script; #IMPLIED -- the form was reset --
target %FrameTarget; #IMPLIED -- render in this frame --
accept-charset %Charsets; #IMPLIED -- list of supported charsets --
>
<!-- Each label must not contain more than ONE field -->
<!ELEMENT <span class="element">LABEL</span> - - (%inline;)* -(LABEL) -- form field label text -->
<!ATTLIST LABEL
%attrs; -- %coreattrs, %i18n, %events --
for IDREF #IMPLIED -- matches field ID value --
accesskey %Character; #IMPLIED -- accessibility key character --
onfocus %Script; #IMPLIED -- the element got the focus --
onblur %Script; #IMPLIED -- the element lost the focus --
>
<!ENTITY <span class="entity">% InputType</span>
"(TEXT | PASSWORD | CHECKBOX |
RADIO | SUBMIT | RESET |
FILE | HIDDEN | IMAGE | BUTTON)"
>
<!-- attribute name required for all but submit and reset -->
<!ELEMENT <span class="element">INPUT</span> - O EMPTY -- form control -->
<!ATTLIST INPUT
%attrs; -- %coreattrs, %i18n, %events --
type %InputType; TEXT -- what kind of widget is needed --
name CDATA #IMPLIED -- submit as part of form --
value CDATA #IMPLIED -- Specify for radio buttons and checkboxes --
checked (checked) #IMPLIED -- for radio buttons and check boxes --
disabled (disabled) #IMPLIED -- unavailable in this context --
readonly (readonly) #IMPLIED -- for text and passwd --
size CDATA #IMPLIED -- specific to each type of field --
maxlength NUMBER #IMPLIED -- max chars for text fields --
src %URI; #IMPLIED -- for fields with images --
alt CDATA #IMPLIED -- short description --
usemap %URI; #IMPLIED -- use client-side image map --
ismap (ismap) #IMPLIED -- use server-side image map --
tabindex NUMBER #IMPLIED -- position in tabbing order --
accesskey %Character; #IMPLIED -- accessibility key character --
onfocus %Script; #IMPLIED -- the element got the focus --
onblur %Script; #IMPLIED -- the element lost the focus --
onselect %Script; #IMPLIED -- some text was selected --
onchange %Script; #IMPLIED -- the element value was changed --
accept %ContentTypes; #IMPLIED -- list of MIME types for file upload --
align %IAlign; #IMPLIED -- vertical or horizontal alignment --
%reserved; -- reserved for possible future use --
>
<!ELEMENT <span class="element">SELECT</span> - - (OPTGROUP|OPTION)+ -- option selector -->
<!ATTLIST SELECT
%attrs; -- %coreattrs, %i18n, %events --
name CDATA #IMPLIED -- field name --
size NUMBER #IMPLIED -- rows visible --
multiple (multiple) #IMPLIED -- default is single selection --
disabled (disabled) #IMPLIED -- unavailable in this context --
tabindex NUMBER #IMPLIED -- position in tabbing order --
onfocus %Script; #IMPLIED -- the element got the focus --
onblur %Script; #IMPLIED -- the element lost the focus --
onchange %Script; #IMPLIED -- the element value was changed --
%reserved; -- reserved for possible future use --
>
<!ELEMENT <span class="element">OPTGROUP</span> - - (OPTION)+ -- option group -->
<!ATTLIST OPTGROUP
%attrs; -- %coreattrs, %i18n, %events --
disabled (disabled) #IMPLIED -- unavailable in this context --
label %Text; #<em class="rfc2119" title="required">required</em> -- for use in hierarchical menus --
>
<!ELEMENT <span class="element">OPTION</span> - O (#PCDATA) -- selectable choice -->
<!ATTLIST OPTION
%attrs; -- %coreattrs, %i18n, %events --
selected (selected) #IMPLIED
disabled (disabled) #IMPLIED -- unavailable in this context --
label %Text; #IMPLIED -- for use in hierarchical menus --
value CDATA #IMPLIED -- defaults to element content --
>
<!ELEMENT <span class="element">TEXTAREA</span> - - (#PCDATA) -- multi-line text field -->
<!ATTLIST TEXTAREA
%attrs; -- %coreattrs, %i18n, %events --
name CDATA #IMPLIED
rows NUMBER #<em class="rfc2119" title="required">required</em>
cols NUMBER #<em class="rfc2119" title="required">required</em>
disabled (disabled) #IMPLIED -- unavailable in this context --
readonly (readonly) #IMPLIED
tabindex NUMBER #IMPLIED -- position in tabbing order --
accesskey %Character; #IMPLIED -- accessibility key character --
onfocus %Script; #IMPLIED -- the element got the focus --
onblur %Script; #IMPLIED -- the element lost the focus --
onselect %Script; #IMPLIED -- some text was selected --
onchange %Script; #IMPLIED -- the element value was changed --
%reserved; -- reserved for possible future use --
>
<!--
#PCDATA is to solve the mixed content problem,
per specification only whitespace is allowed there!
-->
<!ELEMENT <span class="element">FIELDSET</span> - - (#PCDATA,LEGEND,(%flow;)*) -- form control group -->
<!ATTLIST FIELDSET
%attrs; -- %coreattrs, %i18n, %events --
>
<!ELEMENT <span class="element">LEGEND</span> - - (%inline;)* -- fieldset legend -->
<!ENTITY <span class="entity">% LAlign</span> "(top|bottom|left|right)">
<!ATTLIST LEGEND
%attrs; -- %coreattrs, %i18n, %events --
accesskey %Character; #IMPLIED -- accessibility key character --
align %LAlign; #IMPLIED -- relative to fieldset --
>
<!ELEMENT <span class="element">BUTTON</span> - -
(%flow;)* -(A|%formctrl;|FORM|ISINDEX|FIELDSET|IFRAME)
-- push button -->
<!ATTLIST BUTTON
%attrs; -- %coreattrs, %i18n, %events --
name CDATA #IMPLIED
value CDATA #IMPLIED -- sent to server when submitted --
type (button|submit|reset) submit -- for use as form button --
disabled (disabled) #IMPLIED -- unavailable in this context --
tabindex NUMBER #IMPLIED -- position in tabbing order --
accesskey %Character; #IMPLIED -- accessibility key character --
onfocus %Script; #IMPLIED -- the element got the focus --
onblur %Script; #IMPLIED -- the element lost the focus --
%reserved; -- reserved for possible future use --
>
<!--======================= Tables =======================================-->
<!-- IETF HTML table standard, see [RFC1942] -->
<!--
The BORDER attribute sets the thickness of the frame around the
table. The default units are screen pixels.
The FRAME attribute specifies which parts of the frame around
the table should be rendered. The values are not the same as
CALS to avoid a name clash with the VALIGN attribute.
The value "border" is included for backwards compatibility with
<TABLE BORDER> which yields frame=border and border=implied
For <TABLE BORDER=1> you get border=1 and frame=implied. In this
case, it is appropriate to treat this as frame=border for backwards
compatibility with deployed browsers.
-->
<!ENTITY <span class="entity">% TFrame</span> "(void|above|below|hsides|lhs|rhs|vsides|box|border)">
<!--
The RULES attribute defines which rules to draw between cells:
If RULES is absent then assume:
"none" if BORDER is absent or BORDER=0 otherwise "all"
-->
<!ENTITY <span class="entity">% TRules</span> "(none | groups | rows | cols | all)">
<!-- horizontal placement of table relative to document -->
<!ENTITY <span class="entity">% TAlign</span> "(left|center|right)">
<!-- horizontal alignment attributes for cell contents -->
<!ENTITY <span class="entity">% cellhalign</span>
"align (left|center|right|justify|char) #IMPLIED
char %Character; #IMPLIED -- alignment char, e.g. char=':' --
charoff %Length; #IMPLIED -- offset for alignment char --"
>
<!-- vertical alignment attributes for cell contents -->
<!ENTITY <span class="entity">% cellvalign</span>
"valign (top|middle|bottom|baseline) #IMPLIED"
>
<!ELEMENT <span class="element">TABLE</span> - -
(CAPTION?, (COL*|COLGROUP*), THEAD?, TFOOT?, TBODY+)>
<!ELEMENT <span class="element">CAPTION</span> - - (%inline;)* -- table caption -->
<!ELEMENT <span class="element">THEAD</span> - O (TR)+ -- table header -->
<!ELEMENT <span class="element">TFOOT</span> - O (TR)+ -- table footer -->
<!ELEMENT <span class="element">TBODY</span> O O (TR)+ -- table body -->
<!ELEMENT <span class="element">COLGROUP</span> - O (COL)* -- table column group -->
<!ELEMENT <span class="element">COL</span> - O EMPTY -- table column -->
<!ELEMENT <span class="element">TR</span> - O (TH|TD)+ -- table row -->
<!ELEMENT <span class="element">(TH|TD)</span> - O (%flow;)* -- table header cell, table data cell-->
<!ATTLIST TABLE -- table element --
%attrs; -- %coreattrs, %i18n, %events --
summary %Text; #IMPLIED -- purpose/structure for speech output--
width %Length; #IMPLIED -- table width --
border %Pixels; #IMPLIED -- controls frame width around table --
frame %TFrame; #IMPLIED -- which parts of frame to render --
rules %TRules; #IMPLIED -- rulings between rows and cols --
cellspacing %Length; #IMPLIED -- spacing between cells --
cellpadding %Length; #IMPLIED -- spacing within cells --
align %TAlign; #IMPLIED -- table position relative to window --
bgcolor %Color; #IMPLIED -- background color for cells --
%reserved; -- reserved for possible future use --
datapagesize CDATA #IMPLIED -- reserved for possible future use --
>
<!ENTITY <span class="entity">% CAlign</span> "(top|bottom|left|right)">
<!ATTLIST CAPTION
%attrs; -- %coreattrs, %i18n, %events --
align %CAlign; #IMPLIED -- relative to table --
>
<!--
COLGROUP groups a set of COL elements. It allows you to group
several semantically related columns together.
-->
<!ATTLIST COLGROUP
%attrs; -- %coreattrs, %i18n, %events --
span NUMBER 1 -- default number of columns in group --
width %MultiLength; #IMPLIED -- default width for enclosed COLs --
%cellhalign; -- horizontal alignment in cells --
%cellvalign; -- vertical alignment in cells --
>
<!--
COL elements define the alignment properties for cells in
one or more columns.
The WIDTH attribute specifies the width of the columns, e.g.
width=64 width in screen pixels
width=0.5* relative width of 0.5
The SPAN attribute causes the attributes of one
COL element to apply to more than one column.
-->
<!ATTLIST COL -- column groups and properties --
%attrs; -- %coreattrs, %i18n, %events --
span NUMBER 1 -- COL attributes affect N columns --
width %MultiLength; #IMPLIED -- column width specification --
%cellhalign; -- horizontal alignment in cells --
%cellvalign; -- vertical alignment in cells --
>
<!--
Use THEAD to duplicate headers when breaking table
across page boundaries, or for static headers when
TBODY sections are rendered in scrolling panel.
Use TFOOT to duplicate footers when breaking table
across page boundaries, or for static footers when
TBODY sections are rendered in scrolling panel.
Use multiple TBODY sections when rules are needed
between groups of table rows.
-->
<!ATTLIST (THEAD|TBODY|TFOOT) -- table section --
%attrs; -- %coreattrs, %i18n, %events --
%cellhalign; -- horizontal alignment in cells --
%cellvalign; -- vertical alignment in cells --
>
<!ATTLIST TR -- table row --
%attrs; -- %coreattrs, %i18n, %events --
%cellhalign; -- horizontal alignment in cells --
%cellvalign; -- vertical alignment in cells --
bgcolor %Color; #IMPLIED -- background color for row --
>
<!-- Scope is simpler than headers attribute for common tables -->
<!ENTITY <span class="entity">% Scope</span> "(row|col|rowgroup|colgroup)">
<!-- TH is for headers, TD for data, but for cells acting as both use TD -->
<!ATTLIST (TH|TD) -- header or data cell --
%attrs; -- %coreattrs, %i18n, %events --
abbr %Text; #IMPLIED -- abbreviation for header cell --
axis CDATA #IMPLIED -- comma-separated list of related headers--
headers IDREFS #IMPLIED -- list of id's for header cells --
scope %Scope; #IMPLIED -- scope covered by header cells --
rowspan NUMBER 1 -- number of rows spanned by cell --
colspan NUMBER 1 -- number of cols spanned by cell --
%cellhalign; -- horizontal alignment in cells --
%cellvalign; -- vertical alignment in cells --
nowrap (nowrap) #IMPLIED -- suppress word wrap --
bgcolor %Color; #IMPLIED -- cell background color --
width %Length; #IMPLIED -- width for cell --
height %Length; #IMPLIED -- height for cell --
>
<!--================== Document Frames ===================================-->
<!--
The content model for HTML documents depends on whether the HEAD is
followed by a FRAMESET or BODY element. The widespread omission of
the BODY start tag makes it impractical to define the content model
without the use of a marked section.
-->
<![ %HTML.Frameset; [
<!ELEMENT <span class="element">FRAMESET</span> - - ((FRAMESET|FRAME)+ & NOFRAMES?) -- window subdivision-->
<!ATTLIST FRAMESET
%coreattrs; -- id, class, style, title --
rows %MultiLengths; #IMPLIED -- list of lengths,
default: 100% (1 row) --
cols %MultiLengths; #IMPLIED -- list of lengths,
default: 100% (1 col) --
onload %Script; #IMPLIED -- all the frames have been loaded --
onunload %Script; #IMPLIED -- all the frames have been removed --
>
]]>
<![ %HTML.Frameset; [
<!-- reserved frame names start with "_" otherwise starts with letter -->
<!ELEMENT <span class="element">FRAME</span> - O EMPTY -- subwindow -->
<!ATTLIST FRAME
%coreattrs; -- id, class, style, title --
longdesc %URI; #IMPLIED -- link to long description
(complements title) --
name CDATA #IMPLIED -- name of frame for targetting --
src %URI; #IMPLIED -- source of frame content --
frameborder (1|0) 1 -- request frame borders? --
marginwidth %Pixels; #IMPLIED -- margin widths in pixels --
marginheight %Pixels; #IMPLIED -- margin height in pixels --
noresize (noresize) #IMPLIED -- allow users to resize frames? --
scrolling (yes|no|auto) auto -- scrollbar or none --
>
]]>
<!ELEMENT <span class="element">IFRAME</span> - - (%flow;)* -- inline subwindow -->
<!ATTLIST IFRAME
%coreattrs; -- id, class, style, title --
longdesc %URI; #IMPLIED -- link to long description
(complements title) --
name CDATA #IMPLIED -- name of frame for targetting --
src %URI; #IMPLIED -- source of frame content --
frameborder (1|0) 1 -- request frame borders? --
marginwidth %Pixels; #IMPLIED -- margin widths in pixels --
marginheight %Pixels; #IMPLIED -- margin height in pixels --
scrolling (yes|no|auto) auto -- scrollbar or none --
align %IAlign; #IMPLIED -- vertical or horizontal alignment --
height %Length; #IMPLIED -- frame height --
width %Length; #IMPLIED -- frame width --
>
<![ %HTML.Frameset; [
<!ENTITY <span class="entity">% noframes.content</span> "(BODY) -(NOFRAMES)">
]]>
<!ENTITY <span class="entity">% noframes.content</span> "(%flow;)*">
<!ELEMENT <span class="element">NOFRAMES</span> - - %noframes.content;
-- alternate content container for non frame-based rendering -->
<!ATTLIST NOFRAMES
%attrs; -- %coreattrs, %i18n, %events --
>
<!--================ Document Head =======================================-->
<!-- %head.misc; defined earlier on as "SCRIPT|STYLE|META|LINK|OBJECT" -->
<!ENTITY <span class="entity">% head.content</span> "TITLE & ISINDEX? & BASE?">
<!ELEMENT <span class="element">HEAD</span> O O (%head.content;) +(%head.misc;) -- document head -->
<!ATTLIST HEAD
%attrs;
>
<!-- The TITLE element is not considered part of the flow of text.
It should be displayed, for example as the page header or
window title. Exactly one title is required per document.
-->
<!ELEMENT <span class="element">TITLE</span> - - (#PCDATA) -(%head.misc;) -- document title -->
<!ATTLIST TITLE %attrs>
<!ELEMENT <span class="element">ISINDEX</span> - O EMPTY -- single line prompt -->
<!ATTLIST ISINDEX
%coreattrs; -- id, class, style, title --
%i18n; -- lang, dir --
prompt %Text; #IMPLIED -- prompt message -->
<!ELEMENT <span class="element">BASE</span> - O EMPTY -- document base URI -->
<!ATTLIST BASE
href %URI; #IMPLIED -- URI that acts as base URI --
target %FrameTarget; #IMPLIED -- render in this frame --
>
<!ELEMENT <span class="element">META</span> - O EMPTY -- generic metainformation -->
<!ATTLIST META
%i18n; -- lang, dir, for use with content --
%metainformation;
http-equiv NAME #IMPLIED -- HTTP response header name --
name NAME #IMPLIED -- metainformation name --
scheme CDATA #IMPLIED -- select form of content --
>
<!ELEMENT <span class="element">STYLE</span> - - %StyleSheet -- style info -->
<!ATTLIST STYLE
%i18n; -- lang, dir, for use with title --
type %ContentType; #<em class="rfc2119" title="required">required</em> -- content type of style language --
media %MediaDesc; #IMPLIED -- designed for use with these media --
title %Text; #IMPLIED -- advisory title --
>
<!ELEMENT <span class="element">SCRIPT</span> - - %Script; -- script statements -->
<!ATTLIST SCRIPT
charset %Charset; #IMPLIED -- char encoding of linked resource --
type %ContentType; #<em class="rfc2119" title="required">required</em> -- content type of script language --
language CDATA #IMPLIED -- predefined script language name --
src %URI; #IMPLIED -- URI for an external script --
defer (defer) #IMPLIED -- UA may defer execution of script --
event CDATA #IMPLIED -- reserved for possible future use --
for %URI; #IMPLIED -- reserved for possible future use --
>
<!ELEMENT <span class="element">NOSCRIPT</span> - - (%flow;)*
-- alternate content container for non script-based rendering -->
<!ATTLIST NOSCRIPT
%attrs; -- %coreattrs, %i18n, %events --
>
<!--================ Document Structure ==================================-->
<!ENTITY <span class="entity">% version</span> "version CDATA #FIXED '%HTML.Version;'">
<![ %HTML.Frameset; [
<!ENTITY <span class="entity">% html.content</span> "HEAD, FRAMESET">
]]>
<!ENTITY <span class="entity">% html.content</span> "HEAD, BODY">
<!ELEMENT <span class="element">HTML</span> O O (%html.content;) -- document root element -->
<!ATTLIST HTML
%attrs;
%version;
>
</pre></div>
</div>
</div>
<div class="appendix section" id="about-this-document">
<!--OddPage--><h2><span class="secno">C. </span>About this Document</h2>
<div class="informative section" id="history">
<h3><span class="secno">C.1 </span>History</h3><p><em>This section is non-normative.</em></p>
<p>In early 2004, Mark Birbeck published a document named "RDF in XHTML"
via the XHTML2 Working Group wherein he laid
the groundwork for what would eventually become RDFa (The Resource
Description Framework in Attributes).</p>
<p>In 2006, the work was co-sponsored by the Semantic Web Deployment Work
Group, which began to formalize a technology to express semantic data in
XHTML. This technology was successfully developed and reached consensus at
the <acronym title="World Wide Web Consortium">W3C</acronym>, later published as an official <acronym title="World Wide Web Consortium">W3C</acronym> Recommendation. While HTML
provides a mechanism to express the structure of a document (title,
paragraphs, links), RDFa provides a mechanism to express the meaning in a
document (people, places, events).</p>
<p>The document, titled "RDF in XHTML: Syntax and Processing" [XHTML-RDFA],
defined a set of attributes and rules for
processing those attributes that resulted in the output of machine-readable
semantic data. While the document applied to XHTML, the attributes and
rules were always intended to operate across any tree-based structure
containing attributes on tree nodes (such as HTML4, SVG and ODF).</p>
<p>While RDFa was initially specified for use in XHTML, adoption by a
number of large organizations on the Web spurred RDFa's use in non-XHTML
languages. Its use in HTML4, before an official specification was developed
for those languages, caused concern regarding document conformance.</p>
<p>Over the years, the members of the
<a href="http://rdfa.info/">RDFa Task Force</a> had discussed the possibility
of applying
the same attributes and processing rules outlined in the XHTML+RDFa
specification to all HTML family documents. By design, the possibility of a
unified semantic data expression mechanism between all HTML and XHTML
family documents was squarely in the realm of possibility.</p>
<p>An RDFa Working Group was created in 2010 to address the issues concerning
multiple language implementations of RDFa. The XHTML+RDFa document was split
into a base specification, called RDFa Core 1.1 [<a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a>], and <em>thin</em>
specifications that layer above RDFa Core 1.1. The XHTML+RDFa 1.1 specification
[<a class="bibref" rel="biblioentry" href="#bib-XHTML-RDFA">XHTML-RDFA</a>] is an example of such a <em>thin</em> specification. This
document, also a <em>thin</em> specification, is targeted at HTML4, HTML5 and
XHTML5.
</p><p>This document describes the extensions to the RDFa Core 1.1
specification that permits the use of RDFa in all HTML family documents. By
using the attributes and processing rules described in the RDFa Core 1.1
specification and heeding the minor changes in this document, authors can
generate markup that produces the same semantic data output in
HTML4, HTML5 and XHTML5.</p>
</div>
<div class="informative section" id="change-history">
<h3><span class="secno">C.2 </span>Change History</h3><p><em>This section is non-normative.</em></p>
<p>2009-10-15: First version of the RDFa for HTML4, HTML5 and XHTML5.</p>
<p>2010-03-04: Updated HTML5 coercion to Infoset rules, preservation of
namespaces in Infoset and DOM2-based processors, clarifying how to
extract RDFa attributes via Infoset, how to extract RDFa attributes via DOM2.
</p><p>2010-05-02: Inheritance of basic processing rules from RDFa 1.1 [<a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a>],
instead of XHTML+RDFa 1.0 [<a class="bibref" rel="biblioentry" href="#bib-RDFA-SYNTAX">RDFA-SYNTAX</a>], inclusion of the HTML Default
Vocabulary Terms, inclusion of a HTML 4.01 + RDFa 1.1 DTD for validation purposes.</p>
</div>
<div class="informative section" id="acknowledgments">
<h3><span class="secno">C.3 </span>Acknowledgments</h3><p><em>This section is non-normative.</em></p>
<p>At the time of publication, the members of the
RDFa Working Group were:</p>
<p>
Ben Adida (chair), Benjamin Adrian, Mark Birbeck, Abhijit Galkward, Markus Gylling, Ivan Herman (staff contact), Toby Inkster, Shane McCarron, Knud Möller, John O'Donovan, Steven Pemberton, Jeffrey Sonstein, Manu Sporny (chair), Robert Weir
</p>
<p>At the time of publication, the members of the HTML Working Group were:</p>
<p>
Colin Aarts, Miller Abel, D.R.Imanuel Abromeit, Robert Accettura, Chris Adams, Ben Adida, Arihant Agarwal, yael aharon, Jim Allan, Kazuyuki Ashimura, Tab Atkins Jr., Stephen Axthelm, Mark Baker, Christopher Bank, Bogdan Baraszkiewicz, Gary Barber, David Baron, Adam Barth, Aaron Bassett, Adrian Bateman, Matthias Bauer, Johannes Behr, John-Mark Bell, Robin Berjon, Arve Bersvendsen, Levent Besik, David Bills, Mark Birbeck, David Bolter, Anders Bondehagen, Marco Bonetti, Glenn Bookout, Sierk Bornemann, Denis Boudreau, Ben Boyle, River Brandon, Judy Brewer, Dan Brickley, Per-Erik Brodin, Thomas Broyer, Don Brutzman, Craig Buckler, Dick Bulterman, Daniel Burnett, Noel Bush, Andrew Buzzell, Craig Cadwallader, Sally Cain, Ben Caldwell, Brian Campbell, Carlos Cardona, Maurice Carey, Eric Carlson, Laura Carlson, Gavin Carothers, Wayne Carr, Tomas Caspers, James Cassell, Tantek Çelik, Namachivayam Chelladurai, David Child, Wendy Chisholm, David Choi, wu chou, Edward Cianci, Michaeljohn Clement, Richard Conyard, Michael Cooper, Paul Cotton (chair), Chris Cressman, Brendan Cullen, Joseph D'Andrea, Mohammed DADAS, Deborah Dahl, Erik Dahlström, David Dailey, Will Daniels, Ivan De Marino, Tommaso Donnarumma, Chris Double, John Drinkwater, Marc Drumm, Mark DuBois, Karl Dubost, Andrew Duck, Clair Dunn, Henrik Dvergsdal, Dean Edridge, Anand Samuel Edwin, Eric Eggert, S Emerson, Ivan Enderlin, Rob Ennals, Jean-Pierre EVAIN, Steve Faulkner, Andrew Fedoniouk, Alexey Feldgendler, Alejandro Fernandez, Ian Fette, Roy Fielding, Markus Fischer, David Fisher, Nick Fitzsimons, Mark Foladare, John Foliot, Kelly Ford, Jason Fowler, Geoff Freed, Matthew Freels, Steve Gabrio, Mike Ganner, Patrick Garies, Olivier Gendrin, Giovanni Gentili, Dragos Georgita, Dimitri Glazkov, Daniel Glazman, Eliot Graff, James Graham, Aryeh Gregor, Chris Griego, Jonathan Griffin, Guillaume Guérin, Jon Gunderson, Lars Gunther, Raghavan Gurumurthy, Markku Hakkinen, Marcin Hanclik, Matt Harris, Chris Hay, Sean Hayes, Ian Hickson, Thomas Higginbotham, Krijn Hoetmer, Laurens Holst, Mikko Honkala, Tobias Horvath, Peter Howkins, Raul Hudea, Dale Hudjik, Jon Hughes, Lachlan Hunt, David Hyatt, David Håsäther, Eihab Ibrahim, Kunter Ilalan, Toby Inkster, Patrick D F Ion, Erik Isaksen, Richard Ishida, Moto Ishizawa, Yudai Iwasaki, Dean Jackson, Justin James, Arthur Jennings, Arne Johannessen, Kenny Johar, Sam Johnston, Sam Johnston, Doug Jones, Wilhelm Joys Andersen, Philip Jägenstedt, Susanne Jäger, Yehuda Katz, Jeremy Keith, Serge K. Keller, John Kemp, Kazuhito Kidachi, Don Kiely, Dowan Kim, Sebastian Kippe, Martin Kliehm, Egor Kloos, Graham Klyne, Justin Anthony Knapp, Masatomo Kobayashi, Marcel Koeppen, Jirka Kosek, Anssi Kostiainen, Lee Kowalkowski, Michael Kozakewich, Maxim Kozhuh, Peter Krantz, Keith Krieger, Kris Krueger, Mayank Kumar, Michael Köller, Jonatan Lander, Lucas Larson, Bruce Lawson, Josh Lawton, Nicolas LE GALL, Chasen Le Hara, Philippe Le Hégaret, Jane Lee, Kangchan Lee, WonSuk Lee, Niels Leenheer, Dean Leigh, Travis Leithead, Gez Lemon, Kornel Lesinski, aurélien levy, Scott Lewis, Li Li, Danny Liang, Jake Liddell, Håkon Wium Lie, Jedi Lin, Andy Lintner, Feng Liu, Jianjun Liu, Robert Love, Guillaume Ludwig, Andrew Maben, Shefik Macauley, Matthew MacKenzie, Krzysztof Maczynski, Vilem Malek, Murray Maloney, Jatinder Mann, Gabriel Mansour, Zhihong Mao, Bilgehan Maras, Chris Marrin, Robert Marshall, Andrew Martin, Alfonso Martínez de Lizarrondo, Luca Mascaro, Larry Masinter, Bill Mason, Matthew May, Cena Mayo, Charles McCathieNevile, Cameron McCormack, Martin McEvoy, Benjamin Meadowcroft, Shawn Medero, Reinier Meenhorst, Jens Meiert, Jakob Melander, Markus Mielke, Ben Millard, Mark Miller, Ryan Mitchell, Katsuhiko Momoi, Stefan More, Terry Morris, Thomas Morris, Daniel Morrison, Simon Myers, Stuart Myles, Marco Neumann, Sharon Newman, Tom Nguyen, Andrey Nikanorov, Jer Noble, Andrew Norman, Joshue O Connor, Robert O'Callahan, Edward O'Connor, Matt Obee, Frank Olivier, Ryan Orr, Debi Orton, Kulanthaivel Palanichamy, Frank Palinkas, Soohong Daniel Park, Sylvain Pasche, Chris Pearce, Brian Peppler, Ariel Pérez, Adele Peterson, Silvia Pfeiffer, Simon Pieters, Benoit Piette, Thomas Pike, Gabriel Pizzorno, Andrew Polk, Andrei Polushin, Pasquale Popolizio, Harri Porten, Alexey Proskuryakov, Michael Puls II, Juan Quemada, T.V. Raman, Andrew Ramsden, Arun Ranganathan, Marco Ranon, Matthew Ratzloff, Matthew Raymond, Ron Reisor, Daniel Renfer, Julian Reschke, Cyra Richardson, Ole Riesenberg, Anders Ringqvist, Adam Roben, Alex Robinson, Jude Robinson, Leonard Rosenthol, Gregory Rosmaita, Tony Ross, Steven Roussey, Sam Ruby (chair), Pietro Russo, Weston Ruter, Monikandan S, Lucas Sa, Rene Saarsoo, Sajid Saiyed, Janina Sajka, joaquin Salvachua, satish sangaru, Samuel Santos, Sorin Sbarnea, Daniel Schattenkirchner, Doug Schepers, Kai Scheppe, Christian Schmidt, Sebastian Schnitzenbaumer, Christopher Schroeder, Richard Schwerdtfeger, Gavin Sharp, Cynthia Shelly, Jonas Sicking, Andrew Sidwell, Leif Halvard Silli, David Singer, Henri Sivonen, Brian Skahan, Kenneth Sklander, Dan Smith, Dylan Smith, Michael(tm) Smith (staff contact), Geoffrey Sneddon, Gnanasekar S Somanathan, Manu Sporny, Elliott Sprehn, Maciej Stachowiak (chair), Vicki Stanton, Hallvord Steen, Johnny Stenback, Robert Stern, Peter Stewart, Stephen Stewart, Andrew Stibbard, Bruce Stockwell, Motti Strom, Oli Studholme, Mihai Sucan, Bryan Sullivan, Marat Tanalin, Mike Taylor, Philip Taylor, Sander Tekelenburg, Shane Thacker, Nik Thierry, Morten Tollefsen, Dominik Tomaszuk, Dzung Tran, Monika Trebo, Mark Turnage, Jason Turnbull, Scott Turner, Michael Turnwall, Matthew Turvey, Asbjørn Ulsberg, Wesley Upchurch, Ojan Vafai, Erik van Kempen, Anne van Kesteren, Sander van Lambalgen, Charl van Niekerk, Tim van Oostrom, Christopher Varley, Jean-Charles Verdié, John Vernaleo, Scott Vesey, Sigbjørn Vik, Laurent Vilday, Kent Villard, Jace Voracek, David Voth, Vladimir Vukicevic, Johnson Wang, Martijn Wargers, Jonathan Watt, Kyle Weems, Samuel Weinig, Ian Wessman, Ben West, Jason White, Michael Whitley, Joe Williams, Andrew Wilson, Chris Wilson, Doug Wright, Han Xu, Mateo Yadarola, Masataka Yakura, Channy Yun, Michael Zajac, Boris Zbarsky, Milan Zoufal, Michael zur Muehlen
</p>
</div>
</div>
<div id="references" class="appendix section"><!--OddPage--><h2><span class="secno">D. </span>References</h2><div id="normative-references" class="section"><h3><span class="secno">D.1 </span>Normative references</h3><dl class="bibliography"><dt id="bib-HTML5">[HTML5]</dt><dd>Ian Hickson; David Hyatt. <a href="http://www.w3.org/TR/2010/WD-html5-20100624/"><cite>HTML 5.</cite></a> 4 March 2010. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2010/WD-html5-20100624/">http://www.w3.org/TR/2010/WD-html5-20100624/</a>
</dd><dt id="bib-RDFA-CORE">[RDFA-CORE]</dt><dd>Shane McCarron; et al. <a href="http://www.w3.org/TR/2010/WD-rdfa-core-20100422"><cite>RDFa Core 1.1: Syntax and processing rules for embedding RDF through attributes.</cite></a>22 April 2010. W3C Working Draft. URL: <a href="http://www.w3.org/TR/2010/WD-rdfa-core-20100422">http://www.w3.org/TR/2010/WD-rdfa-core-20100422</a>
</dd><dt id="bib-RFC2119">[RFC2119]</dt><dd>S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> Internet RFC 2119. URL: <a href="http://www.ietf.org/rfc/rfc2119.txt">http://www.ietf.org/rfc/rfc2119.txt</a>
</dd><dt id="bib-RFC3236">[RFC3236]</dt><dd>P. Stark; M. Baker. <a href="http://www.rfc-editor.org/rfc/rfc3236.txt"><cite>The 'application/xhtml+xml' Media Type.</cite></a> January 2002. Internet RFC 3236. URL: <a href="http://www.rfc-editor.org/rfc/rfc3236.txt">http://www.rfc-editor.org/rfc/rfc3236.txt</a>
</dd><dt id="bib-XML-NAMES11">[XML-NAMES11]</dt><dd>Andrew Layman; et al. <a href="http://www.w3.org/TR/2006/REC-xml-names11-20060816"><cite>Namespaces in XML 1.1 (Second Edition).</cite></a> 16 August 2006. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2006/REC-xml-names11-20060816">http://www.w3.org/TR/2006/REC-xml-names11-20060816</a>
</dd></dl></div><div id="informative-references" class="section"><h3><span class="secno">D.2 </span>Informative references</h3><dl class="bibliography"><dt id="bib-RDFA-SYNTAX">[RDFA-SYNTAX]</dt><dd>Ben Adida, et al. <a href="http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014"><cite>RDFa in XHTML: Syntax and Processing.</cite></a> 14 October 2008. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014">http://www.w3.org/TR/2008/REC-rdfa-syntax-20081014</a>
</dd><dt id="bib-XHTML-RDFA">[XHTML-RDFA]</dt><dd>Shane McCarron; et. al. <a href="http://www.w3.org/TR/2010/WD-xhtml-rdfa-20100422"><cite>XHTML+RDFa 1.1.</cite></a> 22 April 2010. W3C Working Draft. URL: <a href="http://www.w3.org/TR/2010/WD-xhtml-rdfa-20100422">http://www.w3.org/TR/2010/WD-xhtml-rdfa-20100422/</a>
</dd><dt id="bib-XHTML-VOCAB">[XHTML-VOCAB]</dt><dd>XHTML 2 Working Group. <a href="http://www.w3.org/1999/xhtml/vocab"><cite>XHTML Vocabulary</cite></a>. URL: <a href="http://www.w3.org/1999/xhtml/vocab">http://www.w3.org/1999/xhtml/vocab</a>
</dd></dl></div></div></body></html>