Input: [Responder] John Vernaleo [What to publish?] I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft. [Comments]

Output: For what it's worth, I don't feel as strongly about my answer to this question than the other two and can see good reasons for either way.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Adam Barth [What to publish?] I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft. [Comments]

Output: Publishing two very similar editor's drafts would be pretty confusing. If we end up doing that, we should explain what the differences are and why we're choosing to publish both.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Philip Jägenstedt [What to publish?] I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft. [Comments]

Output: Publishing multiple drafts would be harmful. Instead of having polls like this we should spend our time discussing the specific issues, possibly resulting in the inclusion/removal of notes or warnings in Ian's draft, but preferably actual solutions.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Richard Schwerdtfeger [What to publish?] I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft. [Comments]

Output: These choices seem redundant.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Jace Voracek [What to publish?] I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft. [Comments]

Output: Although I believe that publishing these approved drafts would be acceptable for those that have a preference, I conclude that taking a vote of which individual draft to publish will lead to the best outcome.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Rob Ennals [What to publish?] I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft. [Comments]

Output: Publishing multiple drafts will be confusing.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Debi Orton [What to publish?] I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts. [Comments]

Output: Based on what I have read in the workgroup's listserv, I fully expect the draft with less accessibility support to receive the majority of votes. In that case, I would like the explanatory draft to be available also, so that we could point authors to that version for explanations of changes.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Jirka Kosek [What to publish?] I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft. [Comments]

Output: Publication of multiple drafts will confuse spec readers from outside of HTML WG.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Ben Boyle [What to publish?] I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft. [Comments]

Output: I would prefer there be one draft for clarity, however I am not opposed to publishing multiple drafts to see if that achieves anything (other than confusion), which it might. Think the differences need to be highlighted in a clear and obvious way for this to be effective.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Anne van Kesteren [What to publish?] I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft. [Comments]

Output: In general I'm ok with publishing all Editor's Draft that have majority approval, but they have to offer some normative difference in my opinion.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Daniel Schattenkirchner [What to publish?] I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft. [Comments]

Output: The original draft is sufficient.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Ben Millard [What to publish?] I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts. [Comments]

Output: Being able to fork the development of HTML5 so that alternative approaches can be worked on and reviewed has always been part of the project, as I understand it. Competition and collaboration can co-exist within a project and improve it.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Stéphane Deschamps [What to publish?] I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft. [Comments]

Output: I expect it's a matter of democracy. But I really don't see the point of publishing a draft at this point without comments and warnings.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Nikunj Mehta [What to publish?] I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft. [Comments]

Output: Our vote is focused on the continued progress of HTML5. We are supportive of Manu's intention to clarify to the general audience a full measure of where the working group stands. Given the relative short life to date of Manu's draft and the rather daunting task of adding adequate and appropriate warnings in the existing draft, we feel it is best to advance Ian's draft at this time and revisit this topic at the next heartbeat.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [BASE] SELECT [PREFIX] CONSTRUCT [3] ASK [2]

Output: DESCRIBE


Input: [BASE] ORDER BY [PREFIX] LIMIT [3] DISTINCT [4] REDUCED [2]

Output: OFFSET


Input: [BASE] FROM [PREFIX] FROM NAMED [2]

Output: WHERE


Input: [BASE] GRAPH [PREFIX] OPTIONAL [3] FILTER [4] a [2]

Output: UNION


Input: [BASE] STR [PREFIX] LANG [3] DATATYPE [4] BOUND [5] sameTERM [2]

Output: LANGMATCHES


Input: [BASE] isURI [PREFIX] isIRI [3] REGEX [4] true [5] false [6] isBLANK [2]

Output: isLITERAL


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

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


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

Output: List of bad links in the page


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

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


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

Output: List of HTML markup errors.


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

Output: List of spelling errors.


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

Output: List of style CSS errors.


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

Output: Log of changes to the document


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

Output: HTTP headers sent by the server


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

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


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

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


Input: [Value] copy: [Description]

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

Supported States and Properties | Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [Value] move: [Description]

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

Supported States and Properties | Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [Value] link: [Description]

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

Supported States and Properties | Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [Value] execute: [Description]

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

Supported States and Properties | Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [Value] popup: [Description]

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

Supported States and Properties | Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


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

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

Supported States and Properties | Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [Responder] Cliff Tyllick

Output: I abstain (not vote)

Results of Questionnaire EOWG Review: Standards Harmonization doc (final) - Web-Based Straw-poll and Balloting System


Input: [Responder] Karl Groves

Output: I support publishing this as page as is

Results of Questionnaire EOWG Review: Standards Harmonization doc (final) - Web-Based Straw-poll and Balloting System


Input: [Responder] Jennifer Sutton

