Role Taxonomy for Accessible Adaptable Applications Working Draft, V1, 03-08-2005

The Roles defined in this specification provides user interface designers with the ability to add extra semantic role information.

The goal is to make static and interactive content of Web pages more usable and accessible to their users and their assistive technologies. This goal is achieved by providing a cross-platform role model for dynamic Web content that allows for content adaptations based on role information. The result is to provide an interoperable way for associating behaviors with document-level markup.

Request for Comments

The PF working group has developed a roadmap on making dynamic web content more accessible to people with disabilities. To assure these technologies will interoperate in a manner that improves accessibility for the widest range of web technologies, the PF wokring group asks for comments and suggestions on how this specification can be improved for use in the technologies that you or your working group are developing. In general we prefer public comments so that all people (including the general public) reviewing the document can be aware of your comments, but you may also send member confidential comments that will be available only to the working group and other W3C members.

Status of This Document

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 can be found in the W3C technical reports index at http://www.w3.org/TR/. This report has not been published to the W3C technical reports index.

This specification adds semantics to content to improve the accessibility and interoperability of Web Content and Applications. This document and the States and Adaptable Properties Module are the result of the gap analysis of the DHTML accessibility roadmap to enable accessible dynamic Web content and applications. The Working Group expects to advance this document to a Working Draft and Recommendation.

This document is for review purposes only. The web address, URL and file name of this document may/will change. Publication as a 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.

This document was produced under the 5 February 2004 W3C Patent Policy. The Working Group maintains a public list of patent disclosures relevant to this document; that page also includes instructions for disclosing [and excluding] a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) with respect to this specification should disclose the information in accordance with section 6 of the W3C Patent Policy

1.Introduction

Roles are a simple way for an author to make custom widgets (new interactive elements) accessible and interoperable by encapsulating the functional substructures in a page. The user agent or operating system then knows how to handle the element by mapping the role to an adaptive interface or to the accessibility API (Accessible Programmable Interfaces) of the operating system.

This draft currently handles two aspects of roles - GUI functionality and structural relationships of the element. For more information see the Dynamic Accessible Web Content Roadmap Roadmap and implementation examples for the use of roles making dynamically generated content accessible.

This taxonomy is designed in-part to support the common roles found in platform accessibility API (Accessible Programmable Interfaces) frameworks. Reference to roles found in this taxonomy by dynamic Web content may be used to support dynamic accessible content authoring, interoperability with assistive technologies.

The schema to support this standard has been designed to be extended so that custom roles can be created while providing a common schema for describing how to interact accessibly with a custom role. See extending accessible roles.

At some point the working group intends to add roles for A, Adding concepts in the type of content for adaptation to the user scenario and B, Knowledge representation of Web content.In future versions of this specification the working group intend to add roles in support of individualized content adaptation and knowledge representation of Web content.

1.1 Example

This example shows a role being used to make a simple widget known to the user agent, so that the user agent knows how to handle it.

Roles can be embedded in any host language, e.g. [XHTML] 1.1. In this example, a table has been assigned the role of a spread sheet.

<table id="table1" x2:role="wairole:spreadsheet" >
Encapsulated in the role information is information for the operating system that enables it to be properly treated. (In this case that multiselectable is supported.)

1.2 Terms and Definitions

While some terms are defined in place, the following definitions are used throughout this document. Familiarity with W3C XHTML 1.1 Recommendation [XHTML] and the W3C XML 1.0 Recommendation [XML] is highly recommended.

2.Conformance Requirements

The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].

2.1.Document Conformance

Roles for RDF and XML is not a stand-alone document type. It is intended to be integrated into other host languages such as XHTML. A conforming document 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:

2.2.Host Language Conformance

When Roles are included in a host language, all of the facilities required in this specification must be included in the host language.

2.3.User Agent Conformance

A conforming user agent must reference the role information reference in the DOM.
However it is advised that a conforming user agent also allows for roles to be extended via a RDF . When a role from a different specification extends or inherits from a role in this specification, then that role should also be supported at least to the extent that the original role is supported.

3.The RDF Roles Model

This specification defines a Taxonomy called Role. The Roles Taxonomy uses the XML namespace [XMLNAMES] identifier

All examples are informative. Examples in this document that use the namespace prefix "wairoles" all assume a valid xmlns declaration

The remainder of this section describes the classes instances and properties in this taxonomy, the semantics, and provides an RDF Schema as required in [RDF ].

Example

In this example a div has been used in place of a standard form element checkbox. A role is used to make the behavior of the simple widget known to the user agent.

<rdf:Description rdf:ID="Checkbox">
<rdf:type rdf:resource="#Select"/>
<baseConcept>http://www.w3.org/MarkUp/HTML#checkbox</baseConcept>
<supportedState>waistates:multiselect</supportedState>
</rdf:Description>

In this example a Checkbox is defined as a type of select, but represents the same concept Checkbox as in the [HTML] specification. Although it inherits all the supported states of a select, we also expect it to support multiselect. Note that much of this could be formalized in XML schema of XSD. However being able to define similarities between roles, such as baseConcepts and more descriptive definitions would not be available in XSD.

3.1 Role Properties

Roles are defined and described by their properties. Properties define the structural function of a role, such as: What a roles is, concepts behind it , what it can contain, what it must contain.

In the case of widgets this also includes how it interacts with the user agent based on mapping to [HTML] forms and XFORMS, allowed states and required states.

Relationships between concepts

The are three properties that describe the relationship between concepts. They are:

Property	Description	Values	Related Concepts
supportedState	a supportedState must be supported by this role. Typically refers to states from the SAP namespace	Any valid RDF object reference, such as a URI.
mustContain	A child element that must be contained by this role. For example a list must contain a listitem.	Any valid RDF object reference, such as a URI or RDF ID.	http://www.w3.org/2004/02/skos/core#subject
scope	Context, where this role is allowed. For example a list item is allowed inside a list.	Any valid RDF object reference, such as a URI or RDF ID.	http://www.w3.org/2004/02/skos/core#Concept
media	The media type, where the Role is allowed - a type of scope	Any valid RDF object reference, such as a URI or RDF ID.	baseConcept: DC: Format XFORMS media type
importance	Estimated importance of a role to completion of the main tasks of a delivery unit. For example a main menu is typically required for a user to beale to completer the main tasks of a site. A secondary side menu is typically less important. Hence a main menu has an importance level of one and secondary side menu may have an importance level of 0.6.	0 (min) 1 (max)
nameRef	How a role type name is extracted and referenced inside a document. For example the DOM might reference a role by it's title.	Any valid RDF object reference, such as a URI or RDF ID. Recomended values: Child, title, content.

