Input: [type] keypress [Bubbling phase] Yes [Target node types] Element [DOM interface] KeyboardEvent [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [type] keyup [Bubbling phase] Yes [Target node types] Element [DOM interface] KeyboardEvent [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [type] load [Bubbling phase] No [Target node types] Document, Element [DOM interface] Event [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [type] mousedown [Bubbling phase] Yes [Target node types] Element [DOM interface] MouseEvent [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [type] mouseenter [Bubbling phase] No [Target node types] Element [DOM interface] MouseEvent [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [type] mouseleave [Bubbling phase] No [Target node types] Element [DOM interface] MouseEvent [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [type] mousemove [Bubbling phase] Yes [Target node types] Element [DOM interface] MouseEvent [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [type] mouseout [Bubbling phase] Yes [Target node types] Element [DOM interface] MouseEvent [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [type] mouseover [Bubbling phase] Yes [Target node types] Element [DOM interface] MouseEvent [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [type] mouseup [Bubbling phase] Yes [Target node types] Element [DOM interface] MouseEvent [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [type] mousewheel [Bubbling phase] Yes [Target node types] Document, Element [DOM interface] MouseWheelEvent [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [type] reset [Bubbling phase] Yes [Target node types] Element [DOM interface] Event [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [type] resize [Bubbling phase] Yes [Target node types] Document, Element [DOM interface] UIEvent [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [type] scroll [Bubbling phase] No [Target node types] Document, Element [DOM interface] UIEvent [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [type] select [Bubbling phase] Yes [Target node types] Element [DOM interface] Event [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [type] submit [Bubbling phase] Yes [Target node types] Element [DOM interface] Event [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [type] textInput [Bubbling phase] Yes [Target node types] Element [DOM interface] TextEvent [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [type] unload [Bubbling phase] No [Target node types] Document, Element [DOM interface] Event [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [type] wheel [Bubbling phase] Yes [Target node types] Document, Element [DOM interface] WheelEvent [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [Issues] Current solution; people don't like reification [Technique]

Output: Reification


Input: [Issues] Doesn't really improve things over base reification [Technique]

Output: Reification shadow vocab


Input: [Issues] Not a standard feature. [Technique]

Output: Named Graphs


Input: [Issues] Doesn't work for axiom annotations; hurts roundtripping/transparency/editing; increases the complexity of the base logic [Technique]

Output: Encoding using equivalent forms (like nominals)


Input: [Issues] Some parsers can't handle that. [Technique]

Output: Using Literals


Input: [Issues] Loss of symmetry with regular expressions. [Technique]

Output: Some other syntactic form


Input: [Example] In email [Issues] Compact and clean, at least in some ways. But it requires special casing those URIs. You might have a different syntax/mimetype in the data uri than in the parent document. RFC 2397 Wikipedia article [Technique]

Output: Data schemed uris


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: [EXI Option] alignment [Default Value] bit-packed [Description]

Output: Alignment of event codes and content items

EXI Options in Options Field


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

Output: EXI compression is used to achieve better compactness

EXI Options in Options Field


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

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

EXI Options in Options Field


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

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

EXI Options in Options Field


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

Output: Specifies whether comments, pis, etc. are preserved

EXI Options in Options Field


Input: [EXI Option] schemaID [Default Value] none [Description]

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

EXI Options in Options Field


Input: [EXI Option] codecMap [Default Value] none [Description]

Output: Identify pluggable CODECs used to encode body

EXI Options in Options Field


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

Output: Specifies the block size used for EXI compression

EXI Options in Options Field


Input: [EXI Option] [user defined] [Default Value] none [Description]

Output: User defined headers may be added

EXI Options in Options Field


Input: [Definition] Character data [Attribute Type]

Output: CDATA

Modularization of XHTML - Defining Abstract Modules


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

Output: ID

Modularization of XHTML - Defining Abstract Modules


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

Output: IDREF

Modularization of XHTML - Defining Abstract Modules


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

Output: IDREFS

Modularization of XHTML - Defining Abstract Modules


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

Output: NAME

Modularization of XHTML - Defining Abstract Modules


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

Output: NMTOKEN

Modularization of XHTML - Defining Abstract Modules


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

Output: NMTOKENS

Modularization of XHTML - Defining Abstract Modules


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

Output: PCDATA

Modularization of XHTML - Defining Abstract Modules


Input: [Event Type] pointerdown [Sync/Async] Sync [Cancellable] Yes Document, Element [Event object interface] PointerEvent [Default Action] Varies: when the pointer is primary, all default actions of the mousedown event plus dispatch of compatibility mouse events [Bubbles]

Output: Yes


Input: [Event Type] pointerup [Sync/Async] Sync [Cancellable] Yes Document, Element [Event object interface] PointerEvent [Default Action] Varies: when the pointer is primary, all default actions of mouseup [Bubbles]

Output: Yes


Input: [Event Type] pointercancel [Sync/Async] Sync [Cancellable] Yes Document, Element [Event object interface] PointerEvent [Default Action] None [Bubbles]

Output: Yes


Input: [Event Type] pointermove [Sync/Async] Sync [Cancellable] Yes Document, Element [Event object interface] PointerEvent [Default Action] Varies: when the pointer is primary, all default actions of mousemove [Bubbles]

Output: Yes


Input: [Event Type] pointerover [Sync/Async] Sync [Cancellable] Yes Document, Element [Event object interface] PointerEvent [Default Action] Varies: when the pointer is primary, all default actions of mouseover [Bubbles]

Output: Yes


Input: [Event Type] pointerout [Sync/Async] Sync [Cancellable] Yes Document, Element [Event object interface] PointerEvent [Default Action] Varies: when the pointer is primary, all default actions of mouseout [Bubbles]

Output: Yes


Input: [Event Type] pointerenter [Sync/Async] Sync [Cancellable] Yes Document, Element [Event object interface] PointerEvent [Default Action] Varies: when the pointer is primary, all default actions of mouseenter [Bubbles]

Output: No


Input: [Event Type] pointerleave [Sync/Async] Sync [Cancellable] Yes Document, Element [Event object interface] PointerEvent [Default Action] Varies: when the pointer is primary, all default actions of mouseleave [Bubbles]

Output: No


Input: [Event Type] gotpointercapture [Sync/Async] Async [Cancellable] No Element [Event object interface] PointerEvent [Default Action] None [Bubbles]

Output: Yes


Input: [Event Type] lostpointercapture [Sync/Async] Async [Cancellable] No Element [Event object interface] PointerEvent [Default Action] None [Bubbles]

Output: Yes


Input: [Identifier] eq [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

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


Input: [Identifier] gt [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] gteq [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] hasPart [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] isA [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] isAllOf [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] isAnyOf [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] isNoneOf [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] isPartOf [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] lt [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] lteq [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] neq [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Event Type] pointerdown [Sync/Async] Sync [Bubbles] Yes Document, Element [Event object interface] PointerEvent [Default Action] Varies: when the pointer is primary, all default actions of the mousedown event plus dispatch of compatibility mouse events [Cancellable]

Output: Yes


Input: [Event Type] pointerup [Sync/Async] Sync [Bubbles] Yes Document, Element [Event object interface] PointerEvent [Default Action] Varies: when the pointer is primary, all default actions of mouseup [Cancellable]

Output: Yes


Input: [Event Type] pointercancel [Sync/Async] Sync [Bubbles] Yes Document, Element [Event object interface] PointerEvent [Default Action] None [Cancellable]

Output: Yes


Input: [Event Type] pointermove [Sync/Async] Sync [Bubbles] Yes Document, Element [Event object interface] PointerEvent [Default Action] Varies: when the pointer is primary, all default actions of mousemove [Cancellable]

Output: Yes


Input: [Event Type] pointerover [Sync/Async] Sync [Bubbles] Yes Document, Element [Event object interface] PointerEvent [Default Action] Varies: when the pointer is primary, all default actions of mouseover [Cancellable]

Output: Yes


Input: [Event Type] pointerout [Sync/Async] Sync [Bubbles] Yes Document, Element [Event object interface] PointerEvent [Default Action] Varies: when the pointer is primary, all default actions of mouseout [Cancellable]

Output: Yes


Input: [Event Type] pointerenter [Sync/Async] Sync [Bubbles] No Document, Element [Event object interface] PointerEvent [Default Action] Varies: when the pointer is primary, all default actions of mouseenter [Cancellable]

Output: Yes


Input: [Event Type] pointerleave [Sync/Async] Sync [Bubbles] No Document, Element [Event object interface] PointerEvent [Default Action] Varies: when the pointer is primary, all default actions of mouseleave [Cancellable]

Output: Yes


Input: [Event Type] gotpointercapture [Sync/Async] Async [Bubbles] Yes Element [Event object interface] PointerEvent [Default Action] None [Cancellable]

Output: No


Input: [Event Type] lostpointercapture [Sync/Async] Async [Bubbles] Yes Element [Event object interface] PointerEvent [Default Action] None [Cancellable]

Output: No


Input: [postal] name [Structure] personname [Short display name] Name [Category]

Output: Physical Contact Information, Demographic and Socioeconomic Data

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [postal] street [Structure] unstructured [Short display name] Street Address [Category]

Output: Physical Contact Information

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [postal] city [Structure] unstructured [Short display name] City [Category]

Output: Demographic and Socioeconomic Data

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [postal] stateprov [Structure] unstructured [Short display name] State or Province [Category]

Output: Demographic and Socioeconomic Data

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [postal] postalcode [Structure] unstructured [Short display name] Postal Code [Category]

Output: Demographic and Socioeconomic Data

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [postal] country [Structure] unstructured [Short display name] Country Name [Category]

Output: Demographic and Socioeconomic Data

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [postal] organization [Structure] unstructured [Short display name] Organization Name [Category]

Output: Demographic and Socioeconomic Data

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


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

Output: alignment

Table 2-3. EXI Options


Input: [Description] Indicates if EXI compression is to be used for better compactness [Default Value] false [EXI Option]

Output: compression

Table 2-3. EXI Options


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

Output: strict

Table 2-3. EXI Options


Input: [Description] Indicates if the body is to be encoded as an EXI fragment instead of an EXI document [Default Value] false [EXI Option]

Output: fragment

Table 2-3. EXI Options


Input: [Description] A set of options that controls whether comments, processing instructions, etc. are preserved [Default Value] all false [EXI Option]

Output: preserve

Table 2-3. EXI Options


Input: [Description] Enables self-contained elements. Self-contained elements may be read independently from the rest of the EXI body [Default Value] false [EXI Option]

Output: selfContained

Table 2-3. EXI Options


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

Output: schemaId

Table 2-3. EXI Options


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

Output: datatypeRepresentationMap

Table 2-3. EXI Options


Input: [Description] Specifies the number of Attribute (AT) and Character (CH) values for each block used for EXI compression [Default Value] 1,000,000 [EXI Option]

Output: blockSize

Table 2-3. EXI Options


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

Output: valueMaxLength

Table 2-3. EXI Options


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

Output: valuePartitionCapacity

Table 2-3. EXI Options


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

Output: [user defined meta-data]

Table 2-3. EXI Options


Input: [Status Code] element not selectable [Detail]

Output: An attempt was made to select an element that cannot be selected.


Input: [Status Code] element not visible [Detail]

Output: An element command could not be completed because the element is not visible on the page.


Input: [Status Code] ime engine activation failed [Detail]

Output: An IME engine could not be started.


Input: [Status Code] ime not available [Detail]

Output: IME was not available.


Input: [Status Code] invalid cookie domain [Detail]

Output: An illegal attempt was made to set a cookie under a different domain than the current page.


Input: [Status Code] invalid element coordinates [Detail]

Output: The coordinates provided to an interactions operation are invalid.


Input: [Status Code] invalid element state [Detail]

Output: An element command could not be completed because the element is in an invalid state (e.g. attempting to click an element that is no longer attached to the DOM).


Input: [Status Code] invalid selector [Detail]

Output: Argument was an invalid selector (e.g. XPath/CSS).


Input: [Status Code] javascript error [Detail]

Output: An error occurred while executing user supplied JavaScript.


Input: [Status Code] move target out of bounds [Detail]

Output: The target for mouse interaction is not in the browser's viewport and cannot be brought into that viewport.


Input: [Status Code] no such alert [Detail]

Output: An attempt was made to operate on a modal dialog when one was not open.


Input: [Status Code] no such dom [Detail]

Output: An attempt was made to switch to a hosted Shadow DOM that does not exist.


Input: [Status Code] no such element [Detail]

Output: An element could not be located on the page using the given search parameters.


Input: [Status Code] no such frame [Detail]

Output: A request to switch to a frame could not be satisfied because the frame could not be found.


Input: [Status Code] no such window [Detail]

Output: A request to switch to a different window could not be satisfied because the window could not be found.


Input: [Status Code] script timeout [Detail]

Output: A script did not complete before its timeout expired.


Input: [Status Code] session not created [Detail]

Output: A new session could not be created.


Input: [Status Code] stale element reference [Detail]

Output: An element command failed because the referenced element is no longer attached to the DOM.


Input: [Status Code] success [Detail]

Output: The command executed successfully.


Input: [Status Code] timeout [Detail]

Output: An operation did not complete before its timeout expired.


Input: [Status Code] unable to set cookie [Detail]

Output: A request to set a cookie's value could not be satisfied.


Input: [Status Code] unexpected alert open [Detail]

Output: A modal dialog was open, blocking this operation.


Input: [Status Code] unknown command [Detail]

Output: A command could not be executed because the remote end is not aware of it.


Input: [Status Code] unknown error [Detail]

Output: An unknown error occurred in the remote end while processing the command.


Input: [Status Code] unsupported operation [Detail]

Output: Indicates that a command that should have executed properly cannot be supported for some reason.


Input: [Commentor] LC-2641 Chaals McCathieNevile (archived comment) [Comment] 2. Many devices have more than one camera. Although it makes no sense to insist on a given one (some systems, like super-fancy video conferencing systems that used to be science fiction and are now feasible to construct from spare parts, have a lot of cameras), The fact that in a huge number of cases you can divide them into "facing the user" and "the rest", suggests that it would be nice to at least allow the simple hint as an author request. [Commentor reply] yes [Working Group decision]

Output: We changed the meaning of the capture attribute - it is now a boolean ( thus there are no keywords defined with it). The accept attribute defines the requested MIME type and if present the capture attribute indicates to use the device built-in capture mechanism to obtain content of that MIME type. Thus that mechanism could have a user interaction to determine which device, but that would be implementation dependent. I could also envision different MIME types for different camera choices (though maybe that would probably require standardization elsewhere). Given the wide range of possible accept content types, it probably does not make sense for the HTML Media Capture specification to define capture choices at the device (and the current specification does not provide a means to do so). The latest set of changes make this issue is moot since Keywords previously implied finer granularity but are no longer specified. http://lists.w3.org/Archives/Public/public-device-apis/2012Dec/0022.html

Disposition of comments for the Device APIs Working Group - Comments Tracker


Input: [Commentor] LC-2637 Doug Schepers (archived comment) [Comment] == Video and Audio == http://www.w3.org/TR/2012/WD-html-media-capture-20120712/#attributes The 'camcorder' keyword value may conflate video and audio; I can credibly see a use-case for video-only capture, and user expectation may be ambiguous if that's not called out explicitly when they are selecting their input (e.g. they may be unpleasantly surprised when they accept a video source and their audio is also captured). The user may also wish to select a different microphone input than is bundled with the videocamera. I suggest that the value of @capture should be a list of strings, not just a single value, i.e. This may result in a pair of source selections, sequentially selecting first the videocamera input, then the microphone input (or, depending on the UA and device, might have both in the same dialog... either way, it should be explicit). [Commentor reply] yes [Working Group decision]

Output: No change needed: The accept attribute takes precedence over the capture attribute as per the spec. This means camcorder+audio would be the same as no capture attribute is present if the implementation's video camera control is unable to capture audio only. If the implementation's video camera control is able to capture audio only (in addition to video), then camcorder+audio and microphone+audio would yield similar results i.e. an audio file. http://lists.w3.org/Archives/Public/public-device-apis/2012Aug/0101.html

Disposition of comments for the Device APIs Working Group - Comments Tracker


Input: [Commentor] LC-2635 Michael Cooper (archived comment) [Comment] The Protocols and Formats Working Group took a quick look at the HTML Media Capture specification http://www.w3.org/TR/2012/WD-html-media-capture-20120712/. In a teleconference discussion, minuted at https://www.w3.org/2012/07/18-pf-minutes.html, we had the following comments: What happens if the requested device is not present on the system? People with disabilities may have a different sub-set of devices available than mainstream users. We suggest the specification state explicitly that the user agent should fall back to a standard file upload widget in this situation. [Commentor reply] yes [Working Group decision]

Output: No change needed, addressed by the following normative prose: "The capture attribute's invalid value default and missing value default is the File Upload state."

Disposition of comments for the Device APIs Working Group - Comments Tracker


Input: [Commentor] LC-2636 Michael Cooper (archived comment) [Comment] The Protocols and Formats Working Group took a quick look at the HTML Media Capture specification http://www.w3.org/TR/2012/WD-html-media-capture-20120712/. In a teleconference discussion, minuted at https://www.w3.org/2012/07/18-pf-minutes.html, we had the following comments: * The specification should make explicit statements about security expectations, e.g., requesting permission before turning the microphone on in order to capture from it. [Commentor reply] yes [Working Group decision]

Output: Text added to to the Security and Privacy Considerations section "The user agent should not enable any device for media capture, such as a microphone or camera, until a user interaction giving implicit consent is completed. A user agent should also provide an indication when such an input device is enabled and make it possible to terminate such capture. Similarly, the user agent should allow the user: * to select the exact media capture device to be used if there exists multiple devices of the same type (e.g. a front-facing camera in addition to a primary camera). * to disable sound capture when in the video capture mode." see http://dev.w3.org/2009/dap/camera/#security diff http://dev.w3.org/cvsweb/2009/dap/camera/Overview.html.diff?r1=1.133;r2=1.134;f=h

Disposition of comments for the Device APIs Working Group - Comments Tracker


Input: [Commentor] LC-2640 Chaals McCathieNevile (archived comment) [Comment] Editorial... 1. That the capture attribute in HTML can be added in markup (rather than being added as a DOM attribute in script) is not obvious from the text, but only from the example section. It would be helpful to clarify this. [Commentor reply] yes [Working Group decision]

Output: http://lists.w3.org/Archives/Public/public-device-apis/2012Dec/0022.html We addressed this in a number of places (for formatted version of quoted text see draft link below): Introduction: "The HTML Media Capture specification enables web page authors to declaratively specify the upload of audio, video and still images by adding a new attribute to the HTML input element." Terminology: "The input element, HTMLInputElement interface, accept attribute, and File Upload state are defined in [HTML5]." This indicates that input is an HTML element. Examples: Examples 1,2,3 show declarative form without requiring Javascript; example 4 shows use of markup without form and examples 5-7 show how this can be processed. http://dev.w3.org/2009/dap/camera/

Disposition of comments for the Device APIs Working Group - Comments Tracker


Input: [Commentor] LC-2638 Doug Schepers (archived comment) [Comment] http://www.w3.org/TR/2012/WD-html-media-capture-20120712/#examples I like the example of camera access; I think that makes usage clear to developers. I would like also like to see an example of microphone access, and an example of camcorder+audio input. [Commentor reply] yes [Working Group decision]

Output: Added examples of a video and audio capture to specification, see http://dev.w3.org/2009/dap/camera/#examples

Disposition of comments for the Device APIs Working Group - Comments Tracker


Input: [Commentor] LC-2639 Doug Schepers (archived comment) [Comment] http://www.w3.org/TR/2012/WD-html-media-capture-20120712/#attributes Why 'camcorder' instead of 'videocamera'? I think 'videocamera' would be more intuitive for non-native speakers. [Commentor reply] yes [Working Group decision]

Output: No change in order to maintain consistency with Android 4.0 browser and Chrome for Android.

Disposition of comments for the Device APIs Working Group - Comments Tracker


Input: [Commentor] LC-2642 fantasai (archived comment) [Comment] Hi! I was wondering, how is 'capture' different from 'accept'? It seems to me the following are equivalent: capture accept ---------------------- camera image/* camcorder video/* microphone audio/* filesystem */* ~fantasai [Commentor reply] yes [Working Group decision]

Output: No changes to the specification are needed, please see http://www.w3.org/mid/50127EC5.2080705@opera.com [[ > Not only would this avoid duplication, it also avoids conflicts like > > I believe the spec does address this: "The HTMLInputElement interface's accept attribute takes precedence over the capture attribute. That is, if the accept attribute's value is set to a MIME type that is not accepted in a defined capture state, the user agent must act as if there was no capture attribute." ]] additional updates as part of resolution : http://lists.w3.org/Archives/Public/public-device-apis/2012Dec/0032.html

Disposition of comments for the Device APIs Working Group - Comments Tracker


Input: [Commentor] LC-2644 NN Murthy (archived comment) [Comment] Dear all, This is regarding the above publication. Images media type are captured by computer applications, not only using cameras but also, using document scanners. Another source of images are live scan devices for capturing finger prints, palm prints, iris etc. Can the standard address these requirements? N N Murthy [Commentor reply] yes [Working Group decision]

Output: Changing capture attribute to boolean resolves issue.

Disposition of comments for the Device APIs Working Group - Comments Tracker


Input: [Name] boxdl [Unicode] U+2510 [Unicode Name] BOX DRAWINGS LIGHT DOWN AND LEFT [Description]

Output: lower left quadrant


Input: [Name] boxdL [Unicode] U+2555 [Unicode Name] BOX DRAWINGS DOWN SINGLE AND LEFT DOUBLE [Description]

Output: lower left quadrant


Input: [Name] boxDl [Unicode] U+2556 [Unicode Name] BOX DRAWINGS DOWN DOUBLE AND LEFT SINGLE [Description]

Output: lower left quadrant


Input: [Name] boxDL [Unicode] U+2557 [Unicode Name] BOX DRAWINGS DOUBLE DOWN AND LEFT [Description]

Output: lower left quadrant


Input: [Name] boxdr [Unicode] U+250C [Unicode Name] BOX DRAWINGS LIGHT DOWN AND RIGHT [Description]

Output: lower right quadrant


Input: [Name] boxdR [Unicode] U+2552 [Unicode Name] BOX DRAWINGS DOWN SINGLE AND RIGHT DOUBLE [Description]

Output: lower right quadrant


Input: [Name] boxDr [Unicode] U+2553 [Unicode Name] BOX DRAWINGS DOWN DOUBLE AND RIGHT SINGLE [Description]

Output: lower right quadrant


Input: [Name] boxDR [Unicode] U+2554 [Unicode Name] BOX DRAWINGS DOUBLE DOWN AND RIGHT [Description]

Output: lower right quadrant


Input: [Name] boxh [Unicode] U+2500 [Unicode Name] BOX DRAWINGS LIGHT HORIZONTAL [Aliases] HorizontalLine [Description]

Output: horizontal line


Input: [Name] boxH [Unicode] U+2550 [Unicode Name] BOX DRAWINGS DOUBLE HORIZONTAL [Description]

Output: horizontal line


Input: [Name] boxhd [Unicode] U+252C [Unicode Name] BOX DRAWINGS LIGHT DOWN AND HORIZONTAL [Description]

Output: lower left and right quadrants


Input: [Name] boxhD [Unicode] U+2565 [Unicode Name] BOX DRAWINGS DOWN DOUBLE AND HORIZONTAL SINGLE [Description]

Output: lower left and right quadrants


Input: [Name] boxHd [Unicode] U+2564 [Unicode Name] BOX DRAWINGS DOWN SINGLE AND HORIZONTAL DOUBLE [Description]

Output: lower left and right quadrants


Input: [Name] boxHD [Unicode] U+2566 [Unicode Name] BOX DRAWINGS DOUBLE DOWN AND HORIZONTAL [Description]

Output: lower left and right quadrants


Input: [Name] boxhu [Unicode] U+2534 [Unicode Name] BOX DRAWINGS LIGHT UP AND HORIZONTAL [Description]

Output: upper left and right quadrants


Input: [Name] boxhU [Unicode] U+2568 [Unicode Name] BOX DRAWINGS UP DOUBLE AND HORIZONTAL SINGLE [Description]

Output: upper left and right quadrants


Input: [Name] boxHu [Unicode] U+2567 [Unicode Name] BOX DRAWINGS UP SINGLE AND HORIZONTAL DOUBLE [Description]

Output: upper left and right quadrants


Input: [Name] boxHU [Unicode] U+2569 [Unicode Name] BOX DRAWINGS DOUBLE UP AND HORIZONTAL [Description]

Output: upper left and right quadrants


Input: [Name] boxul [Unicode] U+2518 [Unicode Name] BOX DRAWINGS LIGHT UP AND LEFT [Description]

Output: upper left quadrant


Input: [Name] boxuL [Unicode] U+255B [Unicode Name] BOX DRAWINGS UP SINGLE AND LEFT DOUBLE [Description]

Output: upper left quadrant


Input: [Name] boxUl [Unicode] U+255C [Unicode Name] BOX DRAWINGS UP DOUBLE AND LEFT SINGLE [Description]

Output: upper left quadrant


Input: [Name] boxUL [Unicode] U+255D [Unicode Name] BOX DRAWINGS DOUBLE UP AND LEFT [Description]

Output: upper left quadrant


Input: [Name] boxur [Unicode] U+2514 [Unicode Name] BOX DRAWINGS LIGHT UP AND RIGHT [Description]

Output: upper right quadrant


Input: [Name] boxuR [Unicode] U+2558 [Unicode Name] BOX DRAWINGS UP SINGLE AND RIGHT DOUBLE [Description]

Output: upper right quadrant


Input: [Name] boxUr [Unicode] U+2559 [Unicode Name] BOX DRAWINGS UP DOUBLE AND RIGHT SINGLE [Description]

Output: upper right quadrant


Input: [Name] boxUR [Unicode] U+255A [Unicode Name] BOX DRAWINGS DOUBLE UP AND RIGHT [Description]

Output: upper right quadrant


Input: [Name] boxv [Unicode] U+2502 [Unicode Name] BOX DRAWINGS LIGHT VERTICAL [Description]

Output: vertical line


Input: [Name] boxV [Unicode] U+2551 [Unicode Name] BOX DRAWINGS DOUBLE VERTICAL [Description]

Output: vertical line


Input: [Name] boxvh [Unicode] U+253C [Unicode Name] BOX DRAWINGS LIGHT VERTICAL AND HORIZONTAL [Description]

Output: all four quadrants


Input: [Name] boxvH [Unicode] U+256A [Unicode Name] BOX DRAWINGS VERTICAL SINGLE AND HORIZONTAL DOUBLE [Description]

Output: all four quadrants


Input: [Name] boxVh [Unicode] U+256B [Unicode Name] BOX DRAWINGS VERTICAL DOUBLE AND HORIZONTAL SINGLE [Description]

Output: all four quadrants


Input: [Name] boxVH [Unicode] U+256C [Unicode Name] BOX DRAWINGS DOUBLE VERTICAL AND HORIZONTAL [Description]

Output: all four quadrants


Input: [Name] boxvl [Unicode] U+2524 [Unicode Name] BOX DRAWINGS LIGHT VERTICAL AND LEFT [Description]

Output: upper and lower left quadrants


Input: [Name] boxvL [Unicode] U+2561 [Unicode Name] BOX DRAWINGS VERTICAL SINGLE AND LEFT DOUBLE [Description]

Output: upper and lower left quadrants


Input: [Name] boxVl [Unicode] U+2562 [Unicode Name] BOX DRAWINGS VERTICAL DOUBLE AND LEFT SINGLE [Description]

Output: upper and lower left quadrants


Input: [Name] boxVL [Unicode] U+2563 [Unicode Name] BOX DRAWINGS DOUBLE VERTICAL AND LEFT [Description]

Output: upper and lower left quadrants


Input: [Name] boxvr [Unicode] U+251C [Unicode Name] BOX DRAWINGS LIGHT VERTICAL AND RIGHT [Description]

Output: upper and lower right quadrants


Input: [Name] boxvR [Unicode] U+255E [Unicode Name] BOX DRAWINGS VERTICAL SINGLE AND RIGHT DOUBLE [Description]

Output: upper and lower right quadrants


Input: [Name] boxVr [Unicode] U+255F [Unicode Name] BOX DRAWINGS VERTICAL DOUBLE AND RIGHT SINGLE [Description]

Output: upper and lower right quadrants


Input: [Name] boxVR [Unicode] U+2560 [Unicode Name] BOX DRAWINGS DOUBLE VERTICAL AND RIGHT [Description]

Output: upper and lower right quadrants


Input: [Identifier] acceptTracking [Comment] The collected information may be tracked by the Assigner, or may link to a Party with the role function “trackingParty”. [Semantics]

Output: The Assigner requires that the Assignee(s) accepts that the use of the Asset may be tracked

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

Table 2.2.2: Terms for entity Action used with Duty


Input: [Identifier] attribute [Comment] May link to an Asset with the attribution information. May link to a Party with the role function “attributedParty”. [Semantics]

Output: The Assigner requires that the Assignee(s) attributes the Asset to the Assigner or an attributed Party.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] compensate [Comment] The compensation may use different types of things with a value: – the thing is expressed by the value (term) of the Constraint name – the value is expressed by operator, rightOperand, dataType and unit [Semantics]

Output: The Assigner requires that the Assignee(s) compensates the Assigner (or other specified compensation Party) by some amount of value, if defined, for use of the Asset.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] delete [Comment] Use a constraint to define under which conditions the Asset should be deleted. [Semantics]

Output: The Assigner requires that the Assignee(s) permanently removes all copies of the Asset.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] ensureExclusivity [Semantics]

Output: The Assignee requires that the Assigner(s) ensure(s) that the permission on the Asset is exclusive to the Assignee.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] include [Comment] For example; Bio picture must be included in the attribution. Use of the Asset relation attribute is required [Semantics]

Output: The Assigner requires that the Assignee(s) include(s) other related assets in the Asset.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] inform [Comment] May link to a Party with the role function “informedParty”. [Semantics]

Output: The Assigner requires that the Assignee(s) inform(s) the Assigner or an informed Party that an action has been performed on or in relation to the Asset.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] nextPolicy [Semantics]

Output: The Assigner requires that the Assignee(s) grants the specified Policy to a third party for their use of the Asset.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] obtainConsent [Comment] Used as a Duty to ensure that the Assigner or a Party is authorized to approve such actions on a case-by-case basis. May link to a Party with the role function “consentingParty”. [Semantics]

Output: The Assigner requires that the Assignee(s) obtains explicit consent from the Assigner or a consenting Party to perform the requested action in relation to the Asset.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] reviewPolicy [Comment] Used when human intervention is required to review the Policy. May link to an Asset which represents the full Policy information. [Semantics]

Output: The Assigner requires that the Assignee(s) has(ve) a person review the Policy applicable to the Asset.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] uninstall [Comment] The Asset is no longer accessible to the Assignee(s). [Semantics]

Output: The Assigner requires that the Assignee(s) unload(s) and delete(s) the computer program Asset from a storage device and disable(s) its readiness for operation.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] watermark [Comment] It is recommended to embed a link to the watermark. [Semantics]

Output: The Assigner requires that the Assignee(s) apply(ies) a watermark as provided by the Assigner to the Asset.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Event Type] pointerdown [Sync/Async] Sync [Bubbles] Yes [Cancellable] Yes Document, Element [Event object interface] PointerEvent [Default Action]

Output: Varies: when the pointer is primary, all default actions of the mousedown event plus dispatch of compatibility mouse events


Input: [Event Type] pointerup [Sync/Async] Sync [Bubbles] Yes [Cancellable] Yes Document, Element [Event object interface] PointerEvent [Default Action]

Output: Varies: when the pointer is primary, all default actions of mouseup


Input: [Event Type] pointercancel [Sync/Async] Sync [Bubbles] Yes [Cancellable] Yes Document, Element [Event object interface] PointerEvent [Default Action]


Input: [Event Type] pointermove [Sync/Async] Sync [Bubbles] Yes [Cancellable] Yes Document, Element [Event object interface] PointerEvent [Default Action]

Output: Varies: when the pointer is primary, all default actions of mousemove


Input: [Event Type] pointerover [Sync/Async] Sync [Bubbles] Yes [Cancellable] Yes Document, Element [Event object interface] PointerEvent [Default Action]

Output: Varies: when the pointer is primary, all default actions of mouseover


Input: [Event Type] pointerout [Sync/Async] Sync [Bubbles] Yes [Cancellable] Yes Document, Element [Event object interface] PointerEvent [Default Action]

Output: Varies: when the pointer is primary, all default actions of mouseout


Input: [Event Type] pointerenter [Sync/Async] Sync [Bubbles] No [Cancellable] Yes Document, Element [Event object interface] PointerEvent [Default Action]

Output: Varies: when the pointer is primary, all default actions of mouseenter


Input: [Event Type] pointerleave [Sync/Async] Sync [Bubbles] No [Cancellable] Yes Document, Element [Event object interface] PointerEvent [Default Action]

Output: Varies: when the pointer is primary, all default actions of mouseleave


Input: [Event Type] gotpointercapture [Sync/Async] Async [Bubbles] Yes [Cancellable] No Element [Event object interface] PointerEvent [Default Action]


Input: [Event Type] lostpointercapture [Sync/Async] Async [Bubbles] Yes [Cancellable] No Element [Event object interface] PointerEvent [Default Action]


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

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


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

Output: List of bad links in the page


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

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


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

Output: List of HTML markup errors.


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

Output: List of spelling errors.


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

Output: List of style CSS errors.


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

Output: Log of changes to the document


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

Output: HTTP headers sent by the server


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

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


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

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


Input: [Name] boxdl [Unicode] U+2510 [Description] lower left quadrant [Unicode Name]

Output: BOX DRAWINGS LIGHT DOWN AND LEFT


Input: [Name] boxdL [Unicode] U+2555 [Description] lower left quadrant [Unicode Name]

Output: BOX DRAWINGS DOWN SINGLE AND LEFT DOUBLE


Input: [Name] boxDl [Unicode] U+2556 [Description] lower left quadrant [Unicode Name]

Output: BOX DRAWINGS DOWN DOUBLE AND LEFT SINGLE


Input: [Name] boxDL [Unicode] U+2557 [Description] lower left quadrant [Unicode Name]

Output: BOX DRAWINGS DOUBLE DOWN AND LEFT


Input: [Name] boxdr [Unicode] U+250C [Description] lower right quadrant [Unicode Name]

Output: BOX DRAWINGS LIGHT DOWN AND RIGHT


Input: [Name] boxdR [Unicode] U+2552 [Description] lower right quadrant [Unicode Name]

Output: BOX DRAWINGS DOWN SINGLE AND RIGHT DOUBLE


Input: [Name] boxDr [Unicode] U+2553 [Description] lower right quadrant [Unicode Name]

Output: BOX DRAWINGS DOWN DOUBLE AND RIGHT SINGLE


Input: [Name] boxDR [Unicode] U+2554 [Description] lower right quadrant [Unicode Name]

Output: BOX DRAWINGS DOUBLE DOWN AND RIGHT


Input: [Name] boxh [Unicode] U+2500 [Description] horizontal line [Aliases] HorizontalLine [Unicode Name]

Output: BOX DRAWINGS LIGHT HORIZONTAL


Input: [Name] boxH [Unicode] U+2550 [Description] horizontal line [Unicode Name]

Output: BOX DRAWINGS DOUBLE HORIZONTAL


Input: [Name] boxhd [Unicode] U+252C [Description] lower left and right quadrants [Unicode Name]

Output: BOX DRAWINGS LIGHT DOWN AND HORIZONTAL


Input: [Name] boxhD [Unicode] U+2565 [Description] lower left and right quadrants [Unicode Name]

Output: BOX DRAWINGS DOWN DOUBLE AND HORIZONTAL SINGLE


Input: [Name] boxHd [Unicode] U+2564 [Description] lower left and right quadrants [Unicode Name]

Output: BOX DRAWINGS DOWN SINGLE AND HORIZONTAL DOUBLE


Input: [Name] boxHD [Unicode] U+2566 [Description] lower left and right quadrants [Unicode Name]

Output: BOX DRAWINGS DOUBLE DOWN AND HORIZONTAL


Input: [Name] boxhu [Unicode] U+2534 [Description] upper left and right quadrants [Unicode Name]

Output: BOX DRAWINGS LIGHT UP AND HORIZONTAL


Input: [Name] boxhU [Unicode] U+2568 [Description] upper left and right quadrants [Unicode Name]

Output: BOX DRAWINGS UP DOUBLE AND HORIZONTAL SINGLE


Input: [Name] boxHu [Unicode] U+2567 [Description] upper left and right quadrants [Unicode Name]

Output: BOX DRAWINGS UP SINGLE AND HORIZONTAL DOUBLE


Input: [Name] boxHU [Unicode] U+2569 [Description] upper left and right quadrants [Unicode Name]

Output: BOX DRAWINGS DOUBLE UP AND HORIZONTAL


Input: [Name] boxul [Unicode] U+2518 [Description] upper left quadrant [Unicode Name]

Output: BOX DRAWINGS LIGHT UP AND LEFT


Input: [Name] boxuL [Unicode] U+255B [Description] upper left quadrant [Unicode Name]

Output: BOX DRAWINGS UP SINGLE AND LEFT DOUBLE


Input: [Name] boxUl [Unicode] U+255C [Description] upper left quadrant [Unicode Name]

Output: BOX DRAWINGS UP DOUBLE AND LEFT SINGLE


Input: [Name] boxUL [Unicode] U+255D [Description] upper left quadrant [Unicode Name]

Output: BOX DRAWINGS DOUBLE UP AND LEFT


Input: [Name] boxur [Unicode] U+2514 [Description] upper right quadrant [Unicode Name]

Output: BOX DRAWINGS LIGHT UP AND RIGHT


Input: [Name] boxuR [Unicode] U+2558 [Description] upper right quadrant [Unicode Name]

Output: BOX DRAWINGS UP SINGLE AND RIGHT DOUBLE


Input: [Name] boxUr [Unicode] U+2559 [Description] upper right quadrant [Unicode Name]

Output: BOX DRAWINGS UP DOUBLE AND RIGHT SINGLE


Input: [Name] boxUR [Unicode] U+255A [Description] upper right quadrant [Unicode Name]

Output: BOX DRAWINGS DOUBLE UP AND RIGHT


Input: [Name] boxv [Unicode] U+2502 [Description] vertical line [Unicode Name]

Output: BOX DRAWINGS LIGHT VERTICAL


Input: [Name] boxV [Unicode] U+2551 [Description] vertical line [Unicode Name]

Output: BOX DRAWINGS DOUBLE VERTICAL


Input: [Name] boxvh [Unicode] U+253C [Description] all four quadrants [Unicode Name]

Output: BOX DRAWINGS LIGHT VERTICAL AND HORIZONTAL


Input: [Name] boxvH [Unicode] U+256A [Description] all four quadrants [Unicode Name]

Output: BOX DRAWINGS VERTICAL SINGLE AND HORIZONTAL DOUBLE


Input: [Name] boxVh [Unicode] U+256B [Description] all four quadrants [Unicode Name]

Output: BOX DRAWINGS VERTICAL DOUBLE AND HORIZONTAL SINGLE


Input: [Name] boxVH [Unicode] U+256C [Description] all four quadrants [Unicode Name]

Output: BOX DRAWINGS DOUBLE VERTICAL AND HORIZONTAL


Input: [Name] boxvl [Unicode] U+2524 [Description] upper and lower left quadrants [Unicode Name]

Output: BOX DRAWINGS LIGHT VERTICAL AND LEFT


Input: [Name] boxvL [Unicode] U+2561 [Description] upper and lower left quadrants [Unicode Name]

Output: BOX DRAWINGS VERTICAL SINGLE AND LEFT DOUBLE


Input: [Name] boxVl [Unicode] U+2562 [Description] upper and lower left quadrants [Unicode Name]

Output: BOX DRAWINGS VERTICAL DOUBLE AND LEFT SINGLE


Input: [Name] boxVL [Unicode] U+2563 [Description] upper and lower left quadrants [Unicode Name]

Output: BOX DRAWINGS DOUBLE VERTICAL AND LEFT


Input: [Name] boxvr [Unicode] U+251C [Description] upper and lower right quadrants [Unicode Name]

Output: BOX DRAWINGS LIGHT VERTICAL AND RIGHT


Input: [Name] boxvR [Unicode] U+255E [Description] upper and lower right quadrants [Unicode Name]

Output: BOX DRAWINGS VERTICAL SINGLE AND RIGHT DOUBLE


Input: [Name] boxVr [Unicode] U+255F [Description] upper and lower right quadrants [Unicode Name]

Output: BOX DRAWINGS VERTICAL DOUBLE AND RIGHT SINGLE


Input: [Name] boxVR [Unicode] U+2560 [Description] upper and lower right quadrants [Unicode Name]

Output: BOX DRAWINGS DOUBLE VERTICAL AND RIGHT


Input: [Property] hanging-punctuation [Initial] none [Applies to] inline elements [Inh.] yes [Percentages] N/A [Media] visual [Values]

Output: none | [ first || [ force-end | allow-end ] || last ]


Input: [Property] hyphens [Initial] manual [Applies to] all elements [Inh.] yes [Percentages] N/A [Media] visual [Values]

Output: none | manual | auto


Input: [Property] letter-spacing [Initial] normal [Applies to] all elements [Inh.] yes [Percentages] N/A [Media] visual [Values]

Output: normal |


Input: [Property] line-break [Initial] auto [Applies to] all elements [Inh.] yes [Percentages] N/A [Media] visual [Values]

Output: auto | loose | normal | strict


Input: [Property] overflow-wrap [Initial] normal [Applies to] all elements [Inh.] yes [Percentages] N/A [Media] visual [Values]

Output: normal | break-word


Input: [Property] tab-size [Initial] 8 [Applies to] block containers [Inh.] yes [Percentages] N/A [Media] visual [Values]


Input: [Property] text-align [Initial] start [Applies to] block containers [Inh.] yes [Percentages] N/A [Media] visual [Values]

Output: start | end | left | right | center | justify | match-parent | start end


Input: [Property] text-align-last [Initial] auto [Applies to] block containers [Inh.] yes [Percentages] N/A [Media] visual [Values]

Output: auto | start | end | left | right | center | justify


Input: [Property] text-indent [Initial] 0 [Applies to] block containers [Inh.] yes [Percentages] refers to width of containing block [Media] visual [Values]

Output: [ | ] && hanging? && each-line?


Input: [Property] text-justify [Initial] auto [Applies to] block containers and, optionally, inline elements [Inh.] yes [Percentages] N/A [Media] visual [Values]

Output: auto | none | inter-word | distribute


Input: [Property] text-transform [Initial] none [Applies to] all elements [Inh.] yes [Percentages] N/A [Media] visual [Values]

Output: none | capitalize | uppercase | lowercase | full-width


Input: [Property] white-space [Initial] normal [Applies to] all elements [Inh.] yes [Percentages] N/A [Media] visual [Values]

Output: normal | pre | nowrap | pre-wrap | pre-line


Input: [Property] word-break [Initial] normal [Applies to] all elements [Inh.] yes [Percentages] N/A [Media] visual [Values]

Output: normal | keep-all | break-all


Input: [Property] word-spacing [Initial] normal [Applies to] all elements [Inh.] yes [Percentages] refers to width of the affected glyph [Media] visual [Values]

Output: [ normal | | ]


Input: [Property] word-wrap [Initial] normal [Applies to] all elements [Inh.] yes [Percentages] N/A [Media] visual [Values]

Output: normal | break-word


Input: [Technique] Reification [Issues]

Output: Current solution; people don't like reification


Input: [Technique] Reification shadow vocab [Issues]

Output: Doesn't really improve things over base reification


Input: [Technique] Named Graphs [Issues]

Output: Not a standard feature.


Input: [Technique] Encoding using equivalent forms (like nominals) [Issues]

Output: Doesn't work for axiom annotations; hurts roundtripping/transparency/editing; increases the complexity of the base logic


Input: [Technique] Using Literals [Issues]

Output: Some parsers can't handle that.


Input: [Technique] Some other syntactic form [Issues]

Output: Loss of symmetry with regular expressions.


Input: [Technique] Data schemed uris [Example] In email [Issues]

Output: Compact and clean, at least in some ways. But it requires special casing those URIs. You might have a different syntax/mimetype in the data uri than in the parent document. RFC 2397 Wikipedia article


Input: [Commentor] LC-2641 Chaals McCathieNevile (archived comment) [Working Group decision] We changed the meaning of the capture attribute - it is now a boolean ( thus there are no keywords defined with it). The accept attribute defines the requested MIME type and if present the capture attribute indicates to use the device built-in capture mechanism to obtain content of that MIME type. Thus that mechanism could have a user interaction to determine which device, but that would be implementation dependent. I could also envision different MIME types for different camera choices (though maybe that would probably require standardization elsewhere). Given the wide range of possible accept content types, it probably does not make sense for the HTML Media Capture specification to define capture choices at the device (and the current specification does not provide a means to do so). The latest set of changes make this issue is moot since Keywords previously implied finer granularity but are no longer specified. http://lists.w3.org/Archives/Public/public-device-apis/2012Dec/0022.html [Commentor reply] yes [Comment]

Output: 2. Many devices have more than one camera. Although it makes no sense to insist on a given one (some systems, like super-fancy video conferencing systems that used to be science fiction and are now feasible to construct from spare parts, have a lot of cameras), The fact that in a huge number of cases you can divide them into "facing the user" and "the rest", suggests that it would be nice to at least allow the simple hint as an author request.

Disposition of comments for the Device APIs Working Group - Comments Tracker


Input: [Commentor] LC-2637 Doug Schepers (archived comment) [Working Group decision] No change needed: The accept attribute takes precedence over the capture attribute as per the spec. This means camcorder+audio would be the same as no capture attribute is present if the implementation's video camera control is unable to capture audio only. If the implementation's video camera control is able to capture audio only (in addition to video), then camcorder+audio and microphone+audio would yield similar results i.e. an audio file. http://lists.w3.org/Archives/Public/public-device-apis/2012Aug/0101.html [Commentor reply] yes [Comment]

Output: == Video and Audio == http://www.w3.org/TR/2012/WD-html-media-capture-20120712/#attributes The 'camcorder' keyword value may conflate video and audio; I can credibly see a use-case for video-only capture, and user expectation may be ambiguous if that's not called out explicitly when they are selecting their input (e.g. they may be unpleasantly surprised when they accept a video source and their audio is also captured). The user may also wish to select a different microphone input than is bundled with the videocamera. I suggest that the value of @capture should be a list of strings, not just a single value, i.e. This may result in a pair of source selections, sequentially selecting first the videocamera input, then the microphone input (or, depending on the UA and device, might have both in the same dialog... either way, it should be explicit).

Disposition of comments for the Device APIs Working Group - Comments Tracker


Input: [Commentor] LC-2635 Michael Cooper (archived comment) [Working Group decision] No change needed, addressed by the following normative prose: "The capture attribute's invalid value default and missing value default is the File Upload state." [Commentor reply] yes [Comment]

Output: The Protocols and Formats Working Group took a quick look at the HTML Media Capture specification http://www.w3.org/TR/2012/WD-html-media-capture-20120712/. In a teleconference discussion, minuted at https://www.w3.org/2012/07/18-pf-minutes.html, we had the following comments: What happens if the requested device is not present on the system? People with disabilities may have a different sub-set of devices available than mainstream users. We suggest the specification state explicitly that the user agent should fall back to a standard file upload widget in this situation.

Disposition of comments for the Device APIs Working Group - Comments Tracker


Input: [Commentor] LC-2636 Michael Cooper (archived comment) [Working Group decision] Text added to to the Security and Privacy Considerations section "The user agent should not enable any device for media capture, such as a microphone or camera, until a user interaction giving implicit consent is completed. A user agent should also provide an indication when such an input device is enabled and make it possible to terminate such capture. Similarly, the user agent should allow the user: * to select the exact media capture device to be used if there exists multiple devices of the same type (e.g. a front-facing camera in addition to a primary camera). * to disable sound capture when in the video capture mode." see http://dev.w3.org/2009/dap/camera/#security diff http://dev.w3.org/cvsweb/2009/dap/camera/Overview.html.diff?r1=1.133;r2=1.134;f=h [Commentor reply] yes [Comment]

Output: The Protocols and Formats Working Group took a quick look at the HTML Media Capture specification http://www.w3.org/TR/2012/WD-html-media-capture-20120712/. In a teleconference discussion, minuted at https://www.w3.org/2012/07/18-pf-minutes.html, we had the following comments: * The specification should make explicit statements about security expectations, e.g., requesting permission before turning the microphone on in order to capture from it.

Disposition of comments for the Device APIs Working Group - Comments Tracker


Input: [Commentor] LC-2640 Chaals McCathieNevile (archived comment) [Working Group decision] http://lists.w3.org/Archives/Public/public-device-apis/2012Dec/0022.html We addressed this in a number of places (for formatted version of quoted text see draft link below): Introduction: "The HTML Media Capture specification enables web page authors to declaratively specify the upload of audio, video and still images by adding a new attribute to the HTML input element." Terminology: "The input element, HTMLInputElement interface, accept attribute, and File Upload state are defined in [HTML5]." This indicates that input is an HTML element. Examples: Examples 1,2,3 show declarative form without requiring Javascript; example 4 shows use of markup without form and examples 5-7 show how this can be processed. http://dev.w3.org/2009/dap/camera/ [Commentor reply] yes [Comment]

Output: Editorial... 1. That the capture attribute in HTML can be added in markup (rather than being added as a DOM attribute in script) is not obvious from the text, but only from the example section. It would be helpful to clarify this.

Disposition of comments for the Device APIs Working Group - Comments Tracker


Input: [Commentor] LC-2638 Doug Schepers (archived comment) [Working Group decision] Added examples of a video and audio capture to specification, see http://dev.w3.org/2009/dap/camera/#examples [Commentor reply] yes [Comment]

Output: http://www.w3.org/TR/2012/WD-html-media-capture-20120712/#examples I like the example of camera access; I think that makes usage clear to developers. I would like also like to see an example of microphone access, and an example of camcorder+audio input.

Disposition of comments for the Device APIs Working Group - Comments Tracker


Input: [Commentor] LC-2639 Doug Schepers (archived comment) [Working Group decision] No change in order to maintain consistency with Android 4.0 browser and Chrome for Android. [Commentor reply] yes [Comment]

Output: http://www.w3.org/TR/2012/WD-html-media-capture-20120712/#attributes Why 'camcorder' instead of 'videocamera'? I think 'videocamera' would be more intuitive for non-native speakers.

Disposition of comments for the Device APIs Working Group - Comments Tracker


Input: [Commentor] LC-2642 fantasai (archived comment) [Working Group decision] No changes to the specification are needed, please see http://www.w3.org/mid/50127EC5.2080705@opera.com [[ > Not only would this avoid duplication, it also avoids conflicts like > > I believe the spec does address this: "The HTMLInputElement interface's accept attribute takes precedence over the capture attribute. That is, if the accept attribute's value is set to a MIME type that is not accepted in a defined capture state, the user agent must act as if there was no capture attribute." ]] additional updates as part of resolution : http://lists.w3.org/Archives/Public/public-device-apis/2012Dec/0032.html [Commentor reply] yes [Comment]

Output: Hi! I was wondering, how is 'capture' different from 'accept'? It seems to me the following are equivalent: capture accept ---------------------- camera image/* camcorder video/* microphone audio/* filesystem */* ~fantasai

Disposition of comments for the Device APIs Working Group - Comments Tracker


Input: [Commentor] LC-2644 NN Murthy (archived comment) [Working Group decision] Changing capture attribute to boolean resolves issue. [Commentor reply] yes [Comment]

Output: Dear all, This is regarding the above publication. Images media type are captured by computer applications, not only using cameras but also, using document scanners. Another source of images are live scan devices for capturing finger prints, palm prints, iris etc. Can the standard address these requirements? N N Murthy

Disposition of comments for the Device APIs Working Group - Comments Tracker


Input: [Identifier] Individual [Comment] Must be supported. [Semantics]

Output: The Party is a single individual

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

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


Input: [Identifier] Group [Comment] Must be supported. [Semantics]

Output: The Party represents a defined group with multiple individual members

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: All the collective individuals within a context

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: All the first-level connections of the Party

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: All the second-level connections of the Party

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: All the group connections of the Party

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Prefix] rdf: [Description] The RDF Vocabulary [URI]

Semantic Web Applications in Neuromedicine (SWAN) Ontology


Input: [Prefix] rdfs: [Description] The RDF Schema vocabulary [URI]

Semantic Web Applications in Neuromedicine (SWAN) Ontology


Input: [Prefix] xsd: [Description] XML Schema [URI]

Semantic Web Applications in Neuromedicine (SWAN) Ontology


Input: [Prefix] foaf: [Description] Friend Of A Friend [URI]

Semantic Web Applications in Neuromedicine (SWAN) Ontology


Input: [Prefix] skos: [Description] Simple Knowledge Organization System [URI]

Semantic Web Applications in Neuromedicine (SWAN) Ontology


Input: [Prefix] dc: [Description] Dublin Core Metadata Element Set, Version 1.1 [URI]

Semantic Web Applications in Neuromedicine (SWAN) Ontology


Input: [Prefix] dcterms: [Description] Dublin Core Metadata Terms [URI]

Semantic Web Applications in Neuromedicine (SWAN) Ontology


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

Output: acceptTracking

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: attribute

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: compensate

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: delete

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: ensureExclusivity

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: include

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: inform

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: nextPolicy

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: obtainConsent

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: reviewPolicy

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: uninstall

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: watermark

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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


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

Output: List of bad links in the page


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

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


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

Output: List of HTML markup errors.


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

Output: List of spelling errors.


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

Output: List of style CSS errors.


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

Output: Log of changes to the document


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

Output: HTTP headers sent by the server


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

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


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

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


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

Output: Individual

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Group

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: All

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: AllConnections

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: All2ndConnections

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: AllGroups

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] Individual [Comment] Must be supported. [Semantics]

Output: The Party is a single individual

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] Group [Comment] Must be supported. [Semantics]

Output: The Party represents a defined group with multiple individual members

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: All the collective individuals within a context

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: All the first-level connections of the Party

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: All the second-level connections of the Party

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: All the group connections of the Party

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Alignment of event codes and content items

Table 2-3. EXI Options


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

Output: Indicates if EXI compression is to be used for better compactness

Table 2-3. EXI Options


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

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

Table 2-3. EXI Options


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

Output: Indicates if the body is to be encoded as an EXI fragment instead of an EXI document

Table 2-3. EXI Options


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

Output: A set of options that controls whether comments, processing instructions, etc. are preserved

Table 2-3. EXI Options


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

Output: Enables self-contained elements. Self-contained elements may be read independently from the rest of the EXI body

Table 2-3. EXI Options


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

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

Table 2-3. EXI Options


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

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

Table 2-3. EXI Options


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

Output: Specifies the number of Attribute (AT) and Character (CH) values for each block used for EXI compression

Table 2-3. EXI Options


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

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

Table 2-3. EXI Options


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

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

Table 2-3. EXI Options


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

Output: User defined options may be added

Table 2-3. EXI Options


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

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


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] eq [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] gt [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] gteq [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] hasPart [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] isA [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] isAllOf [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] isAnyOf [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] isNoneOf [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] isPartOf [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] lt [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] lteq [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] neq [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] acceptTracking [Semantics] The Assigner requires that the Assignee(s) accepts that the use of the Asset may be tracked [Comment]

Output: The collected information may be tracked by the Assigner, or may link to a Party with the role function “trackingParty”.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] attribute [Semantics] The Assigner requires that the Assignee(s) attributes the Asset to the Assigner or an attributed Party. [Comment]

Output: May link to an Asset with the attribution information. May link to a Party with the role function “attributedParty”.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] compensate [Semantics] The Assigner requires that the Assignee(s) compensates the Assigner (or other specified compensation Party) by some amount of value, if defined, for use of the Asset. [Comment]

Output: The compensation may use different types of things with a value: – the thing is expressed by the value (term) of the Constraint name – the value is expressed by operator, rightOperand, dataType and unit

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] delete [Semantics] The Assigner requires that the Assignee(s) permanently removes all copies of the Asset. [Comment]

Output: Use a constraint to define under which conditions the Asset should be deleted.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] include [Semantics] The Assigner requires that the Assignee(s) include(s) other related assets in the Asset. [Comment]

Output: For example; Bio picture must be included in the attribution. Use of the Asset relation attribute is required

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] inform [Semantics] The Assigner requires that the Assignee(s) inform(s) the Assigner or an informed Party that an action has been performed on or in relation to the Asset. [Comment]

