Input: [Requirement] Use HTTP properly [Details] Make sure that each page of your site is accessible with a stable address (URL) and that the HTTP caching properties are set correctly. Make sure if you migrate to a new site version that the URLs are either kept as is or at least redirected to the new ones. [Rationale] HTTP is a very powerful protocol and you get most of its power with stable URLs and an efficient caching system: bookmarks and links don't break, network access is faster, users are happy! [Test tool]

Output: The W3C Link Checker can provide some help. Besides, the advices given in the Common HTTP Implementation Problems Note can help assess what needs to be respected.

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use SVG and PNG for graphics [Details] Use PNG for raster images, and SVG for all others. [Rationale] PNG is a much more capable format than other binary formats for raster images because it provides better compression, more options, and it's free. The best format you should require is SVG: it's scalable, XML-based, very light, and has a lot of capabilities, for example, animation using SMIL, which is supported on cell phones, etc. [Test tool]

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use techniques to make your content accessible [Details] Details. [Rationale] Making a site accessible benefits all of your users, and broadens your current audience. This requirement may be required by law in some countries. [Test tool]

Output: See Evaluation Tools for Web Content Accessibility.

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use standards scripting languages [Details] Use the DOM API combined with Ecmascript (but don't make the use of scripts mandatory to navigate in the site!). [Rationale] DOM and Ecmascript (the common standard behind Javascript and JScript) are the best way to go to get interoperable scripts to create animations in your Web site. But do not forget your users that don't have these scripting capacities enabled. [Test tool]

Buy standards compliant Web sites — W3C QA


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

Output: hidden

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: text

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: search

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: tel

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: url

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: email

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: password

4.10.7 The input element — HTML5: Edition for Web Authors


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

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: date

4.10.7 The input element — HTML5: Edition for Web Authors


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

4.10.7 The input element — HTML5: Edition for Web Authors


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

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: time

4.10.7 The input element — HTML5: Edition for Web Authors


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

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: number

4.10.7 The input element — HTML5: Edition for Web Authors


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

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: color

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: checkbox

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: radio

4.10.7 The input element — HTML5: Edition for Web Authors


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

4.10.7 The input element — HTML5: Edition for Web Authors


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

4.10.7 The input element — HTML5: Edition for Web Authors


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

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: reset

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: button

4.10.7 The input element — HTML5: Edition for Web Authors


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: [Property] hanging-punctuation [Values] none | [ first || [ force-end | allow-end ] || last ] [Initial] none [Inh.] yes [Percentages] N/A [Media] visual [Applies to]

Output: inline elements


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

Output: all elements


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

Output: all elements


Input: [Property] line-break [Values] auto | loose | normal | strict [Initial] auto [Inh.] yes [Percentages] N/A [Media] visual [Applies to]

Output: all elements


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

Output: all elements


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

Output: block containers


Input: [Property] text-align [Values] start | end | left | right | center | justify | match-parent | start end [Initial] start [Inh.] yes [Percentages] N/A [Media] visual [Applies to]

Output: block containers


Input: [Property] text-align-last [Values] auto | start | end | left | right | center | justify [Initial] auto [Inh.] yes [Percentages] N/A [Media] visual [Applies to]

Output: block containers


Input: [Property] text-indent [Values] [ | ] && hanging? && each-line? [Initial] 0 [Inh.] yes [Percentages] refers to width of containing block [Media] visual [Applies to]

Output: block containers


Input: [Property] text-justify [Values] auto | none | inter-word | distribute [Initial] auto [Inh.] yes [Percentages] N/A [Media] visual [Applies to]

Output: block containers and, optionally, inline elements


Input: [Property] text-transform [Values] none | capitalize | uppercase | lowercase | full-width [Initial] none [Inh.] yes [Percentages] N/A [Media] visual [Applies to]

Output: all elements


Input: [Property] white-space [Values] normal | pre | nowrap | pre-wrap | pre-line [Initial] normal [Inh.] yes [Percentages] N/A [Media] visual [Applies to]

Output: all elements


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

Output: all elements


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

Output: all elements


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

Output: all elements


Input: [XKMS element] Message/Service [Required]

Output: Required but not dependent

XML Key Management Specification (XKMS 2.0) Bindings


Input: [XKMS element] Request/Signature [Required]

Output: Optional, may be used to support non-repudiation

XML Key Management Specification (XKMS 2.0) Bindings


Input: [XKMS element] Response/Signature [Required]

Output: Optional, may be used to support non-repudiation

XML Key Management Specification (XKMS 2.0) Bindings


Input: [XKMS element] Message/RequestId [Required]

Output: Required but not dependent

XML Key Management Specification (XKMS 2.0) Bindings


Input: [XKMS element] Message/ResponseId [Required]

Output: Required but not dependent

XML Key Management Specification (XKMS 2.0) Bindings


Input: [XKMS element] Message/Nonce [Required]

Output: Unnecessary

XML Key Management Specification (XKMS 2.0) Bindings


Input: [XKMS element] Request/RespondWith=Represent [Required]

Output: Unnecessary

XML Key Management Specification (XKMS 2.0) Bindings


Input: [XKMS element] Request/MessageHash [Required]

Output: Unnecessary

XML Key Management Specification (XKMS 2.0) Bindings


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: [Feature] The use of the role attribute with the value presentation [Indication]

Output: Probably a layout table


Input: [Feature] The use of the border attribute with the non-conforming value 0 [Indication]

Output: Probably a layout table


Input: [Feature] The use of the non-conforming cellspacing and cellpadding attributes with the value 0 [Indication]

Output: Probably a layout table


Input: [Feature] The use of caption, thead, or th elements [Indication]

Output: Probably a non-layout table


Input: [Feature] The use of the headers and scope attributes [Indication]

Output: Probably a non-layout table


Input: [Feature] The use of the border attribute with a value other than 0 [Indication]

Output: Probably a non-layout table


Input: [Feature] Explicit visible borders set using CSS [Indication]

Output: Probably a non-layout table


Input: [Feature] The use of the summary attribute [Indication]

Output: Not a good indicator (both layout and non-layout tables have historically been given this attribute)


Input: [Event Type] abort [Sync / Async] Sync [Bubbling phase] No Element [DOM interface] Event [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] blur [Sync / Async] Sync [Bubbling phase] No Element [DOM interface] FocusEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] click [Sync / Async] Sync [Bubbling phase] Yes Element [DOM interface] MouseEvent [Default Action] DOMActivate event [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] compositionstart [Sync / Async] Sync [Bubbling phase] Yes Element [DOM interface] CompositionEvent [Default Action] Launch text composition system [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] compositionupdate [Sync / Async] Sync [Bubbling phase] Yes Element [DOM interface] CompositionEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] compositionend [Sync / Async] Sync [Bubbling phase] Yes Element [DOM interface] CompositionEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] dblclick [Sync / Async] Sync [Bubbling phase] Yes Element [DOM interface] MouseEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMActivate [Sync / Async] Sync [Bubbling phase] Yes Element [DOM interface] UIEvent [Default Action] none [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMAttributeNameChanged [Sync / Async] Sync [Bubbling phase] Yes Element [DOM interface] MutationNameEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMAttrModified [Sync / Async] Sync [Bubbling phase] Yes Element [DOM interface] MutationEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMCharacterDataModified [Sync / Async] Sync [Bubbling phase] Yes Text, Comment, CDATASection, ProcessingInstruction [DOM interface] MutationEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMElementNameChanged [Sync / Async] Sync [Bubbling phase] Yes Element [DOM interface] MutationNameEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMFocusIn [Sync / Async] Sync [Bubbling phase] Yes Element [DOM interface] FocusEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMFocusOut [Sync / Async] Sync [Bubbling phase] Yes Element [DOM interface] FocusEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMNodeInserted [Sync / Async] Sync [Bubbling phase] Yes Element, Attr, Text, Comment, CDATASection, DocumentType, EntityReference, ProcessingInstruction [DOM interface] MutationEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMNodeInsertedIntoDocument [Sync / Async] Sync [Bubbling phase] No Element, Attr, Text, Comment, CDATASection, DocumentType, EntityReference, ProcessingInstruction [DOM interface] MutationEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMNodeRemoved [Sync / Async] Sync [Bubbling phase] Yes Element, Attr, Text, Comment, CDATASection, DocumentType, EntityReference, ProcessingInstruction [DOM interface] MutationEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMNodeRemovedFromDocument [Sync / Async] Sync [Bubbling phase] No Element, Attr, Text, Comment, CDATASection, DocumentType, EntityReference, ProcessingInstruction [DOM interface] MutationEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMSubtreeModified [Sync / Async] Sync [Bubbling phase] Yes defaultView, Document, DocumentFragment, Element, Attr [DOM interface] MutationEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] error [Sync / Async] Async [Bubbling phase] No Element [DOM interface] Event [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] focus [Sync / Async] Sync [Bubbling phase] No Element [DOM interface] FocusEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] focusin [Sync / Async] Sync [Bubbling phase] Yes Element [DOM interface] FocusEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] focusout [Sync / Async] Sync [Bubbling phase] Yes Element [DOM interface] FocusEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] keydown [Sync / Async] Sync [Bubbling phase] Yes Document, Element [DOM interface] KeyboardEvent [Default Action] Varies: keypress event; launch text composition system; blur and focus events; DOMActivate event; other event [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] keypress [Sync / Async] Sync [Bubbling phase] Yes Document, Element [DOM interface] KeyboardEvent [Default Action] Varies: textinput event; launch text composition system; blur and focus events; DOMActivate event; other event [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] keyup [Sync / Async] Sync [Bubbling phase] Yes Document, Element [DOM interface] KeyboardEvent [Default Action] none [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] load [Sync / Async] Async [Bubbling phase] No defaultView, Document, Element [DOM interface] Event [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] mousedown [Sync / Async] Sync [Bubbling phase] Yes Element [DOM interface] MouseEvent [Default Action] none [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] mouseenter [Sync / Async] Sync [Bubbling phase] No Element [DOM interface] MouseEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] mouseleave [Sync / Async] Sync [Bubbling phase] No Element [DOM interface] MouseEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] mousemove [Sync / Async] Sync [Bubbling phase] Yes Element [DOM interface] MouseEvent [Default Action] none [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] mouseout [Sync / Async] Sync [Bubbling phase] Yes Element [DOM interface] MouseEvent [Default Action] none [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] mouseover [Sync / Async] Sync [Bubbling phase] Yes Element [DOM interface] MouseEvent [Default Action] none [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] mouseup [Sync / Async] Sync [Bubbling phase] Yes Element [DOM interface] MouseEvent [Default Action] none [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] resize [Sync / Async] Sync [Bubbling phase] No defaultView, Document [DOM interface] UIEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] scroll [Sync / Async] Async [Bubbling phase] No / Yes defaultView, Document, Element [DOM interface] UIEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] select [Sync / Async] Sync [Bubbling phase] Yes Element [DOM interface] Event [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] textinput [Sync / Async] Sync [Bubbling phase] Yes Element [DOM interface] TextEvent [Default Action] none [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] unload [Sync / Async] Sync [Bubbling phase] No defaultView, Document, Element [DOM interface] Event [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] wheel [Sync / Async] Async [Bubbling phase] Yes defaultView, Document, Element [DOM interface] WheelEvent [Default Action] Scroll (or zoom) the document [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [0] Dependencies [Payload Security] Authentication defined by XKMS specification, client does not need to implement a comprehensive framework. [Transaction Layer Security]

Output: Authentication mechanism defined by TLS which clients must implement

XML Key Management Specification (XKMS 2.0) Bindings


Input: [0] Use of XML Signature [Payload Security] Uses XML Signature in Enveloped Mode requiring slightly more complex processing. [Transaction Layer Security]

Output: Not required

XML Key Management Specification (XKMS 2.0) Bindings


Input: [0] Support for Routing [Payload Security] Specification describes bi-lateral authentication only, multi-hop message routing and multi-party transactions are not supported. [Transaction Layer Security]

XML Key Management Specification (XKMS 2.0) Bindings


Input: [0] Support for Confidentiality [Payload Security] None, although applications may employ TLS to establish a secure channel [Transaction Layer Security]

Output: Supported

XML Key Management Specification (XKMS 2.0) Bindings


Input: [0] Non-Repudiation [Payload Security] Supported [Transaction Layer Security]

Output: Requires additional payload security

XML Key Management Specification (XKMS 2.0) Bindings


Input: [0] Unspecified Party Authentication [Payload Security] Supported [Transaction Layer Security]

Output: Requires additional payload security

XML Key Management Specification (XKMS 2.0) Bindings


Input: [0] Client Authentication [Payload Security] Supported [Transaction Layer Security]

Output: Supported through certificate client authentication or through use of payload security.

XML Key Management Specification (XKMS 2.0) Bindings


Input: [0] Dependencies [Transaction Layer Security] Authentication mechanism defined by TLS which clients must implement [Payload Security]

Output: Authentication defined by XKMS specification, client does not need to implement a comprehensive framework.

XML Key Management Specification (XKMS 2.0) Bindings


Input: [0] Use of XML Signature [Transaction Layer Security] Not required [Payload Security]

Output: Uses XML Signature in Enveloped Mode requiring slightly more complex processing.

XML Key Management Specification (XKMS 2.0) Bindings


Input: [0] Support for Routing [Transaction Layer Security] None [Payload Security]

Output: Specification describes bi-lateral authentication only, multi-hop message routing and multi-party transactions are not supported.

XML Key Management Specification (XKMS 2.0) Bindings


Input: [0] Support for Confidentiality [Transaction Layer Security] Supported [Payload Security]

Output: None, although applications may employ TLS to establish a secure channel

XML Key Management Specification (XKMS 2.0) Bindings


Input: [0] Non-Repudiation [Transaction Layer Security] Requires additional payload security [Payload Security]

Output: Supported

XML Key Management Specification (XKMS 2.0) Bindings


Input: [0] Unspecified Party Authentication [Transaction Layer Security] Requires additional payload security [Payload Security]

Output: Supported

XML Key Management Specification (XKMS 2.0) Bindings


Input: [0] Client Authentication [Transaction Layer Security] Supported through certificate client authentication or through use of payload security. [Payload Security]

Output: Supported

XML Key Management Specification (XKMS 2.0) Bindings


Input: [User A’s Friends List] User B [User B’s Friends List] User A [User A’s Profile] Bidirlink as Friends [User B’s Profile]

Output: Bidirlink as Friends

Creating a Social Network from an Existing Bulletin Board Community


Input: [User A’s Friends List] User B [User A’s Profile] Is Linked to B as Friend [User B’s Profile]

Output: Is Linked from A as Friend

Creating a Social Network from an Existing Bulletin Board Community


Input: [User B’s Friends List] User A [User A’s Profile] Is Linked from B as Friend [User B’s Profile]

Output: Is Linked to A as Friend

Creating a Social Network from an Existing Bulletin Board Community


Input: [User A’s Enemies List] User B [User B’s Enemies List] User A [User A’s Profile] Bidirlink as Enemies [User B’s Profile]

Output: Bidirlink as Enemies

Creating a Social Network from an Existing Bulletin Board Community


Input: [User A’s Enemies List] User B [User A’s Profile] Is Linked to B as Enemy [User B’s Profile]

Output: Is Linked from A as Enemy

Creating a Social Network from an Existing Bulletin Board Community


Input: [User B’s Enemies List] User A [User A’s Profile] Is Linked from B as Enemy [User B’s Profile]

Output: Is Linked to A as Enemy

Creating a Social Network from an Existing Bulletin Board Community


Input: [User A’s Enemies List] User B [User B’s Friends List] User A [User A’s Profile] Nothing Appears [User B’s Profile]

Output: Nothing Appears

Creating a Social Network from an Existing Bulletin Board Community


Input: [User A’s Friends List] User B [User B’s Enemies List] User A [User A’s Profile] Nothing Appears [User B’s Profile]

Output: Nothing Appears

Creating a Social Network from an Existing Bulletin Board Community


Input: [Status] Proposal [Summary] Proposal to address the basic description of Articles within issues and/or volumes of periodicals of most types. [Vocab] Three new Types: Periodical, PublicationVolume, PublicationIssue, and added properties for two existent Types: Article, CreativeWork [Topic]

Output: Periodicals, Articles and Multi-volume Works

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] Proposal for new Audiobook Type and abridged property for Book. [Vocab] Audiobook subtype of Book and of AudioObject, adds readBy property [Topic]

