Input: [1] Necessary text has been omitted from the localization or source. [2] One or more segments found in the source that should have been translated are missing in the target. [3] S or T [4] This type should not be used for missing whitespace or formatting codes, but instead should be reserved for linguistic content. [0]

Output: omission

Internationalization Tag Set (ITS) Version 2.0


Input: [1] Content that should have been translated was left untranslated. [2] The source segment reads "The Professor said to Smith that he would hear from his lawyer" but the Hungarian localization reads "A professzor azt modta Smithnek, hogy he would hear from his lawyer." [3] T [4] omission takes precedence over untranslated. Omissions are distinct in that they address cases where text is not present, while untranslated addresses cases where text has been carried from the source untranslated. [0]

Output: untranslated

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The translated text contains inappropriate additions. [2] The translated text contains a note from the translator to himself to look up a term; the note should have been deleted but was not. [3] T [0]

Output: addition

Internationalization Tag Set (ITS) Version 2.0


Input: [1] Content has been duplicated improperly. [2] A section of the target text was inadvertently copied twice in a copy and paste operation. [3] T [0]

Output: duplication

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text is inconsistent with itself (NB: not for use with terminology inconsistency). [2] The text states that an event happened in 1912 in one location but in another states that it happened in 1812. [3] S or T [0]

Output: inconsistency

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text contains a grammatical error (including errors of syntax and morphology). [2] The text reads "The guidelines says that users should use a static grounding strap." [3] S or T [0]

Output: grammar

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text is legally problematic (e.g., it is specific to the wrong legal system). [2] The localized text is intended for use in Thailand but includes U.S. regulatory notices. A text translated into German contains comparative advertising claims that are not allowed by German law. [3] S or T [0]

Output: legal

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text is written in the wrong linguistic register of uses slang or other language variants inappropriate to the text. [2] A financia text in U.S. English refers to dollars as "bucks". [3] S or T [0]

Output: register

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The localization contains content that does not apply to the locale for which it was prepared. [2] A text translated for the Japanese market contains call center numbers in Texas and refers to special offers available only in the U.S. [3] S or T [4] Legally inappropriate material should be classified as legal. [0]

Output: locale-specific-content

Internationalization Tag Set (ITS) Version 2.0


Input: [1] Text violates norms for the intended locale. [2] A text localized into German has dates in YYYY-MM-DD format instead of in DD.MM.YYYY. A text for the Irish market uses American-style foot and inch measurements instead of centimeters. [3] S or T [0]

Output: locale-violation

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text contains stylistic errors. [2] Company style guidelines dictates that all individuals be referred to as Mr. or Ms. with a family name, but the text refers to “Jack Smith”. [3] S or T [0]

Output: style

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text contains characters that are garbled or incorrect or that are not used in the language in which the content appears. [2] A text should have a '•' but instead has a '¥' sign. A text translated into German omits the umlauts over 'ü', 'ö', and 'ä'. [3] S or T [0]

Output: characters

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text contains a misspelling. [2] A German text misspells the word "Zustellung" as "Zustellüng". [3] S or T [0]

Output: misspelling

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text has typographical errors such as omitted/incorrect punctuation, incorrect capitalization, etc. [2] An English text has the following sentence: "The man whom, we saw, was in the Military and carried it's insignias". [3] S or T [0]

Output: typographical

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text is formatted incorrectly. [2] Warnings in the text are supposed to be set in italic face, but instead appear in bold face. Margins of the text are narrower than specified. [3] S or T [0]

Output: formatting

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The source and target text contain different named entities (dates, times, place names, individual names, etc.) [2] The name "Thaddeus Cahill" appears in an English source but is rendered as "Tamaš Cahill" in the Czech version. The date "February 9, 2007" appears in the source but the translated text has "2. September 2007". [3] S or T [0]

Output: inconsistent-entities

Internationalization Tag Set (ITS) Version 2.0


Input: [1] Numbers are inconsistent between source and target. [2] A source text states that an object is 120 cm long, but the target text says it is 129 cm. long. [3] S or T [4] Some tools may correct for differences in units of measurement to reduce false positives. [0]

Output: numbers

Internationalization Tag Set (ITS) Version 2.0


Input: [1] There is an issue related to markup or a mismatch in markup between source and target. [2] The source segment has five markup tags but the target has only two. An opening tag in the text is missing a closing tag. [3] S or T [0]

Output: markup

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text fails to match a pattern that defines allowable content (or matches one that defines non-allowable content). [2] The tool disallows the regular expression pattern ['"”’][\.,] but the translated text contains "A leading “expert”, a political hack, claimed otherwise." [3] S or T [0]

Output: pattern-problem

Internationalization Tag Set (ITS) Version 2.0


Input: [1] There is a mismatch in whitespace between source and target content. [2] A source segment starts with six space characters but the corresponding target segment has two non-breaking spaces at the start. [3] S or T [0]

Output: whitespace

Internationalization Tag Set (ITS) Version 2.0


Input: [1] There is an issue related to the internationalization of content. [2] A line of programming code has embedded language-specific strings. A user interface element leaves no room for text expansion. A form allows only for U.S.-style postal addresses and expects five digit U.S. ZIP codes. [3] S or T [4] There are many kinds of internationalization issues. This category is therefore very heterogeneous in what it can refer to. [0]

Output: internationalization

Internationalization Tag Set (ITS) Version 2.0


Input: [1] There is a significant difference in source and target length. [2] The translation of a segment is five times as long as the source. [3] T or S [4] What constitutes a "significant" difference in length is determined by the model referred to in the locQualityIssueProfileRef. [0]

Output: length

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The issue has not been categorized. [2] A new version of a tool returns information on an issue that has not been previously checked and that is not yet classified. [3] S or T [4] This category has two uses: A tool can use it to pass through quality data from another tool in cases where the issues from the other tool are not classified (for example, a localization quality assurance tool interfaces with a third-party grammar checker). A tool's issues are not yet assigned to categories, and, until an updated assignment is made, they may be listed as uncategorized. In this case it is recommended that issues be assigned to appropriate categories as soon as possible since uncategorized does not foster interoperability. [0]

Output: uncategorized

Internationalization Tag Set (ITS) Version 2.0


Input: [1] Any issue that cannot be assigned to any values listed above. [3] S or T [4] This category allows for the inclusion of any issues not included in the previously listed values. This value MUST NOT be used for any tool- or model-specific issues that can be mapped to the values listed above. In addition, this value is not synonymous with uncategorized in that uncategorized issues may be assigned to another precise value, while other issues cannot. If a system has an "miscellaneous" or "other" category, it MUST be mapped to this value even if the specific instance of the issue might be mapped to another category. [0]

Output: other

Internationalization Tag Set (ITS) Version 2.0


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


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


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

Output: Based on effectAllowed value


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


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

Output: Based on effectAllowed value


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

Output: Current drag operation


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

Output: Current drag operation


Input: [Target] controller [Sequencing] one-of: prepared, notPrepared [Description] positive response to prepare (activeGrammars or activeVoiceModel prepared) [Event]

Output: prepared

Voice Extensible Markup Language (VoiceXML) 3.0

Table 7: Events sent by recognition resource


Input: [Target] controller [Sequencing] one-of: prepared, notPrepared [Description] negative response to prepare (no activeGrammars or activeVoiceModel defined) [Event]

Output: notPrepared

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Target] controller [Description] notification that onset of input has been detected [Event]

Output: inputStarted

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Target] controller [Description] notification that the end of input has been detected [Event]

Output: inputFinished

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Target] controller [Payload] results (M), listener (O) [Description] notification of a partial recognition result [Event]

Output: partialResult

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Target] controller [Payload] results (M), listener (O) [Description] notification of complete recognition result, including the results structure and a listener [Event]

Output: recoResult

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Target] controller [Payload] error status (M) [Description] notification that an error has occurred [Event]

Output: error

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Commentor] LC-1978 Dominique Hazael-Massieux (archived comment) [Comment] * when analyzing external resources (in ContentFormatSupport, PageSizeLimit, ExternalResources), the objects and images that are set as fallback of an object that is in an acceptable format shouldn't be counted. For instance, shouldn't trigger an error in ContentFormatSupport, the weight of myimage.png shouldn't be counted in PageSizeLimit and ExternalResources [Commentor reply] yes [Working Group decision]

