Input: [Scenario] When an accessibility subtree is inserted [MSAA] EVENT_OBJECT_REORDER [ATK/AT-SPI event] children_changed::add [Mac OS X Notification]

Output: AXUIElementCreated If in a live region, AXLiveRegionChanged

WAI-ARIA 1.0 User Agent Implementation Guide


Input: [Scenario] When an accessibility subtree is moved [MSAA] Treat it as a removal from one place and insertion in another [ATK/AT-SPI event] Treat it as a removal from one place and insertion in another [Mac OS X Notification]

Output: AXUIElementDestroyed/ AXUIElementCreated If in a live region, AXLiveRegionChanged

WAI-ARIA 1.0 User Agent Implementation Guide

Table of document change scenarios and events to be fired in each API


Input: [Scenario] When an accessibility subtree is changed (e.g. replaceNode) [MSAA] Treat it as a removal and insertion [ATK/AT-SPI event] Treat it as a removal and insertion [Mac OS X Notification]

Output: AXUIElementDestroyed/ AXUIElementCreated If in a live region, AXLiveRegionChanged

WAI-ARIA 1.0 User Agent Implementation Guide


Input: [Name Space] VML [Type] string [Default Value] null [Description] A unique ID that identifies the shadow on a shape. Used by script to reference the shape in a collection. [Attribute]

Output: id


Input: [Name Space] VML [Type] boolean [Default Value] true [Description] Turns the display of the shadow on and off. [Attribute]

Output: on


Input: [Name Space] VML [Type] string [Default Value] single [Description] Can have the values: "single | double | emboss | perspective" [Attribute]

Output: type


Input: [Name Space] VML [Type] boolean [Default Value] false [Description] See through the shadow if there is no fill on the shape. [Attribute]

Output: obscured


Input: [Name Space] VML [Type] boolean [Default Value] gray RGB(128,128,128) [Description] The color of the primary shadow. [Attribute]

Output: color


Input: [Name Space] VML [Type] number [Default Value] 1.0 [Description] Opacity of the shadow effect. [Attribute]

Output: opacity


Input: [Name Space] VML [Type] vector2D [Default Value] 2pt,2pt [Description] Amount of x,y offset from the shapes location. Values are either an absolute measurement, or a fractional value of shape 0.5 to +0.5. [Attribute]

Output: offset


Input: [Name Space] VML [Type] boolean [Default Value] gray RGB(203,203,203) [Description] The color of the second shadow, or highlight in an embossed or engraved shadow.. [Attribute]

Output: color2


Input: [Name Space] VML [Type] vector2D [Default Value] 0pt,0pt [Description] Amount of x,y of second offset from the shapes location. Values are either an absolute measurement, or a fractional value of shape 0.5 to +0.5. [Attribute]

Output: offset2


Input: [Name Space] VML [Type] vector2D [Default Value] 0,0 [Description] A pair of fractional values of shape 0.5 to +0.5. [Attribute]

Output: origin


Input: [Name Space] VML [Type] string [Default Value] null [Description] A perspective transform matrix in the form, "sxx,sxy,syx,syy,px,py" [s=scale, p=perspective] If offset is in absolute units then px,py are in units emu-1, otherwise they are an inverse fraction of shape size. [Attribute]

Output: matrix


Input: [0] GET [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict, GSP returns undefined [LDP Container = GSP endpoint] No conflict, GSP returns undefined [LDP Container = GSP graph]

Output: No conflict

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] HEAD [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict; added LDP headers [LDP Container = GSP endpoint] No conflict; added LDP headers [LDP Container = GSP graph]

Output: No conflict; added LDP headers

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] OPTIONS [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict; added LDP headers [LDP Container = GSP endpoint] No conflict; added LDP headers [LDP Container = GSP graph]

Output: No conflict; added LDP headers

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] PUT [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] Conflict [LDP Container = GSP endpoint] Conflict [LDP Container = GSP graph]

Output: No conflict

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] POST [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] Conflict [LDP Container = GSP endpoint] Conflict [LDP Container = GSP graph]

