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

Output: Supported

XML Key Management Specification (XKMS 2.0) Bindings


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

Output: Supported

XML Key Management Specification (XKMS 2.0) Bindings


Input: [Feature] 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 group] Web accessibility manager/coordinator, liaison between accessibility group and technical development group [Web experience] high [HTML knowledge] high [Disability knowledge] low - high [Web accessibility knowledge] medium-high [Frequency of use *] daily for a month or so, then a couple times per month [Category]

Output: Web developers and content providers


Input: [User group] Web coder/technical developer [Web experience] high [HTML knowledge] high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] daily for a month or so, then a couple times per month [Category]

Output: Web developers and content providers


Input: [User group] Web interaction designer, usability specialist, application designer [Web experience] high [HTML knowledge] high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] daily for a month or so, then a couple times per month [Category]

Output: Web developers and content providers


Input: [User group] Web graphic designer [Web experience] high [HTML knowledge] usually high, can be low [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] daily for a week or so, then once per month or so [Category]

Output: Web developers and content providers


Input: [User group] Webmaster in small shop who performs multiple duties [Web experience] high [HTML knowledge] high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] daily for a month or so, then a couple times per month [Category]

Output: Web developers and content providers


Input: [User group] Web content provider (non-technical, maybe does not input content directly) [Web experience] low - high [HTML knowledge] low [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] daily for a week or so, then once per month or less [Category]

Output: Web developers and content providers


Input: [User group] Internet or intranet site manager [Web experience] high [HTML knowledge] high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] daily for a week or so, then once per month or so [Category]

Output: Web developers and content providers


Input: [User group] Authoring tool developers [Web experience] high [HTML knowledge] high [Disability knowledge] low [Web accessibility knowledge] low [Frequency of use *] daily for a month or so, then a couple times per month [Category]

Output: Tool developers


Input: [User group] User agent developers [Web experience] high [HTML knowledge] high [Disability knowledge] low [Web accessibility knowledge] low [Frequency of use *] daily for a month or so, then a couple times per month [Category]

Output: Tool developers


Input: [User group] Assistive technology developers [Web experience] low-high [HTML knowledge] often low [Disability knowledge] usually high in one area [Web accessibility knowledge] low-high [Frequency of use *] daily for a month or so, then a couple times per month [Category]

Output: Tool developers


Input: [User group] Web evaluation tool developers [Web experience] high [HTML knowledge] high [Disability knowledge] low-high [Web accessibility knowledge] high [Frequency of use *] several times per week in spurts [Category]

Output: Tool developers


Input: [User group] IT/ICT manager, CIO (or similar management role) [Web experience] high [HTML knowledge] low - high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] several times per day in a couple spurts per year [Category]

Output: Managers and assistants


Input: [User group] assistant to IT/ICT manager or CIO [Web experience] medium-high [HTML knowledge] mostly low, some medium [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] several times per day in a couple spurts [Category]

Output: Managers and assistants


Input: [User group] product manager (most likely to "feel the heat" for accessibility) [Web experience] mostly high [HTML knowledge] low - high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] several times per day at first, then seldom [Category]

Output: Managers and assistants


Input: [User group] project manager (e.g., managing one aspect of a Web application) [Web experience] mostly high [HTML knowledge] mostly high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] several times per day at first, then seldom [Category]

Output: Managers and assistants


Input: [User group] other managers, decision makers, influencers, people who pay for accessibilty [Web experience] low - high [HTML knowledge] low - high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] several times per day at first, then seldom [Category]

Output: Managers and assistants


Input: [User group] design shop sales/account manager who could/has been asked to include Web accessibility in contract [Web experience] medium-high [HTML knowledge] low-high (mostly medium) [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] several times per day in a couple spurts per year [Category]

Output: Related to contracts


Input: [User group] person setting up contract with outside Web design shop [Web experience] high [HTML knowledge] low - high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] several times per day in a couple spurts per year [Category]

Output: Related to contracts


Input: [User group] person with disability [Web experience] low-high [HTML knowledge] low-high [Disability knowledge] med-high [Web accessibility knowledge] low-high [Frequency of use *] probably only a few times (since not much there for non-webbie) [Category]

Output: Disability focused


Input: [User group] disability organization members, disability rights advocate [Web experience] low - high [HTML knowledge] mostly low, some up to high [Disability knowledge] high [Web accessibility knowledge] low-high (many low) [Frequency of use *] several times per day in a couple spurts per year [Category]

Output: Disability focused


Input: [User group] rehabilitation specialist [Web experience] low - high [HTML knowledge] mostly low [Disability knowledge] high [Web accessibility knowledge] low - medium [Frequency of use *] several times per day in a couple spurts per year [Category]

Output: Disability focused


Input: [User group] disabilities specialist/liaison/coordinator, e.g., in university or corporate human resources (HR) [Web experience] low - high [HTML knowledge] mostly low [Disability knowledge] medium-high [Web accessibility knowledge] mostly low [Frequency of use *] several times per day in a couple spurts [Category]

Output: Disability focused


Input: [User group] national or international standards developer [Web experience] low-high [HTML knowledge] low-high [Disability knowledge] low-high [Web accessibility knowledge] low-high [Frequency of use *] daily in spurts [Category]

Output: Other


Input: [User group] legislator, government policy maker (or assistant to) [Web experience] medium-high [HTML knowledge] mostly low, some high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] several times per day in a couple spurts per year [Category]

Output: Other


Input: [User group] policy maker for specific organization [Web experience] low - high [HTML knowledge] mostly low, some high [Disability knowledge] low - high [Web accessibility knowledge] low - high [Frequency of use *] several times per day in a one time spurt [Category]

Output: Other


Input: [User group] educator (including accessibility in courses) [Web experience] medium-high [HTML knowledge] low - high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] several times per day in a couple spurts per year [Category]

Output: Other


Input: [User group] reporter, journalist [Web experience] high [HTML knowledge] low-medium [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] several times per day in a spurt [Category]

Output: Other


Input: [User group] internal public relations or marketing [Web experience] mostly high [HTML knowledge] mostly low [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *] several times per day in a couple spurts per year [Category]