Output: We agree that the "myimage.png" should not trigger a CONTENT_FORMAT_SUPPORT error, and should not be taken into account in PAGE_SIZE_LIMIT and EXTERNAL_RESOURCES. This is triggered by the note in 2.4.6 Included Resources: "object elements that are accessed in order to test their Content-Type HTTP header, but do not form part of the ultimate representation of the resource under test (see 3.15 OBJECTS_OR_SCRIPT ), are not considered to be included resources". We agree that the notion of "ultimate representation of the resource" deserves to be clarified though and the note extended to resources retrieved by section 3.15.1 Object Element Processing Rule. On the light of the discussion that followed your other comment (LC-1980) on the use of the HTTP Content-Type value to taste object element, we updated the note to specify that only resources retrieved under the 3.15.1 Object Element Processing Rule whose Content-Type is image/gif or image/jpeg are considered to be Included Resources: http://www.w3.org/2005/MWI/BPWG/Group/Drafts/mobileOK-Basic-1.0-Tests/080707r#included_resources

mobileOK Basic Tests 1.0 - Disposition of comments


Input: [Commentor] LC-1979 Dominique Hazael-Massieux (archived comment) [Comment] * similarly, I don't think we want to raise a ContentFormatSupport error on since this is using correctly the fallback mechanism; while this gets accepted by ObjectsOrScript, this would currently raise an error in the way I read ContentFormatSupport; [Commentor reply] yes [Working Group decision]

Output: We agree that the example should not raise a FAIL in CONTENT_FORMAT_SUPPORT, because "myimage.png" does not form part of the ultimate representation of the resource under test, as noted in 2.4.6 Included Resources. We clarified the note in 2.4.6 Included Resources as noted in our reply to your previous comment (LC-1978) on the need to clarify which objects and images are Included Resources, and which are not.

mobileOK Basic Tests 1.0 - Disposition of comments


Input: [Commentor] LC-1980 Dominique Hazael-Massieux (archived comment) [Comment] * I don't think "myimage.gif" should be counted as external resources/page size limit in the following instance: Hello - the current text says to "include those objects whose content type is either "image/jpeg" or "image/gif" irrespective of whether the type attribute is specified.", but it's not clear why. [Commentor reply] yes [Working Group decision]

Output: We understand that point, but note that there is not a real consistency in the way such objects are handled by mobile browsers in practice. Some browsers download all the objects and use the HTTP Content-Type header irrespective of the presence of the type attribute, while other browsers follow the type attribute and only download objects that match values of the HTTP Accept header. We think Content Providers should "benefit" (or rather should not be "punished") for this lack of consistency in mobile browsers, and decided, in the interest of returning fewer FAIL messages: 1/ to stick to the HTTP Content-Type header to determine whether an object is rendered or the fallback mechanism has to be used. 2/ to stick to our decision not to count objects that define a type attribute not set to image/gif or image/jpeg in PAGE_SIZE_LIMIT and EXTERNAL_RESOURCES. However, since we recognize that the corresponding behavior among mobile browsers is not consistent, that it is a bad practice to have a type attribute that does not match the Content-Type of the underlying resource and that it is a good practice to define the type attribute, we also introduced two additional warning messages: "If there is no type attribute, warn" "If the Internet media type of the retrieved resource, as indicated by its Content-Type HTTP header does not match that stated in the type attribute, warn" We note that our decision introduces a slight inconsistency in the way objects are treated by the specification: on the one hand, section 3.15.1 Object Element Processing Rule says that the Object must be retrieved so that the HTTP Content-Type header may be parsed, on the other hand, section 3.16 PAGE_SIZE_LIMIT (resp. 3.6 EXTERNAL_RESOURCES) says that an object defined with a type attribute set to image/png does not count as a retrieved resource (provided its actual Content-Type is not image/gif or image/jpeg). We think that it is needed though for the above mentioned reasons.

mobileOK Basic Tests 1.0 - Disposition of comments


Input: [Commentor] LC-1981 Dominique Hazael-Massieux (archived comment) [Comment] * if I hit an HTTP redirect, does the size of the page served as the redirect page counts in PAGE_SIZE_LIMIT-1 or only under PAGE_SIZE_LIMIT-2? I've implemented the latter since I find it less confusing, but the spec could be clearer about it [Commentor reply] yes [Working Group decision]

Output: Yes, we agree that the text here deserved to be clarified. We updated the text consequently: - Section 3.16 PAGE_SIZE_LIMIT was clarified with regards to the treatment of HTTP response bodies that are required to retrieve a resource: http://www.w3.org/2005/MWI/BPWG/Group/Drafts/mobileOK-Basic-1.0-Tests/080707r#PAGE_SIZE_LIMIT - Section 2.4.3 HTTP Response was also amended to have the reader refer to 3.16 PAGE_SIZE_LIMIT (resp. 3.6 EXTERNAL_RESOURCES) for details of the total size (resp. count) the HTTP redirect response body should be added to: http://www.w3.org/2005/MWI/BPWG/Group/Drafts/mobileOK-Basic-1.0-Tests/080707r#http_response

mobileOK Basic Tests 1.0 - Disposition of comments


Input: [Commentor] LC-1991 Francois Daoust (archived comment) [Comment] * About the treatment of HTTP Status 401: - Why should tests be applied to the response body of such an HTTP response? The body will never be touched by any browser during the first pass (when authentication credentials have not already been sent) AFAICT. Besides, it wouldn't make any sense to display the resource if it's an included image for instance. It's perfectly normal to count the response in EXTERNAL_RESPONSE and PAGE_SIZE_LIMIT, but I suggest updating the "Carry out tests on the response" to "Do not carry out tests on the response", especially given the fact that the tests FAIL when credentials are wrong (and so there's no need to test the response body anyway even for the second pass) - "Re-request the resource using authentication information" could deserve some clarification. What if the checker doesn't have any authentication information? I would clarify this with "Re-request the resource using authentication information if available or FAIL" (where FAIL would be HTTP_RESPONSE-7) [Commentor reply] yes [Working Group decision]

Output: On your first point, we think that the tests should be carried on the response body because, as specified in the HTTP (RFC 2616) section 10.4.2 401 Unauthorized, the body of the HTTP Status 401 response should be presented to the user if the authentication fails: "If the 401 response contains the same challenge as the prior response, and the user agent has already attempted authentication at least once, then the user SHOULD be presented the entity that was given in the response, since that entity might include relevant diagnostic information" On your second point, we think that the text deserved to be clarified and updated the relevant part to state: "If authentication information was supplied in the HTTP request (i.e. authentication failed) or if no authentication information is available, FAIL" See: http://www.w3.org/2005/MWI/BPWG/Group/Drafts/mobileOK-Basic-1.0-Tests/080707r#http_response

mobileOK Basic Tests 1.0 - Disposition of comments


Input: [Commentor] LC-1992 Francois Daoust (archived comment) [Comment] * HTTP responses and linked resources: I understand the LINK_TARGET_FORMAT test as willing to return WARNs to the user on linked resources, and to never return any FAIL. However, there are several cases in the tests that should be carried by the checker for HTTP responses that return a FAIL, even when the resource is a linked resource: - "If an HTTP request does not result in a valid HTTP response [...], FAIL" - 1 case in "If the response is an HTTPS response" - 2 cases in "If the HTTP status indicates redirection" - "If the HTTP status represents failure (4xx), other than 404 or a request for authentication (e.g. 401), FAIL" I guess one may argue that LINK_TARGET_FORMAT may return a FAIL message. The last point still stands in that case: is a linked resource that returned a 406 Not Acceptable status supposed to trigger a FAIL? I think I should be allowed to include links to external resources that are not able to serve content to the mobileOK checker in a page without losing the possibility for the page to be mobileOK. I would relax the last check to state: "If the HTTP status represents failure (4xx), other than 404 or a request for authentication (e.g. 401): If the response relates to a request for a linked resource (see 2.4.7 Linked Resources), continue with the test (see 3.10 LINK_TARGET_FORMAT ) and warn Otherwise (i.e. for included resources), FAIL" [Commentor reply] yes [Working Group decision]