Output: Audiobook

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] Proposal for new Collection Type and part properties for CreativeWork. [Vocab] Collection subtype of CreativeWork hasPart & isPartOf properties for CreativeWork [Topic]

Output: Collection

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Discussion [Summary] Extension for describing accessibility properties of a CreativeWork. [Vocab] Add accessMode, hasAdapation, isAdaptationof that were not covered in 1.0 [Topic]

Output: Accessibility

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Accepted [Summary] Add one property 'department' to Organization, to allow local businesses to describe their depts (e.g. opening hours) in detail. Final discussion on whether to call it subOrganizationOf instead. [Vocab] department property (range and domain both Organization) [Comments] Proposal very greatly simplified after WebSchemas discussion. [Topic]

Output: Add Organization department property

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] Add one type, 'QuotationSchema', a kind of CreativeWork, alongside some supporting properties. [Vocab] Quotation, spokenByCharacter, incorrectlyAttributedTo, aboutEvent, fromEvent, addressee. [Comments] Several other requirements are addressed by re-use of existing properties. Debate about whether incorrectlyAttributedTo is worthwhile. Some details to finalise. [Topic]

Output: Add Quotation type

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] Add handlers and potential actions to Action type. [Vocab] See full entry and proposal for details. [Comments] The schema.org team solicit comments on this draft via public-vocabs@w3.org. [Topic]