Output: Other


Input: [User group] researcher, or student doing paper on accessibility [Web experience] high [HTML knowledge] high [Disability knowledge] mostly low [Web accessibility knowledge] low [Frequency of use *] several times per day for a week [Category]

Output: Other


Input: [User group] W3C Team member (non WAI) [Web experience] high [HTML knowledge] high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low-medium [Frequency of use *] daily for a week or so, then a couple times per month [Category]

Output: Other


Input: [User group] WAI WG member [Web experience] high [HTML knowledge] mostly high [Disability knowledge] medium-high [Web accessibility knowledge] medium-high [Frequency of use *] several times per day - weekly [Category]

Output: Other


Input: [User group] Web accessibility specialist (consultant, evaluator, trainer) [Web experience] usually high [HTML knowledge] medium-high [Disability knowledge] medium-high [Web accessibility knowledge] medium-high [Frequency of use *] often a couple time per week [Category]

Output: Other


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: [postal] name [Structure] personname [Short display name] Name [Category]

Output: Physical Contact Information, Demographic and Socioeconomic Data

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [postal] street [Structure] unstructured [Short display name] Street Address [Category]

Output: Physical Contact Information

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [postal] city [Structure] unstructured [Short display name] City [Category]

Output: Demographic and Socioeconomic Data

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [postal] stateprov [Structure] unstructured [Short display name] State or Province [Category]

Output: Demographic and Socioeconomic Data

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [postal] postalcode [Structure] unstructured [Short display name] Postal Code [Category]

Output: Demographic and Socioeconomic Data

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [postal] country [Structure] unstructured [Short display name] Country Name [Category]

Output: Demographic and Socioeconomic Data

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [postal] organization [Structure] unstructured [Short display name] Organization Name [Category]

Output: Demographic and Socioeconomic Data

The Platform for Privacy Preferences 1.0 (P3P1.0) Specification


Input: [Category] Web developers and content providers [User group] Web accessibility manager/coordinator, liaison between accessibility group and technical development group [Web experience] high [HTML knowledge] high [Disability knowledge] low - high [Web accessibility knowledge] medium-high [Frequency of use *]

Output: daily for a month or so, then a couple times per month


Input: [Category] Web developers and content providers [User group] Web coder/technical developer [Web experience] high [HTML knowledge] high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: daily for a month or so, then a couple times per month


Input: [Category] Web developers and content providers [User group] Web interaction designer, usability specialist, application designer [Web experience] high [HTML knowledge] high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: daily for a month or so, then a couple times per month


