Input: [Widget Role] Checkboxtristate [Description] A control that has three possible states, (1 0 -1) Often found in installer where an option has been partially installed [Inherited Concepts] Checkbox Checked="true"|"false"|"mixed" [Inherited states] Disable zoom selected [nameRef]

Output: Child content title

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


Input: [Widget Role] Radio [Description] A radio is an option in single-select list. [Inherited Concepts] Checkbox [Base and Related Concepts] HTML input (type : radio) [Inherited states] Disable zoom selected checked="true"|"false" [nameRef]

Output: Child content title

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


Input: [Widget Role] Radiogroup [Description] Maybe, we would rather have a generic "group of choices" type. [Inherited Concepts] Select [Inherited states] Disable zoom selected multiselectable [nameRef]

Output: Title

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


Input: [Widget Role] Button [Description] Allows for user-triggered actions. [Inherited Concepts] Widget Link [Base and Related Concepts] XFORMS trigger Pressed [Inherited states] Disable zoom [nameRef]

Output: Child conteny title

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


Input: [Widget Role] Buttonsubmit [Description] This form control initiates submission of all or part of the instance data to which it is bound [Inherited Concepts] Button [Base and Related Concepts] HTML input (type :submit) [Inherited states] Disable zoom pressed [nameRef]

Output: Child conteny title

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


Input: [Widget Role] Buttoncancel [Description] This button initiates closing a window or leaving a form (e.g. To another page) without submission [Inherited Concepts] Button [Inherited states] Disable zoom pressed [nameRef]

Output: Child content title

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


Input: [Widget Role] Buttonundo [Description] This control brings a form to the initial state (e.g. returns all default values to all inputs) [Inherited Concepts] Button [Base and Related Concepts] HTML input (type : reset) [Inherited states] Disable zoom pressed [nameRef]

Output: Child content title

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


Input: [Widget Role] Buttonback [Description] Brings user-agent to the previous page or state [Inherited Concepts] Button [Base and Related Concepts] HTML Link [Inherited states] Disable zoom pressed [nameRef]

Output: Child content title

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


Input: [Widget Role] MenuItemradio [Description] How it differs from radio? [Inherited Concepts] Menuitem (see structure) Radio [Inherited states] Disable zoom selected checked="true"|"false" [nameRef]

Output: Child content title

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


Input: [Widget Role] MenuItemcheckbox [Description] How it differs from Checkbox? Isn't it defined by its parent's role? [Inherited Concepts] Menuitem Checkbox [Inherited states] Disable zoom selected checked="true"|"false" [nameRef]

Output: Title

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


Input: [Widget Role] Progressbar [Description] Used by applications for tasks that take a long time to execute, to show the execution progress. [Inherited Concepts] Widget [Inherited states] Disable zoom [nameRef]

Output: Title

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


Input: [Widget Role] Hidden [Description] 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". [Inherited Concepts] Input [Base and Related Concepts] [HTML] input (type : hidden) [Inherited states] Disable zoom [nameRef]

Output: Title

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


Input: [Widget Role] Secret [Description] 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. [Inherited Concepts] Input [Base and Related Concepts] [HTML] input (type : password) [Inherited states] Disable zoom [nameRef]

Output: Title

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


Input: [Widget Role] Separator [Description] A line or bar that separates and distinguishes sections of content [Inherited Concepts] Widget [Base and Related Concepts] [HTML] hr [Inherited states] Disable zoom [nameRef]

Output: Title

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


Input: [Widget Role] Range [Description] Represents a range of values that can be set by the user. [Inherited Concepts] Input [Inherited states] Disable zoom [nameRef]

Output: Title

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


Input: [Widget Role] Slider [Description] 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 [Inherited Concepts] Range [Inherited states] Disable zoom [nameRef]

Output: Title

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


Input: [Widget Role] SpinButton [Description] A form of Range that expects a user selecting from discreet choices. [Inherited Concepts] Range [Inherited states] Disable zoom [nameRef]

Output: Title

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


Input: [Widget Role] Spreadsheet [Description] Interactive table where the user can enter the values [Inherited Concepts] Widget Table Multiselectable [Inherited states] Disable zoom [nameRef]

Output: Title

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


Input: [Widget Role] Textarea [Description] Intended for use in entering multi-line content [Inherited Concepts] TextBox [Base and Related Concepts] [HTML] textarea [Inherited states] Disable zoom [nameRef]

Output: Title

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


Input: [Widget Role] Textfield [Description] Free-form data entry for short on-line content. [Inherited Concepts] TextBox [Base and Related Concepts] [HTML] input (type : text) [Inherited states] Disable zoom [nameRef]

Output: Child content title

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


Input: [Widget Role] Tree [Description] A form of a Select (or, generally, of a list having groups inside groups) - where sub trees can be collapsed and expanded [Inherited Concepts] Select Chart Expanded [Inherited states] Disable zoom multiselectable [nameRef]

Output: Child content title

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


Input: [Widget Role] Treeitem [Description] An option item of a tree. [Inherited Concepts] Option [Inherited states] Disable zoom selected [nameRef]

Output: Content child title

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


Input: [Widget Role] Alert [Description] A message with an alert or error information [Inherited Concepts] Window (see structure) Dialog [Base and Related Concepts] XFORMS alert [Inherited states] Disable zoom [nameRef]

Output: Title

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


Input: [Widget Role] Dialog [Description] A small application window [Inherited Concepts] Window [Inherited states] Disable zoom [nameRef]

Output: Title

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


Input: [Widget Role] Input [Inherited Concepts] Widget [Inherited states] Disable zoom [nameRef] Title [Description]

Output: Generic type for widgets that can have a value

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


Input: [Widget Role] Textbox [Inherited Concepts] Input [Base and Related Concepts] XFORMS input [Inherited states] Disable zoom [nameRef] Title [Description]

Output: Generic type for the inputs that allow free-form text, as their value

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


Input: [Widget Role] Link [Inherited Concepts] Widget [Base and Related Concepts] HTML Link [Inherited states] Disable zoom [nameRef] Child content title [Description]

Output: Interactive reference to a resource (note, that in [HTML] 2 any element can have an href attribute and thus be a link)

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


Input: [Widget Role] Select [Inherited Concepts] Input List (see structure) Multiselectable [Inherited states] Disable zoom [nameRef] Title [Description]

Output: A form control that allows the user to make selections from a set of choices

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


Input: [Widget Role] Combobox [Inherited Concepts] Select [Base and Related Concepts] HTML select (multiple) [Inherited states] Disable zoom multiselectable [nameRef] Title [Description]

Output: 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.

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


Input: [Widget Role] Option [Inherited Concepts] Input ListItem (see structure) [Base and Related Concepts] ListItem(see structure), HTML option, XForms item Selected [Inherited states] Disable zoom [nameRef] Child content title [Description]

Output: A selectable item in a list represented by a Select.

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


Input: [Widget Role] Checkbox [Inherited Concepts] Option [Base and Related Concepts] HTML input (type : checkbox) Checked="true"|"false" [Inherited states] Disable zoom selected [nameRef] Child content title [Description]

Output: A control that has two possible states, an equivalent to a boolean

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


Input: [Widget Role] Checkboxtristate [Inherited Concepts] Checkbox Checked="true"|"false"|"mixed" [Inherited states] Disable zoom selected [nameRef] Child content title [Description]

Output: A control that has three possible states, (1 0 -1) Often found in installer where an option has been partially installed

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


Input: [Widget Role] Radio [Inherited Concepts] Checkbox [Base and Related Concepts] HTML input (type : radio) [Inherited states] Disable zoom selected checked="true"|"false" [nameRef] Child content title [Description]

Output: A radio is an option in single-select list.

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


Input: [Widget Role] Radiogroup [Inherited Concepts] Select [Inherited states] Disable zoom selected multiselectable [nameRef] Title [Description]

Output: Maybe, we would rather have a generic "group of choices" type.

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


Input: [Widget Role] Button [Inherited Concepts] Widget Link [Base and Related Concepts] XFORMS trigger Pressed [Inherited states] Disable zoom [nameRef] Child conteny title [Description]

Output: Allows for user-triggered actions.

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


Input: [Widget Role] Buttonsubmit [Inherited Concepts] Button [Base and Related Concepts] HTML input (type :submit) [Inherited states] Disable zoom pressed [nameRef] Child conteny title [Description]

Output: This form control initiates submission of all or part of the instance data to which it is bound

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


Input: [Widget Role] Buttoncancel [Inherited Concepts] Button [Inherited states] Disable zoom pressed [nameRef] Child content title [Description]

Output: This button initiates closing a window or leaving a form (e.g. To another page) without submission

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


Input: [Widget Role] Buttonundo [Inherited Concepts] Button [Base and Related Concepts] HTML input (type : reset) [Inherited states] Disable zoom pressed [nameRef] Child content title [Description]

Output: This control brings a form to the initial state (e.g. returns all default values to all inputs)

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


Input: [Widget Role] Buttonback [Inherited Concepts] Button [Base and Related Concepts] HTML Link [Inherited states] Disable zoom pressed [nameRef] Child content title [Description]

Output: Brings user-agent to the previous page or state

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


Input: [Widget Role] MenuItemradio [Inherited Concepts] Menuitem (see structure) Radio [Inherited states] Disable zoom selected checked="true"|"false" [nameRef] Child content title [Description]

Output: How it differs from radio?

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


Input: [Widget Role] MenuItemcheckbox [Inherited Concepts] Menuitem Checkbox [Inherited states] Disable zoom selected checked="true"|"false" [nameRef] Title [Description]

Output: How it differs from Checkbox? Isn't it defined by its parent's role?

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


Input: [Widget Role] Progressbar [Inherited Concepts] Widget [Inherited states] Disable zoom [nameRef] Title [Description]

