Input: [Test Name] paths-data-05-t [ASV3] Ok [Amaya 64] Fail [CSIRO SVG Toolkit] Ok [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Ok [Batik] Ok [BitFlash Basic] Ok [eSVG13] Ok [BitFlash Tiny] Ok [CSIRO Tiny] Ok [Nokia] Ok [KDDI] Ok [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] paths-data-06-t [ASV3] Ok [Amaya 64] Fail [CSIRO SVG Toolkit] Ok [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Ok [Batik] Ok [BitFlash Basic] Ok [eSVG13] Ok [BitFlash Tiny] Ok [CSIRO Tiny] Ok [Nokia] Ok [KDDI] Ok [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] paths-data-07-t [ASV3] Ok [Amaya 64] Fail [CSIRO SVG Toolkit] Ok [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Ok [Batik] Ok [BitFlash Basic] Ok [eSVG13] Ok [BitFlash Tiny] Ok [CSIRO Tiny] Ok [Nokia] Ok [KDDI] Ok [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] render-elems-01-t [ASV3] Ok [Amaya 64] Ok [CSIRO SVG Toolkit] Ok [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Ok [Batik] Ok [BitFlash Basic] Ok [eSVG13] Ok [BitFlash Tiny] Ok [CSIRO Tiny] Ok [Nokia] Ok [KDDI] Ok [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] render-elems-02-t [ASV3] Ok [Amaya 64] Ok [CSIRO SVG Toolkit] Ok [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Ok [Batik] Ok [BitFlash Basic] Ok [eSVG13] Ok [BitFlash Tiny] Ok [CSIRO Tiny] Ok [Nokia] Ok [KDDI] Ok [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] render-elems-03-t [ASV3] Ok [Amaya 64] Ok [CSIRO SVG Toolkit] Ok [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Ok [Batik] Ok [BitFlash Basic] Ok [eSVG13] Fail [BitFlash Tiny] Ok [CSIRO Tiny] Ok [Nokia] Partial [KDDI] Fail [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] render-elems-06-t [ASV3] Ok [Amaya 64] Partial [CSIRO SVG Toolkit] Ok [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Ok [Batik] Ok [BitFlash Basic] Ok [eSVG13] Ok [BitFlash Tiny] Ok [CSIRO Tiny] Ok [Nokia] Ok [KDDI] Ok [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] render-elems-07-t [ASV3] Ok [Amaya 64] Fail [CSIRO SVG Toolkit] Ok [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Ok [Batik] Ok [BitFlash Basic] Ok [eSVG13] Ok [BitFlash Tiny] Ok [CSIRO Tiny] Ok [Nokia] Ok [KDDI] Ok [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] render-elems-08-t [ASV3] Ok [Amaya 64] Fail [CSIRO SVG Toolkit] Ok [SVG#] Fail [CSIRO Full] Ok [Mozilla SVG] Ok [Batik] Ok [BitFlash Basic] Ok [eSVG13] Ok [BitFlash Tiny] Ok [CSIRO Tiny] Ok [Nokia] Ok [KDDI] Ok [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] render-groups-03-t [ASV3] Ok [Amaya 64] Partial [CSIRO SVG Toolkit] Ok [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Fail [Batik] Ok [BitFlash Basic] Ok [eSVG13] Partial [BitFlash Tiny] Ok [CSIRO Tiny] Ok [Nokia] Ok [KDDI] Ok [ZOOMON] Ok [CSV]

Output: Partial

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] shapes-circle-01-t [ASV3] Ok [Amaya 64] Ok [CSIRO SVG Toolkit] Ok [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Ok [Batik] Ok [BitFlash Basic] Ok [eSVG13] Ok [BitFlash Tiny] Ok [CSIRO Tiny] Ok [Nokia] Ok [KDDI] Ok [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] shapes-ellipse-01-t [ASV3] Ok [Amaya 64] Ok [CSIRO SVG Toolkit] Ok [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Ok [Batik] Ok [BitFlash Basic] Ok [eSVG13] Ok [BitFlash Tiny] Ok [CSIRO Tiny] Ok [Nokia] Ok [KDDI] Ok [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] shapes-line-01-t [ASV3] Ok [Amaya 64] Ok [CSIRO SVG Toolkit] Ok [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Ok [Batik] Ok [BitFlash Basic] Ok [eSVG13] Ok [BitFlash Tiny] Ok [CSIRO Tiny] Ok [Nokia] Ok [KDDI] Ok [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] shapes-polygon-01-t [ASV3] Ok [Amaya 64] Ok [CSIRO SVG Toolkit] Ok [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Ok [Batik] Ok [BitFlash Basic] Ok [eSVG13] Ok [BitFlash Tiny] Ok [CSIRO Tiny] Ok [Nokia] Ok [KDDI] Ok [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] shapes-polyline-01-t [ASV3] Ok [Amaya 64] Ok [CSIRO SVG Toolkit] Ok [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Ok [Batik] Ok [BitFlash Basic] Ok [eSVG13] Ok [BitFlash Tiny] Ok [CSIRO Tiny] Ok [Nokia] Ok [KDDI] Ok [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] shapes-rect-01-t [ASV3] Ok [Amaya 64] Ok [CSIRO SVG Toolkit] Ok [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Ok [Batik] Ok [BitFlash Basic] Ok [eSVG13] Ok [BitFlash Tiny] Ok [CSIRO Tiny] Ok [Nokia] Ok [KDDI] Ok [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] struct-cond-01-t [ASV3] Ok [Amaya 64] Ok [CSIRO SVG Toolkit] Fail [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Fail [Batik] Ok [BitFlash Basic] Ok [eSVG13] Ok [BitFlash Tiny] Ok [CSIRO Tiny] Ok [Nokia] Ok [KDDI] Ok [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] struct-cond-02-t [ASV3] Ok [Amaya 64] Partial [CSIRO SVG Toolkit] Fail [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Fail [Batik] Ok [BitFlash Basic] Ok [eSVG13] Ok [BitFlash Tiny] Ok [CSIRO Tiny] Ok [Nokia] Ok [KDDI] Ok [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] struct-defs-01-t [ASV3] Ok [Amaya 64] Ok [CSIRO SVG Toolkit] Ok [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Fail [Batik] Ok [BitFlash Basic] Ok [eSVG13] Ok [BitFlash Tiny] Ok [CSIRO Tiny] Ok [Nokia] Ok [KDDI] Ok [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] struct-frag-01-t [ASV3] Ok [Amaya 64] Ok [CSIRO SVG Toolkit] Ok [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Fail [Batik] Ok [BitFlash Basic] Ok [eSVG13] Ok [BitFlash Tiny] Ok [CSIRO Tiny] Ok [Nokia] Ok [KDDI] Ok [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] struct-group-01-t [ASV3] Ok [Amaya 64] Ok [CSIRO SVG Toolkit] Ok [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Ok [Batik] Ok [BitFlash Basic] Ok [eSVG13] Ok [BitFlash Tiny] Ok [CSIRO Tiny] Ok [Nokia] Ok [KDDI] Ok [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] struct-group-02-t [ASV3] Ok [Amaya 64] Ok [CSIRO SVG Toolkit] Ok [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Fail [Batik] Ok [BitFlash Basic] Ok [eSVG13] Ok [BitFlash Tiny] Ok [CSIRO Tiny] Ok [Nokia] Ok [KDDI] Ok [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] struct-image-01-t [ASV3] Ok [Amaya 64] Partial [CSIRO SVG Toolkit] Ok [SVG#] Partial [CSIRO Full] Ok [Mozilla SVG] Fail [Batik] Ok [BitFlash Basic] Ok [eSVG13] Fail [BitFlash Tiny] Ok [CSIRO Tiny] Ok [Nokia] Ok [KDDI] Ok [ZOOMON] Ok [CSV]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] struct-image-02-t [ASV3] Ok [Amaya 64] Ok [CSIRO SVG Toolkit] Partial [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Fail [Batik] Ok [BitFlash Basic] Ok [eSVG13] Fail [BitFlash Tiny] Ok [CSIRO Tiny] Ok [Nokia] Ok [KDDI] Ok [ZOOMON] Ok [CSV]

Output: Partial

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] struct-image-03-t [ASV3] Ok [Amaya 64] Ok [CSIRO SVG Toolkit] Fail [SVG#] Fail [CSIRO Full] Ok [Mozilla SVG] Fail [Batik] Ok [BitFlash Basic] Ok [eSVG13] Fail [BitFlash Tiny] Ok [CSIRO Tiny] Ok [Nokia] Partial [KDDI] Fail [ZOOMON] Partial [CSV]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] struct-image-04-t [ASV3] Ok [Amaya 64] Fail [CSIRO SVG Toolkit] Partial [SVG#] Unknown [CSIRO Full] Unknown [Mozilla SVG] Fail [Batik] Ok [BitFlash Basic] Ok [eSVG13] Ok [BitFlash Tiny] Ok [CSIRO Tiny] Unknown [Nokia] Unknown [KDDI] Unknown [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] styling-pres-01-t [ASV3] Fail [Amaya 64] Fail [CSIRO SVG Toolkit] Fail [SVG#] Fail [CSIRO Full] Ok [Mozilla SVG] Fail [Batik] Fail [BitFlash Basic] Ok [eSVG13] Fail [BitFlash Tiny] Ok [CSIRO Tiny] Unknown [Nokia] Ok [KDDI] Fail [ZOOMON] Ok [CSV]

Output: Fail

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] text-fonts-01-t [ASV3] Partial [Amaya 64] Ok [CSIRO SVG Toolkit] Ok [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Fail [Batik] Ok [BitFlash Basic] Ok [eSVG13] Ok [BitFlash Tiny] Ok [CSIRO Tiny] Unknown [Nokia] Ok [KDDI] Ok [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] text-fonts-02-t [ASV3] Ok [Amaya 64] Partial [CSIRO SVG Toolkit] Fail [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Fail [Batik] Ok [BitFlash Basic] Ok [eSVG13] Ok [BitFlash Tiny] Ok [CSIRO Tiny] Unknown [Nokia] Ok [KDDI] Ok [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] text-intro-01-t [ASV3] Partial [Amaya 64] Ok [CSIRO SVG Toolkit] Fail [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Ok [Batik] Ok [BitFlash Basic] Partial [eSVG13] Partial [BitFlash Tiny] Fail [CSIRO Tiny] Unknown [Nokia] Ok [KDDI] Fail [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] text-intro-04-t [ASV3] Ok [Amaya 64] Ok [CSIRO SVG Toolkit] Partial [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Fail [Batik] Ok [BitFlash Basic] Ok [eSVG13] Partial [BitFlash Tiny] Ok [CSIRO Tiny] Partial [Nokia] Ok [KDDI] Fail [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] text-ws-01-t [ASV3] Ok [Amaya 64] Ok [CSIRO SVG Toolkit] Ok [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Fail [Batik] Ok [BitFlash Basic] Ok [eSVG13] Ok [BitFlash Tiny] Ok [CSIRO Tiny] Ok [Nokia] Ok [KDDI] Ok [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [Test Name] text-ws-02-t [ASV3] Ok [Amaya 64] Ok [CSIRO SVG Toolkit] Ok [SVG#] Ok [CSIRO Full] Ok [Mozilla SVG] Fail [Batik] Ok [BitFlash Basic] Ok [eSVG13] Fail [BitFlash Tiny] Ok [CSIRO Tiny] Ok [Nokia] Ok [KDDI] Ok [ZOOMON] Ok [CSV]

Output: Ok

SVG 1.1 Conformance Suite Implementation Status


Input: [BASE] SELECT [PREFIX] CONSTRUCT [3] ASK [2]

Output: DESCRIBE


Input: [BASE] ORDER BY [PREFIX] LIMIT [3] DISTINCT [4] REDUCED [2]

Output: OFFSET


Input: [BASE] FROM [PREFIX] FROM NAMED [2]

Output: WHERE


Input: [BASE] GRAPH [PREFIX] OPTIONAL [3] FILTER [4] a [2]

Output: UNION


Input: [BASE] STR [PREFIX] LANG [3] DATATYPE [4] BOUND [5] sameTERM [2]

Output: LANGMATCHES


Input: [BASE] isURI [PREFIX] isIRI [3] REGEX [4] true [5] false [6] isBLANK [2]

Output: isLITERAL


Input: [Language feature] a element that creates a hyperlink [Restrictions] Role must be either link, button, checkbox, menuitem, menuitemcheckbox, menuitemradio, tab, or treeitem

Output: link role


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

Output: No role


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

Output: article role


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

Output: complementary role


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

Output: No role


Input: [Language feature] button element [Restrictions] Role must be either button, link, menuitem, menuitemcheckbox, menuitemradio, radio

Output: button role


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

Output: group role


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

Output: dialog role


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

Output: No role


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

Output: No role


Input: [Language feature] h1 element that does not have an hgroup ancestor [Restrictions] Role must be either heading or tab

Output: heading role, with the aria-level property set to the element's outline depth


Input: [Language feature] h2 element that does not have an hgroup ancestor [Restrictions] Role must be either heading or tab

Output: heading role, with the aria-level property set to the element's outline depth


Input: [Language feature] h3 element that does not have an hgroup ancestor [Restrictions] Role must be either heading or tab

Output: heading role, with the aria-level property set to the element's outline depth


Input: [Language feature] h4 element that does not have an hgroup ancestor [Restrictions] Role must be either heading or tab

Output: heading role, with the aria-level property set to the element's outline depth


Input: [Language feature] h5 element that does not have an hgroup ancestor [Restrictions] Role must be either heading or tab

Output: heading role, with the aria-level property set to the element's outline depth


Input: [Language feature] h6 element that does not have an hgroup ancestor [Restrictions] Role must be either heading or tab

Output: heading role, with the aria-level property set to the element's outline depth


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

Output: No role


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

Output: No role


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

Output: img role


Input: [Language feature] img element whose alt attribute's value is present and not empty [Restrictions] No restrictions

Output: img role


Input: [Language feature] input element with a type attribute in the Button state [Restrictions] Role must be either button, link, menuitem, menuitemcheckbox, menuitemradio, radio

Output: button role


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

Output: checkbox role


Input: [Language feature] input element with a type attribute in the Image Button state [Restrictions] Role must be either button, link, menuitem, menuitemcheckbox, menuitemradio, radio

Output: button role


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

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

Output: listitem role


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

Output: No role


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

Output: list role


Input: [Language feature] output element [Restrictions] No restrictions

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

Output: region role


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

Output: list role


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

Output: No role


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

Output: document role


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: [Name] src [Required] No [Default Value] None [Description]

Output: The URI specifying the location of the media source.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 34: Attributes


Input: [Name] srcexpr [Required] No [Default Value] undefined [Description]

Output: A data model expression which evaluates to a URI indicating the location of the media resource.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 34: Attributes


Input: [Name] cond [Required] No [Default Value] true [Description]

Output: A data model expression that must evaluate to true after conversion to boolean in order for the media to be played.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 34: Attributes


Input: [Name] type [Required] No [Default Value] undefined [Description]

Output: The preferred media type of the output resource. A resource indicated by the URI reference in the src or expr attributes may be available in one or more media types. The author may specify the preferred media type via the type attribute. When the content represented by a URI is available in many data formats, a VoiceXML platform may use the preferred media-type to influence which of the multiple formats is used. For instance, on a server implementing HTTP content negotiation, the processor may use the preferred media-type to order the preferences in the negotiation. The resource representation delivered by dereferencing the URI reference may be considered in terms of two types. The declared media-type is the asserted value for the resource and the actual media-type is the true format of its content. The actual media-type should be the same as the declared media-type, but this is not always the case (e.g. a misconfigured HTTP server might return 'text/plain' for a 'audio/x-wav' or video/3gpp' resource). A specific URI scheme may require that the resource owner always, sometimes, or never return a media-type. The declared media-type is the value returned by the resource owner or, if none is returned, the preferred media type. There may be no declared media-type if the resource owner does not return a value and no preferred type is specified. Whenever specified, the declared media-type is authoritative. Three special cases may arise. The declared media-type may not be supported by the processor. No error is thrown by the platform and the content of the media element is played instead. The declared media-type may be supported but the actual media-type may not match. No error is thrown by the platform and the content of the media element is played instead. Finally, there may be no declared media-type; the behavior depends on the specific URI scheme and the media capabilities of the VoiceXML processor. For instance, HTTP 1.1 allows document introspection (see [RFC2616] , section 7.2.1), the data scheme falls back to a default media type, and local file access defines no guidelines.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 34: Attributes


Input: [Name] clipBegin [Type] Time Designation [Required] No [Default Value] 0s [Description]

Output: offset from start of media to begin rendering. This offset is measured in normal media playback time from the beginning of the media.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 34: Attributes


Input: [Name] clipEnd [Type] Time Designation [Required] No [Default Value] None [Description]

Output: offset from start of media to end rendering. This offset is measured in normal media playback time from the beginning of the media.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 34: Attributes


Input: [Name] repeatDur [Type] Time Designation [Required] No [Default Value] None [Description]

Output: total duration for repeatedly rendering media. This duration is measured in normal media playback time from the beginning of the media.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 34: Attributes


Input: [Name] repeatCount [Type] positive Real number [Required] No [Default Value] 1 [Description]

Output: number of iterations of media to render. A fractional value describes a portion of the rendered media.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 34: Attributes


Input: [Name] soundLevel [Type] signed ("+" or "-") CSS2 numbers immediately followed by "dB" [Required] No [Default Value] +0.0dB [Description]

Output: Decibel values are interpreted as a ratio of the squares of the new signal amplitude (a1) and the current amplitude (a0) and are defined in terms of dB: soundLevel(dB) = 20 log10 (a1 / a0) A setting of a large negative value effectively plays the media silently. A value of '-6.0dB' will play the media at approximately half the amplitude of its current signal amplitude. Similarly, a value of '+6.0dB' will play the media at approximately twice the amplitude of its current signal amplitude (subject to hardware limitations). The absolute sound level of media perceived is further subject to system volume settings, which cannot be controlled with this attribute.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 34: Attributes


Input: [Name] speed [Type] x% (where x is a positive real value) [Required] No [Default Value] 100% [Description]

Output: the speed at which to play the referenced media, relative to the original speed. The speed is set to the requested percentage of the speed of the original media. For audio, a change in the speed will change the rate at which recorded samples are played back and this will affect the pitch.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 34: Attributes


Input: [Name] outputmodes [Type] space separated list of media types [Required] No [Default Value] outputmodes property [Description]

Output: Determines the modes used for media output. See 8.2.4 Media Properties for further details.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 34: Attributes


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

Output: Multiselectable

Role Taxonomy for Accessible Adaptable Applications Working Draft

Structural Roles that were included in Previous Working Drafts

New supported states(beyond inherited states)


Input: [Widget Role] col [Description] Description of a table column. [Inherited Concepts] Group [nameRef] scope: TD

Output: Name from title attribute

Role Taxonomy for Accessible Adaptable Applications Working Draft

New supported states(beyond inherited states)


Input: [Widget Role] row [Description] Defines a table row. [Inherited Concepts] Group [Base and Related Concepts] [HTML] tr [nameRef] scope: TD

Output: Name from title attribute

Role Taxonomy for Accessible Adaptable Applications Working Draft

New supported states(beyond inherited states)


Input: [Widget Role] menubar [Description] A Visual presentation of a menu [Inherited Concepts] Menu

Output: Name from title attribute

Role Taxonomy for Accessible Adaptable Applications Working Draft

New supported states(beyond inherited states)


Input: [Widget Role] mainmenu [Description] A menu containing the most important links on this page/document [Inherited Concepts] Menu

Output: Name from title attribute

Role Taxonomy for Accessible Adaptable Applications Working Draft

New supported states(beyond inherited states)


Input: [Widget Role] submenu1 [Description] Main submenu [Inherited Concepts] Menu

Output: Name from title attribute

Role Taxonomy for Accessible Adaptable Applications Working Draft

New supported states(beyond inherited states)


Input: [Widget Role] submenu2 [Description] Secondary submenu [Inherited Concepts] Menu

Output: Name from title attribute

Role Taxonomy for Accessible Adaptable Applications Working Draft

New supported states(beyond inherited states)


Input: [Widget Role] submenutrivia [Description] Unimportant submenu [Inherited Concepts] Menu

Output: Name from title attribute

Role Taxonomy for Accessible Adaptable Applications Working Draft

New supported states(beyond inherited states)


Input: [Widget Role] footer [Description] Small text at the end of a page - typically contains copyright and similar information [Base and Related Concepts] [HTML] roles : contentinfo, copyright

Output: Not mapped

Role Taxonomy for Accessible Adaptable Applications Working Draft

New supported states(beyond inherited states)


Input: [Widget Role] footermenusite [Description] A menu found at the bottom of a page containing important site links. Typically includes a link to a "contact us" page and other important site's pages. [Inherited Concepts] Menu Footer

Output: Not mapped

Role Taxonomy for Accessible Adaptable Applications Working Draft

New supported states(beyond inherited states)


Input: [Widget Role] heading1 [Description] Level 1 heading [Inherited Concepts] Sectionhead [Base and Related Concepts] [HTML]/[DTB]/NIMAS h1

Output: Name from child content or title attribute

Role Taxonomy for Accessible Adaptable Applications Working Draft

New supported states(beyond inherited states)


Input: [Widget Role] heading2 [Description] Level 2 heading [Inherited Concepts] Sectionhead [Base and Related Concepts] [HTML]/[DTB]/NIMAS h2 [nameRef] level=2

Output: Name from child content or title attribute

Role Taxonomy for Accessible Adaptable Applications Working Draft

New supported states(beyond inherited states)


Input: [Widget Role] heading3 [Description] Level 3 heading [Inherited Concepts] Sectionhead [Base and Related Concepts] [HTML]/[DTB]/NIMAS h3 [nameRef] level=3

Output: Name from child content or title attribute

Role Taxonomy for Accessible Adaptable Applications Working Draft

New supported states(beyond inherited states)


Input: [Widget Role] heading4 [Description] Level 4 heading [Inherited Concepts] Sectionhead [Base and Related Concepts] [HTML]/[DTB]/NIMAS h4 [nameRef] level=4

Output: Name from child content or title attribute

Role Taxonomy for Accessible Adaptable Applications Working Draft

New supported states(beyond inherited states)


Input: [Widget Role] heading5 [Description] Level 5 heading [Inherited Concepts] Sectionhead [Base and Related Concepts] [HTML]/[DTB]/NIMAS h5 [nameRef] level=5

Output: Name from child content or title attribute

Role Taxonomy for Accessible Adaptable Applications Working Draft

New supported states(beyond inherited states)


Input: [Widget Role] heading6 [Description] Level 6 heading [Inherited Concepts] Sectionhead [Base and Related Concepts] [HTML]/[DTB]/NIMAS h6 [nameRef] level=6

Output: Name from child content or title attribute

Role Taxonomy for Accessible Adaptable Applications Working Draft

New supported states(beyond inherited states)


Input: [General tool] HTML to Text converter [,shortcut] ,text [Access control] Same as the document [For this page]

Output: A plain text version of the page, handy for pasting into email.


Input: [General tool] Link Checker [,shortcut] ,checklink [Access control] Same as the document [For this page]

Output: List of bad links in the page


Input: [General tool] Link Checker [,shortcut] ,rchecklink [Access control] Same as the document [For this page]

Output: Bad links in a page and in pages linked from it


Input: [General tool] HTML Validator [,shortcut] ,validate [Access control] Same as the document [For this page]

Output: List of HTML markup errors.


Input: [General tool] W3C Spellchecker [,shortcut] ,spell [Access control] Same as the document [For this page]

Output: List of spelling errors.


Input: [General tool] CSS Validator [,shortcut] ,cssvalidate [Access control] Works only on public pages. [For this page]

Output: List of style CSS errors.


Input: [General tool] CVS Log [,shortcut] ,cvslog [Access control] Public on dev.w3.org, Team-only on www.w3.org [For this page]

Output: Log of changes to the document


Input: [General tool] Headers [,shortcut] ,headers [Access control] Same as the document [For this page]

Output: HTTP headers sent by the server


Input: [General tool] the pubrules checker [,shortcut] ,pubrules [Access control] Same as the document [For this page]

Output: Check the compliance of this document to the W3C publication rules


Input: [General tool] the pubrules checker [,shortcut] ,pubruleserrors [Access control] Same as the document [For this page]

Output: Check the compliance of this document to the W3C publication rules, only displaying errors


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: [Name] confidencelevel [Default] 0.5 [Description]

Output: The speech recognition confidence level, a float value in the range of 0.0 to 1.0. Results are rejected (a nomatch event is thrown) when application.lastresult$.confidence is below this threshold. A value of 0.0 means minimum confidence is needed for a recognition, and a value of 1.0 requires maximum confidence. The value is a Real Number Designation (see 8.4 Value Designations).

Voice Extensible Markup Language (VoiceXML) 3.0

Table 65: Speech Recognition Properties


Input: [Name] sensitivity [Default] 0.5 [Description]

Output: Set the sensitivity level. A value of 1.0 means that it is highly sensitive to quiet input. A value of 0.0 means it is least sensitive to noise. The value is a Real Number Designation (see 8.4 Value Designations).

Voice Extensible Markup Language (VoiceXML) 3.0

Table 65: Speech Recognition Properties


Input: [Name] speedvsaccuracy [Default] 0.5 [Description]

Output: A hint specifying the desired balance between speed vs. accuracy. A value of 0.0 means fastest recognition. A value of 1.0 means best accuracy. The value is a Real Number Designation (see 8.4 Value Designations).

Voice Extensible Markup Language (VoiceXML) 3.0

Table 65: Speech Recognition Properties


Input: [Name] completetimeout [Default] platform-dependent [Description]

Output: The length of silence required following user speech before the speech recognizer finalizes a result (either accepting it or throwing a nomatch event). The complete timeout is used when the speech is a complete match of an active grammar. By contrast, the incomplete timeout is used when the speech is an incomplete match to an active grammar. A long complete timeout value delays the result completion and therefore makes the computer's response slow. A short complete timeout may lead to an utterance being broken up inappropriately. Reasonable complete timeout values are typically in the range of 0.3 seconds to 1.0 seconds. The value is a Time Designation (see 8.4 Value Designations). See 8.3 Speech and DTMF Input Timing Properties. Although platforms must parse the completetimeout property, platforms are not required to support the behavior of completetimeout. Platforms choosing not to support the behavior of completetimeout must so document and adjust the behavior of the incompletetimeout property as described below.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 65: Speech Recognition Properties


Input: [Name] incompletetimeout [Default] undefined? [Description]

Output: The required length of silence following user speech after which a recognizer finalizes a result. The incomplete timeout applies when the speech prior to the silence is an incomplete match of all active grammars. In this case, once the timeout is triggered, the partial result is rejected (with a nomatch event). The incomplete timeout also applies when the speech prior to the silence is a complete match of an active grammar, but where it is possible to speak further and still match the grammar. By contrast, the complete timeout is used when the speech is a complete match to an active grammar and no further words can be spoken. A long incomplete timeout value delays the result completion and therefore makes the computer's response slow. A short incomplete timeout may lead to an utterance being broken up inappropriately. The incomplete timeout is usually longer than the complete timeout to allow users to pause mid-utterance (for example, to breathe). See 8.3 Speech and DTMF Input Timing Properties Platforms choosing not to support the completetimeout property (described above) must use the maximum of the completetimeout and incompletetimeout values as the value for the incompletetimeout. The value is a Time Designation (see 8.4 Value Designations).

Voice Extensible Markup Language (VoiceXML) 3.0

Table 65: Speech Recognition Properties


Input: [Name] maxspeechtimeout [Default] platform-dependent [Description]

Output: The maximum duration of user speech. If this time elapsed before the user stops speaking, the event "maxspeechtimeout" is thrown. The value is a Time Designation (see 8.4 Value Designations).

Voice Extensible Markup Language (VoiceXML) 3.0

Table 65: Speech Recognition Properties


Input: [media type] xml-stylesheet PI and link [text/html] recognized as HTML [application/xhtml+xml] recognized as XHTML, but the type selector in style sheets matched case-insensitively [application/xml] recognized as XHTML, but the type selector in style sheets matched case-insensitively [text/xml]

Output: recognized as XHTML, but the type selector in style sheets matched case-insensitively

XHTML media type test - results: Opera 7.0b2


Input: [media type] link only [text/html] recognized as HTML [application/xhtml+xml] recognized as XHTML, but the type selector in style sheets matched case-insensitively [application/xml] recognized as XHTML, but the type selector in style sheets matched case-insensitively [text/xml]

Output: recognized as XHTML, but the type selector in style sheets matched case-insensitively

XHTML media type test - results: Opera 7.0b2


Input: [media type] xml-stylesheet PI only [text/html] recognized as HTML, xml-stylesheet PI was not recognized [application/xhtml+xml] recognized as XHTML, but the type selector in style sheets matched case-insensitively [application/xml] recognized as XHTML, but the type selector in style sheets matched case-insensitively [text/xml]

Output: recognized as XHTML, but the type selector in style sheets matched case-insensitively

XHTML media type test - results: Opera 7.0b2


Input: [media type] without xmlns [text/html] recognized as HTML [application/xhtml+xml] recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively [application/xml] recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively [text/xml]

Output: recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively

XHTML media type test - results: Opera 7.0b2


Input: [media type] without DOCTYPE [text/html] recognized as HTML [application/xhtml+xml] recognized as XHTML, but the type selector in style sheets matched case-insensitively [application/xml] recognized as XHTML, but the type selector in style sheets matched case-insensitively [text/xml]

Output: recognized as XHTML, but the type selector in style sheets matched case-insensitively

XHTML media type test - results: Opera 7.0b2


Input: [media type] without DOCTYPE and xmlns [text/html] recognized as HTML [application/xhtml+xml] recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively [application/xml] recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively [text/xml]

Output: recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively

XHTML media type test - results: Opera 7.0b2


Input: [media type] Broken XHTML [text/html] recognized as HTML, well-formedness error was not checked [application/xhtml+xml] well-formedness error was correctly reported [application/xml] well-formedness error was correctly reported [text/xml]

Output: well-formedness error was correctly reported

XHTML media type test - results: Opera 7.0b2


Input: [media type] HTML 4 [text/html] recognized as HTML [application/xhtml+xml] well-formedness error was correctly reported [application/xml] well-formedness error was correctly reported [text/xml]

Output: well-formedness error was correctly reported

XHTML media type test - results: Opera 7.0b2


Input: [Responder] Chris Mejia

Output: I object to Option A: I strongly object to the porting of ANY definition into the TPE. I believe that ALL definitions should be found in the compliance specification of the compliance regime for which a server claims compliance—such compliance regimes may include one created by W3C, or some other qualified organization. This TPE should focus ONLY on the technical protocols, and should not rely on any broad or narrow definition of terms. With respect to the TPE’s context (on it’s own), I counter the argument that the user needs to know what her preference is when she turns on the DNT signal. My opinion is that the user need only know that she has stated a preference to “send” a DNT signal. That’s all the TPE should be about—no further context required. I believe that how the server handles a preference statement from the user should be dependent on the compliance regime honored by the called server, and this should be messaged accordingly to the user. I’m very concerned about the “slippery slope” situation that the porting of ANY definition into the tech spec creates. If these ported definitions were too broad, valuable context could be lost. If these ported definitions were too narrow, technical and policy compliance may be jeopardized (i.e. some organizations may not be able to live with the resultant technical spec and may choose then not to honor DNT at all). Bringing overly broad or unclear definition of Tracking into the TPE does nothing to help the user understand his or her DNT choice. The user’s choice is simple: to send or not send a DNT signal. After all, I cannot conceive of how the TPE would ever, practically speaking, stand alone in the marketplace. Naturally, I think this TPE would be married with SOME compliance policy/spec, and the definition of terms found in the TPE would be made clear in that policy/spec. That policy/spec should be openly reference-able by any user, and that document, with its definitions, should help the user understand their choice to send a DNT signal. So to be clear, I OBJECT STRONGLY (I can’t live with) BOTH Option A and Option B, and am in strong support of Option C in this poll.

Results of Questionnaire [Call for Objections] Tracking definition - Web-Based Straw-poll and Balloting System

Objections to Option A: Tracking across multiple distinct contexts


Input: [Responder] Rob van Eijk

Output: I bbject to this definition. Do Not Track may well be a context negotiation mechanism, but that negotiation is done by the user. Defining the boundaries of context by anyting else but the user would seriously undermine the user centric nature of Do Not Track. Context is highly subjective from a user perspective and should therefore not be pinned down by boundaries like common branding or other assumption.

Results of Questionnaire [Call for Objections] Tracking definition - Web-Based Straw-poll and Balloting System

Objections to Option A: Tracking across multiple distinct contexts


Input: [Responder] Brooks Dobbs

Output: I object to this for two distinct reasons: 1) This definition does not have meaning. It is really just a punt to another misunderstood and not agreed upon term, "context". The non-normative language actually confuses this matter further by saying that a definition is required - just not any particular definition. In reality the term "context" likely has very different meanings to different participants, meaning that the resultant definition of tracking will have an equally un-agreed upon meaning. In my opinion this definition moves us no further towards consensus. 2)Any definition of tracking in a TPE will necessarily be incomplete and therefore incorrect. If "tracking" is the activity that users will be able to effect a choice with respect to, but compliance with that choice is to be determined in another document (documents) there is a logical breakdown. If we define tracking in broad terms in a TPE and allow for a TPE compliant signal to be an expression of a choice for NOT "tracking" then any exceptions to that e.g. permitted uses, would seem to be outside of the choice a user made. While a definition is important, the definition must occur in a location to provide consistency between user expectation and compliance requirements.

Results of Questionnaire [Call for Objections] Tracking definition - Web-Based Straw-poll and Balloting System

Objections to Option A: Tracking across multiple distinct contexts


Input: [Responder] Amy Colando

Output: Microsoft believes that defining Tracking will be helpful for implementers and other readers of the TPE specification. Because the proposals are dependent on other definitions, and are also dependent on other text currently in the Compliance specification, we believe that the editorial notes (in italics) that accompany the selected proposal should accompany the Tracking definition as non-normative text, particularly for option B. We support the inclusion of either option A or B to help define use and retention approaches for DNT, although we note that option A may be slightly easier for nontechnical readers to comprehend.

Results of Questionnaire [Call for Objections] Tracking definition - Web-Based Straw-poll and Balloting System

Objections to Option A: Tracking across multiple distinct contexts


Input: [Responder] Mike O'Neill

Output: I object to Candidate A. This definition restricts the locus of this specification to the collection of data “regarding a particular user’s activity across multiple distinct contexts”, which makes this core definition ambiguous and weakens the meaning conveyed by the Do Not Track signal. A common understanding of tracking involves the collection of a database of any web activity without a user’s knowledge (and therefore without their consent) and to many it is irrelevant what “contexts” apply when this data is collected. This definition would allow the collection, use etc. of data within any single context, not only by “location bar” visited sites but also by third-party content servers. A third-party server receiving a DNT:1 signal could continue to place or retain a unique user identifier and collect other data such as time of visit or geo-location details. Although there may be restrictions on associating this data with details about the explicitly visited first-party this could be by “administrative and operational controls” which would be impossible to verify automatically, leaving the user to simply rely on trust. Restricting the definition of tracking in this way may also reduce the likelihood that this specification could fulfil the requirements for “browser settings” in Recital 66 of the European e-privacy directive or as an automated mechanism to impart a consent or “right to object” signal referred to by the forthcoming general data protection regulation. This could lessen the chance of getting legal backing for the standard in Europe. If a user’s agreement to be tracked, irrespective of their general preference not to be, can be implied by the action of clicking on a link then it would be better to document that as a possible exemption, subject to local law, in the compliance document.

Results of Questionnaire [Call for Objections] Tracking definition - Web-Based Straw-poll and Balloting System

Objections to Option A: Tracking across multiple distinct contexts


Input: [Responder] Alan Chapell

Output: I respectfully object to Option A The inclusion of context into the definition of tracking is certainly interesting and worth discussing in the event that we ultimately work on a compliance specification. However, creating a definition of tracking is unnecessary to complete the technical specification document.

Results of Questionnaire [Call for Objections] Tracking definition - Web-Based Straw-poll and Balloting System

Objections to Option A: Tracking across multiple distinct contexts


Input: [Responder] David Wainberg

Output: I strongly object to the inclusion of any definition of tracking in the TPE. It is unnecessary to defining the technical mechanism for transmitting a user's DNT preference. It's inclusion outside of a broader document that fully defines and describes the meaning of a DNT signal will be highly detrimental to the specification, because it would create considerable ambiguity and therefore risk for potential implementers. However, because it seems likely the chairs will elect to include a definition of tracking in the TPE despite strong objections to doing so, I will also state the following objections to this particular definition: 1. While I support the focus on context, I object to the finalization and inclusion of a definition of tracking that relies on vague, undefined terms, such as context or sharing. 2. Additionally, I specifically object to the portion of this definition that applies to "data derived" from users' activity. This is over-broad in that it could include data and data uses that should not reasonably fall within the definition of tracking, including, for example, aggregate data, or other data that is not tracking data.

Results of Questionnaire [Call for Objections] Tracking definition - Web-Based Straw-poll and Balloting System

Objections to Option A: Tracking across multiple distinct contexts


Input: [Responder] David Singer

Output: This definition has many problems. 1) It needs a definition of 'context', as noted. 2) It's probably not comprehensible to users, whereas the purpose of the definition is to reflect the users' general desires. Users' general objection is to 'keeping records about them' and this is more complex and rather different from that. 3) It talks about the symptom (tying contexts together) rather than the activity or problem (collection and retention of personal data). 4) It would appear to permit a great deal of recording; ad servers could record everything they see about a user 'in their context', for example. Indeed, it appears only to restrict connecting those records 'outside the ad server context', e.g. to the sites on which the ads appeared. That's permitting a lot of tracking and retention. If that is not the intent of the definition, it's misleading. 5) It appears to be a formal definition, but it's at odds with what the current compliance draft actually restricts (there is nothing in there about multiple contexts, for example).

Results of Questionnaire [Call for Objections] Tracking definition - Web-Based Straw-poll and Balloting System

Objections to Option A: Tracking across multiple distinct contexts


Input: [Responder] John Simpson

Output: I object to this definition. First, as presented, it is too contingent on other language that hasn't been clarified. Second, and more to the point, I don't think it is readily understandable by the average user: what exactly is across multiple distinct contexts? It also is too narrow and limiting.

Results of Questionnaire [Call for Objections] Tracking definition - Web-Based Straw-poll and Balloting System

Objections to Option A: Tracking across multiple distinct contexts


Input: [Responder] Roy Fielding

Output: I support this definition. The reason context is not defined as part of this definition is because the scope of what a user considers to be same-context is an orthogonal question. Hence, it can be debated and decided separately, or perhaps not even defined at all (left to the user to define according to what is evident from a site's user experience). The entire point of using context in this definition of tracking is to abstract away from what has clearly been a contentious issue. Objecting to this definition because you don't like the explanatory notes is ludicrous -- they exist for the sole purpose of explaining what I was thinking when writing down the definition, so that the chairs would have a better idea of what might be considered "new information" if we later change those assumptions. They are not part of the definition itself. Objecting to this definition because you don't like relying on undefined terms is nothing more than a delaying tactic to prevent further work on the standard. Every word in the specification is dependent on the specification's scope, and that scope is "Do Not Track". I don't think we need to define the first two words, but we do need to define the third. For two years now, the same people have been complaining about working on a definition of collection because they did not have an agreed upon definition of tracking. We have to start somewhere. If new information is discovered later, the W3C process allows this decision to be reconsidered by the group.

Results of Questionnaire [Call for Objections] Tracking definition - Web-Based Straw-poll and Balloting System

Objections to Option A: Tracking across multiple distinct contexts


Input: [Responder] Brad Kulick

Output: First, I strongly object to moving any definitions into the TPE. I object to this definition. While this is a core term that must be defined, doing so in the TPE, instead of a compliance specification, does not make the TPE a stronger document but rather limits its utility. Furthermore, leaving the term “context” under-defined does not provide enough clarity to avoid confusion of what tracking is. It leaves open for unacceptably different interpretations of what would be within scope of this definition. The nuance involved with getting this definition correct, should not be rushed simply due to pushing the TPE out first. I recommend moving this definition back to the compliance specification and clearly define context in less ambiguous terms.

Results of Questionnaire [Call for Objections] Tracking definition - Web-Based Straw-poll and Balloting System

Objections to Option A: Tracking across multiple distinct contexts


Input: [Responder] Jack Hobaugh

Output: In general, I object to the porting of a TCS compliance definition into the TPE. I feel strongly that the TPE should remain a pure protocol and technical specification document. Some have contended that some TCS definitions are needed in the TPE in order for the user to understand the choice that the user is making regarding the DNT signal. This is simply not the case. A technical specification need only specify the requests and responses necessary for a DNT protocol to be implemented in a scalable and implementable solution across all browsers and the servers called. A technical specification should not inform the user regarding a policy or compliance choice but instead should inform the technical community on how to implement a technical solution. The compliance specification for the DNT signal should be left to the compliance regime, whether it is a national compliance regime, a W3C-based compliance regime or an industry-based compliance regime. Porting definitions from a particular compliance regime into the TPE only serves to provide an incomplete and confusing picture to those attempting to implement the technical protocol. Porting an overly broad or unclear definition of Tracking into the TPE does nothing to help the user understand his or her DNT choice. The user preference that should be supported within the scope of the TPE is fairly simple - to send or not send a DNT signal. Such a preference choice is easily supported by the TPE without importing definitions from the TCS. Specifically, I object to this definition of tracking to the extent that it contains words and phrases that are yet to be fully explored and defined within the TPWG. For example, it is already admitted that “context” is an undefined term. Also, “Data Controller” and “multiple distinct contexts” are not defined. In the non-normative text offered with this proposal, there is a proposed definition for context. But this definition has not been vetted within the TPWG. This highlights the process issues with attempting to define a crucial compliance term without first defining or at the same time defining the necessary terms contained in the proposed definition. If the co-chairs dismiss Option C, although I have serious objections against both Option A and Option B, I would prefer Option A over Option B.

Results of Questionnaire [Call for Objections] Tracking definition - Web-Based Straw-poll and Balloting System

Objections to Option A: Tracking across multiple distinct contexts


Input: [Responder] Shane Wiley

Output: I believe moving forward with this definition will only create further confusion with how to fairly set expectations with users. Outside of the strong question of whether a definition is needed here in the context of a pure technical specification, this definition lacks certainty for implementers. Many elements, chiefly “context”, are unclear in this definition which will lead some to believe the scope is either broader or more narrow than expected.

Results of Questionnaire [Call for Objections] Tracking definition - Web-Based Straw-poll and Balloting System

Objections to Option A: Tracking across multiple distinct contexts


Input: [Description] The speech recognition confidence level, a float value in the range of 0.0 to 1.0. Results are rejected (a nomatch event is thrown) when application.lastresult$.confidence is below this threshold. A value of 0.0 means minimum confidence is needed for a recognition, and a value of 1.0 requires maximum confidence. The value is a Real Number Designation (see 8.4 Value Designations). [Default] 0.5 [Name]

Output: confidencelevel

Voice Extensible Markup Language (VoiceXML) 3.0

Table 65: Speech Recognition Properties


Input: [Description] Set the sensitivity level. A value of 1.0 means that it is highly sensitive to quiet input. A value of 0.0 means it is least sensitive to noise. The value is a Real Number Designation (see 8.4 Value Designations). [Default] 0.5 [Name]

Output: sensitivity

Voice Extensible Markup Language (VoiceXML) 3.0

Table 65: Speech Recognition Properties


Input: [Description] A hint specifying the desired balance between speed vs. accuracy. A value of 0.0 means fastest recognition. A value of 1.0 means best accuracy. The value is a Real Number Designation (see 8.4 Value Designations). [Default] 0.5 [Name]

Output: speedvsaccuracy

Voice Extensible Markup Language (VoiceXML) 3.0

Table 65: Speech Recognition Properties


Input: [Description] The length of silence required following user speech before the speech recognizer finalizes a result (either accepting it or throwing a nomatch event). The complete timeout is used when the speech is a complete match of an active grammar. By contrast, the incomplete timeout is used when the speech is an incomplete match to an active grammar. A long complete timeout value delays the result completion and therefore makes the computer's response slow. A short complete timeout may lead to an utterance being broken up inappropriately. Reasonable complete timeout values are typically in the range of 0.3 seconds to 1.0 seconds. The value is a Time Designation (see 8.4 Value Designations). See 8.3 Speech and DTMF Input Timing Properties. Although platforms must parse the completetimeout property, platforms are not required to support the behavior of completetimeout. Platforms choosing not to support the behavior of completetimeout must so document and adjust the behavior of the incompletetimeout property as described below. [Default] platform-dependent [Name]

Output: completetimeout

Voice Extensible Markup Language (VoiceXML) 3.0

Table 65: Speech Recognition Properties


Input: [Description] The required length of silence following user speech after which a recognizer finalizes a result. The incomplete timeout applies when the speech prior to the silence is an incomplete match of all active grammars. In this case, once the timeout is triggered, the partial result is rejected (with a nomatch event). The incomplete timeout also applies when the speech prior to the silence is a complete match of an active grammar, but where it is possible to speak further and still match the grammar. By contrast, the complete timeout is used when the speech is a complete match to an active grammar and no further words can be spoken. A long incomplete timeout value delays the result completion and therefore makes the computer's response slow. A short incomplete timeout may lead to an utterance being broken up inappropriately. The incomplete timeout is usually longer than the complete timeout to allow users to pause mid-utterance (for example, to breathe). See 8.3 Speech and DTMF Input Timing Properties Platforms choosing not to support the completetimeout property (described above) must use the maximum of the completetimeout and incompletetimeout values as the value for the incompletetimeout. The value is a Time Designation (see 8.4 Value Designations). [Default] undefined? [Name]

Output: incompletetimeout

Voice Extensible Markup Language (VoiceXML) 3.0

Table 65: Speech Recognition Properties


Input: [Description] The maximum duration of user speech. If this time elapsed before the user stops speaking, the event "maxspeechtimeout" is thrown. The value is a Time Designation (see 8.4 Value Designations). [Default] platform-dependent [Name]

Output: maxspeechtimeout

Voice Extensible Markup Language (VoiceXML) 3.0

Table 65: Speech Recognition Properties


Input: [Patterns] RDF terms [Query Forms] SELECT [Modifiers]

Output: DISTINCT


Input: [Patterns] triple patterns [Query Forms] CONSTRUCT [Modifiers]

Output: REDUCED


Input: [Patterns] Basic graph patterns [Query Forms] DESCRIBE [Modifiers]

Output: PROJECT


Input: [Patterns] Groups [Query Forms] ASK [Modifiers]

Output: ORDER BY


Input: [Patterns] OPTIONAL [Modifiers]

Output: LIMIT


Input: [Patterns] UNION [Modifiers]

Output: OFFSET


Input: [Patterns] GRAPH [Modifiers]

Output: GROUP BY


Input: [Patterns] NOT EXISTS [Modifiers]

Output: HAVING


Input: [Patterns] EXISTS [Modifiers]

Output: Select expressions


Input: [0] doctype [1] ro attribute [3] yes [2]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] implementation [1] ro attribute [3] yes [2]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] documentElement [1] ro attribute [3] yes [2]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createElement [1] method [3] yes [2]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createDocumentFragment [1] method [3] yes [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createTextNode [1] method [3] yes [2]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createComment [1] method [3] no [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createCDATASection [1] method [3] yes [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createProcessingInstruction [1] method [3] no [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createAttribute [1] method [3] yes [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createEntityReference [1] method [3] no [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] getElementsByTagName [1] method [3] yes [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] importNode [1] method [3] no [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createElementNS [1] method [3] yes [2]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createAttributeNS [1] method [3] yes [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] getElementsByTagNameNS [1] method [3] yes [2]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] getElementById [1] method [3] yes [2]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


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: [Semantics] Policy expressions that are formal contracts (or licenses) stipulating all the terms of usage and all the parties involved. [Comment] Must contain at least the Party entity with Assigner role and a Party with Assignee role. The latter being granted the terms of the Agreement from the former. [Identifier]

Output: Agreement

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

Table 2.1: Terms for the entity Type of the Policy Entity


Input: [Semantics] Policy expressions that propose terms of usage from an Asset owner [Comment] Must contain a Party entity with Assigner role. The Offer may contain a Party entity with Assignee role, but does not grant any privileges to that Party. [Identifier]

Output: Offer

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] Policy expressions that stipulate the terms of usage over personal information. [Comment] Must contain at least the Party entity with Assigner role and a Party with Assignee role. Must also contain a Duty on the assignee related to obligations towards managing the assigner’s Asset containing personal information. The Assignee is being granted the terms of the Privacy policy from the Assigner. [Identifier]

Output: Privacy

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] Policy expressions that propose terms of usage to an Asset owner [Comment] Must contain a Party entity with Assignee role. The Request may also contain the Party entity with Assigner role if this is known. No privileges are granted to any Party. [Identifier]

Output: Request

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] Policy expressions that consists of entities from the complete model [Comment] The Set is aimed at scenarios where there is an open criteria for the semantics of the policy expressions and typically refined by other systems/profiles that process the information at a later time. No privileges are granted to any Party. [Identifier]

Output: Set

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] Policy expressions that stipulate the terms of usage and is redeemable by any Party who currently holds the Ticket in their possession [Comment] May contain the Party entity with Assigner role and the Party entity with Assignee role. A Ticket (or Voucher) may be anonymous or personalised, where the holder of that Ticket may remain unknown or has to be identified. The holder, or if known, the Assignee, is being granted the terms of the Ticket from the Assigner (in known). [Identifier]

Output: Ticket

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] Agreement [Comment] Must contain at least the Party entity with Assigner role and a Party with Assignee role. The latter being granted the terms of the Agreement from the former. [Semantics]

Output: Policy expressions that are formal contracts (or licenses) stipulating all the terms of usage and all the parties involved.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] Offer [Comment] Must contain a Party entity with Assigner role. The Offer may contain a Party entity with Assignee role, but does not grant any privileges to that Party. [Semantics]

Output: Policy expressions that propose terms of usage from an Asset owner

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] Privacy [Comment] Must contain at least the Party entity with Assigner role and a Party with Assignee role. Must also contain a Duty on the assignee related to obligations towards managing the assigner’s Asset containing personal information. The Assignee is being granted the terms of the Privacy policy from the Assigner. [Semantics]

Output: Policy expressions that stipulate the terms of usage over personal information.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] Request [Comment] Must contain a Party entity with Assignee role. The Request may also contain the Party entity with Assigner role if this is known. No privileges are granted to any Party. [Semantics]

Output: Policy expressions that propose terms of usage to an Asset owner

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] Set [Comment] The Set is aimed at scenarios where there is an open criteria for the semantics of the policy expressions and typically refined by other systems/profiles that process the information at a later time. No privileges are granted to any Party. [Semantics]

Output: Policy expressions that consists of entities from the complete model

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] Ticket [Comment] May contain the Party entity with Assigner role and the Party entity with Assignee role. A Ticket (or Voucher) may be anonymous or personalised, where the holder of that Ticket may remain unknown or has to be identified. The holder, or if known, the Assignee, is being granted the terms of the Ticket from the Assigner (in known). [Semantics]

Output: Policy expressions that stipulate the terms of usage and is redeemable by any Party who currently holds the Ticket in their possession

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [WCAG 2.0 checkpoint] 1.1 Provide a text equivalent for all non-text content. [Examples and Techniques]

Output: Generated content

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 1.2 Synchronize text equivalents with multimedia presentations. [Manual checks] N/A [Auto checks] N/A [Examples and Techniques]

Output: Refer to client-side scripting techniques

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 1.3 Synchronize a description of the essential visual information in multimedia presentations. [Manual checks] N/A [Auto checks] N/A [Examples and Techniques]

Output: Refer to client-side scripting techniques

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 2.1 Provide more than one path or method to find content. [Manual checks] N/A [Auto checks] N/A [Examples and Techniques]

Output: Refer to Core techniques

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 2.2 Provide consistent responses to user actions. [Manual checks] N/A [Auto checks] N/A [Examples and Techniques]

Output: Refer to client-side scripting techniques

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 2.3 Give users control of mechanisms that cause extreme changes in context. [Manual checks] N/A [Auto checks] N/A [Examples and Techniques]

Output: Refer to client-side scripting techniques

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 2.4 Give users control over how long they can spend reading or interacting with content. [Manual checks] N/A [Auto checks] N/A [Examples and Techniques]

Output: Refer to client-side scripting techniques

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 2.5 Use device-independent event handlers. [Manual checks] N/A [Auto checks] N/A [Examples and Techniques]

Output: Refer to client-side scripting techniques

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 3.3 Write clearly and simply. [Manual checks] N/A [Auto checks] N/A [Examples and Techniques]

Output: Refer to Core techniques

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 3.5 Summarize complex information. [Manual checks] N/A [Auto checks] N/A [Examples and Techniques]

Output: Refer to Core techniques

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 3.6 Define key terms, abbreviations, acronyms, and specialized language. [Manual checks] N/A [Auto checks] N/A [Examples and Techniques]

Output: Refer to Core techniques

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [WCAG 2.0 checkpoint] 3.7 Divide information into smaller, more manageable units. [Manual checks] N/A [Auto checks] N/A [Examples and Techniques]

Output: Refer to Core techniques

PDF Techniques for Web Content Accessibility Guidelines 13 September 2001


Input: [Semantics] The Assigner requires that the Assignee(s) accepts that the use of the Asset may be tracked [Comment] The collected information may be tracked by the Assigner, or may link to a Party with the role function “trackingParty”. [Identifier]

Output: acceptTracking

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

Table 2.2.2: Terms for entity Action used with Duty


Input: [Semantics] The Assigner requires that the Assignee(s) attributes the Asset to the Assigner or an attributed Party. [Comment] May link to an Asset with the attribution information. May link to a Party with the role function “attributedParty”. [Identifier]

Output: attribute

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Assigner requires that the Assignee(s) compensates the Assigner (or other specified compensation Party) by some amount of value, if defined, for use of the Asset. [Comment] The compensation may use different types of things with a value: – the thing is expressed by the value (term) of the Constraint name – the value is expressed by operator, rightOperand, dataType and unit [Identifier]

Output: compensate

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Assigner requires that the Assignee(s) permanently removes all copies of the Asset. [Comment] Use a constraint to define under which conditions the Asset should be deleted. [Identifier]

Output: delete

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Assignee requires that the Assigner(s) ensure(s) that the permission on the Asset is exclusive to the Assignee. [Identifier]

Output: ensureExclusivity

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Assigner requires that the Assignee(s) include(s) other related assets in the Asset. [Comment] For example; Bio picture must be included in the attribution. Use of the Asset relation attribute is required [Identifier]

Output: include

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Assigner requires that the Assignee(s) inform(s) the Assigner or an informed Party that an action has been performed on or in relation to the Asset. [Comment] May link to a Party with the role function “informedParty”. [Identifier]

Output: inform

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Assigner requires that the Assignee(s) grants the specified Policy to a third party for their use of the Asset. [Identifier]

Output: nextPolicy

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Assigner requires that the Assignee(s) obtains explicit consent from the Assigner or a consenting Party to perform the requested action in relation to the Asset. [Comment] Used as a Duty to ensure that the Assigner or a Party is authorized to approve such actions on a case-by-case basis. May link to a Party with the role function “consentingParty”. [Identifier]

Output: obtainConsent

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Assigner requires that the Assignee(s) has(ve) a person review the Policy applicable to the Asset. [Comment] Used when human intervention is required to review the Policy. May link to an Asset which represents the full Policy information. [Identifier]

Output: reviewPolicy

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Assigner requires that the Assignee(s) unload(s) and delete(s) the computer program Asset from a storage device and disable(s) its readiness for operation. [Comment] The Asset is no longer accessible to the Assignee(s). [Identifier]

Output: uninstall

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Assigner requires that the Assignee(s) apply(ies) a watermark as provided by the Assigner to the Asset. [Comment] It is recommended to embed a link to the watermark. [Identifier]

Output: watermark

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] Agreement [Semantics] Policy expressions that are formal contracts (or licenses) stipulating all the terms of usage and all the parties involved. [Comment]

Output: Must contain at least the Party entity with Assigner role and a Party with Assignee role. The latter being granted the terms of the Agreement from the former.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] Offer [Semantics] Policy expressions that propose terms of usage from an Asset owner [Comment]

Output: Must contain a Party entity with Assigner role. The Offer may contain a Party entity with Assignee role, but does not grant any privileges to that Party.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] Privacy [Semantics] Policy expressions that stipulate the terms of usage over personal information. [Comment]

Output: Must contain at least the Party entity with Assigner role and a Party with Assignee role. Must also contain a Duty on the assignee related to obligations towards managing the assigner’s Asset containing personal information. The Assignee is being granted the terms of the Privacy policy from the Assigner.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] Request [Semantics] Policy expressions that propose terms of usage to an Asset owner [Comment]

Output: Must contain a Party entity with Assignee role. The Request may also contain the Party entity with Assigner role if this is known. No privileges are granted to any Party.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] Set [Semantics] Policy expressions that consists of entities from the complete model [Comment]

Output: The Set is aimed at scenarios where there is an open criteria for the semantics of the policy expressions and typically refined by other systems/profiles that process the information at a later time. No privileges are granted to any Party.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] Ticket [Semantics] Policy expressions that stipulate the terms of usage and is redeemable by any Party who currently holds the Ticket in their possession [Comment]

Output: May contain the Party entity with Assigner role and the Party entity with Assignee role. A Ticket (or Voucher) may be anonymous or personalised, where the holder of that Ticket may remain unknown or has to be identified. The holder, or if known, the Assignee, is being granted the terms of the Ticket from the Assigner (in known).

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] eq [Semantics]

Output: The “Equals” operator indicating that a given value equals the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

Table 2.3.2: Terms for the attribute “operator” of the entity Constraint


Input: [Identifier] gt [Semantics]

Output: The “Greater Than” operator indicating that a given value is greater than the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] gteq [Semantics]

Output: The “Greater Than or Equal To” operator indicating that a given value is greater than or equal to the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] hasPart [Semantics]

Output: The “Has Part” operator indicating that a given value contains the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] isA [Semantics]

Output: The “Is A” operator indicating that a given value is an instance of the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] isAllOf [Semantics]

Output: The “Is All Of” operator indicating that a given value is all of the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] isAnyOf [Semantics]

Output: The “Is Any Of” operator indicating that a given value is any of the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] isNoneOf [Semantics]

Output: The “Is None Of” operator indicating that a given value is none of the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] isPartOf [Semantics]

Output: The “Is Part Of” operator indicating that a given value is contained by the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] lt [Semantics]

Output: The “Less Than” operator indicating that a given value is less than the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] lteq [Semantics]

Output: The “Less Than or Equal To” operator indicating that a given value is less than or equal to the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] neq [Semantics]

Output: The “Not Equal To” operator indicating that a given value is not equal to the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Party is a single individual [Comment] Must be supported. [Identifier]

Output: Individual

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

Table 2.4.2: Terms for the attribute “scope” of the entity Role


Input: [Semantics] The Party represents a defined group with multiple individual members [Comment] Must be supported. [Identifier]

Output: Group

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] All the collective individuals within a context [Comment] For example, may be used to indicate all the users of a specific social network the party is a member of. Note that “group” scope is also assumed. [Identifier]