Output: Links in a Web page intended for mobile consumption are an important constituent of the user experience. The user should be able to "trust" that clicking on a link does not yield an error message. For that reason, we think that returning FAILs in the LINK_TARGET_FORMAT is indeed needed. However, it occurred to us that HTTP Status 406 responses could well be returned for resources tasted by section 3.15.1 Object Element Processing Rule, and that this should obviously not trigger a FAIL, so we relaxed that last condition in that case as you suggested: http://www.w3.org/2005/MWI/BPWG/Group/Drafts/mobileOK-Basic-1.0-Tests/080707r#http_response

mobileOK Basic Tests 1.0 - Disposition of comments


Input: [Commentor] LC-2159 Thomas Roessler on behalf of Web Security Context Working Group (archived comment) [Comment] Hello, this is a post last call comment concerning the mobile OK basic tests 1.0, on behalf of the Web Security Context Working Group. We notice that section 2.4.3 - HTTP Response - uses the notion of an "HTTPS response". There is no such thing. We also notice that the notion of an "invalid certificate" does not match what we understand to be the Best Practice Working Group's intention with this test. We propose that you update this criterion, at a minimum, as follows: If the resource is accessed through HTTPS: If the certificate presented does not match the resource's URI, FAIL. If the certificate has expired or is not yet valid, warn. If certificate validation otherwise fails, FAIL. Checker SHOULD consider arbitrary root certificates (including self-signed certificates) as trusted for the purposes of mobileOK testing. Note that there are additional error conditions that can occur during TLS negotiation, including a mismatch on supported algorithms and protocol versions. Regards, [Commentor reply] yes [Working Group decision]

Output: We added a section on HTTPS that refines the algorithm of determining an invalid https certificate.

mobileOK Basic Tests 1.0 - Disposition of comments


Input: [Category] Navigation and Click-stream Data [Type] text [Short display name] Click-stream collected on the client [dynamic]

Output: clickstream.client


Input: [Category] Navigation and Click-stream Data [Type] text [Short display name] Click-stream collected on the server [dynamic]

Output: clickstream.server


Input: [Category] (variable-category) [Type] text [Short display name] Cookies are processed (read/write) [dynamic]

Output: cookies


Input: [Category] Computer Information [Type] text [Short display name] User Agent information [dynamic]

Output: http.useragent


Input: [Category] Navigation and Click-stream Data [Type] uri [Short display name] Last URI requested by the user [dynamic]

Output: http.referrer


Input: [Category] (variable-category) [Type] text [Short display name] Miscellaneous non-base data schema information [dynamic]

Output: miscdata


Input: [Category] Interactive Data [Type] text [Short display name] Search terms [dynamic]

Output: searchtext


Input: [Category] Interactive Data [Type] text [Short display name] Server stores the transaction history [dynamic]

Output: interactionrecord


Input: [Postal.] Name. [Type] PersonName. [Short display name] Name [Category]

Output: Physical Contact Information, Demographic and SocioEconomic Data


Input: [Postal.] Street [Type] Text [Short display name] Street Address [Category]

Output: Physical Contact Information


Input: [Postal.] City [Type] Text [Short display name] City [Category]

Output: Physical Contact Information


Input: [Postal.] StateProv [Type] Text [Short display name] State or Province [Category]

Output: Physical Contact Information


Input: [Postal.] PostalCode [Type] Text [Short display name] Postal Code [Category]

Output: Demographic and SocioEconomic Data


Input: [Postal.] CountryCode [Type] Country [Short display name] Country [Category]

Output: Demographic and SocioEconomic Data


Input: [Postal.] Country [Type] Text [Short display name] Country String [Category]

Output: Demographic and SocioEconomic Data


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

Output: dragstart


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

Output: drag


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

Output: dragenter


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

Output: dragleave


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

Output: dragover


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

Output: drop


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

Output: dragend


Input: [Name] initial [Attribute Constraints] none [Type] IDREFS [Default Value] none [Valid Values] A legal state specification. See 3.11 Legal State Configurations and Specifications for details. [Description] The id of the initial state(s) for the document. If not specified, the default initial state is the first child state in document order. [Required]

Output: false

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [Name] name [Attribute Constraints] none [Type] NMTOKEN [Default Value] none [Valid Values] Any valid NMTOKEN [Description] The name of this state machine. It is for purely informational purposes. [Required]

Output: false

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [Name] xmlns [Attribute Constraints] none [Type] URI [Default Value] none [Valid Values] The value must MUST be "http://www.w3.org/2005/07/scxml". [Required]

Output: true

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [Name] version [Attribute Constraints] none [Type] decimal [Default Value] none [Valid Values] The only legal value is MUST be "1.0" [Required]

Output: true

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [Name] datamodel [Attribute Constraints] none [Type] NMTOKEN [Default Value] "none" platform-specific [Valid Values] "none", "null", "ecmascript", "xpath" or other platform-defined values. [Description] The datamodel that this document requires. "none" "null" denotes the Empty Null datamodel, "ecmascript" the ECMAScript datamodel, and "xpath" the XPath datamodel, as defined in D Data Models . [Required]

Output: false

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [Name] binding [Type] enum [Default Value] "early" [Valid Values] "early", "late" [Description] The data binding to use. See 5.3.3 Data Binding and Scoping for details. [Required]

Output: false

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [Name] exmode [Type] enum [Default Value] "lax" [Valid Values] "lax", "strict" [Description] Determines whether the processor should silently ignore markup that it does not support. [Required]

Output: false

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [For this page] A plain text version of the page, handy for pasting into email. [,shortcut] ,text [Access control] Same as the document [General tool]

Output: HTML to Text converter


Input: [For this page] List of bad links in the page [,shortcut] ,checklink [Access control] Same as the document [General tool]

Output: Link Checker


Input: [For this page] Bad links in a page and in pages linked from it [,shortcut] ,rchecklink [Access control] Same as the document [General tool]

Output: Link Checker


Input: [For this page] List of HTML markup errors. [,shortcut] ,validate [Access control] Same as the document [General tool]

Output: HTML Validator


Input: [For this page] List of spelling errors. [,shortcut] ,spell [Access control] Same as the document [General tool]

Output: W3C Spellchecker


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

Output: CSS Validator


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

Output: CVS Log


Input: [For this page] HTTP headers sent by the server [,shortcut] ,headers [Access control] Same as the document [General tool]

Output: Headers


Input: [For this page] Check the compliance of this document to the W3C publication rules [,shortcut] ,pubrules [Access control] Same as the document [General tool]

Output: the pubrules checker


Input: [For this page] Check the compliance of this document to the W3C publication rules, only displaying errors [,shortcut] ,pubruleserrors [Access control] Same as the document [General tool]

Output: the pubrules checker


Input: [Event] prepared [Target] controller [Sequencing] one-of: prepared, notPrepared [Description]

Output: positive response to prepare (activeGrammars or activeVoiceModel prepared)

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Event] notPrepared [Target] controller [Sequencing] one-of: prepared, notPrepared [Description]

Output: negative response to prepare (no activeGrammars or activeVoiceModel defined)

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Event] inputStarted [Target] controller [Description]

Output: notification that onset of input has been detected

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Event] inputFinished [Target] controller [Description]

Output: notification that the end of input has been detected

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Event] partialResult [Target] controller [Payload] results (M), listener (O) [Description]

Output: notification of a partial recognition result

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Event] recoResult [Target] controller [Payload] results (M), listener (O) [Description]

Output: notification of complete recognition result, including the results structure and a listener

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Event] error [Target] controller [Payload] error status (M) [Description]

Output: notification that an error has occurred

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Commentor] LC-1978 Dominique Hazael-Massieux (archived comment) [Working Group decision] We agree that the "myimage.png" should not trigger a CONTENT_FORMAT_SUPPORT error, and should not be taken into account in PAGE_SIZE_LIMIT and EXTERNAL_RESOURCES. This is triggered by the note in 2.4.6 Included Resources: "object elements that are accessed in order to test their Content-Type HTTP header, but do not form part of the ultimate representation of the resource under test (see 3.15 OBJECTS_OR_SCRIPT ), are not considered to be included resources". We agree that the notion of "ultimate representation of the resource" deserves to be clarified though and the note extended to resources retrieved by section 3.15.1 Object Element Processing Rule. On the light of the discussion that followed your other comment (LC-1980) on the use of the HTTP Content-Type value to taste object element, we updated the note to specify that only resources retrieved under the 3.15.1 Object Element Processing Rule whose Content-Type is image/gif or image/jpeg are considered to be Included Resources: http://www.w3.org/2005/MWI/BPWG/Group/Drafts/mobileOK-Basic-1.0-Tests/080707r#included_resources [Commentor reply] yes [Comment]

