Input: [Name] conferenceid [Required] false [Attribute Constraints] Must not be used with connectionid [Type] ECMAScript Expression [Default Value] none [Description] An Optional ECMAScript expression which returns the identifier of a conference bridge. If specified, the dialog being prepared MUST be joined to the referenced conference as specified by the mediadirection attribute. If the attribute value is invalid an error.semantic event must be thrown. [Valid Values]

Output: Conference IDs

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] mediadirection [Required] false [Type] ECMAScript Expression [Default Value] both [Description] An ECMAScript expression that defines the direction of the media flow between the Dialog and the Connection or Conference. The following values must be used: both Specifies a full duplex connection where the media flows in both directions. dialogtransmit The dialog transmits media to the Connection or Conference but does not receive any media streams. dialogreceive The dialog receives media from the Connection or Conference but does not transmit any media streams. The bridge does not take place until a subsequent is executed, but this attribute may be provided as guidance to the dialog environment for preparation. If no value is specified, the dialog environment must make no assumptions as to the bridging type. For more information about connections and bridges, refer to Section 10 . [Valid Values]

Output: both dialogtransmit dialogreceive

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] maxage [Required] false [Type] ECMAScript Expression [Default Value] none [Description] The character string returned must be interpreted as a time interval. This indicates that the document is willing to use content whose age is no greater than the specified time in seconds (cf. 'max-age' in HTTP 1.1 [RFC2616]). The document is not willing to use stale content, unless maxstale is also provided. [Valid Values]

Output: A valid time value for the HTTP 1.1 request [RFC2616]

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] maxstale [Required] false [Type] ECMAScript Expression [Default Value] none [Description] The character string returned must be interpreted as a time interval. This indicates that the document is willing to use content that has exceeded its expiration time (cf. 'max-stale' in HTTP 1.1 [RFC2616]). If maxstale is assigned a value, then the document is willing to accept content that has exceeded its expiration time by no more than the specified number of seconds. [Valid Values]

Output: A valid time value for the HTTP 1.1 request [RFC2616]

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] enctype [Required] false [Attribute Constraints] Valid only when the value of the method is "post", otherwise ignored. [Type] ECMAScript Expression [Default Value] application/x-www-form-urlencoded [Description] An ECMAScript expression which returns a character string that indicates the media encoding type of the submitted document (when the value of the method is "post"). Values defined by the specification are: application/x-www-form-urlencoded This indicates that the ccxml variables specified in the namelist must be url encoded. [Valid Values]

Output: valid media encoding type

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] method [Required] false [Type] ECMAScript Expression [Default Value] get [Description] An ECMAScript expression which returns a character string that indicates the HTTP method to use. Values defined by the specification are: get This indicates that the "GET" method must be used by the dialog manager. post This indicates that the "POST" method must be used by the dialog manager. [Valid Values]

Output: get post

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] hints [Required] false [Type] ECMAScript Expression [Default Value] none [Description] The ECMAScript object returned contains information which may be used by the implementing platform for implementing the dialog operation. Note: The meaning of these hints is specific to the implementing platform and protocol. Platforms that do not support hints MAY ignore this attribute. See Section 9.5.6 for additional requirements when hints are supported by the implementing platform. [Valid Values]

Output: An ECMAScript expression that returns an ECMAScript object

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] true [Type] ECMAScript Expression [Default Value] none [Valid Values] must evaluate to a valid URI [Description] An ECMAScript expression which returns the URI of the resource to be fetched. [Name]

Output: next

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Expression [Default Value] In processed mode "application/ccxml+xml". In raw mode "*/*". [Valid Values] MIME Types formatted as per HTTP Accept header [RFC2616] [Description] An ECMAScript expression which returns a character string setting the value of the HTTP Accept header to tell the application server what content type the application wishes to have returned. [Name]

Output: type

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] Var List [Default Value] none [Valid Values] List of ECMAScript Variable names [Description] A list of zero or more whitespace separated CCXML variable names. These variables must be submitted to the web server, with the same qualification as used in the namelist. When an ECMAScript variable is submitted to the web server, its value must be first converted into a string before being submitted. If the variable is an ECMAScript Object, the mechanism by which it must be submitted is not currently defined. Instead of submitting ECMAScript Objects directly, the application developer may explicitly submit the properties of an Object. e.g. "date.month date.year". [Name]

Output: namelist

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Expression [Default Value] get [Valid Values] get post [Description] An ECMAScript expression which returns a character string that indicates the HTTP method to use. Values defined by the specification are: get This indicates that the "GET" method must be used to fetch the URI post This indicates that the "POST" method must be used while submitting the URI to the web server. [Name]

Output: method

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Left Hand Side Expression [Default Value] none [Valid Values] ECMAScript Variable [Description] An ECMAScript left hand side expression evaluating to a previously defined variable. The value of the attribute must receive an internally generated unique string identifier to be associated with the completion event. This identifier can be tested by the fetch completion event handler to distinguish among several outstanding fetch requests. If this attribute is not specified, the fetch identifier can be acquired from the fetch completion event. Every fetch request must receive a unique fetch identifier, even if the request is for the same URI [Name]

Output: fetchid

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression which returns a character string in CSS2 [CSS2] format [Description] The character string returned must be interpreted as a time interval. This interval begins when the fetch is executed. The fetch must fail if not completed at the end of this interval. A failed fetch must return the error.fetch event. [Name]

Output: timeout

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression which returns a valid time value for the HTTP 1.1 request [RFC2616] [Description] The character string returned must be interpreted as a time interval. This indicates that the document is willing to use content whose age must be no greater than the specified time in seconds (cf. 'max-age' in HTTP 1.1 [RFC2616]). The document is not willing to use stale content, unless maxstale is also provided. [Name]

Output: maxage

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression which returns a valid time value for the HTTP 1.1 request [RFC2616] [Description] The character string returned must be interpreted as a time interval. This indicates that the document is willing to use content that has exceeded its expiration time (cf. 'max-age' in HTTP 1.1 [RFC2616]). If maxstale is assigned a value, then the document is willing to accept content that has exceeded its expiration time by no more than the specified number of seconds. [Name]

Output: maxstale

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Attribute Constraints] Valid only when the value of the method is "post", otherwise ignored. [Type] ECMAScript Expression [Default Value] application/x-www-form-urlencoded [Valid Values] valid media encoding type [Description] An ECMAScript expression which returns a character string that indicates the media encoding type of the submitted document (when the value of the method is "post"). Values defined by the specification are: application/x-www-form-urlencoded This indicates that the ccxml variables specified in the namelist must be url encoded. [Name]

Output: enctype

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] false [Type] ECMAScript Expression [Default Value] processed [Valid Values] processed, raw [Description] Controls what the CCXML platform should do with fetched content. If set to processed (the default) the CCXML platform MUST attempt to parse and validate the returned content. If set to raw the platform MUST NOT attempt to process the data and MUST leave processing of the content to the application who can do what it wishes with the content via the content attribute of the fetch.done event [Name]

Output: mode