Output: All

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] All the first-level connections of the Party [Comment] For example, may be used to indicate all “friends” of the Party. Note that “group” scope is also assumed. [Identifier]

Output: AllConnections

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] All the second-level connections of the Party [Comment] For example, may be used to indicate all “friends of friends” of the Party. Note that “group” scope is also assumed. [Identifier]

Output: All2ndConnections

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] All the group connections of the Party [Comment] For example, may be used to indicate all groups that the Party is a member of. Note that “group” scope is also assumed. [Identifier]

Output: AllGroups

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Contains source node unless a selection is being dragged, in which case it is empty [effectAllowed] uninitialized [dropEffect] none [Default Action] Initiate the drag-and-drop operation [Event Name]

Output: dragstart


Input: [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] none [Default Action] Continue the drag-and-drop operation [Event Name]

Output: drag


Input: [Target] Immediate user selection or the body element [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] Based on effectAllowed value [Default Action] Reject immediate user selection as potential target element [Event Name]

Output: dragenter


Input: [Target] Previous target element [Bubbles?] ✓ Bubbles [Cancelable?] — [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] none [Default Action] None [Event Name]

Output: dragleave


Input: [Target] Current target element [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] Based on effectAllowed value [Default Action] Reset the current drag operation to "none" [Event Name]