Output: Actions in Schema.org (part 2)

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] "While schema.org already supports marking up offers to sell products (pre-transaction), it does not currently provide schema for the common kinds of confirmations and notifications around orders (post-transaction)". [Vocab] Adds classes OrderStatus, Order, DeliveryMethod plus associated properties. [Comments] Complements Actions proposal, but independent. [Topic]

Output: Orders in Schema.org

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] This proposal includes new types for describing reservations and tickets [Vocab] Adds classes Reservation, ReservationStatus, ProgramMembership, Flight, TrainTrip, TrainReservation, FoodEstablishmentReservation, FlightReservation, EventReservation, ReservationPackage, BusReservation, BusTrip, RentalCarReservation, RentalCar, Car, LodgingReservation plus associated properties. [Comments] Complements Actions proposal, but independent. [Topic]

Output: Reservations in Schema.org

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] This proposal adds a single new type, EmailMessage [Vocab] EmailMessage is a CreativeWork representing email messages, just as WebPage already represents Web pages. [Comments] No properties currently defined; proposals welcomed. [Topic]

Output: EmailMessage type

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] Describing public civic services [Vocab] A proposal extending schema.org to cover various kinds of civic services. [Comments] GovernmentService, several kinds of CivicPermit, CivicAudience, BusinessAudience; various properties [Topic]

Output: Civic Services

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Accepted [Summary] This proposal adds a single new type, WorkersUnion, addressing issue 17 in the WebSchemas tracker. [Vocab] "A Workers Union (...) is an organization that promotes the interests of its worker members by collectively bargaining with management, organizing, and political lobbying."" [Comments] One type, see draft schema. [Topic]

Output: Workers Union type

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Accepted; published in next version [Summary] Proposes modest changes and additions to support TV and radio (from EBU and BBC). [Vocab] Adds Series, Season, Episode under CreativeWork. Existing TVSeries, TVSeason, TVEpisode under Series/Season/Episode. Adds RadioSeries/RadioSeason/RadioEpisode alongside. Adds Programme/Clip for programmes other than episodes. Adds description of a service with Service/PublicationEvent for broadcast, streaming, VoD, etc. [Comments] See also background notes and [[1]]. Draft initially from EBU/BBC/NoTube discussions. Nearby vocab: see VideoObject, AudioObject; Movie. Event re scheduling. See also UserPlays, a kind of UserInteraction. Comics and TV/Radio also share a concern for describing fictional characters and narratives. [Topic]

Output: TV and Radio proposal

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Some initial discussions. [Summary] Several parties are working towards a Sports Vocabulary proposal. See query from Paul Kelly (SportsML), Microdata + Sports Stats post describing earlier ESPN/Google collaboration, and the Sports Ontology used by BBC, Press Association and others. See also sports-schema-collab mailing list. [Vocab] Several sources including a full draft from the ESPN+Google work. Needs summary here. [Comments] March 2nd - posted writeup of the ESPN/Google Microdata vocabulary; next is discussion on finding common basic sports vocab for schema.org. [Topic]

Output: Sports

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Discussing Proposals [Summary] Proposal from Marvel (see examples). [Vocab] Adds PeriodicalSeries (under Intangible(?)), PeriodicalIssue (under CreativeWork), Comic Issue (under PeriodicalIssue), GraphicNovel (under Book). Approx 6-9 properties for each of these classes. [Comments] Generally well received and specified, but some detailed discussion re fine-grain detail of comics (imprint, page count etc.). Can those properties be shared with Book/numberOfPages, or ScholarlyArticle? Should PeriodicalSeries be intangible? [Topic]

Output: Comics and Serials

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Hopefully Final Proposal - please review [Summary] Proposes some modifications to Event based on deployment experience. [Vocab] Adds eventStatus, previousStartDate, previousEndDate; eventCategory; makes startDate/endDate repeatable. Encourages use of 'url' from Thing. [Comments] Fairly modest proposals based on implementor feedback. May2013 update addresses the last open issue on repeating events. [Topic]

Output: Event schema update

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] The historical-data.org site proposes some extensions to schema.org to address historical and genealogical (family history) scenarios. [Vocab] Adds HistoricalRecord, HistoricalEvent (subclass of Event), overrides attendees, subEvents, superEvent to point to HistoricalEvent. [Comments] There is an associated implementation, github repository, and blog. [Topic]