Output: Used by applications for tasks that take a long time to execute, to show the execution progress.

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


Input: [Widget Role] Hidden [Inherited Concepts] Input [Base and Related Concepts] [HTML] input (type : hidden) [Inherited states] Disable zoom [nameRef] Title [Description]

Output: 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".

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


Input: [Widget Role] Secret [Inherited Concepts] Input [Base and Related Concepts] [HTML] input (type : password) [Inherited states] Disable zoom [nameRef] Title [Description]

Output: 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.

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


Input: [Widget Role] Separator [Inherited Concepts] Widget [Base and Related Concepts] [HTML] hr [Inherited states] Disable zoom [nameRef] Title [Description]

Output: A line or bar that separates and distinguishes sections of content

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


Input: [Widget Role] Range [Inherited Concepts] Input [Inherited states] Disable zoom [nameRef] Title [Description]

Output: Represents a range of values that can be set by the user.

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


Input: [Widget Role] Slider [Inherited Concepts] Range [Inherited states] Disable zoom [nameRef] Title [Description]

Output: 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

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


Input: [Widget Role] SpinButton [Inherited Concepts] Range [Inherited states] Disable zoom [nameRef] Title [Description]

Output: A form of Range that expects a user selecting from discreet choices.

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


Input: [Widget Role] Spreadsheet [Inherited Concepts] Widget Table Multiselectable [Inherited states] Disable zoom [nameRef] Title [Description]

Output: Interactive table where the user can enter the values

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


Input: [Widget Role] Textarea [Inherited Concepts] TextBox [Base and Related Concepts] [HTML] textarea [Inherited states] Disable zoom [nameRef] Title [Description]

Output: Intended for use in entering multi-line content

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


Input: [Widget Role] Textfield [Inherited Concepts] TextBox [Base and Related Concepts] [HTML] input (type : text) [Inherited states] Disable zoom [nameRef] Child content title [Description]

Output: Free-form data entry for short on-line content.

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


Input: [Widget Role] Tree [Inherited Concepts] Select Chart Expanded [Inherited states] Disable zoom multiselectable [nameRef] Child content title [Description]

Output: A form of a Select (or, generally, of a list having groups inside groups) - where sub trees can be collapsed and expanded

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


Input: [Widget Role] Treeitem [Inherited Concepts] Option [Inherited states] Disable zoom selected [nameRef] Content child title [Description]

Output: An option item of a tree.

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


Input: [Widget Role] Alert [Inherited Concepts] Window (see structure) Dialog [Base and Related Concepts] XFORMS alert [Inherited states] Disable zoom [nameRef] Title [Description]

Output: A message with an alert or error information

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


Input: [Widget Role] Dialog [Inherited Concepts] Window [Inherited states] Disable zoom [nameRef] Title [Description]

Output: A small application window

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


Input: [Property] supportedState [Values] Any valid RDF object reference, such as a URI. [Description]

Output: a supportedState must be supported by this role. Typically refers to states from the SAP namespace

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


Input: [Property] mustContain [Values] Any valid RDF object reference, such as a URI or RDF ID. [Related Concepts] http://www.w3.org/2004/02/skos/core#subject [Description]

Output: A child element that must be contained by this role. For example a list must contain a listitem.

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


Input: [Property] scope [Values] Any valid RDF object reference, such as a URI or RDF ID. [Related Concepts] http://www.w3.org/2004/02/skos/core#Concept [Description]

Output: Context, where this role is allowed. For example a list item is allowed inside a list.

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


Input: [Property] media [Values] Any valid RDF object reference, such as a URI or RDF ID. [Related Concepts] baseConcept: DC: Format XFORMS media type [Description]

Output: The media type, where the Role is allowed - a type of scope

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


Input: [Property] importance [Values] 0 (min) 1 (max) [Description]

Output: 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.

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


Input: [Property] nameRef [Values] Any valid RDF object reference, such as a URI or RDF ID. Recomended values: Child, title, content. [Description]

Output: How a role type name is extracted and referenced inside a document. For example the DOM might reference a role by it's title.

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


Input: [Type] String [Description] Returns whether the time said by the caller was AM or PM [Return value]

Output: AM_PM


Input: [Type] java.util.Calendar [Description] Returns the time in a Calendar representation [Return value]

Output: Calendar


Input: [Type] int [Description] A numerical representation of the time [Return value]

Output: ClockTime


Input: [Type] Playable [Description] The time as a Playable in the standard format (with trailing "am" or "pm") [Return value]

Output: ClockTimePlayable


Input: [Type] int [Description] The hour portion of the time said by the caller [Return value]

Output: Hours


Input: [Type] int [Description] The minutes portion of the time said by the caller [Return value]

Output: Minutes


Input: [Type] Playable [Description] A time Playable in the "intelligent" (colloquial) format (for example, "7 in the evening", "5 in the morning", "noon") [Return value]

Output: SmartTimePlayable


Input: [Type] String [Description] Any user-stated modifier that disambiguated the time [Return value]

Output: UserStatedModifier


Input: [anyURI Name] Success [Final] Final [Description]

Output: The operation succeeded.

XML Key Management Specification (XKMS 2.0)


Input: [anyURI Name] VersionMismatch [Final] Final [Description]

Output: The service does not support the protocol version specified in the request.

XML Key Management Specification (XKMS 2.0)


Input: [anyURI Name] Sender [Final] Final [Description]

Output: An error occurred that was due to the message sent by the sender.

XML Key Management Specification (XKMS 2.0)


Input: [anyURI Name] Receiver [Final] Final [Description]

Output: An error occurred at the receiver.

XML Key Management Specification (XKMS 2.0)


Input: [anyURI Name] Represent [Final] Not Final [Description]

Output: The service has not acted on the request. In order for the request to be acted upon the request MUST be represented with the specified nonce in accordance with the two-phase protocol.

XML Key Management Specification (XKMS 2.0)


Input: [anyURI Name] Pending [Final] Not Final [Description]

Output: The request has been accepted for processing and the service will return the result asynchronously.

XML Key Management Specification (XKMS 2.0)


Input: [Bugzilla bug (if applicable)] Bugzilla bug 6535 [Erratum (if applicable)] None [Description of change] Added definition of the suppress-indentation serialization parameter. [Affected sections] 3 Serialization Parameters 4 Phases of Serialization 5.1.4 XML Output Method: the indent and suppress-indentation Parameters 6.1.4 XHTML Output Method: the indent and suppress-indentation Parameters 7.4.3 HTML Output Method: the indent and suppress-indentation Parameters 8.1.4 Text Output Method: the indent and suppress-indentation Parameters [Category]

Output: Substantive


Input: [Bugzilla bug (if applicable)] Bugzilla bug 7829 [Erratum (if applicable)] SE.E14 [Description of change] Clarified how minimized attributes are handled under the rules of the HTML output method. [Affected sections] 7.2 Writing Attributes [Category]

Output: Substantive


Input: [Bugzilla bug (if applicable)] Bugzilla bug 8245 [Erratum (if applicable)] SE.E15 [Description of change] Corrected description of a serialization error that mentions which control characters are not permitted under the rules of the HTML output method [Affected sections] 7.3 Writing Character Data C Summary of Error Conditions [Category]

Output: Editorial


Input: [Bugzilla bug (if applicable)] Bugzilla bug 7823 [Erratum (if applicable)] SE.E16 [Description of change] Clarified how the script and style elements are handled for the HTML output method. [Affected sections] 7.1 Markup for Elements [Category]

Output: Substantive


Input: [Bugzilla bug (if applicable)] Bugzilla bug 8651 [Erratum (if applicable)] SE.E17 [Description of change] Clarified what it means to compare without regard to case. [Affected sections] 1.1 Terminology 6.1.14 XHTML Output Method: the include-content-type Parameter 7.1 Markup for Elements 7.2 Writing Attributes 7.4.13 HTML Output Method: the include-content-type Parameter [Category]

Output: Substantive


Input: [Bugzilla bug (if applicable)] Bugzilla bug 8206 [Erratum (if applicable)] SE.E18 [Description of change] Clarified what it means to escape according to HTML or XML rules. [Affected sections] 4 Phases of Serialization [Category]

Output: Editorial


Input: [Bugzilla bug (if applicable)] Bugzilla bug 6808 [Erratum (if applicable)] None [Description of change] Relaxed rules for the XML output method that specify where a serializer is permitted to add whitespace. This introduces an incompatibility only inasmuch as the serialized results produced by a serializer conforming to this specification could differ from the results a serializer that adheres to [XSLT 2.0 and XQuery 1.0 Serialization (Second Edition)] would be permitted to produce. [Affected sections] 5.1.4 XML Output Method: the indent and suppress-indentation Parameters [Category]

Output: Substantive


Input: [Bugzilla bug (if applicable)] Bugzilla bug 9302 [Erratum (if applicable)] None [Description of change] Defined a mechanism for specifying serialization parameter settings in the form of a data model instance. [Affected sections] 3.1 Setting Serialization Parameters by Means of a Data Model Instance [Category]

Output: Substantive


Input: [Bugzilla bug (if applicable)] None [Erratum (if applicable)] None [Description of change] Replaced all uses of the words legal and illegal with more appropriate terms. [Category]

Output: Editorial


Input: [ID] 1 [Location] 3.2.3.5 The dir attribute [Subject] Rendering bidi without a style sheet [Owner] RI [WG] Y [Ed. / Subs.] S [8] EditDelete [Comment]