Input: [Category] Web developers and content providers [User group] Web graphic designer [Web experience] high [HTML knowledge] usually high, can be low [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: daily for a week or so, then once per month or so


Input: [Category] Web developers and content providers [User group] Webmaster in small shop who performs multiple duties [Web experience] high [HTML knowledge] high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: daily for a month or so, then a couple times per month


Input: [Category] Web developers and content providers [User group] Web content provider (non-technical, maybe does not input content directly) [Web experience] low - high [HTML knowledge] low [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: daily for a week or so, then once per month or less


Input: [Category] Web developers and content providers [User group] Internet or intranet site manager [Web experience] high [HTML knowledge] high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: daily for a week or so, then once per month or so


Input: [Category] Tool developers [User group] Authoring tool developers [Web experience] high [HTML knowledge] high [Disability knowledge] low [Web accessibility knowledge] low [Frequency of use *]

Output: daily for a month or so, then a couple times per month


Input: [Category] Tool developers [User group] User agent developers [Web experience] high [HTML knowledge] high [Disability knowledge] low [Web accessibility knowledge] low [Frequency of use *]

Output: daily for a month or so, then a couple times per month


Input: [Category] Tool developers [User group] Assistive technology developers [Web experience] low-high [HTML knowledge] often low [Disability knowledge] usually high in one area [Web accessibility knowledge] low-high [Frequency of use *]

Output: daily for a month or so, then a couple times per month


Input: [Category] Tool developers [User group] Web evaluation tool developers [Web experience] high [HTML knowledge] high [Disability knowledge] low-high [Web accessibility knowledge] high [Frequency of use *]

Output: several times per week in spurts


Input: [Category] Managers and assistants [User group] IT/ICT manager, CIO (or similar management role) [Web experience] high [HTML knowledge] low - high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: several times per day in a couple spurts per year


Input: [Category] Managers and assistants [User group] assistant to IT/ICT manager or CIO [Web experience] medium-high [HTML knowledge] mostly low, some medium [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: several times per day in a couple spurts


Input: [Category] Managers and assistants [User group] product manager (most likely to "feel the heat" for accessibility) [Web experience] mostly high [HTML knowledge] low - high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: several times per day at first, then seldom


Input: [Category] Managers and assistants [User group] project manager (e.g., managing one aspect of a Web application) [Web experience] mostly high [HTML knowledge] mostly high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: several times per day at first, then seldom


Input: [Category] Managers and assistants [User group] other managers, decision makers, influencers, people who pay for accessibilty [Web experience] low - high [HTML knowledge] low - high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: several times per day at first, then seldom


Input: [Category] Related to contracts [User group] design shop sales/account manager who could/has been asked to include Web accessibility in contract [Web experience] medium-high [HTML knowledge] low-high (mostly medium) [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: several times per day in a couple spurts per year


Input: [Category] Related to contracts [User group] person setting up contract with outside Web design shop [Web experience] high [HTML knowledge] low - high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: several times per day in a couple spurts per year


Input: [Category] Disability focused [User group] person with disability [Web experience] low-high [HTML knowledge] low-high [Disability knowledge] med-high [Web accessibility knowledge] low-high [Frequency of use *]

Output: probably only a few times (since not much there for non-webbie)


Input: [Category] Disability focused [User group] disability organization members, disability rights advocate [Web experience] low - high [HTML knowledge] mostly low, some up to high [Disability knowledge] high [Web accessibility knowledge] low-high (many low) [Frequency of use *]

Output: several times per day in a couple spurts per year


Input: [Category] Disability focused [User group] rehabilitation specialist [Web experience] low - high [HTML knowledge] mostly low [Disability knowledge] high [Web accessibility knowledge] low - medium [Frequency of use *]

Output: several times per day in a couple spurts per year


Input: [Category] Disability focused [User group] disabilities specialist/liaison/coordinator, e.g., in university or corporate human resources (HR) [Web experience] low - high [HTML knowledge] mostly low [Disability knowledge] medium-high [Web accessibility knowledge] mostly low [Frequency of use *]

Output: several times per day in a couple spurts


Input: [Category] Other [User group] national or international standards developer [Web experience] low-high [HTML knowledge] low-high [Disability knowledge] low-high [Web accessibility knowledge] low-high [Frequency of use *]

Output: daily in spurts


Input: [Category] Other [User group] legislator, government policy maker (or assistant to) [Web experience] medium-high [HTML knowledge] mostly low, some high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: several times per day in a couple spurts per year


Input: [Category] Other [User group] policy maker for specific organization [Web experience] low - high [HTML knowledge] mostly low, some high [Disability knowledge] low - high [Web accessibility knowledge] low - high [Frequency of use *]

Output: several times per day in a one time spurt


Input: [Category] Other [User group] educator (including accessibility in courses) [Web experience] medium-high [HTML knowledge] low - high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: several times per day in a couple spurts per year


Input: [Category] Other [User group] reporter, journalist [Web experience] high [HTML knowledge] low-medium [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: several times per day in a spurt


Input: [Category] Other [User group] internal public relations or marketing [Web experience] mostly high [HTML knowledge] mostly low [Disability knowledge] mostly low [Web accessibility knowledge] mostly low [Frequency of use *]

Output: several times per day in a couple spurts per year


Input: [Category] Other [User group] researcher, or student doing paper on accessibility [Web experience] high [HTML knowledge] high [Disability knowledge] mostly low [Web accessibility knowledge] low [Frequency of use *]

Output: several times per day for a week


Input: [Category] Other [User group] W3C Team member (non WAI) [Web experience] high [HTML knowledge] high [Disability knowledge] mostly low [Web accessibility knowledge] mostly low-medium [Frequency of use *]

Output: daily for a week or so, then a couple times per month


Input: [Category] Other [User group] WAI WG member [Web experience] high [HTML knowledge] mostly high [Disability knowledge] medium-high [Web accessibility knowledge] medium-high [Frequency of use *]

Output: several times per day - weekly


Input: [Category] Other [User group] Web accessibility specialist (consultant, evaluator, trainer) [Web experience] usually high [HTML knowledge] medium-high [Disability knowledge] medium-high [Web accessibility knowledge] medium-high [Frequency of use *]

Output: often a couple time per week


Input: [Property] address [Description] Physical address of the item. [Expected Type]

Output: PostalAddress

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


Input: [Property] aggregateRating [Description] The overall rating, based on a collection of reviews or ratings, of the item. [Expected Type]

Output: aggregateRating

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


Input: [Property] geo [Description] The geo coordinates of the place. [Expected Type]

Output: GeoCoordinates or GeoShape

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


Input: [Property] map [Description] A URL to a map of the place. [Expected Type]

Output: URL

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


Input: [Property] photos [Description] Photographs of this place [Expected Type]

Output: ImageObject or Photograph

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


Input: [Property] reviews [Description] Review of the item [Expected Type]

Output: Review

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


Input: [Property] telephone [Description] The telephone number. [Expected Type]

Output: Text

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


Input: [Feature] 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: [Feature] 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: [Feature] 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: [Feature] 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: [Feature] Non-Repudiation [Payload Security] Supported [Transaction Layer Security]

Output: Requires additional payload security

XML Key Management Specification (XKMS 2.0) Bindings


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

Output: Requires additional payload security

XML Key Management Specification (XKMS 2.0) Bindings


Input: [Feature] 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: [Numerical Code] 200 [Example] property delivered correctly [Textual Description]

Output: OK


Input: [Numerical Code] 204 [Example] property retrieved without content [Textual Description]

Output: No Content


Input: [Numerical Code] 206 [Example] only a subset of the available data stored in the result set [Textual Description]

Output: Partial Content


Input: [Numerical Code] 400 [Example] syntactical error [Textual Description]

Output: Bad Request


Input: [Numerical Code] 404 [Example] the queries resource is not found [Textual Description]

Output: Not Found


Input: [Numerical Code] 415 [Example] get duration call on an image data store [Textual Description]

Output: Unsupported Media Type


Input: [Numerical Code] 462 [Example] location is not defined in MediaRSS [Textual Description]

Output: Property not defined in Source Format


Input: [Numerical Code] 500 [Example] internal library (e.g., extractor) crashes [Textual Description]

Output: Internal Server Error


Input: [Numerical Code] 562 [Example] a subset of properties implemented [Textual Description]

Output: Property not supported


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 2.0


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 2.0


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 2.0


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 2.0


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 2.0


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 2.0


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 2.0


Input: [LiveCycle Placement Rules] Default placement for the label is to the left of the control. If this is not possible, LiveCycle will attempt to place it immediately above the control. [Control Type]

Output: Text input (including date/time and password fields)

Text input (including date/time and password fields)

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


Input: [LiveCycle Placement Rules] Default placement for the label is to the right of the check box. [Control Type]

Output: Checkbox

Text input (including date/time and password fields)

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


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

Output: Radio button group

Text input (including date/time and password fields)

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


Input: [LiveCycle Placement Rules] Default placement for the label is to the left of the drop-down list. If this is not possible, LiveCycle will attempt to place it immediately above the control.. [Control Type]

Output: Combo box

Text input (including date/time and password fields)

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


Input: [LiveCycle Placement Rules] Default placement for the label is above the list box. [Control Type]

Output: List box

Text input (including date/time and password fields)

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


Input: [LiveCycle Placement Rules] LiveCycle automatically places the label on the button; it does not have to be positioned manually. Ensure that the button's purpose is properly described in the label text. [Control Type]

Output: Button

Text input (including date/time and password fields)

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


Input: [XKMS element.attribute name] MessageAbstractType.Service [Required]

Output: Required, but not dependent

XML Key Management Specification (XKMS 2.0) Bindings


Input: [XKMS element.attribute name] MessageAbstractType.Signature [Required]

Output: Optional, may be used to support non-repudiation for both Request and Response messages

XML Key Management Specification (XKMS 2.0) Bindings


Input: [XKMS element.attribute name] ResultType.RequestId [Required]

Output: Required, but not dependent

XML Key Management Specification (XKMS 2.0) Bindings


Input: [XKMS element.attribute name] PendingRequestType.ResponseId [Required]

Output: Required, but not dependent

XML Key Management Specification (XKMS 2.0) Bindings


Input: [XKMS element.attribute name] MessageAbstractType.Nonce [Required]

Output: Unnecessary

XML Key Management Specification (XKMS 2.0) Bindings


Input: [XKMS element.attribute name] MessageAbstractType.RespondWith=Represent [Required]

Output: Unnecessary

XML Key Management Specification (XKMS 2.0) Bindings


Input: [XKMS element.attribute name] MessageAbstractType.Service [Required]

Output: Required, but not dependent

XML Key Management Specification (XKMS 2.0) Bindings


Input: [XKMS element.attribute name] MessageAbstractType.Signature [Required]

Output: Optional, may be used to support non-repudiation for both Request and Response messages

XML Key Management Specification (XKMS 2.0) Bindings


Input: [XKMS element.attribute name] ResultType.RequestId [Required]

Output: Required, but not dependent

XML Key Management Specification (XKMS 2.0) Bindings


Input: [XKMS element.attribute name] PendingRequestType.ResponseId [Required]

Output: Required, but not dependent

XML Key Management Specification (XKMS 2.0) Bindings


Input: [XKMS element.attribute name] MessageAbstractType.Nonce [Required]

Output: Unnecessary

XML Key Management Specification (XKMS 2.0) Bindings


Input: [XKMS element.attribute name] MessageAbstractType.RespondWith=Represent [Required]

Output: Unnecessary

XML Key Management Specification (XKMS 2.0) Bindings


Input: [attribute] archive [function]

Output: For example, when defining an applet you could reference a space-separated list of jar files.


Input: [attribute] content-length [function]

Output: This is similar to meta data, in that this can be used by the object handler as a hint to the physical size of the object data that is to be processed.


Input: [attribute] data [function]

Output: This URI points to the object data to be processed. This can be an absolute URI (http://www.example.com/datafiles/myinstance.mpg), or a relative URI (myinstance.mpg). If you use a relative URI, then you will need to use the xml:base attribute to define the base location of the object data. This attribute should only refer to the data to be processed.


Input: [attribute] declare [function]

Output: This is used to delay the processing of the object data until such time that it is referred to by another element that requires the object data to be processed. In other words, the object data should be downloaded but should not be processed. For example, if an a element is coded to refer to the object element and the a element is activated, then the object data would be processed.


Input: [attribute] standby [function]

Output: The author can provide a text string that should be displayed while the object data is being downloaded and processed.


Input: [attribute] type [function]

Output: Defining the mime type of the object data will assist the object handler in determining whether the object data can be processed by the user agent or if an external application needs to be launched to process the object data.


Input: [attribute] xml:base [function]

Output: Use this attribute to define the base location of the object data. For example: http://www.example.com/datafiles/. This attribute should not be used for any other purpose.


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

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

Internationalization Tag Set (ITS) Version 2.0


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

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

Internationalization Tag Set (ITS) Version 2.0


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

Internationalization Tag Set (ITS) Version 2.0


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

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

Internationalization Tag Set (ITS) Version 2.0


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

Internationalization Tag Set (ITS) Version 2.0


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

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

Internationalization Tag Set (ITS) Version 2.0


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

Internationalization Tag Set (ITS) Version 2.0


Input: [function] For example, when defining an applet you could reference a space-separated list of jar files. [attribute]

Output: archive


Input: [function] This is similar to meta data, in that this can be used by the object handler as a hint to the physical size of the object data that is to be processed. [attribute]

Output: content-length


Input: [function] This URI points to the object data to be processed. This can be an absolute URI (http://www.example.com/datafiles/myinstance.mpg), or a relative URI (myinstance.mpg). If you use a relative URI, then you will need to use the xml:base attribute to define the base location of the object data. This attribute should only refer to the data to be processed. [attribute]

Output: data


Input: [function] This is used to delay the processing of the object data until such time that it is referred to by another element that requires the object data to be processed. In other words, the object data should be downloaded but should not be processed. For example, if an a element is coded to refer to the object element and the a element is activated, then the object data would be processed. [attribute]

Output: declare


Input: [function] The author can provide a text string that should be displayed while the object data is being downloaded and processed. [attribute]

Output: standby


Input: [function] Defining the mime type of the object data will assist the object handler in determining whether the object data can be processed by the user agent or if an external application needs to be launched to process the object data. [attribute]

Output: type


Input: [function] Use this attribute to define the base location of the object data. For example: http://www.example.com/datafiles/. This attribute should not be used for any other purpose. [attribute]

Output: xml:base


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

Output: loadstart

HTML/Elements/audio - Web Education Community Group


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

Output: progress

HTML/Elements/audio - Web Education Community Group


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

Output: suspend

HTML/Elements/audio - Web Education Community Group


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

Output: abort

HTML/Elements/audio - Web Education Community Group


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

Output: error

HTML/Elements/audio - Web Education Community Group


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

Output: emptied

HTML/Elements/audio - Web Education Community Group


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

Output: stalled

HTML/Elements/audio - Web Education Community Group


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

Output: play

HTML/Elements/audio - Web Education Community Group


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

Output: pause

HTML/Elements/audio - Web Education Community Group


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

Output: loadedmetadata

HTML/Elements/audio - Web Education Community Group


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

Output: loadeddata

HTML/Elements/audio - Web Education Community Group


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

Output: waiting

HTML/Elements/audio - Web Education Community Group


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

Output: playing

HTML/Elements/audio - Web Education Community Group


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

Output: canplay

HTML/Elements/audio - Web Education Community Group


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

Output: canplaythrough

HTML/Elements/audio - Web Education Community Group


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

Output: seeking

HTML/Elements/audio - Web Education Community Group


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

Output: seeked

HTML/Elements/audio - Web Education Community Group


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

Output: timeupdate

HTML/Elements/audio - Web Education Community Group


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

Output: ended

HTML/Elements/audio - Web Education Community Group


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

Output: ratechange

HTML/Elements/audio - Web Education Community Group


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

Output: durationchange

HTML/Elements/audio - Web Education Community Group


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

Output: volumechange

HTML/Elements/audio - Web Education Community Group


Input: [Keyword] getter [Purpose] Defines behavior for when an object is indexed for property retrieval. [Special operation]

Output: Getters


Input: [Keyword] setter [Purpose] Defines behavior for when an object is indexed for property assignment. [Special operation]

Output: Setters


Input: [Keyword] creator [Purpose] Defines behavior for when an object is indexed for property creation. [Special operation]

Output: Creators


Input: [Keyword] deleter [Purpose] Defines behavior for when an object is indexed for property deletion. [Special operation]

Output: Deleters


Input: [Keyword] legacycaller [Purpose] Defines behavior for when an object is called as if it were a function. [Special operation]

Output: Legacy callers


Input: [Keyword] stringifier [Purpose] Defines how an object is converted into a DOMString. [Special operation]

Output: Stringifiers


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


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

Output: Text field


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

Output: Search field


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

Output: A text field


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

Output: A text field


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

Output: A text field


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

Output: Text field that obscures data entry


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


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

Output: A date control


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


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


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

Output: A time control


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


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

Output: A text field or spinner control


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


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

Output: A color well


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

Output: A checkbox


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

Output: A radio button


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


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


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


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

Output: A button


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

Output: A button


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

Output: hidden


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

Output: text


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

Output: search


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

Output: tel


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

Output: url


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

Output: email


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

Output: password


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

Output: datetime


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

Output: date


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

Output: month


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

Output: week


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

Output: time


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

Output: datetime-local


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

Output: number


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

Output: range


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

Output: color


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

Output: checkbox


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

Output: radio


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

Output: file


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

Output: submit


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

Output: image


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

Output: reset


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

Output: button


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

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

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


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

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

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


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

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


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

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

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


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

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


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

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

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


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

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


Input: [Names] string-is-in [Result] True iff the first argument is equal to one of the attribute values in the bag of the second argument (according to the "string-equal" predicate). [Arguments]

Output: An attribute value of http://www.w3.org/2001/XMLSchema#string as the first argument, and a bag of attribute values of http://www.w3.org/2001/XMLSchema#string as the second argument

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Names] boolean-is-in [Result] True iff the first argument is equal to one of the attribute values in the bag of the second argument (according to the "boolean-equal" predicate). [Arguments]

Output: An attribute value of http://www.w3.org/2001/XMLSchema#boolean as the first argument, and a bag of attribute values of http://www.w3.org/2001/XMLSchema#boolean as the second argument

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Names] integer-is-in [Result] True iff the first argument is equal to one of the attribute values in the bag of the second argument (according to the "integer-equal" predicate). [Arguments]

Output: An attribute value of http://www.w3.org/2001/XMLSchema#integer as the first argument, and a bag of attribute values of http://www.w3.org/2001/XMLSchema#integer as the second argument

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Names] double-is-in [Result] True iff the first argument is equal to one of the attribute values in the bag of the second argument (according to the "double-equal" predicate). [Arguments]

Output: An attribute value of http://www.w3.org/2001/XMLSchema#double as the first argument, and a bag of attribute values of http://www.w3.org/2001/XMLSchema#double as the second argument

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Names] time-is-in [Result] True iff the first argument is equal to one of the attribute values in the bag of the second argument (according to the "time-equal" predicate). [Arguments]

Output: An attribute value of http://www.w3.org/2001/XMLSchema#time as the first argument, and a bag of attribute values of http://www.w3.org/2001/XMLSchema#time as the second argument

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Names] date-is-in [Result] True iff the first argument is equal to one of the attribute values in the bag of the second argument (according to the "date-equal" predicate). [Arguments]

Output: An attribute value of http://www.w3.org/2001/XMLSchema#date as the first argument, and a bag of attribute values of http://www.w3.org/2001/XMLSchema#date as the second argument

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Names] dateTime-is-in [Result] True iff the first argument is equal to one of the attribute values in the bag of the second argument (according to the "dateTime-equal" predicate). [Arguments]

Output: An attribute value of http://www.w3.org/2001/XMLSchema#dateTime as the first argument, and a bag of attribute values of http://www.w3.org/2001/XMLSchema#dateTime as the second argument

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Names] string-at-least-one-value-equal [Result] True iff at least one attribute value in the bag of the first argument is equal to one of the attribute values in the bag of the second argument (according to the "string-equal" predicate). [Arguments]