Output: Historical Data proposal

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] A schema extension for describing biological databases, Sagace. [Vocab] Adds a class 'BiologicalDatabaseEntry' as a kind of CreativeWork, introducing 'entryID', 'isEntryOf', 'taxonID'. Adds 'BiologicalDatabase' also subclass of CreativeWork, with no special properties. Both also use 'breadcrumb' from WebPage. [Comments] Others have also mentioned interest in adding some notion of species. [Topic]

Output: Biological Databases

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] A proposal resolving current problems handling breadcrumbs. [Vocab] Adds Breadcrumb type with child property and supposes to use this class on breadcrumb property of a WebPage. An important schema, but needs attention. See discussion on using literal values. [Topic]

Output: Breadcrumbs

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] A proposal extending schema.org for describing online discussion forums and message boards. [Vocab] Adds attachmentURL, contributorType, discussionState, interestedUsers, postCount, postType, votedHelpful. [Comments] Addition candidate [Topic]

Output: Discussion

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] A proposal extending schema.org for describing Innovation and related concepts. Discussion found here: [2] [Vocab] Covers concepts and terms such as Need, Benefit, Usage, Disruption, Innovator, Innovation, Embodiment, to name a few. See [3] for complete list of terms. [Comments] Addition candidate [Topic]

Output: Innovation

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] Add a dissolutionDate property to Organization. [Topic]

Output: dissolutionDate

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] A proposal for extending LodgingBusiness. Specification is here http://thematix.com/ontologies/travel/lodging/ [Vocab] Adds Amenity, BusinessService, Feature, GuestRoomAmenity, LodgingBusinessAmenity, LodgingBusinessService, RentalOffer, RentalRate, Room, RoomType and Service. [Comments] In addition to the examples given in the cited website, examples can be seen at http://www.regencyhotelmiami.com/ and http://hiltonvb.com and at Super8 hotel description pages, e.g., http://www.super8.com/hotels/alberta/fort-mcmurray/super-8-fort-mcmurray/hotel-overview. [Topic]

Output: Lodging Extensions

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Topic]

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] How far along [Summary] Summary of contribution. [Vocab] Overview of new terms [Comments] Comments on status, particularly regarding integration, overlaps and open issues. [Topic]

Output: Proposal name

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Requirement] Some [Comments] The information provided by an XKMS service may be confidential, the fact that a party has requested particular information from an XKMS service may allow confidential information to be deduced. Many XKMS applications do not require confidentiality however. [Security Issue]

Output: Confidentiality

XML Key Management Specification (XKMS 2.0) Bindings


Input: [Requirement] Some [Comments] A service only needs to authenticate a request for information if either the information is confidential or some form of charge is to be made for use of the service. [Security Issue]

Output: Request Authentication

XML Key Management Specification (XKMS 2.0) Bindings


Input: [Requirement] Most [Comments] An XKMS service that provides only a Location service for self authenticating key information such as Digital Certificates does not require authentication. [Security Issue]

Output: Response Authentication

XML Key Management Specification (XKMS 2.0) Bindings


Input: [Requirement] Some [Comments] Although some XKMS applications have a specific requirement to support Non-Repudiation, the ability to repudiate requests and responses is acceptable in many applications. [Security Issue]

Output: Persistent Authentication

XML Key Management Specification (XKMS 2.0) Bindings


Input: [Requirement] All [Comments] The RequestId correspondence mechanism can only be used if the Request Authentication mechanism can be relied upon. Otherwise the Digest Mechanism should be used. [Security Issue]

Output: Message Correspondence

XML Key Management Specification (XKMS 2.0) Bindings


Input: [Requirement] Some [Comments] Request replay attacks are likely to only be a concern if the service charges on a per request basis or as a type of Denial of Service attack. [Security Issue]

Output: Request Replay

XML Key Management Specification (XKMS 2.0) Bindings


Input: [Requirement] Most [Comments] Any service made available on a public network is likely to be subject to a Denial of Service attack. The risk of a Denial of Service attack is generally considered to be reduced on closed networks such as internal enterprise networks. [Security Issue]

Output: Denial of Service

XML Key Management Specification (XKMS 2.0) Bindings


Input: [Data category] Translate [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] Yes [Local Usage]

Output: Yes

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


Input: [Data category] Localization Note [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] Yes [Local Usage]

Output: Yes

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


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

Output: Yes

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


Input: [Data category] Directionality [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] Yes [Local Usage]

Output: Yes

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


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

Output: Yes

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


Input: [Data category] Language Information [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] Yes [Local Usage]

Output: No

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


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

Output: No

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


Input: [Change] Group By clause in FLWOR expression. [Bugzilla] None. [Category] Substantive. [Description]

Output: A new clause was added to the FLWOR expression to allow query writers to cause groups of tuples to be created based on the values of some expression.


Input: [Change] Window clause in FLWOR expression. [Bugzilla] None. [Category] Substantive. [Description]

Output: A new clause was added to the FLWOR expression to allow query writers to create sliding and tumbling windows of tuples based on a number of criteria.


Input: [Change] Simplification of FLWOR expression. [Bugzilla] None. [Category] Substantive. [Description]

Output: The syntax of the FLWOR expression was considerably relaxed, permitting most clauses (other than the return clause) to be used at almost any position (only a few clauses are allowed to be the first clause) within a FLWOR expression.


Input: [Change] Outer for supported in FLWOR expressions. [Bugzilla] None. [Category] Substantive. [Description]

Output: The syntax of the for clause in FLWOR expressions was extended to allow the use of "outer for".


Input: [Change] Count clause in FLWOR expression. [Bugzilla] None. [Category] Substantive. [Description]

Output: A new clause was added to the FLWOR expression to allow query writers to capture the total number of items that are returned by a (portion of a) FLWOR expression.


Input: [Change] Declaration of decimal number formats. [Bugzilla] None. [Category] Substantive. [Description]

Output: A new option was added to the query prologue, allowing query authors to specify a named (or an unnamed default) format for decimal numbers. This allows the specification of such items as the decimal separator, the minus sign, the percent and per mille signs, and even the class of Unicode digits.


Input: [Change] Query version and encoding declaration. [Bugzilla] None. [Category] Substantive. [Description]

Output: Allows specification of either or both of the version of XQuery to which a query adheres and the encoding of the query (e.g., UTF8, ISO8859-1).


Input: [Change] Enhanced validation expression. [Bugzilla] [XQuery 1.1] Requirement: validation by type [Category] Substantive. [Description]

Output: Permits query authors to validate an expression against a specified XML Schema type.


Input: [Change] Nondeterministic external functions. [Bugzilla] None. [Category] Substantive. [Description]

Output: Functions declared to be external functions can also be specified to be deterministic or nondeterministic.


Input: [Change] Syntax used to provide default value for external variables. [Bugzilla] None. [Category] Minor. [Description]

Output: The declaration of external variables now uses ":=" to indicate the default value given to such variables, instead of the keyword "default".


Input: [Change] Try/catch for error handling. [Bugzilla] None. [Category] Substantive. [Description]

Output: A try/catch facility is provided that allows query authors to control how errors are handled when raised by evaluation of queries.


Input: [Change] Context item declaration. [Bugzilla] None. [Category] Substantive. [Description]

Output: It is now possible to declare both the type of and the default initial value of the context item of a query, and to specify whether its value may be provided by the external environment.


Input: [Change] Computed namespace constructor. [Bugzilla] None. [Category] Substantive. [Description]

Output: Added new complex type and element to XQueryX schema, and new template to XQueryX stylesheet, in support of computed namespace constructors in XQuery 1.1.