Output: May link to a Party with the role function “informedParty”.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] obtainConsent [Semantics] The Assigner requires that the Assignee(s) obtains explicit consent from the Assigner or a consenting Party to perform the requested action in relation to the Asset. [Comment]

Output: Used as a Duty to ensure that the Assigner or a Party is authorized to approve such actions on a case-by-case basis. May link to a Party with the role function “consentingParty”.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] reviewPolicy [Semantics] The Assigner requires that the Assignee(s) has(ve) a person review the Policy applicable to the Asset. [Comment]

Output: Used when human intervention is required to review the Policy. May link to an Asset which represents the full Policy information.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: The Asset is no longer accessible to the Assignee(s).

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: It is recommended to embed a link to the watermark.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: alignment

EXI Options in Options Field


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

Output: compression

EXI Options in Options Field


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

Output: strict

EXI Options in Options Field


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

Output: fragment

EXI Options in Options Field


Input: [Description] Specifies whether comments, pis, etc. are preserved [Default Value] all false [EXI Option]

Output: preserve

EXI Options in Options Field


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

Output: schemaID

EXI Options in Options Field


Input: [Description] Identify pluggable CODECs used to encode body [Default Value] none [EXI Option]

Output: codecMap

EXI Options in Options Field


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

Output: blockSize