Output: Two bags of attribute values of http://www.w3.org/2001/XMLSchema#string

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Names] boolean-at-least-one-value-equal [Result] True iff at least one attribute value in the bag of the first argument is equal to one of the attribute values in the bag of the second argument (according to the "boolean-equal" predicate). [Arguments]

Output: Two bags of attribute values of http://www.w3.org/2001/XMLSchema#boolean

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Names] integer-at-least-one-value-equal [Result] True iff at least one attribute value in the bag of the first argument is equal to one of the attribute values in the bag of the second argument (according to the "integer-equal" predicate). [Arguments]

Output: Two bags of attribute values of http://www.w3.org/2001/XMLSchema#integer

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Names] double-at-least-one-value-equal [Result] True iff at least one attribute value in the bag of the first argument is equal to one of the attribute values in the bag of the second argument (according to the "double-equal" predicate). [Arguments]

Output: Two bags of attribute values of http://www.w3.org/2001/XMLSchema#double

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Names] time-at-least-one-value-equal [Result] True iff at least one attribute value in the bag of the first argument is equal to one of the attribute values in the bag of the second argument (according to the "time-equal" predicate). [Arguments]

Output: Two bags of attribute values of http://www.w3.org/2001/XMLSchema#time

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Names] date-at-least-one-value-equal [Result] True iff at least one attribute value in the bag of the first argument is equal to one of the attribute values in the bag of the second argument (according to the "date-equal" predicate). [Arguments]