Output: I support publishing this page; however, I suggest the changes in the comments section below (for editors' discretion)

Results of Questionnaire EOWG Review: Standards Harmonization doc (final) - Web-Based Straw-poll and Balloting System


Input: [Responder] Sylvie Duchateau

Output: I support publishing this page; however, I suggest the changes in the comments section below (for editors' discretion)

Results of Questionnaire EOWG Review: Standards Harmonization doc (final) - Web-Based Straw-poll and Balloting System


Input: [Responder] Wayne Dick

Output: I support publishing this as page as is

Results of Questionnaire EOWG Review: Standards Harmonization doc (final) - Web-Based Straw-poll and Balloting System


Input: [Responder] Vicki Menezes Miller

Output: I support publishing this page; however, I suggest the changes in the comments section below (for editors' discretion)

Results of Questionnaire EOWG Review: Standards Harmonization doc (final) - Web-Based Straw-poll and Balloting System


Input: [Responder] Liam McGee

Output: I support publishing this page; however, I suggest the changes in the comments section below (for editors' discretion)

Results of Questionnaire EOWG Review: Standards Harmonization doc (final) - Web-Based Straw-poll and Balloting System


Input: [Responder] Char James-Tanny

Output: I abstain (not vote)

Results of Questionnaire EOWG Review: Standards Harmonization doc (final) - Web-Based Straw-poll and Balloting System


Input: [Responder] Sandi Wassmer

Output: I abstain (not vote)

Results of Questionnaire EOWG Review: Standards Harmonization doc (final) - Web-Based Straw-poll and Balloting System


Input: [Responder] Sharron Rush

Output: I support publishing this page; however, I suggest the changes in the comments section below (for editors' discretion)

Results of Questionnaire EOWG Review: Standards Harmonization doc (final) - Web-Based Straw-poll and Balloting System


Input: [Responder] Ian Pouncey

Output: I abstain (not vote)

Results of Questionnaire EOWG Review: Standards Harmonization doc (final) - Web-Based Straw-poll and Balloting System


Input: [Responder] Shadi Abou-Zahra

Output: I do not support publishing this page because of the comments indicated as [important to be addressed before publication] in the comments section below

Results of Questionnaire EOWG Review: Standards Harmonization doc (final) - Web-Based Straw-poll and Balloting System


Input: [Responder] Andrew Arch

Output: I abstain (not vote)

Results of Questionnaire EOWG Review: Standards Harmonization doc (final) - Web-Based Straw-poll and Balloting System


Input: [Responder] Shawn Henry

Output: I abstain (not vote)

Results of Questionnaire EOWG Review: Standards Harmonization doc (final) - Web-Based Straw-poll and Balloting System


Input: [Responder] Helle Bjarnø

Output: I abstain (not vote)

Results of Questionnaire EOWG Review: Standards Harmonization doc (final) - Web-Based Straw-poll and Balloting System


Input: [Responder] Jack Welsh

Output: I abstain (not vote)

Results of Questionnaire EOWG Review: Standards Harmonization doc (final) - Web-Based Straw-poll and Balloting System


Input: [Responder] Jason Bell

Output: I abstain (not vote)

Results of Questionnaire EOWG Review: Standards Harmonization doc (final) - Web-Based Straw-poll and Balloting System


Input: [Responder] Emmanuelle Gutiérrez y Restrepo

Output: I support publishing this as page as is

Results of Questionnaire EOWG Review: Standards Harmonization doc (final) - Web-Based Straw-poll and Balloting System


Input: [Responder] Denis Boudreau

Output: I support publishing this as page as is

Results of Questionnaire EOWG Review: Standards Harmonization doc (final) - Web-Based Straw-poll and Balloting System


Input: [Definition] Character data [Attribute Type]

Output: CDATA

Modularization of XHTML - Defining Abstract Modules


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

Output: ID

Modularization of XHTML - Defining Abstract Modules


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

Output: IDREF

Modularization of XHTML - Defining Abstract Modules


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

Output: IDREFS

Modularization of XHTML - Defining Abstract Modules


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

Output: NAME

Modularization of XHTML - Defining Abstract Modules


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

Output: NMTOKEN

Modularization of XHTML - Defining Abstract Modules


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

Output: NMTOKENS

Modularization of XHTML - Defining Abstract Modules


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

Output: PCDATA

Modularization of XHTML - Defining Abstract Modules


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

Output: HTML to Text converter


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

Output: Link Checker


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

Output: Link Checker


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

Output: HTML Validator


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

Output: W3C Spellchecker


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

Output: CSS Validator


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

Output: CVS Log


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

Output: Headers


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

Output: the pubrules checker


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

Output: the pubrules checker


Input: [Action] caller disconnects [Event] connection.disconnect.hangup [Reason]

Output: The caller hung up.

Voice Extensible Markup Language (VoiceXML) 2.1

Table 11: Consultation Transfer Outcomes Prior to Connection Being Established


Input: [Action] caller cancels transfer before outgoing call begins [Value of form item variable] near_end_disconnect [Reason]

Output: The caller cancelled the transfer attempt via a DTMF or voice command before the outgoing call begins (during playback of queued audio).

Voice Extensible Markup Language (VoiceXML) 2.1


Input: [Action] callee busy [Value of form item variable] busy [Reason]

Output: The callee was busy.

Voice Extensible Markup Language (VoiceXML) 2.1


Input: [Action] network busy [Value of form item variable] network_busy [Reason]

Output: An intermediate network refused the call.

Voice Extensible Markup Language (VoiceXML) 2.1


Input: [Action] callee does not answer [Value of form item variable] noanswer [Reason]

Output: There was no answer within the time specified by the connecttimeout attribute.

Voice Extensible Markup Language (VoiceXML) 2.1


Input: [Action] --- [Value of form item variable] unknown [Reason]

Output: The transfer ended but the reason is not known.

Voice Extensible Markup Language (VoiceXML) 2.1


Input: [Notation] {$ rule text $} [Interpretation]

Output: Emit the rule text substituting any occurrence of variables from the binding map. The outer {$ $} can be omitted in cases where there is no ambiguity.

Difference between revisions of "OWLRL" - RIF


Input: [Notation] for(?elt in ?list) { template } [Interpretation]

Output: ?list is a variable in the pattern which is bound to an RDF List. The for operator iterates over each element of the ?list in turn replacing the binding map for the ?elt variable with the next list entry and processes the enclosed template in the context of that new binding map.

Difference between revisions of "OWLRL" - RIF


Input: [Notation] for(?elt in ?list, != ?other) { template } [Interpretation]

Output: ?list is a variable in the pattern which is bound to an RDF List. The for operator iterates over each element of the ?list in turn, skipping any element identical to ?other, replacing the binding map for the ?elt variable with the next list entry and processes the enclosed template in the context of that new binding map.

Difference between revisions of "OWLRL" - RIF


Input: [Notation] $length(?list)$ [Interpretation]

Output: Used within a template this will be replaced by the length the RDFList bound to ?list.

Difference between revisions of "OWLRL" - RIF


Input: [Notation] $i$ [Interpretation]

Output: Used within a for(?elt in ?list){ template } this will be replaced by the index of the current ?elt.

Difference between revisions of "OWLRL" - RIF


Input: [Notation] $i+1$ [Interpretation]

Output: Used within a for(?elt in ?list){ template } this will be replaced by the index of the current ?elt, plus 1.

Difference between revisions of "OWLRL" - RIF


Input: [Attribute Type] CDATA [Definition]

Output: Character data

Modularization of XHTML - Defining Abstract Modules


Input: [Attribute Type] ID [Definition]

Output: A document-unique identifier

Modularization of XHTML - Defining Abstract Modules


Input: [Attribute Type] IDREF [Definition]

Output: A reference to a document-unique identifier

Modularization of XHTML - Defining Abstract Modules


Input: [Attribute Type] IDREFS [Definition]

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

Modularization of XHTML - Defining Abstract Modules


Input: [Attribute Type] NAME [Definition]

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

Modularization of XHTML - Defining Abstract Modules


Input: [Attribute Type] NMTOKEN [Definition]

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

Modularization of XHTML - Defining Abstract Modules


Input: [Attribute Type] NMTOKENS [Definition]

Output: One or more whitespace separated NMTOKEN values

Modularization of XHTML - Defining Abstract Modules


Input: [Attribute Type] PCDATA [Definition]

Output: Processed character data

Modularization of XHTML - Defining Abstract Modules


Input: [media type] xml-stylesheet PI and link [text/html] recognized as HTML [application/xhtml+xml] not supported [text/xml] recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively [application/xml]

Output: recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively

XHTML media type test - results: Microsoft Internet Explorer 5.5SP2


Input: [media type] link only [text/html] recognized as HTML [application/xhtml+xml] not supported [text/xml] recognized as XML, linked style sheet was not recognized and document tree was rendered [application/xml]

Output: recognized as XML, linked style sheet was not recognized and document tree was rendered

XHTML media type test - results: Microsoft Internet Explorer 5.5SP2


Input: [media type] xml-stylesheet PI only [text/html] recognized as HTML, xml-stylesheet PI was not recognized [application/xhtml+xml] not supported [text/xml] recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively [application/xml]

Output: recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively

XHTML media type test - results: Microsoft Internet Explorer 5.5SP2


Input: [media type] without xmlns [text/html] recognized as HTML [application/xhtml+xml] not supported [text/xml] recognized as XML, parsing failed due to the omitted xmlns declaration [application/xml]

Output: recognized as XML, parsing failed due to the omitted xmlns declaration

XHTML media type test - results: Microsoft Internet Explorer 5.5SP2


Input: [media type] without DOCTYPE [text/html] recognized as HTML [application/xhtml+xml] not supported [text/xml] recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively [application/xml]

Output: recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively

XHTML media type test - results: Microsoft Internet Explorer 5.5SP2


Input: [media type] without DOCTYPE and xmlns [text/html] recognized as HTML [application/xhtml+xml] not supported [text/xml] recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively and inline style (incorrectly) worked [application/xml]

Output: recognized as XML, XHTML-specific semantics were not recognized but the type selector in style sheets matched case-insensitively and inline style (incorrectly) worked

XHTML media type test - results: Microsoft Internet Explorer 5.5SP2


Input: [media type] Broken XHTML [text/html] recognized as HTML, well-formedness error was not detected [application/xhtml+xml] not supported [text/xml] showed blank page [application/xml]

Output: showed blank page

XHTML media type test - results: Microsoft Internet Explorer 5.5SP2


Input: [media type] HTML 4 [text/html] recognized as HTML [application/xhtml+xml] not supported [text/xml] failed correctly while parsing the DTD [application/xml]

Output: failed correctly while parsing the DTD

XHTML media type test - results: Microsoft Internet Explorer 5.5SP2


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

Output: DISTINCT


Input: [Patterns] triple patterns [Query Forms] CONSTRUCT [Modifiers]

Output: REDUCED


Input: [Patterns] Basic graph patterns [Query Forms] DESCRIBE [Modifiers]

Output: PROJECT


Input: [Patterns] Groups [Query Forms] ASK [Modifiers]

Output: ORDER BY


Input: [Patterns] OPTIONAL [Modifiers]

Output: LIMIT


Input: [Patterns] UNION [Modifiers]

Output: OFFSET


Input: [Patterns] GRAPH [Modifiers]

Output: GROUP BY


Input: [Patterns] NOT EXISTS [Modifiers]

Output: HAVING


Input: [Patterns] EXISTS [Modifiers]

Output: Select expressions


Input: [0] scheme [match] exact [case]

Output: insensitive


Input: [0] userInfo [match] exact [case]

Output: sensitive


Input: [0] host [match] endswith [case]

Output: insensitive


Input: [0] port [match] exact [case]

Output: sensitive


Input: [0] path [match] startswith [case]

Output: sensitive


Input: [0] query [match] startswith [case]

Output: sensitive


Input: [0] fragment [match] startswith [case]

Output: sensitive


Input: [0] uri [match] regex [case]

Output: sensitive


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

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

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


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

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

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


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

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

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


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

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

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


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

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

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


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

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

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


Input: [Responder] Geoffrey Sneddon [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Kornel Lesinski [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Stephen Stewart [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Toby Inkster [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Andrew Sidwell [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Nicolas Le Gall [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Doug Wright [Comments] Whilst I believe the approach of annotating/selectively editing the Editor's draft potentially has merit as a platform for discussion within the WG, I believe that actually publishing multiple versions of the same document as official WDs of the WG is just plain confusing. I would not vote against publishing a reformulation of the additional material as separate WG Note. [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Michael Puls II [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Larry Masinter [Comments] I think neither "majority" nor "most votes" should be used: if there is not "consensus" and there are votes (rather than straw polls), then one-vote-per-independent organization should be retained (one company has 17 members in "good standing"), and the "good standing" role of "invited experts" who are not actually experts or who do not actually participate should be reevaluated. A vote should not determined by those who are listed as working group members out of courtesy or for the rationale that their IPR disclaimer is needed. As far as IPR is concerned, both drafts contain new, unreviewed material that might trigger a patent review; commit-then-discuss should be evaluated against the patent policy to see if some adjustment is needed. [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Martin McEvoy [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] John Drinkwater [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Stephen Axthelm [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Dan Smith [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Joe Williams [Comments] Manu's work can be used but not directly. [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Sam Ruby [Comments] In this case could live with either document and in the case of competing technical drafts I would support publishing both; but publishing two drafts simultaneously that differ only in informative content seems like it would cause confusion. [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Martin Kliehm [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Matthew Turvey [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Julian Reschke [Comments] Publishing both would create confusion, and also raise the question about which is "the right one". [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] David Håsäther [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Benoit Piette [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Edward O'Connor [Comments] I think each "fork" should go through FPWD (which so far has only happened with formal WG decision-by-vote). Once through FPWD, I think we should always publish new WDs whenever the editor(s) would like to. (I think it wouldn't be a good thing for Manu's draft to also go through FPWD, as it only differs in warnings from Ian's, but nevertheless if we're going to embrace the "anyone can author a spec" idea, we should embrace it fully.) [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Catherine Roy [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] John Kemp [Comments] As mentioned, I think it might be confusing to publish two drafts where one is a superset of the other. [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] John Foliot [Comments] If there were technical differences between the 2 documents, my answer would likely have been very different. Since I currently see the "Manu's Draft" version as simply an enhanced copy of the work produced by Ian I see no benefit in making both available as Working Drafts. [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Chris Wilson [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Bruce Lawson [Comments] changed my answer, having seen John Foliot's cleverer response: If there were technical differences between the 2 documents, my answer would likely have been very different. Since I currently see the "Manu's Draft" version as simply an enhanced copy of the work produced by Ian I see no benefit in making both available as Working Drafts. [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Henri Sivonen [Comments] The purpose of heartbeat WDs is to communicate to the community outside the WG itself, and publishing multiple drafts with only differences in informative statements fails at clear communication. [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Jeremy Keith [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Ian Hickson [Comments] If "I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts." wins, please count my vote as YES to both drafts. [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Tantek Çelik [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Jonas Sicking [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] David Hyatt [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Adele Peterson [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Lachlan Hunt [Comments] Publishing two separate drafts that are almost identical except for a few editorial comments about the stability of some random "controversial" sections does not solve any real problems, and will only serve to create confusion among the wider community. Even though I do not support the draft with extra warnings, I would rather see that one published by itself than have both needlessly published together. [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Maciej Stachowiak [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Alexey Proskuryakov [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Lee Kowalkowski [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Adam Roben [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Gavin Sharp [Comments] I think publishing multiple drafts would be problematic from a PR perspective. [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Robert Marshall [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Shawn Medero [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] David Singer [Comments] I fear having two variants of one document would be confusing. [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Shelley Powers [Comments] Two drafts would acknowledge the Editor's work, while providing another document that shows issues of concern. There is no PR problem with this approach--it reflects the current state of the group. On the other hand, I have a difficult time understanding why people who profess support for making information both visible and semantic, would vote for a choice that does neither. [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Charles McCathie Nevile [Comments] Publishing two drafts seems likely to lead to confusion. However I agree with Larry that a serious attempt to reach consensus makes more sense than going through with something that receives a large minority of dissent. I recognise that the decision on how to proceed is up to the chairs, rather than a poll of all comers actually being binding. Please note that Opera Software, with many participants in the group, is not expressing a formal opinion at this time, but rather each participant is free to vote as they see fit, in what we understand to be the spirit of this poll. Should a suggestion such as Larry's be accepted, we would of course submit a single formal vote clarifying that it is such. [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Channy Yun [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Cameron McCormack [Comments] While I am happy for the WG to publish multiple documents, I don't think selecting between drafts to publish as the main HTML 5 spec at a given point in time is the best way to proceed. I wonder if David Hyatt should really be listed as editor on whichever documents end up being published, though, given that he has not edited either. [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Karl Dubost [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Alex Robinson [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Leif Halvard Silli [Comments] Now is the time to, eventually, display disagreement. [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Jason White [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Roy Fielding [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Ben Adida [Comments] I would prefer that we pick a consistent long-term approach: if we are CTR, then everyone gets to CTR. [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] John Vernaleo [Comments] For what it's worth, I don't feel as strongly about my answer to this question than the other two and can see good reasons for either way. [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Masataka Yakura [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Robert O'Callahan [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Adam Barth [Comments] Publishing two very similar editor's drafts would be pretty confusing. If we end up doing that, we should explain what the differences are and why we're choosing to publish both. [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Russell Cavell [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Frank Palinkas [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Alfonso Martínez de Lizarrondo [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Philip Jägenstedt [Comments] Publishing multiple drafts would be harmful. Instead of having polls like this we should spend our time discussing the specific issues, possibly resulting in the inclusion/removal of notes or warnings in Ian's draft, but preferably actual solutions. [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] James Graham [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Laura Carlson [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Joshue O Connor [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Patrick Lauke [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Hallvord Steen [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Jude Robinson [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Denis Boudreau [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Richard Schwerdtfeger [Comments] These choices seem redundant. [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Jace Voracek [Comments] Although I believe that publishing these approved drafts would be acceptable for those that have a preference, I conclude that taking a vote of which individual draft to publish will lead to the best outcome. [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Cynthia Shelly [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Jens Meiert [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Arne Johannessen [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Rob Ennals [Comments] Publishing multiple drafts will be confusing. [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Debi Orton [Comments] Based on what I have read in the workgroup's listserv, I fully expect the draft with less accessibility support to receive the majority of votes. In that case, I would like the explanatory draft to be available also, so that we could point authors to that version for explanations of changes. [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Eric Carlson [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Vicki Stanton [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Jirka Kosek [Comments] Publication of multiple drafts will confuse spec readers from outside of HTML WG. [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Ben Boyle [Comments] I would prefer there be one draft for clarity, however I am not opposed to publishing multiple drafts to see if that achieves anything (other than confusion), which it might. Think the differences need to be highlighted in a clear and obvious way for this to be effective. [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Laurens Holst [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Per-Erik Brodin [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Anne van Kesteren [Comments] In general I'm ok with publishing all Editor's Draft that have majority approval, but they have to offer some normative difference in my opinion. [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Michaeljohn Clement [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Chris Cressman [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Scott Lewis [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Tab Atkins Jr. [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Manu Sporny [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Daniel Schattenkirchner [Comments] The original draft is sufficient. [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Gregory Rosmaita [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Steve Faulkner [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Ben Millard [Comments] Being able to fork the development of HTML5 so that alternative approaches can be worked on and reviewed has always been part of the project, as I understand it. Competition and collaboration can co-exist within a project and improve it. [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Sander van Lambalgen [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Krijn Hoetmer [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Stéphane Deschamps [Comments] I expect it's a matter of democracy. But I really don't see the point of publishing a draft at this point without comments and warnings. [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Nikunj Mehta [Comments] Our vote is focused on the continued progress of HTML5. We are supportive of Manu's intention to clarify to the general audience a full measure of where the working group stands. Given the relative short life to date of Manu's draft and the rather daunting task of adding adequate and appropriate warnings in the existing draft, we feel it is best to advance Ian's draft at this time and revisit this topic at the next heartbeat. [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Tobias Horvath [What to publish?]

Output: I would prefer to publish all Editor's Drafts that have majority approval as Working Drafts.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Responder] Simon Myers [What to publish?]

Output: I prefer to publish only the one Editor's Draft receiving the most votes as a Working Draft.

Results of Questionnaire Publish HTML 5 update with or without warnings? - Web-Based Straw-poll and Balloting System


Input: [Language feature] a element that creates a hyperlink [Restrictions] If specified, role must be one of the following: link, menuitem, tab, or treeitem

Output: link role

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] address element [Restrictions] If specified, role must be contentinfo

Output: No role

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] article element [Restrictions] If specified, role must be one of the following: article, document, application, or main

Output: article role

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] aside element [Restrictions] If specified, role must be one of the following: complementary, note, search or presentation

Output: complementary role

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] audio element [Restrictions] If specified, role must be application

Output: No role

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] body element [Restrictions] If specified, role must be either document or application

Output: document role

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] button element [Restrictions] If specified, role must be one of the following: button, link, menuitem, menuitemcheckbox, menuitemradio or radio

Output: button role

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] details element [Restrictions] If specified, role must be a role that supports aria-expanded

Output: group role

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] dialog element [Restrictions] If specified, role must be one of the following: alert, alertdialog, application, contentinfo, dialog, document, log, main, marquee, region, search, or status

Output: dialog role

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] embed element [Restrictions] If specified, role must be one of the following: application, document, or img

Output: No role

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] h1 element [Restrictions] If specified, role must be one of the following: heading, tab or presentation

Output: heading role, with the aria-level property set to the element's outline depth

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] h2 element [Restrictions] If specified, role must be one of the following: heading, tab or presentation

Output: heading role, with the aria-level property set to the element's outline depth

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] h3 element [Restrictions] If specified, role must be one of the following: heading, tab or presentation

Output: heading role, with the aria-level property set to the element's outline depth

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] h4 element [Restrictions] If specified, role must be heading, tab or presentation

Output: heading role, with the aria-level property set to the element's outline depth

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] h5 element [Restrictions] If specified, role must be one of the following: heading, tab or presentation

Output: heading role, with the aria-level property set to the element's outline depth

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] h6 element [Restrictions] If specified, role must be one of the following: heading, tab or presentation

Output: heading role, with the aria-level property set to the element's outline depth

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] iframe element [Restrictions] If specified, role must be one of the following: application, document, img, or presentation

Output: No role

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] img element whose alt attribute's value is absent [Restrictions] No restrictions

Output: img role

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] img element whose alt attribute's value is present and not empty [Restrictions] No restrictions

Output: img role

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] input element with a type attribute in the Button state [Restrictions] If specified, role must be one of the following: button, link, menuitem, menuitemcheckbox, menuitemradio or radio

Output: button role

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] input element with a type attribute in the Checkbox state [Restrictions] If specified, role must be either checkbox or menuitemcheckbox

Output: checkbox role

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] input element with a type attribute in the Image Button state [Restrictions] If specified, role must be one of the following: button, link, menuitem, menuitemcheckbox, menuitemradio or radio

Output: button role

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] input element with a type attribute in the Radio Button state [Restrictions] If specified, role must be either radio or menuitemradio

Output: radio role

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] input, select or textarea element with a required attribute [Restrictions] If specified, the aria-required state must be set to "true"

Output: The aria-required state set to "true"

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] input, select or textarea element without a required attribute [Restrictions] If specified, the aria-required state set to "true" or "false"

Output: aria-required set to "false"

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] li element whose parent is an ol or ul element [Restrictions] If specified, role must be one of the following: listitem, menuitem, menuitemcheckbox, menuitemradio, option, tab, treeitem or presentation

Output: listitem role

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] menu element with a type attribute in the toolbar state [Restrictions] If specified, role must be one of the following: directory, list, listbox, menu, menubar, tablist, toolbar, or tree or presentation

Output: toolbar role

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] object element [Restrictions] If specified, role must be one of the following: application, document, img, or presentation

Output: No role

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] ol element [Restrictions] If specified, role must be one of the following: directory, list, listbox, menu, menubar, tablist, toolbar, tree or presentation

Output: list role

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] output element [Restrictions] No restrictions

Output: status role

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] section element [Restrictions] If specified, role must be one of the following: alert, alertdialog, application, contentinfo, dialog, document, log, main, marquee, region, search, status or presentation

Output: region role

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] ul element [Restrictions] If specified, role must be one of the following: directory, group, list, listbox, menu, menubar, tablist, toolbar, tree or presentation

Output: list role

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] video element [Restrictions] If specified, role must be application

Output: No role

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] Element with a hidden attribute [Restrictions] If specified, the aria-hidden state must be set to "true"

Output: The aria-hidden state set to "true"

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Language feature] Element without a hidden attribute [Restrictions] If specified, the aria-hidden state set to "true" or "false"

Output: The aria-hidden state set to "false"

3 Semantics, structure, and APIs of HTML documents — HTML 5.1


Input: [Attribute in clause] RejectByURL [Action] Block document [Satisfied by]

Output: URL matches any of the patterns specified


Input: [Attribute in clause] AcceptByURL [Action] Pass document [Satisfied by]

Output: URL matches any of the patterns specified


Input: [Attribute in clause] RejectIf [Action] Block document [Satisfied by]

Output: expression = true


Input: [Attribute in clause] AcceptIf [Action] Pass document [Satisfied by]

Output: expression = true


Input: [Attribute in clause] RejectUnless [Action] Block document [Satisfied by]

Output: expression = false


Input: [Attribute in clause] AcceptUnless [Action] Pass document [Satisfied by]

Output: expression = false


Input: [Event] connection.disconnect.hangup [Reason] The caller hung up. [Action]

Output: caller disconnects

caller cancels transfer before outgoing call begins

Voice Extensible Markup Language (VoiceXML) 2.1


Input: [Value of form item variable] near_end_disconnect [Reason] The caller cancelled the transfer attempt via a DTMF or voice command before the outgoing call begins (during playback of queued audio). [Action]

Output: caller cancels transfer before outgoing call begins

caller cancels transfer before outgoing call begins

Voice Extensible Markup Language (VoiceXML) 2.1


Input: [Value of form item variable] busy [Reason] The callee was busy. [Action]

Output: callee busy

caller cancels transfer before outgoing call begins

Voice Extensible Markup Language (VoiceXML) 2.1


Input: [Value of form item variable] network_busy [Reason] An intermediate network refused the call. [Action]

Output: network busy

caller cancels transfer before outgoing call begins

Voice Extensible Markup Language (VoiceXML) 2.1


Input: [Value of form item variable] noanswer [Reason] There was no answer within the time specified by the connecttimeout attribute. [Action]

Output: callee does not answer

caller cancels transfer before outgoing call begins

Voice Extensible Markup Language (VoiceXML) 2.1


Input: [Value of form item variable] unknown [Reason] The transfer ended but the reason is not known. [Action]

caller cancels transfer before outgoing call begins

Voice Extensible Markup Language (VoiceXML) 2.1


Input: [media type] xml-stylesheet PI and link [text/html] recognized as HTML [application/xhtml+xml] not supported [text/xml] recognized as XML, parsing failed [application/xml]

Output: recognized as XML, parsing failed

XHTML media type test - results: Microsoft Internet Explorer 5.1/Mac


Input: [media type] link only [text/html] recognized as HTML [application/xhtml+xml] not supported [text/xml] recognized as XML, parsing failed [application/xml]

Output: recognized as XML, parsing failed

XHTML media type test - results: Microsoft Internet Explorer 5.1/Mac


Input: [media type] xml-stylesheet PI only [text/html] recognized as HTML, xml-stylesheet PI was not recognized [application/xhtml+xml] not supported [text/xml] recognized as XML, parsing failed [application/xml]

Output: recognized as XML, parsing failed

XHTML media type test - results: Microsoft Internet Explorer 5.1/Mac


Input: [media type] without xmlns [text/html] recognized as HTML [application/xhtml+xml] not supported [text/xml] recognized as XML, parsing failed [application/xml]

Output: recognized as XML, parsing failed

XHTML media type test - results: Microsoft Internet Explorer 5.1/Mac


Input: [media type] without DOCTYPE [text/html] recognized as HTML [application/xhtml+xml] not supported [text/xml] type 3 error occured, browser crashed [application/xml]

Output: type 3 error occured, browser crashed

XHTML media type test - results: Microsoft Internet Explorer 5.1/Mac


Input: [media type] without DOCTYPE and xmlns [text/html] recognized as HTML [application/xhtml+xml] not supported [text/xml] type 3 error occured, browser crashed [application/xml]

Output: type 3 error occured, browser crashed

XHTML media type test - results: Microsoft Internet Explorer 5.1/Mac


Input: [media type] Broken XHTML [text/html] recognized as HTML, well-formedness error was not checked [application/xhtml+xml] not supported [text/xml] failed correctly [application/xml]

Output: failed correctly

XHTML media type test - results: Microsoft Internet Explorer 5.1/Mac


Input: [media type] HTML 4 [text/html] recognized as HTML [application/xhtml+xml] not supported [text/xml] failed correctly while parsing the DTD [application/xml]

Output: failed correctly while parsing the DTD

XHTML media type test - results: Microsoft Internet Explorer 5.1/Mac


Input: [Function] op:to [Meaning]

Output: Returns the sequence containing every xs:integer between the values of the operands.

XQuery 1.0 and XPath 2.0 Functions and Operators (Second Edition)


Input: [Function] fn:id [Meaning]

Output: Returns the sequence of element nodes having an ID value matching the one or more of the supplied IDREF values.

XQuery 1.0 and XPath 2.0 Functions and Operators (Second Edition)


Input: [Function] fn:idref [Meaning]

Output: Returns the sequence of element or attribute nodes with an IDREF value matching one or more of the supplied ID values.

XQuery 1.0 and XPath 2.0 Functions and Operators (Second Edition)


Input: [Function] fn:doc [Meaning]

Output: Returns a document node retrieved using the specified URI.

XQuery 1.0 and XPath 2.0 Functions and Operators (Second Edition)


Input: [Function] fn:doc-available [Meaning]

Output: Returns true if a document node can be retrieved using the specified URI.

XQuery 1.0 and XPath 2.0 Functions and Operators (Second Edition)


Input: [Function] fn:collection [Meaning]

Output: Returns a sequence of nodes retrieved using the specified URI or the nodes in the default collection.

XQuery 1.0 and XPath 2.0 Functions and Operators (Second Edition)


Input: [Final] Final [Description] The operation succeeded. [QName Local Name]

Output: Success


Input: [Final] Final [Description] The service does not support the protocol version specified in the request. [QName Local Name]

Output: VersionMismatch


Input: [Final] Final [Description] An error occurred that was due to the message sent by the sender. [QName Local Name]

Output: Sender


Input: [Final] Final [Description] An error occurred at the receiver. [QName Local Name]

Output: Receiver


Input: [Final] Not Final [Description] The service has not acted on the request. In order for the request to be acted upon the request MUST be represented with the specified nonce in accordance with the two phase protocol [QName Local Name]

Output: Represent


Input: [Final] Not Final [Description] The request has been accepted for processing and the service will return the result asynchronously [QName Local Name]

Output: Pending


Input: [Attribute in clause] RejectByURL [Satisfied by] URL matches any of the patterns specified [Action]

Output: Block document


Input: [Attribute in clause] AcceptByURL [Satisfied by] URL matches any of the patterns specified [Action]

Output: Pass document


Input: [Attribute in clause] RejectIf [Satisfied by] expression = true [Action]

Output: Block document


Input: [Attribute in clause] AcceptIf [Satisfied by] expression = true [Action]

Output: Pass document


Input: [Attribute in clause] RejectUnless [Satisfied by] expression = false [Action]

Output: Block document


Input: [Attribute in clause] AcceptUnless [Satisfied by] expression = false [Action]

Output: Pass document


Input: [Data category] Translate [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] translate="yes" for elements, and translate="no" for attributes [Overriding] Yes [Inheritance]

Output: Textual content of element, including content of child elements, but excluding attributes

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Data category] Localization Note [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] None [Overriding] Yes [Inheritance]

Output: Textual content of element, including content of child elements, but excluding attributes

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Data category] Terminology [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] term="no" [Overriding] Not applicable [Inheritance]

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Data category] Directionality [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] dir="ltr" [Overriding] Yes [Inheritance]

Output: Textual content of element, including attributes and child elements

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Data category] Ruby [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] None [Overriding] Not applicable [Inheritance]

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Data category] Language Information [Local Usage] No [Global, rule-based selection] Yes [Global adding of information] No Yes [Default Values] None [Overriding] Yes [Inheritance]

Output: Textual content of element, including attributes and child elements

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Data category] Elements Within Text [Local Usage] No [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] withinText="no" [Overriding] Not applicable [Inheritance]

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Data category] Translate [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] translate="yes" for elements, and translate="no" for attributes [Inheritance] Textual content of element, including content of child elements, but excluding attributes [Overriding]