3.2 Roles

To support the current user scenario this specification defines roles that A, help define Widgets (For example, a tristate Checkbox) and B, help define page structure (for example, a section header).

3.1.1 Roles: Base Classes

Role	Description	Inherited Category	Base and Related Concepts	Supported states and properties (beyond inherited states) (all support disabled and zoom)
Roletype	Describes the structural and functional purpose of an element. A Role is also a concept.	DC:Type skos:Concept	[HTML] role [HTML] Link rel [HTML] Link rev	DC:Label (required) DC:Description (required) importance - relatedConcept ContentType CanContain HasTask ? baseConcept: relatedConcept
Widget	A component of a GUI	Role		State

3.1.2 Widget Roles

Widget Role	Description	Inherited Concepts	Base and Related Concepts	New supported states(beyond inherited states)	Inherited states	nameRef	Example
Input	Generic type for widgets that can have a value	Widget			Disable zoom	Title
Textbox	Generic type for the inputs that allow free-form text, as their value	Input	XFORMS input		Disable zoom	Title
Link	Interactive reference to a resource (note, that in [HTML] 2 any element can have an href attribute and thus be a link)	Widget	HTML Link		Disable zoom	Child content title
Select	A form control that allows the user to make selections from a set of choices	Input List (see structure)		Multiselectable	Disable zoom	Title
Combobox	Combobox is a presentation of a select, where you can type to locate a selected item. NOTE: In XForms the same select can have one of 3 appearances: combo-box, drop-down box or group of radio-buttons. Besides, many browsers (if not all of them) allow users to type in a drop-down select as well.	Select	HTML select (multiple)		Disable zoom multiselectable	Title
Option	A selectable item in a list represented by a Select.	Input ListItem (see structure)	ListItem(see structure), HTML option, XForms item	Selected	Disable zoom	Child content title
Checkbox	A control that has two possible states, an equivalent to a boolean	Option	HTML input (type : checkbox)	Checked="true"\|"false"	Disable zoom selected	Child content title
Checkboxtristate	A control that has three possible states, (1 0 -1) Often found in installer where an option has been partially installed	Checkbox		Checked="true"\|"false"\|"mixed"	Disable zoom selected	Child content title
Radio	A radio is an option in single-select list.	Checkbox	HTML input (type : radio)		Disable zoom selected checked="true"\|"false"	Child content title
Radiogroup	Maybe, we would rather have a generic "group of choices" type.	Select			Disable zoom selected multiselectable	Title
Button	Allows for user-triggered actions.	Widget Link	XFORMS trigger	Pressed	Disable zoom	Child conteny title
Buttonsubmit	This form control initiates submission of all or part of the instance data to which it is bound	Button	HTML input (type :submit)		Disable zoom pressed	Child conteny title
Buttoncancel	This button initiates closing a window or leaving a form (e.g. To another page) without submission	Button			Disable zoom pressed	Child content title
Buttonundo	This control brings a form to the initial state (e.g. returns all default values to all inputs)	Button	HTML input (type : reset)		Disable zoom pressed	Child content title
Buttonback	Brings user-agent to the previous page or state	Button	HTML Link		Disable zoom pressed	Child content title
MenuItemradio	How it differs from radio?	Menuitem (see structure) Radio			Disable zoom selected checked="true"\|"false"	Child content title
MenuItemcheckbox	How it differs from Checkbox? Isn't it defined by its parent's role?	Menuitem Checkbox			Disable zoom selected checked="true"\|"false"	Title
Progressbar	Used by applications for tasks that take a long time to execute, to show the execution progress.	Widget			Disable zoom	Title
Hidden	A form control that is never displayed to the user, but is always submitted to the server with the form. NOTE: In XForms, unless bound to form controls, instance data nodes are not presented to the user; consequently, there is no need for a form control corresponding to [HTML] `input type="hidden"`.	Input	[HTML] input (type : hidden)		Disable zoom	Title
Secret	Provides the user with the ability to supply information to the system in a manner that makes it difficult for someone, other than the user, who may be observing the process to discern the value that is being supplied.	Input	[HTML] input (type : password)		Disable zoom	Title
Separator	A line or bar that separates and distinguishes sections of content	Widget	[HTML] hr		Disable zoom	Title
Range	Represents a range of values that can be set by the user.	Input			Disable zoom	Title
Slider	A user input where the user selects an input in a given range. It is a form of Range that expects an analog keyboard interface	Range			Disable zoom	Title
SpinButton	A form of Range that expects a user selecting from discreet choices.	Range			Disable zoom	Title
Spreadsheet	Interactive table where the user can enter the values	Widget Table		Multiselectable	Disable zoom	Title
Textarea	Intended for use in entering multi-line content	TextBox	[HTML] textarea		Disable zoom	Title
Textfield	Free-form data entry for short on-line content.	TextBox	[HTML] input (type : text)		Disable zoom	Child content title
Tree	A form of a Select (or, generally, of a list having groups inside groups) - where sub trees can be collapsed and expanded	Select Chart		Expanded	Disable zoom multiselectable	Child content title
Treeitem	An option item of a tree.	Option			Disable zoom selected	Content child title
Alert	A message with an alert or error information	Window (see structure) Dialog	XFORMS alert		Disable zoom	Title
Dialog	A small application window	Window			Disable zoom	Title

3.1.3 Structural Roles

Roles for document structure are also required to support the accessibility of dynamic Web content to assist adaptive technology in determining active content vs. static document content. Structural Roles, by themselves do not all map to accessibility API's, but are used to create widget roles or assist content adaptation.

This schema is likely to evolve as new use cases are added to the scope of this specification.