Output: "The processing of this attribute depends on the presentation layer. For example, CSS 2.1 defines a mapping from this attribute to the CSS 'direction' and 'unicode-bidi' properties, and defines rendering in terms of those properties." We think that HTML 5, like HTML 4, should be able to render bidirectional text without a style sheet. It would break backwards compatibility to remove the ability of a browser to do so without CSS. Therefore in our opinion, HTML 5 has to describe the expected behavior in at least the detail of HTML 4 rather than leave it up to the "presentation layer". Note that we do not want to impose a requirement on implementations of HTML 5 to implement CSS, but you could describe the expected behaviour by just referencing CSS and defining a default stylesheet fragment. This would just mean that an HTML 5 implementation has to make things behave as if it used this CSS default stylesheet fragment


Input: [ID] 2 [Location] 4.6.21 The bdo element [Subject] bdo element doesn't leave rendering up to presentation layer [Owner] RI [WG] Y [Ed. / Subs.] S [8] EditDelete [Comment]

Output: "If the element has the dir attribute set to the exact value ltr, then for the purposes of the bidi algorithm, the user agent must act as if there was a U+202D LEFT-TO-RIGHT OVERRIDE character at the start of the element, and a U+202C POP DIRECTIONAL FORMATTING at the end of the element." "If the element has the dir attribute set to the exact value rtl, then for the purposes of the bidi algorithm, the user agent must act as if there was a U+202E RIGHT-TO-LEFT OVERRIDE character at the start of the element, and a U+202C POP DIRECTIONAL FORMATTING at the end of the element." The section about the element does *not* leave the expected behavior completely up to the presentation layer - which is confusing. Content authors need to know if they should use CSS, if CSS would override the specified behavior etc.


Input: [ID] 3 [Location] 3.2.3.5 The dir attribute [Subject] Add note about using bidi constructs in content [Owner] RI [WG] Y [Ed. / Subs.] E [8] EditDelete [Comment]

Output: We propose that you add a note making clear that using the directional markup provided by HTML5 is is better than attaching CSS styling to arbitrary markup such as etc., since information encoded in this way will apply to the content whether the CSS is used or not.


Input: [ID] 4 [Location] 3.2.3.5 The dir attribute [Subject] rlo and lro attribute values [Owner] RI [WG] Y [Ed. / Subs.] S [8] EditDelete [Comment]

Output: Please consider allowing two new attribute values for the "dir" attribute: 'rlo' and 'lro' for dir. You do not need to remove the bdo element, but the new values will allow content authors to proceed to a scenario we described in the ITS 1.0 specification, It will also provide some additional power to the authors, since they will be able to attach dir="lro" to a block element.


Input: [ID] 5 [Location] 4.2.5.3 Pragma directives [Subject] what's the language of a document [Owner] RI [WG] Y [Ed. / Subs.] S [8] EditDelete [Comment]

Output: Our proposal is as follows and is based on the text of the following sections: http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#document-wide-default-language http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html#the-lang-and-xml:lang-attributes [1] Explain clearly that declarations in the http header and the meta element refer to the document as an object, rather than the text in a specific element (this is what makes the distinction between single and multiple values sensible). [2] Continue to recommend that the document-wide default language be defined by a lang attribute on the html tag, but say that if the lang attribute is missing and there is a language defined in the http or meta, then those language declarations can be used to guess the language of the text, if they contain a single value. [3] Establish the precedence between http vs meta. [4] Establish the rule that multiple values in the place that has precedence equates to lang="". This is very close to what we already have, but doesn't try to make the meta declaration a different thing than the http declaration, or change it so that multiple values are no longer valid. At the same time, it allows either the http or the meta to provide language information for text-processing, if the declaration is useable. We also feel that the spec seems to restrict the use of the term 'document-wide default language' to refer only to a language declared using the meta, and this is rather odd. We feel that in fact the lang attribute on the html element also establishes a document-wide default language. (See the text: "Until the pragma is successfully processed, there is no document-wide default language.") Update: This comment became part of ISSUE-88.


Input: [ID] 6 [Location] 4.6.18 The ruby element [Subject] ruby code samples [Owner] RI [WG] - [Ed. / Subs.] E [8] EditDelete [Comment]

Output: The code samples in the ruby section are misleading because they show white-space between the components that should not be there. eg. ... 漢 かん 字 じ ... Either show the examples as the code should look, eg. ... 漢かん字じ ... or add a note to say that the extra white space is there to show the structure clearly, but should not be copied. Similar comments apply to the examples in the rp section that follows.


Input: [ID] 7 [Location] 4.6.18 The ruby element [Subject] Please add support for rb [Owner] RI [WG] - [Ed. / Subs.] E [8] EditDelete [Comment]

Output: In all the web sites that we looked at that currently use ruby markup in the wild, over 90% of code uses the rb tag. The current HTML5 model for ruby simplifies the code generally, but making the rb element obsolete will make most existing ruby code non-conformant and make it more difficult to copy code that follows the Ruby Annotation model, from XML or other formats, into HTML5. Please allow optional use of the rb element as part of the HTML5 model.


Input: [ID] 8 [Location] 4.2.5.5 Specifying the document's character encoding [Subject] Allow utf-16 encoding declarations [Owner] RI [WG] - [Ed. / Subs.] E [8] EditDelete [Comment]

Output: Currently you are not allowed to use or the equivalent pragma directive in utf-16 encoded documents. While logically it is not needed to identify the character encoding, it introduces a special case for authors to remember, and almost certainly many authors will be unaware that this is disallowed and will do it. In addition, in-document declarations of this kind are particularly useful for developers, testers, or translation production managers who want to visually check the encoding of a document (since the bom cannot be seen). Furthermore, there would appear to be no risk incurred by allowing this, since the document would be encoded in utf-16 anyway. Note that the ask is not that the encoding of the document be determined by the meta element - the bom remains the way of determining that information - solely that no error or warning be raised if the meta element is used. Please make an exception in the spec for utf-16 so that it is allowed to use or the equivalent pragma directive in utf-16 encoded documents.


Input: [Definition] Character data [Attribute Type]

Output: CDATA


Input: [Definition] A document-unique identifier [Attribute Type]

Output: ID


Input: [Definition] A reference to a document-unique identifier [Attribute Type]

Output: IDREF


Input: [Definition] A space-separated list of references to document-unique identifiers [Attribute Type]

Output: IDREFS


Input: [Definition] A name with the same character constraints as ID above [Attribute Type]

Output: NAME


Input: [Definition] A name composed of only name tokens as defined in XML 1.0 [XML] [Attribute Type]

Output: NMTOKEN


Input: [Definition] One or more whitespace separated NMTOKEN values [Attribute Type]

Output: NMTOKENS


Input: [Definition] Processed character data [Attribute Type]

Output: PCDATA


Input: [State] Hidden [Data type] An arbitrary string [Control type] n/a [Keyword]

Output: hidden


Input: [State] Text [Data type] Text with no line breaks [Control type] Text field [Keyword]

Output: text


Input: [State] Search [Data type] Text with no line breaks [Control type] Search field [Keyword]

Output: search


Input: [State] Telephone [Data type] Text with no line breaks [Control type] A text field [Keyword]

Output: tel


Input: [State] URL [Data type] An absolute IRI [Control type] A text field [Keyword]

Output: url


Input: [State] E-mail [Data type] An e-mail address or list of e-mail addresses [Control type] A text field [Keyword]

Output: email


Input: [State] Password [Data type] Text with no line breaks (sensitive information) [Control type] Text field that obscures data entry [Keyword]

Output: password


Input: [State] Date and Time [Data type] A date and time (year, month, day, hour, minute, second, fraction of a second) with the time zone set to UTC [Control type] A date and time control [Keyword]

Output: datetime


Input: [State] Date [Data type] A date (year, month, day) with no time zone [Control type] A date control [Keyword]

Output: date


Input: [State] Month [Data type] A date consisting of a year and a month with no time zone [Control type] A month control [Keyword]

Output: month


Input: [State] Week [Data type] A date consisting of a week-year number and a week number with no time zone [Control type] A week control [Keyword]

Output: week


Input: [State] Time [Data type] A time (hour, minute, seconds, fractional seconds) with no time zone [Control type] A time control [Keyword]

Output: time


Input: [State] Local Date and Time [Data type] A date and time (year, month, day, hour, minute, second, fraction of a second) with no time zone [Control type] A date and time control [Keyword]

Output: datetime-local


Input: [State] Number [Data type] A numerical value [Control type] A text field or spinner control [Keyword]

Output: number


Input: [State] Range [Data type] A numerical value, with the extra semantic that the exact value is not important [Control type] A slider control or similar [Keyword]

Output: range


Input: [State] Color [Data type] An sRGB color with 8-bit red, green, and blue components [Control type] A color well [Keyword]

Output: color


Input: [State] Checkbox [Data type] A set of zero or more values from a predefined list [Control type] A checkbox [Keyword]

Output: checkbox


Input: [State] Radio Button [Data type] An enumerated value [Control type] A radio button [Keyword]

Output: radio


Input: [State] File Upload [Data type] Zero or more files each with a MIME type and optionally a file name [Control type] A label and a button [Keyword]

Output: file


Input: [State] Submit Button [Data type] An enumerated value, with the extra semantic that it must be the last value selected and initiates form submission [Control type] A button [Keyword]

Output: submit


Input: [State] Image Button [Data type] A coordinate, relative to a particular image's size, with the extra semantic that it must be the last value selected and initiates form submission [Control type] Either a clickable image, or a button [Keyword]

Output: image


Input: [State] Reset Button [Data type] n/a [Control type] A button [Keyword]

Output: reset


Input: [State] Button [Data type] n/a [Control type] A button [Keyword]

Output: button


Input: [Definition] Character data [Attribute Type]

Output: CDATA

XHTML Modularization 1.1 - Defining Abstract Modules


Input: [Definition] A document-unique identifier [Attribute Type]

Output: ID

XHTML Modularization 1.1 - Defining Abstract Modules