Voice Browser Call Control: CCXML Version 1.0


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: [Data category] Domain [Local Usage] No [Global, rule-based selection] Yes [Global adding of information] Yes 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] Locale Filter [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] localeFilterType="all" [Inheritance] Textual content of element, including attributes and child elements [Overriding]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] External Resource [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: [Responder] Anne van Kesteren [Comments] I don't think it's good to decide upfront how the various pieces are to be split among documents. It seems better to do more research first into what actually needs to be defined here. [Distinct deliverables]

Output: no

Results of Questionnaire Request for Input on organizing accessibility API binding work in PFWG and HTML WG - Web-Based Straw-poll and Balloting System


Input: [Responder] Ben Millard [Comments] This looks compatible with the way ARIA integration was envisaged at the Breakout session in France 2008. (Mutually agreed "hooks" which are used in the HTML5 spec, which ARIA then specifies in detail.) [Distinct deliverables]

Output: yes

Results of Questionnaire Request for Input on organizing accessibility API binding work in PFWG and HTML WG - Web-Based Straw-poll and Balloting System


Input: [Responder] Shawn Medero [Comments] There's not enough detail here for me to make an informed decision. I'd like to see a discussion thread on this topic brew for a while and see if there is any consensus on what the above deliverables means. [Distinct deliverables]

Output: no

Results of Questionnaire Request for Input on organizing accessibility API binding work in PFWG and HTML WG - Web-Based Straw-poll and Balloting System


Input: [Responder] Aaron Leventhal [Comments] I think this group should be responsible for 1 & 2. If we add all the tests it becomes a bit large I think. But, I can probably be convinced if I learn what kind of work 3 & 4 will entail. [Distinct deliverables]

Output: no

Results of Questionnaire Request for Input on organizing accessibility API binding work in PFWG and HTML WG - Web-Based Straw-poll and Balloting System


Input: [Responder] Frederick Boland [Distinct deliverables]

Output: no

Results of Questionnaire Request for Input on organizing accessibility API binding work in PFWG and HTML WG - Web-Based Straw-poll and Balloting System


Input: [Responder] Gregory Rosmaita [Distinct deliverables]

Output: yes

Results of Questionnaire Request for Input on organizing accessibility API binding work in PFWG and HTML WG - Web-Based Straw-poll and Balloting System


Input: [Responder] Maciej Stachowiak [Comments] As other commentors have mentioned, it's not clear if we can decide up-front if this is the best split. I think there may be interactions between HTML5 requirements and ARIA requirements that make this not the best split. [Distinct deliverables]

Output: no

Results of Questionnaire Request for Input on organizing accessibility API binding work in PFWG and HTML WG - Web-Based Straw-poll and Balloting System


Input: [Responder] Tony Ross [Comments] Specifically having the test suites in addition to the specs will help ensure interoperability. Each test suite should be done by the same group that writes the corresponding spec for consistency. [Distinct deliverables]

Output: yes

Results of Questionnaire Request for Input on organizing accessibility API binding work in PFWG and HTML WG - Web-Based Straw-poll and Balloting System


Input: [Responder] Anna Zhuang [Distinct deliverables]

Output: yes

Results of Questionnaire Request for Input on organizing accessibility API binding work in PFWG and HTML WG - Web-Based Straw-poll and Balloting System


Input: [Name] target [Required] true [Type] ECMAScript Expression [Default Value] none [Description] An ECMAScript expression returning the target location of the event. The target attribute specifies the unique identifier of the event target that the Event I/O Processor must send the event to. [Valid Values]

Output: A valid target URI

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] targettype [Required] false [Type] ECMAScript Expression [Default Value] ccxml [Description] An ECMAScript expression which returns a character string that specifies the type of the Event I/O Processor that the event must be dispatched to. [Valid Values]

Output: ccxml dialog basichttp

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] sendid [Required] false [Type] ECMAScript Left Hand Side Expression [Default Value] none [Description] An ECMAScript left hand side expression evaluating to a previously defined variable. The value of the attribute must receive an internally generated unique string identifier to be associated with the event being sent. [Valid Values]

Output: ECMAScript Variable

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] delay [Required] false [Type] ECMAScript Expression [Default Value] '0s' [Description] The character string returned must be interpreted as a time interval. The send element must return immediately, but the event must not be dispatched until the delay interval elapses. Timers are useful for a wide variety of programming tasks, and can be implemented using this attribute. Note: The delayed event queue for sending events must be maintained locally. Any events waiting to be sent must be purged when the session that issued this request terminates. [Valid Values]

Output: An ECMAScript expression which returns a character string in CSS2 [CSS2] format

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] namelist [Required] false [Attribute Constraints] This attribute must not be specified in conjunction with inline content [Type] Var List [Default Value] none [Description] A list of zero or more whitespace separated CCXML variable names to be included with the event. Values for these variables are evaluated when the element is processed See section 9.2.3.1 for details on how these variables are made available to the target. [Valid Values]

Output: List of ECMAScript Variable names

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] hints [Required] false [Type] ECMAScript Expression [Default Value] none [Description] The ECMAScript object returned contains information which may be used by the implementing platform to configure the Event I/O Processor. The meaning of these hints is specific to the implementing platform and the Event I/O Processor. Note: The meaning of these hints is specific to the implementing platform and protocol. Platforms that do not support hints MAY ignore this attribute. See Section 9.5.6 for additional requirements when hints are supported by the implementing platform. [Valid Values]

Output: An ECMAScript expression that returns an ECMAScript object

Voice Browser Call Control: CCXML Version 1.0


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


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

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

Buy standards compliant Web sites — W3C QA


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

Buy standards compliant Web sites — W3C QA


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

Output: See Evaluation Tools for Web Content Accessibility.

Buy standards compliant Web sites — W3C QA


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

Buy standards compliant Web sites — W3C QA


Input: [Name] src [Required] true [Type] ECMAScript Expression [Default Value] none [Valid Values] a Dialog URI [Description]

Output: An ECMAScript expression which returns a character string identifying the URI of the dialog document that the dialog interpreter must prepare.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] type [Required] false [Type] ECMAScript Expression [Default Value] application/voicexml+xml [Valid Values] a Valid MIME Type [Description]

Output: An ECMAScript expression which returns a character string that specifies the MIME type of the document, and as a result determines which dialog manager environment must actually be used. Values defined by the specification are: application/voicexml+xml This MIME type would request a VoiceXML interpreter instance. audio/x-wav This MIME type would request a dialog manager that merely plays wave files.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] namelist [Required] false [Type] Var List [Default Value] none [Valid Values] List of ECMAScript Variable names [Description]

Output: A list of zero or more whitespace separated CCXML variable names. These variables must be submitted to the web server, with the same qualification as used in the namelist. When an ECMAScript variable is submitted to the web server, its value must be first converted into a string before being submitted. If the variable is an ECMAScript Object, the mechanism by which it is submitted is not currently defined. Instead of submitting ECMAScript Objects directly, the application developer may explicitly submit the properties of an Object. e.g. "date.month date.year".

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] parameters [Required] false [Type] Var List [Default Value] none [Valid Values] List of ECMAScript Variable names [Description]

Output: A list of one or more whitespace separated CCXML variable names. These variables are sent to the dialog environment as a list of name/value pairs. Names are sent exactly as they are specified; values are formed by converting the referenced ECMAScript variable to string form (which is undefined for objects). The dialog environment determines how passed parameters will be handled

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] dialogid [Required] false [Type] ECMAScript Left Hand Side Expression [Default Value] none [Valid Values] ECMAScript Variable [Description]

Output: An ECMAScript left hand side expression evaluating to a previously defined variable. The value of the attribute must receive a dialog identifier value for the launched dialog interpreter instance. If the attribute value is invalid, an error.semantic event MUST be thrown

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] connectionid [Required] false [Attribute Constraints] Must not be used with conferenceid [Type] ECMAScript Expression [Default Value] none [Valid Values] Connection IDs [Description]

Output: An Optional ECMAScript expression which returns the identifier of a connection. If specified, the dialog being prepared MUST be joined to the referenced connection as specified by the mediadirection attribute. Note that if the referenced connection is already bridged to another media endpoint, those existing bridges may be affected according to the rules specified in section 10.4 even prior to being performed If the attribute value is invalid an error.semantic event must be thrown.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] conferenceid [Required] false [Attribute Constraints] Must not be used with connectionid [Type] ECMAScript Expression [Default Value] none [Valid Values] Conference IDs [Description]

