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.
 
 
 
 
 
 

866 lines
40 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>Role Attribute 1.0</title>
<meta content="text/html;charset=utf-8" http-equiv="Content-Type" name="charset" />
<!--
=== 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,
-->
<!-- <script src='/ReSpec.js/js/respec.js' class='remove'></script> -->
<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: medium 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 height="48" width="72" alt="W3C" src="http://www.w3.org/Icons/w3c_home"/></a></p><h1 id="title" class="title" property="dcterms:title">Role Attribute 1.0</h1><h2 id="subtitle" property="bibo:subtitle">An attribute to support the role classification of elements</h2><h2 content="2011-01-13T05:00:00+0000" datatype="xsd:dateTime" property="dcterms:issued" id="w3c-working-draft-13-january-2011">W3C Working Draft 13 January 2011</h2><dl><dt>This version:</dt><dd><a href="http://www.w3.org/TR/2011/WD-role-attribute-20110113/">http://www.w3.org/TR/2011/WD-role-attribute-20110113/</a></dd><dt>Latest published version:</dt><dd><a href="http://www.w3.org/TR/role-attribute/">http://www.w3.org/TR/role-attribute/</a></dd><dt>Previous version:</dt><dd><a href="http://www.w3.org/TR/2010/WD-role-attribute-20100916/" rel="dcterms:replaces">http://www.w3.org/TR/2010/WD-role-attribute-20100916/</a></dd><dt>Editor:</dt><dd rel="bibo:editor"><span typeof="foaf:Person"><a href="http://blog.halindrome.com" content="Shane McCarron" property="foaf:name" rel="foaf:homepage">Shane McCarron</a>, <a href="http://www.aptest.com" rel="foaf:workplaceHomepage">Applied Testing and Technology, Inc.</a> <a href="mailto:shane@aptest.com" rel="foaf:mbox">shane@aptest.com</a> </span>
</dd>
<dt>Authors:</dt><dd rel="dcterms:contributor"><span typeof="foaf:Person"><a href="mailto:ben@adida.net" content="Ben Adida" property="foaf:name" rel="foaf:homepage">Ben Adida</a>, <a href="http://creativecommons.org" rel="foaf:workplaceHomepage">Creative Commons</a></span>
</dd>
<dd rel="dcterms:contributor"><span typeof="foaf:Person"><a href="mailto:mark.birbeck@webBackplane.com" content="Mark Birbeck" property="foaf:name" rel="foaf:homepage">Mark Birbeck</a>, <a href="http://webBackplane.com" rel="foaf:workplaceHomepage">webBackplane</a></span>
</dd>
<dd rel="dcterms:contributor"><span typeof="foaf:Person"><a href="mailto:raman@google.com" content="T. V. Raman" property="foaf:name" rel="foaf:homepage">T. V. Raman</a>, <a href="http://www.google.com" rel="foaf:workplaceHomepage">Google, Inc.</a></span>
</dd>
<dd rel="dcterms:contributor"><span typeof="foaf:Person"><a href="mailto:schwer@us.ibm.com" content="Richard Schwerdtfeger" property="foaf:name" rel="foaf:homepage">Richard Schwerdtfeger</a>, <a href="http://www.ibm.com" rel="foaf:workplaceHomepage">IBM Corporation</a></span>
</dd>
</dl><p class="copyright"><a href="http://www.w3.org/Consortium/Legal/ipr-notice#Copyright" rel="license">Copyright</a> © 2006-2011 <span rel="dcterms:publisher"><span typeof="foaf:Organization"><a href="http://www.w3.org/" content="World Wide Web Consotrium" property="foaf:name" rel="foaf:homepage"><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>The Role Attribute defined in this specification allows the author to annotate markup languages with machine-extractable semantic information about the purpose of an element. Use cases include accessibility, device adaptation, server-side processing, and complex data description. This attribute can be integrated into any markup language. In particular, schema
implementations are provided to facilitate with languages
based upon XHTML Modularization [<cite><a class="bibref" rel="biblioentry" href="#bib-XHTML-MODULARIZATION11-2e">XHTML-MODULARIZATION11-2e</a></cite>].
</p>
</div><div class="introductory section" id="sotd" 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 is a <a href="http://www.w3.org/2005/10/Process-20051014/tr#last-call">Last
Call Working Draft</a> by the <a href="http://www.w3.org/WAI/PF/">Protocols &amp; Formats
Working Group</a> of the <a href="http://www.w3.org/WAI/">Web Accessibility
Initiative</a>. This version incorporates changes in response to public
comments received on the previous version. A <a href="http://www.w3.org/WAI/PF/role-attribute/change-history">history
of changes to Role Attribute 1.0</a> is available.</p>
<p>Feedback on the information provided here is essential to the ultimate success
of the Role attribute. The PFWG asks in particular:</p>
<ul>
<li> Are the use cases and features of this attribute clear?</li>
<li>Is the relationship between the Role attribute and RDFa clear?</li>
<li>Is it clear how to take advantage of the role attribute in host languages?</li>
</ul>
<p>Start with the <a href="http://www.w3.org/WAI/PF/comments/instructions">instructions
for commenting</a> page to submit comments (preferred), or send email to <a href="mailto:public-pfwg-comments@w3.org">public-pfwg-comments@w3.org</a> (<a href="http://lists.w3.org/Archives/Public/public-pfwg-comments/">comment
archive</a>). Comments should be made by <strong>25 February 2011</strong>.
In-progress updates to the document may be viewed in the <a href="/WAI/PF/role-attribute/">publicly
visible editors' draft</a>.</p>
<p>This document was published by the <a href="http://www.w3.org/WAI/PF/">Protocols and Formats 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 send them to <a href="mailto:public-pfwg-comments@w3.org">public-pfwg-comments@w3.org</a> (<a href="mailto:public-pfwg-comments-request@w3.org?subject=subscribe">subscribe</a>, <a href="http://lists.w3.org/Archives/Public/public-pfwg-comments/">archives</a>). The Last Call period ends 25 February 2011. All feedback is welcome.</p><p>Publication as a 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>This is a Last Call Working Draft and thus the Working Group has determined that this document has satisfied the relevant technical requirements and is sufficiently stable to advance through the Technical Recommendation process.</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 rel="disclosure" href="http://www.w3.org/2004/01/pp-impl/32212/status">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="#host-language-conformance" class="tocxref"><span class="secno">2.2 </span>Host Language Conformance</a></li></ul></li><li class="tocline"><a href="#s_role_module_attributes" class="tocxref"><span class="secno">3. </span>The Role Attribute</a><ul class="toc"><li class="tocline"><a href="#extending-the-collection-of-roles" class="tocxref"><span class="secno">3.1 </span>Extending the collection of roles</a></li></ul></li><li class="tocline"><a href="#using-role-in-conjunction-with-rdfa" class="tocxref"><span class="secno">A. </span>Using Role in conjunction with RDFa</a></li><li class="tocline"><a href="#xhtml-role-attribute-module" class="tocxref"><span class="secno">B. </span>XHTML Role Attribute Module</a><ul class="toc"><li class="tocline"><a href="#dtd-implementation" class="tocxref"><span class="secno">B.1 </span>DTD Implementation</a><ul class="toc"><li class="tocline"><a href="#qualified-names-module" class="tocxref"><span class="secno">B.1.1 </span>Qualified Names Module</a></li></ul></li><li class="tocline"><a href="#a_Schema_definition" class="tocxref"><span class="secno">B.2 </span>Schema Implementation</a><ul class="toc"><li class="tocline"><a href="#attributes-module" class="tocxref"><span class="secno">B.2.1 </span>Attributes Module</a></li></ul></li></ul></li><li class="tocline"><a href="#s_acks" class="tocxref"><span class="secno">C. </span>Acknowledgments</a></li><li class="tocline"><a href="#references" class="tocxref"><span class="secno">D. </span>References</a><ul class="toc"><li class="tocline"><a href="#normative-references" class="tocxref"><span class="secno">D.1 </span>Normative references</a></li><li class="tocline"><a href="#informative-references" class="tocxref"><span class="secno">D.2 </span>Informative references</a></li></ul></li></ul></div>
<div class="informative section" id="introduction" typeof="bibo:Chapter" about="#introduction">
<!-- OddPage -->
<h2 id="s_intro"><span class="secno">1. </span>Introduction</h2><p><em>This section is non-normative.</em></p>
<p>This document defines an attribute designed
be used to help improve the accessibility and semantic
markup of documents.
It has been developed in conjunction with the
accessibility community and other groups to make it easier to describe
the semantic meaning of document 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 id="docconf"><span class="secno">2.1 </span>Document Conformance</h3>
<p>The Role Attribute does not represent a stand-alone document type.
It is intended to
be integrated into other host languages such as HTML or XHTML.
A conforming Role Attribute document is a document that
requires only the facilities described as mandatory in this
specification and the facilities described as mandatory in its host language.
Such a document must meet all the following
criteria:</p>
<ol>
<li>
<p>The document <em class="rfc2119" title="must">must</em> conform to the constraints expressed in
its host language implementation.</p>
</li>
<li>
<p>If the host language <em>is</em> an XML [<cite><a class="bibref" rel="biblioentry" href="#bib-XML10-4e">XML10-4e</a></cite>]
markup language and is in the XHTML Namespace
<code>http://www.w3.org/1999/xhtml</code>), there are no
additional requirements.
If the host language is an XML markup language and <em>is not</em> in the XHTML namespace,
and the
host language does not incorporate this attribute in 'no namespace',
then
the document <em class="rfc2119" title="must">must</em> contain an XML namespace declaration for the Role Attribute Module namespace
[<cite><a class="bibref" rel="biblioentry" href="#bib-XML-NAMES11">XML-NAMES11</a></cite>].
The namespace for Role Attribute Module is
defined to be
<code>http://www.w3.org/1999/xhtml</code>.
An example start tag of a root element might look like:</p>
<pre class="example">
&lt;mylang xmlns="http://www.example.com/dtd/mylang"
xmlns:xh="http://www.w3.org/1999/xhtml" xml:lang="en" &gt;</pre>
</li>
</ol>
</div>
<div id="host-language-conformance" typeof="bibo:Chapter" about="#host-language-conformance" class="section">
<h3 id="hostconf"><span class="secno">2.2 </span>Host Language Conformance</h3>
<p>When the Role Attribute is included in a host language, all of the
facilities required in this specification <em class="rfc2119" title="must">must</em> be included in the host
language. In addition, the attribute defined in this
specification <em class="rfc2119" title="must">must</em> be included in the content model of the host
language.
</p>
</div>
</div>
<div id="s_role_module_attributes" typeof="bibo:Chapter" about="#s_role_module_attributes" class="section">
<!-- OddPage -->
<h2><span class="secno">3. </span>The Role Attribute</h2>
<p id="A_role">This specification defines the <code>role</code> attribute.
The <code>role</code> attribute takes as its value one or more
whitespace separated <code>TERMorCURIEorAbsURIs</code>
as defined in [<cite><a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a></cite>].
Each element of the value maps to a URI that corresponds to a vocabulary
term that <em class="rfc2119" title="should">should</em> be defined using RDF.</p>
<p class="note">The datatype used for <span class="aref">@role</span> permits the
use of a TERM, a CURIE, or a full URI. RDFa defines a TERM as an item
from a vocabulary, and defines how a vocabulary is constructed.
The default vocabulary for use with <span class="aref">@role</span> is
defined in [<cite><a class="bibref" rel="biblioentry" href="#bib-XHTML-VOCAB">XHTML-VOCAB</a></cite>].
A host language <em class="rfc2119" title="may">may</em> define a different default vocabulary.
</p>
<p class="note">The specific vocabulary terms
from the default vocabulary are not included in this document.
They are defined in [<cite><a class="bibref" rel="biblioentry" href="#bib-XHTML-VOCAB">XHTML-VOCAB</a></cite>] to ease maintenance. The terms
are drawn from [<cite><a class="bibref" rel="biblioentry" href="#bib-WAI-ARIA">WAI-ARIA</a></cite>] and from the original work on this document
by the XHTML2 Working Group.</p>
<p>The attribute describes the role(s) the current element plays in the
context of the document.
This can be used, for example, by
applications and assistive technologies to
determine the purpose of an element.
This could allow a user to make informed decisions on which actions may
be taken on an element and activate the selected action in a device
independent way. It could also be used as a mechanism for annotating portions
of a document in a domain specific way (e.g., a legal term taxonomy).
Although the role attribute may be used to add semantics to an element,
authors <em class="rfc2119" title="should">should</em> use elements with inherent semantics, such as <code>p</code>,
rather than layering
semantics on semantically neutral elements, such as <code>div role="paragraph"</code>.</p>
<p>The following is an example of a good, appropriate use of the role attribute:</p>
<pre class="example">
&lt;ul role="navigation"&gt;
&lt;li href="downloads"&gt;Downloads&lt;/li&gt;
&lt;li href="docs"&gt;Documentation&lt;/li&gt;
&lt;li href="news"&gt;News&lt;/li&gt;
&lt;/ul&gt;</pre>
<div id="extending-the-collection-of-roles" typeof="bibo:Chapter" about="#extending-the-collection-of-roles" class="section">
<h3><span class="secno">3.1 </span>Extending the collection of roles</h3>
<p>It is possible to define additional role values. Such values <em class="rfc2119" title="must">must</em>
be
defined in their own vocabulary.
The URI associated with that vocabulary <em class="rfc2119" title="should">should</em> resolve to a resource that
allows for the machine and human discovery of the definition of the roles in the
vocabulary. One format that achieves this
is the RDFa Profile as defined in [<cite><a class="bibref" rel="biblioentry" href="#bib-RDFA-CORE">RDFA-CORE</a></cite>].</p>
<p class="note">
If this attribute is used in conjunction with RDFa (see Appendix A), then
the vocabulary definition <em class="rfc2119" title="must">must</em> be the same as that required by
RDFa.</p>
</div>
</div>
<div class="appendix section" id="using-role-in-conjunction-with-rdfa" typeof="bibo:Chapter" about="#using-role-in-conjunction-with-rdfa">
<!-- OddPage -->
<h2><span class="secno">A. </span>Using Role in conjunction with RDFa</h2>
<p>If a Host Language contains the <span class="aref">@role</span> attribute, then an RDFa processor
processing a document written in that Host Language according to the
rules of that Host Language <em class="rfc2119" title="may">may</em> generate additional triples for role attributes. If these
additional triples are being generated, then they <em class="rfc2119" title="must">must</em> be generated as follows:</p>
<ul>
<li>If <span class="aref">@id</span> is present, it is used to supply the <em>subject</em> by concatenating the document's
'base', a fragment separator '#', and the value of <span class="aref">@id</span>.
Otherwise the <em>subject</em> is a unique newly created <code>bnode</code>.</li>
<li>The <em>predicate</em> is the term <code>role</code> in the vocabulary
defined at <code>http://www.w3.org/1999/xhtml/vocab</code>.</li>
<li>Each value of <span class="aref">@role</span> is an <em>object</em>, forming an
RDF triple with the subject and predicate defined above.</li>
</ul>
</div>
<div class="appendix section" id="xhtml-role-attribute-module" typeof="bibo:Chapter" about="#xhtml-role-attribute-module">
<!-- OddPage -->
<h2><span class="secno">B. </span>XHTML Role Attribute Module</h2>
<div id="dtd-implementation" typeof="bibo:Chapter" about="#dtd-implementation" class="section">
<h3 id="a_DTD_definition"><span class="secno">B.1 </span>DTD Implementation</h3>
<p>The DTD implementation of XHTML Role Attribute Module conforms to the requirements defined
in [<cite><a class="bibref" rel="biblioentry" href="#bib-XHTML-MODULARIZATION11-2e">XHTML-MODULARIZATION11-2e</a></cite>]. Consequently, it provides a Qualified
Names declaration module.</p>
<div id="qualified-names-module" typeof="bibo:Chapter" about="#qualified-names-module" class="section">
<h4 id="a_module_qname"><span class="secno">B.1.1 </span>Qualified Names Module</h4>
<p>Note that this module defines the parameter entity
<code>%xhtml-role-attrs.qname;</code>. This entity is intended to be used in
the attribute lists of elements in any host language that permits the use of
the role attribute on elements in its own namespace.
If a host language does not permit role in its namespace, then the host
language driver should set a parameter entity <code>%XHTML-ROLE.prefixed;</code>
to <code>INCLUDE</code> and a parameter entity <code>%XHTML-ROLE.prefix;</code>
to a value that is the prefix for the XHTML Role Attribute Module attribute.</p>
<div><pre class="dtd">
&lt;!-- ....................................................................... --&gt;
&lt;!-- XHTML Role Qname Module ............................................ --&gt;
&lt;!-- file: xhtml-role-qname-1.mod
This is XHTML Role - the Role Attribute Module for XHTML.
Copyright 2006 W3C (MIT, ERCIM, Keio), All Rights Reserved.
This DTD module is identified by the PUBLIC and SYSTEM identifiers:
PUBLIC "-//W3C//ENTITIES XHTML Role Attribute Qnames 1.0//EN"
SYSTEM "http://www.w3.org/MarkUp/DTD/xhtml-role-qname-1.mod"
Revisions:
(none)
....................................................................... --&gt;
&lt;!-- XHTML Role Attribute Qname (Qualified Name) Module
This module is contained in two parts, labeled Section 'A' and 'B':
Section A declares parameter entities to support namespace-
qualified names, namespace declarations, and name prefixing
for XHTML Role and extensions.
Section B declares parameter entities used to provide
namespace-qualified names for the XHTML role attribute:
%role.qname; the xmlns-qualified name for @role
...
XHTML Role extensions would create a module similar to this one.
--&gt;
&lt;!-- Section A: XHTML Role Attribute XML Namespace Framework ::::::::::::::: --&gt;
&lt;!-- 1. Declare a %XHTML-ROLE.prefixed; conditional section keyword, used
to activate namespace prefixing. The default value should
inherit '%NS.prefixed;' from the DTD driver, so that unless
overridden, the default behavior follows the overall DTD
prefixing scheme.
--&gt;
&lt;!ENTITY <span class="entity">% NS.prefixed</span> "IGNORE" &gt;
&lt;!ENTITY <span class="entity">% XHTML-ROLE.prefixed</span> "%NS.prefixed;" &gt;
&lt;!-- 2. Declare a parameter entity (eg., %XHTML-ROLE.xmlns;) containing
the URI reference used to identify the XHTML Role Attribute namespace
--&gt;
&lt;!ENTITY <span class="entity">% XHTML-ROLE.xmlns</span> "http://www.w3.org/1999/xhtml" &gt;
&lt;!-- 3. Declare parameter entities (eg., %XML.prefix;) containing
the default namespace prefix string(s) to use when prefixing
is enabled. This may be overridden in the DTD driver or the
internal subset of an document instance. If no default prefix
is desired, this may be declared as an empty string.
NOTE: As specified in [XMLNAMES], the namespace prefix serves
as a proxy for the URI reference, and is not in itself significant.
--&gt;
&lt;!ENTITY <span class="entity">% XHTML-ROLE.prefix</span> "" &gt;
&lt;!-- 4. Declare parameter entities (eg., %XHTML-ROLE.pfx;) containing the
colonized prefix(es) (eg., '%XHTML-ROLE.prefix;:') used when
prefixing is active, an empty string when it is not.
--&gt;
&lt;![%XHTML-ROLE.prefixed;[
&lt;!ENTITY <span class="entity">% XHTML-ROLE.pfx</span> "%XHTML-ROLE.prefix;:" &gt;
]]&gt;
&lt;!ENTITY <span class="entity">% XHTML-ROLE.pfx</span> "" &gt;
&lt;!-- declare qualified name extensions here ............ --&gt;
&lt;!ENTITY <span class="entity">% xhtml-role-qname-extra.mod</span> "" &gt;
%xhtml-role-qname-extra.mod;
&lt;!-- 5. The parameter entity %XHTML-ROLE.xmlns.extra.attrib; may be
redeclared to contain any non-XHTML Role Attribute namespace
declaration attributes for namespaces embedded in XML. The default
is an empty string. XLink should be included here if used
in the DTD.
--&gt;
&lt;!ENTITY <span class="entity">% XHTML-ROLE.xmlns.extra.attrib</span> "" &gt;
&lt;!-- Section B: XML Qualified Names ::::::::::::::::::::::::::::: --&gt;
&lt;!-- 6. This section declares parameter entities used to provide
namespace-qualified names for the XHTML role attribute.
--&gt;
&lt;!ENTITY <span class="entity">% xhtml-role.role.qname</span> "%XHTML-ROLE.pfx;role" &gt;
&lt;!-- The following defines a PE for use in the attribute sets of elements in
other namespaces that want to incorporate the XHTML role attribute. Note
that in this case the XHTML-ROLE.pfx should be defined. --&gt;
&lt;!ENTITY <span class="entity">% xhtml-role.attrs.qname</span>
"%XHTML-ROLE.pfx;role CDATA #IMPLIED"
&gt;
&lt;!-- end of xhtml-role-qname-1.mod --&gt;
</pre></div>
</div>
</div>
<div id="a_Schema_definition" typeof="bibo:Chapter" about="#a_Schema_definition" class="section">
<h3><span class="secno">B.2 </span>Schema Implementation</h3>
<p>The schema implementation of XHTML Role Attribute Module conforms to the requirements defined
in [<cite><a class="bibref" rel="biblioentry" href="#bib-XHTML-MODULARIZATION11-2e">XHTML-MODULARIZATION11-2e</a></cite>]. It is included here as an
example implementation.</p>
<div id="attributes-module" typeof="bibo:Chapter" about="#attributes-module" class="section">
<h4 id="a_schema_attribs"><span class="secno">B.2.1 </span>Attributes Module</h4>
<div><pre class="dtd">
&lt;?xml version="1.0" encoding="UTF-8"?&gt;
&lt;xs:schema
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
xmlns:xh11d="http://www.w3.org/1999/xhtml/datatypes/"
&gt;
&lt;xs:import namespace="http://www.w3.org/1999/xhtml/datatypes/"
schemaLocation="xhtml-datatypes-1.xsd" /&gt;
&lt;xs:annotation&gt;
&lt;xs:documentation&gt;
This is the XML Schema attribute module for XHTML Role
$Id: Overview.html,v 1.3 2011/01/12 19:57:11 cooper Exp $
&lt;/xs:documentation&gt;
&lt;xs:documentation source="xhtml-copyright-1.xsd"/&gt;
&lt;xs:documentation source="http://www.w3.org/TR/role-attribute#A_role"/&gt;
&lt;/xs:annotation&gt;
&lt;xs:attribute name="role" type="xh11d:TERMorURIorCURIEs"/&gt;
&lt;/xs:schema&gt;
</pre></div>
</div>
</div>
</div>
<div id="s_acks" class="informative section" typeof="bibo:Chapter" about="#s_acks">
<!-- OddPage -->
<h2><span class="secno">C. </span>Acknowledgments</h2><p><em>This section is non-normative.</em></p>
<p>At the time of publication, the participants in the W3C WAI
Protocol and Formats Working Group were:</p>
</div>
<div id="references" class="appendix section" typeof="bibo:Chapter" about="#references">
<!-- OddPage -->
<h2><span class="secno">D. </span>References</h2><div id="normative-references" typeof="bibo:Chapter" about="#normative-references" class="section"><h3><span class="secno">D.1 </span>Normative references</h3><dl class="bibliography" about=""><dt id="bib-RDFA-CORE">[RDFA-CORE]</dt><dd rel="dcterms:requires">Shane McCarron; et al. <a href="http://www.w3.org/TR/2010/WD-rdfa-core-20101026/"><cite>RDFa Core 1.1: Syntax and processing rules for embedding RDF through attributes.</cite></a>26 October 2010. W3C Working Draft. URL: <a href="http://www.w3.org/TR/2010/WD-rdfa-core-20101026/">http://www.w3.org/TR/2010/WD-rdfa-core-20101026/</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-XHTML-MODULARIZATION11-2e">[XHTML-MODULARIZATION11-2e]</dt><dd rel="dcterms:requires">Shane McCarron. <a href="http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729"><cite>XHTML™ Modularization 1.1 Second Edition.</cite></a> 29 July 2010. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729">http://www.w3.org/TR/2010/REC-xhtml-modularization-20100729</a>
</dd><dt id="bib-XHTML-VOCAB">[XHTML-VOCAB]</dt><dd rel="dcterms:requires">XHTML 2 Working Group. <a href="http://www.w3.org/1999/xhtml/vocab"><cite>XHTML Vocabulary</cite></a>. URL: <a href="http://www.w3.org/1999/xhtml/vocab">http://www.w3.org/1999/xhtml/vocab</a>
</dd><dt id="bib-XML10-4e">[XML10-4e]</dt><dd rel="dcterms:requires">C. M. Sperberg-McQueen; et al. <a href="http://www.w3.org/TR/2006/REC-xml-20060816/"><cite>Extensible Markup Language (XML) 1.0 (Fourth Edition).</cite></a> 16 August 2006. W3C Recommendation. URL: <a href="http://www.w3.org/TR/2006/REC-xml-20060816/">http://www.w3.org/TR/2006/REC-xml-20060816/</a>
</dd></dl></div><div id="informative-references" typeof="bibo:Chapter" about="#informative-references" class="section"><h3><span class="secno">D.2 </span>Informative references</h3><dl class="bibliography" about=""><dt id="bib-WAI-ARIA">[WAI-ARIA]</dt><dd rel="dcterms:references">Lisa Pappas; et al. <a href="http://www.w3.org/TR/2010/WD-wai-aria-20100916/"><cite>Accessible Rich Internet Applications (WAI-ARIA) 1.0.</cite></a> 24 February 2009. W3C Working Draft. (Work in progress.) URL: <a href="http://www.w3.org/TR/2010/WD-wai-aria-20100916/">http://www.w3.org/TR/2010/WD-wai-aria-20100916/</a>
</dd><dt id="bib-XML-NAMES11">[XML-NAMES11]</dt><dd rel="dcterms:references">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></body></html>