Output: * when analyzing external resources (in ContentFormatSupport, PageSizeLimit, ExternalResources), the objects and images that are set as fallback of an object that is in an acceptable format shouldn't be counted. For instance, shouldn't trigger an error in ContentFormatSupport, the weight of myimage.png shouldn't be counted in PageSizeLimit and ExternalResources

mobileOK Basic Tests 1.0 - Disposition of comments


Input: [Commentor] LC-1979 Dominique Hazael-Massieux (archived comment) [Working Group decision] We agree that the example should not raise a FAIL in CONTENT_FORMAT_SUPPORT, because "myimage.png" does not form part of the ultimate representation of the resource under test, as noted in 2.4.6 Included Resources. We clarified the note in 2.4.6 Included Resources as noted in our reply to your previous comment (LC-1978) on the need to clarify which objects and images are Included Resources, and which are not. [Commentor reply] yes [Comment]

Output: * similarly, I don't think we want to raise a ContentFormatSupport error on since this is using correctly the fallback mechanism; while this gets accepted by ObjectsOrScript, this would currently raise an error in the way I read ContentFormatSupport;

mobileOK Basic Tests 1.0 - Disposition of comments


Input: [Commentor] LC-1980 Dominique Hazael-Massieux (archived comment) [Working Group decision] We understand that point, but note that there is not a real consistency in the way such objects are handled by mobile browsers in practice. Some browsers download all the objects and use the HTTP Content-Type header irrespective of the presence of the type attribute, while other browsers follow the type attribute and only download objects that match values of the HTTP Accept header. We think Content Providers should "benefit" (or rather should not be "punished") for this lack of consistency in mobile browsers, and decided, in the interest of returning fewer FAIL messages: 1/ to stick to the HTTP Content-Type header to determine whether an object is rendered or the fallback mechanism has to be used. 2/ to stick to our decision not to count objects that define a type attribute not set to image/gif or image/jpeg in PAGE_SIZE_LIMIT and EXTERNAL_RESOURCES. However, since we recognize that the corresponding behavior among mobile browsers is not consistent, that it is a bad practice to have a type attribute that does not match the Content-Type of the underlying resource and that it is a good practice to define the type attribute, we also introduced two additional warning messages: "If there is no type attribute, warn" "If the Internet media type of the retrieved resource, as indicated by its Content-Type HTTP header does not match that stated in the type attribute, warn" We note that our decision introduces a slight inconsistency in the way objects are treated by the specification: on the one hand, section 3.15.1 Object Element Processing Rule says that the Object must be retrieved so that the HTTP Content-Type header may be parsed, on the other hand, section 3.16 PAGE_SIZE_LIMIT (resp. 3.6 EXTERNAL_RESOURCES) says that an object defined with a type attribute set to image/png does not count as a retrieved resource (provided its actual Content-Type is not image/gif or image/jpeg). We think that it is needed though for the above mentioned reasons. [Commentor reply] yes [Comment]

Output: * I don't think "myimage.gif" should be counted as external resources/page size limit in the following instance: Hello - the current text says to "include those objects whose content type is either "image/jpeg" or "image/gif" irrespective of whether the type attribute is specified.", but it's not clear why.

mobileOK Basic Tests 1.0 - Disposition of comments


Input: [Commentor] LC-1981 Dominique Hazael-Massieux (archived comment) [Working Group decision] Yes, we agree that the text here deserved to be clarified. We updated the text consequently: - Section 3.16 PAGE_SIZE_LIMIT was clarified with regards to the treatment of HTTP response bodies that are required to retrieve a resource: http://www.w3.org/2005/MWI/BPWG/Group/Drafts/mobileOK-Basic-1.0-Tests/080707r#PAGE_SIZE_LIMIT - Section 2.4.3 HTTP Response was also amended to have the reader refer to 3.16 PAGE_SIZE_LIMIT (resp. 3.6 EXTERNAL_RESOURCES) for details of the total size (resp. count) the HTTP redirect response body should be added to: http://www.w3.org/2005/MWI/BPWG/Group/Drafts/mobileOK-Basic-1.0-Tests/080707r#http_response [Commentor reply] yes [Comment]

Output: * if I hit an HTTP redirect, does the size of the page served as the redirect page counts in PAGE_SIZE_LIMIT-1 or only under PAGE_SIZE_LIMIT-2? I've implemented the latter since I find it less confusing, but the spec could be clearer about it

mobileOK Basic Tests 1.0 - Disposition of comments


Input: [Commentor] LC-1991 Francois Daoust (archived comment) [Working Group decision] On your first point, we think that the tests should be carried on the response body because, as specified in the HTTP (RFC 2616) section 10.4.2 401 Unauthorized, the body of the HTTP Status 401 response should be presented to the user if the authentication fails: "If the 401 response contains the same challenge as the prior response, and the user agent has already attempted authentication at least once, then the user SHOULD be presented the entity that was given in the response, since that entity might include relevant diagnostic information" On your second point, we think that the text deserved to be clarified and updated the relevant part to state: "If authentication information was supplied in the HTTP request (i.e. authentication failed) or if no authentication information is available, FAIL" See: http://www.w3.org/2005/MWI/BPWG/Group/Drafts/mobileOK-Basic-1.0-Tests/080707r#http_response [Commentor reply] yes [Comment]

Output: * About the treatment of HTTP Status 401: - Why should tests be applied to the response body of such an HTTP response? The body will never be touched by any browser during the first pass (when authentication credentials have not already been sent) AFAICT. Besides, it wouldn't make any sense to display the resource if it's an included image for instance. It's perfectly normal to count the response in EXTERNAL_RESPONSE and PAGE_SIZE_LIMIT, but I suggest updating the "Carry out tests on the response" to "Do not carry out tests on the response", especially given the fact that the tests FAIL when credentials are wrong (and so there's no need to test the response body anyway even for the second pass) - "Re-request the resource using authentication information" could deserve some clarification. What if the checker doesn't have any authentication information? I would clarify this with "Re-request the resource using authentication information if available or FAIL" (where FAIL would be HTTP_RESPONSE-7)

mobileOK Basic Tests 1.0 - Disposition of comments


Input: [Commentor] LC-1992 Francois Daoust (archived comment) [Working Group decision] Links in a Web page intended for mobile consumption are an important constituent of the user experience. The user should be able to "trust" that clicking on a link does not yield an error message. For that reason, we think that returning FAILs in the LINK_TARGET_FORMAT is indeed needed. However, it occurred to us that HTTP Status 406 responses could well be returned for resources tasted by section 3.15.1 Object Element Processing Rule, and that this should obviously not trigger a FAIL, so we relaxed that last condition in that case as you suggested: http://www.w3.org/2005/MWI/BPWG/Group/Drafts/mobileOK-Basic-1.0-Tests/080707r#http_response [Commentor reply] yes [Comment]

Output: * HTTP responses and linked resources: I understand the LINK_TARGET_FORMAT test as willing to return WARNs to the user on linked resources, and to never return any FAIL. However, there are several cases in the tests that should be carried by the checker for HTTP responses that return a FAIL, even when the resource is a linked resource: - "If an HTTP request does not result in a valid HTTP response [...], FAIL" - 1 case in "If the response is an HTTPS response" - 2 cases in "If the HTTP status indicates redirection" - "If the HTTP status represents failure (4xx), other than 404 or a request for authentication (e.g. 401), FAIL" I guess one may argue that LINK_TARGET_FORMAT may return a FAIL message. The last point still stands in that case: is a linked resource that returned a 406 Not Acceptable status supposed to trigger a FAIL? I think I should be allowed to include links to external resources that are not able to serve content to the mobileOK checker in a page without losing the possibility for the page to be mobileOK. I would relax the last check to state: "If the HTTP status represents failure (4xx), other than 404 or a request for authentication (e.g. 401): If the response relates to a request for a linked resource (see 2.4.7 Linked Resources), continue with the test (see 3.10 LINK_TARGET_FORMAT ) and warn Otherwise (i.e. for included resources), FAIL"