Output: dragover


Input: [Target] Current target element [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] getData() returns data set in dragstart event [effectAllowed] Same as last event [dropEffect] Current drag operation [Default Action] Varies [Event Name]

Output: drop


Input: [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] — [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] Current drag operation [Default Action] Varies [Event Name]

Output: dragend


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 white space separated NMTOKEN values [Attribute Type]

Output: NMTOKENS


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

Output: PCDATA


Input: [Requirement] Supports many device form factors [Description] Supports a wide variety of devices including desktop & laptop computers, smart phones, tablets, TVs, cameras, and other connected devices [Source] SysApps Charter [Implications]

Output: The security model can make no assumptions about how the device will be used or shared between people and cannot assume a particular process model.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] DAP API Support [Description] All APIs defined by DAP should be accessible to system applications [Source] SysApps Charter [Implications]

Output: Either DAP APIs will need to change slightly in the systems context or the security model must allow for API-specific access controls

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Minimal user prompting [Description] Problems such as 'double prompting' should be avoided when integrating other APIs [Source] SysApps Charter [Implications]

Output: Some details of the expected user interactions may need to be specified in the security model or APIs

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Communicate with other applications [Description] Applications can communicate with other applications [Implications]

Output: Some kind of messaging will be supported

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Communicate with pre-defined endpoints [Description] Applications can communicate with pre-defined web addresses [Implications]