Input: [Definition] A reference to a document-unique identifier [Attribute Type]

Output: IDREF

XHTML Modularization 1.1 - Defining Abstract Modules


Input: [Definition] A space-separated list of references to document-unique identifiers [Attribute Type]

Output: IDREFS

XHTML Modularization 1.1 - Defining Abstract Modules


Input: [Definition] A name with the same character constraints as ID above [Attribute Type]

Output: NAME

XHTML Modularization 1.1 - Defining Abstract Modules


Input: [Definition] A name composed of only name tokens as defined in XML 1.0 [XML] [Attribute Type]

Output: NMTOKEN

XHTML Modularization 1.1 - Defining Abstract Modules


Input: [Definition] One or more white space separated NMTOKEN values [Attribute Type]

Output: NMTOKENS

XHTML Modularization 1.1 - Defining Abstract Modules


Input: [Bugzilla bug (if applicable)] Bugzilla bug 6535 [Erratum (if applicable)] None [Category] Substantive [Affected sections] 3 Serialization Parameters 4 Phases of Serialization 5.1.4 XML Output Method: the indent and suppress-indentation Parameters 6.1.4 XHTML Output Method: the indent and suppress-indentation Parameters 7.4.3 HTML Output Method: the indent and suppress-indentation Parameters 8.1.4 Text Output Method: the indent and suppress-indentation Parameters [Description of change]

Output: Added definition of the suppress-indentation serialization parameter.


Input: [Bugzilla bug (if applicable)] Bugzilla bug 7829 [Erratum (if applicable)] SE.E14 [Category] Substantive [Affected sections] 7.2 Writing Attributes [Description of change]

Output: Clarified how minimized attributes are handled under the rules of the HTML output method.


Input: [Bugzilla bug (if applicable)] Bugzilla bug 8245 [Erratum (if applicable)] SE.E15 [Category] Editorial [Affected sections] 7.3 Writing Character Data C Summary of Error Conditions [Description of change]

Output: Corrected description of a serialization error that mentions which control characters are not permitted under the rules of the HTML output method


Input: [Bugzilla bug (if applicable)] Bugzilla bug 7823 [Erratum (if applicable)] SE.E16 [Category] Substantive [Affected sections] 7.1 Markup for Elements [Description of change]

Output: Clarified how the script and style elements are handled for the HTML output method.


Input: [Bugzilla bug (if applicable)] Bugzilla bug 8651 [Erratum (if applicable)] SE.E17 [Category] Substantive [Affected sections] 1.1 Terminology 6.1.14 XHTML Output Method: the include-content-type Parameter 7.1 Markup for Elements 7.2 Writing Attributes 7.4.13 HTML Output Method: the include-content-type Parameter [Description of change]

Output: Clarified what it means to compare without regard to case.


Input: [Bugzilla bug (if applicable)] Bugzilla bug 8206 [Erratum (if applicable)] SE.E18 [Category] Editorial [Affected sections] 4 Phases of Serialization [Description of change]

Output: Clarified what it means to escape according to HTML or XML rules.


Input: [Bugzilla bug (if applicable)] Bugzilla bug 6808 [Erratum (if applicable)] None [Category] Substantive [Affected sections] 5.1.4 XML Output Method: the indent and suppress-indentation Parameters [Description of change]

Output: Relaxed rules for the XML output method that specify where a serializer is permitted to add whitespace. This introduces an incompatibility only inasmuch as the serialized results produced by a serializer conforming to this specification could differ from the results a serializer that adheres to [XSLT 2.0 and XQuery 1.0 Serialization (Second Edition)] would be permitted to produce.


Input: [Bugzilla bug (if applicable)] Bugzilla bug 9302 [Erratum (if applicable)] None [Category] Substantive [Affected sections] 3.1 Setting Serialization Parameters by Means of a Data Model Instance [Description of change]

Output: Defined a mechanism for specifying serialization parameter settings in the form of a data model instance.


Input: [Bugzilla bug (if applicable)] None [Erratum (if applicable)] None [Category] Editorial [Description of change]

Output: Replaced all uses of the words legal and illegal with more appropriate terms.


Input: [Property] namespace name [EXI event types]

Output: AT

Mapping of the attribute information item properties to EXI event types


Input: [Property] local name [EXI event types]

Output: AT


Input: [Property] prefix [EXI event types]

Output: AT


Input: [Property] normalized value [EXI event types]

Output: The value of AT


Input: [Property] specified [EXI event types]

Output: True if the item maps to AT, otherwise false


Input: [Property] attribute type [EXI event types]

Output: Computed based on AT and DT


Input: [Property] references [EXI event types]

Output: Computed based on attribute type and value of AT


Input: [Property] owner element [EXI event types]

Output: Computed based on the last SE event encountered that did not get a matching EE event


Input: [EXI Option] alignment [Description] Alignment of event codes and content items [Default Value]

Output: bit-packed

EXI Options in Options Document


Input: [EXI Option] compression [Description] EXI compression is used to achieve better compactness [Default Value]

Output: false

EXI Options in Options Document


Input: [EXI Option] strict [Description] Strict interpretation of schemas is used to achieve better compactness [Default Value]

Output: false

EXI Options in Options Document


Input: [EXI Option] fragment [Description] Body is encoded as an EXI fragment instead of an EXI document [Default Value]

Output: false

EXI Options in Options Document


Input: [EXI Option] preserve [Description] Specifies whether the support for the preservation of comments, pis, etc. is each enabled [Default Value]

Output: all false

EXI Options in Options Document


Input: [EXI Option] selfContained [Description] Enables self-contained elements [Default Value]

Output: false

EXI Options in Options Document


Input: [EXI Option] schemaId [Description] Identify the schema information, if any, used to encode the body [Default Value]

Output: no default value

EXI Options in Options Document


Input: [EXI Option] datatypeRepresentationMap [Description] Specify alternate datatype representations for typed values in the EXI body [Default Value]

Output: no default value

EXI Options in Options Document


Input: [EXI Option] blockSize [Description] Specifies the block size used for EXI compression [Default Value]

Output: 1,000,000

EXI Options in Options Document


Input: [EXI Option] valueMaxLength [Description] Specifies the maximum string length of value content items to be considered for addition to the string table. [Default Value]

Output: unbounded

EXI Options in Options Document


Input: [EXI Option] valuePartitionCapacity [Description] Specifies the total capacity of value partitions in a string table [Default Value]

Output: unbounded

EXI Options in Options Document


Input: [EXI Option] [user defined meta-data] [Description] User defined meta-data may be added [Default Value]

Output: no default value

EXI Options in Options Document


Input: [Final] Final [Description] The operation succeeded. [anyURI Name]

Output: Success

XML Key Management Specification (XKMS 2.0)


Input: [Final] Final [Description] The service does not support the protocol version specified in the request. [anyURI Name]

Output: VersionMismatch

XML Key Management Specification (XKMS 2.0)


Input: [Final] Final [Description] An error occurred that was due to the message sent by the sender. [anyURI Name]

Output: Sender

XML Key Management Specification (XKMS 2.0)


Input: [Final] Final [Description] An error occurred at the receiver. [anyURI Name]

Output: Receiver

XML Key Management Specification (XKMS 2.0)


Input: [Final] Not Final [Description] The service has not acted on the request. In order for the request to be acted upon the request MUST be represented with the specified nonce in accordance with the two-phase protocol. [anyURI Name]

Output: Represent

XML Key Management Specification (XKMS 2.0)


Input: [Final] Not Final [Description] The request has been accepted for processing and the service will return the result asynchronously. [anyURI Name]

Output: Pending

XML Key Management Specification (XKMS 2.0)


Input: [Term] issuedby [Type] OWL Annotation Property [Introduced] Section 2.2 [Notes]

Output: Range is undefined but it is RECOMMENDED that the filler be either a dcterms:Agent or a foaf:Agent

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] issued [Type] OWL Annotation Property [Introduced] Section 2.2 [Notes]

Output: It takes as value a literal of type xsd:dateTime.

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] text [Type] OWL Annotation Property [Introduced] Section 2.2 [Notes]

Output: As displaytext in previous table

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] logo [Type] OWL Annotation Property [Introduced] Section 2.2 [Notes]

Output: As displayicon in previous table

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] matchesregex [Type] OWL Datatype Property [Introduced] Section 2.2 [Notes]

Output: RDF/OWL tools must understand the POWDER Semantic Extension to process the semantics of this property.

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] notmatchesregex [Type] OWL Datatype Property [Introduced] Section 2.2 [Notes]

Output: RDF/OWL tools must understand the POWDER Semantic Extension to process the semantics of this property.

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] Processor [Type] Sub class of dcterms:Agent [Introduced] Section 3 [Notes]

Output: The class of POWDER Processors

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] Document [Type] Sub class of owl:Ontology [Introduced] Section 3 [Notes]

Output: The class of POWDER documents

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] data_error [Type] OWL Datatype Property [Introduced] Section 3 [Notes]

Output: A property denoting a description of the specific processing error occurred when processing a given POWDER document. Domain is #Document

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] proc_error [Type] OWL Datatype Property [Introduced] Section 3 [Notes]

Output: A property denoting a description of the specific processing error occurred when processing a given POWDER document. Domain is #Processor

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] err_code [Type] OWL Datatype Property [Introduced] Section 3 [Notes]

Output: A property denoting a description of the specific processing error occurred when processing a given POWDER document. Range is xsd:nonNegativeInterger

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] describedby [Type] OWL Object Property [Introduced] Section 4.1.3 [Notes]

Output: A property that links a described resource to a POWDER document. For use with RDFa and other rich formats.

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] tag [Type] OWL Datatype Property [Introduced] Section 2.7 [Notes]