Input: [Change] Generate proper syntax for variable names in positional variable bindings. [Bugzilla] [XQX30] template for positionalVariableBinding [Category] Substantive. [Description]

Output: Modified XQueryX stylesheet template to correctly generate a "$" preceding the variable name.


Input: [Change] Allow positional variable bindings to be optional in window variables. [Bugzilla] [XQX30] positionalVariableBinding should be optional in windowVars [Category] Substantive. [Description]

Output: Modified XQueryX schema to add minOccurs="0" on element positionalVariableBinding in windowVars complex type definition.


Input: [Change] XQueryX syntax must allow wildcards in the try/catch error list. [Bugzilla] [XQX30] cannot represent a catchErrorList wildcard in XQueryX [Category] Substantive. [Description]

Output: In XQueryX schema, modified catchErrorList complex type definition to allow a choice between a nameText (essentially a QName) and a Wildcard. In XQueryX stylesheet, modified catchErrorList template to support Wildcard as well as nameText.


Input: [Change] Private functions. [Bugzilla] None. [Category] Substantive. [Description]

Output: In XQueryX schema, added new attribute "private" in functionDecl complex type. In XQUeryX stylesheet, template for functionDecl, added support for @private (generate "private" for private functions and "public" for others)


Input: [Change] Replace "outer for" with "allowing empty". [Bugzilla] None. [Category] Substantive. [Description]

Output: In XQueryX schema, forClause complex type, delete attribute "outer"; in forClauseItem complex type, add new element allowingEmpty. In XQueryX stylesheet template for forClause, remove generation of "outer"; in template for forClauseItem, generate "allowing empty".


Input: [Change] Higher-order functions. [Bugzilla] None. [Category] Substantive. [Description]

Output: Made changes to XQueryX schema and stylesheet corresponding to new higher-order function syntax in XQuery 1.1.


Input: [Change] New "switch" expression ("value switch", analogous to typeswitch). [Bugzilla] None. [Category] Substantive. [Description]

Output: Made changes to XQueryX schema and stylesheet corresponding to new switch syntax in XQuery 3.0.


Input: [Change] Support for partial function application. [Bugzilla] None. [Category] Substantive. [Description]

Output: Made changes to XQueryX schema and stylesheet to support the partial function application capability of XQuery 3.0.


Input: [Change] XML Schema and XSLT Stylesheet [Bugzilla] lack of syntactic symmetry between the control flow expressions [Category] Substantive. [Description]

Output: Eliminated the possibility of defining three "error variables" as part of the catch clause; those variables (and others) are now implicitly defined, and may be used without explicit definition. At the same time, fixed a bug in the schema and stylesheet that recognized and produced invalid syntax for the validation expression.


Input: 77,000 USD

Output: For-profit organization that has annual gross revenue, as measured by the most recent audited statement, of greater than or equal to 1,000,000,000 USD.

Organization Type in Upper Middle Income Country (World Bank category)


Input: 68,500 USD

Output: For-profit organization that has annual gross revenue, as measured by the most recent audited statement, of greater than or equal to 50,000,000 USD and less than 1,000,000,000 USD.

Organization Type in Upper Middle Income Country (World Bank category)


Input: 34,250 USD

Output: Introductory Industry Membership, available for two years to a for-profit organization that has annual gross revenue, as measured by the most recent audited statement, of greater than or equal to 50,000,000 USD. Participation limited to one Interest Group

Organization Type in Upper Middle Income Country (World Bank category)


Input: 7,900 USD

Output: For-profit organization that has annual gross revenue, as measured by the most recent audited statement, of greater than or equal to 30,000,000 USD and less than 50,000,000 USD.

Organization Type in Upper Middle Income Country (World Bank category)


Input: 2,250 USD

Output: Enterprises and non-profits with 10 or fewer employees, who are not also membership organizations, revenues less than 3,000,000 USD and have never been a W3C Member. This fee only valid for the first two years of W3C Membership.

Organization Type in Upper Middle Income Country (World Bank category)


Input: 3,810 USD

Output: All other organizations, including non-profit organizations and government agencies.

Organization Type in Upper Middle Income Country (World Bank category)


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

Output: Hidden


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

Output: Text


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

Output: Search


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

Output: Telephone


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

Output: URL


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

Output: E-mail


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

Output: Password


Input: [Keyword] datetime [Data type] A date and time (year, month, day, hour, minute, second, fraction of a second) with the time zone set to UTC [Control type] A date and time control [State]

Output: Date and Time


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

Output: Date


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

Output: Month


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

Output: Week


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

Output: Time


Input: [Keyword] datetime-local [Data type] A date and time (year, month, day, hour, minute, second, fraction of a second) with no time zone [Control type] A date and time control [State]

Output: Local Date and Time


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

Output: Number


Input: [Keyword] range [Data type] A numerical value, with the extra semantic that the exact value is not important [Control type] A slider control or similar [State]

Output: Range


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

Output: Color


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

Output: Checkbox


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

Output: Radio Button


Input: [Keyword] file [Data type] Zero or more files each with a MIME type and optionally a file name [Control type] A label and a button [State]

Output: File Upload


Input: [Keyword] submit [Data type] An enumerated value, with the extra semantic that it must be the last value selected and initiates form submission [Control type] A button [State]

Output: Submit Button


Input: [Keyword] image [Data type] A coordinate, relative to a particular image's size, with the extra semantic that it must be the last value selected and initiates form submission [Control type] Either a clickable image, or a button [State]

Output: Image Button


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

Output: Reset Button


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

Output: Button