Output: Access remote domains will be possible

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Trusted application source [Description] When installing or using an application for the first time, the runtime shall establish that the user trusts the source of the application. [Source] webinos [Implications]

Output: Apps must have provenance data attached to them

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] App stores can revoke applications [Description] "An app store needs to be able to approve an application, implying they can verify the permissions, integrity and authenticity of the app" [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications]

Output: App permissions can be changed remotely

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] External trusted party can set app default permissions [Description] B2G: "App store must be able to set the default permissions for an app". [Source] Extrapolated from B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications]

Output: The user is not the only source of access control decisions. this also suggests a need for conflict resolution.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Owner override [Description] The device owner must be able to override app settings and permissions (this may not be the user, but a corporate, for example) [Source] B2G (user), webinos (user) [Implications]

Output: Access control settings must be changeable

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] App privilege visibility [Description] Apps should be able to discover their privileges and degrade gracefully in a limited privilege environment [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications]

Output: There must be a standard way for applications to identify the permissions they have and lack

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Immunity to browser-based threats [Description] Apps should not be vulnerable to common web vulnerabilities when granted significant privileges [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications]

Output: Non-browser security context: may be additional restrictions on HTML/JavaScript

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Pre-installed app permissions [Description] Ability to grant trust for certain highly sensitive privileges (such as phone dialing) may be restricted at the OS level to specific trusted parties [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications]