Output: Filler is a string literal that may include spaces

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] notknownto [Type] OWL Object Property [Introduced] Section 3 [Notes]

Output: Property used by a POWDER Processor that it does not have any information about a particular IRI. Range is #Processor.

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] authenticate [Type] OWL Object Property [Introduced] Section 5.1 [Notes]

Output: An RDF property that links a dcterms:Agent or foaf:Agent class to a resource describing how to authenticate its DRs.

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] validfrom [Type] OWL Annotation Property [Introduced] Section 5.2 [Notes]

Output: It takes as value a literal of type xsd:dateTime.

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] validuntil [Type] OWL Annotation Property [Introduced] Section 5.2 [Notes]

Output: It takes as value a literal of type xsd:dateTime.

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] sha1sum [Type] OWL Datatype Property [Introduced] Section 5.2 [Notes]

Output: Range is datatype xsd:base64Binary.

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] certified [Type] OWL Datatype Property [Introduced] Section 5.2 [Notes]

Output: It takes as value a literal of type xsd:boolean.

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] certifiedby [Type] OWL Object Property [Introduced] Section 5.2 [Notes]

Output: owl:Thing.

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] supportedby [Type] OWL Object Property [Introduced] Section 5.3 [Notes]

Output: owl:Thing

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Final] Final [Description] The operation succeeded. [anyURI Name]

Output: Success

XML Key Management Specification (XKMS 2.0)


Input: [Final] Final [Description] The service does not support the protocol version specified in the request. [anyURI Name]

Output: VersionMismatch

XML Key Management Specification (XKMS 2.0)


Input: [Final] Final [Description] An error occurred that was due to the message sent by the sender. [anyURI Name]

Output: Sender

XML Key Management Specification (XKMS 2.0)


Input: [Final] Final [Description] An error occurred at the receiver. [anyURI Name]

Output: Receiver

XML Key Management Specification (XKMS 2.0)


Input: [Final] Not Final [Description] The service has not acted on the request. In order for the request to be acted upon the request MUST be represented with the specified nonce in accordance with the two-phase protocol. [anyURI Name]

Output: Represent

XML Key Management Specification (XKMS 2.0)


Input: [Final] Not Final [Description] The request has been accepted for processing and the service will return the result asynchronously. [anyURI Name]

Output: Pending

XML Key Management Specification (XKMS 2.0)


Input: [0] Parameter [1] Type [2]

Output: Description


Input: [0] Filter [1] ResultFilter [2]

Output: Used to examine n-best SpeechObject.Results and filter out invalid results


Input: [0] Grammar [1] Grammar [2]

Output: The grammar used for recognition


Input: [0] HelpPrompt [1] Playable [2]

Output: This prompt is played if the user requests help


Input: [0] InitialPrompt [1] Playable [2]

Output: Unless an error occurs or the user requests help, this is the prompt that is played before recognition


Input: [0] MaxErrorCount [1] int [2]

Output: The maximum number of errors (rejections, timeouts, or unexpected dtmf keypresses) permitted before the SpeechObject gives up


Input: [0] MaxHelpCount [1] int [2]

Output: The maximum number of help requests permitted before the SpeechObject gives up


Input: [0] NoResultFoundPrompt [1] Playable [2]