Output: An Optional ECMAScript expression which returns the identifier of a conference bridge. If specified, the dialog being prepared MUST be joined to the referenced conference as specified by the mediadirection attribute. If the attribute value is invalid an error.semantic event must be thrown.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] mediadirection [Required] false [Type] ECMAScript Expression [Default Value] both [Valid Values] both dialogtransmit dialogreceive [Description]

Output: An ECMAScript expression that defines the direction of the media flow between the Dialog and the Connection or Conference. The following values must be used: both Specifies a full duplex connection where the media flows in both directions. dialogtransmit The dialog transmits media to the Connection or Conference but does not receive any media streams. dialogreceive The dialog receives media from the Connection or Conference but does not transmit any media streams. The bridge does not take place until a subsequent is executed, but this attribute may be provided as guidance to the dialog environment for preparation. If no value is specified, the dialog environment must make no assumptions as to the bridging type. For more information about connections and bridges, refer to Section 10 .

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] maxage [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] A valid time value for the HTTP 1.1 request [RFC2616] [Description]

Output: The character string returned must be interpreted as a time interval. This indicates that the document is willing to use content whose age is no greater than the specified time in seconds (cf. 'max-age' in HTTP 1.1 [RFC2616]). The document is not willing to use stale content, unless maxstale is also provided.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] maxstale [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] A valid time value for the HTTP 1.1 request [RFC2616] [Description]

Output: The character string returned must be interpreted as a time interval. This indicates that the document is willing to use content that has exceeded its expiration time (cf. 'max-stale' in HTTP 1.1 [RFC2616]). If maxstale is assigned a value, then the document is willing to accept content that has exceeded its expiration time by no more than the specified number of seconds.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] enctype [Required] false [Attribute Constraints] Valid only when the value of the method is "post", otherwise ignored. [Type] ECMAScript Expression [Default Value] application/x-www-form-urlencoded [Valid Values] valid media encoding type [Description]

Output: An ECMAScript expression which returns a character string that indicates the media encoding type of the submitted document (when the value of the method is "post"). Values defined by the specification are: application/x-www-form-urlencoded This indicates that the ccxml variables specified in the namelist must be url encoded.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] method [Required] false [Type] ECMAScript Expression [Default Value] get [Valid Values] get post [Description]

Output: An ECMAScript expression which returns a character string that indicates the HTTP method to use. Values defined by the specification are: get This indicates that the "GET" method must be used by the dialog manager. post This indicates that the "POST" method must be used by the dialog manager.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] hints [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression that returns an ECMAScript object [Description]

Output: The ECMAScript object returned contains information which may be used by the implementing platform for implementing the dialog operation. Note: The meaning of these hints is specific to the implementing platform and protocol. Platforms that do not support hints MAY ignore this attribute. See Section 9.5.6 for additional requirements when hints are supported by the implementing platform.

Voice Browser Call Control: CCXML Version 1.0


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: [Data category] Domain [Local Usage] No [Global, rule-based selection] Yes [Global adding of information] Yes 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] Locale Filter [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] localeFilterType="all" [Overriding] Yes [Inheritance]

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

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] External Resource [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: [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: [0] doctype [1] ro attribute [2] yes [3]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] implementation [1] ro attribute [2] yes [3]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] documentElement [1] ro attribute [2] yes [3]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createElement [1] method [2] yes [3]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createDocumentFragment [1] method [2] no [3]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createTextNode [1] method [2] yes [3]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createComment [1] method [2] no [3]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createCDATASection [1] method [2] no [3]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createProcessingInstruction [1] method [2] no [3]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createAttribute [1] method [2] no [3]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createEntityReference [1] method [2] no [3]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] getElementsByTagName [1] method [2] no [3]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] importNode [1] method [2] no [3]

Output: no

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createElementNS [1] method [2] yes [3]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] createAttributeNS [1] method [2] no [3]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] getElementsByTagNameNS [1] method [2] no [3]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [0] getElementById [1] method [2] yes [3]

Output: yes

Mobile SVG Profiles: SVG Tiny and SVG Basic


Input: [Attribute Type] CDATA [Definition]

Output: Character data


Input: [Attribute Type] ID [Definition]

Output: A document-unique identifier


Input: [Attribute Type] IDREF [Definition]

Output: A reference to a document-unique identifier


Input: [Attribute Type] IDREFS [Definition]

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


Input: [Attribute Type] NAME [Definition]

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


Input: [Attribute Type] NMTOKEN [Definition]

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


Input: [Attribute Type] NMTOKENS [Definition]

Output: One or more white space separated NMTOKEN values


Input: [Final] Final [Description] The operation succeeded. [anyURI Name]

Output: Success

XML Key Management Specification (XKMS 2.0)


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

Output: VersionMismatch

XML Key Management Specification (XKMS 2.0)


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

Output: Sender

XML Key Management Specification (XKMS 2.0)


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

Output: Receiver

XML Key Management Specification (XKMS 2.0)


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

Output: Represent

XML Key Management Specification (XKMS 2.0)


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

Output: Pending

XML Key Management Specification (XKMS 2.0)


Input: [Category] Project purpose and scope [4] The project purpose is well defined: the client is described well, the scope of the project and the project goals are clear and understandable. [2] Some of the project purpose is defined: the client is described only partially, the scope of the project and the project goals are partially clear and understandable. [1] Little if any of the project purpose is defined: the client description is inaccurate, the scope of the project and the project goals are unclear and difficult to understand. [3]

Output: The project purpose is mostly defined: the client is described moderately, the scope of the project and the project goals are mostly clear and understandable.

Interact/Project Management - Web Education Community Group


Input: [Category] Stakeholders / sponsors [4] All of the stakeholders/sponsors have accurate and complete contact information. [2] Some stakeholders/sponsors have accurate and mostly complete contact information. [1] Few if any of the stakeholders/sponsors have accurate and complete contact information. [3]

Output: The stakeholders/sponsors have accurate and mostly complete contact information.

Interact/Project Management - Web Education Community Group


Input: [Category] Success criteria and quality definition [4] The success criteria is itemized, accurate and complete. [2] The success criteria is itemized, partially accurate and somewhat complete. [1] The success criteria is poorly itemized, potentially inaccurate and incomplete. [3]

Output: The success criteria is itemized, mostly accurate and mostly complete.

Interact/Project Management - Web Education Community Group


Input: [Category] Project constraints, assumptions and dependencies [4] Project constraints are clearly and comprehensively outlined, complete with assumptions and dependencies. [2] Project constraints are partially outlined, with some assumptions and dependencies. [1] Project constraints not poorly outlined, with some assumptions and dependencies. [3]

Output: Project constraints are clearly outlined, complete with assumptions and dependencies.

Interact/Project Management - Web Education Community Group


Input: [Category] Resources [4] Resources are comprehensively listed. [2] Resources are partially listed. [1] Resources are incomplete. [3]

Output: Resources are mostly listed.

Interact/Project Management - Web Education Community Group


Input: [Category] Budget [4] The project budget is itemized, accurate and complete. [2] The project budget is itemized, partially accurate and somewhat complete. [1] The project budget is poorly itemized, potentially inaccurate and incomplete. [3]

Output: The project budget is itemized, mostly accurate and mostly complete.

Interact/Project Management - Web Education Community Group


Input: [Category] Milestones [4] Milestones are comprehensively indicated. [2] Milestones are partially indicated. [1] Some or few milestones are indicated. [3]

Output: Most milestones are indicated.

Interact/Project Management - Web Education Community Group