Output: Yes

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Data category] Localization Note [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] None [Inheritance] Textual content of element, including content of child elements, but excluding attributes [Overriding]

Output: Yes

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Data category] Terminology [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] term="no" [Inheritance] None [Overriding]

Output: Not applicable

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Data category] Directionality [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] dir="ltr" [Inheritance] Textual content of element, including attributes and child elements [Overriding]

Output: Yes

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Data category] Ruby [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] None [Inheritance] None [Overriding]

Output: Not applicable

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Data category] Language Information [Local Usage] No [Global, rule-based selection] Yes [Global adding of information] No Yes [Default Values] None [Inheritance] Textual content of element, including attributes and child elements [Overriding]

Output: Yes

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Data category] Elements Within Text [Local Usage] No [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] withinText="no" [Inheritance] None [Overriding]

Output: Not applicable

Internationalization Tag Set (ITS) Version 1.0 -- Review Version


Input: [Keyword] hidden [State] Hidden [Control type] n/a [Data type]

Output: An arbitrary string


Input: [Keyword] text [State] Text [Control type] Text field [Data type]

Output: Text with no line breaks


Input: [Keyword] search [State] Search [Control type] Search field [Data type]

Output: Text with no line breaks


Input: [Keyword] tel [State] Telephone [Control type] A text field [Data type]