Roles	Description	Inherited Category	Base and Related Concepts	domRef or Not Mapped to Accessibility API's	New support states(beyond inherited states) (all support disabled and zoom)	scope
Presentational	An element who's role is Presentational does not need to be mapped to the accessibility API	DeliveryUnit/Task		Not Mapped
Application	A software unit executing a set of tasks for its users	DeliveryUnit/Task		True
Document	Content that contains information	DeliveryUnit		True
Site	A collection of documents accessible via HTTP on the Internet	group scope: pages, Application, task		Not Mapped
Page	One side of a leaf, in a printed book, or a displayed unit, in computer documents.	DeliveryUnit Site/Document		Not Mapped
Book	A document or a collection of documents delivered as one unit.	Document scope: page		Not Mapped
Frountmatter	Preliminary material in a book: e.g. copyright notice, foreword, acknowledgments, table of contents, etc. It serves as a guide to the content and nature of a book.	Section scope: Document (Book)	[DTB]	Not mapped
Rearmatter	Contains supplementary material such as appendices, glossaries, bibliographies, and indices. It follows the BodyMatter of the book	Section scope: Document (Book)	[DTB]	Not mapped
Bodymatter	Text proper of a book, as contrasted with preliminary material FrontMatter or supplementary information in RearMatter.	Section scope: Document (Book)	[DTB]	Not mapped
Section	A logical part of a DeliveryUnit (page or a document)		document, [DTB], NIMAS, [HTML] link rel	Name from child content or title attribute
Window	Browser or application window	Application		Name from child content or title attribute
Frame	A sub window in a Web-page that displays a whole [HTML] document.	Window		Name from child content or title attribute
Group	Group is a collection of sections, and is itself a section. It defines a set or sub set. It has a broad scope.	Section	DC: Collection, Dataset	Name from title attribute		mustContain sections
Grouplist	A list of names or short descriptions of items/elements contained in a Group	List,	DAISY :ToC	Name from child content or title attribute		scope: Sectionheaders
Accordion	A visual presentation of a group of sections	Group		Name from title attribute
Tilegroup	A group of tiles	Group		Name from title attribute		scope: Tile
Tile	A visual presentation of section	Section		Name from child content or title attribute
Tilelist	List of names or short descriptions of tiles in a TileGroup	GroupList		Name from title attribute		scope: Tile
Chart	A graphic representation of some data.	Group	[HTML] table ?	Not mapped
Chartsection	A section inside a chart	Section	[HTML] td	Name from child content or title attribute	name, start value, effect, has header (or literal),stack, tile
Grid	A system of two sets of lines that intersect each other at a fixed angle.	Group	[HTML] table ?	Name from title attribute		scope: Gridcells
Gridcell	A cell in a grid	Section	[HTML] td	Name from child content or title attribute
Tabpanel	A visual presentation of a section	Section		Name from child content or title attribute
Tab	A TabPanel header	Sectionhead		Name from child content or title attribute		scope: tabPanel
Tablist	A list of TabPanels in a Tab	Grouplist		Name from title attribute
Table	Contains cells of tabular data arranged in rows and columns.	Group	[HTML] table	Name from title attribute
Td	A table cell containing data.	Section	[HTML] td	Name from child content or title attribute
Th	A table cell containing header information.	Sectionhead TD	[HTML] th	Name from child content or title attribute		scope: TD
Col	Description of a table column.	Group		Name from title attribute		scope: TD
Row	Defines a table row.	Group	[HTML] tr	Name from title attribute		scope: TD
List	Group of small items	Group	[HTML] list	Name from title attribute
Listitem	An entry in a list.	Section	XForms item	Name from child content or title attribute
Linkblock	A list of related links.	List		Name from title attribute
Menu	A list of links to important sections of a Document or a Site.	Linkblock	navigation in [HTML] roles see http://www.w3.org/ TR/2005/WD-xhtml2-20050527 /mod-role.html#col_Role	Name from title attribute	menuLevel ??
Menubar	A Visual presentation of a menu	Menu		Name from title attribute
Mainmenu	A menu containing the most important links on this page/document	Menu		Name from title attribute
Submenu1	Main submenu	Menu		Name from title attribute
Submenu2	Secondary submenu	Menu		Name from title attribute
Submenutrivia	Unimportant submenu	Menu		Name from title attribute
Toolbar	A toolbar is a type of menu where icons are often toggle-able or they are not focusable. ToolBars do not have drop down menus	Menu		Name from title attribute
Footer	Small text at the end of a page - typically contains copyright and similar information		[HTML] roles : contentinfo, copyright	Not mapped
Footermenusite	A menu found at the bottom of a page containing important site links. Typically includes a link to a "contact us" page and other important site's pages.	Menu Footer		Not mapped
Menuitem	A link in a menu	Listitem Link		Name from child content or title attribute
Sectionhead	A heading without level	Heading	[HTML]/[DTB]/NIMAS h1, h2...	Name from child content or title attribute
Heading1	Level 1 heading	Sectionhead	[HTML]/[DTB]/NIMAS h1	Name from child content or title attribute
Heading2	Level 2 heading	Sectionhead	[HTML]/[DTB]/NIMAS h2	Name from child content or title attribute		level=2
Heading3	Level 3 heading	Sectionhead	[HTML]/[DTB]/NIMAS h3	Name from child content or title attribute		level=3
Heading4	Level 4 heading	Sectionhead	[HTML]/[DTB]/NIMAS h4	Name from child content or title attribute		level=4
Heading5	Level 5 heading	Sectionhead	[HTML]/[DTB]/NIMAS h5	Name from child content or title attribute		level=5
Heading6	Level 6 heading	Sectionhead	[HTML]/[DTB]/NIMAS h6	Name from child content or title attribute		level=6

A.Implementation

<?xml version="1.0" encoding="UTF-8"?>



<!DOCTYPE rdf:RDF [



<!ENTITY xsd "http://www.w3.org/2001/XMLSchema#">



<!ENTITY dc "http://dublincore.org/2003/03/24/dces#">



<!ENTITY owl "http://www.w3.org/2002/07/owl#">



<!ENTITY rdfs "http://www.w3.org/2000/01/rdf-schema#">



<!ENTITY rdf "http://www.w3.org/1999/02/22-rdf-syntax-ns#">



<!ENTITY states "http://www.w3.org/2005/01/aaa#">



<!ENTITY skos "http://www.w3.org/2004/02/skos/core#">



]>



<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:dc="http://purl.org/dc/elements/1.1/#"
xmlns:owl="http://www.w3.org/2002/07/owl#"
xmlns:role="http://www.w3.org/2005/01/wai-rdf/GUIRoleTaxonomy#"

xmlns:skos="http://www.w3.org/2004/02/skos/core#"

xml:base="http://www.w3.org/2005/01/wai-rdf/GUIRoleTaxonomy">



<owl:ObjectProperty rdf:ID="relatedConcept">



<rdfs:comment xml:lang="en">The URI of similar/related types from other
specifications (See SKOS)</rdfs:comment>