Input: [Category] Time/cost estimation [4] The time/cost estimations are clear and accurate. [2] The time/cost estimations are only partially clear and accurate. [1] The time/cost estimations are only unclear and of questionable accuracy. [3]

Output: The time/cost estimations are mostly clear and accurate.

Interact/Project Management - Web Education Community Group


Input: [Category] Process [4] The explanation of the project process is clear, easy to understand, and follows a natural progression. Roles and participation of parties involved is clearly explained. [2] The explanation of the project process is only partially clear and understandable, and only slightly follows a natural progression. Roles and participation of parties involved are not fully explained. [1] The explanation of the project process is unclear and not understandable, and only does not follow a natural progression. Roles and participation of parties involved are unclear or not explained. [3]

Output: The explanation of the project process is fairly clear, moderately understandable, and mostly follows a natural progression. Roles and participation of parties involved is moderately explained.

Interact/Project Management - Web Education Community Group


Input: [Category] Project solution proposal [4] Description is clear, concise and states what activities that will be undertaken, as well as an appropriate technological solution. [2] Description is vague, too long (or too short) mentioning some activities that will be undertaken and a fairly appropriate technological solution. [1] Description is vague, too long (or too short) mentioning some activities that will be undertaken and an inappropriate technological solution. [3]

Output: Description is clear, concise, mentioning most activities that will be undertaken, as well as an appropriate technological solution.

Interact/Project Management - Web Education Community Group


Input: [Category] Presentation [4] The scope document is well-organized, consistently formatted, and has a very professional presentation/look and feel. [2] The scope document is only somewhat organized and consistently formatted, and has a slight professional presentation/look and feel. [1] The scope document is poorly organized and inconsistently formatted, and completely lacks a professional presentation/look and feel. [3]

Output: The scope document is mostly organized and consistently formatted, and has a moderatly professional presentation/look and feel.

Interact/Project Management - Web Education Community Group


Input: [Name] exclusiveMode ExclusiveMode [Values] true or false [Description] whether to do inclusive or exclusive dealing of namespaces. In exclusive mode the inclusiveNamespacePrefixList InclusiveNamespaces parameter can be specified listing the prefixes that are to be treated in an inclusive mode [Default]

Output: false


Input: [Name] inclusiveNamespacePrefixList InclusiveNamespace [Values] space separated list of prefixes [Description] list of prefixes to be treated inclusively. Special token #default indicates the default namespace. [Default]

Output: empty


Input: [Name] ignoreComments IgnoreComments [Values] true or false [Description] whether to ignore comments during canonicalization [Default]

Output: true


Input: [Name] trimTextNodes TrimTextNodes [Values] true or false [Description] whether to trim (i.e. remove leading and trailing whitespaces) all text nodes when canonicalizing. Adjacent text nodes must be coalesced prior to trimming. If an element has an xml:space="preserve" attribute, then text nodes node descendants of that element are not trimmed regardless of the value of this parameter. [Default]

Output: false


