task
stringlengths 12
101
| input
stringlengths 5
5.87k
| output
stringlengths 1
5.47k
| options
sequence | pageTitle
stringlengths 0
151
| outputColName
stringlengths 1
142
| url
stringlengths 24
147
| wdcFile
stringlengths 71
75
|
|---|---|---|---|---|---|---|---|
30ae7837_tion_Tag_Set__ITS__Version_2_0__Description | [Value] length [Example] The translation of a segment is five times as long as the source. [Scope] S or T [Notes] What constitutes a "significant" difference in length is determined by the model referred to in the locQualityIssueProfileRef. [Description] | There is a significant difference in source and target length. | [] | Internationalization Tag Set (ITS) Version 2.0 | Description | http://www.w3.org/TR/its20/ | 27/1438042989826.86_20150728002309-00079-ip-10-236-191-2_825201540_4.json |
30ae7837_tion_Tag_Set__ITS__Version_2_0__Description | [Value] non-conformance [Example] The sentence "The harbour connected which to printer is busy or configared not properly." would have poor conformance. [Scope] S or T [Notes] Non-conformance is determined through the use of multiple statistical measures of similarity to a corpus of known-good content. For example, in a system that uses classification techniques the poor conformance might be a function of combined incorrect terminology, wrong spelling and bad grammar, or other features as determined by the system. [Description] | The content is deemed to show poor statistical conformance to a reference corpus. Higher severity values reflect poorer conformance. | [] | Internationalization Tag Set (ITS) Version 2.0 | Description | http://www.w3.org/TR/its20/ | 27/1438042989826.86_20150728002309-00079-ip-10-236-191-2_825201540_4.json |
30ae7837_tion_Tag_Set__ITS__Version_2_0__Description | [Value] uncategorized [Example] A new version of a tool returns information on an issue that has not been previously checked and that is not yet classified. A text is defective in ways that defy categorization, such as the appearance of nonsense garbled text of unknown origin (e.g., a translation shows an unintelligible result and/or appears unrelated to the source material). [Scope] S or T [Notes] This value has the following 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 values, 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 values as soon as possible since uncategorized does not foster interoperability. uncategorized can be used where a portion of text is defective in a way that defies assignment to a value in either the originating system or in any other ITS localization quality markup to indicate that it is uncategorizable. [Description] | The issue either has not been categorized or cannot be categorized. | [] | Internationalization Tag Set (ITS) Version 2.0 | Description | http://www.w3.org/TR/its20/ | 27/1438042989826.86_20150728002309-00079-ip-10-236-191-2_825201540_4.json |
30ae7837_tion_Tag_Set__ITS__Version_2_0__Description | [Value] other [Scope] S or T [Notes] This value allows for the inclusion of any issues not included in the previously listed values. It is encouraged not to use this value 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" value, it is better to map this to this value even if the specific instance of the issue might be mapped to another value. [Description] | Any issue that cannot be assigned to any values listed above. | [] | Internationalization Tag Set (ITS) Version 2.0 | Description | http://www.w3.org/TR/its20/ | 27/1438042989826.86_20150728002309-00079-ip-10-236-191-2_825201540_4.json |
1231806f_3C_P3_Vocabulary_Working_Draft__Applies_to | [Clause] Access [Description] The ability of users to obtain and correct information that an entity has collected about them [Required in Every Proposal] yes [Default Type of Label] URI or text string [May be Defined in Vocabulary] yes [Applies to] | proposal or statement | [] | W3C P3 Vocabulary Working Draft | Applies to | http://www.w3.org/TR/WD-P3P-grammar-971014.html | 27/1438042988051.33_20150728002308-00301-ip-10-236-191-2_821933300_1.json |
1231806f_3C_P3_Vocabulary_Working_Draft__Applies_to | [Clause] Agreement With [Description] The entity who the user is entering into an agreement with [Required in Every Proposal] yes [Default Type of Label] certificate, URI, or text string [May be Defined in Vocabulary] yes [Applies to] | proposal or statement | [] | W3C P3 Vocabulary Working Draft | Applies to | http://www.w3.org/TR/WD-P3P-grammar-971014.html | 27/1438042988051.33_20150728002308-00301-ip-10-236-191-2_821933300_1.json |
1231806f_3C_P3_Vocabulary_Working_Draft__Applies_to | [Clause] Consequence [Description] The impact on the user of reaching an agreement [Required in Every Proposal] yes [Default Type of Label] URI or text string [May be Defined in Vocabulary] yes [Applies to] | proposal or statement | [] | W3C P3 Vocabulary Working Draft | Applies to | http://www.w3.org/TR/WD-P3P-grammar-971014.html | 27/1438042988051.33_20150728002308-00301-ip-10-236-191-2_821933300_1.json |
1231806f_3C_P3_Vocabulary_Working_Draft__Applies_to | [Clause] Contact [Description] Information for contacting a service with inquiries about the services privacy practices. [Required in Every Proposal] yes [Default Type of Label] URI or text string [May be Defined in Vocabulary] yes [Applies to] | proposal or statement | [] | W3C P3 Vocabulary Working Draft | Applies to | http://www.w3.org/TR/WD-P3P-grammar-971014.html | 27/1438042988051.33_20150728002308-00301-ip-10-236-191-2_821933300_1.json |
1231806f_3C_P3_Vocabulary_Working_Draft__Applies_to | [Clause] Experience Space [Description] The space where a particular statement is valid [Required in Every Proposal] yes [Default Type of Label] set of URIs [May be Defined in Vocabulary] no [Applies to] | proposal or statement | [] | W3C P3 Vocabulary Working Draft | Applies to | http://www.w3.org/TR/WD-P3P-grammar-971014.html | 27/1438042988051.33_20150728002308-00301-ip-10-236-191-2_821933300_1.json |
1231806f_3C_P3_Vocabulary_Working_Draft__Applies_to | [Clause] Practice [Description] What a service will do with data [Required in Every Proposal] yes [Default Type of Label] none [May be Defined in Vocabulary] yes [Applies to] | statement | [] | W3C P3 Vocabulary Working Draft | Applies to | http://www.w3.org/TR/WD-P3P-grammar-971014.html | 27/1438042988051.33_20150728002308-00301-ip-10-236-191-2_821933300_1.json |
1231806f_3C_P3_Vocabulary_Working_Draft__Applies_to | [Clause] Qualified Data Set [Description] The data a service proposes to collect or requests [Required in Every Proposal] yes [Default Type of Label] see definition below [May be Defined in Vocabulary] no, but qualifier and category components may be [Applies to] | statement | [] | W3C P3 Vocabulary Working Draft | Applies to | http://www.w3.org/TR/WD-P3P-grammar-971014.html | 27/1438042988051.33_20150728002308-00301-ip-10-236-191-2_821933300_1.json |
1231806f_3C_P3_Vocabulary_Working_Draft__Applies_to | [Clause] Qualifier [Description] Used by the creator of a vocabulary to provide extra functionality beyond that in the base P3 Proposal Grammar [Required in Every Proposal] no [Default Type of Label] none [May be Defined in Vocabulary] yes [Applies to] | proposal, statement, or clause | [] | W3C P3 Vocabulary Working Draft | Applies to | http://www.w3.org/TR/WD-P3P-grammar-971014.html | 27/1438042988051.33_20150728002308-00301-ip-10-236-191-2_821933300_1.json |
1231806f_3C_P3_Vocabulary_Working_Draft__Applies_to | [Clause] Required [Description] A binary value indicating whether a particular practice, qualified data set, or statement is required in an agreement [Required in Every Proposal] no (defaults to 1 when not present) [Default Type of Label] 0 or 1 [May be Defined in Vocabulary] no [Applies to] | practice clause, qualified data set clause, or statement | [] | W3C P3 Vocabulary Working Draft | Applies to | http://www.w3.org/TR/WD-P3P-grammar-971014.html | 27/1438042988051.33_20150728002308-00301-ip-10-236-191-2_821933300_1.json |
1231806f_3C_P3_Vocabulary_Working_Draft__Applies_to | [Clause] Schema [Description] A URI that identifies a particular P3 proposal vocabulary [Required in Every Proposal] yes [Default Type of Label] URI [May be Defined in Vocabulary] no [Applies to] | proposal | [] | W3C P3 Vocabulary Working Draft | Applies to | http://www.w3.org/TR/WD-P3P-grammar-971014.html | 27/1438042988051.33_20150728002308-00301-ip-10-236-191-2_821933300_1.json |
1231806f_3C_P3_Vocabulary_Working_Draft__Applies_to | [Clause] Signature [Description] Signature and attribution information as defined by the Digital Signature effort [Required in Every Proposal] no [Default Type of Label] none [May be Defined in Vocabulary] yes [Applies to] | Proposal or statement | [] | W3C P3 Vocabulary Working Draft | Applies to | http://www.w3.org/TR/WD-P3P-grammar-971014.html | 27/1438042988051.33_20150728002308-00301-ip-10-236-191-2_821933300_1.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onabort [Event handler event type] | abort | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] oncancel [Event handler event type] | cancel | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] oncanplay [Event handler event type] | canplay | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] oncanplaythrough [Event handler event type] | canplaythrough | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onchange [Event handler event type] | change | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onclick [Event handler event type] | click | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onclose [Event handler event type] | close | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] oncuechange [Event handler event type] | cuechange | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] ondblclick [Event handler event type] | dblclick | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] ondrag [Event handler event type] | drag | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] ondragend [Event handler event type] | dragend | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] ondragenter [Event handler event type] | dragenter | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] ondragexit [Event handler event type] | dragexit | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] ondragleave [Event handler event type] | dragleave | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] ondragover [Event handler event type] | dragover | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] ondragstart [Event handler event type] | dragstart | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] ondrop [Event handler event type] | drop | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] ondurationchange [Event handler event type] | durationchange | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onemptied [Event handler event type] | emptied | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onended [Event handler event type] | ended | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] oninput [Event handler event type] | input | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] oninvalid [Event handler event type] | invalid | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onkeydown [Event handler event type] | keydown | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onkeypress [Event handler event type] | keypress | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onkeyup [Event handler event type] | keyup | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onloadeddata [Event handler event type] | loadeddata | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onloadedmetadata [Event handler event type] | loadedmetadata | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onloadstart [Event handler event type] | loadstart | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onmousedown [Event handler event type] | mousedown | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onmouseenter [Event handler event type] | mouseenter | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onmouseleave [Event handler event type] | mouseleave | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onmousemove [Event handler event type] | mousemove | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onmouseout [Event handler event type] | mouseout | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onmouseover [Event handler event type] | mouseover | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onmouseup [Event handler event type] | mouseup | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onmousewheel [Event handler event type] | mousewheel | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onpause [Event handler event type] | pause | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onplay [Event handler event type] | play | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onplaying [Event handler event type] | playing | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onprogress [Event handler event type] | progress | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onratechange [Event handler event type] | ratechange | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onreset [Event handler event type] | reset | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onseeked [Event handler event type] | seeked | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onseeking [Event handler event type] | seeking | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onselect [Event handler event type] | select | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onshow [Event handler event type] | show | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onstalled [Event handler event type] | stalled | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onsubmit [Event handler event type] | submit | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onsuspend [Event handler event type] | suspend | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] ontimeupdate [Event handler event type] | timeupdate | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onvolumechange [Event handler event type] | volumechange | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
aea65010_6_Web_application_APIs___HTML5__Event_handler_event_type | [Event handler] onwaiting [Event handler event type] | waiting | [] | 6 Web application APIs — HTML5 | Event handler event type | http://www.w3.org/TR/2013/CR-html5-20130806/webappapis.html | 27/1438042990112.92_20150728002310-00291-ip-10-236-191-2_820302653_0.json |
f7fe1c52_Canonical_XML_Version_2_0__Default | [Name] exclusiveMode [Values] true or false [Description] whether to do inclusive or exclusive dealing of namespaces. In exclusive mode the inclusiveNamespacePrefixList parameter can be specified listing the prefixes that are to be treated in an inclusive mode [Default] | false | [
[
"f",
"a",
"l",
"s",
"e"
],
[
"e",
"m",
"p",
"t",
"y"
],
[
"t",
"r",
"u",
"e"
],
[
"X",
"M",
"L"
],
[
"n",
"o",
"n",
"e"
],
[
"c",
"o",
"m",
"b",
"i",
"n",
"e"
],
[
"i",
"n",
"h",
"e",
"r",
"i",
"t"
]
] | Canonical XML Version 2.0 | Default | http://www.w3.org/TR/2010/WD-xml-c14n2-20100304/ | 27/1438042989826.86_20150728002309-00164-ip-10-236-191-2_820185960_0.json |
f7fe1c52_Canonical_XML_Version_2_0__Default | [Name] inclusiveNamespacePrefixList [Values] space separated list of prefixes [Description] list of prefixes to be treated inclusively. Special token #default indicates the default namespace. [Default] | empty | [
[
"f",
"a",
"l",
"s",
"e"
],
[
"e",
"m",
"p",
"t",
"y"
],
[
"t",
"r",
"u",
"e"
],
[
"X",
"M",
"L"
],
[
"n",
"o",
"n",
"e"
],
[
"c",
"o",
"m",
"b",
"i",
"n",
"e"
],
[
"i",
"n",
"h",
"e",
"r",
"i",
"t"
]
] | Canonical XML Version 2.0 | Default | http://www.w3.org/TR/2010/WD-xml-c14n2-20100304/ | 27/1438042989826.86_20150728002309-00164-ip-10-236-191-2_820185960_0.json |
f7fe1c52_Canonical_XML_Version_2_0__Default | [Name] ignoreComments [Values] true or false [Description] whether to ignore comments during canonicalization [Default] | true | [
[
"f",
"a",
"l",
"s",
"e"
],
[
"e",
"m",
"p",
"t",
"y"
],
[
"t",
"r",
"u",
"e"
],
[
"X",
"M",
"L"
],
[
"n",
"o",
"n",
"e"
],
[
"c",
"o",
"m",
"b",
"i",
"n",
"e"
],
[
"i",
"n",
"h",
"e",
"r",
"i",
"t"
]
] | Canonical XML Version 2.0 | Default | http://www.w3.org/TR/2010/WD-xml-c14n2-20100304/ | 27/1438042989826.86_20150728002309-00164-ip-10-236-191-2_820185960_0.json |
f7fe1c52_Canonical_XML_Version_2_0__Default | [Name] trimTextNodes [Values] true or false [Description] whether to trim (i.e. remove leading and trailing whitespaces) all text nodes when canonicalizing. Adjacent text nodes must be coalesced prior to trimming. If an element has an xml:space="preserve" attribute, then text nodes descendants of that element are not trimmed regardless of the value of this parameter. [Default] | false | [
[
"f",
"a",
"l",
"s",
"e"
],
[
"e",
"m",
"p",
"t",
"y"
],
[
"t",
"r",
"u",
"e"
],
[
"X",
"M",
"L"
],
[
"n",
"o",
"n",
"e"
],
[
"c",
"o",
"m",
"b",
"i",
"n",
"e"
],
[
"i",
"n",
"h",
"e",
"r",
"i",
"t"
]
] | Canonical XML Version 2.0 | Default | http://www.w3.org/TR/2010/WD-xml-c14n2-20100304/ | 27/1438042989826.86_20150728002309-00164-ip-10-236-191-2_820185960_0.json |
f7fe1c52_Canonical_XML_Version_2_0__Default | [Name] serialization [Values] XML or EXI [Description] whether to do the normal XML serialization, or do an EXI serialization - which is useful if the original document to be signed is already in EXI format. [Default] | XML | [
[
"f",
"a",
"l",
"s",
"e"
],
[
"e",
"m",
"p",
"t",
"y"
],
[
"t",
"r",
"u",
"e"
],
[
"X",
"M",
"L"
],
[
"n",
"o",
"n",
"e"
],
[
"c",
"o",
"m",
"b",
"i",
"n",
"e"
],
[
"i",
"n",
"h",
"e",
"r",
"i",
"t"
]
] | Canonical XML Version 2.0 | Default | http://www.w3.org/TR/2010/WD-xml-c14n2-20100304/ | 27/1438042989826.86_20150728002309-00164-ip-10-236-191-2_820185960_0.json |
f7fe1c52_Canonical_XML_Version_2_0__Default | [Name] prefixRewrite [Values] none, sequential, derived [Description] with none, prefixes are not changed, with sequential prefixes are changed to n1, n2, n3 ... and with derived, each prefix is changed to nSuffix, where the suffix is derived by doing a digest of the namespace URI. [Default] | none | [
[
"f",
"a",
"l",
"s",
"e"
],
[
"e",
"m",
"p",
"t",
"y"
],
[
"t",
"r",
"u",
"e"
],
[
"X",
"M",
"L"
],
[
"n",
"o",
"n",
"e"
],
[
"c",
"o",
"m",
"b",
"i",
"n",
"e"
],
[
"i",
"n",
"h",
"e",
"r",
"i",
"t"
]
] | Canonical XML Version 2.0 | Default | http://www.w3.org/TR/2010/WD-xml-c14n2-20100304/ | 27/1438042989826.86_20150728002309-00164-ip-10-236-191-2_820185960_0.json |
f7fe1c52_Canonical_XML_Version_2_0__Default | [Name] sortAttributes [Values] true or false [Description] whether the attributes need to be sorted before canonicalization. In some environments the order of attributes changes in transit so sorting is important. [Default] | true | [
[
"f",
"a",
"l",
"s",
"e"
],
[
"e",
"m",
"p",
"t",
"y"
],
[
"t",
"r",
"u",
"e"
],
[
"X",
"M",
"L"
],
[
"n",
"o",
"n",
"e"
],
[
"c",
"o",
"m",
"b",
"i",
"n",
"e"
],
[
"i",
"n",
"h",
"e",
"r",
"i",
"t"
]
] | Canonical XML Version 2.0 | Default | http://www.w3.org/TR/2010/WD-xml-c14n2-20100304/ | 27/1438042989826.86_20150728002309-00164-ip-10-236-191-2_820185960_0.json |
f7fe1c52_Canonical_XML_Version_2_0__Default | [Name] ignoreDTD [Values] true or false [Description] if set to true, ignore the DTD completely, which means do not normalize attributes, do not look into entity definitions, do not add default attributes to each element [Default] | false | [
[
"f",
"a",
"l",
"s",
"e"
],
[
"e",
"m",
"p",
"t",
"y"
],
[
"t",
"r",
"u",
"e"
],
[
"X",
"M",
"L"
],
[
"n",
"o",
"n",
"e"
],
[
"c",
"o",
"m",
"b",
"i",
"n",
"e"
],
[
"i",
"n",
"h",
"e",
"r",
"i",
"t"
]
] | Canonical XML Version 2.0 | Default | http://www.w3.org/TR/2010/WD-xml-c14n2-20100304/ | 27/1438042989826.86_20150728002309-00164-ip-10-236-191-2_820185960_0.json |
f7fe1c52_Canonical_XML_Version_2_0__Default | [Name] expandEntities [Values] true or false [Description] if set to true ignore all entity declarations, and expand only the predefined entites (lt, gt, amp, apos, quot) and character references. (Entity declarations are potential attack points, [BradHill] mentions an entity that is 2 GB is length, also expanding external entities can lead to cross site scripting attacks) [Default] | true | [
[
"f",
"a",
"l",
"s",
"e"
],
[
"e",
"m",
"p",
"t",
"y"
],
[
"t",
"r",
"u",
"e"
],
[
"X",
"M",
"L"
],
[
"n",
"o",
"n",
"e"
],
[
"c",
"o",
"m",
"b",
"i",
"n",
"e"
],
[
"i",
"n",
"h",
"e",
"r",
"i",
"t"
]
] | Canonical XML Version 2.0 | Default | http://www.w3.org/TR/2010/WD-xml-c14n2-20100304/ | 27/1438042989826.86_20150728002309-00164-ip-10-236-191-2_820185960_0.json |
f7fe1c52_Canonical_XML_Version_2_0__Default | [Name] xmlBaseAncestors [Values] inherit, none, combine [Description] whether to inherit xml:base attributes from ancestors (like C14N 1.0) or not (like Exc C14n 1.0) or combine them (like C14n 1.1) [Default] | combine | [
[
"f",
"a",
"l",
"s",
"e"
],
[
"e",
"m",
"p",
"t",
"y"
],
[
"t",
"r",
"u",
"e"
],
[
"X",
"M",
"L"
],
[
"n",
"o",
"n",
"e"
],
[
"c",
"o",
"m",
"b",
"i",
"n",
"e"
],
[
"i",
"n",
"h",
"e",
"r",
"i",
"t"
]
] | Canonical XML Version 2.0 | Default | http://www.w3.org/TR/2010/WD-xml-c14n2-20100304/ | 27/1438042989826.86_20150728002309-00164-ip-10-236-191-2_820185960_0.json |
f7fe1c52_Canonical_XML_Version_2_0__Default | [Name] xmlIdAncestors [Values] inherit, none [Description] whether to inherit xml:id attributes from ancestors (like C14N 1.0) or not (like C14N 1.1 or Exc C14n 1.0) [Default] | none | [
[
"f",
"a",
"l",
"s",
"e"
],
[
"e",
"m",
"p",
"t",
"y"
],
[
"t",
"r",
"u",
"e"
],
[
"X",
"M",
"L"
],
[
"n",
"o",
"n",
"e"
],
[
"c",
"o",
"m",
"b",
"i",
"n",
"e"
],
[
"i",
"n",
"h",
"e",
"r",
"i",
"t"
]
] | Canonical XML Version 2.0 | Default | http://www.w3.org/TR/2010/WD-xml-c14n2-20100304/ | 27/1438042989826.86_20150728002309-00164-ip-10-236-191-2_820185960_0.json |
f7fe1c52_Canonical_XML_Version_2_0__Default | [Name] xmlLangAncestors [Values] inherit, none [Description] whether to inherit xml:lang attributes from ancestors (like C14N 1.0 and C14n 1.1) or not (Exc C14n 1.0) [Default] | inherit | [
[
"f",
"a",
"l",
"s",
"e"
],
[
"e",
"m",
"p",
"t",
"y"
],
[
"t",
"r",
"u",
"e"
],
[
"X",
"M",
"L"
],
[
"n",
"o",
"n",
"e"
],
[
"c",
"o",
"m",
"b",
"i",
"n",
"e"
],
[
"i",
"n",
"h",
"e",
"r",
"i",
"t"
]
] | Canonical XML Version 2.0 | Default | http://www.w3.org/TR/2010/WD-xml-c14n2-20100304/ | 27/1438042989826.86_20150728002309-00164-ip-10-236-191-2_820185960_0.json |
f7fe1c52_Canonical_XML_Version_2_0__Default | [Name] xmlSpaceAncestors [Values] inherit, none [Description] whether to inherit xml:space attributes from ancestors (like C14N 1.0 and C14n 1.1) or not (Exc C14n 1.0) [Default] | inherit | [
[
"f",
"a",
"l",
"s",
"e"
],
[
"e",
"m",
"p",
"t",
"y"
],
[
"t",
"r",
"u",
"e"
],
[
"X",
"M",
"L"
],
[
"n",
"o",
"n",
"e"
],
[
"c",
"o",
"m",
"b",
"i",
"n",
"e"
],
[
"i",
"n",
"h",
"e",
"r",
"i",
"t"
]
] | Canonical XML Version 2.0 | Default | http://www.w3.org/TR/2010/WD-xml-c14n2-20100304/ | 27/1438042989826.86_20150728002309-00164-ip-10-236-191-2_820185960_0.json |
f7fe1c52_Canonical_XML_Version_2_0__Default | [Name] xsiTypeAware [Values] true or false [Description] if set to true, looks for namespace prefix usages in xsi:type attributes as well, otherwise xsi:type attributes are treated just like regular attributes. [Default] | false | [
[
"f",
"a",
"l",
"s",
"e"
],
[
"e",
"m",
"p",
"t",
"y"
],
[
"t",
"r",
"u",
"e"
],
[
"X",
"M",
"L"
],
[
"n",
"o",
"n",
"e"
],
[
"c",
"o",
"m",
"b",
"i",
"n",
"e"
],
[
"i",
"n",
"h",
"e",
"r",
"i",
"t"
]
] | Canonical XML Version 2.0 | Default | http://www.w3.org/TR/2010/WD-xml-c14n2-20100304/ | 27/1438042989826.86_20150728002309-00164-ip-10-236-191-2_820185960_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-421 on behalf of I18N WG [Comment] Comment from the i18n review of: link Comment 6 At link Editorial/substantive: S Owner: FS Location in reviewed document: Sec. 2.2 [link] Comment: We propose to add to this section on \"input\" the requirement to provide an adequate input method for the user. Especially for complex scripts like Chinese or Japanese, this is a crucial requirement. [Working Group decision] The Best Practices do not set requirements on user agents, only on content; we already give recommendations on input mode for the content (see AVOID_FREE_TEXT and DEFAULT_INPUT_MODE]. Any further consideration would better fit in the techniques related to these best practices, on which we welcome contributions: link link [Commentor reply] | no reply from commenter | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-422 on behalf of I18N WG [Comment] Comment from the i18n review of: link Comment 7 At link Editorial/substantive: E Owner: FS Location in reviewed document: Sec.2.3 [link] Comment: In some character encodings like UTF-8, scripts with a similar number of characters (e.g. latin versus indic scripts) vary in space requirements. To avoid high bandwidth / cost related to scripts, you might propose for such cases the use of the compression scheme for unicode [link] . [Working Group decision] We have not found sufficient support for this encoding scheme in mobile devices. [Commentor reply] | no reply from commenter | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-433 on behalf of I18N WG [Comment] Comment from the i18n review of: link Comment 18 At link Editorial/substantive: S Owner: RI Location in reviewed document: 5.4.12 Comment: The section mentions the use of the XML declaration for declaring in-document the encoding of XML documents, but makes no mention of the standard in-document declaration of encoding for HTML documents or XHTML served as text/html, which uses the Content-Type meta element. This seems a strange omission. Please add text describing this. [Working Group decision] We have added a link to the I18N tutorial on specifying the encoding and have added the specific case you mention in the related technique: link (note that the document only focuses on XHTML, not on HTML) [Commentor reply] | no reply from commenter | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-436 on behalf of I18N WG [Comment] Comment from the i18n review of: link Comment 21 At link Editorial/substantive: S Owner: RI Location in reviewed document: General Comment: We believe the document should encourage all participants in the mobile value chain to support Unicode. This is extremely helpful in ensuring international use of this technology and ease of localization of content. [Working Group decision] After futher discussion with Richard Ishida, we have added more specific recommendations as to why using Unicode is a smart thing to do: "Encoding of the content to a desired character encoding is dependent on the authoring tools being used, Web server configuration and the server side scripting technology being used (if any). For a discussion of this see [CHARSET1] and [CHARSET2]. Unicode is a good choice for representing content when served in multiple languages. The amount of bandwidth required to transmit content can vary significantly depending on the character encoding used. Text consisting principally of characters from the Latin alphabet will encode more efficiently in UTF-8, whereas text consisting principally of characters from ideographic scripts will encode more efficiently in UTF-16. When choosing a character encoding, consider the efficiency of the available encodings. Since the Default Delivery Context specifies use only of UTF-8, all applications should support UTF-8. " [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-393 on behalf of Nokia [Comment] 5.4.15 Cache Headers Proposal for adding a statement [CACHE_CLOCK_SKEW]. Ensure the site will function acceptably without cache, but explicitly set cache headers with long expiration times to allow for clock or time zone inaccuracy in the client. [Working Group decision] Timezone inaccuracies in the client don't normally affect caching since it relies on GMT time. Clock skews aren't specific to mobile devices and should be handled as a case of deficiency in the implementation when specific to a given mobile device. As such, we haven't modified the document, but would welcome a technique on this specific item: link [Commentor reply] | no reply from commenter | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-366 Bruno von Niman (ANEC W3C) on behalf of ANEC [Comment] We believe that Web site access through mobile devices would benefit from the provision of some minimum-level requirements on terminal capabilities and browser features. If this cannot be achieved, other work should be referenced. [Working Group decision] The Default Delivery Context (section 1.4 in the Last Call Working Draft) provides the assumed minimum-level requirements alluded to. [Commentor reply] | no reply from commenter | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-367 Bruno von Niman (ANEC W3C) on behalf of ANEC [Comment] Accessibility should be addressed more specifically, as the mobile Web (and its specific issues) does not seem to be in the scope of the WAI/WCAG guidelines 2.0, currently under updating. The provided cross-referencing is beneficial but it does not provide enough substance. [Working Group decision] The group took inspiration from WCAG 1.0 (and links back to it), but the accessibility experts are in the WAI groups. As such, we think further work on accessibility in the mobile context is out of our scope. [Commentor reply] | no reply from commenter | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-368 Bruno von Niman (ANEC W3C) on behalf of ANEC [Comment] Access to the mobile Web through a speech user interface is not covered by the present draft version. We believe it should be addressed (also as there is excellent work in W3C to cross-reference), as it is an important accessibility enabler to young and older users and users with temporary or permanent functional abilities. [Working Group decision] This is out of scope of the current phase of work of the Best Practices, as stated in our scope document: """ As the Mobile Web Initiative is primarily concerned with accessing content that would currently be rendered in a desktop or laptop browser, the BPWG's focus is currently on best practices that are most pertinent to "traditional" browsing. However, in future phases, the group may broaden the scope of its work in order to take into account other content presentation options that may be available on mobile devices - e.g., using the emerging multimodal technologies.""" link [Commentor reply] | no reply from commenter | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-370 Bruno von Niman (ANEC W3C) on behalf of ANEC [Comment] Setup and configuration is currently considered by consumers as a major difficulty, when trying to access mobile services and applications. As this document does not address setup and configuration-specific issues and it does not provide such guidelines, it should reference available recommendations and best practices developed in other standard bodies and fora, in order to improve the user experience. [Working Group decision] Setup and configuration is out of scope for the Mobile Web Best Practices which only focus on the delivery of content to Mobile Web devices. [Commentor reply] | no reply from commenter | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-385 Bruno von Niman (ANEC W3C) on behalf of ANEC [Comment] Chapter 5.2.2.2, How to do it: Provide advice on how to implement device-based wrapping. [Working Group decision] The group thinks this topic would be a better fit as part of the techniques, on which we welcome contributions: link [Commentor reply] | no reply from commenter | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-388 Bruno von Niman (ANEC W3C) on behalf of ANEC [Comment] Chapter 5.4.13, Error messages: The purpose of error messages should be dual: 1. To provide information to the user; and 2. To provide information to the service provider. The recommendation should cover both aspects. [Working Group decision] Telling providers to check their error logs is out of scope for this document. [Commentor reply] | no reply from commenter | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-358 Charles McCathieNevile on behalf of Opera Software [Comment] 3. Security In order to build commercial services on the web, secure connections are necessary. In addition, these are widely implemented already. Is there no requirement to support https connections in the mobile space as a best practice? [Working Group decision] We don't have any best practice regarding security, and deploying a secure service on the Web and on mobile devices require much more guidance than simple best practices. As a consequence, the group doesn't feel the document should talk about HTTPS. [Commentor reply] | no reply from commenter | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-394 Charles McCathieNevile on behalf of Opera Software [Comment] BP Not covered: 1. Don\'t format text as justified. Text aligned to be justified on both sides is often problematic on the web in general - on mobile devices with a relatively small range of fonts and display options, it seriously reduces legibility of content, often at a cost of some extra processing. [Working Group decision] We have added a new best practice on text effects: "[FONTS] Do not rely on support of font related styling." but we think the particular aspect of justification would be better handled by a technique that was started at: link [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-395 Charles McCathieNevile on behalf of Opera Software [Comment] BP Not covered: 2. Identify word breaks. (This is related to the previous point) Long words which can be broken should include useful information about appropriate points to do so by including a or similar. display options, it seriously reduces legibility of content, often at a cost of some extra processing. [Working Group decision] We think this would be a better fit for a technique rather than a specific best practice. A technique has been started in: link [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-267 Ian Jacobs [Comment] "From the perspective of this document this means that services should be available as some variant of HTML over HTTP." Why is the previous statement here? It sounds like it is an assumption about delivery and belongs in the next section. [Working Group decision] Yes and no: yes, HTTP has been added in the default delivery context -- but no, it also belongs here -- as a clarification of what "One Web" means in the context of this document. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-285 Ian Jacobs [Comment] * The word "exploit" seems like it is being used in the French sense of "make use of". I find that in (American) English it carries a negative connotation, as when one "exploits" a security hole. * This statement is so broad that it should be dropped as a best practice note. Instead, I recommend that you create a section a the top of the document that explains what the best practices notes strive to allow people to do. For example: By following the guidance of this document, designers can: * Learn to optimize their designs for delivery to a mobile device by taking full advantage of device capabilities. * .... In short, this best practice note doesn't actually teach me anything useful. Instead, I would like to learn from the document how to do the thing you are talking about. I realize that there is an "abstract" layer and a "techniques" layer and that the abstract point is to take advantage of device capabilities, but I do not believe you have captured the right level in the above note. Instead, if you are thinking of one or two slightly more specific points, I recommend stating those instead of this very general point. [Working Group decision] * "exploit is the word used in the Device Independence authoring techniques, so we prefer being consistent with them * we think it is important to inform the reader that a good user experience on a mobile devices needs most of the time to be adapated to the device * the techniques document is the place where the reader can learn more on actual ways to learn about device capabilitiles * we have also clarified that we mean more client capabilities than just the ones required to implement the other best practices. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-287 Ian Jacobs [Comment] * Please delete "reasonable" (if you keep this one). [Working Group decision] We think that reasonable is an appropriate word to use. We expect you to try, but don't expect you to break your back. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-288 Ian Jacobs [Comment] * This can be a dangerous point if not worded carefully. See the relatedprinciple in Webarch: " Agents that recover from error by making a choice without the user's consent are not acting on the user's behalf." I realize that in this context one may not always be interacting directly with the user. But "silently recovering from error" is one of the things that I believe the TAG feels strongly is a bad thing. [Working Group decision] The "silently recovering from error" point is relevant to user agent requirements which is out of scope. We believe the text already addresses the issues you've raised. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
2ed08599_ices_1_0_dated_January_13_2006__Commentor_reply | [Commentor] LC-290 Ian Jacobs [Comment] * Below you say something more interesting, which I paraphrase as "It's ok to not follow some of the other best practices in this document when you need to work around errors." That's a big gate and you should strive to narrow it. Furthermore, you seem to define conformance below "then content providers must comply..." Does that statement belong in 5.1.3.1 or is it a general statement that belongs in a conformance section? [Working Group decision] We decided to keep the best practice as is, but we have added text to the default delivery context to mention that no get-out clauses apply in the default delivery context. [Commentor reply] | yes | [
[
"n",
"o",
" ",
"r",
"e",
"p",
"l",
"y",
" ",
"f",
"r",
"o",
"m",
" ",
"c",
"o",
"m",
"m",
"e",
"n",
"t",
"e",
"r"
],
[
"y",
"e",
"s"
]
] | Disposition of Last Call comments for the Mobile Web Best Practices 1.0 dated January 13 2006 | Commentor reply | http://www.w3.org/2006/04/mwbp-doc | 27/1438042989826.86_20150728002309-00056-ip-10-236-191-2_836737130_0.json |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.