Another abandoned server code base... this is kind of an ancestor of taskrambler.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 

2579 lines
129 KiB

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML+RDFa 1.0//EN' 'http://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd'>
<html dir="ltr" about="" property="dcterms:language" content="en" xmlns="http://www.w3.org/1999/xhtml" xmlns:dcterms='http://purl.org/dc/terms/' xmlns:bibo='http://purl.org/ontology/bibo/' xmlns:foaf='http://xmlns.com/foaf/0.1/' xmlns:xsd='http://www.w3.org/2001/XMLSchema#'>
<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><style type="text/css">
/*****************************************************************
* ReSpec CSS
* Robin Berjon (robin at berjon dot com)
* v0.05 - 2009-07-31
*****************************************************************/
/* --- INLINES --- */
em.rfc2119 {
text-transform: lowercase;
font-variant: small-caps;
font-style: normal;
color: #900;
}
h1 acronym, h2 acronym, h3 acronym, h4 acronym, h5 acronym, h6 acronym, a acronym,
h1 abbr, h2 abbr, h3 abbr, h4 abbr, h5 abbr, h6 abbr, a abbr {
border: none;
}
dfn {
font-weight: bold;
}
a.internalDFN {
color: inherit;
border-bottom: 1px solid #99c;
text-decoration: none;
}
a.externalDFN {
color: inherit;
border-bottom: medium dotted #ccc;
text-decoration: none;
}
a.bibref {
text-decoration: none;
}
code {
color: #ff4500;
}
/* --- WEB IDL --- */
pre.idl {
border-top: 1px solid #90b8de;
border-bottom: 1px solid #90b8de;
padding: 1em;
line-height: 120%;
}
pre.idl::before {
content: "WebIDL";
display: block;
width: 150px;
background: #90b8de;
color: #fff;
font-family: initial;
padding: 3px;
font-weight: bold;
margin: -1em 0 1em -1em;
}
.idlType {
color: #ff4500;
font-weight: bold;
text-decoration: none;
}
/*.idlModule*/
/*.idlModuleID*/
/*.idlInterface*/
.idlInterfaceID {
font-weight: bold;
color: #005a9c;
}
.idlSuperclass {
font-style: italic;
color: #005a9c;
}
/*.idlAttribute*/
.idlAttrType, .idlFieldType {
color: #005a9c;
}
.idlAttrName, .idlFieldName {
color: #ff4500;
}
.idlAttrName a, .idlFieldName a {
color: #ff4500;
border-bottom: 1px dotted #ff4500;
text-decoration: none;
}
/*.idlMethod*/
.idlMethType {
color: #005a9c;
}
.idlMethName {
color: #ff4500;
}
.idlMethName a {
color: #ff4500;
border-bottom: 1px dotted #ff4500;
text-decoration: none;
}
/*.idlParam*/
.idlParamType {
color: #005a9c;
}
.idlParamName {
font-style: italic;
}
.extAttr {
color: #666;
}
/*.idlConst*/
.idlConstType {
color: #005a9c;
}
.idlConstName {
color: #ff4500;
}
.idlConstName a {
color: #ff4500;
border-bottom: 1px dotted #ff4500;
text-decoration: none;
}
/*.idlException*/
.idlExceptionID {
font-weight: bold;
color: #c00;
}
.idlTypedefID, .idlTypedefType {
color: #005a9c;
}
.idlRaises, .idlRaises a.idlType, .idlRaises a.idlType code, .excName a, .excName a code {
color: #c00;
font-weight: normal;
}
.excName a {
font-family: monospace;
}
.idlRaises a.idlType, .excName a.idlType {
border-bottom: 1px dotted #c00;
}
.excGetSetTrue, .excGetSetFalse, .prmNullTrue, .prmNullFalse, .prmOptTrue, .prmOptFalse {
width: 45px;
text-align: center;
}
.excGetSetTrue, .prmNullTrue, .prmOptTrue { color: #0c0; }
.excGetSetFalse, .prmNullFalse, .prmOptFalse { color: #c00; }
.idlImplements a {
font-weight: bold;
}
dl.attributes, dl.methods, dl.constants, dl.fields {
margin-left: 2em;
}
.attributes dt, .methods dt, .constants dt, .fields dt {
font-weight: normal;
}
.attributes dt code, .methods dt code, .constants dt code, .fields dt code {
font-weight: bold;
color: #000;
font-family: monospace;
}
.attributes dt code, .fields dt code {
background: #ffffd2;
}
.attributes dt .idlAttrType code, .fields dt .idlFieldType code {
color: #005a9c;
background: transparent;
font-family: inherit;
font-weight: normal;
font-style: italic;
}
.methods dt code {
background: #d9e6f8;
}
.constants dt code {
background: #ddffd2;
}
.attributes dd, .methods dd, .constants dd, .fields dd {
margin-bottom: 1em;
}
table.parameters, table.exceptions {
border-spacing: 0;
border-collapse: collapse;
margin: 0.5em 0;
width: 100%;
}
table.parameters { border-bottom: 1px solid #90b8de; }
table.exceptions { border-bottom: 1px solid #deb890; }
.parameters th, .exceptions th {
color: #fff;
padding: 3px 5px;
text-align: left;
font-family: initial;
font-weight: normal;
text-shadow: #666 1px 1px 0;
}
.parameters th { background: #90b8de; }
.exceptions th { background: #deb890; }
.parameters td, .exceptions td {
padding: 3px 10px;
border-top: 1px solid #ddd;
vertical-align: top;
}
.parameters tr:first-child td, .exceptions tr:first-child td {
border-top: none;
}
.parameters td.prmName, .exceptions td.excName, .exceptions td.excCodeName {
width: 100px;
}
.parameters td.prmType {
width: 120px;
}
table.exceptions table {
border-spacing: 0;
border-collapse: collapse;
width: 100%;
}
/* --- TOC --- */
.toc a {
text-decoration: none;
}
a .secno {
color: #000;
}
/* --- TABLE --- */
table.simple {
border-spacing: 0;
border-collapse: collapse;
border-bottom: 3px solid #005a9c;
}
.simple th {
background: #005a9c;
color: #fff;
padding: 3px 5px;
text-align: left;
}
.simple th[scope="row"] {
background: inherit;
color: inherit;
border-top: 1px solid #ddd;
}
.simple td {
padding: 3px 10px;
border-top: 1px solid #ddd;
}
.simple tr:nth-child(even) {
background: #f0f6ff;
}
/* --- DL --- */
.section dd > p:first-child {
margin-top: 0;
}
.section dd > p:last-child {
margin-bottom: 0;
}
.section dd {
margin-bottom: 1em;
}
.section dl.attrs dd, .section dl.eldef dd {
margin-bottom: 0;
}
/* --- EXAMPLES --- */
pre.example {
border-top: 1px solid #ff4500;
border-bottom: 1px solid #ff4500;
padding: 1em;
margin-top: 1em;
}
pre.example::before {
content: "Example";
display: block;
width: 150px;
background: #ff4500;
color: #fff;
font-family: initial;
padding: 3px;
font-weight: bold;
margin: -1em 0 1em -1em;
}
/* --- EDITORIAL NOTES --- */
.issue {
padding: 1em;
margin: 1em 0em 0em;
border: 1px solid #f00;
background: #ffc;
}
.issue::before {
content: "Issue";
display: block;
width: 150px;
margin: -1.5em 0 0.5em 0;
font-weight: bold;
border: 1px solid #f00;
background: #fff;
padding: 3px 1em;
}
.note {
margin: 1em 0em 0em;
padding: 1em;
border: 2px solid #cff6d9;
background: #e2fff0;
}
.note::before {
content: "Note";
display: block;
width: 150px;
margin: -1.5em 0 0.5em 0;
font-weight: bold;
border: 1px solid #cff6d9;
background: #fff;
padding: 3px 1em;
}
/* --- Best Practices --- */
div.practice {
border: solid #bebebe 1px;
margin: 2em 1em 1em 2em;
}
span.practicelab {
margin: 1.5em 0.5em 1em 1em;
font-weight: bold;
font-style: italic;
}
span.practicelab { background: #dfffff; }
span.practicelab {
position: relative;
padding: 0 0.5em;
top: -1.5em;
}
p.practicedesc {
margin: 1.5em 0.5em 1em 1em;
}
@media screen {
p.practicedesc {
position: relative;
top: -2em;
padding: 0;
margin: 1.5em 0.5em -1em 1em;
}
/* --- SYNTAX HIGHLIGHTING --- */
pre.sh_sourceCode {
background-color: white;
color: black;
font-style: normal;
font-weight: normal;
}
pre.sh_sourceCode .sh_keyword { color: #005a9c; font-weight: bold; } /* language keywords */
pre.sh_sourceCode .sh_type { color: #666; } /* basic types */
pre.sh_sourceCode .sh_usertype { color: teal; } /* user defined types */
pre.sh_sourceCode .sh_string { color: red; font-family: monospace; } /* strings and chars */
pre.sh_sourceCode .sh_regexp { color: orange; font-family: monospace; } /* regular expressions */
pre.sh_sourceCode .sh_specialchar { color: #ffc0cb; font-family: monospace; } /* e.g., \n, \t, \\ */
pre.sh_sourceCode .sh_comment { color: #A52A2A; font-style: italic; } /* comments */
pre.sh_sourceCode .sh_number { color: purple; } /* literal numbers */
pre.sh_sourceCode .sh_preproc { color: #00008B; font-weight: bold; } /* e.g., #include, import */
pre.sh_sourceCode .sh_symbol { color: blue; } /* e.g., *, + */
pre.sh_sourceCode .sh_function { color: black; font-weight: bold; } /* function calls and declarations */
pre.sh_sourceCode .sh_cbracket { color: red; } /* block brackets (e.g., {, }) */
pre.sh_sourceCode .sh_todo { font-weight: bold; background-color: #00FFFF; } /* TODO and FIXME */
/* Predefined variables and functions (for instance glsl) */
pre.sh_sourceCode .sh_predef_var { color: #00008B; }
pre.sh_sourceCode .sh_predef_func { color: #00008B; font-weight: bold; }
/* for OOP */
pre.sh_sourceCode .sh_classname { color: teal; }
/* line numbers (not yet implemented) */
pre.sh_sourceCode .sh_linenum { display: none; }
/* Internet related */
pre.sh_sourceCode .sh_url { color: blue; text-decoration: underline; font-family: monospace; }
/* for ChangeLog and Log files */
pre.sh_sourceCode .sh_date { color: blue; font-weight: bold; }
pre.sh_sourceCode .sh_time, pre.sh_sourceCode .sh_file { color: #00008B; font-weight: bold; }
pre.sh_sourceCode .sh_ip, pre.sh_sourceCode .sh_name { color: #006400; }
/* for Prolog, Perl... */
pre.sh_sourceCode .sh_variable { color: #006400; }
/* for LaTeX */
pre.sh_sourceCode .sh_italics { color: #006400; font-style: italic; }
pre.sh_sourceCode .sh_bold { color: #006400; font-weight: bold; }
pre.sh_sourceCode .sh_underline { color: #006400; text-decoration: underline; }
pre.sh_sourceCode .sh_fixed { color: green; font-family: monospace; }
pre.sh_sourceCode .sh_argument { color: #006400; }
pre.sh_sourceCode .sh_optionalargument { color: purple; }
pre.sh_sourceCode .sh_math { color: orange; }
pre.sh_sourceCode .sh_bibtex { color: blue; }
/* for diffs */
pre.sh_sourceCode .sh_oldfile { color: orange; }
pre.sh_sourceCode .sh_newfile { color: #006400; }
pre.sh_sourceCode .sh_difflines { color: blue; }
/* for css */
pre.sh_sourceCode .sh_selector { color: purple; }
pre.sh_sourceCode .sh_property { color: blue; }
pre.sh_sourceCode .sh_value { color: #006400; font-style: italic; }
/* other */
pre.sh_sourceCode .sh_section { color: black; font-weight: bold; }
pre.sh_sourceCode .sh_paren { color: red; }
pre.sh_sourceCode .sh_attribute { color: #006400; }
</style><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 property="dcterms:title" class="title" id="title">HTML+RDFa 1.1</h1><h2 property="bibo:subtitle" id="subtitle">Support for RDFa in HTML4 and HTML5</h2><h2 property="dcterms:issued" datatype="xsd:dateTime" content="2011-05-25T04:00:00+0000" id="w3c-working-draft-25-may-2011">W3C Working Draft 25 May 2011</h2>
<dl>
<dt>This version:</dt>
<dd><a href="http://www.w3.org/TR/2011/WD-rdfa-in-html-20110525/">http://www.w3.org/TR/2011/WD-rdfa-in-html-20110525/</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 versions:</dt>
<dd><a rel="dcterms:replaces" href="http://www.w3.org/TR/2011/WD-rdfa-in-html-20110405/">http://www.w3.org/TR/2011/WD-rdfa-in-html-20110405/</a></dd>
<dd><a href="http://www.w3.org/TR/2011/WD-rdfa-in-html-20110113/">http://www.w3.org/TR/2011/WD-rdfa-in-html-20110113/</a></dd>
<dd><a href="http://www.w3.org/TR/2010/WD-rdfa-in-html-20101019/">http://www.w3.org/TR/2010/WD-rdfa-in-html-20101019/</a></dd>
<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>
<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>
<dd><a href="http://www.w3.org/TR/2009/WD-rdfa-in-html-20091015/">http://www.w3.org/TR/2009/WD-rdfa-in-html-20091015/</a></dd>
<dt>Editors:</dt><dd rel="bibo:editor"><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Manu Sporny" href="mailto:msporny@digitalbazaar.com">Manu Sporny</a>, <a rel="foaf:workplaceHomepage" href="http://blog.digitalbazaar.com">Digital Bazaar, Inc.</a></span>
</dd>
<dd rel="bibo:editor"><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Shane McCarron" href="mailto:shane@aptest.com">Shane McCarron</a>, <a rel="foaf:workplaceHomepage" href="http://www.aptest.com/">Applied Testing and Technology, Inc.</a></span>
</dd>
<dt>Authors:</dt><dd rel="dcterms:contributor"><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Ben Adida" href="http://adida.net/">Ben Adida</a>, <a rel="foaf:workplaceHomepage" href="http://creativecommons.org/">Creative Commons</a></span>
</dd>
<dd rel="dcterms:contributor"><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Mark Birbeck" href="http://webbackplane.com/">Mark Birbeck</a>, <a rel="foaf:workplaceHomepage" href="http://webbackplane.com/">Web Backplane Ltd.</a></span>
</dd>
<dd rel="dcterms:contributor"><span typeof="foaf:Person"><a rel="foaf:homepage" property="foaf:name" content="Steven Pemberton" href="http://homepages.cwi.nl/~steven/">Steven Pemberton</a>, <a rel="foaf:workplaceHomepage" href="http://www.cwi.nl/">CWI</a></span>
</dd>
</dl>
<p
class="copyright"><a rel="license"
href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
© 2009-2011 <span rel="dcterms:publisher"><span
typeof="foaf:Organization"><a rel="foaf:homepage" property="foaf:name"
content="World Wide Web Consotrium" href="http://www.w3.org/"><acronym
title="World Wide Web
Consortium">W3C</acronym></a><sup>®</sup></span></span> (<a
href="http://www.csail.mit.edu/"><acronym title="Massachusetts Institute of
Technology">MIT</acronym></a>, <a href="http://www.ercim.eu/"><acronym
title="European Research Consortium for Informatics and
Mathematics">ERCIM</acronym></a>, <a
href="http://www.keio.ac.jp/">Keio</a>), All Rights Reserved. W3C <a
href="http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>,
<a
href="http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a>
and <a
href="http://www.w3.org/Consortium/Legal/copyright-documents">document
use</a> rules apply.</p><hr /></div>
<div id="abstract" class="introductory section" property="dcterms:abstract" datatype="" typeof="bibo:Chapter" about="#abstract"><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" typeof="bibo:Chapter" about="#sotd"><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 W3C publications and the latest revision of this technical report can be found in the <a href="http://www.w3.org/TR/">W3C technical reports index</a> at http://www.w3.org/TR/.</em></p>
<!-- <p>This 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>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 W3C 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/">RDF Web Applications Working Group</a>,
recently re-chartered from the RDFa Working Group, and the
<a href="http://www.w3.org/html/wg/">HTML Working Group</a>. The specification
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/test-suite/">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 Last Call Working Draft.
This document is intended to become a W3C Recommendation.
If you wish to make comments regarding this document, please submit them
via the <a href="http://www.w3.org/Bugs/Public/enter_bug.cgi?product=HTML%20WG">public bug database</a>.
If you cannot do this then submit 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>),
and arrangements will be made to submit your comments to the
<a href="http://www.w3.org/Bugs/Public/enter_bug.cgi?product=HTML%20WG">public bug
database</a>.
The Last Call period ends 03 August 2011.
All feedback is welcome.</p>
<p>Publication as a Last Call Working Draft does not imply endorsement
by the W3C 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>Activities are being pursued by some members of the HTML Working Group
to provide new information related to this document, with the intent of
reopening
<a href="http://dev.w3.org/html5/status/new-information-status.html#ISSUE-120">HTML Working Group issue 120 (Clarify how prefixes work in RDFa, and document that they’re an optional feature)</a>.</p>
<p>W3C anticipates that there will be changes to this specification as a
result of the resolution of Last Call issues. Per the usual W3C Process,
any significant changes to the specification will trigger a subsequent Last
Call.</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
W3C Patent Policy</a>. W3C 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 W3C Patent Policy</a>.</p></div><div id="toc"
typeof="bibo:Chapter" about="#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></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></li><li class="tocline"><a href="#backwards-compatibility"
class="tocxref"><span class="secno">5. </span>Backwards
Compatibility</a><ul class="toc"><li class="tocline"><a
href="#xmlns--prefixed-attributes" class="tocxref"><span class="secno">5.1
</span><code>xmlns:</code>-Prefixed Attributes</a></li><li
class="tocline"><a
href="#conformance-criteria-for-xmlns--prefixed-attributes"
class="tocxref"><span class="secno">5.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">5.3 </span>Preserving Namespaces via Coercion to
Infoset</a></li><li class="tocline"><a href="#infoset-based-processors"
class="tocxref"><span class="secno">5.4 </span>Infoset-based
Processors</a><ul class="toc"><li class="tocline"><a
href="#extracting-uri-mappings-from-infosets" class="tocxref"><span
class="secno">5.4.1 </span>Extracting URI Mappings from
Infosets</a></li><li class="tocline"><a href="#processing-rdfa-attributes"
class="tocxref"><span class="secno">5.4.2 </span>Processing RDFa
Attributes</a></li></ul></li><li class="tocline"><a
href="#dom-level-1-and-level-2-based-processors" class="tocxref"><span
class="secno">5.5 </span>DOM Level 1 and Level 2-based Processors</a><ul
class="toc"><li class="tocline"><a
href="#extracting-uri-mappings-via-dom-level-2" class="tocxref"><span
class="secno">5.5.1 </span>Extracting URI Mappings via DOM Level
2</a></li><li class="tocline"><a href="#processing-rdfa-attributes-1"
class="tocxref"><span class="secno">5.5.2 </span>Processing RDFa
Attributes</a></li></ul></li></ul></li><li class="tocline"><a
href="#validation" class="tocxref"><span class="secno">A.
</span>Validation</a><ul class="toc"><li class="tocline"><a
href="#the-html-4.01---rdfa-1.1-dtd" class="tocxref"><span
class="secno">A.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">B. </span>About this Document</a><ul class="toc"><li
class="tocline"><a href="#history" class="tocxref"><span class="secno">B.1
</span>History</a></li><li class="tocline"><a href="#change-history"
class="tocxref"><span class="secno">B.2 </span>Change History</a></li><li
class="tocline"><a href="#acknowledgments" class="tocxref"><span
class="secno">B.3 </span>Acknowledgments</a></li></ul></li><li
class="tocline"><a href="#references" class="tocxref"><span
class="secno">C. </span>References</a><ul class="toc"><li
class="tocline"><a href="#normative-references" class="tocxref"><span
class="secno">C.1 </span>Normative references</a></li><li
class="tocline"><a href="#informative-references" class="tocxref"><span
class="secno">C.2 </span>Informative
references</a></li></ul></li></ul></div>
<div class="informative section" id="introduction" typeof="bibo:Chapter" about="#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 readers. 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 pages: browsers only see presentation information. RDFa is
intended to solve the problem of marking up 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" typeof="bibo:Chapter" about="#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 [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC2119">RFC2119</a></cite>].</p>
<div id="document-conformance" typeof="bibo:Chapter" about="#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 [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a></cite>]. All RDFa attributes <em class="rfc2119" title="should">should</em> be used in a way that
is conformant with [<cite><a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a></cite>] and this 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 Appendix A.
</li>
</ul>
<p>An example of a conforming HTML+RDFa document:</p>
<pre class="example" title="Example of an HTML+RDFa 1.1 document">
&lt;html lang="en"&gt;
&lt;head&gt;
&lt;title&gt;Example Document&lt;/title&gt;
&lt;/head&gt;
&lt;body&gt;
&lt;p&gt;This website is &lt;a href="http://example.org/"&gt;example.org&lt;/a&gt;.&lt;/p&gt;
&lt;/body&gt;
&lt;/html&gt;</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 [<cite><a class="bibref" rel="biblioentry" href="#bib-RFC3236">RFC3236</a></cite>].
</p>
</div>
<div id="rdfa-processor-conformance" typeof="bibo:Chapter" about="#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 [<cite><a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a></cite>].</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" typeof="bibo:Chapter" about="#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" typeof="bibo:Chapter" about="#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 [<cite><a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a></cite>] 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" typeof="bibo:Chapter" about="#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 [<cite><a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a></cite>] with the following extensions:</p>
<ul>
<li>The <a class="tref" title="default_vocabulary_URI">default vocabulary URI</a> is undefined.</li>
<li>HTML+RDFa uses two profiles by default - first incorporating the
XML+RDFa profile document <code>http://www.w3.org/profile/rdfa-1.1</code>,
and then incorporating the RDFa Profile at
<code>http://www.w3.org/profile/html-rdfa-1.1</code>.</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>
<p>
The <code>version</code> attribute is not supported in HTML5 and is
non-conforming. However, if an HTML+RDFa document contains the
<code>version</code> attribute on the <code>html</code> element, a conforming
RDFa Processor must examine the value of this attribute. If the value matches
that of a defined version of RDFa, then the processing rules for that version
must be used. If the value does not match a defined version, or there is no
<code>version</code> attribute, then the processing rules for the most recent
version of RDFa 1.1 must be used.
</p>
</div>
<div id="modifying-the-input-document" typeof="bibo:Chapter" about="#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 [<cite><a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a></cite>], 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" typeof="bibo:Chapter" about="#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#T-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 [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a></cite>]
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" typeof="bibo:Chapter" about="#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#T-evaluation-context">evaluation context</a>
in the
<a class="tref" title="list_of_URI_mappings" href="http://www.w3.org/TR/rdfa-core#T-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">
&lt;p xmlns:ex="http://example.org/vocab#" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"&gt;
Two rectangles (the example markup for them are stored in a triple):
&lt;svg <span class="hilite">xmlns</span>="<span class="hilite">http://www.w3.org/2000/svg</span>" property="ex:markup" datatype="rdf:XMLLiteral"&gt;
&lt;rect width="300" height="100" style="fill:rgb(0,0,255);stroke-width:1; stroke:rgb(0,0,0)"&gt;&lt;/rect&gt;
&lt;rect width="50" height="50" style="fill:rgb(255,0,0);stroke-width:2;stroke:rgb(0,0,0)"&gt;&lt;/rect&gt;&lt;/svg&gt;
&lt;/p&gt;</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">
&lt;&gt;
&lt;http://example.org/vocab#markup&gt;
"&lt;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)\"/&gt;
&lt;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)\"/&gt;"^^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">
&lt;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>&gt;
This is how you markup a user in FBML:
&lt;span property="ex:markup" datatype="rdf:XMLLiteral"&gt;
&lt;p&gt;&lt;fb:user uid="12345"&gt;The User&lt;/fb:user&gt;&lt;/p&gt;
&lt;/span&gt;
&lt;/p&gt;</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">
&lt;&gt;
&lt;http://example.org/vocab#markup&gt;
"&lt;p <span class="hilite">xmlns:fb="http://www.facebook.com/2008/fbml"</span>&gt;
&lt;fb:user uid="12345"&gt;
&lt;/p&gt;"^^http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral .</pre>
<p></p>
</div>
</div>
<div id="extensions-to-the-html5-syntax" typeof="bibo:Chapter" about="#extensions-to-the-html5-syntax" class="section">
<!-- OddPage -->
<h2><span class="secno">4. </span>Extensions to the HTML5 Syntax</h2>
<p>There are a few attributes that are added as extensions to the HTML5
syntax in order to fully support RDFa:
</p><ul>
<li>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>, <em class="rfc2119" title="must">must</em> be allowed and seen as conforming when used in
an HTML4, HTML5 or XHTML5 document.</li>
</ul>
</div>
<div id="backwards-compatibility" typeof="bibo:Chapter" about="#backwards-compatibility" class="section">
<!-- OddPage -->
<h2><span class="secno">5. </span>Backwards Compatibility</h2>
<p>RDFa Core 1.1 deprecates the usage of <code>xmlns:</code> in RDFa 1.1
documents. Web page authors <em class="rfc2119" title="should not">should not</em> use <code>xmlns:</code> to express
prefix mappings in RDFa 1.1 documents. Web page authors <em class="rfc2119" title="should">should</em> use
the <code>prefix</code> attribute to specify prefix mappings.</p>
<p>However, there are times when XHTML+RDFa 1.0 documents are served by web
servers using the <code>text/html</code> MIMEType. In these instances, the
HTML5 specification asserts that the document is processed according to the
non-XML mode HTML5 processing rules. In these particular cases, it is
important that the prefixes declared via <code>xmlns:</code> are preserved
for the RDFa processors to ensure backwards-compatibility with RDFa 1.0
documents. The following sections detail the backwards compatibility
details for RDFa processor implementations.</p>
<div id="xmlns--prefixed-attributes" typeof="bibo:Chapter" about="#xmlns--prefixed-attributes" class="section">
<h3><span class="secno">5.1 </span><code>xmlns:</code>-Prefixed Attributes</h3>
<p>The RDFa Core 1.1 [<cite><a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a></cite>] specification effectively deprecates the
use of the <code>xmlns:</code> mechanism to declare CURIE prefix mappings in
favor of the <code>prefix</code> attribute. While utilizing
<code>xmlns:</code> is now frowned upon, there are instances where it is
unavoidable - such as publishing legacy documents as HTML5 or supporting
older XHTML+RDFa 1.0 documents that rely on the <code>xmlns:</code>
attribute.</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-via-dom-level-2">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:&lt;PREFIX>="&lt;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>"&lt;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 id="conformance-criteria-for-xmlns--prefixed-attributes" typeof="bibo:Chapter" about="#conformance-criteria-for-xmlns--prefixed-attributes" class="section">
<h3><span class="secno">5.2 </span>Conformance Criteria for <code>xmlns:</code>-Prefixed Attributes</h3>
<p>Since RDFa 1.0 documents may contain 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. Conformance checkers <em class="rfc2119" title="should">should</em> generate
warnings noting that the use of <code>xmlns:</code> is deprecated.
</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 [<cite><a class="bibref" rel="biblioentry" href="#bib-XML-NAMES11">XML-NAMES11</a></cite>],
<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" typeof="bibo:Chapter" about="#preserving-namespaces-via-coercion-to-infoset" class="section">
<h3><span class="secno">5.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 1.0 documents may contain 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 [<cite><a class="bibref" rel="biblioentry" href="#bib-HTML5">HTML5</a></cite>]
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">
&lt;div xmlns:com="http://purl.org/commerce#"&gt;</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>com</code>, and a [normalized value] of
"<code>http://purl.org/commerce#</code>".
</p>
</div>
<div id="infoset-based-processors" typeof="bibo:Chapter" about="#infoset-based-processors" class="section">
<h3><span class="secno">5.4 </span>Infoset-based Processors</h3>
<p>While the intent of the RDFa processing instructions are 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" typeof="bibo:Chapter" about="#extracting-uri-mappings-from-infosets" class="section">
<h4><span class="secno">5.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 [<cite><a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a></cite>],
<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/#T-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/#T-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">
&lt;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" typeof="bibo:Chapter" about="#processing-rdfa-attributes" class="section">
<h4><span class="secno">5.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 [<cite><a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a></cite>],
<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-1-and-level-2-based-processors" typeof="bibo:Chapter" about="#dom-level-1-and-level-2-based-processors" class="section">
<h3><span class="secno">5.5 </span>DOM Level 1 and 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>Most DOM-aware RDFa Processors are capable of accessing DOM Level 1
[<cite><a class="bibref" rel="biblioentry" href="#bib-DOM-LEVEL-1">DOM-LEVEL-1</a></cite>]
methods to process attributes on elements. To discover all
<code>xmlns:</code>-specified CURIE prefix mappings, the
<a href="http://www.w3.org/TR/REC-DOM-Level-1/level-one-core.html#ID-1950641247">
Node.attributes</a>
<a href="http://www.w3.org/TR/REC-DOM-Level-1/level-one-core.html#ID-1780488922">
NamedNodeMap</a> can be iterated over. Each
<a href="http://www.w3.org/TR/REC-DOM-Level-1/level-one-core.html#ID-637646024">
Attr.name</a> that
starts with the text string <code>xmlns:</code> specifies a CURIE prefix
mapping. The value to be mapped is the string after the <code>xmlns:</code>
substring in the Attr.name variable and the value to be mapped is
the value of the Attr.value variable.</p>
<p>The intent of the RDFa processing instructions are to provide a
set of rules that are as language and toolchain agnostic as possible. If
a developer chooses to not use the DOM1 environment mechanism outlined in
the previous paragraph, they may use the following DOM2 [<cite><a class="bibref" rel="biblioentry" href="#bib-DOM-LEVEL-2-CORE">DOM-LEVEL-2-CORE</a></cite>]
environment mechanism.</p>
<div id="extracting-uri-mappings-via-dom-level-2" typeof="bibo:Chapter" about="#extracting-uri-mappings-via-dom-level-2" class="section">
<h4><span class="secno">5.5.1 </span>Extracting URI Mappings via DOM Level 2</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 [<cite><a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a></cite>],
<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/#T-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/#T-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">
&lt;div xmlns:com="http://purl.org/commerce#" ...</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>com</code> to <code>http://purl.org/commerce#</code>.
</p>
</div>
<div id="processing-rdfa-attributes-1" typeof="bibo:Chapter" about="#processing-rdfa-attributes-1" class="section">
<h4><span class="secno">5.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 [<cite><a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a></cite>],
<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="validation" typeof="bibo:Chapter" about="#validation">
<!-- OddPage -->
<h2><span class="secno">A. </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">
&lt;!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01+RDFa 1.1//EN"
"http://www.w3.org/MarkUp/DTD/html401-rdfa11-1.dtd"&gt;</pre>
<div id="the-html-4.01---rdfa-1.1-dtd" typeof="bibo:Chapter" about="#the-html-4.01---rdfa-1.1-dtd" class="section">
<h3 id="html-rdfa-dtd"><span class="secno">A.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">
&lt;!--
This is the HTML 4.01 + RDFa 1.1 DTD, which includes
presentation attributes and elements that W3C expects to phase out
as support for style sheets matures. Authors should use the Strict
DTD when possible, but may use the Transitional DTD when support
for presentation attribute and elements is required.
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: 2011/05/25 16:25:17 $
Editors:
Shane McCarron &lt;shane@aptest.com&gt;
Manu Sporny &lt;msporny@digitalbazaar.com&gt;
Original Authors:
Dave Raggett &lt;dsr@w3.org&gt;
Arnaud Le Hors &lt;lehors@w3.org&gt;
Ian Jacobs &lt;ij@w3.org&gt;
Further information about RDFa in HTML is available at:
http://www.w3.org/TR/rdfa-in-html
Further information about HTML 4.01 is available at:
http://www.w3.org/TR/1999/REC-html401-19991224
And further information about RDFa is available at:
http://www.w3.org/TR/rdfa-core
The HTML 4.01 specification includes additional
syntactic constraints that cannot be expressed within
the DTDs.
--&gt;
&lt;!ENTITY <span class="entity">% HTML.Version</span> "-//W3C//DTD HTML 4.01+RDFa 1.1//EN"
-- Typical usage:
&lt;!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01+RDFa 1.1//EN"
"http://www.w3.org/MarkUp/DTD/html401-rdfa11-1.dtd"&gt;
&lt;html&gt;
&lt;head&gt;
...
&lt;/head&gt;
&lt;body&gt;
...
&lt;/body&gt;
&lt;/html&gt;
The URI used as a system identifier with the public identifier allows
the user agent to download the DTD and entity sets as needed.
--&gt;
&lt;!--================== Imported Names ====================================--&gt;
&lt;!-- Feature Switch for frameset documents --&gt;
&lt;!ENTITY <span class="entity">% HTML.Frameset</span> "IGNORE"&gt;
&lt;!ENTITY <span class="entity">% ContentType</span> "CDATA"
-- media type, as per [RFC2045]
--&gt;
&lt;!ENTITY <span class="entity">% ContentTypes</span> "CDATA"
-- comma-separated list of media types, as per [RFC2045]
--&gt;
&lt;!ENTITY <span class="entity">% Charset</span> "CDATA"
-- a character encoding, as per [RFC2045]
--&gt;
&lt;!ENTITY <span class="entity">% Charsets</span> "CDATA"
-- a space-separated list of character encodings, as per [RFC2045]
--&gt;
&lt;!ENTITY <span class="entity">% LanguageCode</span> "NAME"
-- a language code, as per [RFC1766]
--&gt;
&lt;!ENTITY <span class="entity">% Character</span> "CDATA"
-- a single character from [ISO10646]
--&gt;
&lt;!ENTITY <span class="entity">% LinkTypes</span> "CDATA"
-- space-separated list of link types
--&gt;
&lt;!ENTITY <span class="entity">% MediaDesc</span> "CDATA"
-- single or comma-separated list of media descriptors
--&gt;
&lt;!ENTITY <span class="entity">% URI</span> "CDATA"
-- a Uniform Resource Identifier,
see [URI]
--&gt;
&lt;!ENTITY <span class="entity">% Datetime</span> "CDATA" -- date and time information. ISO date format --&gt;
&lt;!ENTITY <span class="entity">% Script</span> "CDATA" -- script expression --&gt;
&lt;!ENTITY <span class="entity">% StyleSheet</span> "CDATA" -- style sheet data --&gt;
&lt;!ENTITY <span class="entity">% FrameTarget</span> "CDATA" -- render in this frame --&gt;
&lt;!ENTITY <span class="entity">% Text</span> "CDATA"&gt;
&lt;!-- Parameter Entities --&gt;
&lt;!ENTITY <span class="entity">% head.misc</span> "SCRIPT|STYLE|META|LINK|OBJECT" -- repeatable head elements --&gt;
&lt;!ENTITY <span class="entity">% heading</span> "H1|H2|H3|H4|H5|H6"&gt;
&lt;!ENTITY <span class="entity">% list</span> "UL | OL | DIR | MENU"&gt;
&lt;!ENTITY <span class="entity">% preformatted</span> "PRE"&gt;
&lt;!ENTITY <span class="entity">% Color</span> "CDATA" -- a color using sRGB: #RRGGBB as Hex values --&gt;
&lt;!-- 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
--&gt;
&lt;!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 --
"&gt;
&lt;!--================ Character mnemonic entities =========================--&gt;
&lt;!ENTITY <span class="entity">% HTMLlat1</span> PUBLIC
"-//W3C//ENTITIES Latin1//EN//HTML"
"http://www.w3.org/TR/html401/HTMLlat1.ent"&gt;
%HTMLlat1;
&lt;!ENTITY <span class="entity">% HTMLsymbol</span> PUBLIC
"-//W3C//ENTITIES Symbols//EN//HTML"
"http://www.w3.org/TR/html401/HTMLsymbol.ent"&gt;
%HTMLsymbol;
&lt;!ENTITY <span class="entity">% HTMLspecial</span> PUBLIC
"-//W3C//ENTITIES Special//EN//HTML"
"http://www.w3.org/TR/html401/HTMLspecial.ent"&gt;
%HTMLspecial;
&lt;!--=================== Generic Attributes ===============================--&gt;
&lt;!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 --"
&gt;
&lt;!ENTITY <span class="entity">% i18n</span>
"lang %LanguageCode; #IMPLIED -- language code --
dir (ltr|rtl) #IMPLIED -- direction for weak/neutral text --"
&gt;
&lt;!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 --"
&gt;
&lt;!ENTITY <span class="entity">% CURIE</span> "CDATA" &gt;
&lt;!ENTITY <span class="entity">% CURIEs</span> "CDATA" &gt;
&lt;!ENTITY <span class="entity">% CURIEorURI</span> "CDATA" &gt;
&lt;!ENTITY <span class="entity">% CURIEorURIs</span> "CDATA" &gt;
&lt;!ENTITY <span class="entity">% SafeCURIEorCURIEorURI</span> "CDATA" &gt;
&lt;!ENTITY <span class="entity">% SafeCURIEorCURIEorURIs</span> "CDATA" &gt;
&lt;!ENTITY <span class="entity">% TERMorCURIEorAbsURI</span> "CDATA" &gt;
&lt;!ENTITY <span class="entity">% TERMorCURIEorAbsURIs</span> "CDATA" &gt;
&lt;!ENTITY <span class="entity">% URIs</span> "CDATA" &gt;
&lt;!ENTITY <span class="entity">% metainformation</span>
"about %SafeCURIEorCURIEorURI; #IMPLIED
content CDATA #IMPLIED
datatype %TERMorCURIEorAbsURI; #IMPLIED
typeof %TERMorCURIEorAbsURIs; #IMPLIED
prefix CDATA #IMPLIED
profile %URIs; #IMPLIED
property %TERMorCURIEorAbsURIs; #IMPLIED
href %URI; #IMPLIED
rel %TERMorCURIEorAbsURIs; #IMPLIED
rev %TERMorCURIEorAbsURIs; #IMPLIED
resource %SafeCURIEorCURIEorURI; #IMPLIED
vocab %URI; #IMPLIED"
&gt;
&lt;!-- Reserved Feature Switch --&gt;
&lt;!ENTITY <span class="entity">% HTML.Reserved</span> "IGNORE"&gt;
&lt;!-- The following attributes are reserved for possible future use --&gt;
&lt;![ %HTML.Reserved; [
&lt;!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 --"
&gt;
]]&gt;
&lt;!ENTITY <span class="entity">% reserved</span> ""&gt;
&lt;!ENTITY <span class="entity">% attrs</span> "%coreattrs; %i18n; %events; %metainformation;"&gt;
&lt;!ENTITY <span class="entity">% align</span> "align (left|center|right|justify) #IMPLIED"
-- default is left for ltr paragraphs, right for rtl --
&gt;
&lt;!--=================== Text Markup ======================================--&gt;
&lt;!ENTITY <span class="entity">% fontstyle</span>
"TT | I | B | U | S | STRIKE | BIG | SMALL"&gt;
&lt;!ENTITY <span class="entity">% phrase</span> "EM | STRONG | DFN | CODE |
SAMP | KBD | VAR | CITE | ABBR | ACRONYM" &gt;
&lt;!ENTITY <span class="entity">% special</span>
"A | IMG | APPLET | OBJECT | FONT | BASEFONT | BR | SCRIPT |
MAP | Q | SUB | SUP | SPAN | BDO | IFRAME"&gt;
&lt;!ENTITY <span class="entity">% formctrl</span> "INPUT | SELECT | TEXTAREA | LABEL | BUTTON"&gt;
&lt;!-- %inline; covers inline or "text-level" elements --&gt;
&lt;!ENTITY <span class="entity">% inline</span> "#PCDATA | %fontstyle; | %phrase; | %special; | %formctrl; "&gt;
&lt;!ELEMENT <span class="element">(%fontstyle;|%phrase;)</span> - - (%inline;)*&gt;
&lt;!ATTLIST (%fontstyle;|%phrase;)
%attrs; -- %coreattrs, %i18n, %events --
&gt;
&lt;!ELEMENT <span class="element">(SUB|SUP)</span> - - (%inline;)* -- subscript, superscript --&gt;
&lt;!ATTLIST (SUB|SUP)
%attrs; -- %coreattrs, %i18n, %events --
&gt;
&lt;!ELEMENT <span class="element">SPAN</span> - - (%inline;)* -- generic language/style container --&gt;
&lt;!ATTLIST SPAN
%attrs; -- %coreattrs, %i18n, %events --
%reserved; -- reserved for possible future use --
&gt;
&lt;!ELEMENT <span class="element">BDO</span> - - (%inline;)* -- I18N BiDi over-ride --&gt;
&lt;!ATTLIST BDO
%coreattrs; -- id, class, style, title --
%metainformation; -- metadata attributes --
lang %LanguageCode; #IMPLIED -- language code --
dir (ltr|rtl) #<em class="rfc2119" title="required">required</em> -- directionality --
&gt;
&lt;!ELEMENT <span class="element">BASEFONT</span> - O EMPTY -- base font size --&gt;
&lt;!ATTLIST BASEFONT
%metainformation; -- metadata attributes --
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 --
&gt;
&lt;!ELEMENT <span class="element">FONT</span> - - (%inline;)* -- local change to font --&gt;
&lt;!ATTLIST FONT
%coreattrs; -- id, class, style, title --
%metainformation; -- metadata attributes --
%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 --
&gt;
&lt;!ELEMENT <span class="element">BR</span> - O EMPTY -- forced line break --&gt;
&lt;!ATTLIST BR
%coreattrs; -- id, class, style, title --
%metainformation; -- metadata attributes --
clear (left|all|right|none) none -- control of text flow --
&gt;
&lt;!--================== HTML content models ===============================--&gt;
&lt;!--
HTML has two basic content models:
%inline; character level elements and text strings
%block; block-like elements e.g. paragraphs and lists
--&gt;
&lt;!ENTITY <span class="entity">% block</span>
"P | %heading; | %list; | %preformatted; | DL | DIV | CENTER |
NOSCRIPT | NOFRAMES | BLOCKQUOTE | FORM | ISINDEX | HR |
TABLE | FIELDSET | ADDRESS"&gt;
&lt;!ENTITY <span class="entity">% flow</span> "%block; | %inline;"&gt;
&lt;!--=================== Document Body ====================================--&gt;
&lt;!ELEMENT <span class="element">BODY</span> O O (%flow;)* +(INS|DEL) -- document body --&gt;
&lt;!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 --
&gt;
&lt;!ELEMENT <span class="element">ADDRESS</span> - - ((%inline;)|P)* -- information on author --&gt;
&lt;!ATTLIST ADDRESS
%attrs; -- %coreattrs, %i18n, %events --
&gt;
&lt;!ELEMENT <span class="element">DIV</span> - - (%flow;)* -- generic language/style container --&gt;
&lt;!ATTLIST DIV
%attrs; -- %coreattrs, %i18n, %events --
%align; -- align, text alignment --
%reserved; -- reserved for possible future use --
&gt;
&lt;!ELEMENT <span class="element">CENTER</span> - - (%flow;)* -- shorthand for DIV align=center --&gt;
&lt;!ATTLIST CENTER
%attrs; -- %coreattrs, %i18n, %events --
&gt;
&lt;!--================== The Anchor Element ================================--&gt;
&lt;!ENTITY <span class="entity">% Shape</span> "(rect|circle|poly|default)"&gt;
&lt;!ENTITY <span class="entity">% Coords</span> "CDATA" -- comma-separated list of lengths --&gt;
&lt;!ELEMENT <span class="element">A</span> - - (%inline;)* -(A) -- anchor --&gt;
&lt;!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 --
&gt;
&lt;!--================== Client-side image maps ============================--&gt;
&lt;!-- These can be placed in the same document or grouped in a
separate document although this isn't yet widely supported --&gt;
&lt;!ELEMENT <span class="element">MAP</span> - - ((%block;) | AREA)+ -- client-side image map --&gt;
&lt;!ATTLIST MAP
%attrs; -- %coreattrs, %i18n, %events --
name CDATA #<em class="rfc2119" title="required">required</em> -- for reference by usemap --
&gt;
&lt;!ELEMENT <span class="element">AREA</span> - O EMPTY -- client-side image map area --&gt;
&lt;!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 --
&gt;
&lt;!--================== The LINK Element ==================================--&gt;
&lt;!--
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)
--&gt;
&lt;!ELEMENT <span class="element">LINK</span> - O EMPTY -- a media-independent link --&gt;
&lt;!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 --
&gt;
&lt;!--=================== Images ===========================================--&gt;
&lt;!-- Length defined in strict DTD for cellpadding/cellspacing --&gt;
&lt;!ENTITY <span class="entity">% Length</span> "CDATA" -- nn for pixels or nn% for percentage length --&gt;
&lt;!ENTITY <span class="entity">% MultiLength</span> "CDATA" -- pixel, percentage, or relative --&gt;
&lt;![ %HTML.Frameset; [
&lt;!ENTITY <span class="entity">% MultiLengths</span> "CDATA" -- comma-separated list of MultiLength --&gt;
]]&gt;
&lt;!ENTITY <span class="entity">% Pixels</span> "CDATA" -- integer representing length in pixels --&gt;
&lt;!ENTITY <span class="entity">% IAlign</span> "(top|middle|bottom|left|right)" -- center? --&gt;
&lt;!-- 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 --&gt;
&lt;!ELEMENT <span class="element">IMG</span> - O EMPTY -- Embedded image --&gt;
&lt;!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 --
&gt;
&lt;!-- USEMAP points to a MAP element which may be in this document
or an external document, although the latter is not widely supported --&gt;
&lt;!--==================== OBJECT ======================================--&gt;
&lt;!--
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 ...
--&gt;
&lt;!ELEMENT <span class="element">OBJECT</span> - - (PARAM | %flow;)*
-- generic embedded object --&gt;
&lt;!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 --
&gt;
&lt;!ELEMENT <span class="element">PARAM</span> - O EMPTY -- named property value --&gt;
&lt;!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 --
&gt;
&lt;!--=================== Java APPLET ==================================--&gt;
&lt;!--
One of code or object attributes must be present.
Place PARAM elements before other content.
--&gt;
&lt;!ELEMENT <span class="element">APPLET</span> - - (PARAM | %flow;)* -- Java applet --&gt;
&lt;!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 --
&gt;
&lt;!--=================== Horizontal Rule ==================================--&gt;
&lt;!ELEMENT <span class="element">HR</span> - O EMPTY -- horizontal rule --&gt;
&lt;!ATTLIST HR
%attrs; -- %coreattrs, %i18n, %events --
align (left|center|right) #IMPLIED
noshade (noshade) #IMPLIED
size %Pixels; #IMPLIED
width %Length; #IMPLIED
&gt;
&lt;!--=================== Paragraphs =======================================--&gt;
&lt;!ELEMENT <span class="element">P</span> - O (%inline;)* -- paragraph --&gt;
&lt;!ATTLIST P
%attrs; -- %coreattrs, %i18n, %events --
%align; -- align, text alignment --
&gt;
&lt;!--=================== Headings =========================================--&gt;
&lt;!--
There are six levels of headings from H1 (the most important)
to H6 (the least important).
--&gt;
&lt;!ELEMENT <span class="element">(%heading;)</span> - - (%inline;)* -- heading --&gt;
&lt;!ATTLIST (%heading;)
%attrs; -- %coreattrs, %i18n, %events --
%align; -- align, text alignment --
&gt;
&lt;!--=================== Preformatted Text ================================--&gt;
&lt;!-- excludes markup for images and changes in font size --&gt;
&lt;!ENTITY <span class="entity">% pre.exclusion</span> "IMG|OBJECT|APPLET|BIG|SMALL|SUB|SUP|FONT|BASEFONT"&gt;
&lt;!ELEMENT <span class="element">PRE</span> - - (%inline;)* -(%pre.exclusion;) -- preformatted text --&gt;
&lt;!ATTLIST PRE
%attrs; -- %coreattrs, %i18n, %events --
width NUMBER #IMPLIED
&gt;
&lt;!--===================== Inline Quotes ==================================--&gt;
&lt;!ELEMENT <span class="element">Q</span> - - (%inline;)* -- short inline quotation --&gt;
&lt;!ATTLIST Q
%attrs; -- %coreattrs, %i18n, %events --
cite %URI; #IMPLIED -- URI for source document or msg --
&gt;
&lt;!--=================== Block-like Quotes ================================--&gt;
&lt;!ELEMENT <span class="element">BLOCKQUOTE</span> - - (%flow;)* -- long quotation --&gt;
&lt;!ATTLIST BLOCKQUOTE
%attrs; -- %coreattrs, %i18n, %events --
cite %URI; #IMPLIED -- URI for source document or msg --
&gt;
&lt;!--=================== Inserted/Deleted Text ============================--&gt;
&lt;!-- INS/DEL are handled by inclusion on BODY --&gt;
&lt;!ELEMENT <span class="element">(INS|DEL)</span> - - (%flow;)* -- inserted text, deleted text --&gt;
&lt;!ATTLIST (INS|DEL)
%attrs; -- %coreattrs, %i18n, %events --
cite %URI; #IMPLIED -- info on reason for change --
datetime %Datetime; #IMPLIED -- date and time of change --
&gt;
&lt;!--=================== Lists ============================================--&gt;
&lt;!-- definition lists - DT for term, DD for its definition --&gt;
&lt;!ELEMENT <span class="element">DL</span> - - (DT|DD)+ -- definition list --&gt;
&lt;!ATTLIST DL
%attrs; -- %coreattrs, %i18n, %events --
compact (compact) #IMPLIED -- reduced interitem spacing --
&gt;
&lt;!ELEMENT <span class="element">DT</span> - O (%inline;)* -- definition term --&gt;
&lt;!ELEMENT <span class="element">DD</span> - O (%flow;)* -- definition description --&gt;
&lt;!ATTLIST (DT|DD)
%attrs; -- %coreattrs, %i18n, %events --
&gt;
&lt;!-- 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.
--&gt;
&lt;!ENTITY <span class="entity">% OLStyle</span> "CDATA" -- constrained to: "(1|a|A|i|I)" --&gt;
&lt;!ELEMENT <span class="element">OL</span> - - (LI)+ -- ordered list --&gt;
&lt;!ATTLIST OL
%attrs; -- %coreattrs, %i18n, %events --
type %OLStyle; #IMPLIED -- numbering style --
compact (compact) #IMPLIED -- reduced interitem spacing --
start NUMBER #IMPLIED -- starting sequence number --
&gt;
&lt;!-- Unordered Lists (UL) bullet styles --&gt;
&lt;!ENTITY <span class="entity">% ULStyle</span> "(disc|square|circle)"&gt;
&lt;!ELEMENT <span class="element">UL</span> - - (LI)+ -- unordered list --&gt;
&lt;!ATTLIST UL
%attrs; -- %coreattrs, %i18n, %events --
type %ULStyle; #IMPLIED -- bullet style --
compact (compact) #IMPLIED -- reduced interitem spacing --
&gt;
&lt;!ELEMENT <span class="element">(DIR|MENU)</span> - - (LI)+ -(%block;) -- directory list, menu list --&gt;
&lt;!ATTLIST DIR
%attrs; -- %coreattrs, %i18n, %events --
compact (compact) #IMPLIED -- reduced interitem spacing --
&gt;
&lt;!ATTLIST MENU
%attrs; -- %coreattrs, %i18n, %events --
compact (compact) #IMPLIED -- reduced interitem spacing --
&gt;
&lt;!ENTITY <span class="entity">% LIStyle</span> "CDATA" -- constrained to: "(%ULStyle;|%OLStyle;)" --&gt;
&lt;!ELEMENT <span class="element">LI</span> - O (%flow;)* -- list item --&gt;
&lt;!ATTLIST LI
%attrs; -- %coreattrs, %i18n, %events --
type %LIStyle; #IMPLIED -- list item style --
value NUMBER #IMPLIED -- reset sequence number --
&gt;
&lt;!--================ Forms ===============================================--&gt;
&lt;!ELEMENT <span class="element">FORM</span> - - (%flow;)* -(FORM) -- interactive form --&gt;
&lt;!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 --
&gt;
&lt;!-- Each label must not contain more than ONE field --&gt;
&lt;!ELEMENT <span class="element">LABEL</span> - - (%inline;)* -(LABEL) -- form field label text --&gt;
&lt;!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 --
&gt;
&lt;!ENTITY <span class="entity">% InputType</span>
"(TEXT | PASSWORD | CHECKBOX |
RADIO | SUBMIT | RESET |
FILE | HIDDEN | IMAGE | BUTTON)"
&gt;
&lt;!-- attribute name required for all but submit and reset --&gt;
&lt;!ELEMENT <span class="element">INPUT</span> - O EMPTY -- form control --&gt;
&lt;!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 --
&gt;
&lt;!ELEMENT <span class="element">SELECT</span> - - (OPTGROUP|OPTION)+ -- option selector --&gt;
&lt;!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 --
&gt;
&lt;!ELEMENT <span class="element">OPTGROUP</span> - - (OPTION)+ -- option group --&gt;
&lt;!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 --
&gt;
&lt;!ELEMENT <span class="element">OPTION</span> - O (#PCDATA) -- selectable choice --&gt;
&lt;!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 --
&gt;
&lt;!ELEMENT <span class="element">TEXTAREA</span> - - (#PCDATA) -- multi-line text field --&gt;
&lt;!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 --
&gt;
&lt;!--
#PCDATA is to solve the mixed content problem,
per specification only whitespace is allowed there!
--&gt;
&lt;!ELEMENT <span class="element">FIELDSET</span> - - (#PCDATA,LEGEND,(%flow;)*) -- form control group --&gt;
&lt;!ATTLIST FIELDSET
%attrs; -- %coreattrs, %i18n, %events --
&gt;
&lt;!ELEMENT <span class="element">LEGEND</span> - - (%inline;)* -- fieldset legend --&gt;
&lt;!ENTITY <span class="entity">% LAlign</span> "(top|bottom|left|right)"&gt;
&lt;!ATTLIST LEGEND
%attrs; -- %coreattrs, %i18n, %events --
accesskey %Character; #IMPLIED -- accessibility key character --
align %LAlign; #IMPLIED -- relative to fieldset --
&gt;
&lt;!ELEMENT <span class="element">BUTTON</span> - -
(%flow;)* -(A|%formctrl;|FORM|ISINDEX|FIELDSET|IFRAME)
-- push button --&gt;
&lt;!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 --
&gt;
&lt;!--======================= Tables =======================================--&gt;
&lt;!-- IETF HTML table standard, see [RFC1942] --&gt;
&lt;!--
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
&lt;TABLE BORDER&gt; which yields frame=border and border=implied
For &lt;TABLE BORDER=1&gt; 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.
--&gt;
&lt;!ENTITY <span class="entity">% TFrame</span> "(void|above|below|hsides|lhs|rhs|vsides|box|border)"&gt;
&lt;!--
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"
--&gt;
&lt;!ENTITY <span class="entity">% TRules</span> "(none | groups | rows | cols | all)"&gt;
&lt;!-- horizontal placement of table relative to document --&gt;
&lt;!ENTITY <span class="entity">% TAlign</span> "(left|center|right)"&gt;
&lt;!-- horizontal alignment attributes for cell contents --&gt;
&lt;!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 --"
&gt;
&lt;!-- vertical alignment attributes for cell contents --&gt;
&lt;!ENTITY <span class="entity">% cellvalign</span>
"valign (top|middle|bottom|baseline) #IMPLIED"
&gt;
&lt;!ELEMENT <span class="element">TABLE</span> - -
(CAPTION?, (COL*|COLGROUP*), THEAD?, TFOOT?, TBODY+)&gt;
&lt;!ELEMENT <span class="element">CAPTION</span> - - (%inline;)* -- table caption --&gt;
&lt;!ELEMENT <span class="element">THEAD</span> - O (TR)+ -- table header --&gt;
&lt;!ELEMENT <span class="element">TFOOT</span> - O (TR)+ -- table footer --&gt;
&lt;!ELEMENT <span class="element">TBODY</span> O O (TR)+ -- table body --&gt;
&lt;!ELEMENT <span class="element">COLGROUP</span> - O (COL)* -- table column group --&gt;
&lt;!ELEMENT <span class="element">COL</span> - O EMPTY -- table column --&gt;
&lt;!ELEMENT <span class="element">TR</span> - O (TH|TD)+ -- table row --&gt;
&lt;!ELEMENT <span class="element">(TH|TD)</span> - O (%flow;)* -- table header cell, table data cell--&gt;
&lt;!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 --
&gt;
&lt;!ENTITY <span class="entity">% CAlign</span> "(top|bottom|left|right)"&gt;
&lt;!ATTLIST CAPTION
%attrs; -- %coreattrs, %i18n, %events --
align %CAlign; #IMPLIED -- relative to table --
&gt;
&lt;!--
COLGROUP groups a set of COL elements. It allows you to group
several semantically related columns together.
--&gt;
&lt;!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 --
&gt;
&lt;!--
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.
--&gt;
&lt;!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 --
&gt;
&lt;!--
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.
--&gt;
&lt;!ATTLIST (THEAD|TBODY|TFOOT) -- table section --
%attrs; -- %coreattrs, %i18n, %events --
%cellhalign; -- horizontal alignment in cells --
%cellvalign; -- vertical alignment in cells --
&gt;
&lt;!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 --
&gt;
&lt;!-- Scope is simpler than headers attribute for common tables --&gt;
&lt;!ENTITY <span class="entity">% Scope</span> "(row|col|rowgroup|colgroup)"&gt;
&lt;!-- TH is for headers, TD for data, but for cells acting as both use TD --&gt;
&lt;!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 --
&gt;
&lt;!--================== Document Frames ===================================--&gt;
&lt;!--
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.
--&gt;
&lt;![ %HTML.Frameset; [
&lt;!ELEMENT <span class="element">FRAMESET</span> - - ((FRAMESET|FRAME)+ &amp; NOFRAMES?) -- window subdivision--&gt;
&lt;!ATTLIST FRAMESET
%coreattrs; -- id, class, style, title --
%metainformation; -- metadata attributes --
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 --
&gt;
]]&gt;
&lt;![ %HTML.Frameset; [
&lt;!-- reserved frame names start with "_" otherwise starts with letter --&gt;
&lt;!ELEMENT <span class="element">FRAME</span> - O EMPTY -- subwindow --&gt;
&lt;!ATTLIST FRAME
%coreattrs; -- id, class, style, title --
%metainformation; -- metadata attributes --
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 --
&gt;
]]&gt;
&lt;!ELEMENT <span class="element">IFRAME</span> - - (%flow;)* -- inline subwindow --&gt;
&lt;!ATTLIST IFRAME
%coreattrs; -- id, class, style, title --
%metainformation; -- metadata attributes --
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 --
&gt;
&lt;![ %HTML.Frameset; [
&lt;!ENTITY <span class="entity">% noframes.content</span> "(BODY) -(NOFRAMES)"&gt;
]]&gt;
&lt;!ENTITY <span class="entity">% noframes.content</span> "(%flow;)*"&gt;
&lt;!ELEMENT <span class="element">NOFRAMES</span> - - %noframes.content;
-- alternate content container for non frame-based rendering --&gt;
&lt;!ATTLIST NOFRAMES
%attrs; -- %coreattrs, %i18n, %events --
&gt;
&lt;!--================ Document Head =======================================--&gt;
&lt;!-- %head.misc; defined earlier on as "SCRIPT|STYLE|META|LINK|OBJECT" --&gt;
&lt;!ENTITY <span class="entity">% head.content</span> "TITLE &amp; ISINDEX? &amp; BASE?"&gt;
&lt;!ELEMENT <span class="element">HEAD</span> O O (%head.content;) +(%head.misc;) -- document head --&gt;
&lt;!ATTLIST HEAD
%attrs;
&gt;
&lt;!-- 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.
--&gt;
&lt;!ELEMENT <span class="element">TITLE</span> - - (#PCDATA) -(%head.misc;) -- document title --&gt;
&lt;!ATTLIST TITLE %attrs&gt;
&lt;!ELEMENT <span class="element">ISINDEX</span> - O EMPTY -- single line prompt --&gt;
&lt;!ATTLIST ISINDEX
%coreattrs; -- id, class, style, title --
%i18n; -- lang, dir --
%metainformation; -- metadata attributes --
prompt %Text; #IMPLIED -- prompt message --&gt;
&lt;!ELEMENT <span class="element">BASE</span> - O EMPTY -- document base URI --&gt;
&lt;!ATTLIST BASE
%metainformation; -- metadata attributes --
href %URI; #IMPLIED -- URI that acts as base URI --
target %FrameTarget; #IMPLIED -- render in this frame --
&gt;
&lt;!ELEMENT <span class="element">META</span> - O EMPTY -- generic metainformation --&gt;
&lt;!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 --
&gt;
&lt;!ELEMENT <span class="element">STYLE</span> - - %StyleSheet -- style info --&gt;
&lt;!ATTLIST STYLE
%i18n; -- lang, dir, for use with title --
%metainformation; -- metadata attributes --
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 --
&gt;
&lt;!ELEMENT <span class="element">SCRIPT</span> - - %Script; -- script statements --&gt;
&lt;!ATTLIST SCRIPT
%metainformation; -- metadata attributes --
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 --
&gt;
&lt;!ELEMENT <span class="element">NOSCRIPT</span> - - (%flow;)*
-- alternate content container for non script-based rendering --&gt;
&lt;!ATTLIST NOSCRIPT
%attrs; -- %coreattrs, %i18n, %events --
&gt;
&lt;!--================ Document Structure ==================================--&gt;
&lt;![ %HTML.Frameset; [
&lt;!ENTITY <span class="entity">% html.content</span> "HEAD, FRAMESET"&gt;
]]&gt;
&lt;!ENTITY <span class="entity">% html.content</span> "HEAD, BODY"&gt;
&lt;!ELEMENT <span class="element">HTML</span> O O (%html.content;) -- document root element --&gt;
&lt;!ATTLIST HTML
%attrs;
&gt;
</pre></div>
</div>
</div>
<div class="appendix section" id="about-this-document" typeof="bibo:Chapter" about="#about-this-document">
<!-- OddPage -->
<h2><span class="secno">B. </span>About this Document</h2>
<div class="informative section" id="history" typeof="bibo:Chapter" about="#history">
<h3><span class="secno">B.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 W3C, later published as an official W3C 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 [<cite><a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a></cite>], and <em>thin</em>
specifications that layer above RDFa Core 1.1. The XHTML+RDFa 1.1 specification
[<cite><a class="bibref" rel="biblioentry" href="#bib-XHTML-RDFA">XHTML-RDFA</a></cite>] 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" typeof="bibo:Chapter" about="#change-history">
<h3><span class="secno">B.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 [<cite><a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a></cite>],
instead of XHTML+RDFa 1.0 [<cite><a class="bibref" rel="biblioentry" href="#bib-RDFA-SYNTAX">RDFA-SYNTAX</a></cite>], inclusion of the HTML Default
Vocabulary Terms, inclusion of a HTML 4.01 + RDFa 1.1 DTD for validation purposes.</p>
<p>2010-06-24: Inheritance of basic processing rules from RDFa 1.1 [<cite><a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a></cite>],
instead of XHTML+RDFa 1.0 [<cite><a class="bibref" rel="biblioentry" href="#bib-RDFA-SYNTAX">RDFA-SYNTAX</a></cite>], inclusion of the HTML Default
Vocabulary Terms, added HTML 4.01 + RDFa 1.1 DTD for validation purposes,
added normative definition of @version attribute.</p>
<p>2010-10-19: Removal of @version attribute, migrated HTML Vocabulary Terms to
RDFa Profile document, added statement to send comments to the HTML WG bug tracker.
</p>
<p>2011-01-11: Removed decentralized extensibility issue markers, added
DOM Level 1 prefix mapping extraction algorithm.
</p>
<p>2011-04-05: Moved all xmlns: rules into a section titled Backwards
Compatibility and brought spec in-line with latest RDFa Core 1.1 spec.
</p>
<p>2011-05-12: Generated Last Call document, no substatitive changes.
</p>
</div>
<div class="informative section" id="acknowledgments" typeof="bibo:Chapter" about="#acknowledgments">
<h3><span class="secno">B.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, Benjamin Adrian, Mark Birbeck, Ivan Herman (staff contact), Toby Inkster, Shane McCarron, Knud Möller, Steven Pemberton, Nathan Rixham, Manu Sporny (chair), Thomas Steiner, Ted Thibodeau
</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" typeof="bibo:Chapter" about="#references">
<!-- OddPage -->
<h2><span class="secno">C. </span>References</h2><div id="normative-references" typeof="bibo:Chapter" about="#normative-references" class="section"><h3><span class="secno">C.1 </span>Normative references</h3><dl class="bibliography" about=""><dt id="bib-DOM-LEVEL-1">[DOM-LEVEL-1]</dt><dd rel="dcterms:requires">Vidur Apparao; et al. <a href="http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/"><cite>Document Object Model (DOM) Level 1.</cite></a> 1 October 1998. W3C Recommendation. URL: <a href="http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/">http://www.w3.org/TR/1998/REC-DOM-Level-1-19981001/</a>
</dd><dt id="bib-DOM-LEVEL-2-CORE">[DOM-LEVEL-2-CORE]</dt><dd rel="dcterms:requires">Arnaud Le Hors; et al. <a href="http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/"><cite>Document Object Model (DOM) Level 2 Core Specification.</cite></a> 13 November 2000. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/">http://www.w3.org/TR/2000/REC-DOM-Level-2-Core-20001113/</a>
</dd><dt id="bib-HTML5">[HTML5]</dt><dd rel="dcterms:requires">Ian Hickson; David Hyatt. <a href="http://www.w3.org/TR/2010/WD-html5-20100304/"><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-20100304/">http://www.w3.org/TR/2010/WD-html5-20100304/</a>
</dd><dt id="bib-RDFA-CORE">[RDFA-CORE]</dt><dd rel="dcterms:requires">Shane McCarron; et al. <a href="http://www.w3.org/TR/2011/WD-rdfa-core-20110331"><cite>RDFa Core 1.1: Syntax and processing rules for embedding RDF through attributes.</cite></a> 31 March 2011. W3C Working Draft. URL: <a href="http://www.w3.org/TR/2011/WD-rdfa-core-20110331">http://www.w3.org/TR/2011/WD-rdfa-core-20110331</a>
</dd><dt id="bib-RFC2119">[RFC2119]</dt><dd rel="dcterms:requires">S. Bradner. <a href="http://www.ietf.org/rfc/rfc2119.txt"><cite>Key words for use in RFCs to Indicate Requirement Levels.</cite></a> March 1997. 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 rel="dcterms:requires">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 rel="dcterms:requires">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" typeof="bibo:Chapter" about="#informative-references" class="section"><h3><span class="secno">C.2 </span>Informative references</h3><dl class="bibliography" about=""><dt id="bib-RDFA-SYNTAX">[RDFA-SYNTAX]</dt><dd rel="dcterms:references">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 rel="dcterms:references">Shane McCarron; et. al. <a href="http://www.w3.org/TR/2011/WD-xhtml-rdfa-20110331"><cite>XHTML+RDFa 1.1.</cite></a> 31 March 2011. W3C Working Draft. URL: <a href="http://www.w3.org/TR/2011/WD-xhtml-rdfa-20110331">http://www.w3.org/TR/2011/WD-xhtml-rdfa-20110331</a>
</dd></dl></div></div></body></html>