Input: [Name] serialization Serialization [Values] XML serializeXML or EXI serializeEXI [Description] whether to do the normal XML serialization, serialization ( http://www.w3.org/2010/xml-c14n2#serializeXML ), or do an EXI serialization ( http://www.w3.org/2010/xml-c14n2#serializeEXI ) - which is useful if the original document to be signed canonicalized is already in EXI format. [Default]

Output: XML serializeXML


Input: [Name] prefixRewrite PrefixRewrite [Values] none, sequential, derived [Description] with none, prefixes are not changed, with sequential prefixes are changed to n1, n2, n3 ... and with derived, each prefix is changed to nSuffix, where the suffix is derived by doing a digest of the namespace URI. [Default]


Input: [Name] sortAttributes SortAttributes [Values] true or false [Description] whether the attributes need to be sorted before canonicalization. In some environments the order of attributes changes in transit so sorting is important. [Default]

Output: true


Input: [Name] ignoreDTD XmlAncestors [Values] true or false inherit, none [Description] if set where to true, ignore inherit the DTD completely, which means do not normalize attributes, do not look into entity definitions, do not add default simple inheritable attributes ( xml:lang and xml:space ) and combine the xml:base i.e. similar to each element false expandEntities true Canonical XML 1.1 or false if set to true completely ignore all entity declarations, and expand only the predefined entites (lt, gt, amp, apos, quot) and character references. (Entity declarations are potential attack points, [BradHill] mentions an entity that is 2 GB is length, also expanding external entities can lead xml attributes in ancestors similar to cross site scripting attacks) Exclusive Canonical XML 1.0 [Default]

Output: true inherit


Input: [Name] xmlBaseAncestors QNameAware [Values] inherit, none, combine an enumeration of qualified element names, qualified attribute names, and unqualified attribute names (identified by name, and parent qualified name) [Description] whether to inherit xml:base attributes from ancestors (like C14N 1.0) or not (like Exc C14n 1.0) set of nodes whose entire content must be processed as QName-valued or combine them (like C14n 1.1) [ CURIE ]-valued for the purposes of canonicalization, including prefix rewriting and recognition of prefix "visible utilization" [Default]

Output: combine empty set


Input: [timeRefURI] Attribute indicating the URI used to anchor the relative timestamp. [Annotation]

Output: Definition


Input: [timeRefURI] timeRefAnchor [Annotation]

Output: Annotation


Input: [timeRefURI] Attribute indicating whether to measure the time from the start or end of the interval designated with timeRefURI. Possible values are "start" and "end", default value is "start". [Annotation]

Output: Definition


Input: [timeRefURI] offsetToStart [Annotation]

Output: Annotation


Input: [timeRefURI] Attribute with a time value, defaulting to zero. It specifies the offset for the start of input from the anchor point designated with timeRefURI and timeRefAnchor. Allowed values must be conform with the SMIL clock value syntax [Annotation]

Output: Definition


Input: [timeRefURI] The above attributes MAY occur as part of an . If offsetToStart or timeRefAnchor are given, timeRefURI MUST also be specified. [Annotation]

Output: Occurence


Input: [anyURI Name] Success [Description] The operation succeeded. [Final]

Output: Final

XML Key Management Specification (XKMS 2.0)


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

Output: Final

XML Key Management Specification (XKMS 2.0)


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

Output: Final

XML Key Management Specification (XKMS 2.0)


Input: [anyURI Name] Receiver [Description] An error occurred at the receiver. [Final]

Output: Final

XML Key Management Specification (XKMS 2.0)


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

Output: Not Final

XML Key Management Specification (XKMS 2.0)


Input: [anyURI Name] Pending [Description] The request has been accepted for processing and the service will return the result asynchronously. [Final]

Output: Not Final

XML Key Management Specification (XKMS 2.0)


Input: [Description] Specifies whether a condition is checking for the 'Success' or the 'Failure' of a binding attempt, or whether a binding attempt should be retried in the case of a 'server busy' error. Any variable that returns a NULL value will cause the entire binding to fail, unless the NULLOK attribute of that variable has been set to true. Conditions can catch the success or failure of either a specific object reference or of an entire binding. In the case where a condition initiates a service chain, it is important that all variables bind properly. [Type] String [#] 0 or 1 [Default] "Success" [Attribute Name]

Output: TYPE

Web Interface Definition Language Submission


Input: [Description] Specifies an object reference which extracts data from the HTML or XML document returned as the result of a service invocation. The Reference attribute for conditions is equivalent to the Reference attribute used in variable definitions. Identifies the document object property that will be compared with the text pattern specified by the Match attribute. [Type] String [#] Exactly One [Attribute Name]

Output: REFERENCE

Web Interface Definition Language Submission


Input: [Description] Specifies a text pattern that will be compared with the object property referenced by the Reference attribute. [Type] String [#] Exactly One [Attribute Name]

Output: MATCH

Web Interface Definition Language Submission


Input: [Description] Specifies an alternate output binding. Typically a failure condition indicates that the document returned cannot be bound properly. Rebind redirects the binding attempt. The use of REBIND allows a conditions to determine the appropriate binding for extracting the desired data. Must refer to a binding that is defined in the same WIDL interface. [Type] String [#] 0 or 1 [Attribute Name]

Output: REBIND

Web Interface Definition Language Submission


Input: [Description] Specifies a service to invoke with the results of an output binding. Aside from the obvious benefit of chaining services to further automate the tasks that can be encapsulated for client programs, there are many cases when target documents can only be retrieved after visiting several Web pages in succession. In some instances cookies are issued by an entry page that must be visited prior to interacting with HTML forms; in others, URLs are dynamically generated from databases for specific user identities. [Type] String [#] 0 or 1 [Attribute Name]

Output: SERVICE

Web Interface Definition Language Submission


Input: [Description] Reference to an object's attribute to be returned as an error message when a service fails. [Type] String [#] 0 or 1 [Attribute Name]

Output: REASONREF

Web Interface Definition Language Submission


Input: [Description] The text to be returned as an error message when a service fails. [Type] String [#] 0 or 1 [Attribute Name]

Output: REASONTEXT

Web Interface Definition Language Submission


Input: [Description] Number of seconds to wait before re-trying retrieval of a document after a server has returned a 'service busy' error. [Type] String [#] 0 or 1 [Attribute Name]

Output: WAIT

Web Interface Definition Language Submission


Input: [Description] Number of times to retry the service before failing. [Type] String [#] 0 or 1 [Attribute Name]

Output: RETRIES

Web Interface Definition Language Submission


Input: [Component] XPath 1.0 compatibility mode [Value]

Output: false

Static Context Components for use-when Expressions


Input: [Component] In scope namespaces [Value]

Output: determined by the in-scope namespaces for the containing element in the stylesheet


Input: [Component] Default element/type namespace [Value]

Output: determined by the xpath-default-namespace attribute if present (see 5.2 Unprefixed QNames in Expressions and Patterns); otherwise the null namespace


Input: [Component] Default function namespace [Value]

Output: The standard function namespace


Input: [Component] In scope type definitions [Value]

Output: The type definitions that would be available in the absence of any xsl:import-schema declaration


Input: [Component] In scope element declarations [Value]


Input: [Component] In scope attribute declarations [Value]


Input: [Component] In scope variables [Value]


Input: [Component] In scope functions [Value]

Output: The core functions defined in [Functions and Operators], together with the functions element-available, function-available, and system-property defined in this specification, plus an implementation-defined set of extension functions. Note that stylesheet functions are not included in the context, which means that the function function-available will return false in respect of such functions.


Input: [Component] In scope collations [Value]

Output: Implementation-defined


Input: [Component] Default collation [Value]

Output: The Unicode Codepoint Collation


Input: [Component] Base URI [Value]

Output: The base URI of the containing element in the stylesheet


Input: [Component] Statically known documents [Value]


Input: [Component] Statically known collections [Value]


Input: [Category] Project purpose and scope [4] The project purpose is well defined: the client is described well, the scope of the project and the project goals are clear and understandable. [3] The project purpose is mostly defined: the client is described moderately, the scope of the project and the project goals are mostly clear and understandable. [2] Some of the project purpose is defined: the client is described only partially, the scope of the project and the project goals are partially clear and understandable. [1]

Output: Little if any of the project purpose is defined: the client description is inaccurate, the scope of the project and the project goals are unclear and difficult to understand.

Interact/Project Management - Web Education Community Group


Input: [Category] Stakeholders / sponsors [4] All of the stakeholders/sponsors have accurate and complete contact information. [3] The stakeholders/sponsors have accurate and mostly complete contact information. [2] Some stakeholders/sponsors have accurate and mostly complete contact information. [1]

Output: Few if any of the stakeholders/sponsors have accurate and complete contact information.

Interact/Project Management - Web Education Community Group


Input: [Category] Success criteria and quality definition [4] The success criteria is itemized, accurate and complete. [3] The success criteria is itemized, mostly accurate and mostly complete. [2] The success criteria is itemized, partially accurate and somewhat complete. [1]

Output: The success criteria is poorly itemized, potentially inaccurate and incomplete.

Interact/Project Management - Web Education Community Group


Input: [Category] Project constraints, assumptions and dependencies [4] Project constraints are clearly and comprehensively outlined, complete with assumptions and dependencies. [3] Project constraints are clearly outlined, complete with assumptions and dependencies. [2] Project constraints are partially outlined, with some assumptions and dependencies. [1]

Output: Project constraints not poorly outlined, with some assumptions and dependencies.

Interact/Project Management - Web Education Community Group


Input: [Category] Resources [4] Resources are comprehensively listed. [3] Resources are mostly listed. [2] Resources are partially listed. [1]

Output: Resources are incomplete.

Interact/Project Management - Web Education Community Group


Input: [Category] Budget [4] The project budget is itemized, accurate and complete. [3] The project budget is itemized, mostly accurate and mostly complete. [2] The project budget is itemized, partially accurate and somewhat complete. [1]

Output: The project budget is poorly itemized, potentially inaccurate and incomplete.

Interact/Project Management - Web Education Community Group


Input: [Category] Milestones [4] Milestones are comprehensively indicated. [3] Most milestones are indicated. [2] Milestones are partially indicated. [1]

Output: Some or few milestones are indicated.

Interact/Project Management - Web Education Community Group


Input: [Category] Time/cost estimation [4] The time/cost estimations are clear and accurate. [3] The time/cost estimations are mostly clear and accurate. [2] The time/cost estimations are only partially clear and accurate. [1]

Output: The time/cost estimations are only unclear and of questionable accuracy.

Interact/Project Management - Web Education Community Group


Input: [Category] Process [4] The explanation of the project process is clear, easy to understand, and follows a natural progression. Roles and participation of parties involved is clearly explained. [3] The explanation of the project process is fairly clear, moderately understandable, and mostly follows a natural progression. Roles and participation of parties involved is moderately explained. [2] The explanation of the project process is only partially clear and understandable, and only slightly follows a natural progression. Roles and participation of parties involved are not fully explained. [1]

Output: The explanation of the project process is unclear and not understandable, and only does not follow a natural progression. Roles and participation of parties involved are unclear or not explained.

Interact/Project Management - Web Education Community Group


Input: [Category] Project solution proposal [4] Description is clear, concise and states what activities that will be undertaken, as well as an appropriate technological solution. [3] Description is clear, concise, mentioning most activities that will be undertaken, as well as an appropriate technological solution. [2] Description is vague, too long (or too short) mentioning some activities that will be undertaken and a fairly appropriate technological solution. [1]

Output: Description is vague, too long (or too short) mentioning some activities that will be undertaken and an inappropriate technological solution.

Interact/Project Management - Web Education Community Group


Input: [Category] Presentation [4] The scope document is well-organized, consistently formatted, and has a very professional presentation/look and feel. [3] The scope document is mostly organized and consistently formatted, and has a moderatly professional presentation/look and feel. [2] The scope document is only somewhat organized and consistently formatted, and has a slight professional presentation/look and feel. [1]

Output: The scope document is poorly organized and inconsistently formatted, and completely lacks a professional presentation/look and feel.

Interact/Project Management - Web Education Community Group


Input: [1] Description of an emotion or a related state using a set of action tendencies. [Annotation]

Output: Definition


Input: [1] MUST contain one or more action-tendency elements. The names of action-tendency elements which may occur as valid child elements are identified by the set attribute. [Annotation]

Output: Children


Input: [1] Required: set, a name or URI identifying the set of action-tendency names that can be used. Optional: confidence, the annotator's confidence that the entirety of action-tendency annotation given is correct. [Annotation]

Output: Attributes


Input: [1] A single MAY occur as a child of . [Annotation]

Output: Occurrence


Input: [1] Action-tendency elements [Annotation]

Output: Annotation


Input: [1] Annotation of a single action-tendency. The tag name must be contained in the list of values identified by the set attribute of the enclosing element. [Annotation]

Output: Definition


Input: [1] Optionally, an action-tendency MAY have a child element. [Annotation]

Output: Children


Input: [1] Required: (none) Optional: value, the (constant) scale value of this action-tendency. confidence, the annotator's (constant) confidence that the annotation given for this action-tendency is correct. [Annotation]

Output: Attributes


Input: [1] action-tendency elements occur as children of . Valid tag names are constrained to the set of action-tendency names identified in the set attribute of the parent element. For any given action-tendency name in the set, zero or one occurrences are allowed within a element. [Annotation]

Output: Occurrence


Input: [Category] Project purpose and scope [4] The project purpose is well defined: the client is described well, the scope of the project and the project goals are clear and understandable. [3] The project purpose is mostly defined: the client is described moderately, the scope of the project and the project goals are mostly clear and understandable. [1] Little if any of the project purpose is defined: the client description is inaccurate, the scope of the project and the project goals are unclear and difficult to understand. [2]

Output: Some of the project purpose is defined: the client is described only partially, the scope of the project and the project goals are partially clear and understandable.

Interact/Project Management - Web Education Community Group


Input: [Category] Stakeholders / sponsors [4] All of the stakeholders/sponsors have accurate and complete contact information. [3] The stakeholders/sponsors have accurate and mostly complete contact information. [1] Few if any of the stakeholders/sponsors have accurate and complete contact information. [2]

Output: Some stakeholders/sponsors have accurate and mostly complete contact information.

Interact/Project Management - Web Education Community Group


Input: [Category] Success criteria and quality definition [4] The success criteria is itemized, accurate and complete. [3] The success criteria is itemized, mostly accurate and mostly complete. [1] The success criteria is poorly itemized, potentially inaccurate and incomplete. [2]

Output: The success criteria is itemized, partially accurate and somewhat complete.

Interact/Project Management - Web Education Community Group


Input: [Category] Project constraints, assumptions and dependencies [4] Project constraints are clearly and comprehensively outlined, complete with assumptions and dependencies. [3] Project constraints are clearly outlined, complete with assumptions and dependencies. [1] Project constraints not poorly outlined, with some assumptions and dependencies. [2]

Output: Project constraints are partially outlined, with some assumptions and dependencies.

Interact/Project Management - Web Education Community Group


Input: [Category] Resources [4] Resources are comprehensively listed. [3] Resources are mostly listed. [1] Resources are incomplete. [2]

Output: Resources are partially listed.

Interact/Project Management - Web Education Community Group


Input: [Category] Budget [4] The project budget is itemized, accurate and complete. [3] The project budget is itemized, mostly accurate and mostly complete. [1] The project budget is poorly itemized, potentially inaccurate and incomplete. [2]

Output: The project budget is itemized, partially accurate and somewhat complete.

Interact/Project Management - Web Education Community Group


Input: [Category] Milestones [4] Milestones are comprehensively indicated. [3] Most milestones are indicated. [1] Some or few milestones are indicated. [2]

Output: Milestones are partially indicated.

Interact/Project Management - Web Education Community Group


Input: [Category] Time/cost estimation [4] The time/cost estimations are clear and accurate. [3] The time/cost estimations are mostly clear and accurate. [1] The time/cost estimations are only unclear and of questionable accuracy. [2]

Output: The time/cost estimations are only partially clear and accurate.

Interact/Project Management - Web Education Community Group


Input: [Category] Process [4] The explanation of the project process is clear, easy to understand, and follows a natural progression. Roles and participation of parties involved is clearly explained. [3] The explanation of the project process is fairly clear, moderately understandable, and mostly follows a natural progression. Roles and participation of parties involved is moderately explained. [1] The explanation of the project process is unclear and not understandable, and only does not follow a natural progression. Roles and participation of parties involved are unclear or not explained. [2]

Output: The explanation of the project process is only partially clear and understandable, and only slightly follows a natural progression. Roles and participation of parties involved are not fully explained.

Interact/Project Management - Web Education Community Group


Input: [Category] Project solution proposal [4] Description is clear, concise and states what activities that will be undertaken, as well as an appropriate technological solution. [3] Description is clear, concise, mentioning most activities that will be undertaken, as well as an appropriate technological solution. [1] Description is vague, too long (or too short) mentioning some activities that will be undertaken and an inappropriate technological solution. [2]

Output: Description is vague, too long (or too short) mentioning some activities that will be undertaken and a fairly appropriate technological solution.

Interact/Project Management - Web Education Community Group


Input: [Category] Presentation [4] The scope document is well-organized, consistently formatted, and has a very professional presentation/look and feel. [3] The scope document is mostly organized and consistently formatted, and has a moderatly professional presentation/look and feel. [1] The scope document is poorly organized and inconsistently formatted, and completely lacks a professional presentation/look and feel. [2]

Output: The scope document is only somewhat organized and consistently formatted, and has a slight professional presentation/look and feel.

Interact/Project Management - Web Education Community Group


Input: [0] The cells in [1] this table [2]

Output: should go


Input: [0] green when [1] you hover [2]

Output: the pointing


Input: [0] The rows in [1] this table [2]

Output: should go


Input: [0] dark green [1] when the [2]

Output: pointing device


Input: [0] is over the [1] five pixel [2]

Output: border spacing


Input: [0] Including here, [2]

Output: blank cells.


Input: [Expression] font name [Description] the name of the font [Setting]

Output: string


Input: [Expression] point size [Description] the size of the font [Setting]

Output: short int


Input: [Expression] weight [Description] use plain face [Setting]

Output: plain


Input: [Description] use bold face [Setting]

Output: bold


Input: [Expression] effects [Description] underline the text [Setting]

Output: underline


Input: [Expression] form [Description] use the italic form [Setting]

Output: italics


Input: [IDL type] boolean [ECMAScript type]

Output: Boolean

ECMAScript Language Binding – SVG 1.1 (Second Edition)


Input: [IDL type] float [ECMAScript type]

Output: Number

ECMAScript Language Binding – SVG 1.1 (Second Edition)


Input: [IDL type] long [ECMAScript type]

Output: Number

ECMAScript Language Binding – SVG 1.1 (Second Edition)


Input: [IDL type] unsigned short [ECMAScript type]

Output: Number

ECMAScript Language Binding – SVG 1.1 (Second Edition)


Input: [IDL type] unsigned long [ECMAScript type]

Output: Number

ECMAScript Language Binding – SVG 1.1 (Second Edition)


Input: [IDL type] DOMString [ECMAScript type]

Output: String

ECMAScript Language Binding – SVG 1.1 (Second Edition)


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: [Expression] font name [Setting] string [Description]

Output: the name of the font


Input: [Expression] point size [Setting] short int [Description]

Output: the size of the font


Input: [Expression] weight [Setting] plain [Description]

Output: use plain face


Input: [Setting] bold [Description]

Output: use bold face


Input: [Expression] effects [Setting] underline [Description]

Output: underline the text


Input: [Expression] form [Setting] italics [Description]

Output: use the italic form


Input: [0] GET [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict, GSP returns undefined [LDP Container = GSP endpoint] No conflict, GSP returns undefined [LDP Container = GSP graph]

Output: No conflict

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] HEAD [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict; added LDP headers [LDP Container = GSP endpoint] No conflict; added LDP headers [LDP Container = GSP graph]

Output: No conflict; added LDP headers

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] OPTIONS [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict; added LDP headers [LDP Container = GSP endpoint] No conflict; added LDP headers [LDP Container = GSP graph]

Output: No conflict; added LDP headers

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] PUT [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] Conflict [LDP Container = GSP endpoint] Conflict [LDP Container = GSP graph]

Output: No conflict

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] POST [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] Conflict [LDP Container = GSP endpoint] Conflict [LDP Container = GSP graph]

Output: No conflict? Different functionality is to be expected, but do not influence each other

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] DELETE [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict [LDP Container = GSP endpoint] No conflict [LDP Container = GSP graph]

Output: No conflict

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [0] PATCH [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict [LDP Container = GSP endpoint] No conflict [LDP Container = GSP graph]

Output: Conflict; changes through GSP can break consistency in LDPC

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [4] Routinely provides useful ideas when participating in the group and in classroom discussion. Not afraid to challenge an idea constructively. A definite leader who contributes a lot of effort. [3] Usually provides useful ideas when participating in the group and in classroom discussion. Hesitant to challenge ideas. A strong group member who tries hard. [2] Sometimes provides useful ideas when participating in the group and in classroom discussion. Does not challenge existing ideas. A satisfactory group member who does what is required. [1] Rarely provides useful ideas when participating in the group and in classroom discussion. May refuse to participate. [Category]

Output: Contributions

Interact/Project Management - Web Education Community Group


Input: [4] Almost always listens to, shares with, and supports the efforts of others. Tries to keep people working well together. [3] Usually listens to, shares, with, and supports the efforts of others. Does not cause “waves” in the group. [2] Often listens to, shares with, and supports the efforts of others, but sometimes is not a good team member. [1] Rarely listens to, shares with, and supports the efforts of others. Often is not a good team player. [Category]

Output: Working with others

Interact/Project Management - Web Education Community Group


Input: [4] Meeting objectives are clearly defined, items of discussion are listed and written in an actionable manner. [3] Meeting objectives are reasonably clearly stated, items of discussion are listed. [2] Meeting objectives are vague, items of discussion are incomplete and somewhat actionable. [1] Meeting objectives not specific enough, items of discussion are not actionable. [Category]

Output: Meeting agenda

Interact/Project Management - Web Education Community Group


Input: [4] Meeting is kept on track and on time, all points are covered, and all action points are assigned. [3] Meeting runs over time, all points are covered and all action points are assigned. [2] Meeting runs over time, most points are covered, action items established. [1] Meeting runs over time, not all points are covered and action points are not explicitly stated. [Category]

Output: Meeting management

Interact/Project Management - Web Education Community Group


Input: [4] Summary is readable, comprehensive, mentioning attendees, problems raised, solutions decided upon and clear action points assigned to team members. [3] Summary is readable and fairly comprehensive, mentioning some problems raised, solutions decided upon, and clear action points. [2] Summary is fairly readable but not comprehensive, mentions some problem raised, some solutions decided upon and lacking clear action points. [1] Summary is unclear, and not comprehensive, missing problems raised, solutions decided upon and lacking action points. [Category]

Output: Summary message to team

Interact/Project Management - Web Education Community Group


Input: [4] Summary is readable and concise, clearly reiterating the issue, and the team’s proposed solution. Summary indicates clearly what the next steps will be. [3] Summary is readable and concise, clearly reiterating the issue, and the team’s proposed solution. [2] Summary is fairly readable (too long or too short), does not reiterate the issue, but states the team’s proposed solution. [1] Summary is unclear (too long or too short), does not reiterate the issue nor clearly states the team’s proposed solution. [Category]

Output: Summary message to client

Interact/Project Management - Web Education Community Group


Input: [user] name [Category] Physical Contact Information, Demographic and Socioeconomic Data [Short display name] User's Name [Structure]

Output: personname

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


Input: [user] bdate [Category] Demographic and Socioeconomic Data [Short display name] User's Birth Date [Structure]

Output: date

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


Input: [user] cert [Category] Unique Identifiers [Short display name] User's Identity Certificate [Structure]

Output: certificate

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


Input: [user] gender [Category] Demographic and Socioeconomic Data [Short display name] User's Gender (male or female) [Structure]

Output: unstructured

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


Input: [user] employer [Category] Demographic and Socioeconomic Data [Short display name] User's Employer [Structure]

Output: unstructured

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


Input: [user] department [Category] Demographic and Socioeconomic Data [Short display name] Department or division of organization where user is employed [Structure]

Output: unstructured

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


Input: [user] jobtitle [Category] Demographic and Socioeconomic Data [Short display name] User's Job Title [Structure]

Output: unstructured

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


Input: [user] home-info [Category] Physical Contact Information, Online Contact Information, Demographic and Socioeconomic Data [Short display name] User's Home Contact Information [Structure]

Output: contact

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


Input: [user] business-info [Category] Physical Contact Information, Online Contact Information, Demographic and Socioeconomic Data [Short display name] User's Business Contact Information [Structure]

Output: contact

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


Input: [Attribute Name] TYPE [Type] String [#] 0 or 1 [Default] "Success" [Description]

Output: Specifies whether a condition is checking for the 'Success' or the 'Failure' of a binding attempt, or whether a binding attempt should be retried in the case of a 'server busy' error. Any variable that returns a NULL value will cause the entire binding to fail, unless the NULLOK attribute of that variable has been set to true. Conditions can catch the success or failure of either a specific object reference or of an entire binding. In the case where a condition initiates a service chain, it is important that all variables bind properly.

Web Interface Definition Language Submission


Input: [Attribute Name] REFERENCE [Type] String [#] Exactly One [Description]

Output: Specifies an object reference which extracts data from the HTML or XML document returned as the result of a service invocation. The Reference attribute for conditions is equivalent to the Reference attribute used in variable definitions. Identifies the document object property that will be compared with the text pattern specified by the Match attribute.

Web Interface Definition Language Submission


Input: [Attribute Name] MATCH [Type] String [#] Exactly One [Description]

Output: Specifies a text pattern that will be compared with the object property referenced by the Reference attribute.

Web Interface Definition Language Submission


Input: [Attribute Name] REBIND [Type] String [#] 0 or 1 [Description]

Output: Specifies an alternate output binding. Typically a failure condition indicates that the document returned cannot be bound properly. Rebind redirects the binding attempt. The use of REBIND allows a conditions to determine the appropriate binding for extracting the desired data. Must refer to a binding that is defined in the same WIDL interface.

Web Interface Definition Language Submission


Input: [Attribute Name] SERVICE [Type] String [#] 0 or 1 [Description]

Output: Specifies a service to invoke with the results of an output binding. Aside from the obvious benefit of chaining services to further automate the tasks that can be encapsulated for client programs, there are many cases when target documents can only be retrieved after visiting several Web pages in succession. In some instances cookies are issued by an entry page that must be visited prior to interacting with HTML forms; in others, URLs are dynamically generated from databases for specific user identities.

Web Interface Definition Language Submission


Input: [Attribute Name] REASONREF [Type] String [#] 0 or 1 [Description]

Output: Reference to an object's attribute to be returned as an error message when a service fails.

Web Interface Definition Language Submission


Input: [Attribute Name] REASONTEXT [Type] String [#] 0 or 1 [Description]

Output: The text to be returned as an error message when a service fails.

Web Interface Definition Language Submission


Input: [Attribute Name] WAIT [Type] String [#] 0 or 1 [Description]

Output: Number of seconds to wait before re-trying retrieval of a document after a server has returned a 'service busy' error.

Web Interface Definition Language Submission


Input: [Attribute Name] RETRIES [Type] String [#] 0 or 1 [Description]

Output: Number of times to retry the service before failing.

Web Interface Definition Language Submission


Input: [Id: Title] melton1 : Useless and confusing self-referencing link [State] agreed [Ack.] No reply from reviewer [Type]

Output: clarification


Input: [Id: Title] melton2 : Inability to submit comments using the ExIT system [State] agreed [Ack.] No reply from reviewer [Type]

Output: clarification


Input: [Id: Title] melton3 : Unclear form field when attempting to "Create new issue from scratch" [State] agreed [Ack.] No reply from reviewer [Type]

Output: clarification


Input: [Id: Title] melton4 : Unclear structure of XML document containing the actual issues [State] agreed [Ack.] No reply from reviewer [Type]

Output: editorial


Input: [Id: Title] ashok-1 : Global variable or parameter "uri-to-issues-xml" cannot be defined more than once with the same import precedence [State] agreed [Ack.] No reply from reviewer [Type]

Output: error


Input: [Id: Title] walsh1 : Proposed ExIT schema improvements [State] agreed [Ack.] Agreement [Type]

Output: proposal


Input: [Id: Title] melton5 : A Tool vs A Kit to Build a Tool [State] no decision (accepted) [Type]

Output: request


Input: [Id: Title] kay2 : Allow description with the discussion element [State] no decision (raised) [Type]

Output: request


Input: [Id: Title] kay1 : Recording follow-up discussions [State] agreed [Ack.] No reply from reviewer [Type]

Output: request


Input: [Id: Title] jacobs1 : Switch to UTF-8 in /2004 space [State] agreed [Ack.] No reply from reviewer [Type]

Output: request


Input: [Property]

Output: Properties from Place[2]

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


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

Output: address

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


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

Output: aggregateRating

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


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

Output: geo

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


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

Output: map

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


Input: [Expected Type] ImageObject or Photograph [Description] Photographs of this place [Property]

Output: photos

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


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

Output: reviews

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


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

Output: telephone

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


Input: [Description] Applications can create alarms, notifying users [Source] SysApps Charter [Requirement]

Output: Alarm API

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Apps can add, remove and edit contacts [Source] SysApps Charter [Requirement]

Output: Contacts API

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Apps can send, receive and view SMS [Source] SysApps Charter [Requirement]

Output: Messaging API

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Apps can access the telephony capabilities of the underlyling platform: dial a number, pick up a call, route to voicemail, access the call log [Source] SysApps Charter [Requirement]

Output: Telephony API

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Apps can create, manipulate and listen for low-level TCP and UDP connections [Source] SysApps Charter [Requirement]

Output: Raw Sockets API

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Supports a wide variety of devices including desktop & laptop computers, smart phones, tablets, TVs, cameras, and other connected devices [Source] SysApps Charter [Implications] The security model can make no assumptions about how the device will be used or shared between people and cannot assume a particular process model. [Requirement]

Output: Supports many device form factors

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] All APIs defined by DAP should be accessible to system applications [Source] SysApps Charter [Implications] Either DAP APIs will need to change slightly in the systems context or the security model must allow for API-specific access controls [Requirement]

Output: DAP API Support

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Problems such as 'double prompting' should be avoided when integrating other APIs [Source] SysApps Charter [Implications] Some details of the expected user interactions may need to be specified in the security model or APIs [Requirement]

Output: Minimal user prompting

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Applications consist of HTML, CSS and JavaScript [Requirement]

Output: HTML5

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Applications have access to geolocation data [Requirement]

Output: Location

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Applications can communicate with other applications [Implications] Some kind of messaging will be supported [Requirement]

Output: Communicate with other applications

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Applications can communicate with pre-defined web addresses [Implications] Access remote domains will be possible [Requirement]

Output: Communicate with pre-defined endpoints

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Applications can run on any conformant platform, potentially including any device form factor [Source] Compatibility of application packages [Requirement]

Output: Valid across multiple platforms

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Allow access control decisions to be logged. [Source] webinos [Requirement]

Output: Access control log

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Applications shall be able to explain why access to data or APIs is being requested. [Source] webinos [Requirement]

Output: API access rationale

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Applications shall access only its specified device features, extensions and content. [Source] webinos [Requirement]

Output: Application capability restriction

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Applications shall specify its required functionality at install time or during updates. [Source] webinos [Requirement]

Output: Application intent

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Applications shall be isolated from each other. [Source] webinos [Requirement]

Output: Application isolation

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Changes to existing application intentions and permissions shall be approved by the end user. [Source] webinos [Requirement]

Output: Application policy approval

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Before being installed or updated, origin authenticity and integrity checks shall be performed by the runtime [Source] webinos [Requirement]

Output: Authenticity check

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] The list of authorities that certified an application shall be viewable by end-users. [Source] webinos [Requirement]

Output: Certifier list

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] The webinos runtime shall support the confidential storage of user credentials. [Source] webinos [Requirement]

Output: Confidential credentials storage

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Access to credentials storage shall be limited to a specific user, a specific device and a set of applications. [Source] webinos [Requirement]

Output: Credentials access restriction

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] applications shall be able to explain how collected sensitive data will be managed. [Source] webinos [Requirement]

Output: Data management rationale

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] A default security and privacy policy shall exist an be enforced on each conformant runtime [Source] webinos [Requirement]

Output: Default policy

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Personal devices shall be bound to their owner's identities. [Source] webinos [Requirement]

Output: Device-identity binding

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] The binding between personal devices and owner's identity shall be revokable. [Source] webinos [Requirement]

Output: Device-identity binding revokation

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Runtimes can enforce multiple access control rules written by multiple stakeholders in a hierarchy. [Source] webinos [Requirement]

Output: Hierarchical policy enforcement

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Data cached by a runtime shall be securely stored to prevent disclosure and tampering by unauthorised entitites. [Source] webinos [Requirement]

Output: Secure cache

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Application data shall be securely stored to prevent disclosure and tampering by unauthorised entities. [Source] webinos [Requirement]

Output: Secure storage

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] When installing or using an application for the first time, the runtime shall establish that the user trusts the source of the application. [Source] webinos [Implications] Apps must have provenance data attached to them [Requirement]

Output: Trusted application source

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] "An app store needs to be able to approve an application, implying they can verify the permissions, integrity and authenticity of the app" [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications] App permissions can be changed remotely [Requirement]

Output: App stores can revoke applications

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] B2G: "App store must be able to set the default permissions for an app". [Source] Extrapolated from B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications] The user is not the only source of access control decisions. this also suggests a need for conflict resolution. [Requirement]

Output: External trusted party can set app default permissions

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Applications must be installed before executed [Source] B2G, webinos [Requirement]

Output: Installation

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] The device owner must be able to override app settings and permissions (this may not be the user, but a corporate, for example) [Source] B2G (user), webinos (user) [Implications] Access control settings must be changeable [Requirement]

Output: Owner override

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Apps should be able to discover their privileges and degrade gracefully in a limited privilege environment [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications] There must be a standard way for applications to identify the permissions they have and lack [Requirement]

Output: App privilege visibility

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Apps should be able to discover their privileges and degrade gracefully in a limited privilege environment [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Requirement]

Output: Permission usability

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki


Input: [Description] Apps should not be vulnerable to common web vulnerabilities when granted significant privileges [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications] Non-browser security context: may be additional restrictions on HTML/JavaScript [Requirement]

Output: Immunity to browser-based threats

Difference between revisions of "System Applications WG: Security Model" - W3C Wiki