Output: Text with no line breaks


Input: [Keyword] url [State] URL [Control type] A text field [Data type]

Output: An absolute IRI


Input: [Keyword] email [State] E-mail [Control type] A text field [Data type]

Output: An e-mail address or list of e-mail addresses


Input: [Keyword] password [State] Password [Control type] Text field that obscures data entry [Data type]

Output: Text with no line breaks (sensitive information)


Input: [Keyword] datetime [State] Date and Time [Control type] A date and time control [Data type]

Output: A date and time (year, month, day, hour, minute, second, fraction of a second) with the time zone set to UTC


Input: [Keyword] date [State] Date [Control type] A date control [Data type]

Output: A date (year, month, day) with no time zone


Input: [Keyword] month [State] Month [Control type] A month control [Data type]

Output: A date consisting of a year and a month with no time zone


Input: [Keyword] week [State] Week [Control type] A week control [Data type]

Output: A date consisting of a week-year number and a week number with no time zone


Input: [Keyword] time [State] Time [Control type] A time control [Data type]

Output: A time (hour, minute, seconds, fractional seconds) with no time zone


Input: [Keyword] datetime-local [State] Local Date and Time [Control type] A date and time control [Data type]

Output: A date and time (year, month, day, hour, minute, second, fraction of a second) with no time zone