Output: No conflict? Different functionality is to be expected, but do not influence each other

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] DELETE [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict [LDP Container = GSP endpoint] No conflict [LDP Container = GSP graph]

Output: No conflict

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] PATCH [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict [LDP Container = GSP endpoint] No conflict [LDP Container = GSP graph]

Output: Conflict; changes through GSP can break consistency in LDPC

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [Event Name] dragstart [Target] Source node [Cancelable?] ✓ Cancelable [Drag data store mode] Read/write mode [Default Action] Initiate the drag-and-drop operation [dropEffect]

Output: "none"

7.6 Drag and drop — HTML5: Edition for Web Authors


Input: [Event Name] drag [Target] Source node [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [Default Action] Continue the drag-and-drop operation [dropEffect]

Output: "none"

7.6 Drag and drop — HTML5: Edition for Web Authors


Input: [Event Name] dragenter [Target] Immediate user selection or the body element [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [Default Action] Reject immediate user selection as potential target element [dropEffect]

Output: Based on effectAllowed value

7.6 Drag and drop — HTML5: Edition for Web Authors


Input: [Event Name] dragleave [Target] Previous target element [Cancelable?] — [Drag data store mode] Protected mode [Default Action] None [dropEffect]

Output: "none"

7.6 Drag and drop — HTML5: Edition for Web Authors


Input: [Event Name] dragover [Target] Current target element [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [Default Action] Reset the current drag operation to "none" [dropEffect]

Output: Based on effectAllowed value

7.6 Drag and drop — HTML5: Edition for Web Authors


Input: [Event Name] drop [Target] Current target element [Cancelable?] ✓ Cancelable [Drag data store mode] Read-only mode [Default Action] Varies [dropEffect]

Output: Current drag operation

7.6 Drag and drop — HTML5: Edition for Web Authors


Input: [Event Name] dragend [Target] Source node [Cancelable?] — [Drag data store mode] Protected mode [Default Action] Varies [dropEffect]

Output: Current drag operation

7.6 Drag and drop — HTML5: Edition for Web Authors


Input: [Control Type] Text input (including date/time and password fields) [LiveCycle Placement Rules]

Output: Default placement for the label is to the left of the control. If this is not possible, LiveCycle will attempt to place it immediately above the control.

PDF Techniques | Techniques for WCAG 2.0


Input: [Control Type] Checkbox [LiveCycle Placement Rules]

Output: Default placement for the label is to the right of the check box.

PDF Techniques | Techniques for WCAG 2.0


Input: [Control Type] Radio button group [LiveCycle Placement Rules]

Output: Default placement for the label for each individual radio button is to the right of the button. Create a visible caption for the radio button group by creating static text and placing it to the left of or above the group. (See Labeling radio buttons below.)

PDF Techniques | Techniques for WCAG 2.0


Input: [Control Type] Combo box [LiveCycle Placement Rules]

Output: Default placement for the label is to the left of the drop-down list. If this is not possible, LiveCycle will attempt to place it immediately above the control..

PDF Techniques | Techniques for WCAG 2.0


Input: [Control Type] List box [LiveCycle Placement Rules]

Output: Default placement for the label is above the list box.

PDF Techniques | Techniques for WCAG 2.0


Input: [Control Type] Button [LiveCycle Placement Rules]

Output: LiveCycle automatically places the label on the button; it does not have to be positioned manually. Ensure that the button's purpose is properly described in the label text.

PDF Techniques | Techniques for WCAG 2.0


Input: [Event handler] onabort [Event handler event type]

Output: abort


Input: [Event handler] oncancel [Event handler event type]

Output: cancel


Input: [Event handler] oncanplay [Event handler event type]

Output: canplay


Input: [Event handler] oncanplaythrough [Event handler event type]

Output: canplaythrough


Input: [Event handler] onchange [Event handler event type]

Output: change


Input: [Event handler] onclick [Event handler event type]

Output: click


Input: [Event handler] onclose [Event handler event type]

Output: close


Input: [Event handler] oncontextmenu [Event handler event type]

Output: contextmenu


Input: [Event handler] oncuechange [Event handler event type]

Output: cuechange


Input: [Event handler] ondblclick [Event handler event type]

Output: dblclick


Input: [Event handler] ondrag [Event handler event type]

Output: drag


Input: [Event handler] ondragend [Event handler event type]

Output: dragend


Input: [Event handler] ondragenter [Event handler event type]

Output: dragenter


Input: [Event handler] ondragleave [Event handler event type]

Output: dragleave


Input: [Event handler] ondragover [Event handler event type]

Output: dragover


Input: [Event handler] ondragstart [Event handler event type]

Output: dragstart


Input: [Event handler] ondrop [Event handler event type]

Output: drop


Input: [Event handler] ondurationchange [Event handler event type]

Output: durationchange


Input: [Event handler] onemptied [Event handler event type]

Output: emptied


Input: [Event handler] onended [Event handler event type]

Output: ended


Input: [Event handler] oninput [Event handler event type]

Output: input


Input: [Event handler] oninvalid [Event handler event type]

Output: invalid


Input: [Event handler] onkeydown [Event handler event type]

Output: keydown


Input: [Event handler] onkeypress [Event handler event type]

Output: keypress


Input: [Event handler] onkeyup [Event handler event type]

Output: keyup


Input: [Event handler] onloadeddata [Event handler event type]

Output: loadeddata


Input: [Event handler] onloadedmetadata [Event handler event type]

Output: loadedmetadata


Input: [Event handler] onloadstart [Event handler event type]

Output: loadstart


Input: [Event handler] onmousedown [Event handler event type]

Output: mousedown


Input: [Event handler] onmousemove [Event handler event type]

Output: mousemove


Input: [Event handler] onmouseout [Event handler event type]

Output: mouseout


Input: [Event handler] onmouseover [Event handler event type]

Output: mouseover


Input: [Event handler] onmouseup [Event handler event type]

Output: mouseup


Input: [Event handler] onmousewheel [Event handler event type]

Output: mousewheel


Input: [Event handler] onpause [Event handler event type]

Output: pause


Input: [Event handler] onplay [Event handler event type]

Output: play


Input: [Event handler] onplaying [Event handler event type]

Output: playing


Input: [Event handler] onprogress [Event handler event type]

Output: progress


Input: [Event handler] onratechange [Event handler event type]

Output: ratechange


Input: [Event handler] onreset [Event handler event type]

Output: reset


Input: [Event handler] onseeked [Event handler event type]

Output: seeked


Input: [Event handler] onseeking [Event handler event type]

Output: seeking


Input: [Event handler] onselect [Event handler event type]

Output: select


Input: [Event handler] onshow [Event handler event type]

Output: show


Input: [Event handler] onstalled [Event handler event type]

Output: stalled


Input: [Event handler] onsubmit [Event handler event type]

Output: submit


Input: [Event handler] onsuspend [Event handler event type]

Output: suspend


Input: [Event handler] ontimeupdate [Event handler event type]

Output: timeupdate


Input: [Event handler] onvolumechange [Event handler event type]

Output: volumechange


Input: [Event handler] onwaiting [Event handler event type]

Output: waiting


Input: [WSC Clause] I [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] II [Opera] Conforms Advanced [Firefox] Conforms Advanced [Chrome]

Output: Conforms Advanced


Input: [WSC Clause] IIa [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] IV [Opera] NA [Firefox] NA [Chrome]


Input: [WSC Clause] V [Opera] Conforms Optional [Firefox] Does Not Conform Optional [Chrome]

Output: Does Not Conform Optional


Input: [WSC Clause] VI [Opera] Conforms Advanced [Firefox] Conforms Advanced [Chrome]

Output: Conforms Advanced


Input: [WSC Clause] VII [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] VIII [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] IX [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] X [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XI [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XII [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XIII [Opera] Conforms Optional [Firefox] Conforms Optional [Chrome]

Output: Does Not Conform Optional


Input: [WSC Clause] XIV [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XV [Opera] Conforms Optional [Firefox] Conforms Optional [Chrome]

Output: Conforms Optional


Input: [WSC Clause] XVI [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XVII [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XVIII [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XIX [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XX [Opera] Conforms Optional [Firefox] Conforms Optional [Chrome]

Output: Conforms Optional


Input: [WSC Clause] XXI [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XXII [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XXIII [Opera] NA [Firefox] NA [Chrome]


Input: [WSC Clause] XXIV [Opera] Conforms Optional [Firefox] Conforms Optional [Chrome]

Output: Does Not Conform Optional


Input: [WSC Clause] XXV [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XXVI [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XXVII [Opera] NA [Firefox] NA [Chrome]


Input: [WSC Clause] XXVIII [Opera] NA [Firefox] NA [Chrome]


Input: [WSC Clause] XXIX [Opera] NA [Firefox] NA [Chrome]


Input: [WSC Clause] XXX [Opera] NA [Firefox] NA [Chrome]


Input: [WSC Clause] XXXI [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XXXII [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XXXIII [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XXXIV [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XXXV [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XXXVI [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XXXVII [Opera] Conforms Optional [Firefox] Conforms Optional [Chrome]

Output: Conforms Optional


Input: [WSC Clause] XXXVIII [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XXXIX [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XL [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XLI [Opera] Conforms Optional [Firefox] Conforms Optional [Chrome]

Output: Conforms Optional


Input: [WSC Clause] XLII [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XLIII [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XLIV [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XLV [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XLVI [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XLVII [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XLVIII [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XLIX [Opera] Conforms Advanced [Firefox] Conforms Advanced [Chrome]

Output: Conforms Advanced


Input: [WSC Clause] L [Opera] Conforms Advanced [Firefox] Conforms Advanced [Chrome]

Output: Conforms Advanced


Input: [WSC Clause] LI [Opera] Does Not Conform Advanced [Firefox] Conforms Advanced [Chrome]

Output: Conforms Advanced


Input: [WSC Clause] LII [Opera] Does Not Conform Advanced [Firefox] Conforms Advanced [Chrome]

Output: Does Not Conform Advanced


Input: [WSC Clause] LIII [Opera] Conforms Advanced [Firefox] Conforms Advanced [Chrome]

Output: Conforms Advanced


Input: [WSC Clause] LIV [Opera] Conforms Advanced [Firefox] Conforms Advanced [Chrome]

Output: Conforms Advanced


Input: [WSC Clause] LV [Opera] NA [Firefox] NA [Chrome]


Input: [WSC Clause] LVI [Opera] Does Not Conform Optional [Firefox] Does Not Conform Optional [Chrome]

Output: Conforms Optional


Input: [WSC Clause] LVII [Opera] Does Not Conform Optional [Firefox] Conforms Optional [Chrome]

Output: Does Not Conform Optional


Input: [WSC Clause] LVIII [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] LIX [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] LX [Opera] Conforms Advanced [Firefox] Conforms Advanced [Chrome]

Output: Conforms Advanced


Input: [WSC Clause] LXI [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] LXII [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] LXIII [Opera] NA [Firefox] NA [Chrome]


Input: [WSC Clause] LXIV [Opera] NA [Firefox] NA [Chrome]


Input: [WSC Clause] LXV [Opera] Conforms Advanced [Firefox] Conforms Advanced [Chrome]

Output: Conforms Advanced


Input: [WSC Clause] LXVI [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] LXVII [Opera] Conforms Advanced [Firefox] Conforms Advanced [Chrome]

Output: Conforms Advanced


Input: [WSC Clause] LXVIII [Opera] Conforms Optional [Firefox] Conforms Optional [Chrome]

Output: Conforms Optional


Input: [WSC Clause] LXIX [Opera] Conforms Optional [Firefox] Does Not Conform Optional [Chrome]

Output: Does Not Conform Optional


Input: [WSC Clause] LXX [Opera] Conforms Advanced [Firefox] Conforms Advanced [Chrome]

Output: Conforms Advanced


Input: [WSC Clause] LXXI [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] LXXII [Opera] Conforms Advanced [Firefox] Conforms Advanced [Chrome]

Output: Conforms Advanced


Input: [WSC Clause] LXXIII [Opera] Conforms Advanced [Firefox] Conforms Advanced [Chrome]

Output: Conforms Advanced


Input: [WSC Clause] LXXIV [Opera] Conforms Advanced [Firefox] Conforms Advanced [Chrome]

Output: Conforms Advanced


Input: [WSC Clause] LXXV [Opera] NA [Firefox] NA [Chrome]


Input: [WSC Clause] LXXVI [Opera] NA [Firefox] NA [Chrome]


Input: [WSC Clause] LXXVII [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] LXXVIII [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] LXXIX [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] LXXX [Opera] Does Not Conform Advanced [Firefox] Conforms Advanced [Chrome]

Output: Conforms Advanced


Input: [WSC Clause] LXXXI [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] LXXXII [Opera] NA [Firefox] NA [Chrome]


Input: [WSC Clause] LXXXIII [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] LXXXIV [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] LXXXV [Opera] Conforms Advanced [Firefox] Conforms Advanced [Chrome]

Output: Conforms Advanced


Input: [WSC Clause] LXXXVI [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] LXXXVII [Opera] Conforms Optional [Firefox] Conforms Optional [Chrome]

Output: Conforms Optional


Input: [WSC Clause] LXXXVIII [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] LXXXIX [Opera] Conforms Advanced [Firefox] Conforms Advanced [Chrome]

Output: Conforms Advanced


Input: [WSC Clause] XC [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XCI [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XCII [Opera] Conforms Advanced [Firefox] Conforms Advanced [Chrome]

Output: Conforms Advanced


Input: [WSC Clause] XCIII [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XCIV [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XCV [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XCVI [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XCVII [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XCVIII [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] XCIX [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] C [Opera] Conforms Advanced [Firefox] Conforms Advanced [Chrome]

Output: Conforms Advanced


Input: [WSC Clause] CI [Opera] NA [Firefox] NA [Chrome]


Input: [WSC Clause] CII [Opera] Conforms Advanced [Firefox] Conforms Advanced [Chrome]

Output: Conforms Advanced


Input: [WSC Clause] CIII [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] CIV [Opera] Conforms Basic [Firefox] Conforms Basic [Chrome]

Output: Conforms Basic


Input: [WSC Clause] CV [Opera] Conforms Advanced [Firefox] Conforms Advanced [Chrome]

Output: Conforms Advanced


Input: [WSC Clause] CVI [Opera] Conforms Advanced [Firefox] Conforms Advanced [Chrome]

Output: Conforms Advanced


Input: [Evaluation] Bandwidth efficiency [Picture Element] Yes, requests only what it needs [image-set CSS/uri templates] Yes, requests only what it needs [Spacer background-image] Yes, requests only what it needs [Request headers]

Output: Yes, requests only what it needs


Input: [Evaluation] Single HTTP request [Picture Element] Yes [image-set CSS/uri templates] Yes [Spacer background-image] Yes [Request headers]

Output: Yes


Input: [Evaluation] Server-side config not required [Picture Element] Client based [image-set CSS/uri templates] Client based [Spacer background-image] Client based [Request headers]

Output: Server-config required


Input: [Evaluation] Structure Simplicity (HTML) [Picture Element] Difficult for beginners [image-set CSS/uri templates] (structure not decided, only focuses on CSS) [Spacer background-image] Existing elements [Request headers]

Output: No changes


Input: [Evaluation] Presentation Simplicity (CSS) [Picture Element] Yes [image-set CSS/uri templates] Difficult for beginners, but consistent image-set for backgrounds [Spacer background-image] Heavy use of media queries [Request headers]

Output: No changes


Input: [Evaluation] Easy of maintenance [Picture Element] Responsive scenarios within structure [image-set CSS/uri templates] Control image variants with CSS [Spacer background-image] Control image variants with CSS [Request headers]

Output: Server-side config


Input: [Evaluation] Separation of concerns [Picture Element] Presentation scenarios within structure [image-set CSS/uri templates] Control image variants with CSS [Spacer background-image] Control image variants with CSS [Request headers]

Output: Depends on implementation


Input: [Evaluation] Declarative? (e.g provides semantic hooks for sizes) [Picture Element] Yes [image-set CSS/uri templates] This is only CSS, so it allows the markup to be declarative too. Additionally, it provides the browser with request formats and presentation scenarios which can be reused sitewide. [Spacer background-image] No [Request headers]

Output: No


Input: [Evaluation] Centralized image variants [Picture Element] Located within structure [image-set CSS/uri templates] Variants formats within image-set() urls [Spacer background-image] Variants within media queries [Request headers]

Output: Depends on implementation


Input: [Evaluation] Request static images [Picture Element] Yes [image-set CSS/uri templates] Yes [Spacer background-image] Yes [Request headers]

Output: Yes


Input: [Evaluation] Request dynamically resized images [Picture Element] Manually code dimensions within urls [image-set CSS/uri templates] Request exact dimension needed [Spacer background-image] Manually code dimensions within urls [Request headers]

Output: Yes


Input: [Evaluation] High-resolution when the device is capable [Picture Element] Yes, from media queries [image-set CSS/uri templates] Yes, from image-set() [Spacer background-image] Yes, from media queries [Request headers]

Output: Yes, but may be maintained by user agent


Input: [Evaluation] Adjusts to device bandwidth [Picture Element] Yes (if bandwidth added to media queries) [image-set CSS/uri templates] Yes (if bandwidth added to image-set) [Spacer background-image] Yes (if bandwidth added to media queries) [Request headers]

Output: No


Input: [Evaluation] Fallback for browsers without support [Picture Element] Yes, img within noscript [image-set CSS/uri templates] (no structure to evaluate) [Spacer background-image] Yes [Request headers]

Output: Yes


Input: [Evaluation] Printable images [Picture Element] Yes [image-set CSS/uri templates] Yes [Spacer background-image] No [Request headers]

Output: Yes


Input: [Evaluation] Polyfill [Picture Element] Yes [image-set CSS/uri templates] Yes [Spacer background-image] Not needed [Request headers]

Output: Not needed


Input: [Evaluation] Minimal structure updates for browser support [Picture Element] Create a new picture element [image-set CSS/uri templates] (no structure to evaluate) [Spacer background-image] Not needed [Request headers]

Output: Heavy restructuring


Input: [Evaluation] Minimal presentation updates for browser support [Picture Element] No new CSS required [image-set CSS/uri templates] image-set being evaluated by webkit for background images [Spacer background-image] Not needed [Request headers]

Output: No new CSS required


Input: [Evaluation] Image within content [Picture Element] Yes [image-set CSS/uri templates] Yes [Spacer background-image] No [Request headers]

Output: Yes


Input: [Evaluation] No new file formats [Picture Element] Works with existing files [image-set CSS/uri templates] Works with existing files [Spacer background-image] Works with existing files [Request headers]

Output: Works with existing files


Input: [Description] A single character, as per section 2.2 of [ XML ]. [Data type]

Output: Character


Input: [Description] A comma-separated list of 'charset's with optional q parameters, as defined in section 14.2 of [ RFC2616 ] as the field value of the Accept-Charset request header. [Data type]

Output: Encodings


Input: [Description] Attributes of this type identify the allowable content type(s) of an associated URI (usually a value of another attribute on the same element). At its most general, it is a comma-separated list of media ranges with optional accept parameters, as defined in section 14.1 of [ RFC2616 ] as the field value of the accept request header. In its simplest case, this is just a media type, such as "image/png" or "application/xml", but it may also contain asterisks, such as "image/*" or "*/*", or lists of acceptable media types, such as "image/png, image/gif, image/jpeg". The user agent must combine this list with its own list of acceptable media types by taking the intersection, and then use the resulting list as the field value of the accept request header when requesting the resource using HTTP. For instance, if the attribute specifies the value "image/png, image/gif, image/jpeg", but the user agent does not accept images of type "image/gif" then the resultant accept header would contain "image/png, image/jpeg". A user agent must imitate similar behavior when using other methods than HTTP. For instance, when accessing files in a local filestore, might cause the user agent first to look for a file logo.png ,and then for logo.jpg . If a value for the content type is not given, "*/*" must be used for its value. For the current list of registered content types, please consult [ MIMETYPES ]. [Data type]

Output: ContentTypes


Input: [Description] Comma separated list of Length s used in defining areas. [Data type]

Output: Coordinates


Input: [Description] Date and time information, as defined by the type dateTime in [ XMLSCHEMA ] except that the timezone part is required. [Data type]

Output: Datetime


Input: [Description] Name used as destination for results of certain actions, with legal values as defined by NMTOKEN . [Data type]

Output: HrefTarget


Input: [Description] A language code. The values should conform to [ RFC3066 ] or its successors. [Data type]

Output: LanguageCode


Input: [Description] A comma-separated list of language ranges with optional q parameters, as defined in section 14.4 of [ RFC2616 ] as the field value of the Accept-Language request header. Individual language codes should conform to [ RFC3066 ] or its successors. [Data type]

Output: LanguageCodes


Input: [Description] Either a number, representing a number of pixels, or a percentage, representing a percentage of the available horizontal or vertical space. Thus, the value "50%" means half of the available space. [Data type]

Output: Length


Input: [Description] A location path as defined in [ XPATH ]. [Data type]

Output: LocationPath


Input: [Description] A comma-separated list of media descriptors as described by [ CSS2 ]. The default is all . [Data type]

Output: MediaDesc


Input: [Description] One or more digits [Data type]

Output: Number


Input: [Description] An [ XMLNS ]-qualified name. See QName for a formal definition. [Data type]

Output: QName


Input: [Description] A character string. [Data type]

Output: Text


Input: [Description] An Internationalized Resource Identifier Reference, as defined by [ IRI ]. [Data type]

Output: URI


Input: [Description] A space-separated list of URIs as defined above. [Data type]

Output: URIs


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: [Attribute Type] CDATA [Definition]

Output: Character data

XHTML™ Modularization 1.1 - Second Edition


Input: [Attribute Type] ID [Definition]

Output: A document-unique identifier

XHTML™ Modularization 1.1 - Second Edition


Input: [Attribute Type] IDREF [Definition]

Output: A reference to a document-unique identifier

XHTML™ Modularization 1.1 - Second Edition


Input: [Attribute Type] IDREFS [Definition]

Output: A space-separated list of references to document-unique identifiers

XHTML™ Modularization 1.1 - Second Edition


Input: [Attribute Type] NAME [Definition]

Output: A name with the same character constraints as ID above

XHTML™ Modularization 1.1 - Second Edition


Input: [Attribute Type] NMTOKEN [Definition]

Output: A name composed of only name tokens as defined in XML 1.0 [XML]

XHTML™ Modularization 1.1 - Second Edition


Input: [Attribute Type] NMTOKENS [Definition]

Output: One or more white space separated NMTOKEN values

XHTML™ Modularization 1.1 - Second Edition


Input: [attribute] archive [function]

Output: For example, when defining an applet you could reference a space-separated list of jar files.


Input: [attribute] content-length [function]

Output: This is similar to meta data, in that this can be used by the object handler as a hint to the physical size of the object data that is to be processed.


Input: [attribute] data [function]

Output: This URI points to the object data to be processed. This can be an absolute URI (http://www.example.com/datafiles/myinstance.mpg), or a relative URI (myinstance.mpg). If you use a relative URI, then you will need to use the xml:base attribute to define the base location of the object data. This attribute should only refer to the data to be processed.


Input: [attribute] declare [function]

Output: This is used to delay the processing of the object data until such time that it is referred to by another element that requires the object data to be processed. In other words, the object data should be downloaded but should not be processed. For example, if an a element is coded to refer to the object element and the a element is activated, then the object data would be processed.


Input: [attribute] type [function]

Output: Defining the mime type of the object data will assist the object handler in determining whether the object data can be processed by the user agent or if an external application needs to be launched to process the object data.


Input: [attribute] xml:base [function]

Output: Use this attribute to define the base location of the object data. For example: http://www.example.com/datafiles/. This attribute should not be used for any other purpose.


Input: [LiveCycle Placement Rules] Default placement for the label is to the left of the control. If this is not possible, LiveCycle will attempt to place it immediately above the control. [Control Type]

Output: Text input (including date/time and password fields)

Text input (including date/time and password fields)

PDF Techniques | Techniques for WCAG 2.0


Input: [LiveCycle Placement Rules] Default placement for the label is to the right of the check box. [Control Type]

Output: Checkbox

Text input (including date/time and password fields)

PDF Techniques | Techniques for WCAG 2.0


Input: [LiveCycle Placement Rules] Default placement for the label for each individual radio button is to the right of the button. Create a visible caption for the radio button group by creating static text and placing it to the left of or above the group. (See Labeling radio buttons below.) [Control Type]

Output: Radio button group

Text input (including date/time and password fields)

PDF Techniques | Techniques for WCAG 2.0


Input: [LiveCycle Placement Rules] Default placement for the label is to the left of the drop-down list. If this is not possible, LiveCycle will attempt to place it immediately above the control.. [Control Type]

Output: Combo box

Text input (including date/time and password fields)

PDF Techniques | Techniques for WCAG 2.0


Input: [LiveCycle Placement Rules] Default placement for the label is above the list box. [Control Type]

Output: List box

Text input (including date/time and password fields)

PDF Techniques | Techniques for WCAG 2.0


Input: [LiveCycle Placement Rules] LiveCycle automatically places the label on the button; it does not have to be positioned manually. Ensure that the button's purpose is properly described in the label text. [Control Type]

Output: Button

Text input (including date/time and password fields)

PDF Techniques | Techniques for WCAG 2.0


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

Output: DISTINCT


Input: [Patterns] Property path expression [Query Forms] CONSTRUCT [Other] SERVICE [Modifiers]

Output: REDUCED


Input: [Patterns] Property path patterns [Query Forms] DESCRIBE [Modifiers]

Output: Projection


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: Select expressions


Input: [Event name] loadstart [Dispatched when...]

Output: The user agent begins looking for media data, as part of the resource selection algorithm.


Input: [Event name] progress [Dispatched when...]

Output: The user agent is fetching media data.


Input: [Event name] suspend [Dispatched when...]

Output: The user agent is intentionally not currently fetching media data, but does not have the entire media resource downloaded.


Input: [Event name] abort [Dispatched when...]

Output: The user agent stops fetching the media data before it is completely downloaded, but not due to an error.


Input: [Event name] error [Dispatched when...]

Output: An error occurs while fetching the media data.


Input: [Event name] emptied [Dispatched when...]

Output: A media element whose networkState was previously not in the NETWORK_EMPTY state has just switched to that state (either because of a fatal error during load that's about to be reported, or because the load() method was invoked while the resource selection algorithm was already running).


Input: [Event name] stalled [Dispatched when...]

Output: The user agent is trying to fetch media data, but data is unexpectedly not forthcoming.


Input: [Event name] play [Dispatched when...]

Output: Playback has begun. Fired after the play() method has returned, or when the autoplay attribute has caused playback to begin.


Input: [Event name] pause [Dispatched when...]

Output: Playback has been paused. Fired after the pause() method has returned.


Input: [Event name] loadedmetadata [Dispatched when...]

Output: The user agent has just determined the duration and dimensions of the media resource


Input: [Event name] loadeddata [Dispatched when...]

Output: The user agent can render the media data at the current playback position for the first time.


Input: [Event name] waiting [Dispatched when...]

Output: Playback has stopped because the next frame is not available, but the user agent expects that frame to become available in due course.


Input: [Event name] playing [Dispatched when...]

Output: Playback has started.


Input: [Event name] canplay [Dispatched when...]

Output: The user agent can resume playback of the media data, but estimates that if playback were to be started now, the media resource could not be rendered at the current playback rate up to its end without having to stop for further buffering of content.


Input: [Event name] canplaythrough [Dispatched when...]

Output: The user agent estimates that if playback were to be started now, the media resource could be rendered at the current playback rate all the way to its end without having to stop for further buffering.


Input: [Event name] seeking [Dispatched when...]

Output: The seeking IDL attribute changed to true and the seek operation is taking long enough that the user agent has time to fire the event.


Input: [Event name] seeked [Dispatched when...]

Output: The seeking IDL attribute changed to false.


Input: [Event name] timeupdate [Dispatched when...]

Output: The current playback position changed as part of normal playback or in an especially interesting way, for example discontinuously.


Input: [Event name] ended [Dispatched when...]

Output: Playback has stopped because the end of the media resource was reached.


Input: [Event name] ratechange [Dispatched when...]

Output: Either the defaultPlaybackRate or the playbackRate attribute has just been updated.


Input: [Event name] durationchange [Dispatched when...]

Output: The duration attribute has just been updated.


Input: [Event name] volumechange [Dispatched when...]

Output: Either the volume attribute or the muted attribute has changed. Fired after the relevant attribute's setter has returned.


Input: [Name] InvalidStateError [Description]

Output: The call state is invalid, or the an attempted operation conflicts with the call state in the implementation of the telephony modem and middleware


Input: [Name] InvalidModificationError [Description]

Output: The attempted operation conflicts with the call state or other constraints in the implementation, for instance attempting to disconnect a held call in a GSM network.


Input: [Name] NetworkError [Description]

Output: There was a telephony network error during the operation


Input: [Name] TimeoutError [Description]

Output: The attempted operation timed out


Input: [Name] NotSupportedError [Description]

Output: The attempted operation is not supported by the implementation, or the telephony network. This includes cases when a needed network feature (such as a supplementary service like Call Transfer) is not enabled.


Input: [Name] SecurityError [Description]

Output: The attempted operation is not permitted.


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 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] Sequence of one or more digits ([0-9]) [Attribute Type]

Output: NUMBER


Input: [Feature] Level of abstraction [Webinos proposal] Javascript API to obtain Javascript-based Service APIs [Opera/CableLabs proposal] Javascript API to obtain HTTP Service URL endpoints [Google Web Intents] Javascript API to allow client web application to find and communicate with service web application [Google Web Introducer]

Output: Javascript API to allow client web application to find and communicate with service web application

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Relation to underlying low level discovery/communication mechanisms [Webinos proposal] Agnostic to underlying low levels discovery/communication mechanisms. This is subject for implementation of discovery infrastructure and services based on supported low level discovery and communication mechanisms [Opera/CableLabs proposal] Agnostic to underlying low levels discovery/communication mechanisms (but includes standard processing rules for Zeroconf and UPnP). [Google Web Intents] None [Google Web Introducer]

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Location of services [Webinos proposal] In device, locally connected, local network and web-based services [Opera/CableLabs proposal] In device, locally connected, local network and web-based services [Google Web Intents] Anywhere, service is represented by a web application that hides any underlying low level service access methods [Google Web Introducer]

Output: Anywhere, service is represented by a web application that hides any underlying low level service access methods

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Network infrastructure required [Webinos proposal] Underlying infrastructure for registering user’s devices/services (more details) [Opera/CableLabs proposal] Both an underlying Zeroconf and UPnP infrastructure [Google Web Intents] None (Claes: Rich, I believe a “Web Intents server”is needed. Please explain your view [Google Web Introducer]

Output: “Web Introducer server”

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Identification of service type [Webinos proposal] URI identifying a JavaScript API to access the service [Opera/CableLabs proposal] Service type tokens exposed from the underlying discovery mechanisms [Google Web Intents] A service (intent) is defined by: Action: a URI defining what to do (share, pick, view, etc) Type: the data type to perform the action on (image, url, json etc) [Google Web Introducer]

Output: A service (intent) is a string identifying an interaction pattern between a Client and a Service. Examples are bookmark for sharing, link to media file, user's stream of incoming SMSs

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Security / access control [Webinos proposal] Based on user selection of discovered service and security mechanisms implemented for respective services. A distributed approach where policy decisions are hosted in a Personal Zone. [Opera/CableLabs proposal] Based on user selection of discovered service and security mechanisms implemented for respective services. Assumes that access control is handled in the UA. [Google Web Intents] Based on user selection of discovered service and security mechanisms implemented for respective services [Google Web Introducer]

Output: Based on user selection of discovered service and security mechanisms implemented for respective services

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Service registration [Webinos proposal] An application can register new services through a statement in the manifest file [Opera/CableLabs proposal] UA silently (i.e. in the background) handles discovery and registration of services from the local device, local network. UA also silently handles service discovery and registration on visited web sites. [Google Web Intents] To make a service (intent) discoverable it need to be registered in the UA through a simple API. The services Action, Type and URL to a web page that implements the service is registered. For example, in-page meta header registration syntax is collected as the user browses their web sites. [Google Web Introducer]

Output: To make a service (intent) discoverable it need to be registered in the UA through a simple API. The service's name, supported intent strings, icons, URLs to service pages are registered.

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Discovery process [Webinos proposal] UA searches for networked services at API invocation.A successCallback is issued for each service found. Timer for how long search process lasts could be set. Pending search process can be canceled [Opera/CableLabs proposal] UA searches for networked services (the timing of which is at the discretion of the UA) in the local network and on user visited web sites and maintains a list of currently available services. [Google Web Intents] A web application wanting to use a service calls a simple API stating the requested Action and Type. An iframe allows the user to select one of the registered services for this Action and Type. [Google Web Introducer]

Output: A web application wanting to use a service calls a simple API stating the requested intent. An iframe or a new window allows the user to select one of the registered services for this intent.

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Search filter [Webinos proposal] Yes. Allows web application to search for services belonging to certain user(s), to state remote or local only services and to state location of service. Also allows the page to set a timer for how long search process lasts could be set. Pending search processes can be canceled. [Opera/CableLabs proposal] No [1]. [Google Web Intents] No. [Google Web Introducer]

Output: No.

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Communication with service [Webinos proposal] A standardized / “well-known” JavaScript API is provided to the web application to access the service. [Opera/CableLabs proposal] A URL, extracted directly from the underlying service discovery process, is provided to the web application to access the service. The web page can then use standard XmlHttpRequest, Web Sockets, Server-Sent Events and Web Messaging, etc (all with implicit cross-origin resource sharing) to communcate with the service. Protocol depends on messaging format implemented in device implementing service (e.g. json, protobufs, text-based, xml, etc). [Google Web Intents] Data is sent bi-directionally between client web application page and the service web page through the Web Intents API. The format/protocol of this data exchange is defined for each Action by the Web Intents specification. Underlying communication mechanism is web messaging but this level is hided to the application developer. [Google Web Introducer]

Output: Data is sent bi-directionally between client web application page and the service web page through Web Messaging. The format/protocol of this data exchange must be defined for each Intent by specific API/protocol specifications for each intent type.

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Service status monitoring [Webinos proposal] onLost callback when found but not yet bound service is lost. onServiceUnavaialble and onServiceAvailable callbacks for bound services. [Opera/CableLabs proposal] readyState changes fire back to web page's network service objects. readystatechange events occur on a network service object when the service becomes available or unavailable. servicesAvailable attribute is used to monitor general number of services of the authorized type currently available in the user's network(s). [Google Web Intents] No service status monitoring in the Web Intents API itself but guess that this could be handled in the specific protocol for the specific Action. [Google Web Introducer]

Output: No service status monitoring in the Web Introducer API itself but guess that this could be handled in the specific protocol for the specific intent type.

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Service binding lifecycle [Webinos proposal] Service binding valid until unbind() is called or client page is left. Later the binding to the service can be resumed using the saved service id. [Opera/CableLabs proposal] Opera to elaborate [Google Web Intents] To be completed [Google Web Introducer]

Output: To be completed

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] .... [Webinos proposal] ... [Opera/CableLabs proposal] ... [Google Web Intents] .... [Google Web Introducer]

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Evaluation] Bandwidth efficiency [Picture Element] Yes, requests only what it needs [Spacer background-image] Yes, requests only what it needs [Request headers] Yes, requests only what it needs [image-set CSS/uri templates]

Output: Yes, requests only what it needs


Input: [Evaluation] Single HTTP request [Picture Element] Yes [Spacer background-image] Yes [Request headers] Yes [image-set CSS/uri templates]

Output: Yes


Input: [Evaluation] Server-side config not required [Picture Element] Client based [Spacer background-image] Client based [Request headers] Server-config required [image-set CSS/uri templates]

Output: Client based


Input: [Evaluation] Structure Simplicity (HTML) [Picture Element] Difficult for beginners [Spacer background-image] Existing elements [Request headers] No changes [image-set CSS/uri templates]

Output: (structure not decided, only focuses on CSS)


Input: [Evaluation] Presentation Simplicity (CSS) [Picture Element] Yes [Spacer background-image] Heavy use of media queries [Request headers] No changes [image-set CSS/uri templates]

Output: Difficult for beginners, but consistent image-set for backgrounds


Input: [Evaluation] Easy of maintenance [Picture Element] Responsive scenarios within structure [Spacer background-image] Control image variants with CSS [Request headers] Server-side config [image-set CSS/uri templates]

Output: Control image variants with CSS


Input: [Evaluation] Separation of concerns [Picture Element] Presentation scenarios within structure [Spacer background-image] Control image variants with CSS [Request headers] Depends on implementation [image-set CSS/uri templates]

Output: Control image variants with CSS


Input: [Evaluation] Declarative? (e.g provides semantic hooks for sizes) [Picture Element] Yes [Spacer background-image] No [Request headers] No [image-set CSS/uri templates]

Output: This is only CSS, so it allows the markup to be declarative too. Additionally, it provides the browser with request formats and presentation scenarios which can be reused sitewide.


Input: [Evaluation] Centralized image variants [Picture Element] Located within structure [Spacer background-image] Variants within media queries [Request headers] Depends on implementation [image-set CSS/uri templates]

Output: Variants formats within image-set() urls


Input: [Evaluation] Request static images [Picture Element] Yes [Spacer background-image] Yes [Request headers] Yes [image-set CSS/uri templates]

Output: Yes


Input: [Evaluation] Request dynamically resized images [Picture Element] Manually code dimensions within urls [Spacer background-image] Manually code dimensions within urls [Request headers] Yes [image-set CSS/uri templates]

Output: Request exact dimension needed


Input: [Evaluation] High-resolution when the device is capable [Picture Element] Yes, from media queries [Spacer background-image] Yes, from media queries [Request headers] Yes, but may be maintained by user agent [image-set CSS/uri templates]

Output: Yes, from image-set()


Input: [Evaluation] Adjusts to device bandwidth [Picture Element] Yes (if bandwidth added to media queries) [Spacer background-image] Yes (if bandwidth added to media queries) [Request headers] No [image-set CSS/uri templates]

Output: Yes (if bandwidth added to image-set)


Input: [Evaluation] Fallback for browsers without support [Picture Element] Yes, img within noscript [Spacer background-image] Yes [Request headers] Yes [image-set CSS/uri templates]

Output: (no structure to evaluate)


Input: [Evaluation] Printable images [Picture Element] Yes [Spacer background-image] No [Request headers] Yes [image-set CSS/uri templates]

Output: Yes


Input: [Evaluation] Polyfill [Picture Element] Yes [Spacer background-image] Not needed [Request headers] Not needed [image-set CSS/uri templates]

Output: Yes


Input: [Evaluation] Minimal structure updates for browser support [Picture Element] Create a new picture element [Spacer background-image] Not needed [Request headers] Heavy restructuring [image-set CSS/uri templates]

Output: (no structure to evaluate)


Input: [Evaluation] Minimal presentation updates for browser support [Picture Element] No new CSS required [Spacer background-image] Not needed [Request headers] No new CSS required [image-set CSS/uri templates]

Output: image-set being evaluated by webkit for background images


Input: [Evaluation] Image within content [Picture Element] Yes [Spacer background-image] No [Request headers] Yes [image-set CSS/uri templates]

Output: Yes


Input: [Evaluation] No new file formats [Picture Element] Works with existing files [Spacer background-image] Works with existing files [Request headers] Works with existing files [image-set CSS/uri templates]

Output: Works with existing files


Input: [Status] Proposal [Summary] To promote the 'citation' property currently on MedicalScholarlyArticle up to CreativeWork. [Vocab] Moves citation up to CreativeWork [Topic]

Output: Citation Promotion

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


Input: [Status] Proposal [Summary] Extension for describing accessibility properties of a CreativeWork. [Comments] Draft published to elicit feedback. [Topic]

Output: Accessibility

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


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

Output: Add Organization department property

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


Input: [Status] Proposal [Summary] Property to indicate that a single identity is being described. [Vocab] Essentially same meaning as owl:sameAs, but suggesting a distinct name to make it easier to talk about; also schema.org data is typically scruffier than OWL re http-range-14. [Comments] Draft published to elicit feedback. [Topic]

Output: sameThingAs

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


Input: [Status] Proposal [Summary] A proposal for a new Action type. [Vocab] See full entry and proposal for details. May2013 version builds on two previously published designs. [Comments] The schema.org team solicit comments on this draft via public-vocabs@w3.org. [Topic]

Output: Actions in Schema.org

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


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

Output: Orders in Schema.org

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


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

Output: Reservations in Schema.org

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


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

Output: EmailMessage type

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


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

Output: Workers Union type

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


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

Output: TV and Radio proposal

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


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

Output: Sports

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


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

Output: Comics and Serials

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


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

Output: Event schema update

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


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

Output: Historical Data proposal

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


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

Output: Biological Databases

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


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

Output: Breadcrumbs

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


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

Output: Discussion

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


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

Output: Innovation

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


Input: [Topic]

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


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

Output: Proposal name

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


Input: [Attribute Type] CDATA [Definition]

Output: Character data


Input: [Attribute Type] ID [Definition]

Output: A document-unique identifier


Input: [Attribute Type] IDREF [Definition]

Output: A reference to a document-unique identifier


Input: [Attribute Type] IDREFS [Definition]

Output: A space-separated list of references to document-unique identifiers


Input: [Attribute Type] NAME [Definition]

Output: A name with the same character constraints as ID above


Input: [Attribute Type] NMTOKEN [Definition]

Output: A name composed of only name tokens as defined in XML 1.0 [ XML ].


Input: [Attribute Type] NMTOKENS [Definition]

Output: One or more white space separated NMTOKEN values


Input: [Attribute Type] PCDATA [Definition]

Output: Processed character data


Input: [Evaluation] Bandwidth efficiency [image-set CSS/uri templates] Yes, requests only what it needs [Spacer background-image] Yes, requests only what it needs [Request headers] Yes, requests only what it needs [Picture Element]

Output: Yes, requests only what it needs


Input: [Evaluation] Single HTTP request [image-set CSS/uri templates] Yes [Spacer background-image] Yes [Request headers] Yes [Picture Element]

Output: Yes


Input: [Evaluation] Server-side config not required [image-set CSS/uri templates] Client based [Spacer background-image] Client based [Request headers] Server-config required [Picture Element]

Output: Client based


Input: [Evaluation] Structure Simplicity (HTML) [image-set CSS/uri templates] (structure not decided, only focuses on CSS) [Spacer background-image] Existing elements [Request headers] No changes [Picture Element]

Output: Difficult for beginners


Input: [Evaluation] Presentation Simplicity (CSS) [image-set CSS/uri templates] Difficult for beginners, but consistent image-set for backgrounds [Spacer background-image] Heavy use of media queries [Request headers] No changes [Picture Element]

Output: Yes


Input: [Evaluation] Easy of maintenance [image-set CSS/uri templates] Control image variants with CSS [Spacer background-image] Control image variants with CSS [Request headers] Server-side config [Picture Element]

Output: Responsive scenarios within structure


Input: [Evaluation] Separation of concerns [image-set CSS/uri templates] Control image variants with CSS [Spacer background-image] Control image variants with CSS [Request headers] Depends on implementation [Picture Element]

Output: Presentation scenarios within structure


Input: [Evaluation] Declarative? (e.g provides semantic hooks for sizes) [image-set CSS/uri templates] This is only CSS, so it allows the markup to be declarative too. Additionally, it provides the browser with request formats and presentation scenarios which can be reused sitewide. [Spacer background-image] No [Request headers] No [Picture Element]

Output: Yes


Input: [Evaluation] Centralized image variants [image-set CSS/uri templates] Variants formats within image-set() urls [Spacer background-image] Variants within media queries [Request headers] Depends on implementation [Picture Element]

Output: Located within structure


Input: [Evaluation] Request static images [image-set CSS/uri templates] Yes [Spacer background-image] Yes [Request headers] Yes [Picture Element]

Output: Yes


Input: [Evaluation] Request dynamically resized images [image-set CSS/uri templates] Request exact dimension needed [Spacer background-image] Manually code dimensions within urls [Request headers] Yes [Picture Element]

Output: Manually code dimensions within urls


Input: [Evaluation] High-resolution when the device is capable [image-set CSS/uri templates] Yes, from image-set() [Spacer background-image] Yes, from media queries [Request headers] Yes, but may be maintained by user agent [Picture Element]

Output: Yes, from media queries


Input: [Evaluation] Adjusts to device bandwidth [image-set CSS/uri templates] Yes (if bandwidth added to image-set) [Spacer background-image] Yes (if bandwidth added to media queries) [Request headers] No [Picture Element]

Output: Yes (if bandwidth added to media queries)


Input: [Evaluation] Fallback for browsers without support [image-set CSS/uri templates] (no structure to evaluate) [Spacer background-image] Yes [Request headers] Yes [Picture Element]

Output: Yes, img within noscript


Input: [Evaluation] Printable images [image-set CSS/uri templates] Yes [Spacer background-image] No [Request headers] Yes [Picture Element]

Output: Yes


Input: [Evaluation] Polyfill [image-set CSS/uri templates] Yes [Spacer background-image] Not needed [Request headers] Not needed [Picture Element]

Output: Yes


Input: [Evaluation] Minimal structure updates for browser support [image-set CSS/uri templates] (no structure to evaluate) [Spacer background-image] Not needed [Request headers] Heavy restructuring [Picture Element]

Output: Create a new picture element


Input: [Evaluation] Minimal presentation updates for browser support [image-set CSS/uri templates] image-set being evaluated by webkit for background images [Spacer background-image] Not needed [Request headers] No new CSS required [Picture Element]

Output: No new CSS required


Input: [Evaluation] Image within content [image-set CSS/uri templates] Yes [Spacer background-image] No [Request headers] Yes [Picture Element]

Output: Yes


Input: [Evaluation] No new file formats [image-set CSS/uri templates] Works with existing files [Spacer background-image] Works with existing files [Request headers] Works with existing files [Picture Element]

Output: Works with existing files


Input: [Scenario] When an accessibility subtree is hidden [MSAA] EVENT_OBJECT_HIDE The MSAA event called EVENT_OBJECT_DESTROY is not used because this has a history of stability issues and assistive technology avoids it. In any case, from the user's point of view, there is no difference between something that is hidden or destroyed. [Mac OS X Notification] AXUIElementDestroyed If in a live region, AXLiveRegionChanged [ATK/AT-SPI event]

Output: children_changed::remove

WAI-ARIA 1.0 User Agent Implementation Guide


Input: [Scenario] When an accessibility subtree is removed [MSAA] EVENT_OBJECT_REORDER The MSAA event called EVENT_OBJECT_DESTROY is not used because this has a history of stability issues and assistive technology avoids it. In any case, from the user's point of view, there is no difference between something that is hidden or destroyed. [Mac OS X Notification] AXUIElementDestroyed If in a live region, AXLiveRegionChanged [ATK/AT-SPI event]

Output: children_changed::remove

WAI-ARIA 1.0 User Agent Implementation Guide


Input: [Scenario] When an accessibility subtree is shown [MSAA] EVENT_OBJECT_SHOW [Mac OS X Notification] AXUIElementCreated If in a live region, AXLiveRegionChanged [ATK/AT-SPI event]

Output: children_changed::add

WAI-ARIA 1.0 User Agent Implementation Guide


Input: [Scenario] When an accessibility subtree is inserted [MSAA] EVENT_OBJECT_REORDER [Mac OS X Notification] AXUIElementCreated If in a live region, AXLiveRegionChanged [ATK/AT-SPI event]

Output: children_changed::add

WAI-ARIA 1.0 User Agent Implementation Guide


Input: [Scenario] When an accessibility subtree is moved [MSAA] Treat it as a removal from one place and insertion in another [Mac OS X Notification] AXUIElementDestroyed/ AXUIElementCreated If in a live region, AXLiveRegionChanged [ATK/AT-SPI event]

Output: Treat it as a removal from one place and insertion in another

WAI-ARIA 1.0 User Agent Implementation Guide


Input: [Scenario] When an accessibility subtree is changed (e.g. replaceNode) [MSAA] Treat it as a removal and insertion [Mac OS X Notification] AXUIElementDestroyed/ AXUIElementCreated If in a live region, AXLiveRegionChanged [ATK/AT-SPI event]

Output: Treat it as a removal and insertion

WAI-ARIA 1.0 User Agent Implementation Guide


Input: [0] Row 1 [Row] Pending [Column B] Pending [Column C] Pending [Column A]

Output: Pending


Input: [0] Row 2 [Row] Yes [Column B] Yes [Column C] Pending [Column A]

Output: Yes


Input: [0] Row 3 [Row] Yes [Column B] Yes [Column C] Pending [Column A]

Output: Yes


Input: [0] Row 4 [Row] Yes [Column B] Yes [Column C] Pending [Column A]

Output: Yes


Input: [0] Row 5 [Row] Pending [Column B] Pending [Column C] Pending [Column A]

Output: Pending


Input: [0] Row 6 [Row] Pending [Column B] Pending [Column C] Pending [Column A]

Output: Pending


Input: [0] Row 7 [Row] Yes [Column B] Pending [Column C] Pending [Column A]

Output: Pending


Input: [0] Row 8 [Row] Yes [Column B] Pending [Column C] Pending [Column A]

Output: Pending


Input: [WSC Clause] I [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] II [Chrome] Conforms Advanced [Firefox] Conforms Advanced [Opera]

Output: Conforms Advanced


Input: [WSC Clause] IIa [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] IV [Chrome] NA [Firefox] NA [Opera]


Input: [WSC Clause] V [Chrome] Does Not Conform Optional [Firefox] Does Not Conform Optional [Opera]

Output: Conforms Optional


Input: [WSC Clause] VI [Chrome] Conforms Advanced [Firefox] Conforms Advanced [Opera]

Output: Conforms Advanced


Input: [WSC Clause] VII [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] VIII [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] IX [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] X [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XI [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XII [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XIII [Chrome] Does Not Conform Optional [Firefox] Conforms Optional [Opera]

Output: Conforms Optional


Input: [WSC Clause] XIV [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XV [Chrome] Conforms Optional [Firefox] Conforms Optional [Opera]

Output: Conforms Optional


Input: [WSC Clause] XVI [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XVII [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XVIII [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XIX [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XX [Chrome] Conforms Optional [Firefox] Conforms Optional [Opera]

Output: Conforms Optional


Input: [WSC Clause] XXI [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XXII [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XXIII [Chrome] NA [Firefox] NA [Opera]


Input: [WSC Clause] XXIV [Chrome] Does Not Conform Optional [Firefox] Conforms Optional [Opera]

Output: Conforms Optional


Input: [WSC Clause] XXV [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XXVI [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XXVII [Chrome] NA [Firefox] NA [Opera]


Input: [WSC Clause] XXVIII [Chrome] NA [Firefox] NA [Opera]


Input: [WSC Clause] XXIX [Chrome] NA [Firefox] NA [Opera]


Input: [WSC Clause] XXX [Chrome] NA [Firefox] NA [Opera]


Input: [WSC Clause] XXXI [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XXXII [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XXXIII [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XXXIV [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XXXV [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XXXVI [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XXXVII [Chrome] Conforms Optional [Firefox] Conforms Optional [Opera]

Output: Conforms Optional


Input: [WSC Clause] XXXVIII [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XXXIX [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XL [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XLI [Chrome] Conforms Optional [Firefox] Conforms Optional [Opera]

Output: Conforms Optional


Input: [WSC Clause] XLII [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XLIII [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XLIV [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XLV [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XLVI [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XLVII [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XLVIII [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XLIX [Chrome] Conforms Advanced [Firefox] Conforms Advanced [Opera]

Output: Conforms Advanced


Input: [WSC Clause] L [Chrome] Conforms Advanced [Firefox] Conforms Advanced [Opera]

Output: Conforms Advanced


Input: [WSC Clause] LI [Chrome] Conforms Advanced [Firefox] Conforms Advanced [Opera]

Output: Does Not Conform Advanced


Input: [WSC Clause] LII [Chrome] Does Not Conform Advanced [Firefox] Conforms Advanced [Opera]

Output: Does Not Conform Advanced


Input: [WSC Clause] LIII [Chrome] Conforms Advanced [Firefox] Conforms Advanced [Opera]

Output: Conforms Advanced


Input: [WSC Clause] LIV [Chrome] Conforms Advanced [Firefox] Conforms Advanced [Opera]

Output: Conforms Advanced


Input: [WSC Clause] LV [Chrome] NA [Firefox] NA [Opera]


Input: [WSC Clause] LVI [Chrome] Conforms Optional [Firefox] Does Not Conform Optional [Opera]

Output: Does Not Conform Optional


Input: [WSC Clause] LVII [Chrome] Does Not Conform Optional [Firefox] Conforms Optional [Opera]

Output: Does Not Conform Optional


Input: [WSC Clause] LVIII [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] LIX [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] LX [Chrome] Conforms Advanced [Firefox] Conforms Advanced [Opera]

Output: Conforms Advanced


Input: [WSC Clause] LXI [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] LXII [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] LXIII [Chrome] NA [Firefox] NA [Opera]


Input: [WSC Clause] LXIV [Chrome] NA [Firefox] NA [Opera]


Input: [WSC Clause] LXV [Chrome] Conforms Advanced [Firefox] Conforms Advanced [Opera]

Output: Conforms Advanced


Input: [WSC Clause] LXVI [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] LXVII [Chrome] Conforms Advanced [Firefox] Conforms Advanced [Opera]

Output: Conforms Advanced


Input: [WSC Clause] LXVIII [Chrome] Conforms Optional [Firefox] Conforms Optional [Opera]

Output: Conforms Optional


Input: [WSC Clause] LXIX [Chrome] Does Not Conform Optional [Firefox] Does Not Conform Optional [Opera]

Output: Conforms Optional


Input: [WSC Clause] LXX [Chrome] Conforms Advanced [Firefox] Conforms Advanced [Opera]

Output: Conforms Advanced


Input: [WSC Clause] LXXI [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] LXXII [Chrome] Conforms Advanced [Firefox] Conforms Advanced [Opera]

Output: Conforms Advanced


Input: [WSC Clause] LXXIII [Chrome] Conforms Advanced [Firefox] Conforms Advanced [Opera]

Output: Conforms Advanced


Input: [WSC Clause] LXXIV [Chrome] Conforms Advanced [Firefox] Conforms Advanced [Opera]

Output: Conforms Advanced


Input: [WSC Clause] LXXV [Chrome] NA [Firefox] NA [Opera]


Input: [WSC Clause] LXXVI [Chrome] NA [Firefox] NA [Opera]


Input: [WSC Clause] LXXVII [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] LXXVIII [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] LXXIX [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] LXXX [Chrome] Conforms Advanced [Firefox] Conforms Advanced [Opera]

Output: Does Not Conform Advanced


Input: [WSC Clause] LXXXI [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] LXXXII [Chrome] NA [Firefox] NA [Opera]


Input: [WSC Clause] LXXXIII [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] LXXXIV [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] LXXXV [Chrome] Conforms Advanced [Firefox] Conforms Advanced [Opera]

Output: Conforms Advanced


Input: [WSC Clause] LXXXVI [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] LXXXVII [Chrome] Conforms Optional [Firefox] Conforms Optional [Opera]

Output: Conforms Optional


Input: [WSC Clause] LXXXVIII [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] LXXXIX [Chrome] Conforms Advanced [Firefox] Conforms Advanced [Opera]

Output: Conforms Advanced


Input: [WSC Clause] XC [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XCI [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XCII [Chrome] Conforms Advanced [Firefox] Conforms Advanced [Opera]

Output: Conforms Advanced


Input: [WSC Clause] XCIII [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XCIV [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XCV [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XCVI [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XCVII [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XCVIII [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] XCIX [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] C [Chrome] Conforms Advanced [Firefox] Conforms Advanced [Opera]

Output: Conforms Advanced


Input: [WSC Clause] CI [Chrome] NA [Firefox] NA [Opera]


Input: [WSC Clause] CII [Chrome] Conforms Advanced [Firefox] Conforms Advanced [Opera]

Output: Conforms Advanced


Input: [WSC Clause] CIII [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] CIV [Chrome] Conforms Basic [Firefox] Conforms Basic [Opera]

Output: Conforms Basic


Input: [WSC Clause] CV [Chrome] Conforms Advanced [Firefox] Conforms Advanced [Opera]

Output: Conforms Advanced


Input: [WSC Clause] CVI [Chrome] Conforms Advanced [Firefox] Conforms Advanced [Opera]

Output: Conforms Advanced


Input: [Feature] Level of abstraction [Webinos proposal] Javascript API to obtain Javascript-based Service APIs [Opera/CableLabs proposal] Javascript API to obtain HTTP Service URL endpoints [Google Web Introducer] Javascript API to allow client web application to find and communicate with service web application [Google Web Intents]

Output: Javascript API to allow client web application to find and communicate with service web application

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Relation to underlying low level discovery/communication mechanisms [Webinos proposal] Agnostic to underlying low levels discovery/communication mechanisms. This is subject for implementation of discovery infrastructure and services based on supported low level discovery and communication mechanisms [Opera/CableLabs proposal] Agnostic to underlying low levels discovery/communication mechanisms (but includes standard processing rules for Zeroconf and UPnP). [Google Web Introducer] None [Google Web Intents]

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Location of services [Webinos proposal] In device, locally connected, local network and web-based services [Opera/CableLabs proposal] In device, locally connected, local network and web-based services [Google Web Introducer] Anywhere, service is represented by a web application that hides any underlying low level service access methods [Google Web Intents]

Output: Anywhere, service is represented by a web application that hides any underlying low level service access methods

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Network infrastructure required [Webinos proposal] Underlying infrastructure for registering user’s devices/services (more details) [Opera/CableLabs proposal] Both an underlying Zeroconf and UPnP infrastructure [Google Web Introducer] “Web Introducer server” [Google Web Intents]

Output: None (Claes: Rich, I believe a “Web Intents server”is needed. Please explain your view

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Identification of service type [Webinos proposal] URI identifying a JavaScript API to access the service [Opera/CableLabs proposal] Service type tokens exposed from the underlying discovery mechanisms [Google Web Introducer] A service (intent) is a string identifying an interaction pattern between a Client and a Service. Examples are bookmark for sharing, link to media file, user's stream of incoming SMSs [Google Web Intents]

Output: A service (intent) is defined by: Action: a URI defining what to do (share, pick, view, etc) Type: the data type to perform the action on (image, url, json etc)

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Security / access control [Webinos proposal] Based on user selection of discovered service and security mechanisms implemented for respective services. A distributed approach where policy decisions are hosted in a Personal Zone. [Opera/CableLabs proposal] Based on user selection of discovered service and security mechanisms implemented for respective services. Assumes that access control is handled in the UA. [Google Web Introducer] Based on user selection of discovered service and security mechanisms implemented for respective services [Google Web Intents]

Output: Based on user selection of discovered service and security mechanisms implemented for respective services

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Service registration [Webinos proposal] An application can register new services through a statement in the manifest file [Opera/CableLabs proposal] UA silently (i.e. in the background) handles discovery and registration of services from the local device, local network. UA also silently handles service discovery and registration on visited web sites. [Google Web Introducer] To make a service (intent) discoverable it need to be registered in the UA through a simple API. The service's name, supported intent strings, icons, URLs to service pages are registered. [Google Web Intents]

Output: To make a service (intent) discoverable it need to be registered in the UA through a simple API. The services Action, Type and URL to a web page that implements the service is registered. For example, in-page meta header registration syntax is collected as the user browses their web sites.

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Discovery process [Webinos proposal] UA searches for networked services at API invocation.A successCallback is issued for each service found. Timer for how long search process lasts could be set. Pending search process can be canceled [Opera/CableLabs proposal] UA searches for networked services (the timing of which is at the discretion of the UA) in the local network and on user visited web sites and maintains a list of currently available services. [Google Web Introducer] A web application wanting to use a service calls a simple API stating the requested intent. An iframe or a new window allows the user to select one of the registered services for this intent. [Google Web Intents]

Output: A web application wanting to use a service calls a simple API stating the requested Action and Type. An iframe allows the user to select one of the registered services for this Action and Type.

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Search filter [Webinos proposal] Yes. Allows web application to search for services belonging to certain user(s), to state remote or local only services and to state location of service. Also allows the page to set a timer for how long search process lasts could be set. Pending search processes can be canceled. [Opera/CableLabs proposal] No [1]. [Google Web Introducer] No. [Google Web Intents]

Output: No.

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Communication with service [Webinos proposal] A standardized / “well-known” JavaScript API is provided to the web application to access the service. [Opera/CableLabs proposal] A URL, extracted directly from the underlying service discovery process, is provided to the web application to access the service. The web page can then use standard XmlHttpRequest, Web Sockets, Server-Sent Events and Web Messaging, etc (all with implicit cross-origin resource sharing) to communcate with the service. Protocol depends on messaging format implemented in device implementing service (e.g. json, protobufs, text-based, xml, etc). [Google Web Introducer] Data is sent bi-directionally between client web application page and the service web page through Web Messaging. The format/protocol of this data exchange must be defined for each Intent by specific API/protocol specifications for each intent type. [Google Web Intents]

Output: Data is sent bi-directionally between client web application page and the service web page through the Web Intents API. The format/protocol of this data exchange is defined for each Action by the Web Intents specification. Underlying communication mechanism is web messaging but this level is hided to the application developer.

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Service status monitoring [Webinos proposal] onLost callback when found but not yet bound service is lost. onServiceUnavaialble and onServiceAvailable callbacks for bound services. [Opera/CableLabs proposal] readyState changes fire back to web page's network service objects. readystatechange events occur on a network service object when the service becomes available or unavailable. servicesAvailable attribute is used to monitor general number of services of the authorized type currently available in the user's network(s). [Google Web Introducer] No service status monitoring in the Web Introducer API itself but guess that this could be handled in the specific protocol for the specific intent type. [Google Web Intents]

Output: No service status monitoring in the Web Intents API itself but guess that this could be handled in the specific protocol for the specific Action.

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Service binding lifecycle [Webinos proposal] Service binding valid until unbind() is called or client page is left. Later the binding to the service can be resumed using the saved service id. [Opera/CableLabs proposal] Opera to elaborate [Google Web Introducer] To be completed [Google Web Intents]

Output: To be completed

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] .... [Webinos proposal] ... [Opera/CableLabs proposal] ... [Google Web Introducer] .... [Google Web Intents]

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Dispatched when...] The user agent begins looking for media data, as part of the resource selection algorithm. [Event name]

Output: loadstart


Input: [Dispatched when...] The user agent is fetching media data. [Event name]

Output: progress


Input: [Dispatched when...] The user agent is intentionally not currently fetching media data, but does not have the entire media resource downloaded. [Event name]

Output: suspend


Input: [Dispatched when...] The user agent stops fetching the media data before it is completely downloaded, but not due to an error. [Event name]

Output: abort


Input: [Dispatched when...] An error occurs while fetching the media data. [Event name]

Output: error


Input: [Dispatched when...] A media element whose networkState was previously not in the NETWORK_EMPTY state has just switched to that state (either because of a fatal error during load that's about to be reported, or because the load() method was invoked while the resource selection algorithm was already running). [Event name]

Output: emptied


Input: [Dispatched when...] The user agent is trying to fetch media data, but data is unexpectedly not forthcoming. [Event name]

Output: stalled


Input: [Dispatched when...] Playback has begun. Fired after the play() method has returned, or when the autoplay attribute has caused playback to begin. [Event name]

Output: play


Input: [Dispatched when...] Playback has been paused. Fired after the pause() method has returned. [Event name]

Output: pause


Input: [Dispatched when...] The user agent has just determined the duration and dimensions of the media resource [Event name]

Output: loadedmetadata


Input: [Dispatched when...] The user agent can render the media data at the current playback position for the first time. [Event name]

Output: loadeddata


Input: [Dispatched when...] Playback has stopped because the next frame is not available, but the user agent expects that frame to become available in due course. [Event name]

Output: waiting


Input: [Dispatched when...] Playback has started. [Event name]

Output: playing


Input: [Dispatched when...] The user agent can resume playback of the media data, but estimates that if playback were to be started now, the media resource could not be rendered at the current playback rate up to its end without having to stop for further buffering of content. [Event name]

Output: canplay


Input: [Dispatched when...] The user agent estimates that if playback were to be started now, the media resource could be rendered at the current playback rate all the way to its end without having to stop for further buffering. [Event name]

Output: canplaythrough


Input: [Dispatched when...] The seeking IDL attribute changed to true and the seek operation is taking long enough that the user agent has time to fire the event. [Event name]

Output: seeking


Input: [Dispatched when...] The seeking IDL attribute changed to false. [Event name]

Output: seeked


Input: [Dispatched when...] The current playback position changed as part of normal playback or in an especially interesting way, for example discontinuously. [Event name]

Output: timeupdate


Input: [Dispatched when...] Playback has stopped because the end of the media resource was reached. [Event name]

Output: ended


Input: [Dispatched when...] Either the defaultPlaybackRate or the playbackRate attribute has just been updated. [Event name]

Output: ratechange


Input: [Dispatched when...] The duration attribute has just been updated. [Event name]

Output: durationchange


Input: [Dispatched when...] Either the volume attribute or the muted attribute has changed. Fired after the relevant attribute's setter has returned. [Event name]

Output: volumechange


Input: [Target] Source node [Cancelable?] ✓ Cancelable [Drag data store mode] Read/write mode [dropEffect] "none" [Default Action] Initiate the drag-and-drop operation [Event Name]

Output: dragstart

7.6 Drag and drop — HTML5: Edition for Web Authors


Input: [Target] Source node [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [dropEffect] "none" [Default Action] Continue the drag-and-drop operation [Event Name]

Output: drag

7.6 Drag and drop — HTML5: Edition for Web Authors


Input: [Target] Immediate user selection or the body element [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [dropEffect] Based on effectAllowed value [Default Action] Reject immediate user selection as potential target element [Event Name]

Output: dragenter

7.6 Drag and drop — HTML5: Edition for Web Authors