mobileOK Basic Tests 1.0 - Disposition of comments


Input: [Commentor] LC-2159 Thomas Roessler on behalf of Web Security Context Working Group (archived comment) [Working Group decision] We added a section on HTTPS that refines the algorithm of determining an invalid https certificate. [Commentor reply] yes [Comment]

Output: Hello, this is a post last call comment concerning the mobile OK basic tests 1.0, on behalf of the Web Security Context Working Group. We notice that section 2.4.3 - HTTP Response - uses the notion of an "HTTPS response". There is no such thing. We also notice that the notion of an "invalid certificate" does not match what we understand to be the Best Practice Working Group's intention with this test. We propose that you update this criterion, at a minimum, as follows: If the resource is accessed through HTTPS: If the certificate presented does not match the resource's URI, FAIL. If the certificate has expired or is not yet valid, warn. If certificate validation otherwise fails, FAIL. Checker SHOULD consider arbitrary root certificates (including self-signed certificates) as trusted for the purposes of mobileOK testing. Note that there are additional error conditions that can occur during TLS negotiation, including a mismatch on supported algorithms and protocol versions. Regards,

mobileOK Basic Tests 1.0 - Disposition of comments


Input: [0] Value [1] Description [2] Example [3] Scope [4]

Output: Notes

Internationalization Tag Set (ITS) Version 2.0


Input: [0] mistranslation [1] The content of the target mistranslates the content of the source. [2] The English source reads "An ape succeeded in grasping a banana lying outside its cage with the help of a stick" but the Italian translation reads "l'ape riuscì a prendere la banana posta tuori dall sua gabbia aiutandosi con un bastone" ("A bee succeeded...") [3] T [4]

Output: Issues related to translation of specific terms related to the domain or task-specific language should be categorized as terminology issues.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] omission [1] Necessary text has been omitted from the localization or source. [2] One or more segments found in the source that should have been translated are missing in the target. [3] S or T [4]

Output: This type should not be used for missing whitespace or formatting codes, but instead should be reserved for linguistic content.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] untranslated [1] Content that should have been translated was left untranslated. [2] The source segment reads "The Professor said to Smith that he would hear from his lawyer" but the Hungarian localization reads "A professzor azt modta Smithnek, hogy he would hear from his lawyer." [3] T [4]

Output: omission takes precedence over untranslated. Omissions are distinct in that they address cases where text is not present, while untranslated addresses cases where text has been carried from the source untranslated.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] locale-specific-content [1] The localization contains content that does not apply to the locale for which it was prepared. [2] A text translated for the Japanese market contains call center numbers in Texas and refers to special offers available only in the U.S. [3] S or T [4]

Output: Legally inappropriate material should be classified as legal.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] numbers [1] Numbers are inconsistent between source and target. [2] A source text states that an object is 120 cm long, but the target text says it is 129 cm. long. [3] S or T [4]

Output: Some tools may correct for differences in units of measurement to reduce false positives.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] internationalization [1] There is an issue related to the internationalization of content. [2] A line of programming code has embedded language-specific strings. A user interface element leaves no room for text expansion. A form allows only for U.S.-style postal addresses and expects five digit U.S. ZIP codes. [3] S or T [4]

Output: There are many kinds of internationalization issues. This category is therefore very heterogeneous in what it can refer to.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] length [1] There is a significant difference in source and target length. [2] The translation of a segment is five times as long as the source. [3] T or S [4]

Output: What constitutes a "significant" difference in length is determined by the model referred to in the locQualityIssueProfileRef.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] uncategorized [1] The issue has not been categorized. [2] A new version of a tool returns information on an issue that has not been previously checked and that is not yet classified. [3] S or T [4]

Output: This category has two uses: A tool can use it to pass through quality data from another tool in cases where the issues from the other tool are not classified (for example, a localization quality assurance tool interfaces with a third-party grammar checker). A tool's issues are not yet assigned to categories, and, until an updated assignment is made, they may be listed as uncategorized. In this case it is recommended that issues be assigned to appropriate categories as soon as possible since uncategorized does not foster interoperability.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] other [1] Any issue that cannot be assigned to any values listed above. [3] S or T [4]

Output: This category allows for the inclusion of any issues not included in the previously listed values. This value MUST NOT be used for any tool- or model-specific issues that can be mapped to the values listed above. In addition, this value is not synonymous with uncategorized in that uncategorized issues may be assigned to another precise value, while other issues cannot. If a system has an "miscellaneous" or "other" category, it MUST be mapped to this value even if the specific instance of the issue might be mapped to another category.

Internationalization Tag Set (ITS) Version 2.0


Input: [user] name [Category] Physical Contact Information, Demographic and Socioeconomic Data [Type] personname [Short display name]

Output: User's Name


Input: [user] bdate [Category] Demographic and Socioeconomic Data [Type] date [Short display name]

Output: User's Birth Date


Input: [user] cert [Category] Unique Identifiers [Type] certificate [Short display name]

Output: User's Identity Certificate


Input: [user] gender [Category] Demographic and Socioeconomic Data [Type] gender [Short display name]

Output: User's Gender


Input: [user] employer [Category] Demographic and Socioeconomic Data [Type] text [Short display name]

Output: User's Employer


Input: [user] department [Category] Demographic and Socioeconomic Data [Type] text [Short display name]

Output: Department or division of organization where user is employed


Input: [user] jobtitle [Category] Demographic and Socioeconomic Data [Type] text [Short display name]

Output: User's Job Title


Input: [user] home-info [Category] Physical Contact Information, Online Contact Information, Demographic and Socioeconomic Data [Type] contact [Short display name]

Output: User's Home Contact Information


Input: [user] business-info [Category] Physical Contact Information, Online Contact Information, Demographic and Socioeconomic Data [Type] contact [Short display name]

Output: User's Business Contact Information


Input: [Item] W3C [Required?] all [Notes] Branding [Primary Audience]

Output: all

Difference between revisions of "SpecProd/Restyle/Content" - W3C Wiki


Input: [Item] WG/TF [Required?] all [Notes] Associated WG or Task Force [Primary Audience]

Output: potential participants

Difference between revisions of "SpecProd/Restyle/Content" - W3C Wiki


Input: [Item] Title [Required?] all [Primary Audience]

Output: all

Difference between revisions of "SpecProd/Restyle/Content" - W3C Wiki


Input: [Item] Pub date [Required?] all [Notes] Indication of out-of-date-ness / recency of change [Primary Audience]

Output: all

Difference between revisions of "SpecProd/Restyle/Content" - W3C Wiki


Input: [Item] Status [Required?] all [Notes] ED/WD/LC/CR/PR/REC/NOTE [Primary Audience]

Output: all

Difference between revisions of "SpecProd/Restyle/Content" - W3C Wiki


Input: [Item] Status disclaimer [Required?] all [Notes] Warn people the document is unstable, etc. [Primary Audience]

Output: new to reading W3C specs

Difference between revisions of "SpecProd/Restyle/Content" - W3C Wiki


Input: [Item] Copyright [Required?] all [Primary Audience]

Output: lawyers

Difference between revisions of "SpecProd/Restyle/Content" - W3C Wiki


Input: [Item] Patent Policy / Disclosures [Required?] some [Primary Audience]

Output: laywers

Difference between revisions of "SpecProd/Restyle/Content" - W3C Wiki


Input: [Item] Errata [Required?] REC [Notes] Only if there's errata [Primary Audience]

Output: implementers, reviewers

Difference between revisions of "SpecProd/Restyle/Content" - W3C Wiki


Input: [Item] Issues list [Required?] all? [Primary Audience]

Output: reviewers

Difference between revisions of "SpecProd/Restyle/Content" - W3C Wiki


Input: [Item] At-risk list [Required?] LC/CR [Primary Audience]

Output: W3C

Difference between revisions of "SpecProd/Restyle/Content" - W3C Wiki


Input: [Item] Discussion fora / Feedback [Required?] all [Notes] Mailing list, IRC, wiki, bugtracker, etc. [Primary Audience]

Output: reviewers

Difference between revisions of "SpecProd/Restyle/Content" - W3C Wiki


Input: [Item] Editor's draft [Required?] most [Primary Audience]