Output: This prompt is played after a valid recognition but when none of the candidates in the n-best list are successfully processed into a SpeechObject.Result (e.g. if the entries fail to pass this Object's Filter)


Input: [0] NoSpeechTimeoutPrompt [1] Playable [2]

Output: This prompt is played when a recognition error code of "no speech timeout" is returned by the recognizer


Input: [0] RecognitionErrorPrompt [1] Playable [2]

Output: This prompt is played by default when a recognition error occurs unless a more specific error prompt is defined


Input: [0] RecognizerTooSlowTimeoutPrompt [1] Playable [2]

Output: This prompt is played when a recognition error code of "recognizer too slow timeout" is returned by the recognizer


Input: [0] RejectedPrompt [1] Playable [2]

Output: This prompt is played when a recognition error code of "rejected" is returned by the recognizer


Input: [0] ReturnAllPossibleResults [1] boolean [2]

Output: If true, this Object returns an entire n-best list of SpeechObject.Results. Otherwise, it will return only the first valid result it interprets and processes


Input: [0] SpeechTooEarlyPrompt [1] Playable [2]

Output: This prompt is played when a recognition error code of "speech too early" is returned by the recognizer


Input: [0] TooMuchSpeechTimeoutPrompt [1] Playable [2]

Output: This prompt is played when a recognition error code of "too much speech timeout" is returned by the recognizer


Input: [0] UnexpectedKeyPrompt [1] Playable [2]

Output: This prompt is played when a recognition error code of "unexpected_key" is returned by the recognizer


Input: [anyURI Name] Success [Description] The operation succeeded. [Final]

Output: Final

XML Key Management Specification (XKMS 2.0)


Input: [anyURI Name] VersionMismatch [Description] The service does not support the protocol version specified in the request. [Final]

Output: Final

XML Key Management Specification (XKMS 2.0)


Input: [anyURI Name] Sender [Description] An error occurred that was due to the message sent by the sender. [Final]

Output: Final

XML Key Management Specification (XKMS 2.0)


Input: [anyURI Name] Receiver [Description] An error occurred at the receiver. [Final]

Output: Final

XML Key Management Specification (XKMS 2.0)


Input: [anyURI Name] Represent [Description] The service has not acted on the request. In order for the request to be acted upon the request MUST be represented with the specified nonce in accordance with the two-phase protocol. [Final]

Output: Not Final

XML Key Management Specification (XKMS 2.0)


Input: [anyURI Name] Pending [Description] The request has been accepted for processing and the service will return the result asynchronously. [Final]

Output: Not Final

XML Key Management Specification (XKMS 2.0)


Input: [0] Parameter [1] Type [2]

Output: Description


Input: [0] Confirmation [1] Confirmation [2]

Output: The object that performs confirmation


Input: [0] GetInitialResultsIfNeeded [1] boolean [2]

Output: If true, will initially invoke all contained SpeechObjects that have not yet obtained results


Input: [0] Identify [1] Identify [2]

Output: The object that identifies which information needs to be corrected


Input: [0] MaxRetryCount [1] int [2]

Output: Maximum number of retries attempted by Confirm and Correct


Input: [0] SpeechObject [1] SpeechObject[] [2]

Output: SpeechObjects to be contained (confirmed/corrected)


Input: [0] SpeechObject [1] (int, SpeechObject) [2]

Output: Adds/sets a SpeechObject for confirmation/correction


Input: [Language feature] address element [Restrictions] If specified, role must be contentinfo [Default implied ARIA semantic]

Output: No role


Input: [Language feature] article element [Restrictions] Role must be either article, document, application, or main [Default implied ARIA semantic]

Output: article role


Input: [Language feature] aside element [Restrictions] Role must be either note, complementary, or search [Default implied ARIA semantic]

Output: note role


Input: [Language feature] audio element [Restrictions] If specified, role must be application [Default implied ARIA semantic]

Output: No role


Input: [Language feature] details element [Restrictions] Role must be a role that supports aria-expanded [Default implied ARIA semantic]

Output: group role


Input: [Language feature] embed element [Restrictions] If specified, role must be either application, document, or img [Default implied ARIA semantic]

Output: No role


Input: [Language feature] footer element [Restrictions] If specified, role must be contentinfo [Default implied ARIA semantic]

Output: No role


Input: [Language feature] header element [Restrictions] If specified, role must be banner [Default implied ARIA semantic]

Output: No role


Input: [Language feature] iframe element [Restrictions] If specified, role must be either application, document, or img [Default implied ARIA semantic]

Output: No role


Input: [Language feature] img element whose alt attribute's value is absent [Restrictions] No restrictions [Default implied ARIA semantic]

Output: img role


Input: [Language feature] input element with a type attribute in the Checkbox state [Restrictions] Role must be either checkbox or menuitemcheckbox [Default implied ARIA semantic]

Output: checkbox role


Input: [Language feature] input element with a type attribute in the Radio Button state [Restrictions] Role must be either radio or menuitemradio [Default implied ARIA semantic]

Output: radio role


Input: [Language feature] li element whose parent is an ol or ul element [Restrictions] Role must be either listitem, menuitemcheckbox, menuitemradio, option, tab, or treeitem [Default implied ARIA semantic]

Output: listitem role


Input: [Language feature] object element [Restrictions] If specified, role must be either application, document, or img [Default implied ARIA semantic]

Output: No role


Input: [Language feature] ol element [Restrictions] Role must be either directory, list, listbox, menu, menubar, tablist, toolbar, tree [Default implied ARIA semantic]

Output: list role


Input: [Language feature] output element [Restrictions] No restrictions [Default implied ARIA semantic]

Output: status role


Input: [Language feature] section element [Restrictions] Role must be either alert, alertdialog, application, contentinfo, dialog, document, log, main, marquee, region, search, or status [Default implied ARIA semantic]

Output: region role


Input: [Language feature] ul element [Restrictions] Role must be either directory, list, listbox, menu, menubar, tablist, toolbar, tree [Default implied ARIA semantic]

Output: list role


Input: [Language feature] video element [Restrictions] If specified, role must be application [Default implied ARIA semantic]

Output: No role


Input: [Language feature] The body element [Restrictions] Role must be either document or application [Default implied ARIA semantic]

Output: document role


Input: [Widget Role] Input [Description] Generic type for widgets that can have a value [Inherited Concepts] Widget [nameRef] Title [Inherited states]

Output: Disable zoom

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


Input: [Widget Role] Textbox [Description] Generic type for the inputs that allow free-form text, as their value [Inherited Concepts] Input [Base and Related Concepts] XFORMS input [nameRef] Title [Inherited states]

Output: Disable zoom

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


Input: [Widget Role] Link [Description] Interactive reference to a resource (note, that in [HTML] 2 any element can have an href attribute and thus be a link) [Inherited Concepts] Widget [Base and Related Concepts] HTML Link [nameRef] Child content title [Inherited states]

Output: Disable zoom

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


Input: [Widget Role] Select [Description] A form control that allows the user to make selections from a set of choices [Inherited Concepts] Input List (see structure) Multiselectable [nameRef] Title [Inherited states]

Output: Disable zoom

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


Input: [Widget Role] Combobox [Description] 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. [Inherited Concepts] Select [Base and Related Concepts] HTML select (multiple) [nameRef] Title [Inherited states]

Output: Disable zoom multiselectable

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


Input: [Widget Role] Option [Description] A selectable item in a list represented by a Select. [Inherited Concepts] Input ListItem (see structure) [Base and Related Concepts] ListItem(see structure), HTML option, XForms item Selected [nameRef] Child content title [Inherited states]

Output: Disable zoom

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


Input: [Widget Role] Checkbox [Description] A control that has two possible states, an equivalent to a boolean [Inherited Concepts] Option [Base and Related Concepts] HTML input (type : checkbox) Checked="true"|"false" [nameRef] Child content title [Inherited states]

Output: Disable zoom selected

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


Input: [Widget Role] Checkboxtristate [Description] A control that has three possible states, (1 0 -1) Often found in installer where an option has been partially installed [Inherited Concepts] Checkbox Checked="true"|"false"|"mixed" [nameRef] Child content title [Inherited states]

Output: Disable zoom selected

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


Input: [Widget Role] Radio [Description] A radio is an option in single-select list. [Inherited Concepts] Checkbox [Base and Related Concepts] HTML input (type : radio) [nameRef] Child content title [Inherited states]

Output: Disable zoom selected checked="true"|"false"

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


Input: [Widget Role] Radiogroup [Description] Maybe, we would rather have a generic "group of choices" type. [Inherited Concepts] Select [nameRef] Title [Inherited states]

Output: Disable zoom selected multiselectable

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


Input: [Widget Role] Button [Description] Allows for user-triggered actions. [Inherited Concepts] Widget Link [Base and Related Concepts] XFORMS trigger Pressed [nameRef] Child conteny title [Inherited states]

Output: Disable zoom

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


Input: [Widget Role] Buttonsubmit [Description] This form control initiates submission of all or part of the instance data to which it is bound [Inherited Concepts] Button [Base and Related Concepts] HTML input (type :submit) [nameRef] Child conteny title [Inherited states]

Output: Disable zoom pressed

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


Input: [Widget Role] Buttoncancel [Description] This button initiates closing a window or leaving a form (e.g. To another page) without submission [Inherited Concepts] Button [nameRef] Child content title [Inherited states]

Output: Disable zoom pressed

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


Input: [Widget Role] Buttonundo [Description] This control brings a form to the initial state (e.g. returns all default values to all inputs) [Inherited Concepts] Button [Base and Related Concepts] HTML input (type : reset) [nameRef] Child content title [Inherited states]

Output: Disable zoom pressed

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


Input: [Widget Role] Buttonback [Description] Brings user-agent to the previous page or state [Inherited Concepts] Button [Base and Related Concepts] HTML Link [nameRef] Child content title [Inherited states]

Output: Disable zoom pressed

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


Input: [Widget Role] MenuItemradio [Description] How it differs from radio? [Inherited Concepts] Menuitem (see structure) Radio [nameRef] Child content title [Inherited states]

Output: Disable zoom selected checked="true"|"false"

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


Input: [Widget Role] MenuItemcheckbox [Description] How it differs from Checkbox? Isn't it defined by its parent's role? [Inherited Concepts] Menuitem Checkbox [nameRef] Title [Inherited states]

Output: Disable zoom selected checked="true"|"false"

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


Input: [Widget Role] Progressbar [Description] Used by applications for tasks that take a long time to execute, to show the execution progress. [Inherited Concepts] Widget [nameRef] Title [Inherited states]

Output: Disable zoom

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


Input: [Widget Role] Hidden [Description] 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". [Inherited Concepts] Input [Base and Related Concepts] [HTML] input (type : hidden) [nameRef] Title [Inherited states]

Output: Disable zoom

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


Input: [Widget Role] Secret [Description] 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. [Inherited Concepts] Input [Base and Related Concepts] [HTML] input (type : password) [nameRef] Title [Inherited states]

Output: Disable zoom

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


Input: [Widget Role] Separator [Description] A line or bar that separates and distinguishes sections of content [Inherited Concepts] Widget [Base and Related Concepts] [HTML] hr [nameRef] Title [Inherited states]

Output: Disable zoom

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


Input: [Widget Role] Range [Description] Represents a range of values that can be set by the user. [Inherited Concepts] Input [nameRef] Title [Inherited states]

Output: Disable zoom

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


Input: [Widget Role] Slider [Description] 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 [Inherited Concepts] Range [nameRef] Title [Inherited states]

Output: Disable zoom

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


Input: [Widget Role] SpinButton [Description] A form of Range that expects a user selecting from discreet choices. [Inherited Concepts] Range [nameRef] Title [Inherited states]

Output: Disable zoom

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


Input: [Widget Role] Spreadsheet [Description] Interactive table where the user can enter the values [Inherited Concepts] Widget Table Multiselectable [nameRef] Title [Inherited states]

Output: Disable zoom

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


Input: [Widget Role] Textarea [Description] Intended for use in entering multi-line content [Inherited Concepts] TextBox [Base and Related Concepts] [HTML] textarea [nameRef] Title [Inherited states]

Output: Disable zoom

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


Input: [Widget Role] Textfield [Description] Free-form data entry for short on-line content. [Inherited Concepts] TextBox [Base and Related Concepts] [HTML] input (type : text) [nameRef] Child content title [Inherited states]

Output: Disable zoom

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


Input: [Widget Role] Tree [Description] A form of a Select (or, generally, of a list having groups inside groups) - where sub trees can be collapsed and expanded [Inherited Concepts] Select Chart Expanded [nameRef] Child content title [Inherited states]

Output: Disable zoom multiselectable

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


Input: [Widget Role] Treeitem [Description] An option item of a tree. [Inherited Concepts] Option [nameRef] Content child title [Inherited states]

Output: Disable zoom selected

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


Input: [Widget Role] Alert [Description] A message with an alert or error information [Inherited Concepts] Window (see structure) Dialog [Base and Related Concepts] XFORMS alert [nameRef] Title [Inherited states]

Output: Disable zoom

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


Input: [Widget Role] Dialog [Description] A small application window [Inherited Concepts] Window [nameRef] Title [Inherited states]

Output: Disable zoom

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


Input: [0] Parameter [1] Type [2]

Output: Description


Input: [0] AutoAdvance [1] boolean [2]

Output: If set to true, forces the list to advance automatically to the next item if there is no response from the user


Input: [0] Browsable [1] Browsable [2]

Output: Object providing access to items to be browsed


Input: [0] ExitPrompt [1] Playable [2]

Output: Prompt played when the list exits


Input: [0] FirstPrePrompt [1] Playable [2]

Output: The pre-prompt played before the first item


Input: [0] Grammar [1] Grammar [2]

Output: The grammar used for both preamble and list item recognitions


Input: [0] LastPrePrompt [1] Playable [2]

Output: The pre-prompt played before the last item


Input: [0] ListNoSpeechTimeoutPrompt [1] Playable [2]

Output: The prompt played if there is a "no-speech" timeout when the user says a command after the list item


Input: [0] ListRecognizerTooSlowTimeoutPrompt [1] Playable [2]

Output: The prompt played if there is a "recognizer-too-slow" timeout when the user says a command after the list item


Input: [0] ListRejectedPrompt [1] Playable [2]

Output: The prompt played if there is a rejection when the user says a command after the list item


Input: [0] ListSpeechTooEarlyPrompt [1] Playable [2]

Output: The prompt played if there is a "speech-too-early" condition when the user says a command after the list item


Input: [0] ListTooMuchSpeechTimeoutPrompt [1] Playable [2]

Output: The prompt played if there is a "too-much-speech" timeout when the user says a command after the list item


Input: [0] ListUnexpectedKeyPrompt [1] Playable [2]

Output: The prompt played if the user presses a dtmf key instead of speaking a command after the list item


Input: [0] MultiItemListErrorPrompt [1] Playable [2]

Output: The recognition error prompt when the list has more than one item


Input: [0] MultiItemListHelpPrompt [1] Playable [2]

Output: The help prompt when the list has more than one item


Input: [0] NextPrePrompt [1] Playable [2]

Output: The pre-prompt played when the user says "next", or when the list auto-advances to the next item


Input: [0] OnlyItemListErrorPrompt [1] Playable [2]

Output: The recognition error prompt when the list has only one item


Input: [0] OnlyItemListHelpPrompt [1] Playable [2]

Output: The help prompt when the list has only one item


Input: [0] OnlyItemPrePrompt [1] Playable [2]

Output: The pre-prompt played when there is only one item


Input: [0] PreambleHelpPrompt [1] Playable [2]

Output: The prompt played if the user asks for help during the preamble


Input: [0] PreamblePrompt [1] Playable [2]

Output: The prompt that is played only once when the user first enters the list


Input: [0] PreambleRecognitionErrorPrompt [1] Playable [2]

Output: The prompt played if there is a recognition error in the preamble


Input: [0] PreviousPrePrompt [1] Playable [2]

Output: The pre-prompt played when the user says "previous"


Input: [0] ReturnAtEnd [1] boolean [2]

Output: If true, list will automatically exit when it reaches the end


Input: [Term] issuedby [Notes] Range is undefined but it is RECOMMENDED that the filler be either a dcterms:Agent or a foaf:Agent [Introduced] Section 2.2 [Type]

Output: OWL Annotation Property

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] issued [Notes] It takes as value a literal of type xsd:dateTime. [Introduced] Section 2.2 [Type]

