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
b959d542_all_Control__CCXML_Version_1_0__Description
[Name] hints [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression that returns an ECMAScript object [Description]
The ECMAScript object returned contains information which may be used by the implementing platform to configure the event processor. The meaning of these hints is specific to the implementing platform and the event processor.
[]
Voice Browser Call Control: CCXML Version 1.0
Description
http://www.w3.org/TR/2005/WD-ccxml-20050111/ccxml-change.html
10/1438042992201.62_20150728002312-00248-ip-10-236-191-2_810991988_47.json
ff099dc9_all_Control__CCXML_Version_1_0__Attribute_Name
[Details] an ECMAScript expression which returns the URI of the CCXML document to be fetched. [Attribute Name]
next
[ [ "n", "e", "x", "t" ], [ "n", "a", "m", "e", "l", "i", "s", "t" ], [ "m", "e", "t", "h", "o", "d" ], [ "f", "e", "t", "c", "h", "i", "d" ], [ "s", "y", "n", "c", "h" ], [ "t", "i", "m", "e", "o", "u", "t" ] ]
Voice Browser Call Control: CCXML Version 1.0
Attribute Name
http://www.w3.org/TR/2005/WD-ccxml-20050111/ccxml-change.html
10/1438042992201.62_20150728002312-00248-ip-10-236-191-2_810991988_7.json
ff099dc9_all_Control__CCXML_Version_1_0__Attribute_Name
[Details] a list of zero or more whitespace separated CCXML variable names. These variable names and their associated values will be included in the URI sent to the server, with the same qualification used in the namelist. [Attribute Name]
namelist
[ [ "n", "e", "x", "t" ], [ "n", "a", "m", "e", "l", "i", "s", "t" ], [ "m", "e", "t", "h", "o", "d" ], [ "f", "e", "t", "c", "h", "i", "d" ], [ "s", "y", "n", "c", "h" ], [ "t", "i", "m", "e", "o", "u", "t" ] ]
Voice Browser Call Control: CCXML Version 1.0
Attribute Name
http://www.w3.org/TR/2005/WD-ccxml-20050111/ccxml-change.html
10/1438042992201.62_20150728002312-00248-ip-10-236-191-2_810991988_7.json
ff099dc9_all_Control__CCXML_Version_1_0__Attribute_Name
[Details] an ECMAScript expression which returns a character string that indicates the HTTP method to use. Valid values are " get " and " post ". The default is " get ". [Attribute Name]
method
[ [ "n", "e", "x", "t" ], [ "n", "a", "m", "e", "l", "i", "s", "t" ], [ "m", "e", "t", "h", "o", "d" ], [ "f", "e", "t", "c", "h", "i", "d" ], [ "s", "y", "n", "c", "h" ], [ "t", "i", "m", "e", "o", "u", "t" ] ]
Voice Browser Call Control: CCXML Version 1.0
Attribute Name
http://www.w3.org/TR/2005/WD-ccxml-20050111/ccxml-change.html
10/1438042992201.62_20150728002312-00248-ip-10-236-191-2_810991988_7.json
ff099dc9_all_Control__CCXML_Version_1_0__Attribute_Name
[Details] is an ECMAScript left-hand-side expression which receives an internally generated unique string identifier to be associated with the completion event. This identifier can be tested by the fetch completion event handler to distinguish among several outstanding fetch requests. If this attribute is not specified, the fetch ID can be acquired from the fetch completion event. Every fetch request will receive a unique fetch ID, even requests for the same document. [Attribute Name]
fetchid
[ [ "n", "e", "x", "t" ], [ "n", "a", "m", "e", "l", "i", "s", "t" ], [ "m", "e", "t", "h", "o", "d" ], [ "f", "e", "t", "c", "h", "i", "d" ], [ "s", "y", "n", "c", "h" ], [ "t", "i", "m", "e", "o", "u", "t" ] ]
Voice Browser Call Control: CCXML Version 1.0
Attribute Name
http://www.w3.org/TR/2005/WD-ccxml-20050111/ccxml-change.html
10/1438042992201.62_20150728002312-00248-ip-10-236-191-2_810991988_7.json
ff099dc9_all_Control__CCXML_Version_1_0__Attribute_Name
[Details] is an ECMAScript left-hand-side expression that is set to the fetch completion event. The specification of this attribute in a implies a blocking fetch, which will be executed synchronously. If this attribute is not specified, the fetch is asynchronous. [Attribute Name]
synch
[ [ "n", "e", "x", "t" ], [ "n", "a", "m", "e", "l", "i", "s", "t" ], [ "m", "e", "t", "h", "o", "d" ], [ "f", "e", "t", "c", "h", "i", "d" ], [ "s", "y", "n", "c", "h" ], [ "t", "i", "m", "e", "o", "u", "t" ] ]
Voice Browser Call Control: CCXML Version 1.0
Attribute Name
http://www.w3.org/TR/2005/WD-ccxml-20050111/ccxml-change.html
10/1438042992201.62_20150728002312-00248-ip-10-236-191-2_810991988_7.json
ff099dc9_all_Control__CCXML_Version_1_0__Attribute_Name
[Details] is an ECMAScript expression returning a string in CSS2 [CSS2] format interpreted as a time interval. The interval begins when the is executed. The fetch will fail if not completed at the end of this interval. A failed fetch will return the error.fetch event. [Attribute Name]
timeout
[ [ "n", "e", "x", "t" ], [ "n", "a", "m", "e", "l", "i", "s", "t" ], [ "m", "e", "t", "h", "o", "d" ], [ "f", "e", "t", "c", "h", "i", "d" ], [ "s", "y", "n", "c", "h" ], [ "t", "i", "m", "e", "o", "u", "t" ] ]
Voice Browser Call Control: CCXML Version 1.0
Attribute Name
http://www.w3.org/TR/2005/WD-ccxml-20050111/ccxml-change.html
10/1438042992201.62_20150728002312-00248-ip-10-236-191-2_810991988_7.json
31ba77e1_all_Control__CCXML_Version_1_0__Valid_Values
[Name] src [Required] false [Attribute Constraints] This attribute may not be specified in conjunction with the prepareddialogid attribute. [Type] ECMAScript Expression [Default Value] none [Description] An ECMAScript expression which returns a character string identifying the URI of the dialog document that the dialog interpreter should load and begin execution upon startup. [Valid Values]
a valid Dialog URL
[]
Voice Browser Call Control: CCXML Version 1.0
Valid Values
http://www.w3.org/TR/2005/WD-ccxml-20050111/ccxml-change.html
10/1438042992201.62_20150728002312-00248-ip-10-236-191-2_810991988_23.json
31ba77e1_all_Control__CCXML_Version_1_0__Valid_Values
[Name] prepareddialogid [Required] false [Attribute Constraints] This attribute may not be specified in conjunction with the src, type or namelist attributes. [Type] ECMAScript Expression [Default Value] none [Description] An ECMAScript expression which returns a dialog identifier of a dialog previously prepared by the execution of a dialogprepare element. If the specified dialog identifier refers to an unknown dialog or a dialog that has already been executed, by way of another dialogstart element, an error.dialogwrongstate event is thrown. [Valid Values]
a valid dialogid
[]
Voice Browser Call Control: CCXML Version 1.0
Valid Values
http://www.w3.org/TR/2005/WD-ccxml-20050111/ccxml-change.html
10/1438042992201.62_20150728002312-00248-ip-10-236-191-2_810991988_23.json
31ba77e1_all_Control__CCXML_Version_1_0__Valid_Values
[Name] type [Required] false [Attribute Constraints] This attribute may not be specified in conjunction with the prepareddialogid attribute. [Type] ECMAScript Expression [Default Value] application/voicexml+xml [Description] An ECMAScript expression which returns a character string that specifies the MIME type of the document, and as a result determines which dialog manager environment is actually used. Values defined by the specification are: application/voicexml+xml This MIME type would request a VoiceXML interpreter instance. audio/wav This MIME type would request a dialog manager that merely plays wave files. [Valid Values]
a Valid MIME Type
[]
Voice Browser Call Control: CCXML Version 1.0
Valid Values
http://www.w3.org/TR/2005/WD-ccxml-20050111/ccxml-change.html
10/1438042992201.62_20150728002312-00248-ip-10-236-191-2_810991988_23.json
31ba77e1_all_Control__CCXML_Version_1_0__Valid_Values
[Name] namelist [Required] false [Attribute Constraints] This attribute may not be specified in conjunction with the prepareddialogid attribute. [Type] Var List [Default Value] none [Description] A list of one or more whitespace separated CCXML variable names. These variables will be submitted to the server, with the same qualification as used in the namelist. When an ECMAscript variable is submitted to the server, its value is first converted into a string before being submitted. If the variable is an ECMAScript Object, the mechanism by which it is submitted is not currently defined. Instead of submitting ECMAScript Objects directly, the application developer may explicitly submit the properties of an Object. e.g. "date.month date.year". [Valid Values]
List of ECMAScript Variable names
[]
Voice Browser Call Control: CCXML Version 1.0
Valid Values
http://www.w3.org/TR/2005/WD-ccxml-20050111/ccxml-change.html
10/1438042992201.62_20150728002312-00248-ip-10-236-191-2_810991988_23.json
31ba77e1_all_Control__CCXML_Version_1_0__Valid_Values
[Name] dialogid [Required] false [Type] ECMAScript Left Hand Side Expression [Default Value] none [Description] An ECMAScript left hand side expression evaluating to a previously defined variable. The value of the attribute will receive a dialog identifier value for the launched dialog interpreter instance. This identifier may be used on future invocations of dialogterminate, join, or unjoin. [Valid Values]
ECMAScript Variable
[]
Voice Browser Call Control: CCXML Version 1.0
Valid Values
http://www.w3.org/TR/2005/WD-ccxml-20050111/ccxml-change.html
10/1438042992201.62_20150728002312-00248-ip-10-236-191-2_810991988_23.json
31ba77e1_all_Control__CCXML_Version_1_0__Valid_Values
[Name] connectionid [Required] false [Attribute Constraints] Can not be used with conferenceid. [Type] ECMAScript Expression [Default Value] comes from the event being processed [Description] An Optional ECMAScript expression which returns the identifier of a connection. The specified connection will be associated with the dialog being prepared. If both the connectionid and the conferenceid are omitted and the dialog was previously prepared using a dialogprepare element with a connectionid or conferenceid specified, the interpreter will use the id as specified on the dialogprepare element. If neither the connectionid or conferenceid is specified and the dialog had not previously been prepared, the interpreter will use the id indicated in the current event being processed. For more information about connections and bridges, refer to Section 10 . If both connectionid and conferenceid are specified, an error.fetch event will be thrown. If the attribute value is invalid or there is no valid default value, an error.semantic event will be thrown. [Valid Values]
Connection IDs
[]
Voice Browser Call Control: CCXML Version 1.0
Valid Values
http://www.w3.org/TR/2005/WD-ccxml-20050111/ccxml-change.html
10/1438042992201.62_20150728002312-00248-ip-10-236-191-2_810991988_23.json
31ba77e1_all_Control__CCXML_Version_1_0__Valid_Values
[Name] conferenceid [Required] false [Attribute Constraints] Can not be used with connectionid. [Type] ECMAScript Expression [Default Value] comes from the event being processed [Description] An Optional ECMAScript expression which returns the identifier of a conference bridge. If both the connectionid and the conferenceid are omitted and the dialog was previously prepared using a dialogprepare element with a connectionid or conferenceid specified, the interpreter will use the id as specified on the dialogprepare element. If neither the connectionid or conferenceid is specified and the dialog had not previously been prepared, the interpreter will use the id indicated in the current event being processed. For more information about connections and bridges, refer to Section 10 . If both connectionid and conferenceid are specified, an error.fetch event will be thrown. If the attribute value is invalid or there is no valid default value, an error.semantic event will be thrown. [Valid Values]
Conference IDs
[]
Voice Browser Call Control: CCXML Version 1.0
Valid Values
http://www.w3.org/TR/2005/WD-ccxml-20050111/ccxml-change.html
10/1438042992201.62_20150728002312-00248-ip-10-236-191-2_810991988_23.json
31ba77e1_all_Control__CCXML_Version_1_0__Valid_Values
[Name] mediadirection [Required] false [Attribute Constraints] If used in conjunction with prepareddialogid , the bridge type must match that used on the previous dialogprepare element. [Type] ECMAScript Expression [Default Value] both [Description] An ECMAScript expression that defines the direction of the media flow between the Dialog and the Connection or Conference. The following values can be used: both Specifies a full duplex connection where the media flows in both directions. dialogtransmit The dialog transmits media to the Connection or Conference but does not receive any media streams. dialogreceive The dialog receives media from the Connection or Conference but does not transmit any media streams. If both the mediadirection and the prepareddialogid are specified and the bridge type specified by the mediadirection attribute does not match that used on the previous dialogprepare element, an error.dialog.notstarted event will be raised. If no value for the mediadirection attribute was specified on the previous dialogprepare element, any mediadirection type option may be specified. [Valid Values]
both dialogtransmit dialogreceive
[]
Voice Browser Call Control: CCXML Version 1.0
Valid Values
http://www.w3.org/TR/2005/WD-ccxml-20050111/ccxml-change.html
10/1438042992201.62_20150728002312-00248-ip-10-236-191-2_810991988_23.json
31ba77e1_all_Control__CCXML_Version_1_0__Valid_Values
[Name] maxage [Required] false [Attribute Constraints] This attribute may not be specified in conjunction with the prepareddialogid attribute. [Type] ECMAScript Expression [Default Value] none [Description] The character string returned is interpreted as a time interval. This indicates that the document is willing to use content whose age is no greater than the specified time in seconds (cf. 'max-age' in HTTP 1.1 [RFC2616]). The document is not willing to use stale content, unless maxstale is also provided. [Valid Values]
An ECMAScript expression which returns a valid time value for the HTTP 1.1 request [RFC2616]
[]
Voice Browser Call Control: CCXML Version 1.0
Valid Values
http://www.w3.org/TR/2005/WD-ccxml-20050111/ccxml-change.html
10/1438042992201.62_20150728002312-00248-ip-10-236-191-2_810991988_23.json
31ba77e1_all_Control__CCXML_Version_1_0__Valid_Values
[Name] maxstale [Required] false [Attribute Constraints] This attribute may not be specified in conjunction with the prepareddialogid attribute. [Type] ECMAScript Expression [Default Value] none [Description] The character string returned is interpreted as a time interval. This indicates that the document is willing to use content that has exceeded its expiration time (cf. 'max-age' in HTTP 1.1 [RFC2616]). If maxstale is assigned a value, then the document is willing to accept content that has exceeded its expiration time by no more than the specified number of seconds. [Valid Values]
An ECMAScript expression which returns a valid time value for the HTTP 1.1 request [RFC2616]
[]
Voice Browser Call Control: CCXML Version 1.0
Valid Values
http://www.w3.org/TR/2005/WD-ccxml-20050111/ccxml-change.html
10/1438042992201.62_20150728002312-00248-ip-10-236-191-2_810991988_23.json
31ba77e1_all_Control__CCXML_Version_1_0__Valid_Values
[Name] enctype [Required] false [Attribute Constraints] This attribute may not be specified in conjunction with the prepareddialogid attribute. Valid only when the value of the method is "post". [Type] ECMAScript Expression [Default Value] application/x-www-form-urlencoded [Description] An ECMAScript expression which returns a character string that indicates the media encoding type of the submitted document (when the value of the method is "post"). Values defined by the specification are: application/x-www-form-urlencoded This indicates that the ccxml variables specified in the namelist will be url encoded. [Valid Values]
valid media encoding type
[]
Voice Browser Call Control: CCXML Version 1.0
Valid Values
http://www.w3.org/TR/2005/WD-ccxml-20050111/ccxml-change.html
10/1438042992201.62_20150728002312-00248-ip-10-236-191-2_810991988_23.json
31ba77e1_all_Control__CCXML_Version_1_0__Valid_Values
[Name] method [Required] false [Attribute Constraints] This attribute may not be specified in conjunction with the prepareddialogid attribute. [Type] ECMAScript Expression [Default Value] get [Description] An ECMAScript expression which returns a character string that indicates the HTTP method to use. Values defined by the specification are: get This indicates that the "GET" method will be used by the dialog manager. post This indicates that the "POST" method will be used by the dialog manager. [Valid Values]
get post
[]
Voice Browser Call Control: CCXML Version 1.0
Valid Values
http://www.w3.org/TR/2005/WD-ccxml-20050111/ccxml-change.html
10/1438042992201.62_20150728002312-00248-ip-10-236-191-2_810991988_23.json
79659038_HTML_Elements_input___W3C_Wiki__State
[Keyword] hidden [Data type] An arbitrary string [Control type] n/a [State]
Hidden
[]
HTML/Elements/input - W3C Wiki
State
http://www.w3.org/wiki/index.php?title=HTML/Elements/input&redirect=no
10/1438042992201.62_20150728002312-00036-ip-10-236-191-2_807597332_0.json
79659038_HTML_Elements_input___W3C_Wiki__State
[Keyword] text [Data type] Text with no line breaks [Control type] Text field [State]
Text
[]
HTML/Elements/input - W3C Wiki
State
http://www.w3.org/wiki/index.php?title=HTML/Elements/input&redirect=no
10/1438042992201.62_20150728002312-00036-ip-10-236-191-2_807597332_0.json
79659038_HTML_Elements_input___W3C_Wiki__State
[Keyword] search [Data type] Text with no line breaks [Control type] Search field [State]
Search
[]
HTML/Elements/input - W3C Wiki
State
http://www.w3.org/wiki/index.php?title=HTML/Elements/input&redirect=no
10/1438042992201.62_20150728002312-00036-ip-10-236-191-2_807597332_0.json
79659038_HTML_Elements_input___W3C_Wiki__State
[Keyword] tel [Data type] Text with no line breaks [Control type] A text field [State]
Telephone
[]
HTML/Elements/input - W3C Wiki
State
http://www.w3.org/wiki/index.php?title=HTML/Elements/input&redirect=no
10/1438042992201.62_20150728002312-00036-ip-10-236-191-2_807597332_0.json
79659038_HTML_Elements_input___W3C_Wiki__State
[Keyword] url [Data type] An absolute IRI [Control type] A text field [State]
URL
[]
HTML/Elements/input - W3C Wiki
State
http://www.w3.org/wiki/index.php?title=HTML/Elements/input&redirect=no
10/1438042992201.62_20150728002312-00036-ip-10-236-191-2_807597332_0.json
79659038_HTML_Elements_input___W3C_Wiki__State
[Keyword] email [Data type] An e-mail address or list of e-mail addresses [Control type] A text field [State]
E-mail
[]
HTML/Elements/input - W3C Wiki
State
http://www.w3.org/wiki/index.php?title=HTML/Elements/input&redirect=no
10/1438042992201.62_20150728002312-00036-ip-10-236-191-2_807597332_0.json
79659038_HTML_Elements_input___W3C_Wiki__State
[Keyword] password [Data type] Text with no line breaks (sensitive information) [Control type] Text field that obscures data entry [State]
Password
[]
HTML/Elements/input - W3C Wiki
State
http://www.w3.org/wiki/index.php?title=HTML/Elements/input&redirect=no
10/1438042992201.62_20150728002312-00036-ip-10-236-191-2_807597332_0.json
79659038_HTML_Elements_input___W3C_Wiki__State
[Keyword] datetime [Data type] A date and time (year, month, day, hour, minute, second, fraction of a second) with the time zone set to UTC [Control type] A date and time control [State]
Date and Time
[]
HTML/Elements/input - W3C Wiki
State
http://www.w3.org/wiki/index.php?title=HTML/Elements/input&redirect=no
10/1438042992201.62_20150728002312-00036-ip-10-236-191-2_807597332_0.json
79659038_HTML_Elements_input___W3C_Wiki__State
[Keyword] date [Data type] A date (year, month, day) with no time zone [Control type] A date control [State]
Date
[]
HTML/Elements/input - W3C Wiki
State
http://www.w3.org/wiki/index.php?title=HTML/Elements/input&redirect=no
10/1438042992201.62_20150728002312-00036-ip-10-236-191-2_807597332_0.json
79659038_HTML_Elements_input___W3C_Wiki__State
[Keyword] month [Data type] A date consisting of a year and a month with no time zone [Control type] A month control [State]
Month
[]
HTML/Elements/input - W3C Wiki
State
http://www.w3.org/wiki/index.php?title=HTML/Elements/input&redirect=no
10/1438042992201.62_20150728002312-00036-ip-10-236-191-2_807597332_0.json
79659038_HTML_Elements_input___W3C_Wiki__State
[Keyword] week [Data type] A date consisting of a week-year number and a week number with no time zone [Control type] A week control [State]
Week
[]
HTML/Elements/input - W3C Wiki
State
http://www.w3.org/wiki/index.php?title=HTML/Elements/input&redirect=no
10/1438042992201.62_20150728002312-00036-ip-10-236-191-2_807597332_0.json
79659038_HTML_Elements_input___W3C_Wiki__State
[Keyword] time [Data type] A time (hour, minute, seconds, fractional seconds) with no time zone [Control type] A time control [State]
Time
[]
HTML/Elements/input - W3C Wiki
State
http://www.w3.org/wiki/index.php?title=HTML/Elements/input&redirect=no
10/1438042992201.62_20150728002312-00036-ip-10-236-191-2_807597332_0.json
79659038_HTML_Elements_input___W3C_Wiki__State
[Keyword] datetime-local [Data type] A date and time (year, month, day, hour, minute, second, fraction of a second) with no time zone [Control type] A date and time control [State]
Local Date and Time
[]
HTML/Elements/input - W3C Wiki
State
http://www.w3.org/wiki/index.php?title=HTML/Elements/input&redirect=no
10/1438042992201.62_20150728002312-00036-ip-10-236-191-2_807597332_0.json
79659038_HTML_Elements_input___W3C_Wiki__State
[Keyword] number [Data type] A numerical value [Control type] A text field or spinner control [State]
Number
[]
HTML/Elements/input - W3C Wiki
State
http://www.w3.org/wiki/index.php?title=HTML/Elements/input&redirect=no
10/1438042992201.62_20150728002312-00036-ip-10-236-191-2_807597332_0.json
79659038_HTML_Elements_input___W3C_Wiki__State
[Keyword] range [Data type] A numerical value, with the extra semantic that the exact value is not important [Control type] A slider control or similar [State]
Range
[]
HTML/Elements/input - W3C Wiki
State
http://www.w3.org/wiki/index.php?title=HTML/Elements/input&redirect=no
10/1438042992201.62_20150728002312-00036-ip-10-236-191-2_807597332_0.json
79659038_HTML_Elements_input___W3C_Wiki__State
[Keyword] color [Data type] An sRGB color with 8-bit red, green, and blue components [Control type] A color well [State]
Color
[]
HTML/Elements/input - W3C Wiki
State
http://www.w3.org/wiki/index.php?title=HTML/Elements/input&redirect=no
10/1438042992201.62_20150728002312-00036-ip-10-236-191-2_807597332_0.json
79659038_HTML_Elements_input___W3C_Wiki__State
[Keyword] checkbox [Data type] A set of zero or more values from a predefined list [Control type] A checkbox [State]
Checkbox
[]
HTML/Elements/input - W3C Wiki
State
http://www.w3.org/wiki/index.php?title=HTML/Elements/input&redirect=no
10/1438042992201.62_20150728002312-00036-ip-10-236-191-2_807597332_0.json
79659038_HTML_Elements_input___W3C_Wiki__State
[Keyword] radio [Data type] An enumerated value [Control type] A radio button [State]
Radio Button
[]
HTML/Elements/input - W3C Wiki
State
http://www.w3.org/wiki/index.php?title=HTML/Elements/input&redirect=no
10/1438042992201.62_20150728002312-00036-ip-10-236-191-2_807597332_0.json
79659038_HTML_Elements_input___W3C_Wiki__State
[Keyword] file [Data type] Zero or more files each with a MIME type and optionally a file name [Control type] A label and a button [State]
File Upload
[]
HTML/Elements/input - W3C Wiki
State
http://www.w3.org/wiki/index.php?title=HTML/Elements/input&redirect=no
10/1438042992201.62_20150728002312-00036-ip-10-236-191-2_807597332_0.json
79659038_HTML_Elements_input___W3C_Wiki__State
[Keyword] submit [Data type] An enumerated value, with the extra semantic that it must be the last value selected and initiates form submission [Control type] A button [State]
Submit Button
[]
HTML/Elements/input - W3C Wiki
State
http://www.w3.org/wiki/index.php?title=HTML/Elements/input&redirect=no
10/1438042992201.62_20150728002312-00036-ip-10-236-191-2_807597332_0.json
79659038_HTML_Elements_input___W3C_Wiki__State
[Keyword] image [Data type] A coordinate, relative to a particular image's size, with the extra semantic that it must be the last value selected and initiates form submission [Control type] Either a clickable image, or a button [State]
Image Button
[]
HTML/Elements/input - W3C Wiki
State
http://www.w3.org/wiki/index.php?title=HTML/Elements/input&redirect=no
10/1438042992201.62_20150728002312-00036-ip-10-236-191-2_807597332_0.json
79659038_HTML_Elements_input___W3C_Wiki__State
[Keyword] reset [Data type] n/a [Control type] A button [State]
Reset Button
[]
HTML/Elements/input - W3C Wiki
State
http://www.w3.org/wiki/index.php?title=HTML/Elements/input&redirect=no
10/1438042992201.62_20150728002312-00036-ip-10-236-191-2_807597332_0.json
79659038_HTML_Elements_input___W3C_Wiki__State
[Keyword] button [Data type] n/a [Control type] A button [State]
Button
[]
HTML/Elements/input - W3C Wiki
State
http://www.w3.org/wiki/index.php?title=HTML/Elements/input&redirect=no
10/1438042992201.62_20150728002312-00036-ip-10-236-191-2_807597332_0.json
ae033ee9_cification__XKMS_2_0__Bindings__Payload_Security
[Feature] Dependencies [Transaction Layer Security] Authentication mechanism defined by TLS which clients must implement [Payload Security]
Authentication defined by XKMS specification, client does not need to implement a comprehensive framework
[]
XML Key Management Specification (XKMS 2.0) Bindings
Payload Security
http://www.w3.org/TR/2005/PR-xkms2-bindings-20050502/
10/1438042992201.62_20150728002312-00078-ip-10-236-191-2_815409064_2.json
ae033ee9_cification__XKMS_2_0__Bindings__Payload_Security
[Feature] Use of XML Signature [Transaction Layer Security] Not required [Payload Security]
Uses XML Signature in Enveloped Mode requiring slightly more complex processing
[]
XML Key Management Specification (XKMS 2.0) Bindings
Payload Security
http://www.w3.org/TR/2005/PR-xkms2-bindings-20050502/
10/1438042992201.62_20150728002312-00078-ip-10-236-191-2_815409064_2.json
ae033ee9_cification__XKMS_2_0__Bindings__Payload_Security
[Feature] Support for Routing [Transaction Layer Security] None [Payload Security]
Specification describes bi-lateral authentication only, multi-hop message routing and multi-party transactions are not supported
[]
XML Key Management Specification (XKMS 2.0) Bindings
Payload Security
http://www.w3.org/TR/2005/PR-xkms2-bindings-20050502/
10/1438042992201.62_20150728002312-00078-ip-10-236-191-2_815409064_2.json
ae033ee9_cification__XKMS_2_0__Bindings__Payload_Security
[Feature] Support for Confidentiality [Transaction Layer Security] Supported [Payload Security]
None, although applications may employ TLS to establish a secure channel
[]
XML Key Management Specification (XKMS 2.0) Bindings
Payload Security
http://www.w3.org/TR/2005/PR-xkms2-bindings-20050502/
10/1438042992201.62_20150728002312-00078-ip-10-236-191-2_815409064_2.json
ae033ee9_cification__XKMS_2_0__Bindings__Payload_Security
[Feature] Non-Repudiation [Transaction Layer Security] Requires additional payload security [Payload Security]
Supported
[]
XML Key Management Specification (XKMS 2.0) Bindings
Payload Security
http://www.w3.org/TR/2005/PR-xkms2-bindings-20050502/
10/1438042992201.62_20150728002312-00078-ip-10-236-191-2_815409064_2.json
ae033ee9_cification__XKMS_2_0__Bindings__Payload_Security
[Feature] Unspecified Party Authentication [Transaction Layer Security] Requires additional payload security [Payload Security]
Supported
[]
XML Key Management Specification (XKMS 2.0) Bindings
Payload Security
http://www.w3.org/TR/2005/PR-xkms2-bindings-20050502/
10/1438042992201.62_20150728002312-00078-ip-10-236-191-2_815409064_2.json
ae033ee9_cification__XKMS_2_0__Bindings__Payload_Security
[Feature] Client Authentication [Transaction Layer Security] Supported through certificate client authentication or through use of payload security [Payload Security]
Supported
[]
XML Key Management Specification (XKMS 2.0) Bindings
Payload Security
http://www.w3.org/TR/2005/PR-xkms2-bindings-20050502/
10/1438042992201.62_20150728002312-00078-ip-10-236-191-2_815409064_2.json
3c7e424e_ta_API_for_Media_Resources_1_0__Textual_Description
[Numerical Code] 200 [Example] property delivered correctly [Textual Description]
OK
[ [ "O", "K" ], [ "N", "o", " ", "C", "o", "n", "t", "e", "n", "t" ], [ "P", "a", "r", "t", "i", "a", "l", " ", "C", "o", "n", "t", "e", "n", "t" ], [ "B", "a", "d", " ", "R", "e", "q", "u", "e", "s", "t" ], [ "N", "o", "t", " ", "F", "o", "u", "n", "d" ], [ "U", "n", "s", "u", "p", "p", "o", "r", "t", "e", "d", " ", "M", "e", "d", "i", "a", " ", "T", "y", "p", "e" ], [ "P", "r", "o", "p", "e", "r", "t", "y", " ", "n", "o", "t", " ", "d", "e", "f", "i", "n", "e", "d", " ", "i", "n", " ", "S", "o", "u", "r", "c", "e", " ", "F", "o", "r", "m", "a", "t" ], [ "I", "n", "t", "e", "r", "n", "a", "l", " ", "S", "e", "r", "v", "e", "r", " ", "E", "r", "r", "o", "r" ], [ "P", "r", "o", "p", "e", "r", "t", "y", " ", "n", "o", "t", " ", "s", "u", "p", "p", "o", "r", "t", "e", "d" ] ]
Metadata API for Media Resources 1.0
Textual Description
http://www.w3.org/TR/mediaont-api-1.0/
10/1438042992201.62_20150728002312-00020-ip-10-236-191-2_812491962_7.json
3c7e424e_ta_API_for_Media_Resources_1_0__Textual_Description
[Numerical Code] 204 [Example] property retrieved without content [Textual Description]
No Content
[ [ "O", "K" ], [ "N", "o", " ", "C", "o", "n", "t", "e", "n", "t" ], [ "P", "a", "r", "t", "i", "a", "l", " ", "C", "o", "n", "t", "e", "n", "t" ], [ "B", "a", "d", " ", "R", "e", "q", "u", "e", "s", "t" ], [ "N", "o", "t", " ", "F", "o", "u", "n", "d" ], [ "U", "n", "s", "u", "p", "p", "o", "r", "t", "e", "d", " ", "M", "e", "d", "i", "a", " ", "T", "y", "p", "e" ], [ "P", "r", "o", "p", "e", "r", "t", "y", " ", "n", "o", "t", " ", "d", "e", "f", "i", "n", "e", "d", " ", "i", "n", " ", "S", "o", "u", "r", "c", "e", " ", "F", "o", "r", "m", "a", "t" ], [ "I", "n", "t", "e", "r", "n", "a", "l", " ", "S", "e", "r", "v", "e", "r", " ", "E", "r", "r", "o", "r" ], [ "P", "r", "o", "p", "e", "r", "t", "y", " ", "n", "o", "t", " ", "s", "u", "p", "p", "o", "r", "t", "e", "d" ] ]
Metadata API for Media Resources 1.0
Textual Description
http://www.w3.org/TR/mediaont-api-1.0/
10/1438042992201.62_20150728002312-00020-ip-10-236-191-2_812491962_7.json
3c7e424e_ta_API_for_Media_Resources_1_0__Textual_Description
[Numerical Code] 206 [Example] only a subset of the available data stored in the result set [Textual Description]
Partial Content
[ [ "O", "K" ], [ "N", "o", " ", "C", "o", "n", "t", "e", "n", "t" ], [ "P", "a", "r", "t", "i", "a", "l", " ", "C", "o", "n", "t", "e", "n", "t" ], [ "B", "a", "d", " ", "R", "e", "q", "u", "e", "s", "t" ], [ "N", "o", "t", " ", "F", "o", "u", "n", "d" ], [ "U", "n", "s", "u", "p", "p", "o", "r", "t", "e", "d", " ", "M", "e", "d", "i", "a", " ", "T", "y", "p", "e" ], [ "P", "r", "o", "p", "e", "r", "t", "y", " ", "n", "o", "t", " ", "d", "e", "f", "i", "n", "e", "d", " ", "i", "n", " ", "S", "o", "u", "r", "c", "e", " ", "F", "o", "r", "m", "a", "t" ], [ "I", "n", "t", "e", "r", "n", "a", "l", " ", "S", "e", "r", "v", "e", "r", " ", "E", "r", "r", "o", "r" ], [ "P", "r", "o", "p", "e", "r", "t", "y", " ", "n", "o", "t", " ", "s", "u", "p", "p", "o", "r", "t", "e", "d" ] ]
Metadata API for Media Resources 1.0
Textual Description
http://www.w3.org/TR/mediaont-api-1.0/
10/1438042992201.62_20150728002312-00020-ip-10-236-191-2_812491962_7.json
3c7e424e_ta_API_for_Media_Resources_1_0__Textual_Description
[Numerical Code] 400 [Example] syntactical error [Textual Description]
Bad Request
[ [ "O", "K" ], [ "N", "o", " ", "C", "o", "n", "t", "e", "n", "t" ], [ "P", "a", "r", "t", "i", "a", "l", " ", "C", "o", "n", "t", "e", "n", "t" ], [ "B", "a", "d", " ", "R", "e", "q", "u", "e", "s", "t" ], [ "N", "o", "t", " ", "F", "o", "u", "n", "d" ], [ "U", "n", "s", "u", "p", "p", "o", "r", "t", "e", "d", " ", "M", "e", "d", "i", "a", " ", "T", "y", "p", "e" ], [ "P", "r", "o", "p", "e", "r", "t", "y", " ", "n", "o", "t", " ", "d", "e", "f", "i", "n", "e", "d", " ", "i", "n", " ", "S", "o", "u", "r", "c", "e", " ", "F", "o", "r", "m", "a", "t" ], [ "I", "n", "t", "e", "r", "n", "a", "l", " ", "S", "e", "r", "v", "e", "r", " ", "E", "r", "r", "o", "r" ], [ "P", "r", "o", "p", "e", "r", "t", "y", " ", "n", "o", "t", " ", "s", "u", "p", "p", "o", "r", "t", "e", "d" ] ]
Metadata API for Media Resources 1.0
Textual Description
http://www.w3.org/TR/mediaont-api-1.0/
10/1438042992201.62_20150728002312-00020-ip-10-236-191-2_812491962_7.json
3c7e424e_ta_API_for_Media_Resources_1_0__Textual_Description
[Numerical Code] 404 [Example] the queries resource is not found [Textual Description]
Not Found
[ [ "O", "K" ], [ "N", "o", " ", "C", "o", "n", "t", "e", "n", "t" ], [ "P", "a", "r", "t", "i", "a", "l", " ", "C", "o", "n", "t", "e", "n", "t" ], [ "B", "a", "d", " ", "R", "e", "q", "u", "e", "s", "t" ], [ "N", "o", "t", " ", "F", "o", "u", "n", "d" ], [ "U", "n", "s", "u", "p", "p", "o", "r", "t", "e", "d", " ", "M", "e", "d", "i", "a", " ", "T", "y", "p", "e" ], [ "P", "r", "o", "p", "e", "r", "t", "y", " ", "n", "o", "t", " ", "d", "e", "f", "i", "n", "e", "d", " ", "i", "n", " ", "S", "o", "u", "r", "c", "e", " ", "F", "o", "r", "m", "a", "t" ], [ "I", "n", "t", "e", "r", "n", "a", "l", " ", "S", "e", "r", "v", "e", "r", " ", "E", "r", "r", "o", "r" ], [ "P", "r", "o", "p", "e", "r", "t", "y", " ", "n", "o", "t", " ", "s", "u", "p", "p", "o", "r", "t", "e", "d" ] ]
Metadata API for Media Resources 1.0
Textual Description
http://www.w3.org/TR/mediaont-api-1.0/
10/1438042992201.62_20150728002312-00020-ip-10-236-191-2_812491962_7.json
3c7e424e_ta_API_for_Media_Resources_1_0__Textual_Description
[Numerical Code] 415 [Example] get duration call on an image data store [Textual Description]
Unsupported Media Type
[ [ "O", "K" ], [ "N", "o", " ", "C", "o", "n", "t", "e", "n", "t" ], [ "P", "a", "r", "t", "i", "a", "l", " ", "C", "o", "n", "t", "e", "n", "t" ], [ "B", "a", "d", " ", "R", "e", "q", "u", "e", "s", "t" ], [ "N", "o", "t", " ", "F", "o", "u", "n", "d" ], [ "U", "n", "s", "u", "p", "p", "o", "r", "t", "e", "d", " ", "M", "e", "d", "i", "a", " ", "T", "y", "p", "e" ], [ "P", "r", "o", "p", "e", "r", "t", "y", " ", "n", "o", "t", " ", "d", "e", "f", "i", "n", "e", "d", " ", "i", "n", " ", "S", "o", "u", "r", "c", "e", " ", "F", "o", "r", "m", "a", "t" ], [ "I", "n", "t", "e", "r", "n", "a", "l", " ", "S", "e", "r", "v", "e", "r", " ", "E", "r", "r", "o", "r" ], [ "P", "r", "o", "p", "e", "r", "t", "y", " ", "n", "o", "t", " ", "s", "u", "p", "p", "o", "r", "t", "e", "d" ] ]
Metadata API for Media Resources 1.0
Textual Description
http://www.w3.org/TR/mediaont-api-1.0/
10/1438042992201.62_20150728002312-00020-ip-10-236-191-2_812491962_7.json
3c7e424e_ta_API_for_Media_Resources_1_0__Textual_Description
[Numerical Code] 462 [Example] location is not defined in MediaRSS [Textual Description]
Property not defined in Source Format
[ [ "O", "K" ], [ "N", "o", " ", "C", "o", "n", "t", "e", "n", "t" ], [ "P", "a", "r", "t", "i", "a", "l", " ", "C", "o", "n", "t", "e", "n", "t" ], [ "B", "a", "d", " ", "R", "e", "q", "u", "e", "s", "t" ], [ "N", "o", "t", " ", "F", "o", "u", "n", "d" ], [ "U", "n", "s", "u", "p", "p", "o", "r", "t", "e", "d", " ", "M", "e", "d", "i", "a", " ", "T", "y", "p", "e" ], [ "P", "r", "o", "p", "e", "r", "t", "y", " ", "n", "o", "t", " ", "d", "e", "f", "i", "n", "e", "d", " ", "i", "n", " ", "S", "o", "u", "r", "c", "e", " ", "F", "o", "r", "m", "a", "t" ], [ "I", "n", "t", "e", "r", "n", "a", "l", " ", "S", "e", "r", "v", "e", "r", " ", "E", "r", "r", "o", "r" ], [ "P", "r", "o", "p", "e", "r", "t", "y", " ", "n", "o", "t", " ", "s", "u", "p", "p", "o", "r", "t", "e", "d" ] ]
Metadata API for Media Resources 1.0
Textual Description
http://www.w3.org/TR/mediaont-api-1.0/
10/1438042992201.62_20150728002312-00020-ip-10-236-191-2_812491962_7.json
3c7e424e_ta_API_for_Media_Resources_1_0__Textual_Description
[Numerical Code] 500 [Example] internal library (e.g., extractor) crashes [Textual Description]
Internal Server Error
[ [ "O", "K" ], [ "N", "o", " ", "C", "o", "n", "t", "e", "n", "t" ], [ "P", "a", "r", "t", "i", "a", "l", " ", "C", "o", "n", "t", "e", "n", "t" ], [ "B", "a", "d", " ", "R", "e", "q", "u", "e", "s", "t" ], [ "N", "o", "t", " ", "F", "o", "u", "n", "d" ], [ "U", "n", "s", "u", "p", "p", "o", "r", "t", "e", "d", " ", "M", "e", "d", "i", "a", " ", "T", "y", "p", "e" ], [ "P", "r", "o", "p", "e", "r", "t", "y", " ", "n", "o", "t", " ", "d", "e", "f", "i", "n", "e", "d", " ", "i", "n", " ", "S", "o", "u", "r", "c", "e", " ", "F", "o", "r", "m", "a", "t" ], [ "I", "n", "t", "e", "r", "n", "a", "l", " ", "S", "e", "r", "v", "e", "r", " ", "E", "r", "r", "o", "r" ], [ "P", "r", "o", "p", "e", "r", "t", "y", " ", "n", "o", "t", " ", "s", "u", "p", "p", "o", "r", "t", "e", "d" ] ]
Metadata API for Media Resources 1.0
Textual Description
http://www.w3.org/TR/mediaont-api-1.0/
10/1438042992201.62_20150728002312-00020-ip-10-236-191-2_812491962_7.json
3c7e424e_ta_API_for_Media_Resources_1_0__Textual_Description
[Numerical Code] 562 [Example] a subset of properties implemented [Textual Description]
Property not supported
[ [ "O", "K" ], [ "N", "o", " ", "C", "o", "n", "t", "e", "n", "t" ], [ "P", "a", "r", "t", "i", "a", "l", " ", "C", "o", "n", "t", "e", "n", "t" ], [ "B", "a", "d", " ", "R", "e", "q", "u", "e", "s", "t" ], [ "N", "o", "t", " ", "F", "o", "u", "n", "d" ], [ "U", "n", "s", "u", "p", "p", "o", "r", "t", "e", "d", " ", "M", "e", "d", "i", "a", " ", "T", "y", "p", "e" ], [ "P", "r", "o", "p", "e", "r", "t", "y", " ", "n", "o", "t", " ", "d", "e", "f", "i", "n", "e", "d", " ", "i", "n", " ", "S", "o", "u", "r", "c", "e", " ", "F", "o", "r", "m", "a", "t" ], [ "I", "n", "t", "e", "r", "n", "a", "l", " ", "S", "e", "r", "v", "e", "r", " ", "E", "r", "r", "o", "r" ], [ "P", "r", "o", "p", "e", "r", "t", "y", " ", "n", "o", "t", " ", "s", "u", "p", "p", "o", "r", "t", "e", "d" ] ]
Metadata API for Media Resources 1.0
Textual Description
http://www.w3.org/TR/mediaont-api-1.0/
10/1438042992201.62_20150728002312-00020-ip-10-236-191-2_812491962_7.json
7351e5cc_10_7_The_input_element___HTML5__Control_type
[Keyword] hidden [State] Hidden [Data type] An arbitrary string [Control type]
n/a
[]
4.10.7 The input element — HTML5
Control type
http://www.w3.org/TR/2011/WD-html5-20110525/the-input-element.html
10/1438042988065.26_20150728002308-00029-ip-10-236-191-2_820517405_0.json
7351e5cc_10_7_The_input_element___HTML5__Control_type
[Keyword] text [State] Text [Data type] Text with no line breaks [Control type]
Text field
[]
4.10.7 The input element — HTML5
Control type
http://www.w3.org/TR/2011/WD-html5-20110525/the-input-element.html
10/1438042988065.26_20150728002308-00029-ip-10-236-191-2_820517405_0.json
7351e5cc_10_7_The_input_element___HTML5__Control_type
[Keyword] search [State] Search [Data type] Text with no line breaks [Control type]
Search field
[]
4.10.7 The input element — HTML5
Control type
http://www.w3.org/TR/2011/WD-html5-20110525/the-input-element.html
10/1438042988065.26_20150728002308-00029-ip-10-236-191-2_820517405_0.json
7351e5cc_10_7_The_input_element___HTML5__Control_type
[Keyword] tel [State] Telephone [Data type] Text with no line breaks [Control type]
A text field
[]
4.10.7 The input element — HTML5
Control type
http://www.w3.org/TR/2011/WD-html5-20110525/the-input-element.html
10/1438042988065.26_20150728002308-00029-ip-10-236-191-2_820517405_0.json
7351e5cc_10_7_The_input_element___HTML5__Control_type
[Keyword] url [State] URL [Data type] An absolute IRI [Control type]
A text field
[]
4.10.7 The input element — HTML5
Control type
http://www.w3.org/TR/2011/WD-html5-20110525/the-input-element.html
10/1438042988065.26_20150728002308-00029-ip-10-236-191-2_820517405_0.json
7351e5cc_10_7_The_input_element___HTML5__Control_type
[Keyword] email [State] E-mail [Data type] An e-mail address or list of e-mail addresses [Control type]
A text field
[]
4.10.7 The input element — HTML5
Control type
http://www.w3.org/TR/2011/WD-html5-20110525/the-input-element.html
10/1438042988065.26_20150728002308-00029-ip-10-236-191-2_820517405_0.json
7351e5cc_10_7_The_input_element___HTML5__Control_type
[Keyword] password [State] Password [Data type] Text with no line breaks (sensitive information) [Control type]
Text field that obscures data entry
[]
4.10.7 The input element — HTML5
Control type
http://www.w3.org/TR/2011/WD-html5-20110525/the-input-element.html
10/1438042988065.26_20150728002308-00029-ip-10-236-191-2_820517405_0.json
7351e5cc_10_7_The_input_element___HTML5__Control_type
[Keyword] datetime [State] Date and Time [Data type] A date and time (year, month, day, hour, minute, second, fraction of a second) with the time zone set to UTC [Control type]
A date and time control
[]
4.10.7 The input element — HTML5
Control type
http://www.w3.org/TR/2011/WD-html5-20110525/the-input-element.html
10/1438042988065.26_20150728002308-00029-ip-10-236-191-2_820517405_0.json
7351e5cc_10_7_The_input_element___HTML5__Control_type
[Keyword] date [State] Date [Data type] A date (year, month, day) with no time zone [Control type]
A date control
[]
4.10.7 The input element — HTML5
Control type
http://www.w3.org/TR/2011/WD-html5-20110525/the-input-element.html
10/1438042988065.26_20150728002308-00029-ip-10-236-191-2_820517405_0.json
7351e5cc_10_7_The_input_element___HTML5__Control_type
[Keyword] month [State] Month [Data type] A date consisting of a year and a month with no time zone [Control type]
A month control
[]
4.10.7 The input element — HTML5
Control type
http://www.w3.org/TR/2011/WD-html5-20110525/the-input-element.html
10/1438042988065.26_20150728002308-00029-ip-10-236-191-2_820517405_0.json
7351e5cc_10_7_The_input_element___HTML5__Control_type
[Keyword] week [State] Week [Data type] A date consisting of a week-year number and a week number with no time zone [Control type]
A week control
[]
4.10.7 The input element — HTML5
Control type
http://www.w3.org/TR/2011/WD-html5-20110525/the-input-element.html
10/1438042988065.26_20150728002308-00029-ip-10-236-191-2_820517405_0.json
7351e5cc_10_7_The_input_element___HTML5__Control_type
[Keyword] time [State] Time [Data type] A time (hour, minute, seconds, fractional seconds) with no time zone [Control type]
A time control
[]
4.10.7 The input element — HTML5
Control type
http://www.w3.org/TR/2011/WD-html5-20110525/the-input-element.html
10/1438042988065.26_20150728002308-00029-ip-10-236-191-2_820517405_0.json
7351e5cc_10_7_The_input_element___HTML5__Control_type
[Keyword] datetime-local [State] Local Date and Time [Data type] A date and time (year, month, day, hour, minute, second, fraction of a second) with no time zone [Control type]
A date and time control
[]
4.10.7 The input element — HTML5
Control type
http://www.w3.org/TR/2011/WD-html5-20110525/the-input-element.html
10/1438042988065.26_20150728002308-00029-ip-10-236-191-2_820517405_0.json
7351e5cc_10_7_The_input_element___HTML5__Control_type
[Keyword] number [State] Number [Data type] A numerical value [Control type]
A text field or spinner control
[]
4.10.7 The input element — HTML5
Control type
http://www.w3.org/TR/2011/WD-html5-20110525/the-input-element.html
10/1438042988065.26_20150728002308-00029-ip-10-236-191-2_820517405_0.json
7351e5cc_10_7_The_input_element___HTML5__Control_type
[Keyword] range [State] Range [Data type] A numerical value, with the extra semantic that the exact value is not important [Control type]
A slider control or similar
[]
4.10.7 The input element — HTML5
Control type
http://www.w3.org/TR/2011/WD-html5-20110525/the-input-element.html
10/1438042988065.26_20150728002308-00029-ip-10-236-191-2_820517405_0.json
7351e5cc_10_7_The_input_element___HTML5__Control_type
[Keyword] color [State] Color [Data type] An sRGB color with 8-bit red, green, and blue components [Control type]
A color well
[]
4.10.7 The input element — HTML5
Control type
http://www.w3.org/TR/2011/WD-html5-20110525/the-input-element.html
10/1438042988065.26_20150728002308-00029-ip-10-236-191-2_820517405_0.json
7351e5cc_10_7_The_input_element___HTML5__Control_type
[Keyword] checkbox [State] Checkbox [Data type] A set of zero or more values from a predefined list [Control type]
A checkbox
[]
4.10.7 The input element — HTML5
Control type
http://www.w3.org/TR/2011/WD-html5-20110525/the-input-element.html
10/1438042988065.26_20150728002308-00029-ip-10-236-191-2_820517405_0.json
7351e5cc_10_7_The_input_element___HTML5__Control_type
[Keyword] radio [State] Radio Button [Data type] An enumerated value [Control type]
A radio button
[]
4.10.7 The input element — HTML5
Control type
http://www.w3.org/TR/2011/WD-html5-20110525/the-input-element.html
10/1438042988065.26_20150728002308-00029-ip-10-236-191-2_820517405_0.json
7351e5cc_10_7_The_input_element___HTML5__Control_type
[Keyword] file [State] File Upload [Data type] Zero or more files each with a MIME type and optionally a file name [Control type]
A label and a button
[]
4.10.7 The input element — HTML5
Control type
http://www.w3.org/TR/2011/WD-html5-20110525/the-input-element.html
10/1438042988065.26_20150728002308-00029-ip-10-236-191-2_820517405_0.json
7351e5cc_10_7_The_input_element___HTML5__Control_type
[Keyword] submit [State] Submit Button [Data type] An enumerated value, with the extra semantic that it must be the last value selected and initiates form submission [Control type]
A button
[]
4.10.7 The input element — HTML5
Control type
http://www.w3.org/TR/2011/WD-html5-20110525/the-input-element.html
10/1438042988065.26_20150728002308-00029-ip-10-236-191-2_820517405_0.json
7351e5cc_10_7_The_input_element___HTML5__Control_type
[Keyword] image [State] Image Button [Data type] A coordinate, relative to a particular image's size, with the extra semantic that it must be the last value selected and initiates form submission [Control type]
Either a clickable image, or a button
[]
4.10.7 The input element — HTML5
Control type
http://www.w3.org/TR/2011/WD-html5-20110525/the-input-element.html
10/1438042988065.26_20150728002308-00029-ip-10-236-191-2_820517405_0.json
7351e5cc_10_7_The_input_element___HTML5__Control_type
[Keyword] reset [State] Reset Button [Data type] n/a [Control type]
A button
[]
4.10.7 The input element — HTML5
Control type
http://www.w3.org/TR/2011/WD-html5-20110525/the-input-element.html
10/1438042988065.26_20150728002308-00029-ip-10-236-191-2_820517405_0.json
7351e5cc_10_7_The_input_element___HTML5__Control_type
[Keyword] button [State] Button [Data type] n/a [Control type]
A button
[]
4.10.7 The input element — HTML5
Control type
http://www.w3.org/TR/2011/WD-html5-20110525/the-input-element.html
10/1438042988065.26_20150728002308-00029-ip-10-236-191-2_820517405_0.json
c8a9752f_ta_API_for_Media_Resources_1_0__Example
[Numerical Code] 200 [Textual Description] OK [Example]
property delivered correctly
[]
Metadata API for Media Resources 1.0
Example
http://www.w3.org/TR/mediaont-api-1.0/
10/1438042992201.62_20150728002312-00020-ip-10-236-191-2_812491962_7.json
c8a9752f_ta_API_for_Media_Resources_1_0__Example
[Numerical Code] 204 [Textual Description] No Content [Example]
property retrieved without content
[]
Metadata API for Media Resources 1.0
Example
http://www.w3.org/TR/mediaont-api-1.0/
10/1438042992201.62_20150728002312-00020-ip-10-236-191-2_812491962_7.json
c8a9752f_ta_API_for_Media_Resources_1_0__Example
[Numerical Code] 206 [Textual Description] Partial Content [Example]
only a subset of the available data stored in the result set
[]
Metadata API for Media Resources 1.0
Example
http://www.w3.org/TR/mediaont-api-1.0/
10/1438042992201.62_20150728002312-00020-ip-10-236-191-2_812491962_7.json
c8a9752f_ta_API_for_Media_Resources_1_0__Example
[Numerical Code] 400 [Textual Description] Bad Request [Example]
syntactical error
[]
Metadata API for Media Resources 1.0
Example
http://www.w3.org/TR/mediaont-api-1.0/
10/1438042992201.62_20150728002312-00020-ip-10-236-191-2_812491962_7.json
c8a9752f_ta_API_for_Media_Resources_1_0__Example
[Numerical Code] 404 [Textual Description] Not Found [Example]
the queries resource is not found
[]
Metadata API for Media Resources 1.0
Example
http://www.w3.org/TR/mediaont-api-1.0/
10/1438042992201.62_20150728002312-00020-ip-10-236-191-2_812491962_7.json
c8a9752f_ta_API_for_Media_Resources_1_0__Example
[Numerical Code] 415 [Textual Description] Unsupported Media Type [Example]
get duration call on an image data store
[]
Metadata API for Media Resources 1.0
Example
http://www.w3.org/TR/mediaont-api-1.0/
10/1438042992201.62_20150728002312-00020-ip-10-236-191-2_812491962_7.json
c8a9752f_ta_API_for_Media_Resources_1_0__Example
[Numerical Code] 462 [Textual Description] Property not defined in Source Format [Example]
location is not defined in MediaRSS
[]
Metadata API for Media Resources 1.0
Example
http://www.w3.org/TR/mediaont-api-1.0/
10/1438042992201.62_20150728002312-00020-ip-10-236-191-2_812491962_7.json
c8a9752f_ta_API_for_Media_Resources_1_0__Example
[Numerical Code] 500 [Textual Description] Internal Server Error [Example]
internal library (e.g., extractor) crashes
[]
Metadata API for Media Resources 1.0
Example
http://www.w3.org/TR/mediaont-api-1.0/
10/1438042992201.62_20150728002312-00020-ip-10-236-191-2_812491962_7.json
c8a9752f_ta_API_for_Media_Resources_1_0__Example
[Numerical Code] 562 [Textual Description] Property not supported [Example]
a subset of properties implemented
[]
Metadata API for Media Resources 1.0
Example
http://www.w3.org/TR/mediaont-api-1.0/
10/1438042992201.62_20150728002312-00020-ip-10-236-191-2_812491962_7.json
1b637e8f_traw_poll_and_Balloting_System___optional_version_information_
[Responder] David Baron
Making varying DOCTYPE syntax conforming will make it more likely that browsers to use variations in DOCTYPE decarations to trigger new mode changes, even if the specification declares this to be nonconforming. I believe authors would be more willing to use apparently-non-proprietary mode changing syntax than clearly proprietary markup or clearly-proprietary comment syntax. Having more modes makes it harder for new entrants in the browser market, as I described in http://dbaron.org/log/2007-03#e20070325a , http://lists.w3.org/Archives/Public/public-html/2007Apr/0279.html , and http://lists.w3.org/Archives/Public/www-tag/2009Aug/0054.html . Allowing variations in syntax that are conforming, but do nothing, seems likely to encourage authors to believe that those variations will do something. (Witness, for example, the large numbers of authors who change the "EN" within the HTML 4.0 FPI to their own language code.) Allowing DOCTYPE declarations that can be connected to DTD-based validators encourages people to use inferior DTD-based validation tools rather than a conformant HTML5 conformance checker.
[]
Results of Questionnaire ISSUE-4 & ISSUE-84: HTML5 versioning and doctypes - Straw Poll for Objections - Web-Based Straw-poll and Balloting System
Objections to the Change Proposal to Allow much more general DOCTYPE syntax to be conforming, possibly including optional version information.
http://www.w3.org/2002/09/wbs/40318/issues-4-84-objection-poll/results
10/1438042988065.26_20150728002308-00009-ip-10-236-191-2_814197501_0.json
1b637e8f_traw_poll_and_Balloting_System___optional_version_information_
[Responder] Boris Zbarsky
Fundamentally, if UAs treat all HTML versions as the same there is no need for versioning information. So a proposal to create such information presupposes that UAs will NOT treat versions the same. We have this to a small extent now in terms of quirks mode, and even that is a significant maintenance burden. So in effect, a proposal that we introduce versioning is a proposal that favors big players over small ones in the HTML space: the next obvious course of action is to make sure several incompatible versions of HTML are created and that all need to be supported. This raises barriers to entry into the field, and while it may be good for certain W3C member companies I believe it's very bad for HTML and HTML consumers as a whole. I can see various scenarios where a producer might want to keep internal versioning information, but I believe this can be put in a comment as well as in a doctype, and in any case ideally should be removed before publishing the content (so that conformance issues don't arise even is such tools want to put the information in the doctype). While I agree that it's possible that in the future a situation will arise where HTML documents from that point on need to be differentiated from all preceding ones, such a situation has not arisen in practice in the nearly 20 years of HTML's existence. In the unlikely event that it does arise, that would be the right time to consider adding a version indicator. Clearly this would not be done lightly at that point, but neither should changes to HTML that are backwards-incompatible to the extent envisioned in this scenario be undertaken lightly.
[]
Results of Questionnaire ISSUE-4 & ISSUE-84: HTML5 versioning and doctypes - Straw Poll for Objections - Web-Based Straw-poll and Balloting System
Objections to the Change Proposal to Allow much more general DOCTYPE syntax to be conforming, possibly including optional version information.
http://www.w3.org/2002/09/wbs/40318/issues-4-84-objection-poll/results
10/1438042988065.26_20150728002308-00009-ip-10-236-191-2_814197501_0.json
1b637e8f_traw_poll_and_Balloting_System___optional_version_information_
[Responder] Henri Sivonen
I strongly object to this change proposal. A WBS bug prevented me from posting my objections here, so I posted them to http://lists.w3.org/Archives/Public/www-archive/2010Jul/0124.html as advised by the Team Contact. Please consider that message as if the objections in it were stated here.
[]
Results of Questionnaire ISSUE-4 & ISSUE-84: HTML5 versioning and doctypes - Straw Poll for Objections - Web-Based Straw-poll and Balloting System
Objections to the Change Proposal to Allow much more general DOCTYPE syntax to be conforming, possibly including optional version information.
http://www.w3.org/2002/09/wbs/40318/issues-4-84-objection-poll/results
10/1438042988065.26_20150728002308-00009-ip-10-236-191-2_814197501_0.json
1b637e8f_traw_poll_and_Balloting_System___optional_version_information_
[Responder] Anne van Kesteren
I have the same objections to this proposal as I have had to the ISSUE-88 change proposal to allow something without any observable effect. This will only lead to confusion for authors. http://www.w3.org/2002/09/wbs/40318/issue-88-objection-poll/results In addition, this would give the opportunity for Web browsers to fragment HTML which would be a very bad thing for the Web. If we ever need versioning for HTML (and we have not since HTML was invented) we can add it at that point. Designing for a theoretical future is not at all necessary here and only complicates matters.
[]
Results of Questionnaire ISSUE-4 & ISSUE-84: HTML5 versioning and doctypes - Straw Poll for Objections - Web-Based Straw-poll and Balloting System
Objections to the Change Proposal to Allow much more general DOCTYPE syntax to be conforming, possibly including optional version information.
http://www.w3.org/2002/09/wbs/40318/issues-4-84-objection-poll/results
10/1438042988065.26_20150728002308-00009-ip-10-236-191-2_814197501_0.json
1b637e8f_traw_poll_and_Balloting_System___optional_version_information_
[Responder] James Graham
I strongly object to the proposal to add versioning information in HTML. In general terms, versioning on the UA side is bad for the web, significantly increasing the burden of complexity in new implementations, and therefore reducing competition in the browser space. Versioning is also bad for authors because it means they have to learn magic incantations to opt into the behaviour they expect, leading to confusion when things go wrong due to picking the wrong version. These problems can be seen today with quirks vs limited quirks vs standards modes. Given that switching behaviour based on versions is bad for both end users and authors, we should be designing the language to make it difficult for UAs to version switch, even if it is in their interests to do so, because it is not in the interests of the web as a whole. Although the change proposal makes some attempt to limit the scope of when versioning information is permitted and how UAs may react to it, it seems foolish to rely on both authors and vendors following such a complex set of rules when the downsides of breaking them is so great. In particular if UA vendors break the rules. costs are mostly in the form of externalities incurred by other vendors, authors and ultimately end users. We should be working to avoid such things, not encouraging them by making them easy. The suggested rules continually refer to "controlled environments". This implies that the change proposal is mainly concerned with non-web use cases. I do not believe we should give priority to non-web use cases particularly when they directly conflict with the requirements for the web. I also note that were these rules to be followed, and versioning only used in non-web applications, several of the supposed benefits of versioning could not actually occur in the manner described, unless we believe the argument that an unused syntactic construct is materially different from one that does not exist. However it is not clear why this is so; for example one suggested benefit of versioning is continuity of conformance for existing documents in the face of changes to the conformance requirements of the language. It is hard to see how this is realised in the case where there is a versioning mechanism that a document is not permitted to use, but not in the case where there is no versioning mechanism. In this sense I believe that the proposal is internally inconsistent. This inconsistency would be more troubling if the purported benefits of versioning were real. However I believe they are not, and agree with the criticisms that Henri made in his response. It has been suggested that non-browser UAs, in particular editors (or "editing workflows"), may benefit from versioning information. However it is not clear why this would be uniquely important, or even necessary, metadata for an editor. Such a UA may also want to store information such as the current cursor position, or details of the allowed features according to a specific set of browsers that the author wished to target. I do not think such UAs benefit substantially from a version indicator and certainly I see no need to raise it to a privileged position above all other possible metadata.
[]
Results of Questionnaire ISSUE-4 & ISSUE-84: HTML5 versioning and doctypes - Straw Poll for Objections - Web-Based Straw-poll and Balloting System
Objections to the Change Proposal to Allow much more general DOCTYPE syntax to be conforming, possibly including optional version information.
http://www.w3.org/2002/09/wbs/40318/issues-4-84-objection-poll/results
10/1438042988065.26_20150728002308-00009-ip-10-236-191-2_814197501_0.json
1b637e8f_traw_poll_and_Balloting_System___optional_version_information_
[Responder] Jeremy Orlow
Backwards compatibility is central to HTML. If your HTML needs to target specific versions of the spec, then we've failed. Adding the notion of versions to the DOCTYPE will simply confuse authors and provides no real benefit as far as I can tell. If we do for some reason, in the future, do need to break backwards compatibility, we should then consider adding a mechanism for citing versions. Until then, the version number will just be noise/overhead/confusing.
[]
Results of Questionnaire ISSUE-4 & ISSUE-84: HTML5 versioning and doctypes - Straw Poll for Objections - Web-Based Straw-poll and Balloting System
Objections to the Change Proposal to Allow much more general DOCTYPE syntax to be conforming, possibly including optional version information.
http://www.w3.org/2002/09/wbs/40318/issues-4-84-objection-poll/results
10/1438042988065.26_20150728002308-00009-ip-10-236-191-2_814197501_0.json
1b637e8f_traw_poll_and_Balloting_System___optional_version_information_
[Responder] Aryeh Gregor
First, point #11 of the Rationale suggests that if an incompatible change to HTML is ever needed, adding support for version indicators now will help to avert the cost of switching to the new and incompatible version. But according to the proposal, browsers will treat a versioned doctype the same as an unversioned one, so why not just use the latter exclusively? If versioning ever needs to be added in the future, add it then. Pages with plain can then be treated as "old" pages, while ones with the new versioning syntax (whatever it is) will be "new" ones. Indeed, this is exactly what HTTP did. HTTP 0.9 had no explicit versioning, and when HTTP 1.0 added versioning, it provided that "If the protocol version is not specified, the recipient must assume that the message is in the simple HTTP/0.9 format." This scheme proved successful in practice, obviously. It is not explained why permitting versioning now makes later incompatible changes easier. As far as I can tell, this eliminates the rationale for the entire proposal, because it leaves no reason to actually permit explicit versioning now. Second, the Change Proposal (also in point #11 of the Rationale) states: """ In the history of computer languages, there are no languages that have not evolved, been extended, or otherwise "versioned" as long as the language has been in use. This applies to network protocols, character encoding standards, programming languages, and certainly to every known technology found on the web. There are no known cases where a language hasn't gone through some at least minor incompatible change. The standards process is established as a way of evolving specifications and implementations in a way to reduce the likelihood of complete failure to interoperate, but certainly not to guarantee that no incompatible changes will be needed in the future. """ I believe this is materially very wrong. HTML, CSS, and JavaScript are all languages that have maintained an extremely high degree of backward compatibility, and in particular have not ever used explicit versioning to date (that is, none that authors or UAs respected in practice, formal talismans notwithstanding). There are many other languages and interfaces that try to maintain this level of compatibility as well. The Linux system call API, the X Window System, and the Windows system call interface have all kept changes down to a level where they do not require programs or operating systems to advertise particular versions. I cannot think of a single programming language that requires programs to explicitly state what version of the language they're written in. (Perhaps this just shows my limited knowledge of programming languages, but then the original Change Proposal should have given supporting evidence for the claim in the first place.) Indeed, it's difficult to think of successful technologies that really rely on explicit versioning in practice. HTTP and XML have explicit versions, but in practice they're stuck at 1.1 and 1.0 respectively, and any new features that are adopted in practice are added backwards-compatibly, without incrementing the version number. So although they technically have version numbers, they're not good support for this Change Proposal. It's true that all languages sometimes need to break backward compatibility a bit, but version indicators are rarely necessary or helpful in doing this. In most cases, such breakage is kept as minimal as possible, so incrementing a version number would be excessive. In some cases, such as Python, there are large-scale backward compatibility breaks, but version indicators are still not used -- because they impose a permanent cost on the language to moderately ease a temporary transition period. On top of that, even if a few other languages do use explicit version indicators in the real world, they are not in the same position as web technologies. HTML is used by billions of people every day, and there are trillions of web pages in existence, under the control of countless different authors. Browser implementers have consistently emphasized that in order for people to use their browsers, they *cannot* break significant numbers of web pages. It is not a question of whether we want to change HTML incompatibly; it is impossible whether we want to or not, because market forces prohibit it. No reason is given for why this situation would ever change, as long as HTML remains widely deployed. Thus adding explicit version indicators is not only useless in the event of an incompatible change, as I explain in my first point. It also exemplifies one of the cardinal problems with pursuing long-term theoretical purity over short- to mid-term pragmatism: it burdens the language with extra syntax to avoid a problem that will very likely never exist, so that the cure is worse than the disease. In summary, the proposal seeks to address a nonexistent problem, and fails to do even that. On a final and more minor note, I also specifically object to the suggestion that the wording "mostly useless" be changed. It's good to use clear and forceful wording to help get the message out to authors that doctypes have no real purpose on the web, since they don't control browser processing (except by avoiding quirks mode). Weaker wording like "of limited utility" would reduce the effectiveness of this message. We do not need to write the spec in an overly formal fashion if that reduces the effectiveness of its phrasing.
[]
Results of Questionnaire ISSUE-4 & ISSUE-84: HTML5 versioning and doctypes - Straw Poll for Objections - Web-Based Straw-poll and Balloting System
Objections to the Change Proposal to Allow much more general DOCTYPE syntax to be conforming, possibly including optional version information.
http://www.w3.org/2002/09/wbs/40318/issues-4-84-objection-poll/results
10/1438042988065.26_20150728002308-00009-ip-10-236-191-2_814197501_0.json
1b637e8f_traw_poll_and_Balloting_System___optional_version_information_
[Responder] Tab Atkins Jr.
Robin Berjon addressed the issue of a version indicator eloquently in his series on "XML Bad Practices", based on his experiences developing the SVG specification: http://berjon.com/blog/2009/12/xmlbp-naive-versioning.html. If content is expected to be rejected across version boundaries, then "versions" are actually different languages entirely. Pretending that they're just different versions helps no one, and so a versioning indicator is not needed. Luckily, HTML has never and likely will never fall into this category - the next category is the relevant one here. If content is expected to be accepted across version boundaries, then good "versioning" behavior must be relatively complex and subtle to correctly handle unknown (read: newly introduced) content. The versioning indicator itself doesn't help in any way with this - what happens if the author says the content is version 2, but uses a construct from version 1 that's obsolete in version 2, and a construct from version 3 that hadn't been thought of at the time version 2 was created? Proper error-handling (for the version1 construct) and forward-compatible design (for the version3 construct) needs to be designed into the language in the first place, and an additional version indicator provides precisely zero help here. Thus, a versioning indicator is never needed. As this appears to be the primary justification for this change proposal, then, I strongly object to changing the language in this way.
[]
Results of Questionnaire ISSUE-4 & ISSUE-84: HTML5 versioning and doctypes - Straw Poll for Objections - Web-Based Straw-poll and Balloting System
Objections to the Change Proposal to Allow much more general DOCTYPE syntax to be conforming, possibly including optional version information.
http://www.w3.org/2002/09/wbs/40318/issues-4-84-objection-poll/results
10/1438042988065.26_20150728002308-00009-ip-10-236-191-2_814197501_0.json
1b637e8f_traw_poll_and_Balloting_System___optional_version_information_
[Responder] Jace Voracek
It is a key necessity for the World Wide Web to operate on a basis which does not require version-specific syntax with DOCTYPE for HTML in order to avoid confusion among platforms. Allowing such syntax may break the universal standards of HTML if many different DOCTYPE documents are produced.
[]
Results of Questionnaire ISSUE-4 & ISSUE-84: HTML5 versioning and doctypes - Straw Poll for Objections - Web-Based Straw-poll and Balloting System
Objections to the Change Proposal to Allow much more general DOCTYPE syntax to be conforming, possibly including optional version information.
http://www.w3.org/2002/09/wbs/40318/issues-4-84-objection-poll/results
10/1438042988065.26_20150728002308-00009-ip-10-236-191-2_814197501_0.json
1b637e8f_traw_poll_and_Balloting_System___optional_version_information_
[Responder] David Singer
- HTML and other core specifications of the Web platform are processed in an unversioned way in practice. Having an in-band version indicator is misleading to authors, who expect it to have a material effect, and creates a great deal of misunderstanding. - It may be tempting for some implementors to use a standard version indicator as an implementation version indicator. For reasons well-explained by Adam Barth, David Baron and others, this would have an anti-competitive effect on the browser market; content would end up locked in to specific bug profiles. - The proposal not only allows versioning in the doctype but also allows creation of ad-hoc custom doctypes. Profiling the language this way is likely to lead to interoperability problems. - If versioning is to be supported, versioning the doctype is inferior to versioning via an attribute; other specs use an attribute, XML documents generally would not use a doctype, and the doctype is not viable for compound documents such as Atom that embeds XHTML. - The change proposal argues that versioning in the doctype may be useful for controlled environments, but on the other hand argues that versioning must be ignored by implementations. If it has an effect, it creates an interoperability problem; if it has no effect, then it is unclear how it helps controlled environments.
[]
Results of Questionnaire ISSUE-4 & ISSUE-84: HTML5 versioning and doctypes - Straw Poll for Objections - Web-Based Straw-poll and Balloting System
Objections to the Change Proposal to Allow much more general DOCTYPE syntax to be conforming, possibly including optional version information.
http://www.w3.org/2002/09/wbs/40318/issues-4-84-objection-poll/results
10/1438042988065.26_20150728002308-00009-ip-10-236-191-2_814197501_0.json