<rdfs:domain rdf:resource="&xsd;anyURI"/>



</owl:ObjectProperty>



<owl:ObjectProperty rdf:ID="baseConcept">



<rdfs:comment xml:lang="en">This is similar to type but without
inheritance of limitations and properties. role:baseConcepts are designed as
a substitute for inheritance for external concepts. </rdfs:comment>



<rdfs:sub propertyOf rdf:resource="#role:relatedConcept"/>



</owl:ObjectProperty>



<owl:ObjectProperty rdf:ID="scope">



<rdfs:comment xml:lang="en">Context where this role is
allowed</rdfs:comment>



<rdfs:domain rdf:resource="#role"/>





</owl:ObjectProperty>



<owl:ObjectProperty rdf:ID="mustContain">





<rdfs:comment xml:lang="en">A child that must be supported by this
role</rdfs:comment>



<rdfs:sub propertyOf rdf:resource="#role:scope"/>



</owl:ObjectProperty>



<owl:ObjectProperty rdf:ID="media">



<rdfs:comment xml:lang="en">The media type, where the Role is allowed -
a type of role:scope, simmilar to DC: Format or media
type</rdfs:comment>



<rdfs:sub propertyOf rdf:resource="#role:scope"/>



</owl:ObjectProperty>



<owl:ObjectProperty rdf:ID="canSupportState">



<rdfs:comment xml:lang="en">A state that can be supported for this a
Role</rdfs:comment>



<rdfs:domain rdf:resource="#Widget"/>



</owl:ObjectProperty>



<owl:ObjectProperty rdf:ID="supportedState">



<rdfs:comment xml:lang="en">A state that must be supported for this
Role</rdfs:comment>



<rdfs:sub propertyOf rdf:resource="#canSupportState"/>



</owl:ObjectProperty>



<owl:ObjectProperty rdf:ID="default">



<rdfs:comment>Default value of a supported state in the context of this
role</rdfs:comment>



</owl:ObjectProperty>





<owl:ObjectProperty rdf:ID="importance">



<rdfs:comment>relative importance of a role (0 -
1)</rdfs:comment>



<rdfs:domain rdf:resource="&xsd;anyURI"/>



</owl:ObjectProperty>



<owl:ObjectProperty rdf:ID="domRef">



<rdfs:comment>How the DOM references the widget</rdfs:comment>



<rdfs:domain rdf:resource="#Widget"/>



<rdfs:Range/>



</owl:ObjectProperty>



<owl:Class rdf:ID="roletype">



<rdfs:comment>This is a draft resource for adding semantic annotations
and information to Web resources. Knowing what the types of content are in a
Web page allows for better customized renderings. Including want to allow
information hiding, or rendering common types of content in a consistent way
- it makes the Web easer to use and more accessibility. You can also use this
for device independence so that content is better formatted to fit on the
device. </rdfs:comment>





<rdfs:subClassOf>



<owl:Restriction>



<owl:onProperty rdf:resource="dc:description"/>



<owl:cardinality
rdf:datatype="&xsd;string">1</owl:cardinality>



</owl:Restriction>



</rdfs:subClassOf>