Input: [Data category] Translate [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes [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] Yes

Output: No

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 [Default Values] None [Inheritance] Textual content of element, including content of child elements, but excluding attributes [Overriding] Yes

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 [Default Values] term="no" [Inheritance] None [Overriding] Not applicable

Output: Yes

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 [Default Values] dir="ltr" [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes

Output: No

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 [Default Values] None [Inheritance] None [Overriding] Not applicable

Output: Yes

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 [Default Values] None [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes

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 [Default Values] withinText="no" [Inheritance] None [Overriding] Not applicable

Output: No

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


Input: [Keyword] hidden [State] Hidden [Data type] An arbitrary string [Control type]

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: Text field

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: Search field

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: A text field

4.10.7 The input element — HTML5: Edition for Web Authors


Input: [Keyword] url [State] URL [Data type] An absolute IRI [Control type]

Output: A text field

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: A text field

4.10.7 The input element — HTML5: Edition for Web Authors


Input: [Keyword] password [State] Password [Data type] Text with no line breaks (sensitive information) [Control type]

Output: Text field that obscures data entry

4.10.7 The input element — HTML5: Edition for Web Authors


Input: [Keyword] datetime [State] Date and Time [Data type] A date and time (year, month, day, hour, minute, second, fraction of a second) with the time zone set to UTC [Control type]

Output: A date and time control

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: A date control

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: A month control

4.10.7 The input element — HTML5: Edition for Web Authors


Input: [Keyword] week [State] Week [Data type] A date consisting of a week-year number and a week number with no time zone [Control type]

Output: A week control

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: A time control

4.10.7 The input element — HTML5: Edition for Web Authors


Input: [Keyword] datetime-local [State] Local Date and Time [Data type] A date and time (year, month, day, hour, minute, second, fraction of a second) with no time zone [Control type]

Output: A date and time control

4.10.7 The input element — HTML5: Edition for Web Authors


Input: [Keyword] number [State] Number [Data type] A numerical value [Control type]

Output: A text field or spinner control

4.10.7 The input element — HTML5: Edition for Web Authors


Input: [Keyword] range [State] Range [Data type] A numerical value, with the extra semantic that the exact value is not important [Control type]

Output: A slider control or similar

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: A color well

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: A checkbox

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: A radio button

4.10.7 The input element — HTML5: Edition for Web Authors


Input: [Keyword] file [State] File Upload [Data type] Zero or more files each with a MIME type and optionally a file name [Control type]

Output: A label and a button

4.10.7 The input element — HTML5: Edition for Web Authors


Input: [Keyword] submit [State] Submit Button [Data type] An enumerated value, with the extra semantic that it must be the last value selected and initiates form submission [Control type]

Output: A button

4.10.7 The input element — HTML5: Edition for Web Authors


Input: [Keyword] image [State] Image Button [Data type] A coordinate, relative to a particular image's size, with the extra semantic that it must be the last value selected and initiates form submission [Control type]

Output: Either a clickable image, or a button

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: A button

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: A button

4.10.7 The input element — HTML5: Edition for Web Authors


Input: [Requirement] Use valid (X)HTML [Details] Using valid HTML means having an HTML code that follows one of the DTDs of the HTML specification. Your best choice is valid XHTML strict markup: XHTML means that the code will benefit from all the XML power, and strict ensures your site won't mix presentation markup with the structure. [Test tool] The W3C HTML Validator is one of the many options available. The LogValidator is especially helpful in maintaining a valid Web site. [Rationale]

Output: Valid HTML code is a first step toward more compatibility with browsers and better rendering on the latest ones. Using only strict HTML (that is, the Strict HTML DTD) makes the site easier to maintain and evolve.

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use extensively valid CSS [Details] Avoid any presentational markup and keep all the layout features in well-defined CSS style sheets. [Test tool] The CSS Validator detects any non-compliant use of the CSS technologies. [Rationale]

Output: Linked style sheets allow presentation to be decoupled completely from the page structure of your site, and lets you quickly change its layout and rendering. It also guarantees that everybody can adjust the rendering to their needs and tastes.

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use HTTP properly [Details] Make sure that each page of your site is accessible with a stable address (URL) and that the HTTP caching properties are set correctly. Make sure if you migrate to a new site version that the URLs are either kept as is or at least redirected to the new ones. [Test tool] The W3C Link Checker can provide some help. Besides, the advices given in the Common HTTP Implementation Problems Note can help assess what needs to be respected. [Rationale]

Output: HTTP is a very powerful protocol and you get most of its power with stable URLs and an efficient caching system: bookmarks and links don't break, network access is faster, users are happy!

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use SVG and PNG for graphics [Details] Use PNG for raster images, and SVG for all others. [Test tool] N/A [Rationale]

Output: PNG is a much more capable format than other binary formats for raster images because it provides better compression, more options, and it's free. The best format you should require is SVG: it's scalable, XML-based, very light, and has a lot of capabilities, for example, animation using SMIL, which is supported on cell phones, etc.

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use techniques to make your content accessible [Details] Details. [Test tool] See Evaluation Tools for Web Content Accessibility. [Rationale]

Output: Making a site accessible benefits all of your users, and broadens your current audience. This requirement may be required by law in some countries.

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use standards scripting languages [Details] Use the DOM API combined with Ecmascript (but don't make the use of scripts mandatory to navigate in the site!). [Test tool] N/A [Rationale]

Output: DOM and Ecmascript (the common standard behind Javascript and JScript) are the best way to go to get interoperable scripts to create animations in your Web site. But do not forget your users that don't have these scripting capacities enabled.

Buy standards compliant Web sites — W3C QA


Input: [Model] Secure complete subtrees [Server-Side Access Control] possible [Subtree encryption] possible [Pool encryption]

Output: possible

XML Encryption Workshop - Geuer-Pollmann


Input: [Model] Secure only attribute values [Server-Side Access Control] possible [Subtree encryption] possible (depends on proposal) [Pool encryption]

Output: possible

XML Encryption Workshop - Geuer-Pollmann


Input: [Model] Leave "deep" descendants visible [Server-Side Access Control] yes [Subtree encryption] no [Pool encryption]

Output: yes

XML Encryption Workshop - Geuer-Pollmann


Input: [Model] Needs trustworthy server [Server-Side Access Control] yes [Subtree encryption] no [Pool encryption]

Output: no

XML Encryption Workshop - Geuer-Pollmann


Input: [Model] Automation of access/encryption decisions [Server-Side Access Control] yes [Subtree encryption] needs some sort of style sheet [Pool encryption]

Output: needs some sort of style sheet

XML Encryption Workshop - Geuer-Pollmann


Input: [Model] Needs additional transport security (SSL) [Server-Side Access Control] yes [Subtree encryption] no [Pool encryption]

Output: no

XML Encryption Workshop - Geuer-Pollmann


Input: [Model] New recipients can without reencrypting content [Server-Side Access Control] yes, only new (X)ACL [Subtree encryption] depends on situation [Pool encryption]

Output: yes

XML Encryption Workshop - Geuer-Pollmann


Input: [Process Stage] Activity proposal with charter(s) Draft charters include proposed patent licensing mode. Advisory Committee representatives comment on proposed licensing mode.

Process Changes Proposed by draft Patent Policy


Input: [Process Stage] Call for participation in a Working Group Revised patent disclosure questions will replace IPR section of Call for Review/Participation none


Input: [Process Stage] Submission to W3C Submissions must include complete patent disclosures and proposed licensing terms. Determine relevant disclosures to be made and licensing commitment as part of preparing Submission.

Output: Determine relevant disclosures to be made and licensing commitment as part of preparing Submission intended for the Working Group.


Input: [Process Stage] Working Drafts none none


Input: [Process Stage] Last Call Working Draft Opt-out of RAND licensing obligation within 60 days after Last Call Working Draft published. All W3C Members who do not want to make essential technology available on RAND terms must indicate which patents they plan to withhold within 60 days after the publication of the Last Call Working Draft.

Output: All Working Group members who do not want to make essential technology available on RAND terms must indicate which patents they plan to withhold within 60 days after the publication of the Last Call Working Draft.


Input: [Process Stage] Candidate Recommendation, Proposed Recommendation, Recommendation Specifications may not advance unless they have met the licensing mode specified in the Working Group charter. n/a


Input: [Process Stage] Activity proposal with charter(s) Draft charters include proposed patent licensing mode. n/a

Output: Advisory Committee representatives comment on proposed licensing mode.


Input: [Process Stage] Call for participation in a Working Group Revised patent disclosure questions will replace IPR section of Call for Review/Participation none


Input: [Process Stage] Submission to W3C Submissions must include complete patent disclosures and proposed licensing terms. Determine relevant disclosures to be made and licensing commitment as part of preparing Submission intended for the Working Group.

Output: Determine relevant disclosures to be made and licensing commitment as part of preparing Submission.


Input: [Process Stage] Working Drafts none none


Input: [Process Stage] Last Call Working Draft Opt-out of RAND licensing obligation within 60 days after Last Call Working Draft published. All Working Group members who do not want to make essential technology available on RAND terms must indicate which patents they plan to withhold within 60 days after the publication of the Last Call Working Draft.

Output: All W3C Members who do not want to make essential technology available on RAND terms must indicate which patents they plan to withhold within 60 days after the publication of the Last Call Working Draft.


Input: [Process Stage] Candidate Recommendation, Proposed Recommendation, Recommendation Specifications may not advance unless they have met the licensing mode specified in the Working Group charter. n/a


Input: Draft charters include proposed patent licensing mode. Advisory Committee representatives comment on proposed licensing mode. n/a [Process Stage]

Output: Activity proposal with charter(s)


Input: Revised patent disclosure questions will replace IPR section of Call for Review/Participation none none [Process Stage]

Output: Call for participation in a Working Group


Input: Submissions must include complete patent disclosures and proposed licensing terms. Determine relevant disclosures to be made and licensing commitment as part of preparing Submission. Determine relevant disclosures to be made and licensing commitment as part of preparing Submission intended for the Working Group. [Process Stage]

Output: Submission to W3C


Input: none none none [Process Stage]

Output: Working Drafts


Input: Opt-out of RAND licensing obligation within 60 days after Last Call Working Draft published. All W3C Members who do not want to make essential technology available on RAND terms must indicate which patents they plan to withhold within 60 days after the publication of the Last Call Working Draft. All Working Group members who do not want to make essential technology available on RAND terms must indicate which patents they plan to withhold within 60 days after the publication of the Last Call Working Draft. [Process Stage]

Output: Last Call Working Draft


Input: Specifications may not advance unless they have met the licensing mode specified in the Working Group charter. n/a n/a [Process Stage]

Output: Candidate Recommendation, Proposed Recommendation, Recommendation


Input: [Security Issue] Confidentiality [Requirement] Some [Comments]

Output: The information provided by an XKMS service may be confidential, the fact that a party has requested particular information from an XKMS service may allow confidential information to be deduced. Many XKMS applications do not require confidentiality however.

XML Key Management Specification (XKMS 2.0) Bindings


Input: [Security Issue] Request Authentication [Requirement] Some [Comments]

Output: A service only needs to authenticate a request for information if either the information is confidential or some form of charge is to be made for use of the service.

XML Key Management Specification (XKMS 2.0) Bindings


Input: [Security Issue] Response Authentication [Requirement] Most [Comments]

Output: An XKMS service that provides only a Location service for self authenticating key information such as Digital Certificates does not require authentication.

XML Key Management Specification (XKMS 2.0) Bindings


Input: [Security Issue] Persistent Authentication [Requirement] Some [Comments]

Output: Although some XKMS applications have a specific requirement to support Non-Repudiation, the ability to repudiate requests and responses is acceptable in many applications.

XML Key Management Specification (XKMS 2.0) Bindings


Input: [Security Issue] Message Correspondence [Requirement] All [Comments]

Output: The RequestId correspondence mechanism can only be used if the Request Authentication mechanism can be relied upon. Otherwise the Digest Mechanism should be used.

XML Key Management Specification (XKMS 2.0) Bindings


Input: [Security Issue] Request Replay [Requirement] Some [Comments]

Output: Request replay attacks are likely to only be a concern if the service charges on a per request basis or as a type of Denial of Service attack.

XML Key Management Specification (XKMS 2.0) Bindings


Input: [Security Issue] Denial of Service [Requirement] Most [Comments]

Output: Any service made available on a public network is likely to be subject to a Denial of Service attack. The risk of a Denial of Service attack is generally considered to be reduced on closed networks such as internal enterprise networks.

XML Key Management Specification (XKMS 2.0) Bindings


Input: [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] Yes [Data category]

Output: Translate

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


Input: [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] Yes [Data category]

Output: Localization Note

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


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

Output: Terminology

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


Input: [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] Yes [Data category]

Output: Directionality

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


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

Output: Ruby

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


Input: [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] Yes [Data category]

Output: Language Information

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


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

Output: Elements Within Text

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


Input: [Process Stage] Activity proposal with charter(s) Advisory Committee representatives comment on proposed licensing mode. n/a

Output: Draft charters include proposed patent licensing mode.


Input: [Process Stage] Call for participation in a Working Group none none

Output: Revised patent disclosure questions will replace IPR section of Call for Review/Participation


Input: [Process Stage] Submission to W3C Determine relevant disclosures to be made and licensing commitment as part of preparing Submission. Determine relevant disclosures to be made and licensing commitment as part of preparing Submission intended for the Working Group.

Output: Submissions must include complete patent disclosures and proposed licensing terms.


Input: [Process Stage] Working Drafts none none


Input: [Process Stage] Last Call Working Draft All W3C Members who do not want to make essential technology available on RAND terms must indicate which patents they plan to withhold within 60 days after the publication of the Last Call Working Draft. All Working Group members who do not want to make essential technology available on RAND terms must indicate which patents they plan to withhold within 60 days after the publication of the Last Call Working Draft.

Output: Opt-out of RAND licensing obligation within 60 days after Last Call Working Draft published.


Input: [Process Stage] Candidate Recommendation, Proposed Recommendation, Recommendation n/a n/a

Output: Specifications may not advance unless they have met the licensing mode specified in the Working Group charter.


Input: [Security Issue] Confidentiality [Comments] The information provided by an XKMS service may be confidential, the fact that a party has requested particular information from an XKMS service may allow confidential information to be deduced. Many XKMS applications do not require confidentiality however. [Requirement]

Output: Some

XML Key Management Specification (XKMS 2.0) Bindings


Input: [Security Issue] Request Authentication [Comments] A service only needs to authenticate a request for information if either the information is confidential or some form of charge is to be made for use of the service. [Requirement]

Output: Some

XML Key Management Specification (XKMS 2.0) Bindings


Input: [Security Issue] Response Authentication [Comments] An XKMS service that provides only a Location service for self authenticating key information such as Digital Certificates does not require authentication. [Requirement]

Output: Most

XML Key Management Specification (XKMS 2.0) Bindings


Input: [Security Issue] Persistent Authentication [Comments] Although some XKMS applications have a specific requirement to support Non-Repudiation, the ability to repudiate requests and responses is acceptable in many applications. [Requirement]

Output: Some

XML Key Management Specification (XKMS 2.0) Bindings


Input: [Security Issue] Message Correspondence [Comments] The RequestId correspondence mechanism can only be used if the Request Authentication mechanism can be relied upon. Otherwise the Digest Mechanism should be used. [Requirement]

Output: All

XML Key Management Specification (XKMS 2.0) Bindings


Input: [Security Issue] Request Replay [Comments] Request replay attacks are likely to only be a concern if the service charges on a per request basis or as a type of Denial of Service attack. [Requirement]

Output: Some

XML Key Management Specification (XKMS 2.0) Bindings


Input: [Security Issue] Denial of Service [Comments] Any service made available on a public network is likely to be subject to a Denial of Service attack. The risk of a Denial of Service attack is generally considered to be reduced on closed networks such as internal enterprise networks. [Requirement]

Output: Most

XML Key Management Specification (XKMS 2.0) Bindings


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

Output: Hidden

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: Text

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: Search

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: Telephone

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: URL

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: E-mail

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: Password

4.10.7 The input element — HTML5: Edition for Web Authors


Input: [Keyword] datetime [Data type] A date and time (year, month, day, hour, minute, second, fraction of a second) with the time zone set to UTC [Control type] A date and time control [State]

Output: Date and Time

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: Date

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: Month

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: Week

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: Time

4.10.7 The input element — HTML5: Edition for Web Authors


Input: [Keyword] datetime-local [Data type] A date and time (year, month, day, hour, minute, second, fraction of a second) with no time zone [Control type] A date and time control [State]

Output: Local Date and Time

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: Number

4.10.7 The input element — HTML5: Edition for Web Authors


Input: [Keyword] range [Data type] A numerical value, with the extra semantic that the exact value is not important [Control type] A slider control or similar [State]

Output: Range

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: Color

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: Checkbox

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: Radio Button

4.10.7 The input element — HTML5: Edition for Web Authors


Input: [Keyword] file [Data type] Zero or more files each with a MIME type and optionally a file name [Control type] A label and a button [State]

Output: File Upload

4.10.7 The input element — HTML5: Edition for Web Authors


Input: [Keyword] submit [Data type] An enumerated value, with the extra semantic that it must be the last value selected and initiates form submission [Control type] A button [State]

Output: Submit Button

4.10.7 The input element — HTML5: Edition for Web Authors


Input: [Keyword] image [Data type] A coordinate, relative to a particular image's size, with the extra semantic that it must be the last value selected and initiates form submission [Control type] Either a clickable image, or a button [State]

Output: Image Button

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: Reset Button

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: Button

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: An arbitrary string

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: Text with no line breaks

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: Text with no line breaks

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: Text with no line breaks

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: An absolute IRI

4.10.7 The input element — HTML5: Edition for Web Authors


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

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

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: Text with no line breaks (sensitive information)

4.10.7 The input element — HTML5: Edition for Web Authors


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

4.10.7 The input element — HTML5: Edition for Web Authors


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

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

4.10.7 The input element — HTML5: Edition for Web Authors


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

4.10.7 The input element — HTML5: Edition for Web Authors


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

4.10.7 The input element — HTML5: Edition for Web Authors


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

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

4.10.7 The input element — HTML5: Edition for Web Authors


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

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: A numerical value

4.10.7 The input element — HTML5: Edition for Web Authors


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

4.10.7 The input element — HTML5: Edition for Web Authors


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

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

4.10.7 The input element — HTML5: Edition for Web Authors


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

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

4.10.7 The input element — HTML5: Edition for Web Authors


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

Output: An enumerated value

4.10.7 The input element — HTML5: Edition for Web Authors


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

4.10.7 The input element — HTML5: Edition for Web Authors


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

4.10.7 The input element — HTML5: Edition for Web Authors


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

4.10.7 The input element — HTML5: Edition for Web Authors


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

4.10.7 The input element — HTML5: Edition for Web Authors


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

4.10.7 The input element — HTML5: Edition for Web Authors


Input: [User A’s Friends List] User B [User B’s Friends List] User A [User B’s Profile] Bidirlink as Friends [User A’s Profile]

Output: Bidirlink as Friends

Creating a Social Network from an Existing Bulletin Board Community


Input: [User A’s Friends List] User B [User B’s Profile] Is Linked from A as Friend [User A’s Profile]

Output: Is Linked to B as Friend

Creating a Social Network from an Existing Bulletin Board Community


Input: [User B’s Friends List] User A [User B’s Profile] Is Linked to A as Friend [User A’s Profile]

Output: Is Linked from B as Friend

Creating a Social Network from an Existing Bulletin Board Community


Input: [User A’s Enemies List] User B [User B’s Enemies List] User A [User B’s Profile] Bidirlink as Enemies [User A’s Profile]

Output: Bidirlink as Enemies

Creating a Social Network from an Existing Bulletin Board Community


Input: [User A’s Enemies List] User B [User B’s Profile] Is Linked from A as Enemy [User A’s Profile]

Output: Is Linked to B as Enemy

Creating a Social Network from an Existing Bulletin Board Community


Input: [User B’s Enemies List] User A [User B’s Profile] Is Linked to A as Enemy [User A’s Profile]

Output: Is Linked from B as Enemy

Creating a Social Network from an Existing Bulletin Board Community


Input: [User A’s Enemies List] User B [User B’s Friends List] User A [User B’s Profile] Nothing Appears [User A’s Profile]

Output: Nothing Appears

Creating a Social Network from an Existing Bulletin Board Community


Input: [User A’s Friends List] User B [User B’s Enemies List] User A [User B’s Profile] Nothing Appears [User A’s Profile]

Output: Nothing Appears

Creating a Social Network from an Existing Bulletin Board Community


Input: [Change] Group By clause in FLWOR expression. [Bugzilla] None. [Category] Substantive. [Description]

Output: A new clause was added to the FLWOR expression to allow query writers to cause groups of tuples to be created based on the values of some expression.


Input: [Change] Window clause in FLWOR expression. [Bugzilla] None. [Category] Substantive. [Description]

Output: A new clause was added to the FLWOR expression to allow query writers to create sliding and tumbling windows of tuples based on a number of criteria.


Input: [Change] Simplification of FLWOR expression. [Bugzilla] None. [Category] Substantive. [Description]

Output: The syntax of the FLWOR expression was considerably relaxed, permitting most clauses (other than the return clause) to be used at almost any position (only a few clauses are allowed to be the first clause) within a FLWOR expression.


Input: [Change] Outer for supported in FLWOR expressions. [Bugzilla] None. [Category] Substantive. [Description]

Output: The syntax of the for clause in FLWOR expressions was extended to allow the use of "outer for".


Input: [Change] Count clause in FLWOR expression. [Bugzilla] None. [Category] Substantive. [Description]

Output: A new clause was added to the FLWOR expression to allow query writers to capture the total number of items that are returned by a (portion of a) FLWOR expression.


Input: [Change] Declaration of decimal number formats. [Bugzilla] None. [Category] Substantive. [Description]

Output: A new option was added to the query prologue, allowing query authors to specify a named (or an unnamed default) format for decimal numbers. This allows the specification of such items as the decimal separator, the minus sign, the percent and per mille signs, and even the class of Unicode digits.


Input: [Change] Query version and encoding declaration. [Bugzilla] None. [Category] Substantive. [Description]

Output: Allows specification of either or both of the version of XQuery to which a query adheres and the encoding of the query (e.g., UTF8, ISO8859-1).


Input: [Change] Enhanced validation expression. [Bugzilla] [XQuery 1.1] Requirement: validation by type [Category] Substantive. [Description]

Output: Permits query authors to validate an expression against a specified XML Schema type.


Input: [Change] Nondeterministic external functions. [Bugzilla] None. [Category] Substantive. [Description]

Output: Functions declared to be external functions can also be specified to be deterministic or nondeterministic.


Input: [Change] Syntax used to provide default value for external variables. [Bugzilla] None. [Category] Minor. [Description]

Output: The declaration of external variables now uses ":=" to indicate the default value given to such variables, instead of the keyword "default".


Input: [Change] Try/catch for error handling. [Bugzilla] None. [Category] Substantive. [Description]

Output: A try/catch facility is provided that allows query authors to control how errors are handled when raised by evaluation of queries.


Input: [Change] Context item declaration. [Bugzilla] None. [Category] Substantive. [Description]

Output: It is now possible to declare both the type of and the default initial value of the context item of a query, and to specify whether its value may be provided by the external environment.


Input: [Change] Computed namespace constructor. [Bugzilla] None. [Category] Substantive. [Description]

Output: Added new complex type and element to XQueryX schema, and new template to XQueryX stylesheet, in support of computed namespace constructors in XQuery 1.1.


Input: [Change] Generate proper syntax for variable names in positional variable bindings. [Bugzilla] [XQX30] template for positionalVariableBinding [Category] Substantive. [Description]

Output: Modified XQueryX stylesheet template to correctly generate a "$" preceding the variable name.