Output: OWL Annotation Property

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] text [Notes] As displaytext in previous table [Introduced] Section 2.2 [Type]

Output: OWL Annotation Property

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] logo [Notes] As displayicon in previous table [Introduced] Section 2.2 [Type]

Output: OWL Annotation Property

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] matchesregex [Notes] RDF/OWL tools must understand the POWDER Semantic Extension to process the semantics of this property. [Introduced] Section 2.2 [Type]

Output: OWL Datatype Property

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] notmatchesregex [Notes] RDF/OWL tools must understand the POWDER Semantic Extension to process the semantics of this property. [Introduced] Section 2.2 [Type]

Output: OWL Datatype Property

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] Processor [Notes] The class of POWDER Processors [Introduced] Section 3 [Type]

Output: Sub class of dcterms:Agent

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] Document [Notes] The class of POWDER documents [Introduced] Section 3 [Type]

Output: Sub class of owl:Ontology

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] data_error [Notes] A property denoting a description of the specific processing error occurred when processing a given POWDER document. Domain is #Document [Introduced] Section 3 [Type]

Output: OWL Datatype Property

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] proc_error [Notes] A property denoting a description of the specific processing error occurred when processing a given POWDER document. Domain is #Processor [Introduced] Section 3 [Type]

Output: OWL Datatype Property

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] err_code [Notes] A property denoting a description of the specific processing error occurred when processing a given POWDER document. Range is xsd:nonNegativeInterger [Introduced] Section 3 [Type]

Output: OWL Datatype Property

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] describedby [Notes] A property that links a described resource to a POWDER document. For use with RDFa and other rich formats. [Introduced] Section 4.1.3 [Type]

Output: OWL Object Property

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] tag [Notes] Filler is a string literal that may include spaces [Introduced] Section 2.7 [Type]

Output: OWL Datatype Property

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] notknownto [Notes] Property used by a POWDER Processor that it does not have any information about a particular IRI. Range is #Processor. [Introduced] Section 3 [Type]

Output: OWL Object Property

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] authenticate [Notes] An RDF property that links a dcterms:Agent or foaf:Agent class to a resource describing how to authenticate its DRs. [Introduced] Section 5.1 [Type]

Output: OWL Object Property

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] validfrom [Notes] It takes as value a literal of type xsd:dateTime. [Introduced] Section 5.2 [Type]

Output: OWL Annotation Property

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] validuntil [Notes] It takes as value a literal of type xsd:dateTime. [Introduced] Section 5.2 [Type]

Output: OWL Annotation Property

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] sha1sum [Notes] Range is datatype xsd:base64Binary. [Introduced] Section 5.2 [Type]

Output: OWL Datatype Property

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] certified [Notes] It takes as value a literal of type xsd:boolean. [Introduced] Section 5.2 [Type]

Output: OWL Datatype Property

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] certifiedby [Notes] owl:Thing. [Introduced] Section 5.2 [Type]

Output: OWL Object Property

Protocol for Web Description Resources (POWDER): Description Resources


Input: [Term] supportedby [Notes] owl:Thing [Introduced] Section 5.3 [Type]

Output: OWL Object Property

Protocol for Web Description Resources (POWDER): Description Resources


Input: [EXI Option] alignment [Default Value] bit-packed [Description]

Output: Alignment of event codes and content items

EXI Options in Options Document


Input: [EXI Option] compression [Default Value] false [Description]

Output: EXI compression is used to achieve better compactness

EXI Options in Options Document


Input: [EXI Option] strict [Default Value] false [Description]

Output: Strict interpretation of schemas is used to achieve better compactness

EXI Options in Options Document


Input: [EXI Option] fragment [Default Value] false [Description]

Output: Body is encoded as an EXI fragment instead of an EXI document

EXI Options in Options Document


Input: [EXI Option] preserve [Default Value] all false [Description]

Output: Specifies whether the support for the preservation of comments, pis, etc. is each enabled

EXI Options in Options Document


Input: [EXI Option] selfContained [Default Value] false [Description]

Output: Enables self-contained elements

EXI Options in Options Document


Input: [EXI Option] schemaId [Default Value] no default value [Description]

Output: Identify the schema information, if any, used to encode the body

EXI Options in Options Document


Input: [EXI Option] datatypeRepresentationMap [Default Value] no default value [Description]

Output: Specify alternate datatype representations for typed values in the EXI body

EXI Options in Options Document


Input: [EXI Option] blockSize [Default Value] 1,000,000 [Description]

Output: Specifies the block size used for EXI compression

EXI Options in Options Document


Input: [EXI Option] valueMaxLength [Default Value] unbounded [Description]

Output: Specifies the maximum string length of value content items to be considered for addition to the string table.

EXI Options in Options Document


Input: [EXI Option] valuePartitionCapacity [Default Value] unbounded [Description]

Output: Specifies the total capacity of value partitions in a string table

EXI Options in Options Document


Input: [EXI Option] [user defined meta-data] [Default Value] no default value [Description]

Output: User defined meta-data may be added

EXI Options in Options Document


Input: [Specification] CORS [Spec Status] CR (Jan/Feb 2013) [Test Suite] Yes (WebApps WG); Yes (WebAppSec WG) [Remarks] Implementation Report [Test Suite Status]

Output: Complete or very close

Difference between revisions of "Testing/Common" - W3C Wiki


Input: [Specification] DOM 3 Events [Spec Status] LCWD [Test Suite] Yes [Remarks] Approved Tests [Test Suite Status]

Output: Complete or very close

Difference between revisions of "Testing/Common" - W3C Wiki


Input: [Specification] DOM4 [Spec Status] WD [Test Suite] Yes [Remarks] Approved Tests [Test Suite Status]

Output: Not complete

Difference between revisions of "Testing/Common" - W3C Wiki


Input: [Specification] Progress Events [Spec Status] CR [Test Suite] Yes [Test Suite Status]

Output: Complete

Difference between revisions of "Testing/Common" - W3C Wiki


Input: [Specification] Web Storage [Spec Status] CR [Test Suite] Yes [Remarks] Approved Tests [Test Suite Status]

Output: Complete or very close

Difference between revisions of "Testing/Common" - W3C Wiki


Input: [Specification] Web Workers [Spec Status] CR [Test Suite] Yes [Test Suite Status]

Output: Not complete

Difference between revisions of "Testing/Common" - W3C Wiki


Input: [Specification] XMLHttpRequest [Spec Status] WD [Test Suite] Yes [Test Suite Status]

Output: Not complete

Difference between revisions of "Testing/Common" - W3C Wiki


Input: [0] The cells in [1] this table [2]

Output: should go


Input: [0] green when [1] you hover [2]

Output: the pointing


Input: [0] The rows in [1] this table [2]

Output: should go


Input: [0] dark green [1] when the [2]

Output: pointing device


Input: [0] is over the [1] five pixel [2]

Output: border spacing


Input: [0] Including here, [2]

Output: blank cells.


Input: [Description] Alignment of event codes and content items [Default Value] bit-packed [EXI Option]

Output: alignment

EXI Options in Options Document


Input: [Description] EXI compression is used to achieve better compactness [Default Value] false [EXI Option]

Output: compression

EXI Options in Options Document


Input: [Description] Strict interpretation of schemas is used to achieve better compactness [Default Value] false [EXI Option]

Output: strict

EXI Options in Options Document


Input: [Description] Body is encoded as an EXI fragment instead of an EXI document [Default Value] false [EXI Option]

Output: fragment

EXI Options in Options Document


Input: [Description] Specifies whether the support for the preservation of comments, pis, etc. is each enabled [Default Value] all false [EXI Option]

Output: preserve

EXI Options in Options Document


Input: [Description] Enables self-contained elements [Default Value] false [EXI Option]

Output: selfContained

EXI Options in Options Document


Input: [Description] Identify the schema information, if any, used to encode the body [Default Value] no default value [EXI Option]

Output: schemaId

EXI Options in Options Document


Input: [Description] Specify alternate datatype representations for typed values in the EXI body [Default Value] no default value [EXI Option]

Output: datatypeRepresentationMap

EXI Options in Options Document


Input: [Description] Specifies the block size used for EXI compression [Default Value] 1,000,000 [EXI Option]

Output: blockSize

EXI Options in Options Document


Input: [Description] Specifies the maximum string length of value content items to be considered for addition to the string table. [Default Value] unbounded [EXI Option]

Output: valueMaxLength

EXI Options in Options Document


Input: [Description] Specifies the total capacity of value partitions in a string table [Default Value] unbounded [EXI Option]

Output: valuePartitionCapacity

EXI Options in Options Document


Input: [Description] User defined meta-data may be added [Default Value] no default value [EXI Option]

Output: [user defined meta-data]

EXI Options in Options Document


Input: [Status] Proposal [Summary] Proposal to address the basic description of Articles within issues and/or volumes of periodicals of most types. [Vocab] Three new Types: Periodical, PublicationVolume, PublicationIssue, and added properties for two existent Types: Article, CreativeWork [Topic]

Output: Periodicals, Articles and Multi-volume Works

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] Proposal for new Audiobook Type and abridged property for Book. [Vocab] Audiobook subtype of Book and of AudioObject, adds readBy property [Topic]

Output: Audiobook

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] Proposal for new Collection Type and part properties for CreativeWork. [Vocab] Collection subtype of CreativeWork hasPart & isPartOf properties for CreativeWork [Topic]