Output: Two bags of attribute values of http://www.w3.org/2001/XMLSchema#date

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Names] dateTime-at-least-one-value-equal [Result] True iff at least one attribute value in the bag of the first argument is equal to one of the attribute values in the bag of the second argument (according to the "dateTime-equal" predicate). [Arguments]

Output: Two bags of attribute values of http://www.w3.org/2001/XMLSchema#dateTime

Enterprise Privacy Authorization Language (EPAL 1.2)


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

Output: possible

XML Encryption Workshop - Geuer-Pollmann


Input: [Model] Secure only attribute values [Server-Side Access Control] possible [Pool encryption] possible [Subtree encryption]

Output: possible (depends on proposal)

XML Encryption Workshop - Geuer-Pollmann


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

Output: no

XML Encryption Workshop - Geuer-Pollmann


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

Output: no

XML Encryption Workshop - Geuer-Pollmann


Input: [Model] Automation of access/encryption decisions [Server-Side Access Control] yes [Pool encryption] needs some sort of style sheet [Subtree 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 [Pool encryption] no [Subtree 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 [Pool encryption] yes [Subtree encryption]

Output: depends on situation

XML Encryption Workshop - Geuer-Pollmann


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

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

HTML/Elements/audio - Web Education Community Group


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

Output: The user agent is fetching media data.

HTML/Elements/audio - Web Education Community Group


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

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

HTML/Elements/audio - Web Education Community Group


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

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

HTML/Elements/audio - Web Education Community Group


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

Output: An error occurs while fetching the media data.

HTML/Elements/audio - Web Education Community Group


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

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

HTML/Elements/audio - Web Education Community Group


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

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

HTML/Elements/audio - Web Education Community Group


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

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

HTML/Elements/audio - Web Education Community Group


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

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

HTML/Elements/audio - Web Education Community Group


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

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

HTML/Elements/audio - Web Education Community Group


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

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

HTML/Elements/audio - Web Education Community Group


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

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

HTML/Elements/audio - Web Education Community Group


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

Output: Playback has started.

HTML/Elements/audio - Web Education Community Group


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

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

HTML/Elements/audio - Web Education Community Group


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

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

HTML/Elements/audio - Web Education Community Group


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

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

HTML/Elements/audio - Web Education Community Group


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

Output: The seeking IDL attribute changed to false.

HTML/Elements/audio - Web Education Community Group


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

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

HTML/Elements/audio - Web Education Community Group


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

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

HTML/Elements/audio - Web Education Community Group


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

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

HTML/Elements/audio - Web Education Community Group


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

Output: The duration attribute has just been updated.

HTML/Elements/audio - Web Education Community Group


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

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

HTML/Elements/audio - Web Education Community Group


Input: [Property] hanging-punctuation [Initial] none [Applies to] inline elements [Inh.] yes [Percentages] N/A [Media] visual [Values]

Output: none | [ first || [ force-end | allow-end ] || last ]


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

Output: none | manual | auto


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

Output: normal |


Input: [Property] line-break [Initial] auto [Applies to] all elements [Inh.] yes [Percentages] N/A [Media] visual [Values]

Output: auto | loose | normal | strict


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

Output: normal | break-word


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


Input: [Property] text-align [Initial] start [Applies to] block containers [Inh.] yes [Percentages] N/A [Media] visual [Values]

Output: start | end | left | right | center | justify | match-parent | start end


Input: [Property] text-align-last [Initial] auto [Applies to] block containers [Inh.] yes [Percentages] N/A [Media] visual [Values]

Output: auto | start | end | left | right | center | justify


Input: [Property] text-indent [Initial] 0 [Applies to] block containers [Inh.] yes [Percentages] refers to width of containing block [Media] visual [Values]

Output: [ | ] && hanging? && each-line?


Input: [Property] text-justify [Initial] auto [Applies to] block containers and, optionally, inline elements [Inh.] yes [Percentages] N/A [Media] visual [Values]

Output: auto | none | inter-word | distribute


Input: [Property] text-transform [Initial] none [Applies to] all elements [Inh.] yes [Percentages] N/A [Media] visual [Values]

Output: none | capitalize | uppercase | lowercase | full-width


Input: [Property] white-space [Initial] normal [Applies to] all elements [Inh.] yes [Percentages] N/A [Media] visual [Values]

Output: normal | pre | nowrap | pre-wrap | pre-line


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

Output: normal | keep-all | break-all


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

Output: [ normal | | ]


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

Output: normal | break-word


Input: [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. [Rationale] 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. [Test tool] The W3C HTML Validator is one of the many options available. The LogValidator is especially helpful in maintaining a valid Web site. [Requirement]

Output: Use valid (X)HTML

Buy standards compliant Web sites — W3C QA


Input: [Details] Avoid any presentational markup and keep all the layout features in well-defined CSS style sheets. [Rationale] 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. [Test tool] The CSS Validator detects any non-compliant use of the CSS technologies. [Requirement]

Output: Use extensively valid CSS

Buy standards compliant Web sites — W3C QA


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

Output: Use HTTP properly

Buy standards compliant Web sites — W3C QA


Input: [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] N/A [Requirement]

Output: Use SVG and PNG for graphics

Buy standards compliant Web sites — W3C QA


Input: [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] See Evaluation Tools for Web Content Accessibility. [Requirement]

Output: Use techniques to make your content accessible

Buy standards compliant Web sites — W3C QA


Input: [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] N/A [Requirement]

Output: Use standards scripting languages

Buy standards compliant Web sites — W3C QA


Input: [Property] break-after [Values] auto | always | avoid | left | right | page | column | region | avoid-page | avoid-column | avoid-region [Applies to] block-level elements [Inh.] no [Percentages] N/A [Media] visual [Initial]

Output: auto


Input: [Property] break-before [Values] auto | always | avoid | left | right | page | column | region | avoid-page | avoid-column | avoid-region [Applies to] block-level elements [Inh.] no [Percentages] N/A [Media] visual [Initial]

Output: auto


Input: [Property] break-inside [Values] auto | avoid | avoid-page | avoid-column | avoid-region [Applies to] block-level elements [Inh.] no [Percentages] N/A [Media] visual [Initial]

Output: auto


Input: [Property] flow-from [Values] | none | inherit [Applies to] Non-replaced block containers. This might be expanded in future versions of the specification to allow other types of containers to receive flow content. [Inh.] no [Percentages] N/A [Media] visual [Initial]


Input: [Property] flow-into [Values] none | [element|content]? [Applies to] All elements, but not pseudo-elements such as ::first-line, ::first-letter, ::before or ::after. [Inh.] no [Percentages] N/A [Media] visual [Initial]


Input: [Property] region-fragment [Values] auto | break [Applies to] CSS Regions [Inh.] no [Percentages] N/A [Media] visual [Initial]

Output: auto


Input: [Special operation] Getters [Keyword] getter [Purpose]

Output: Defines behavior for when an object is indexed for property retrieval.


Input: [Special operation] Setters [Keyword] setter [Purpose]

Output: Defines behavior for when an object is indexed for property assignment.


Input: [Special operation] Creators [Keyword] creator [Purpose]

Output: Defines behavior for when an object is indexed for property creation.


Input: [Special operation] Deleters [Keyword] deleter [Purpose]

Output: Defines behavior for when an object is indexed for property deletion.


Input: [Special operation] Legacy callers [Keyword] legacycaller [Purpose]

Output: Defines behavior for when an object is called as if it were a function.


Input: [Special operation] Stringifiers [Keyword] stringifier [Purpose]

Output: Defines how an object is converted into a DOMString.


Input: [Property] break-after [Initial] auto [Applies to] block-level elements [Inh.] no [Percentages] N/A [Media] visual [Values]

Output: auto | always | avoid | left | right | page | column | region | avoid-page | avoid-column | avoid-region


Input: [Property] break-before [Initial] auto [Applies to] block-level elements [Inh.] no [Percentages] N/A [Media] visual [Values]

Output: auto | always | avoid | left | right | page | column | region | avoid-page | avoid-column | avoid-region


Input: [Property] break-inside [Initial] auto [Applies to] block-level elements [Inh.] no [Percentages] N/A [Media] visual [Values]

Output: auto | avoid | avoid-page | avoid-column | avoid-region


Input: [Property] flow-from [Initial] none [Applies to] Non-replaced block containers. This might be expanded in future versions of the specification to allow other types of containers to receive flow content. [Inh.] no [Percentages] N/A [Media] visual [Values]

Output: | none | inherit


Input: [Property] flow-into [Initial] none [Applies to] All elements, but not pseudo-elements such as ::first-line, ::first-letter, ::before or ::after. [Inh.] no [Percentages] N/A [Media] visual [Values]

Output: none | [element|content]?


Input: [Property] region-fragment [Initial] auto [Applies to] CSS Regions [Inh.] no [Percentages] N/A [Media] visual [Values]

Output: auto | break


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

Output: Event

Document Object Model (DOM) Level 3 Events Specification


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

Output: FocusEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: MouseEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: CompositionEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: CompositionEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: CompositionEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: MouseEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: UIEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: MutationNameEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: MutationEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: MutationEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: MutationNameEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: FocusEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: FocusEvent

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 [Cancelable] No [Default Action] none [DOM interface]

Output: MutationEvent

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 [Cancelable] No [Default Action] none [DOM interface]

Output: MutationEvent

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 [Cancelable] No [Default Action] none [DOM interface]

Output: MutationEvent

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 [Cancelable] No [Default Action] none [DOM interface]

Output: MutationEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: MutationEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: Event

Document Object Model (DOM) Level 3 Events Specification


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

Output: FocusEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: FocusEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: FocusEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: KeyboardEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: KeyboardEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: KeyboardEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: Event

Document Object Model (DOM) Level 3 Events Specification


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

Output: MouseEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: MouseEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: MouseEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: MouseEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: MouseEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: MouseEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: MouseEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: UIEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: UIEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: Event

Document Object Model (DOM) Level 3 Events Specification


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

Output: TextEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: Event

Document Object Model (DOM) Level 3 Events Specification


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

Output: WheelEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Name] string-bag-size [Arguments] A single bag of attribute values of http://www.w3.org/2001/XMLSchema#string [Return Value]

Output: An attribute value of http://www.w3.org/2001/XMLSchema#integer representing the size of the bag.

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Name] boolean-bag-size [Arguments] A single bag of attribute values of http://www.w3.org/2001/XMLSchema#boolean [Return Value]

Output: An attribute value of http://www.w3.org/2001/XMLSchema#integer representing the size of the bag.

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Name] integer-bag-size [Arguments] A single bag of attribute values of http://www.w3.org/2001/XMLSchema#integer [Return Value]