Input: [Keyword] number [State] Number [Control type] A text field or spinner control [Data type]

Output: A numerical value


Input: [Keyword] range [State] Range [Control type] A slider control or similar [Data type]

Output: A numerical value, with the extra semantic that the exact value is not important


Input: [Keyword] color [State] Color [Control type] A color well [Data type]

Output: An sRGB color with 8-bit red, green, and blue components


Input: [Keyword] checkbox [State] Checkbox [Control type] A checkbox [Data type]

Output: A set of zero or more values from a predefined list


Input: [Keyword] radio [State] Radio Button [Control type] A radio button [Data type]

Output: An enumerated value


Input: [Keyword] file [State] File Upload [Control type] A label and a button [Data type]

Output: Zero or more files each with a MIME type and optionally a file name


Input: [Keyword] submit [State] Submit Button [Control type] A button [Data type]

Output: An enumerated value, with the extra semantic that it must be the last value selected and initiates form submission


Input: [Keyword] image [State] Image Button [Control type] Either a clickable image, or a button [Data type]

Output: 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


Input: [Keyword] reset [State] Reset Button [Control type] A button [Data type]


Input: [Keyword] button [State] Button [Control type] A button [Data type]


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

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


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

Output: The user agent is fetching media data.


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

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


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

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


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