Output: Collection

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Discussion [Summary] Extension for describing accessibility properties of a CreativeWork. [Vocab] Add accessMode, hasAdapation, isAdaptationof that were not covered in 1.0 [Topic]

Output: Accessibility

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Accepted [Summary] Add one property 'department' to Organization, to allow local businesses to describe their depts (e.g. opening hours) in detail. Final discussion on whether to call it subOrganizationOf instead. [Vocab] department property (range and domain both Organization) [Comments] Proposal very greatly simplified after WebSchemas discussion. [Topic]

Output: Add Organization department property

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] Add one type, 'QuotationSchema', a kind of CreativeWork, alongside some supporting properties. [Vocab] Quotation, spokenByCharacter, incorrectlyAttributedTo, aboutEvent, fromEvent, addressee. [Comments] Several other requirements are addressed by re-use of existing properties. Debate about whether incorrectlyAttributedTo is worthwhile. Some details to finalise. [Topic]

Output: Add Quotation type

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] Add handlers and potential actions to Action type. [Vocab] See full entry and proposal for details. [Comments] The schema.org team solicit comments on this draft via public-vocabs@w3.org. [Topic]

Output: Actions in Schema.org (part 2)

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] "While schema.org already supports marking up offers to sell products (pre-transaction), it does not currently provide schema for the common kinds of confirmations and notifications around orders (post-transaction)". [Vocab] Adds classes OrderStatus, Order, DeliveryMethod plus associated properties. [Comments] Complements Actions proposal, but independent. [Topic]

Output: Orders in Schema.org

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] This proposal includes new types for describing reservations and tickets [Vocab] Adds classes Reservation, ReservationStatus, ProgramMembership, Flight, TrainTrip, TrainReservation, FoodEstablishmentReservation, FlightReservation, EventReservation, ReservationPackage, BusReservation, BusTrip, RentalCarReservation, RentalCar, Car, LodgingReservation plus associated properties. [Comments] Complements Actions proposal, but independent. [Topic]

Output: Reservations in Schema.org

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] This proposal adds a single new type, EmailMessage [Vocab] EmailMessage is a CreativeWork representing email messages, just as WebPage already represents Web pages. [Comments] No properties currently defined; proposals welcomed. [Topic]

Output: EmailMessage type

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] Describing public civic services [Vocab] A proposal extending schema.org to cover various kinds of civic services. [Comments] GovernmentService, several kinds of CivicPermit, CivicAudience, BusinessAudience; various properties [Topic]

Output: Civic Services

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Accepted [Summary] This proposal adds a single new type, WorkersUnion, addressing issue 17 in the WebSchemas tracker. [Vocab] "A Workers Union (...) is an organization that promotes the interests of its worker members by collectively bargaining with management, organizing, and political lobbying."" [Comments] One type, see draft schema. [Topic]

Output: Workers Union type

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Accepted; published in next version [Summary] Proposes modest changes and additions to support TV and radio (from EBU and BBC). [Vocab] Adds Series, Season, Episode under CreativeWork. Existing TVSeries, TVSeason, TVEpisode under Series/Season/Episode. Adds RadioSeries/RadioSeason/RadioEpisode alongside. Adds Programme/Clip for programmes other than episodes. Adds description of a service with Service/PublicationEvent for broadcast, streaming, VoD, etc. [Comments] See also background notes and [[1]]. Draft initially from EBU/BBC/NoTube discussions. Nearby vocab: see VideoObject, AudioObject; Movie. Event re scheduling. See also UserPlays, a kind of UserInteraction. Comics and TV/Radio also share a concern for describing fictional characters and narratives. [Topic]

Output: TV and Radio proposal

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Some initial discussions. [Summary] Several parties are working towards a Sports Vocabulary proposal. See query from Paul Kelly (SportsML), Microdata + Sports Stats post describing earlier ESPN/Google collaboration, and the Sports Ontology used by BBC, Press Association and others. See also sports-schema-collab mailing list. [Vocab] Several sources including a full draft from the ESPN+Google work. Needs summary here. [Comments] March 2nd - posted writeup of the ESPN/Google Microdata vocabulary; next is discussion on finding common basic sports vocab for schema.org. [Topic]

Output: Sports

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Discussing Proposals [Summary] Proposal from Marvel (see examples). [Vocab] Adds PeriodicalSeries (under Intangible(?)), PeriodicalIssue (under CreativeWork), Comic Issue (under PeriodicalIssue), GraphicNovel (under Book). Approx 6-9 properties for each of these classes. [Comments] Generally well received and specified, but some detailed discussion re fine-grain detail of comics (imprint, page count etc.). Can those properties be shared with Book/numberOfPages, or ScholarlyArticle? Should PeriodicalSeries be intangible? [Topic]

Output: Comics and Serials

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Hopefully Final Proposal - please review [Summary] Proposes some modifications to Event based on deployment experience. [Vocab] Adds eventStatus, previousStartDate, previousEndDate; eventCategory; makes startDate/endDate repeatable. Encourages use of 'url' from Thing. [Comments] Fairly modest proposals based on implementor feedback. May2013 update addresses the last open issue on repeating events. [Topic]

Output: Event schema update

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] The historical-data.org site proposes some extensions to schema.org to address historical and genealogical (family history) scenarios. [Vocab] Adds HistoricalRecord, HistoricalEvent (subclass of Event), overrides attendees, subEvents, superEvent to point to HistoricalEvent. [Comments] There is an associated implementation, github repository, and blog. [Topic]

Output: Historical Data proposal

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] A schema extension for describing biological databases, Sagace. [Vocab] Adds a class 'BiologicalDatabaseEntry' as a kind of CreativeWork, introducing 'entryID', 'isEntryOf', 'taxonID'. Adds 'BiologicalDatabase' also subclass of CreativeWork, with no special properties. Both also use 'breadcrumb' from WebPage. [Comments] Others have also mentioned interest in adding some notion of species. [Topic]

Output: Biological Databases

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] A proposal resolving current problems handling breadcrumbs. [Vocab] Adds Breadcrumb type with child property and supposes to use this class on breadcrumb property of a WebPage. An important schema, but needs attention. See discussion on using literal values. [Topic]

Output: Breadcrumbs

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] A proposal extending schema.org for describing online discussion forums and message boards. [Vocab] Adds attachmentURL, contributorType, discussionState, interestedUsers, postCount, postType, votedHelpful. [Comments] Addition candidate [Topic]

Output: Discussion

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] A proposal extending schema.org for describing Innovation and related concepts. Discussion found here: [2] [Vocab] Covers concepts and terms such as Need, Benefit, Usage, Disruption, Innovator, Innovation, Embodiment, to name a few. See [3] for complete list of terms. [Comments] Addition candidate [Topic]

Output: Innovation

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] Add a dissolutionDate property to Organization. [Topic]

Output: dissolutionDate

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] A proposal for extending LodgingBusiness. Specification is here http://thematix.com/ontologies/travel/lodging/ [Vocab] Adds Amenity, BusinessService, Feature, GuestRoomAmenity, LodgingBusinessAmenity, LodgingBusinessService, RentalOffer, RentalRate, Room, RoomType and Service. [Comments] In addition to the examples given in the cited website, examples can be seen at http://www.regencyhotelmiami.com/ and http://hiltonvb.com and at Super8 hotel description pages, e.g., http://www.super8.com/hotels/alberta/fort-mcmurray/super-8-fort-mcmurray/hotel-overview. [Topic]

Output: Lodging Extensions

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Topic]

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] How far along [Summary] Summary of contribution. [Vocab] Overview of new terms [Comments] Comments on status, particularly regarding integration, overlaps and open issues. [Topic]

Output: Proposal name

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Bugzilla bug (if applicable)] Bugzilla bug 16311 [Erratum (if applicable)] None [Category] Substantive [Affected sections] 2 Sequence Normalization 5.1.15 XML Output Method: the item-separator Parameter 6.1.15 XHTML Output Method: the item-separator Parameter 7.4.14 HTML Output Method: the item-separator Parameter 8.1.15 Text Output Method: the item-separator Parameter [Description of change]

Output: Added new serialization parameter for specifying a separator that is inserted between items in the sequence that is to be serialized.


Input: [Bugzilla bug (if applicable)] None [Erratum (if applicable)] None [Category] Editorial [Affected sections] 3.1 Setting Serialization Parameters by Means of a Data Model Instance [Description of change]

Output: Added XSLT instructions equivalent to XQuery expressions for setting serialization parameters by means of a data model instance, and other editorial corrections and improvements.


Input: [Bugzilla bug (if applicable)] None [Erratum (if applicable)] None [Category] Editorial [Affected sections] 11 Conformance [Description of change]

Output: Clarified the definition of host language to make it clear that APIs can be considered to be host languages.


Input: [Bugzilla bug (if applicable)] Bugzilla 6129 [Erratum (if applicable)] None [Category] Substantive [Affected sections] 3 Serialization Parameters 5.1.2 XML Output Method: the html-version Parameter 6 XHTML Output Method 6.1.2 XHTML Output Method: the html-version Parameter 6.1.4 XHTML Output Method: the indent and suppress-indentation Parameters 6.1.7 XHTML Output Method: the doctype-system and doctype-public Parameters 6.1.14 XHTML Output Method: the include-content-type Parameter 7 HTML Output Method 7.1 Markup for Elements 7.2 Writing Attributes 7.3 Writing Character Data 7.4.1 HTML Output Method: the version and html-version Parameters 7.4.3 HTML Output Method: the indent and suppress-indentation Parameters 7.4.6 HTML Output Method: the doctype-system and doctype-public Parameters 7.4.6 HTML Output Method: the doctype-system and doctype-public Parameters D List of URI Attributes [Description of change]

Output: Extended the definitions of the HTML and XHTML output methods to include support for HTML5 serialization.