Output: An attribute value of http://www.w3.org/2001/XMLSchema#integer representing the size of the bag.

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Name] double-bag-size [Arguments] A single bag of attribute values of http://www.w3.org/2001/XMLSchema#double [Return Value]

Output: An attribute value of http://www.w3.org/2001/XMLSchema#integer representing the size of the bag.

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Name] time-bag-size [Arguments] A single bag of attribute values of http://www.w3.org/2001/XMLSchema#time [Return Value]

Output: An attribute value of http://www.w3.org/2001/XMLSchema#integer representing the size of the bag.

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Name] date-bag-size [Arguments] A single bag of attribute values of http://www.w3.org/2001/XMLSchema#date [Return Value]

Output: An attribute value of http://www.w3.org/2001/XMLSchema#integer representing the size of the bag.

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Name] dateTime-bag-size [Arguments] A single bag of attribute values of http://www.w3.org/2001/XMLSchema#dateTime [Return Value]

Output: An attribute value of http://www.w3.org/2001/XMLSchema#integer representing the size of the bag.

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Name] string-bag-to-value [Arguments] A single bag of attribute values of http://www.w3.org/2001/XMLSchema#string [Return Value]

Output: This function checks whether the bag contains one and only one attribute value. If it is true, then an attribute value of http://www.w3.org/2001/XMLSchema#string representing the only one value is returned, otherwise an error is returned.

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Name] boolean-bag-to-value [Arguments] A single bag of attribute values of http://www.w3.org/2001/XMLSchema#boolean [Return Value]