EXI Options in Options Field


Input: [Description] User defined headers may be added [Default Value] none [EXI Option]

Output: [user defined]

EXI Options in Options Field


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

Output: Individual

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Group

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: All

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: AllConnections

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: All2ndConnections

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: AllGroups

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Detail] An attempt was made to select an element that cannot be selected. [Status Code]

Output: element not selectable


Input: [Detail] An element command could not be completed because the element is not visible on the page. [Status Code]

Output: element not visible


Input: [Detail] An IME engine could not be started. [Status Code]

Output: ime engine activation failed


Input: [Detail] IME was not available. [Status Code]

Output: ime not available


Input: [Detail] An illegal attempt was made to set a cookie under a different domain than the current page. [Status Code]

Output: invalid cookie domain


Input: [Detail] The coordinates provided to an interactions operation are invalid. [Status Code]

Output: invalid element coordinates


Input: [Detail] An element command could not be completed because the element is in an invalid state (e.g. attempting to click an element that is no longer attached to the DOM). [Status Code]

Output: invalid element state


Input: [Detail] Argument was an invalid selector (e.g. XPath/CSS). [Status Code]

Output: invalid selector


Input: [Detail] An error occurred while executing user supplied JavaScript. [Status Code]

Output: javascript error


Input: [Detail] The target for mouse interaction is not in the browser's viewport and cannot be brought into that viewport. [Status Code]