Output: reviewers, implementers

Difference between revisions of "SpecProd/Restyle/Content" - W3C Wiki


Input: [Item] Previous version(s) [Required?] all [Primary Audience]

Output: reviewers

Difference between revisions of "SpecProd/Restyle/Content" - W3C Wiki


Input: [Item] Test suite Link [Required?] CR/REC [Primary Audience]

Output: implementers, contributors

Difference between revisions of "SpecProd/Restyle/Content" - W3C Wiki


Input: [Item] Editors [Required?] all [Notes] Tells people who to talk to and who can fix issues [Primary Audience]

Output: participants

Difference between revisions of "SpecProd/Restyle/Content" - W3C Wiki


Input: [Item] Translations [Required?] some [Primary Audience]

Output: non-English speakers

Difference between revisions of "SpecProd/Restyle/Content" - W3C Wiki


Input: [Item] Other formats [Required?] some [Notes] Links to other formats suitable for offline/printing; particularly useful for multipage specs [Primary Audience]

Output: all

Difference between revisions of "SpecProd/Restyle/Content" - W3C Wiki


Input: [User Action/External Input] User presses button on steering wheel [Action on Device] Service is initiated and GPS satellite detection begins [Event Description] HTTP Request to app server [Resulting Action] Welcome prompts are played. Authentication dialog is initiated (may be initiated via speaker identification or key identification). [Event Handler]

Output: App server returns initial page to device


Input: [User Action/External Input] User interacts in an authentication dialog [Action on Device] Device executes authentication dialog using local ASR processing [Event Description] HTTP Request to app server which includes user credentials [Resulting Action] User is prompted for a destination (if additional services are availble after authentication, assume that user selects driving direction application) [Event Handler]

Output: App server returns initial page to device including user preferences


Input: [User Action/External Input] Initial GPS Input [Action on Device] N/A [Event Description] GPS_Data_In Event [Resulting Action] Device updates map on graphical display (assumes all maps are stored locally on device) [Event Handler]

Output: Device handles location information


Input: [User Action/External Input] User selects option to change volume of on-board unit using touch display. [Action on Device] N/A [Event Description] Touch_screen_event (includes x, y coordinates) [Resulting Action] Volume indicator changes on screen. Volume of speech output is changed [Event Handler]

Output: Touch screen detects and processes input


Input: [User Action/External Input] User presses button on steering wheel [Action on Device] Device initiates connection to ASR server [Event Description] Start_Listening Event [Resulting Action] "listening" icon appears on display (utterances prior to establishing the connection are buffered) [Event Handler]

Output: ASR Server receives request and establishes connection


Input: [User Action/External Input] User says destination address (may improve recognition accuracy by sending grammar constraints to server based on a local dialog with the user instead of allowing any address from the start) [Action on Device] N/A [Event Description] N/A [Resulting Action] Device processes results and plays confirmation dialog to user while highlighting destination and route on graphical display [Event Handler]

Output: ASR Server processes speech and returns results to device


Input: [User Action/External Input] User confirms destination [Action on Device] Device performs ASR Processing locally. Upon confirmation, destination info is sent to app server [Event Description] HTTP Request is sent to app server (includes current location and destination information) [Resulting Action] Device processes results and updates graphical display with route and directions highlighting next step [Event Handler]

Output: App Server processes input and returns data to device


Input: [User Action/External Input] GPS Input at regular intervals [Action on Device] N/A [Event Description] GPS_Data_In Event [Resulting Action] Device updates map on graphical display (assumes all maps are stored locally on device) and highlights current step. When milestone is hit, next instruction is played to user [Event Handler]

Output: Device processes location data and checks if location milestone is hit


Input: [User Action/External Input] GPS Input at regular intervals (indicating driver is off course) [Action on Device] N/A [Event Description] GPS_Data_In Event [Resulting Action] Map on graphical display is updated and textual message is displayed indicating that route is not correct. Prompt is played from the device indicating that route is being recalculated [Event Handler]

Output: Device processes location data and determines that user is off course


Input: [User Action/External Input] N/A [Action on Device] Route request is sent to app server including new location data [Event Description] HTTP Request is sent to app server (includes current location and destination information) [Resulting Action] Device processes results and updates graphical display with route and directions highlighting next step [Event Handler]

Output: App Server processes input and returns data to device


Input: [User Action/External Input] Alert received on device based on traffic conditions [Action on Device] N/A [Event Description] Route_Change Alert [Resulting Action] User is informed of traffic conditions and asked whether route should be recalculated. [Event Handler]

Output: Device processes event and initiates dialog to determine if route should be recalculated


Input: [User Action/External Input] User requests recalculation of route based on current traffic conditions [Action on Device] Device performs ASR Processing locally. Upon confirmation, destination info is sent to app server [Event Description] HTTP Request is sent to app server (includes current location and destination information) [Resulting Action] Device processes results and updates graphical display with route and directions highlighting next step [Event Handler]

Output: App Server processes input and returns data to device


Input: [User Action/External Input] User presses button on steering wheel [Action on Device] Connection to ASR server is established [Event Description] Start_Listening Event [Resulting Action] User hears acknowledgement prompt for continuation, and "listening" icon appears on display [Event Handler]

Output: ASR Server receives request and establishes connection


Input: [User Action/External Input] User requests new destination by destination type while still depressing button on steering wheel (may improve recognition accuracy by sending grammar constraints to server based on a local dialog with the user) [Action on Device] N/A [Event Description] N/A [Resulting Action] Device processes results and plays confirmation dialog to user while highlighting destination and route on graphical display [Event Handler]

Output: ASR Server processes speech and returns results to device


Input: [User Action/External Input] User confirms destination via a multiple interaction dialog to determine exact destination [Action on Device] Device executes dialog based on user responses (using local ASR Processing) and accesses app server as needed [Event Description] HTTP requests to app server for dialog and data specific to user response [Resulting Action] User interacts in a dialog and selects destination. User is asked whether this is a new destination [Event Handler]

Output: App server responds with appropriate dialog


Input: [User Action/External Input] User indicates that this is a stop on the way to original destination [Action on Device] Devices sends updated destination information to app server [Event Description] HTTP Request for updated directions (based on current location, detour destination, and ultimate destination) [Resulting Action] Device processes results and updates graphical display with new route and directions highlighting next step [Event Handler]

Output: App Server processes input and returns data to device


Input: [dynamic] clickstream.client [Category] Navigation and Click-stream Data [Type] text [Short display name]

Output: Click-stream collected on the client


Input: [dynamic] clickstream.server [Category] Navigation and Click-stream Data [Type] text [Short display name]

Output: Click-stream collected on the server


Input: [dynamic] cookies [Category] (variable-category) [Type] text [Short display name]

Output: Cookies are processed (read/write)


Input: [dynamic] http.useragent [Category] Computer Information [Type] text [Short display name]

Output: User Agent information


Input: [dynamic] http.referrer [Category] Navigation and Click-stream Data [Type] uri [Short display name]

Output: Last URI requested by the user


Input: [dynamic] miscdata [Category] (variable-category) [Type] text [Short display name]

Output: Miscellaneous non-base data schema information


Input: [dynamic] searchtext [Category] Interactive Data [Type] text [Short display name]

Output: Search terms


Input: [dynamic] interactionrecord [Category] Interactive Data [Type] text [Short display name]

Output: Server stores the transaction history