Output: This function checks whether the bag contains one and only one attribute value. If it is true, then an attribute value of http://www.w3.org/2001/XMLSchema#boolean representing the only one value is returned, otherwise an error is returned.

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Name] integer-bag-to-value [Arguments] A single bag of attribute values of http://www.w3.org/2001/XMLSchema#integer [Return Value]

Output: This function checks whether the bag contains one and only one attribute value. If it is true, then an attribute value of http://www.w3.org/2001/XMLSchema#integer representing the only one value is returned, otherwise an error is returned.

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Name] double-bag-to-value [Arguments] A single bag of attribute values of http://www.w3.org/2001/XMLSchema#double [Return Value]

Output: This function checks whether the bag contains one and only one attribute value. If it is true, then an attribute value of http://www.w3.org/2001/XMLSchema#double representing the only one value is returned, otherwise an error is returned.

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Name] time-bag-to-value [Arguments] A single bag of attribute values of http://www.w3.org/2001/XMLSchema#time [Return Value]

Output: This function checks whether the bag contains one and only one attribute value. If it is true, then an attribute value of http://www.w3.org/2001/XMLSchema#time representing the only one value is returned, otherwise an error is returned.

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Name] date-bag-to-value [Arguments] A single bag of attribute values of http://www.w3.org/2001/XMLSchema#date [Return Value]