Output: Different 'levels' apply to SysApps - possibly 'roles'

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Access to files outside owned by the platform [Description] Ability for a system application to access (read and write) files outside of that application's sandboxed storage area. [Source] Mailing list: http://lists.w3.org/Archives/Public/public-sysapps/2012Nov/0003.html [Implications]

Output: Need to provide both sandboxed and non-sandboxed storage

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Alarm API [Source] SysApps Charter [Description]

Output: Applications can create alarms, notifying users

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Contacts API [Source] SysApps Charter [Description]

Output: Apps can add, remove and edit contacts

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Messaging API [Source] SysApps Charter [Description]

Output: Apps can send, receive and view SMS

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Telephony API [Source] SysApps Charter [Description]

Output: Apps can access the telephony capabilities of the underlyling platform: dial a number, pick up a call, route to voicemail, access the call log

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Raw Sockets API [Source] SysApps Charter [Description]

Output: Apps can create, manipulate and listen for low-level TCP and UDP connections

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Supports many device form factors [Source] SysApps Charter [Implications] The security model can make no assumptions about how the device will be used or shared between people and cannot assume a particular process model. [Description]

Output: Supports a wide variety of devices including desktop & laptop computers, smart phones, tablets, TVs, cameras, and other connected devices

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] DAP API Support [Source] SysApps Charter [Implications] Either DAP APIs will need to change slightly in the systems context or the security model must allow for API-specific access controls [Description]