Output: move target out of bounds


Input: [Detail] An attempt was made to operate on a modal dialog when one was not open. [Status Code]

Output: no such alert


Input: [Detail] An attempt was made to switch to a hosted Shadow DOM that does not exist. [Status Code]

Output: no such dom


Input: [Detail] An element could not be located on the page using the given search parameters. [Status Code]

Output: no such element


Input: [Detail] A request to switch to a frame could not be satisfied because the frame could not be found. [Status Code]

Output: no such frame


Input: [Detail] A request to switch to a different window could not be satisfied because the window could not be found. [Status Code]

Output: no such window


Input: [Detail] A script did not complete before its timeout expired. [Status Code]

Output: script timeout


Input: [Detail] A new session could not be created. [Status Code]

Output: session not created


Input: [Detail] An element command failed because the referenced element is no longer attached to the DOM. [Status Code]

Output: stale element reference


Input: [Detail] The command executed successfully. [Status Code]

Output: success


Input: [Detail] An operation did not complete before its timeout expired. [Status Code]

Output: timeout


Input: [Detail] A request to set a cookie's value could not be satisfied. [Status Code]

Output: unable to set cookie


Input: [Detail] A modal dialog was open, blocking this operation. [Status Code]

Output: unexpected alert open


Input: [Detail] A command could not be executed because the remote end is not aware of it. [Status Code]