Output: An error occurs while fetching the media data.


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

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


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

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


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

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


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

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


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

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


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

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


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

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


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

Output: Playback has started.


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

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


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

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


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

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


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

Output: The seeking IDL attribute changed to false.


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

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


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

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


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

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


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

Output: The duration attribute has just been updated.


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

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


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

Output: loadstart

HTML/Elements/video - Web Education Community Group


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

Output: progress

HTML/Elements/video - Web Education Community Group


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

Output: suspend

HTML/Elements/video - Web Education Community Group


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

Output: abort

HTML/Elements/video - Web Education Community Group


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

Output: error

HTML/Elements/video - Web Education Community Group


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

Output: emptied

HTML/Elements/video - Web Education Community Group


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

Output: stalled

HTML/Elements/video - Web Education Community Group


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

Output: play

HTML/Elements/video - Web Education Community Group


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

Output: pause

HTML/Elements/video - Web Education Community Group


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

Output: loadedmetadata

HTML/Elements/video - Web Education Community Group


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

Output: loadeddata

HTML/Elements/video - Web Education Community Group


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

Output: waiting

HTML/Elements/video - Web Education Community Group


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

Output: playing

HTML/Elements/video - Web Education Community Group


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

Output: canplay

HTML/Elements/video - Web Education Community Group


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