Output: All APIs defined by DAP should be accessible to system applications

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Minimal user prompting [Source] SysApps Charter [Implications] Some details of the expected user interactions may need to be specified in the security model or APIs [Description]

Output: Problems such as 'double prompting' should be avoided when integrating other APIs

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] HTML5 [Description]

Output: Applications consist of HTML, CSS and JavaScript

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Location [Description]

Output: Applications have access to geolocation data

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Communicate with other applications [Implications] Some kind of messaging will be supported [Description]

Output: Applications can communicate with other applications

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Communicate with pre-defined endpoints [Implications] Access remote domains will be possible [Description]

Output: Applications can communicate with pre-defined web addresses

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Valid across multiple platforms [Source] Compatibility of application packages [Description]

Output: Applications can run on any conformant platform, potentially including any device form factor

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Access control log [Source] webinos [Description]

Output: Allow access control decisions to be logged.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] API access rationale [Source] webinos [Description]

Output: Applications shall be able to explain why access to data or APIs is being requested.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Application capability restriction [Source] webinos [Description]

Output: Applications shall access only its specified device features, extensions and content.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Application intent [Source] webinos [Description]

Output: Applications shall specify its required functionality at install time or during updates.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Application isolation [Source] webinos [Description]

Output: Applications shall be isolated from each other.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Application policy approval [Source] webinos [Description]