Output: unknown command


Input: [Detail] An unknown error occurred in the remote end while processing the command. [Status Code]

Output: unknown error


Input: [Detail] Indicates that a command that should have executed properly cannot be supported for some reason. [Status Code]

Output: unsupported operation


Input: [Responder] Sharron Rush

Output: I support publishing these Training pages as they are

Results of Questionnaire EOWG Review: Training Resource Suite - Web-Based Straw-poll and Balloting System

Support for publishing and announcing the pages as drafts for public review


Input: [Responder] Andrew Arch

Output: I support publishing these Training pages as they are

Results of Questionnaire EOWG Review: Training Resource Suite - Web-Based Straw-poll and Balloting System

Support for publishing and announcing the pages as drafts for public review


Input: [Responder] Wayne Dick

Output: I support publishing these Training pages as they are

Results of Questionnaire EOWG Review: Training Resource Suite - Web-Based Straw-poll and Balloting System

Support for publishing and announcing the pages as drafts for public review


Input: [Responder] Suzette Keith

Output: I support publishing these Training pages as they are

Results of Questionnaire EOWG Review: Training Resource Suite - Web-Based Straw-poll and Balloting System

Support for publishing and announcing the pages as drafts for public review


Input: [Responder] Jennifer Sutton

Output: I support publishing these Training pages as they are