<rdfs:comment>You have to give each content type a title and
description sorry folks (just be glad I did not put a min length on the
description</rdfs:comment>



<rdfs:comment>These are the required properties - however we recommend
also using role:importance. </rdfs:comment>



</owl:Class>



<owl:Class rdf:ID="widget">



<rdfs:subClassOf rdf:resource="#roletype"/>



<dc:description xml:lang="en">A widget is a base class for widgets.
</dc:description>



<role:supportedState rdf:parseType="Resource">

<rdfs:value>states:disabled</rdfs:value>

<role:default>false</role:default>

</role:supportedState>



<role:supportedState rdf:resource="&states;describedby"/>



<role:supportedState rdf:resource="&states;labelledby"/>



</owl:Class>



<owl:Class rdf:ID="input">



<rdfs:subClassOf rdf:resource="#widget"/>



<role:baseConcept
rdf:resource="http://www.w3.org/TR/html4/interact/forms.html#edef-INPUT"/>



<dc:description xml:lang="en">An input is a base class for widgets that
have a value. </dc:description>



<role:domRef rdf:resource="&states;title"/>



</owl:Class>



<owl:Class rdf:ID="textbox">



<rdfs:subClassOf rdf:resource="#input"/>



<dc:description xml:lang="en">A textbox is a base class for widgets
that have a free-form text value. </dc:description>



<role:domRef rdf:resource="&states;Child conten"/>



</owl:Class>



<owl:Class rdf:ID="link">



<rdfs:subClassOf rdf:resource="#widget"/>



<dc:description xml:lang="en">Interactive reference.
</dc:description>



<role:domRef rdf:resource="&states;title"/>



<role:domRef rdf:resource="&states;Child conten"/>



</owl:Class>



<owl:Class rdf:ID="select">



<rdfs:subClassOf rdf:resource="#input"/>



<role:baseConcept
rdf:resource="http://www.w3.org/TR/html4/interact/forms.html#edef-SELECT"/>



<role:relatedConcept rdf:resource="#list"/>



<role:mustContain rdf:resource="#option"/>



<dc:description xml:lang="en">A select is an Input that allows the user
to make selections from a set of choices. </dc:description>



<role:supportedState rdf:resource="&states;multiselectable"/>



</owl:Class>



<owl:Class rdf:ID="combobox">



<rdfs:subClassOf rdf:resource="#select"/>



<role:baseConcept
rdf:resource="http://www.w3.org/TR/html4/interact/forms.html#edef-SELECT"/>



<role:relatedConcept rdf:resource="#list"/>



<role:mustContain rdf:resource="#option"/>



<dc:description xml:lang="en">A combobox is a sellect with a specific
presentation. </dc:description>



</owl:Class>



<owl:Class rdf:ID="radiogroup">



<rdfs:subClassOf rdf:resource="#select"/>



<role:baseConcept
rdf:resource="http://www.w3.org/TR/html4/interact/forms.html#edef-SELECT"/>



<role:relatedConcept rdf:resource="#list"/>



<role:mustContain rdf:resource="#radio"/>



<dc:description xml:lang="en">A select containing radio-buttons,
instead of options. </dc:description>



</owl:Class>



<owl:Class rdf:ID="Option">



<rdfs:subClassOf rdf:resource="#input"/>



<role:baseConcept
rdf:resource="http://www.w3.org/TR/html4/interact/forms.html#edef-OPTION"/>



<role:relatedConcept rdf:resource="#listitem"/>



<role:scope rdf:resource="#select"/>



<dc:description xml:lang="en">An option is a selectable item in a list
represented by a Select. </dc:description>



<role:supportedState rdf:parseType="Resource">

<rdfs:value>states:selected</rdfs:value>

<role:default>false</role:default>

</role:supportedState>



<role:domRef rdf:resource="&states;Child conten"/>



</owl:Class>



<owl:Class rdf:ID="checkbox">



<rdfs:subClassOf rdf:resource="#input"/>



<dc:description xml:lang="en">A checkbox is an input that has two
possible values, an equivalent to a boolean. </dc:description>



<role:supportedState rdf:parseType="Resource">

<rdfs:value>states:checked</rdfs:value>

<role:default>false</role:default>

</role:supportedState>



<rdfs:comment
xml:lang="en">checked="true"|"false"</rdfs:comment>



<role:domRef rdf:resource="&states;Child conten"/>



</owl:Class>



<owl:Class rdf:ID="checkboxtristate">



<rdfs:subClassOf rdf:resource="#Checkbox"/>



<dc:description xml:lang="en">A checkboxtristate is a control that has
three possible states. </dc:description>



<rdfs:comment
xml:lang="en">checked="true"|"false"|"mixed"</rdfs:comment>



</owl:Class>



<owl:Class rdf:ID="radio">



<rdfs:subClassOf rdf:resource="#checkbox"/>



<dc:description xml:lang="en">An option in single-select list.
</dc:description>



</owl:Class>



<owl:Class rdf:ID="menuitemcheckbox">



<rdfs:subClassOf rdf:resource="#checkbox"/>



<role:relatedConcept rdf:resource="#menuitem"/>



<role:scope rdf:resource="#menu"/>



<dc:description xml:lang="en">A menuitemcheckbox is a checkbox that is
inside a menu, next to a menu item. </dc:description>



</owl:Class>



<owl:Class rdf:ID="menuitemradio">



<rdfs:subClassOf rdf:resource="#radio"/>



<role:relatedConcept rdf:resource="#menuitem"/>



<role:scope rdf:resource="#menu"/>



<dc:description xml:lang="en">A menuitemradio is a radio-button that is
inside a menu, next to a menu item. </dc:description>



</owl:Class>



<owl:Class rdf:ID="button">



<rdfs:subClassOf rdf:resource="#widget"/>



<role:baseConcept
rdf:resource="http://www.w3.org/TR/html4/interact/forms.html#edef-BUTTON"/>



<role:relatedConcept rdf:resource="#link"/>



<dc:description xml:lang="en">A button is a widget that allows for
user-triggered actions. </dc:description>



<role:supportedState rdf:parseType="Resource">

<rdfs:value>states:pressed</rdfs:value>

<role:default>false</role:default>

</role:supportedState>



<role:domRef rdf:resource="&states;Child conten"/>



</owl:Class>



<owl:Class rdf:ID="buttonsubmit">



<rdfs:subClassOf rdf:resource="#button"/>



<dc:description xml:lang="en">Buttonsubmit is a button that initiates
submission of all or part of the instance data to which it is bound.
</dc:description>



</owl:Class>



<owl:Class rdf:ID="buttoncancel">



<rdfs:subClassOf rdf:resource="#button"/>



<dc:description xml:lang="en">Buttoncancel is a button that initiates
closing a window or leaving a form (e.g. To another page) without submission.
</dc:description>



</owl:Class>



<owl:Class rdf:ID="buttonundo">



<rdfs:subClassOf rdf:resource="#button"/>



<dc:description xml:lang="en">Buttonundo is button that brings a form
to the initial state (e.g. returns all default values to all inputs).
</dc:description>



</owl:Class>



<owl:Class rdf:ID="buttonback">



<rdfs:subClassOf rdf:resource="#button"/>



<dc:description xml:lang="en">Buttonback is a button that brings
user-agent to the previous page/state. </dc:description>



</owl:Class>



<owl:Class rdf:ID="progressbar">



<rdfs:subClassOf rdf:resource="#widget"/>



<dc:description xml:lang="en">Progressbar is a widget used by
applications to show the execution progress for tasks that take a long time
to execute. </dc:description>



</owl:Class>



<owl:Class rdf:ID="separator">



<rdfs:subClassOf rdf:resource="#widget"/>



<dc:description xml:lang="en">A separator is a line or bar that
separates and distinguishes sections of content. </dc:description>



</owl:Class>



<owl:Class rdf:ID="hidden">



<rdfs:subClassOf rdf:resource="#input"/>



<dc:description xml:lang="en">A hidden input is never displayed to the
user, but is always submitted to the server with the
form.</dc:description>



</owl:Class>



<owl:Class rdf:ID="secret">



<rdfs:subClassOf rdf:resource="#input"/>



<dc:description xml:lang="en">A secret input provides the user with the
ability to supply information to the system in a manner that makes it
difficult for someone, other than the user, who may be observing the process
to discern the value that is being supplied.</dc:description> 



</owl:Class>



<owl:Class rdf:ID="range">



<rdfs:subClassOf rdf:resource="#input"/>



<dc:description xml:lang="en">A range is an input that restricts the
user to a range of values.</dc:description>



</owl:Class>



<owl:Class rdf:ID="slider">



<rdfs:subClassOf rdf:resource="#range"/>



<dc:description xml:lang="en">A slider is a range input thatthat
restricts the user to a range of values and expects an analog keyboard
interface.</dc:description>



</owl:Class>



<owl:Class rdf:ID="spinbutton">



<rdfs:subClassOf rdf:resource="#range"/>



<dc:description xml:lang="en">A spinbutton is a range input that
restricts the user to a range of values, and expects discreet
choices..</dc:description>



</owl:Class>



<owl:Class rdf:ID="textarea">



<rdfs:subClassOf rdf:resource="#textbox"/>



<role:baseConcept
rdf:resource="http://www.w3.org/TR/html4/interact/forms.html#edef-TEXTAREA"/>



<dc:description xml:lang="en">A textarea is a textbox input intended
for use in entering multi-line content.</dc:description>



</owl:Class>



<owl:Class rdf:ID="textfield">



<rdfs:subClassOf rdf:resource="#textbox"/>



<dc:description xml:lang="en">A textfield is a textbox input intended
for free-form data entry for short on-line content.</dc:description>



</owl:Class>



<owl:Class rdf:ID="tree">



<rdfs:subClassOf rdf:resource="#select"/>



<role:baseConcept rdf:resource="#chart"/>



<role:mustContain rdf:resource="#treeitem"/>



<dc:description xml:lang="en">A tree is a select, where groups of
options (sub-trees) can be collapsed and expanded.</dc:description>



<role:supportedState rdf:resource="&states;expanded"/>



</owl:Class>



<owl:Class rdf:ID="spreadsheet">



<rdfs:subClassOf rdf:resource="#widget"/>



<role:baseConcept rdf:resource="#table"/>



<dc:description xml:lang="en">A spreadsheet is an interactive table
where the user can enter the values.</dc:description>



<role:supportedState rdf:resource="&states;multiselectable"/>



</owl:Class>



<owl:Class rdf:ID="treeitem">



<rdfs:subClassOf rdf:resource="#option"/>



<role:scope rdf:resource="#tree"/>



<dc:description xml:lang="en">A treeitem is an option item of a
tree.</dc:description>



</owl:Class>



<owl:Class rdf:ID="dialog">



<rdfs:subClassOf rdf:resource="#window"/>



<dc:description xml:lang="en">A dialog is a (small) application
window.</dc:description>



</owl:Class>



<owl:Class rdf:ID="alert">



<rdfs:subClassOf rdf:resource="#dialog"/>



<dc:description xml:lang="en">An alert is a dialog with inportant alert
or error information.</dc:description>



</owl:Class>



<owl:Class rdf:ID="deliveryunit">



<rdfs:subClassOf rdf:resource="#roletype"/>



<dc:description xml:lang="en">A deliveryunit is structure that is
delivered to the client </dc:description>



<role:supportedState rdf:resource="&states;describedby"/>



<role:supportedState rdf:resource="&states;labelledby"/>



</owl:Class>



<owl:Class rdf:ID="task">



<rdfs:subClassOf rdf:resource="#deliveryunit"/>



<dc:description xml:lang="en">A task is a delivery unit that is
delivered to the client to perform a specific task </dc:description>



</owl:Class>



<owl:Class rdf:ID="presentational">



<rdfs:subClassOf rdf:resource="#task"/>



<dc:description xml:lang="en">An element who's role is Presentational
does not need to be mapped to the accessibility API</dc:description>



</owl:Class>



<owl:Class rdf:ID="application">



<rdfs:subClassOf rdf:resource="#task"/>



<dc:description xml:lang="en">An application is a software unit task
executing a set of sub tasks for its users</dc:description>



</owl:Class>



<owl:Class rdf:ID="document">



<rdfs:subClassOf rdf:resource="#deliverunit"/>



<dc:description xml:lang="en">A document is a unit of content, such as
text, that together conveys information</dc:description>



</owl:Class>



<owl:Class rdf:ID="page">



<rdfs:subClassOf rdf:resource="#document"/>



<dc:description xml:lang="en">A page represents one side of a leaf in a
printed book, or a similar unit in computer
documents.</dc:description>



</owl:Class>



<owl:Class rdf:ID="book">



<rdfs:subClassOf rdf:resource="#document"/>



<rdfs:subClassOf rdf:resource="#group"/>



<role:mustContain rdf:resource="#page"/>



<role:baseConcept
rdf:resource="http://www.loc.gov/nls/z3986/v100/dtbook110doc.htm#book"/>



<dc:description xml:lang="en">A book is a document that is also
collection of pages </dc:description>



</owl:Class>



<owl:Class rdf:ID="frontmatter">



<rdfs:subClassOf rdf:resource="#section"/>



<role:scope rdf:resource="#document"/>



<role:baseConcept
rdf:resource="http://www.loc.gov/nls/z3986/v100/dtbook110doc.htm#frontmatter"/>



<dc:description xml:lang="en">Frontmatter is the preliminary material
in a book: e.g. notice, foreword, acknowledgments, table of contents, etc. It
often acts as a guide to the content and nature of a
book.</dc:description>



</owl:Class>



<owl:Class rdf:ID="rearmatter">



<rdfs:subClassOf rdf:resource="#section"/>



<role:baseConcept
rdf:resource="http://www.loc.gov/nls/z3986/v100/dtbook110doc.htm#reamatter"/>



<role:scope rdf:resource="#document"/>



<dc:description xml:lang="en">Rearmatter contains supplementary
material such as , glossaries, bibliographies, and indices.
</dc:description>



</owl:Class>



<owl:Class rdf:ID="bodymatter">



<rdfs:subClassOf rdf:resource="#section"/>



<role:scope rdf:resource="#document"/>



<role:baseConcept
rdf:resource="http://www.loc.gov/nls/z3986/v100/dtbook110doc.htm#bodymatter"/>



<dc:description xml:lang="en">Bodymatter is the main text of a book, as
contrasted with material FrontMatter or supplementary information in
Rearmatter .</dc:description>



</owl:Class>



<owl:Class rdf:ID="section">



<role:relatedConcept
rdf:resource="http://www.loc.gov/nls/z3986/v100/dtbook110doc.htm#frontmatter"/>



<role:relatedConcept
rdf:resource="http://www.loc.gov/nls/z3986/v100/dtbook110doc.htm#level"/>



<role:relatedConcept
rdf:resource="http://www.w3.org/TR/REC-smil/#par"/>



<dc:description xml:lang="en">A section is a logical part of a
DeliveryUnit (page or a item) </dc:description>



</owl:Class>



<owl:Class rdf:ID="window">



<rdfs:subClassOf rdf:resource="#application"/>



<dc:description xml:lang="en">A window refers to a browser or
application window</dc:description>



</owl:Class>



<owl:Class rdf:ID="frame">



<rdfs:subClassOf rdf:resource="#window"/>



<dc:description xml:lang="en">A frame is a sub window in a Web page
that displays a HTML document.</dc:description>



</owl:Class>



<owl:Class rdf:ID="group">



<rdfs:subClassOf rdf:resource="#section"/>



<role:mustContain rdf:resource="#section"/>



<dc:description xml:lang="en">A group is a collection of sections, and
is also itself a section. It defines a set or sub set.
</dc:description>



</owl:Class>



<owl:Class rdf:ID="list">



<rdfs:subClassOf rdf:resource="#group"/>



<dc:description xml:lang="en">a list is a group of small
items</dc:description>



<role:mustContain rdf:resource="listitem"/>



<role:baseConcept
rdf:resource="http://www.w3.org/TR/html4/struct/lists.html#edef-UL"/>



</owl:Class>



<owl:Class rdf:ID="listitem">



<rdfs:subClassOf rdf:resource="#section"/>



<dc:description xml:lang="en">A listitem is an entry or item in a
list.</dc:description>



<role:scope rdf:resource="list"/>



<role:baseConcept
rdf:resource="http://www.w3.org/TR/html4/struct/lists.html#edef-LI"/>



</owl:Class>



<owl:Class rdf:ID="grouplist">



<rdfs:subClassOf rdf:resource="#list"/>



<role:scope rdf:resource="group"/>



<dc:description xml:lang="en">A grouplist is a list of the names or
short descriptions of elements contained in a Group</dc:description>



</owl:Class>



<owl:Class rdf:ID="accordion">



<rdfs:subClassOf rdf:resource="#group"/>



<dc:description xml:lang="en">An accordion is visual presentation of a
group of </dc:description>



</owl:Class>



<owl:Class rdf:ID="tilegroup">



<rdfs:subClassOf rdf:resource="#group"/>



<role:mustContain rdf:resource="tiles"/>



<dc:description xml:lang="en">A tilegroup is a visual presentation of a
group of </dc:description>



</owl:Class>



<owl:Class rdf:ID="tile">



<rdfs:subClassOf rdf:resource="#section"/>



<dc:description xml:lang="en">A tile is visual presentation of section
found inside a tilegroup.</dc:description>



</owl:Class>



<owl:Class rdf:ID="tilelist">



<rdfs:subClassOf rdf:resource="#grouplist"/>



<role:scope rdf:resource="tile"/>



<dc:description xml:lang="en">A tilelist ia a list of names or short
descriptions of tiles a tilegroup</dc:description>



</owl:Class>



<owl:Class rdf:ID="chart">



<rdfs:subClassOf rdf:resource="#group"/>



<role:relatedConcept
rdf:resource="http://www.w3.org/TR/html4/struct/tables.html#edef-TABLE"/>



<dc:description xml:lang="en">A chart is a visual presentation of a
group of data. </dc:description>



</owl:Class>



<owl:Class rdf:ID="chartsection">



<rdfs:subClassOf rdf:resource="#section"/>



<role:relatedConcept
rdf:resource="http://www.w3.org/TR/html4/struct/tables.html#edef-TD"/>



<dc:description xml:lang="en">A chartsection is a section of a
chart</dc:description>



<role:scope rdf:resource="chart"/>



</owl:Class>



<owl:Class rdf:ID="grid">



<rdfs:subClassOf rdf:resource="#group"/>



<role:relatedConcept
rdf:resource="http://www.w3.org/TR/html4/struct/tables.html#edef-TABLE"/>



<dc:description xml:lang="en">A grid is a visual presentation of a
group of data </dc:description>



</owl:Class>



<owl:Class rdf:ID="gridcell">



<rdfs:subClassOf rdf:resource="#section"/>



<role:relatedConcept
rdf:resource="http://www.w3.org/TR/html4/struct/tables.html#edef-TD"/>



<dc:description xml:lang="en">A gridcell is a section inside a
grid</dc:description>



<role:scope rdf:resource="grid"/>



</owl:Class>



<owl:Class rdf:ID="tab">



<rdfs:subClassOf rdf:resource="#sectionhead"/>



<dc:description xml:lang="en">A tab is the header for a
tabpanel.</dc:description>



<role:scope rdf:resource="tabpanel"/>



</owl:Class>



<owl:Class rdf:ID="tabpanel">



<rdfs:subClassOf rdf:resource="#section"/>



<dc:description xml:lang="en">A tabpanel is a section of a group with a
tab. </dc:description>



</owl:Class>



<owl:Class rdf:ID="tablist">



<rdfs:subClassOf rdf:resource="#grouplist"/>



<role:scope rdf:resource="tab"/>



<dc:description xml:lang="en">A tablist is a list of names or short
descriptions of tabs in a group.</dc:description>



</owl:Class>



<owl:Class rdf:ID="table">



<rdfs:subClassOf rdf:resource="#group"/>



<role:relatedConcept
rdf:resource="http://www.w3.org/TR/html4/struct/tables.html#edef-TABLE"/>



<dc:description xml:lang="en">A table is avisual presentation of a
group of data. A table contains cells of tabular data arranged in rows and
columns.</dc:description>



</owl:Class>



<owl:Class rdf:ID="td">



<rdfs:subClassOf rdf:resource="#section"/>



<role:relatedConcept
rdf:resource="http://www.w3.org/TR/html4/struct/tables.html#edef-TD"/>



<dc:description xml:lang="en">A td is a table cell containing data and
is a small section a table.</dc:description>



<role:scope rdf:resource="#table"/>



</owl:Class>



<owl:Class rdf:ID="th">



<rdfs:subClassOf rdf:resource="#td"/>



<rdfs:subClassOf rdf:resource="#sectionheader"/>



<role:relatedConcept
rdf:resource="http://www.w3.org/TR/html4/struct/tables.html#edef-TH"/>



<dc:description xml:lang="en">A th is a table cell containing data that
acts as a heading for a group of table cells.</dc:description>



<role:scope rdf:resource="#table"/>



</owl:Class>



<owl:Class rdf:ID="col">



<rdfs:subClassOf rdf:resource="#group"/>



<role:relatedConcept
rdf:resource="http://www.w3.org/TR/html4/struct/tables.html#edef-COL"/>



<dc:description xml:lang="en">A col is a section of a table containing
table cells. A col is also visual presentation of a group of table cells
arranged in a column.</dc:description>



<role:scope rdf:resource="#table"/>



<role:mustContain rdf:resource="#td"/>



</owl:Class>



<owl:Class rdf:ID="row">



<rdfs:subClassOf rdf:resource="#group"/>



<role:relatedConcept
rdf:resource="http://www.w3.org/TR/html4/struct/tables.html#rowgroups"/>



<dc:description xml:lang="en">A row is a section of a table containing
table cells. A row is also visual presentation of a group of table cells
arranged in a row.</dc:description>



<role:mustContain rdf:resource="#td"/>



<role:scope rdf:resource="#table"/>



</owl:Class>



<owl:Class rdf:ID="linkblock">



<rdfs:subClassOf rdf:resource="#list"/>



<dc:description xml:lang="en">A linkblock is a group or list of
links</dc:description>



<role:mustContain rdf:resource="#link"/>



</owl:Class>



<owl:Class rdf:ID="menu">



<rdfs:subClassOf rdf:resource="#linkblock"/>



<dc:description xml:lang="en">A menu is a block of
links.</dc:description>



<role:relatedConcept>See navigation in XHTML roles,
See://www.w3.org/TR/2005/WD-xhtml2-20050527/mod-role.html#col_Role</role:relatedConcept>



<role:relatedConcept
rdf:resource="http://www.loc.gov/nls/z3986/v100/dtbook110doc.htm#sidebar"/>



</owl:Class>



<owl:Class rdf:ID="menuitem">



<rdfs:subClassOf rdf:resource="#listitem"/>



<role:scope rdf:resource="#menu"/>



<dc:description xml:lang="en">A menu item is an item or link inside a
menu.</dc:description>



</owl:Class>



<owl:Class rdf:ID="menubar">



<rdfs:subClassOf rdf:resource="#menu"/>



<dc:description xml:lang="en">A menu bar is a visual presentation of a
menu.</dc:description>



</owl:Class>



<owl:Class rdf:ID="mainmenu">



<rdfs:subClassOf rdf:resource="#menu"/>



<role:importance>1</role:importance>



<dc:description xml:lang="en">A mainmenu is a menu containing the most
important links in a page or document.</dc:description>



</owl:Class>



<owl:Class rdf:ID="submenu1">



<rdfs:subClassOf rdf:resource="#menu"/>



<role:importance>0.7</role:importance>



<dc:description xml:lang="en">Submenu1 is a sub menu containing links
on a page or document that may be important.</dc:description>



</owl:Class>



<owl:Class rdf:ID="submenu2">



<rdfs:subClassOf rdf:resource="#menu"/>



<role:importance>0.4</role:importance>



<dc:description xml:lang="en">A submenu2 is a less important sub
menu.</dc:description>



</owl:Class>



<owl:Class rdf:ID="submenutrivia">



<rdfs:subClassOf rdf:resource="#menu"/>



<role:importance>0.2</role:importance>



<dc:description xml:lang="en">A submenutrivia is a sub menu that is not
important to the main tasks of a site, document or
page.</dc:description>



</owl:Class>



<owl:Class rdf:ID="toolbar">



<rdfs:subClassOf rdf:resource="#menu"/>



<role:importance>0.8</role:importance>



<dc:description xml:lang="en">A toolbar is a type of menu where icons
are toggle-able or menu items and icons are not
focusable</dc:description>



</owl:Class>



<owl:Class rdf:ID="footer">



<rdfs:subClassOf rdf:resource="#section"/>



<role:importance>0.2</role:importance>



<dc:description xml:lang="en">A footer is (small) text at the end of a
page - typically copyright and similar information. A footer may contain
links.</dc:description>



<role:relatedConcept>See contentinfo, copyrightin XHTML roles,
See://www.w3.org/TR/2005/WD-xhtml2-20050527/mod-role.html#col_Role</role:relatedConcept>



</owl:Class>



<owl:Class rdf:ID="footermenusite">

<rdfs:subClassOf rdf:resource="#menu"/>

<rdfs:subClassOf rdf:resource="#footer"/>



<role:importance>0.8</role:importance>



<dc:description xml:lang="en">A footermenusite is a menu found at the
bottom of a page important on-site links. Typically a footermenusite includes
a link to a "contact us" page and other important site's
pages.</dc:description>



</owl:Class>



<owl:Class rdf:ID="sectionheader">



<rdfs:subClassOf rdf:resource="#section"/>



<dc:description xml:lang="en">A sectionheader is the header od a
section.</dc:description>



<role:relatedConcept>See HTML Headings -
://www.w3.org/TR/html4/struct/global.html#edef-H1</role:relatedConcept>



<role:relatedConcept
rdf:resource="http://www.loc.gov/nls/z3986/v100/dtbook110doc.htm#levelhd"/>



</owl:Class>



<owl:Class rdf:ID="heading1">



<rdfs:subClassOf rdf:resource="#sectionheader"/>



<role:importance>1</role:importance>



<dc:description xml:lang="en">A heading1 is a level 1 section heading
.</dc:description>



<role:baseConcept
rdf:resource="http://www.w3.org/TR/html4/struct/global.html#edef-H1"/>



</owl:Class>



<owl:Class rdf:ID="heading2">



<rdfs:subClassOf rdf:resource="#sectionheader"/>



<role:importance>0.9</role:importance>



<dc:description xml:lang="en">A headings is a level 2 section heading
.</dc:description>



<role:baseConcept
rdf:resource="http://www.w3.org/TR/html4/struct/global.html#edef-H2"/>



</owl:Class>



<owl:Class rdf:ID="heading3">



<rdfs:subClassOf rdf:resource="#SectionHeader"/>



<role:importance>0.8</role:importance>



<dc:description xml:lang="en">A heading3 is a level 3 section heading
.</dc:description>



<role:baseConcept
rdf:resource="http://www.w3.org/TR/html4/struct/global.html#edef-H3"/>



</owl:Class>



<owl:Class rdf:ID="heading4">



<rdfs:subClassOf rdf:resource="#sectionheader"/>



<role:importance>0.7</role:importance>



<dc:description xml:lang="en">A heading4 is a level 4 section heading
.</dc:description>



<role:baseConcept
rdf:resource="http://www.w3.org/TR/html4/struct/global.html#edef-H4"/>



</owl:Class>



<owl:Class rdf:ID="heading5">



<rdfs:subClassOf rdf:resource="#sectionheader"/>



<role:importance>0.6</role:importance>



<dc:description xml:lang="en">A heading5 is a level 5 section heading
.</dc:description>



<role:baseConcept
rdf:resource="http://www.w3.org/TR/html4/struct/global.html#edef-H5"/>



</owl:Class>



<owl:Class rdf:ID="heading6">



<rdfs:subClassOf rdf:resource="#sectionheader"/>



<role:importance>0.5</role:importance>



<dc:description xml:lang="en">A heading6 is a level 6 section heading
.</dc:description>



<role:baseConcept
rdf:resource="http://www.w3.org/TR/html4/struct/global.html#edef-H6"/>



</owl:Class>



</rdf:RDF>

Role Taxonomy for Accessible Adaptable Applications

An RDF Role taxonomy with Qname support for Accessible Adaptable XML Applications

PFWG Editor's Draft 06 November 2005

Abstract