Output: Changes to existing application intentions and permissions shall be approved by the end user.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Authenticity check [Source] webinos [Description]

Output: Before being installed or updated, origin authenticity and integrity checks shall be performed by the runtime

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Certifier list [Source] webinos [Description]

Output: The list of authorities that certified an application shall be viewable by end-users.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Confidential credentials storage [Source] webinos [Description]

Output: The webinos runtime shall support the confidential storage of user credentials.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Credentials access restriction [Source] webinos [Description]

Output: Access to credentials storage shall be limited to a specific user, a specific device and a set of applications.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Data management rationale [Source] webinos [Description]

Output: applications shall be able to explain how collected sensitive data will be managed.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Default policy [Source] webinos [Description]

Output: A default security and privacy policy shall exist an be enforced on each conformant runtime

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Device-identity binding [Source] webinos [Description]

Output: Personal devices shall be bound to their owner's identities.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Device-identity binding revokation [Source] webinos [Description]

Output: The binding between personal devices and owner's identity shall be revokable.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Hierarchical policy enforcement [Source] webinos [Description]

Output: Runtimes can enforce multiple access control rules written by multiple stakeholders in a hierarchy.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Secure cache [Source] webinos [Description]

Output: Data cached by a runtime shall be securely stored to prevent disclosure and tampering by unauthorised entitites.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Secure storage [Source] webinos [Description]

Output: Application data shall be securely stored to prevent disclosure and tampering by unauthorised entities.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Trusted application source [Source] webinos [Implications] Apps must have provenance data attached to them [Description]

Output: When installing or using an application for the first time, the runtime shall establish that the user trusts the source of the application.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] App stores can revoke applications [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications] App permissions can be changed remotely [Description]

Output: "An app store needs to be able to approve an application, implying they can verify the permissions, integrity and authenticity of the app"

System Applications WG: Security Model - W3C Wiki