Output: canplaythrough

HTML/Elements/video - Web Education Community Group


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

Output: seeking

HTML/Elements/video - Web Education Community Group


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

Output: seeked

HTML/Elements/video - Web Education Community Group


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

Output: timeupdate

HTML/Elements/video - Web Education Community Group


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

Output: ended

HTML/Elements/video - Web Education Community Group


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

Output: ratechange

HTML/Elements/video - Web Education Community Group


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

Output: durationchange

HTML/Elements/video - Web Education Community Group


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

Output: volumechange

HTML/Elements/video - Web Education Community Group


Input: [State] Hidden [Data type] An arbitrary string [Control type] n/a [Keyword]

Output: hidden


Input: [State] Text [Data type] Text with no line breaks [Control type] Text field [Keyword]

Output: text


Input: [State] Search [Data type] Text with no line breaks [Control type] Search field [Keyword]

Output: search


Input: [State] Telephone [Data type] Text with no line breaks [Control type] A text field [Keyword]

Output: tel


Input: [State] URL [Data type] An absolute IRI [Control type] A text field [Keyword]

Output: url


Input: [State] E-mail [Data type] An e-mail address or list of e-mail addresses [Control type] A text field [Keyword]

Output: email


Input: [State] Password [Data type] Text with no line breaks (sensitive information) [Control type] Text field that obscures data entry [Keyword]