Output: This function checks whether the bag contains one and only one attribute value. If it is true, then an attribute value of http://www.w3.org/2001/XMLSchema#date representing the only one value is returned, otherwise an error is returned.

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Name] dateTime-bag-to-value [Arguments] A single bag of attribute values of http://www.w3.org/2001/XMLSchema#dateTime [Return Value]

Output: This function checks whether the bag contains one and only one attribute value. If it is true, then an attribute value of http://www.w3.org/2001/XMLSchema#dateTime representing the only one value is returned, otherwise an error is returned.

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Name] string-bag [Arguments] Zero or more attribute values of http://www.w3.org/2001/XMLSchema#string [Return Value]

Output: A bag of http://www.w3.org/2001/XMLSchema#string containing all the argument values.

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Name] boolean-bag [Arguments] Zero or more attribute values of http://www.w3.org/2001/XMLSchema#boolean [Return Value]

Output: A bag of http://www.w3.org/2001/XMLSchema#boolean containing all the argument values.

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Name] integer-bag [Arguments] Zero or more attribute values of http://www.w3.org/2001/XMLSchema#integer [Return Value]

Output: A bag of http://www.w3.org/2001/XMLSchema#integer containing all the argument values.

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Name] double-bag [Arguments] Zero or more attribute values of http://www.w3.org/2001/XMLSchema#double [Return Value]

Output: A bag of http://www.w3.org/2001/XMLSchema#double containing all the argument values.

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Name] time-bag [Arguments] Zero or more attribute values of http://www.w3.org/2001/XMLSchema#time [Return Value]

Output: A bag of http://www.w3.org/2001/XMLSchema#time containing all the argument values.

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Name] date-bag [Arguments] Zero or more attribute values of http://www.w3.org/2001/XMLSchema#date [Return Value]

Output: A bag of http://www.w3.org/2001/XMLSchema#date containing all the argument values.

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Name] dateTime-bag [Arguments] Zero or more attribute values of http://www.w3.org/2001/XMLSchema#dateTime [Return Value]

Output: A bag of http://www.w3.org/2001/XMLSchema#dateTime containing all the argument values.

Enterprise Privacy Authorization Language (EPAL 1.2)


Input: [Requirement] Use valid (X)HTML [Rationale] 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. [Test tool] The W3C HTML Validator is one of the many options available. The LogValidator is especially helpful in maintaining a valid Web site. [Details]

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

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use extensively valid CSS [Rationale] 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. [Test tool] The CSS Validator detects any non-compliant use of the CSS technologies. [Details]

Output: Avoid any presentational markup and keep all the layout features in well-defined CSS style sheets.

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use HTTP properly [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] 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. [Details]

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

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use SVG and PNG for graphics [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] N/A [Details]

Output: Use PNG for raster images, and SVG for all others.

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use techniques to make your content accessible [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] See Evaluation Tools for Web Content Accessibility. [Details]

Output: Details.

Buy standards compliant Web sites — W3C QA


Input: [Requirement] Use standards scripting languages [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] N/A [Details]

Output: Use the DOM API combined with Ecmascript (but don't make the use of scripts mandatory to navigate in the site!).

Buy standards compliant Web sites — W3C QA


Input: [Special operation] Getters [Purpose] Defines behavior for when an object is indexed for property retrieval. [Keyword]

Output: getter


Input: [Special operation] Setters [Purpose] Defines behavior for when an object is indexed for property assignment. [Keyword]

Output: setter


Input: [Special operation] Creators [Purpose] Defines behavior for when an object is indexed for property creation. [Keyword]

Output: creator


Input: [Special operation] Deleters [Purpose] Defines behavior for when an object is indexed for property deletion. [Keyword]

Output: deleter


Input: [Special operation] Legacy callers [Purpose] Defines behavior for when an object is called as if it were a function. [Keyword]

Output: legacycaller


Input: [Special operation] Stringifiers [Purpose] Defines how an object is converted into a DOMString. [Keyword]

Output: stringifier


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. [Rationale] 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. [Test tool]

Output: The W3C HTML Validator is one of the many options available. The LogValidator is especially helpful in maintaining a valid Web site.

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. [Rationale] 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. [Test tool]

Output: The CSS Validator detects any non-compliant use of the CSS technologies.

Buy standards compliant Web sites — W3C QA