Results of Questionnaire EOWG Review: Training Resource Suite - Web-Based Straw-poll and Balloting System

Support for publishing and announcing the pages as drafts for public review


Input: [Responder] Shadi Abou-Zahra

Output: I support publishing these Training pages; however, I suggest the changes in the comments sections below (for editors' discretion)

Results of Questionnaire EOWG Review: Training Resource Suite - Web-Based Straw-poll and Balloting System

Support for publishing and announcing the pages as drafts for public review


Input: [Responder] Ian Pouncey

Output: I support publishing these Training pages as they are

Results of Questionnaire EOWG Review: Training Resource Suite - Web-Based Straw-poll and Balloting System

Support for publishing and announcing the pages as drafts for public review


Input: [Responder] Vicki Menezes Miller

Output: I support publishing these Training pages as they are

Results of Questionnaire EOWG Review: Training Resource Suite - Web-Based Straw-poll and Balloting System

Support for publishing and announcing the pages as drafts for public review


Input: [Responder] Emmanuelle Gutiérrez y Restrepo

Output: I support publishing these Training pages as they are

Results of Questionnaire EOWG Review: Training Resource Suite - Web-Based Straw-poll and Balloting System

Support for publishing and announcing the pages as drafts for public review


Input: [Responder] Sylvie Duchateau

Output: I support publishing these Training pages; however, I suggest the changes in the comments sections below (for editors' discretion)

Results of Questionnaire EOWG Review: Training Resource Suite - Web-Based Straw-poll and Balloting System

Support for publishing and announcing the pages as drafts for public review


Input: [Identifier] acceptTracking [Semantics] The Assigner requires that the Assignee(s) accepts that the use of the Asset may be tracked [Comment]

Output: The collected information may be tracked by the Assigner, or may link to a Party with the role function “trackingParty”.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] attribute [Semantics] The Assigner requires that the Assignee(s) attributes the Asset to the Assigner or an attributed Party. [Comment]

Output: May link to an Asset with the attribution information. May link to a Party with the role function “attributedParty”.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] compensate [Semantics] The Assigner requires that the Assignee(s) compensates the Assigner (or other specified compensation Party) by some amount of value, if defined, for use of the Asset. [Comment]

Output: The compensation may use different types of things with a value: – the thing is expressed by the value (term) of the Constraint name – the value is expressed by operator, rightOperand, dataType and unit

ODRL Version 2.1 Common Vocabulary | ODRL Community Group