Output: password


Input: [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 [Keyword]

Output: datetime


Input: [State] Date [Data type] A date (year, month, day) with no time zone [Control type] A date control [Keyword]

Output: date


Input: [State] Month [Data type] A date consisting of a year and a month with no time zone [Control type] A month control [Keyword]

Output: month


Input: [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 [Keyword]

Output: week


Input: [State] Time [Data type] A time (hour, minute, seconds, fractional seconds) with no time zone [Control type] A time control [Keyword]

Output: time


Input: [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 [Keyword]

Output: datetime-local


Input: [State] Number [Data type] A numerical value [Control type] A text field or spinner control [Keyword]

Output: number


Input: [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 [Keyword]

Output: range


Input: [State] Color [Data type] An sRGB color with 8-bit red, green, and blue components [Control type] A color well [Keyword]

Output: color


Input: [State] Checkbox [Data type] A set of zero or more values from a predefined list [Control type] A checkbox [Keyword]

Output: checkbox


Input: [State] Radio Button [Data type] An enumerated value [Control type] A radio button [Keyword]

Output: radio


Input: [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 [Keyword]

Output: file


Input: [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 [Keyword]

Output: submit


Input: [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 [Keyword]

Output: image


Input: [State] Reset Button [Data type] n/a [Control type] A button [Keyword]

Output: reset


Input: [State] Button [Data type] n/a [Control type] A button [Keyword]

Output: button


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

Output: "none"

7.7 Drag and drop — HTML5 (Edition for Web Authors)


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

Output: "none"

7.7 Drag and drop — HTML5 (Edition for Web Authors)


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

Output: Based on effectAllowed value

7.7 Drag and drop — HTML5 (Edition for Web Authors)


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

Output: "none"

7.7 Drag and drop — HTML5 (Edition for Web Authors)


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

Output: Based on effectAllowed value

7.7 Drag and drop — HTML5 (Edition for Web Authors)