Input: [Event Name] dragstart [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Contains source node unless a selection is being dragged, in which case it is empty; files returns any files included in the drag operation [effectAllowed] uninitialized [dropEffect] none [Default Action]

Output: Initiate the drag-and-drop operation


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

Output: Continue the drag-and-drop operation


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

Output: Reject immediate user selection as potential target element


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


Input: [Event Name] dragover [Target] Current target element [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] Based on effectAllowed value [Default Action]

Output: Reset the current drag operation to "none"


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

Output: Varies


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

Output: Varies


Input: [Component] XPath 1.0 compatibility mode [Value]

Output: false

Static Context Components for use-when Expressions


Input: [Component] In scope namespaces [Value]

Output: determined by the in-scope namespaces for the containing element in the stylesheet


Input: [Component] Default element/type namespace [Value]

Output: determined by the xpath-default-namespace attribute if present (see 5.2 Unprefixed QNames in Expressions and Patterns); otherwise the null namespace


Input: [Component] Default function namespace [Value]

Output: The standard function namespace


Input: [Component] In scope type definitions [Value]

Output: The type definitions that would be available in the absence of any xsl:import-schema declaration


Input: [Component] In scope element declarations [Value]


Input: [Component] In scope attribute declarations [Value]


Input: [Component] In scope variables [Value]


Input: [Component] In scope functions [Value]

Output: The core functions defined in [Functions and Operators], together with the functions element-available, function-available, and system-property defined in this specification, plus an implementation-defined set of extension functions. Note that stylesheet functions are not included in the context, which means that the function function-available will return false in respect of such functions.


Input: [Component] In scope collations [Value]

Output: Implementation-defined


Input: [Component] Default collation [Value]

Output: The Unicode Codepoint Collation


Input: [Component] Base URI [Value]

Output: The base URI of the containing element in the stylesheet


Input: [Component] Statically known documents [Value]


Input: [Component] Statically known collections [Value]


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

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

Voice Extensible Markup Language (VoiceXML) 3.0

Table 98: Speech Recognition Properties


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

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

Voice Extensible Markup Language (VoiceXML) 3.0

Table 98: Speech Recognition Properties


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

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

Voice Extensible Markup Language (VoiceXML) 3.0

Table 98: Speech Recognition Properties


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

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

Voice Extensible Markup Language (VoiceXML) 3.0

Table 98: Speech Recognition Properties


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

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

Voice Extensible Markup Language (VoiceXML) 3.0

Table 98: Speech Recognition Properties


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

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

Voice Extensible Markup Language (VoiceXML) 3.0

Table 98: Speech Recognition Properties


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

Output: should go


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

Output: the pointing


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

Output: should go


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

Output: pointing device


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

Output: border spacing


Input: [0] Including here, [2]

Output: blank cells.


Input: [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 Space] VML [Type] string [Default Value] null [Description] A unique ID that identifies the shadow on a shape. Used by script to reference the shape in a collection. [Attribute]

Output: id


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

Output: on


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

Output: type


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

Output: obscured


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

Output: color


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

Output: opacity


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

Output: offset


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

Output: color2


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

Output: offset2


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

Output: origin


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

Output: matrix


Input: [0] UI [.capture*] new non-modal prompt [2] form control derived from input file, part of the page [(resp audio, video)]

Output: new form control, part of the page


Input: [0] scope of new API [.capture*] several new interfaces [2] limited (derive from FileReader) [(resp audio, video)]

Output: limited (derive from FileReader)


Input: [0] In widgets [.capture*] can grant access to API without prompt [2] awkward to use [(resp audio, video)]

Output: awkward to use


Input: [0] Integration with Media gallery [.capture*] left to the developer [2] possibly transparent (but down to the UA) [(resp audio, video)]

Output: possibly transparent (but down to the UA)


Input: [0] viewfinder compat [.capture*] new API calls needed [2] possibly transparent? [(resp audio, video)]

Output: possibly transparent?


Input: [0] control on number and duration of captures [.capture*] available in API [2] number controled by number of fields — awkward user exp; not clear how to control duration [(resp audio, video)]

Output: could be controled with attributes on the input field?


Input: [0] detection for support of capture capabilities [.capture*] possible with boolean flags added to Capture interface [2] not clear; might need flags addition [(resp audio, video)]

Output: not clear either


Input: [0] evolution for more control of the capture devices [.capture*] need new API calls added to Capture [2] no clear path; probably would need API of its own, but not clear how to plug in [(resp audio, video)]

Output: no clear path; probably would need API of its own, but not clear how to plug in


Input: [0] impact/dependence on markup spec (html5?) [.capture*] None [2] Limited [(resp audio, video)]

Output: Not trivial


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

Output: No conflict

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


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

Output: No conflict; added LDP headers

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


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

Output: No conflict; added LDP headers

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


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

Output: No conflict

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


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

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

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


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

Output: No conflict

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


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

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

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


Input: [0] UI [2] form control derived from input file, part of the page [(resp audio, video)] new form control, part of the page [.capture*]

Output: new non-modal prompt


Input: [0] scope of new API [2] limited (derive from FileReader) [(resp audio, video)] limited (derive from FileReader) [.capture*]

Output: several new interfaces


Input: [0] In widgets [2] awkward to use [(resp audio, video)] awkward to use [.capture*]

Output: can grant access to API without prompt


Input: [0] Integration with Media gallery [2] possibly transparent (but down to the UA) [(resp audio, video)] possibly transparent (but down to the UA) [.capture*]

Output: left to the developer


Input: [0] viewfinder compat [2] possibly transparent? [(resp audio, video)] possibly transparent? [.capture*]

Output: new API calls needed


Input: [0] control on number and duration of captures [2] number controled by number of fields — awkward user exp; not clear how to control duration [(resp audio, video)] could be controled with attributes on the input field? [.capture*]

Output: available in API


Input: [0] detection for support of capture capabilities [2] not clear; might need flags addition [(resp audio, video)] not clear either [.capture*]

Output: possible with boolean flags added to Capture interface


Input: [0] evolution for more control of the capture devices [2] no clear path; probably would need API of its own, but not clear how to plug in [(resp audio, video)] no clear path; probably would need API of its own, but not clear how to plug in [.capture*]

Output: need new API calls added to Capture


Input: [0] impact/dependence on markup spec (html5?) [2] Limited [(resp audio, video)] Not trivial [.capture*]


Input: [Name] bargein [Type] boolean [Required] No [Default Value] bargein property [Description]

Output: Controls whether the prompt can be interrupted.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 28: Attributes


Input: [Name] bargeintype [Type] string [Required] No [Default Value] bargeintype property [Description]

Output: On prompts that can be interrupted, determines the type of bargein, either 'speech', or 'hotword'.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 28: Attributes


Input: [Name] cond [Type] data model expression [Required] No [Default Value] true [Description]

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

Voice Extensible Markup Language (VoiceXML) 3.0

Table 28: Attributes


Input: [Name] count [Type] positive integer [Required] No [Default Value] 1 [Description]

Output: A number indicating the repetition count, allowing a prompt to be activated or not depending on the current repetition count.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 28: Attributes


Input: [Name] timeout [Type] Time Designation [Required] No [Default Value] timeout property [Description]

Output: The time to wait for user input.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 28: Attributes


Input: [Name] xml:lang [Type] string [Required] No [Default Value] document's "xml:lang" attribute [Description]

Output: The language identifier for the prompt.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 28: Attributes


Input: [Name] xml:base [Type] string [Required] No [Default Value] document's "xml:base" attribute [Description]

Output: Declares the base URI from which relative URIs in the prompt are resolved.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 28: Attributes


Input: [Event Name] dragstart [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [effectAllowed] uninitialized [dropEffect] none [Default Action] Initiate the drag-and-drop operation [dataTransfer]

Output: Contains source node unless a selection is being dragged, in which case it is empty; files returns any files included in the drag operation


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

Output: Empty


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

Output: Empty


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

Output: Empty


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

Output: Empty


Input: [Event Name] drop [Target] Current target element [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [effectAllowed] Same as last event [dropEffect] Current drag operation [Default Action] Varies [dataTransfer]

Output: getData() returns data set in dragstart event; files returns any files included in the drag operation


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

Output: Empty


Input: [user] name [Type] personname [Short display name] User's Name [Category]

Output: Physical Contact Information, Demographic and Socioeconomic Data


Input: [user] bdate [Type] date [Short display name] User's Birth Date [Category]

Output: Demographic and Socioeconomic Data


Input: [user] cert [Type] certificate [Short display name] User's Identity Certificate [Category]

Output: Unique Identifiers


Input: [user] gender [Type] gender [Short display name] User's Gender [Category]

Output: Demographic and Socioeconomic Data


Input: [user] employer [Type] text [Short display name] User's Employer [Category]

Output: Demographic and Socioeconomic Data


Input: [user] department [Type] text [Short display name] Department or division of organization where user is employed [Category]

Output: Demographic and Socioeconomic Data


Input: [user] jobtitle [Type] text [Short display name] User's Job Title [Category]

Output: Demographic and Socioeconomic Data


Input: [user] home-info [Type] contact [Short display name] User's Home Contact Information [Category]

Output: Physical Contact Information, Online Contact Information, Demographic and Socioeconomic Data


Input: [user] business-info [Type] contact [Short display name] User's Business Contact Information [Category]

Output: Physical Contact Information, Online Contact Information, Demographic and Socioeconomic Data


Input: [Value] copy: [Description]

Output: A duplicate of the source object will be dropped into the target.

Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [Value] move: [Description]

Output: The source object will be removed from its current location and dropped into the target.

Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [Value] link: [Description]

Output: A reference or shortcut to the dragged object will be created in the target object.

Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [Value] execute: [Description]

Output: A function supported by the drop target is executed, using the drag source as an input.

Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [Value] popup: [Description]

Output: There is a popup menu or dialog that allows the user to choose one of the drag operations (copy, move, link, execute) and any other drag functionality, such as cancel.

Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [Value] none (default): [Description]

Output: No operation can be performed; effectively cancels the drag operation if an attempt is made to drop on this object. Ignored if combined with any other token value. e.g. 'none copy' is equivalent to a 'copy' value.

Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [User Action/External Input] User presses button on steering wheel [Action on Device] Service is initiated and GPS satellite detection begins [Event Handler] App server returns initial page to device [Resulting Action] Welcome prompts are played. Authentication dialog is initiated (may be initiated via speaker identification or key identification). [Event Description]

Output: HTTP Request to app server


Input: [User Action/External Input] User interacts in an authentication dialog [Action on Device] Device executes authentication dialog using local ASR processing [Event Handler] App server returns initial page to device including user preferences [Resulting Action] User is prompted for a destination (if additional services are availble after authentication, assume that user selects driving direction application) [Event Description]

Output: HTTP Request to app server which includes user credentials


Input: [User Action/External Input] Initial GPS Input [Action on Device] N/A [Event Handler] Device handles location information [Resulting Action] Device updates map on graphical display (assumes all maps are stored locally on device) [Event Description]

Output: GPS_Data_In Event


Input: [User Action/External Input] User selects option to change volume of on-board unit using touch display. [Action on Device] N/A [Event Handler] Touch screen detects and processes input [Resulting Action] Volume indicator changes on screen. Volume of speech output is changed [Event Description]

Output: Touch_screen_event (includes x, y coordinates)


Input: [User Action/External Input] User presses button on steering wheel [Action on Device] Device initiates connection to ASR server [Event Handler] ASR Server receives request and establishes connection [Resulting Action] "listening" icon appears on display (utterances prior to establishing the connection are buffered) [Event Description]

Output: Start_Listening Event


Input: [User Action/External Input] User says destination address (may improve recognition accuracy by sending grammar constraints to server based on a local dialog with the user instead of allowing any address from the start) [Action on Device] N/A [Event Handler] ASR Server processes speech and returns results to device [Resulting Action] Device processes results and plays confirmation dialog to user while highlighting destination and route on graphical display [Event Description]


Input: [User Action/External Input] User confirms destination [Action on Device] Device performs ASR Processing locally. Upon confirmation, destination info is sent to app server [Event Handler] App Server processes input and returns data to device [Resulting Action] Device processes results and updates graphical display with route and directions highlighting next step [Event Description]

Output: HTTP Request is sent to app server (includes current location and destination information)


Input: [User Action/External Input] GPS Input at regular intervals [Action on Device] N/A [Event Handler] Device processes location data and checks if location milestone is hit [Resulting Action] Device updates map on graphical display (assumes all maps are stored locally on device) and highlights current step. When milestone is hit, next instruction is played to user [Event Description]

Output: GPS_Data_In Event


Input: [User Action/External Input] GPS Input at regular intervals (indicating driver is off course) [Action on Device] N/A [Event Handler] Device processes location data and determines that user is off course [Resulting Action] Map on graphical display is updated and textual message is displayed indicating that route is not correct. Prompt is played from the device indicating that route is being recalculated [Event Description]

Output: GPS_Data_In Event


Input: [User Action/External Input] N/A [Action on Device] Route request is sent to app server including new location data [Event Handler] App Server processes input and returns data to device [Resulting Action] Device processes results and updates graphical display with route and directions highlighting next step [Event Description]

Output: HTTP Request is sent to app server (includes current location and destination information)


Input: [User Action/External Input] Alert received on device based on traffic conditions [Action on Device] N/A [Event Handler] Device processes event and initiates dialog to determine if route should be recalculated [Resulting Action] User is informed of traffic conditions and asked whether route should be recalculated. [Event Description]

Output: Route_Change Alert


Input: [User Action/External Input] User requests recalculation of route based on current traffic conditions [Action on Device] Device performs ASR Processing locally. Upon confirmation, destination info is sent to app server [Event Handler] App Server processes input and returns data to device [Resulting Action] Device processes results and updates graphical display with route and directions highlighting next step [Event Description]

Output: HTTP Request is sent to app server (includes current location and destination information)


Input: [User Action/External Input] User presses button on steering wheel [Action on Device] Connection to ASR server is established [Event Handler] ASR Server receives request and establishes connection [Resulting Action] User hears acknowledgement prompt for continuation, and "listening" icon appears on display [Event Description]

Output: Start_Listening Event


Input: [User Action/External Input] User requests new destination by destination type while still depressing button on steering wheel (may improve recognition accuracy by sending grammar constraints to server based on a local dialog with the user) [Action on Device] N/A [Event Handler] ASR Server processes speech and returns results to device [Resulting Action] Device processes results and plays confirmation dialog to user while highlighting destination and route on graphical display [Event Description]


Input: [User Action/External Input] User confirms destination via a multiple interaction dialog to determine exact destination [Action on Device] Device executes dialog based on user responses (using local ASR Processing) and accesses app server as needed [Event Handler] App server responds with appropriate dialog [Resulting Action] User interacts in a dialog and selects destination. User is asked whether this is a new destination [Event Description]

Output: HTTP requests to app server for dialog and data specific to user response


Input: [User Action/External Input] User indicates that this is a stop on the way to original destination [Action on Device] Devices sends updated destination information to app server [Event Handler] App Server processes input and returns data to device [Resulting Action] Device processes results and updates graphical display with new route and directions highlighting next step [Event Description]

Output: HTTP Request for updated directions (based on current location, detour destination, and ultimate destination)


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

Output: AT

Mapping of the attribute information item properties to EXI event types


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

Output: AT


Input: [Property] prefix [EXI event types]

Output: AT


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

Output: The value of AT


Input: [Property] specified [EXI event types]

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


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

Output: Computed based on AT and DT


Input: [Property] references [EXI event types]

Output: Computed based on attribute type and value of AT


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

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


Input: [Definition] Character data [Attribute Type]

Output: CDATA

XHTML™ Modularization 1.1 - Second Edition


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

Output: ID

XHTML™ Modularization 1.1 - Second Edition


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

Output: IDREF

XHTML™ Modularization 1.1 - Second Edition


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

Output: IDREFS

XHTML™ Modularization 1.1 - Second Edition


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

Output: NAME

XHTML™ Modularization 1.1 - Second Edition


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

Output: NMTOKEN

XHTML™ Modularization 1.1 - Second Edition


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

Output: NMTOKENS

XHTML™ Modularization 1.1 - Second Edition


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

Output: Read/write mode

7.6 Drag and drop — HTML5: Edition for Web Authors


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

Output: Protected mode

7.6 Drag and drop — HTML5: Edition for Web Authors


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

Output: Protected mode

7.6 Drag and drop — HTML5: Edition for Web Authors


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

Output: Protected mode

7.6 Drag and drop — HTML5: Edition for Web Authors


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

Output: Protected mode

7.6 Drag and drop — HTML5: Edition for Web Authors


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

Output: Read-only mode

7.6 Drag and drop — HTML5: Edition for Web Authors


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

Output: Protected mode

7.6 Drag and drop — HTML5: Edition for Web Authors


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

Output: AXUIElementDestroyed If in a live region, AXLiveRegionChanged

WAI-ARIA 1.0 User Agent Implementation Guide

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


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

Output: AXUIElementDestroyed If in a live region, AXLiveRegionChanged

WAI-ARIA 1.0 User Agent Implementation Guide


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

Output: AXUIElementCreated If in a live region, AXLiveRegionChanged

WAI-ARIA 1.0 User Agent Implementation Guide