Input: [Name] type [Required] false [Type] ECMAScript Expression [Default Value] application/voicexml+xml [Description] An ECMAScript expression which returns a character string that specifies the MIME type of the document, and as a result determines which dialog manager environment must actually be used. Values defined by the specification are: application/voicexml+xml This MIME type would request a VoiceXML interpreter instance. audio/wav This MIME type would request a dialog manager that merely plays wave files. [Valid Values]

Output: a Valid MIME Type

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] namelist [Required] false [Type] Var List [Default Value] none [Description] A list of one 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". [Valid Values]

Output: List of ECMAScript Variable names

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] parameters [Required] false [Type] Var List [Default Value] none [Description] 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 [Valid Values]

Output: List of ECMAScript Variable names

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] dialogid [Required] false [Type] ECMAScript Left Hand Side Expression [Default Value] none [Description] An ECMAScript left hand side expression evaluating to a previously defined variable. The value of the attribute must receive a dialog identifier value for the launched dialog interpreter instance. [Valid Values]

Output: ECMAScript Variable

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 [Description] An Optional ECMAScript expression which returns the identifier of a connection. The specified connection must be associated with the dialog being prepared. If the attribute value is invalid an error.semantic event must be thrown. [Valid Values]

Output: Connection IDs

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 [Description] An Optional ECMAScript expression which returns the identifier of a conference bridge. A connection must be allocated for the dialog being prepared. 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 dialogstart 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: An ECMAScript expression which returns a character string in CSS2 [CSS2] format

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-age' in HTTP 1.1 [RFC2616]). If maxstale is assigned a value, then the document is willing to accept content that has exceeded its expiration time by no more than the specified number of seconds. [Valid Values]

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

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" [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 dialog type. [Valid Values]

Output: An ECMAScript expression that returns an ECMAScript object

Voice Browser Call Control: CCXML Version 1.0


Input: [event handler] onreceived [event name] received [event type] MessagingEvent [short description]

Output: handles received messages


Input: [event handler] onsent [event name] sent [event type] MessagingEvent [short description]

Output: handles sent messages


Input: [event handler] ondeliverysuccess [event name] deliverysuccess [event type] DeliveryReportEvent [short description]

Output: handles successful delivery reports


Input: [event handler] ondeliveryerror [event name] deliveryerror [event type] DeliveryReportEvent [short description]

Output: handles failure delivery reports


Input: [event handler] onserviceadded [event name] serviceadded [event type] ServiceChangeEvent [short description]

Output: handle new messaging services


Input: [event handler] onserviceremoved [event name] serviceremoved [event type] ServiceChangeEvent [short description]

Output: handle disabled messaging services


Input: [0] Content [Jost Eckhardt, AISquared] All text All enabled elements Attribute info items for some elements (e.g., frames) (Navigation) ordered list of links, frames, form controls Functional blocks of content (in UAAG 1.0 terms, "important elements") Layout v. Data table [Cathy Laws, IBM] Retrieve and change all element content Retrieve and change all attribute values [Jill Thomas, ION]

Output: All text All attribute info items All parent element info items

Summary of API requirements suggested by AT developers


Input: [0] Rendering structure [Jost Eckhardt, AISquared] Coordinates of rendered elements Coordinates of rendered words Coordinates of rendered characters Mapping from screen coordinates to source element [Cathy Laws, IBM] For each rendered character, pixel location Mapping from character pixel location to DOM text node and character offset [Jill Thomas, ION]

Summary of API requirements suggested by AT developers


Input: [0] Style [Jost Eckhardt, AISquared] Text foreground and background color, font family name, text size, font characteristics [Cathy Laws, IBM] Text display attributes [Jill Thomas, ION]

Summary of API requirements suggested by AT developers


Input: [0] UI/Session variables [Jost Eckhardt, AISquared] Content focus (fast access) State of form controls [Cathy Laws, IBM] Selection (including selected non-text content). Get viewports for embedded objets or applets. Note: This is generally done through the operating system, not the API used to access content. [Jill Thomas, ION]

Summary of API requirements suggested by AT developers


Input: [0] Events/Change notification [Jost Eckhardt, AISquared] Content focus Selection Form controls: radio buttons, check boxes, choices, text area Download complete [Cathy Laws, IBM] Receive event notifications for mouse events, key events Changes to elements/attributes [Jill Thomas, ION]

Summary of API requirements suggested by AT developers


Input: [0] Programmatic control [Jost Eckhardt, AISquared] Move rendered content into viewport Move focus to enabled elements Activate enabled elements [Cathy Laws, IBM] For both rendered elements and characters, simulate an event even if not for an enabled element (left or right mouse click) Move focus to viewports with embedded objects or applets. Select content (text and images). Set focus [Jill Thomas, ION]

Summary of API requirements suggested by AT developers


Input: [0] API requirements [Jost Eckhardt, AISquared] Preserve document order [Cathy Laws, IBM] Content information and events must represent rendered content (after error correction). [Jill Thomas, ION]

Output: Preserve document order Provide alert when document object construction is complete.

Summary of API requirements suggested by AT developers


Input: [Name] mode [Type] The only allowed values are "voice" and "dtmf" [Required] No [Default Value] The value of the document property "grammarmode" [Description]

Output: Defines the mode of the grammar following the modes of the W3C Speech Recognition Grammar Specification [SRGS] .

Voice Extensible Markup Language (VoiceXML) 3.0

Table 10: 12: Attributes


Input: [Name] weight [Type] Weights are simple positive floating point values without exponentials. Legal formats are "n", "n.", ".n" and "n.n" where "n" is a sequence of one or many digits. [Required] No [Default Value] 1.0 [Description]

Output: Specifies the weight of the grammar. See vxml2: Section 3.1.1.3

Voice Extensible Markup Language (VoiceXML) 3.0

Table 10: 12: Attributes


Input: [Name] fetchhint [Type] One of the values "safe" or "prefetch" [Required] No [Default Value] None [Description]

Output: Defines when the interpreter context should retrieve content from the server. prefetch indicates a file may be downloaded when the page is loaded, whereas safe indicates a file that should only be downloaded when actually needed.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 10: 12: Attributes


Input: [Name] fetchtimeout [Type] Time Designation [Required] No [Default Value] None [Description]

Output: The interval to wait for the content to be returned before throwing an error.badfetch event.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 10: 12: Attributes


Input: [Name] maxage [Type] An unsigned integer [Required] No [Default Value] None [Description]

Output: 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 Extensible Markup Language (VoiceXML) 3.0

Table 10: 12: Attributes


Input: [Name] maxstale [Type] An unsigned integer [Required] No [Default Value] None [Description]

Output: 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 Extensible Markup Language (VoiceXML) 3.0

Table 10: 12: Attributes


Input: [Attribute Name] name [Type] string [Details] error.connection [Required]

Output: true

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] connectionid [Type] string [Details] The ID of the Connection associated with this event. [Required]

Output: true

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] protocol [Type] string [Details] The platform protocol ID of the Connection protocol. [Required]

Output: false

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] reason [Type] string [Details] A description of the reason the operation failed. Content of this field is platform-specific. [Required]

Output: true

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] info [Type] ECMAScript Object [Details] An object which provides additional platform or protocol dependent information. [Required]

Output: false

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] connection [Type] ECMAScript Object [Details] An ECMAScript object reference to the Connection object identified by the connectionid property of this event. [Required]

Output: true

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] eventid [Type] string [Details] The unique identifier for the event. This must match the sendid attribute of send, if the event was generated by a CCXML document. [Required]

Output: true

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] eventsource [Type] string [Details] The unique identifier of the event source. This identifies the Platform Event I/O Processor that sent this event. [Required]

Output: true

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] eventsourcetype [Type] string [Details] The name of the Event I/O Processor that sent this event. The value is platform dependent as this is an event generated by the Platform Event I/O processor. [Required]

Output: true

Voice Browser Call Control: CCXML Version 1.0


Input: [Name of the Project] Akshaya [Future planes] Delivery of multiple service at Akshaya centers and expand it to other districts [Purpose]

Output: Making a district E-literate, limited employment generation.

Usage and Demand for Mobile Data Services in Rural and Urban India


Input: [Name of the Project] Bhoomi [Future planes] Expand rural kiosk network [Purpose]

Output: Issue of Land title at 177 Bhoomi kiosks and through privately owned kiosks

Usage and Demand for Mobile Data Services in Rural and Urban India


Input: [Name of the Project] Drishtee [Future planes] Expand Network to cover new kiosk [Purpose]

Output: Creating a network of privately owned kiosks for e access to info, government and service commercial

Usage and Demand for Mobile Data Services in Rural and Urban India


Input: [Name of the Project] E-choupal [Future planes] Scale to more users [Purpose]

Output: The prime target is farmer. Farmers get information about seeds’ price, etc

Usage and Demand for Mobile Data Services in Rural and Urban India


Input: [Name of the Project] N-Logue [Future planes] Expand for commercial utilization [Purpose]

Output: Multipurpose Internet kiosks based on WILL

Usage and Demand for Mobile Data Services in Rural and Urban India


Input: [Name of the Project] Gyandoot [Future planes] Extend for global Internet [Purpose]

Output: Connecting rural cyber café catering the everyday needs of the masses.

Usage and Demand for Mobile Data Services in Rural and Urban India


Input: [Type] The only allowed values are "voice" and "dtmf" [Description] Defines the mode of the grammar following the modes of the W3C Speech Recognition Grammar Specification [SRGS] . [Required] No [Default Value] The value of the document property "grammarmode" [Name]

Output: mode

Voice Extensible Markup Language (VoiceXML) 3.0

Table 10: 12: Attributes


Input: [Type] Weights are simple positive floating point values without exponentials. Legal formats are "n", "n.", ".n" and "n.n" where "n" is a sequence of one or many digits. [Description] Specifies the weight of the grammar. See vxml2: Section 3.1.1.3 [Required] No [Default Value] 1.0 [Name]

Output: weight

Voice Extensible Markup Language (VoiceXML) 3.0

Table 10: 12: Attributes


Input: [Type] One of the values "safe" or "prefetch" [Description] Defines when the interpreter context should retrieve content from the server. prefetch indicates a file may be downloaded when the page is loaded, whereas safe indicates a file that should only be downloaded when actually needed. [Required] No [Default Value] None [Name]

Output: fetchhint

Voice Extensible Markup Language (VoiceXML) 3.0

Table 10: 12: Attributes


Input: [Type] Time Designation [Description] The interval to wait for the content to be returned before throwing an error.badfetch event. [Required] No [Default Value] None [Name]

Output: fetchtimeout

Voice Extensible Markup Language (VoiceXML) 3.0

Table 10: 12: Attributes


Input: [Type] An unsigned integer [Description] 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. [Required] No [Default Value] None [Name]

Output: maxage

Voice Extensible Markup Language (VoiceXML) 3.0

Table 10: 12: Attributes


Input: [Type] An unsigned integer [Description] 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. [Required] No [Default Value] None [Name]

Output: maxstale

Voice Extensible Markup Language (VoiceXML) 3.0

Table 10: 12: Attributes


Input: [Attribute Name] name [Required] true [Type] string [Details]

Output: error.move

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] sourceid [Required] true [Type] string [Details]

Output: The ID of the event source referenced either directly via the source attribute or indirectly via the event attribute of the move element.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] sessionid [Required] true [Type] string [Details]

Output: The ID of the target session to which it was attempted to move the event source.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] reason [Required] true [Type] string [Details]

Output: A description of the reason for which the move request failed. Content of this field is platform-specific.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] eventid [Required] true [Type] string [Details]

Output: The unique identifier for the event. This must match the sendid attribute of send, if the event was generated by a CCXML document.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] eventsource [Required] true [Type] string [Details]

Output: The unique identifier of the event source. This identifies the CCXML Event I/O Processor that sent this event.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] eventsourcetype [Required] true [Type] string [Details]

Output: The name of the Event I/O Processor that sent this event. This must be set to ccxml as this is an event generated by the CCXML Session Event processor.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] target [Required] true [Type] ECMAScript Expression [Default Value] none [Valid Values] A valid target URL [Description]

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] targettype [Required] false [Type] ECMAScript Expression [Default Value] ccxml [Valid Values] ccxml dialog basichttp [Description]

Output: 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. Values defined by the specification are: ccxml This specifies that the event must be dispatched to the CCXML Session Event Processor.. dialog This specifies that the event must be dispatched to the Dialog Event Processor. basichttp This specifies that the event must be dispatched to the Basic HTTP Event Processor.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] sendid [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 an internally generated unique string identifier to be associated with the event being sent. If this attribute is not specified, the event identifier must be dropped.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] delay [Required] false [Type] ECMAScript Expression [Default Value] '0s' [Valid Values] An ECMAScript expression which returns a character string in CSS2 [CSS2] format [Description]

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] data name [Required] false [Attribute Constraints] This attribute must not be specified in conjunction with inline content [Type] ECMAScript Expression [Default Value] none [Description]

Output: An ECMAScript expression which returns a character string that indicates the type of event being generated. The event type may include alphanumeric characters and the "." (dot) character. The first character may not be a dot or a digit. Event type names are case-insensitive. If neither the data name attribute nor inline content is specified, an error.fetch event must be thrown. If used in conjunction with the inline content, an error.fetch must be thrown.

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 [Valid Values] List of ECMAScript Variable names [Description]

Output: A list of zero or more whitespace separated CCXML variable names to be included with the event. When an ECMAscript variable is included with the event, its value must be first converted into a string. If the variable is an ECMAScript Object, the mechanism by which it must be included is currently not defined. Instead of including ECMAScript Objects directly, the application developer may explicitly include the properties of an Object. e.g. "date.month date.year". If used in conjunction with the inline content, an error.fetch must be thrown. 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. If used in conjunction with the inline content, an error.fetch must be thrown.

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 to configure the event processor. The meaning of these hints is specific to the implementing platform and the event processor.

Voice Browser Call Control: CCXML Version 1.0


Input: [test #] G1 [Metadata format] Format independent n/a [Implementation 1] passed [Implementation 2] passed [Implementation 3] passed [Normative JSON response] supportedModes:1 supportedModes:2 supportedModes:1,2,3 [Coverage]

Output: Implemented Mode

Implementation report for API for Media Resources 1.0


Input: [test #] G2-incorrect G2-correct [Metadata format] Format independent propertyNames=["fakeIdentifier"] [Implementation 1] passed [Implementation 2] passed [Implementation 3] passed [Normative JSON response] Not existant property Response G2 correct [Coverage]

Output: Not-existent property

Implementation report for API for Media Resources 1.0


Input: [test #] G3-incorrect G3-correct [Metadata format] Format independent propertyNames=NULL [Implementation 1] passed [Implementation 2] passed [Implementation 3] passed [Normative JSON response] Passing NULL value instead property array Response [Coverage]

Output: Passing NULL value instead property array

Implementation report for API for Media Resources 1.0


Input: [test #] G4-incorrect G4-correct [Metadata format] Format independent propertyNames=["identifier","identifier"] [Implementation 1] passed [Implementation 2] passed [Implementation 3] passed [Normative JSON response] Property array filled with duplicates Response [Coverage]

Output: Property array filled with duplicates

Implementation report for API for Media Resources 1.0


Input: [test #] G5 [Metadata format] Format independent Two metadata sources need to be created [Implementation 1] passed [Implementation 2] passed [Implementation 3] passed [Normative JSON response] Multiple metadata sources specified Response [Coverage]

Output: Multiple metadata sources specified

Implementation report for API for Media Resources 1.0


Input: [test #] G6 [Metadata format] Format independent metadataSources = NULL; [Implementation 1] passed [Implementation 2] passed [Implementation 3] passed [Normative JSON response] No metadata source specified Response [Coverage]

Output: No metadata source specified

Implementation report for API for Media Resources 1.0


Input: [test #] G7 [Metadata format] Format independent metadataSources = new MetadataSource[1]; metadataSources[0] = new MetadataSource("http://a.non.existing.url/file.xml","dc") [Implementation 1] passed [Implementation 2] passed [Implementation 3] passed [Normative JSON response] Non-existent metadata source Response [Coverage]

Output: Non-existent metadata source

Implementation report for API for Media Resources 1.0


Input: [Language feature] address element [Restrictions] If specified, role must be contentinfo (ARIA restricts usage of this role to one per page) [Default implied ARIA semantic]

Output: No role


Input: [Language feature] article element [Restrictions] Role must be either article, document, application, or main (ARIA restricts usage of this role to one per page) [Default implied ARIA semantic]

Output: article role


Input: [Language feature] aside element [Restrictions] Role must be either note, complementary, or search [Default implied ARIA semantic]

Output: note role


Input: [Language feature] footer element [Restrictions] If specified, role must be contentinfo (ARIA restricts usage of this role to one per page) [Default implied ARIA semantic]

Output: No role


Input: [Language feature] header element [Restrictions] If specified, role must be banner (ARIA restricts usage of this role to one per page) [Default implied ARIA semantic]

Output: No role


Input: [Language feature] li element whose parent is an ol or ul element [Restrictions] Role must be either listitem or treeitem [Default implied ARIA semantic]

Output: listitem role


Input: [Language feature] ol element [Restrictions] Role must be either list, tree, or directory [Default implied ARIA semantic]

Output: list role


Input: [Language feature] output element [Restrictions] No restrictions [Default implied ARIA semantic]

Output: status role


Input: [Language feature] section element [Restrictions] Role must be either region, document, application, contentinfo (ARIA restricts usage of this role to one per page), main (ARIA restricts usage of this role to one per page), search, alert, dialog, alertdialog, status, or log [Default implied ARIA semantic]

Output: region role


Input: [Language feature] table element [Restrictions] Role must be either grid or treegrid [Default implied ARIA semantic]

Output: grid role


Input: [Language feature] ul element [Restrictions] Role must be either list or tree, or directory [Default implied ARIA semantic]

Output: list role


Input: [Language feature] The body element [Restrictions] Role must be either document or application [Default implied ARIA semantic]

Output: document role


Input: [test #] G1 [Metadata format] Format independent [Coverage] Implemented Mode n/a [Implementation 1] passed [Implementation 2] passed [Implementation 3] passed [Normative JSON response]

Output: supportedModes:1 supportedModes:2 supportedModes:1,2,3

Implementation report for API for Media Resources 1.0


Input: [test #] G2-incorrect G2-correct [Metadata format] Format independent [Coverage] Not-existent property propertyNames=["fakeIdentifier"] [Implementation 1] passed [Implementation 2] passed [Implementation 3] passed [Normative JSON response]

Output: Not existant property Response G2 correct

Implementation report for API for Media Resources 1.0


Input: [test #] G3-incorrect G3-correct [Metadata format] Format independent [Coverage] Passing NULL value instead property array propertyNames=NULL [Implementation 1] passed [Implementation 2] passed [Implementation 3] passed [Normative JSON response]

Output: Passing NULL value instead property array Response

Implementation report for API for Media Resources 1.0


Input: [test #] G4-incorrect G4-correct [Metadata format] Format independent [Coverage] Property array filled with duplicates propertyNames=["identifier","identifier"] [Implementation 1] passed [Implementation 2] passed [Implementation 3] passed [Normative JSON response]

Output: Property array filled with duplicates Response

Implementation report for API for Media Resources 1.0


Input: [test #] G5 [Metadata format] Format independent [Coverage] Multiple metadata sources specified Two metadata sources need to be created [Implementation 1] passed [Implementation 2] passed [Implementation 3] passed [Normative JSON response]

Output: Multiple metadata sources specified Response

Implementation report for API for Media Resources 1.0


Input: [test #] G6 [Metadata format] Format independent [Coverage] No metadata source specified metadataSources = NULL; [Implementation 1] passed [Implementation 2] passed [Implementation 3] passed [Normative JSON response]

Output: No metadata source specified Response

Implementation report for API for Media Resources 1.0


Input: [test #] G7 [Metadata format] Format independent [Coverage] Non-existent metadata source metadataSources = new MetadataSource[1]; metadataSources[0] = new MetadataSource("http://a.non.existing.url/file.xml","dc") [Implementation 1] passed [Implementation 2] passed [Implementation 3] passed [Normative JSON response]

Output: Non-existent metadata source Response

Implementation report for API for Media Resources 1.0


Input: [Property] additionalType [Expected Type] URL [Description]

Output: An additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax.


Input: [Property] description [Expected Type] Text [Description]

Output: A short description of the entry.


Input: [Property] image [Expected Type] URL [Description]

Output: URL of an image of the entry.


Input: [Property] name [Expected Type] Text [Description]

Output: The name of the entry.


Input: [Property] url [Expected Type] URL [Description]

Output: URL of the entry.


Input: [Property] alternativeHeadline [Expected Type] Text [Description]

Output: A secondary title of the entry.


Input: [Property] inLanguage [Expected Type] Language [Description]

Output: The language of the content. Please use one of the language codes from the IETF BCP 47 standard.


Input: [Property] dateCreated [Expected Type] Date [Description]

Output: The date on which the content was created (in ISO 8601 date format).


Input: [Property] dateModified [Expected Type] Date [Description]

Output: The date on which the content was most recently modified (in ISO 8601 date format).


Input: [Property] keywords [Expected Type] Text [Description]

Output: The keywords/tags used to describe this content.


Input: [Property] provider [Expected Type] Person or Organization [Description]

Output: Specifies the person or organization that distributed the content.


Input: [Property] breadcrumb [Expected Type] Text [Description]

Output: A set of links that can help a user understand and navigate a website hierarchy.


Input: [Property] entryID [Expected Type] Text [Description]

Output: The identifier of the entry.


Input: [Property] isEntryOf [Expected Type] BiologicalDatabase [Description]

Output: Indicates the database to which the entry belongs.


Input: [Property] taxon [Expected Type] BiologicalDatabaseEntry or Text [Description]

Output: The taxonomy information of the entry.


Input: [Property] seeAlso [Expected Type] BiologicalDatabaseEntry or URL [Description]

Output: Reference to another resource.


Input: [Property] reference [Expected Type] Text [Description]

Output: The identifier of the reference, such as PMID, DOI, and PMCID. For example: .


Input: [Action] connection.disconnected [Event] connection.progressing [End State] DISCONNECTED [Description]

Output: Call was disconnected by the network/remote party.

Voice Browser Call Control: CCXML Version 1.0


Input: [Action] connection.signal [Event] connection.signal [End State] CONNECTED [Description]

Output: Additional Connection related information is available for processing by the CCXML application.

Voice Browser Call Control: CCXML Version 1.0


Input: [Event] connection.redirected [End State] DISCONNECTED [Description]

Output: The CCXML document redirects an connected call.

Voice Browser Call Control: CCXML Version 1.0


Input: [Event] connection.disconnected [End State] DISCONNECTED [Description]

Output: The CCXML document disconnects an active call.

Voice Browser Call Control: CCXML Version 1.0


Input: [Event] connection.merged [End State] DISCONNECTED [Description]

Output: The CCXML document merges an incoming/connected call with another call at the network level.

Voice Browser Call Control: CCXML Version 1.0


Input: [Action] error.connection [Event] error.connection [End State] ERROR [Description]

Output: The CCXML connection had a platform operational error.

Voice Browser Call Control: CCXML Version 1.0


Input: [Action] connection.disconnected [Description] Call was disconnected by the network/remote party. [End State] DISCONNECTED [Event]

Output: connection.progressing

Voice Browser Call Control: CCXML Version 1.0


Input: [Action] connection.signal [Description] Additional Connection related information is available for processing by the CCXML application. [End State] CONNECTED [Event]

Output: connection.signal

Voice Browser Call Control: CCXML Version 1.0


Input: [Description] The CCXML document redirects an connected call. [End State] DISCONNECTED [Event]

Output: connection.redirected

Voice Browser Call Control: CCXML Version 1.0


Input: [Description] The CCXML document disconnects an active call. [End State] DISCONNECTED [Event]

Output: connection.disconnected

Voice Browser Call Control: CCXML Version 1.0


Input: [Description] The CCXML document merges an incoming/connected call with another call at the network level. [End State] DISCONNECTED [Event]

Output: connection.merged

Voice Browser Call Control: CCXML Version 1.0


Input: [Action] error.connection [Description] The CCXML connection had a platform operational error. [End State] ERROR [Event]

Output: error.connection

Voice Browser Call Control: CCXML Version 1.0


Input: [Required] true [Type] ECMAScript Expression [Default Value] none [Valid Values] must evaluate to a valid URL [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] application/ccxml+xml [Valid Values] application/ccxml+xml text/ecmascript text/javascript [Description] An ECMAScript expression which returns a character string that specifies the MIME type of the fetched content. Values defined by the specification are: application/ccxml+xml This species that the document being fetched is a CCXML document. text/ecmascript This species that the fetched content is ECMA Script. text/javascript This species that the fetched content is JAVA Script. [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 will be submitted to the server, with the same qualification as used in the namelist. When an ECMAscript variable is submitted to the server, its value is first converted into a string before being submitted. If the variable is an ECMAScript Object, the mechanism by which it is submitted is not currently defined. Instead of submitting ECMAScript Objects directly, the application developer may explicitly submit the properties of an Object. e.g. "date.month date.year". [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 will be used to fetch the URL. post This indicates that the "POST" method will be used while submitting the URL to the 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 will 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 will receive a unique fetch identifier, even if the request if for the same URL. [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 is interpreted as a time interval. This interval begins when the fetch is executed. The fetch will fail if not completed at the end of this interval. A failed fetch will 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 is interpreted as a time interval. This indicates that the document is willing to use content whose age is no greater than the specified time in seconds (cf. 'max-age' in HTTP 1.1 [RFC2616]). The document is not willing to use stale content, unless maxstale is also provided. [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 is interpreted as a time interval. This indicates that the document is willing to use content that has exceeded its expiration time (cf. 'max-age' in HTTP 1.1 [RFC2616]). If maxstale is assigned a value, then the document is willing to accept content that has exceeded its expiration time by no more than the specified number of seconds. [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" [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 will be url encoded. [Name]

Output: enctype

Voice Browser Call Control: CCXML Version 1.0


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 should send the event to. [Valid Values]

Output: A valid target URL

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 should be dispatched to. Values defined by the specification are: ccxml This species that the event will be dispatched to the CCXML Session Event Processor.. dialog This species that the event will be dispatched to the Dialog Event Processor.. [Valid Values]

Output: ccxml dialog

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 will receive an internally generated unique string identifier to be associated with the event being sent. If this attribute is not specified, the event identifier is dropped. [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 is interpreted as a time interval. The send tag will return immediately, but the event is not 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 queue for sending events is maintained locally. Any events waiting to be sent will 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 may 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. When an ECMAscript variable is included with the event, its value is first converted into a string. If the variable is an ECMAScript Object, the mechanism by which it is included is not currently defined. Instead of including ECMAScript Objects directly, the application developer may explicitly include the properties of an Object. e.g. "date.month date.year". If used in conjunction with the inline content, an error.fetch will be thrown. [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 processor. The meaning of these hints is specific to the implementing platform and the event processor. [Valid Values]

Output: An ECMAScript expression that returns an ECMAScript object

Voice Browser Call Control: CCXML Version 1.0


Input: [Description] Updated to use the http://www.w3.org/2001/XMLSchema namespace [Class]

Output: Namespace

SOAP Version 1.2 Part 1: Messaging Framework

Changes to Envelope Schema


Input: [Description] Value of targetNamespace attribute changed to http://www.w3.org/2001/06/soap-envelope [Class]

Output: Namespace

SOAP Version 1.2 Part 1: Messaging Framework

Changes to Envelope Schema


Input: [Description] Changed element and attribute wildcards in Envelope complex type to namespace="##other" [Class]

Output: Clarification

SOAP Version 1.2 Part 1: Messaging Framework

Changes to Envelope Schema


Input: [Description] Changed element and attribute wildcards in Header complex type to namespace="##other" [Class]

Output: Clarification

SOAP Version 1.2 Part 1: Messaging Framework

Changes to Envelope Schema


Input: [Description] Added explicit namespace="##any" to element and attribute wildcards in Body complex type [Class]

Output: Clarification

SOAP Version 1.2 Part 1: Messaging Framework

Changes to Envelope Schema


Input: [Description] Added explicit namespace="##any" to element and attribute wildcards in detail complex type [Class]

Output: Clarification

SOAP Version 1.2 Part 1: Messaging Framework

Changes to Envelope Schema


Input: [Description] Added an element wildcard with namespace="##other" to the Fault complex type [Class]

Output: Clarification

SOAP Version 1.2 Part 1: Messaging Framework

Changes to Envelope Schema


Input: [Description] Changed item type of encodingStyle from uri-reference to anyURI [Class]

Output: Name

SOAP Version 1.2 Part 1: Messaging Framework

Changes to Envelope Schema


Input: [Description] Changed type of actor attribute from uri-reference to anyURI [Class]

Output: Name

SOAP Version 1.2 Part 1: Messaging Framework

Changes to Envelope Schema


Input: [Description] Changed type of faultactor attribute from uri-reference to anyURI [Class]

Output: Name

SOAP Version 1.2 Part 1: Messaging Framework

Changes to Envelope Schema


Input: [Description] Added processContents="lax" to all element and attribute wildcards [Class]

Output: Semantic

SOAP Version 1.2 Part 1: Messaging Framework

Changes to Envelope Schema


Input: [Description] Changed type of the mustUnderstand attribute from restriction of boolean that only allowed 0 or 1 as lexical values to the standard boolean in the http://www.w3.org/2001/XMLSchema namespace. The lexical forms 0, 1, false, true are now allowed. [Class]

Output: Semantic

SOAP Version 1.2 Part 1: Messaging Framework

Changes to Envelope Schema


Input: [Description] Where possible comments have been changed into annotations [Class]

Output: Style

SOAP Version 1.2 Part 1: Messaging Framework

Changes to Envelope Schema


Input: [Description] Changed all occurrences of maxOccurs="*" to maxOccurs="unbounded" [Class]

Output: Syntax

SOAP Version 1.2 Part 1: Messaging Framework

Changes to Envelope Schema


Input: [Description] Added to all complex type definitions derived implicitly from the ur-type [Class]

Output: Syntax

SOAP Version 1.2 Part 1: Messaging Framework

Changes to Envelope Schema


Input: [Description] Added to all named model group definitions [Class]

Output: Syntax

SOAP Version 1.2 Part 1: Messaging Framework

Changes to Envelope Schema


Input: [Description] Changed local name of faultcode element to Code [Class]

Output: Name

SOAP Version 1.2 Part 1: Messaging Framework

Changes to Envelope Schema


Input: [Description] Changed local name of value element to Value [Class]

Output: Name

SOAP Version 1.2 Part 1: Messaging Framework

Changes to Envelope Schema


Input: [Description] Changed local name of subcode element to Subcode [Class]

Output: Name

SOAP Version 1.2 Part 1: Messaging Framework

Changes to Envelope Schema


Input: [Description] Changed local name of faultstring element to Reason [Class]

Output: Name

SOAP Version 1.2 Part 1: Messaging Framework

Changes to Envelope Schema


Input: [Description] Changed local name of faultactor element to Node [Class]

Output: Name

SOAP Version 1.2 Part 1: Messaging Framework

Changes to Envelope Schema


Input: [Description] Added Role element [Class]

Output: Addition

SOAP Version 1.2 Part 1: Messaging Framework

Changes to Envelope Schema


Input: [Description] Changed local name of detail element to Detail [Class]

Output: Name

SOAP Version 1.2 Part 1: Messaging Framework

Changes to Envelope Schema


Input: [Description] Made all local element declaration declare qualified elements [Class]

Output: Semantic

SOAP Version 1.2 Part 1: Messaging Framework

Changes to Envelope Schema


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: [Target] Source node [Cancelable?] ✓ Cancelable [Drag data store mode] Read/write mode [dropEffect] "none" [Default Action] Initiate the drag-and-drop operation [Event Name]

Output: dragstart


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

Output: drag


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

Output: dragenter


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

Output: dragleave


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

Output: dragover


Input: [Target] Current target element [Cancelable?] ✓ Cancelable [Drag data store mode] Read-only mode [dropEffect] Current drag operation [Default Action] Varies [Event Name]

Output: drop


Input: [Target] Source node [Cancelable?] — [Drag data store mode] Protected mode [dropEffect] Current drag operation [Default Action] Varies [Event Name]

Output: dragend


Input: [Event Name] dragstart [Target] Source node [Cancelable?] ✓ Cancelable [Drag data store mode] Read/write mode [dropEffect] "none" [Default Action]

Output: Initiate the drag-and-drop operation


Input: [Event Name] drag [Target] Source node [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [dropEffect] "none" [Default Action]

Output: Continue the drag-and-drop operation


Input: [Event Name] dragenter [Target] Immediate user selection or the body element [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [dropEffect] Based on effectAllowed value [Default Action]

Output: Reject immediate user selection as potential target element


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


Input: [Event Name] dragover [Target] Current target element [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [dropEffect] Based on effectAllowed value [Default Action]

Output: Reset the current drag operation to "none"


Input: [Event Name] drop [Target] Current target element [Cancelable?] ✓ Cancelable [Drag data store mode] Read-only mode [dropEffect] Current drag operation [Default Action]

Output: Varies


Input: [Event Name] dragend [Target] Source node [Cancelable?] — [Drag data store mode] Protected mode [dropEffect] Current drag operation [Default Action]

Output: Varies


Input: [Criteria] Category

Output: SMS MMS mobile web voice service

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: [Criteria] Type of service

Output: Type of services provided infrastructure type of tools e.g. sms hub, voice platform task specific e.g. market prices type of tool authoring tools e.g. CMS, html auhtoring tool

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: [Criteria] Sector

Output: healthcare education agriculture government

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: [Criteria] Transport layer

Output: voice (voice XML, other voice) signaling (SMS, USSD) data connection (mobile web, other data)

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: [Criteria] Initial cost of tool

Output: What is the cost structure? none one-off cost subscription Are there associated tools or components required? software e.g. certain type of server and libraries hardware e.g. a Mac, Linux network capability e.g. 3G, Brew operator specific capability

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: [Criteria] Long-term costs and infrastructure

Output: electricity e.g. computers, servers running 24 hrs a day internet access (what speed?) hosting

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: [Criteria] Operator independence

Output: does it need authorization and partnerships with operators? does it work accross multiple operators? does it work across multiple networks standards?

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: [Criteria] License

Output: Is the tool (or aspects of it) open source? Are there license restrictions?

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: [Criteria] Deployment time [Notes] e.g. days, weeks, months

Output: Time required to learn, set up, and deploy the tool

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: [Criteria] Roadmap

Output: Are plug-ins or additional components available? Are new features planned? Is the tool relatively future-proof from a technology point of view?

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: [Criteria] Existing user base

Output: How many existing users/deployments? Are there case studies available?

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: [Criteria] Required skills for deployment

Output: technology skills programming languages other skills to operate or deploy the tool.

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: [Criteria] Maintenance

Output: Resources required to maintain the tool or service. frequency of maintenance frequency of software updates (if provided by the tool creator) skills required for updates or maintenance e.g. does this require a specialist? time e.g. wordpress updates are provided by the creators however each update requires time to install, adjust settings, verify nothing has broken etc.

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: [Criteria] Documentation

Output: Is documentation available? Is it comprehensive? It is multilingual? Is it online or offline? Who is the target audience? e.g. end-users vs those who deploy the tool

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: [Criteria] Content requirements [Notes] Trying to capture external costs that might be related to the tool. An example might be, an open source server that sends SMS updates, but would require some 3rd party (e.g. health practitioners) to create the SMS content at regular intervals.

Output: Is additional content required for this tool to function effectively?

Mw4d tools - Mobile Web For Social Development (MW4D)


Input: [Criteria] Audience

Output: What audience can be served using this tool? age region (if relevant) spoken language literacy level (language, numeracy, technology)

Mw4d tools - Mobile Web For Social Development (MW4D)


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

Output: Read/write mode


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

Output: Protected mode


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

Output: Protected mode


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

Output: Protected mode


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

Output: Protected mode


Input: [Event Name] drop [Target] Current target element [Cancelable?] ✓ Cancelable [dropEffect] Current drag operation [Default Action] Varies [Drag data store mode]

Output: Read-only mode


Input: [Event Name] dragend [Target] Source node [Cancelable?] — [dropEffect] Current drag operation [Default Action] Varies [Drag data store mode]

Output: Protected mode


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

Output: Required

XML Key Management Specification (XKMS 2.0) Bindings


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

Output: Required in profile II where client is authenticated using payload security for both Request and Response Messages

XML Key Management Specification (XKMS 2.0) Bindings


Input: [XKMS element.attribute name] Response/Signature [Required]

Output: Required

XML Key Management Specification (XKMS 2.0) Bindings


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

Output: Required

XML Key Management Specification (XKMS 2.0) Bindings


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

Output: Required

XML Key Management Specification (XKMS 2.0) Bindings


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

Output: Optional, may be used to protect against Denial of Service

XML Key Management Specification (XKMS 2.0) Bindings


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

Output: Optional, may be used to protect against Denial of Service

XML Key Management Specification (XKMS 2.0) Bindings


Input: [XKMS element.attribute name] Request / MessageDigest .Signature with MAC [Required]

Output: Required in profile I where no mechanism is used to authenticate the client, Optional in profile II where client is authenticated using payload security

XML Key Management Specification (XKMS 2.0) Bindings


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

Output: hidden


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

Output: text


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

Output: search


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

Output: tel


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

Output: url


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

Output: email


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

Output: password


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

Output: datetime


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

Output: date


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

Output: month


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

Output: week


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

Output: time


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

Output: datetime-local


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

Output: number


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

Output: range


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

Output: color


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

Output: checkbox


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

Output: radio


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

Output: file


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

Output: submit


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

Output: image


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

Output: reset


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

Output: button


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

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


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

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


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

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


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

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


Input: [Notation] $i$ [Interpretation]

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


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

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


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

Output: insensitive


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

Output: sensitive


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

Output: insensitive


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

Output: sensitive


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

Output: sensitive


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

Output: sensitive


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

Output: sensitive


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

Output: sensitive


Input: [Property] additionalType [Description] An additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax. [Expected Type]

Output: URL


Input: [Property] description [Description] A short description of the entry. [Expected Type]

Output: Text


Input: [Property] image [Description] URL of an image of the entry. [Expected Type]

Output: URL


Input: [Property] name [Description] The name of the entry. [Expected Type]

Output: Text


Input: [Property] url [Description] URL of the entry. [Expected Type]

Output: URL


Input: [Property] alternativeHeadline [Description] A secondary title of the entry. [Expected Type]

Output: Text


Input: [Property] inLanguage [Description] The language of the content. Please use one of the language codes from the IETF BCP 47 standard. [Expected Type]

Output: Language


Input: [Property] dateCreated [Description] The date on which the content was created (in ISO 8601 date format). [Expected Type]

Output: Date


Input: [Property] dateModified [Description] The date on which the content was most recently modified (in ISO 8601 date format). [Expected Type]

Output: Date


Input: [Property] keywords [Description] The keywords/tags used to describe this content. [Expected Type]

Output: Text


Input: [Property] provider [Description] Specifies the person or organization that distributed the content. [Expected Type]

Output: Person or Organization


Input: [Property] breadcrumb [Description] A set of links that can help a user understand and navigate a website hierarchy. [Expected Type]

Output: Text


Input: [Property] entryID [Description] The identifier of the entry. [Expected Type]

Output: Text


Input: [Property] isEntryOf [Description] Indicates the database to which the entry belongs. [Expected Type]

Output: BiologicalDatabase


Input: [Property] taxon [Description] The taxonomy information of the entry. [Expected Type]

Output: BiologicalDatabaseEntry or Text


Input: [Property] seeAlso [Description] Reference to another resource. [Expected Type]

Output: BiologicalDatabaseEntry or URL


Input: [Property] reference [Description] The identifier of the reference, such as PMID, DOI, and PMCID. For example: . [Expected Type]

Output: Text


Input: [Action] connection.disconnected [Description] Call was disconnected by the network/remote party. [Event] connection.progressing [End State]

Output: DISCONNECTED

Voice Browser Call Control: CCXML Version 1.0


Input: [Action] connection.signal [Description] Additional Connection related information is available for processing by the CCXML application. [Event] connection.signal [End State]

Output: CONNECTED

Voice Browser Call Control: CCXML Version 1.0


Input: [Description] The CCXML document redirects an connected call. [Event] connection.redirected [End State]

Output: DISCONNECTED

Voice Browser Call Control: CCXML Version 1.0


Input: [Description] The CCXML document disconnects an active call. [Event] connection.disconnected [End State]

Output: DISCONNECTED

Voice Browser Call Control: CCXML Version 1.0


Input: [Description] The CCXML document merges an incoming/connected call with another call at the network level. [Event] connection.merged [End State]

Output: DISCONNECTED

Voice Browser Call Control: CCXML Version 1.0


Input: [Action] error.connection [Description] The CCXML connection had a platform operational error. [Event] error.connection [End State]

Output: ERROR

Voice Browser Call Control: CCXML Version 1.0


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

Output: An arbitrary string


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

Output: Text with no line breaks


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

Output: Text with no line breaks


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

Output: Text with no line breaks


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

Output: An absolute IRI


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

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


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

Output: Text with no line breaks (sensitive information)


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

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


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

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


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

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


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

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


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

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


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

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


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

Output: A numerical value


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

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


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

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


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

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


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

Output: An enumerated value


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

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


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

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


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

Output: A coordinate, relative to a particular image's size, with the extra semantic that it must be the last value selected and initiates form submission


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


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


Input: [Name] next [Required] true [Type] ECMAScript Expression [Default Value] none [Valid Values] must evaluate to a valid URL [Description]

Output: An ECMAScript expression which returns the URI of the resource to be fetched.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] type [Required] false [Type] ECMAScript Expression [Default Value] application/ccxml+xml [Valid Values] application/ccxml+xml text/ecmascript text/javascript [Description]

Output: An ECMAScript expression which returns a character string that specifies the MIME type of the fetched content. Values defined by the specification are: application/ccxml+xml This species that the document being fetched is a CCXML document. text/ecmascript This species that the fetched content is ECMA Script. text/javascript This species that the fetched content is JAVA Script.

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 will be submitted to the server, with the same qualification as used in the namelist. When an ECMAscript variable is submitted to the server, its value is first converted into a string before being submitted. If the variable is an ECMAScript Object, the mechanism by which it is submitted is not currently defined. Instead of submitting ECMAScript Objects directly, the application developer may explicitly submit the properties of an Object. e.g. "date.month date.year".

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 will be used to fetch the URL. post This indicates that the "POST" method will be used while submitting the URL to the server.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] fetchid [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 will 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 will receive a unique fetch identifier, even if the request if for the same URL.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] timeout [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression which returns a character string in CSS2 [CSS2] format [Description]

Output: The character string returned is interpreted as a time interval. This interval begins when the fetch is executed. The fetch will fail if not completed at the end of this interval. A failed fetch will return the error.fetch event.

Voice Browser Call Control: CCXML Version 1.0


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

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

Voice Browser Call Control: CCXML Version 1.0


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

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

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" [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 will be url encoded.

Voice Browser Call Control: CCXML Version 1.0


Input: [0] GET [LDP Resource = GSP graph] No conflict [LDP Resource = GSP endpoint] No conflict, GSP returns undefined [LDP Collection = GSP endpoint] No conflict, GSP returns undefined [LDP Collection = 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 Collection = GSP endpoint] No conflict; added LDP headers [LDP Collection = 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 Collection = GSP endpoint] No conflict; added LDP headers [LDP Collection = 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 Collection = GSP endpoint] Conflict [LDP Collection = 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 Collection = GSP endpoint] Conflict [LDP Collection = 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 Collection = GSP endpoint] No conflict [LDP Collection = 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 Collection = GSP endpoint] No conflict [LDP Collection = 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: [Checkpoint] 3.3.1 Error Identification: If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. (Level A) [Comments]

Output: PDF form controls that accept user input provide validation functionality which can alert the user of the error in text. Test results: Test id 31 (Error Validation)

Accessibility Support Documentation for PDF

Guideline 3.3 Input Assistance: Help users avoid and correct mistakes


Input: [Checkpoint] 3.3.2 Labels or Instructions: Labels or instructions are provided when content requires user input. (Level A) [Comments]

Output: PDF form controls allow authors to provide labels or instructions. Test results: Test id 32 (Sample form with correctly labeled controls)

Accessibility Support Documentation for PDF


Input: [Checkpoint] 3.3.3 Error Suggestion: If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. (Level AA) [Comments]

Output: PDF form controls that accept user input provide validation functionality which can alert the user of the error in text. PDF supports scripting functionality which allows customization of error responses, enabling the provision of suggestions when possible.

Accessibility Support Documentation for PDF


Input: [Checkpoint] 3.3.4 Error Prevention (Legal, Financial, Data): For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: (Level AA) Reversible: Submissions are reversible. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission. [Comments]

Output: No Accessibility Support impact. This is design-specific. Application or document authors need to consider this provision and ensure conformance. In such forms, PDF authors are able to utilize validation or server-side error-checking prior to final submission.

Accessibility Support Documentation for PDF


Input: [Checkpoint] 3.3.5 Help: Context-sensitive help is available. (Level AAA) [Comments]

Output: PDF authors can provide context-sensitive help by utilizing the following general techniques: G71: Providing a help link on every Web page G184: Providing text instructions at the beginning of a form or set of fields that describes the necessary input

Accessibility Support Documentation for PDF


Input: [Checkpoint] 3.3.6 Error Prevention (All): For Web pages that require the user to submit information, at least one of the following is true: (Level AAA) Reversible: Submissions are reversible. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission. [Comments]

Output: No Accessibility Support impact. This is design-specific. Application or document authors need to consider this provision and ensure conformance. In such forms, PDF authors are able to utilize validation or server-side error-checking prior to final submission.

Accessibility Support Documentation for PDF


Input: [Definition] Character data [Attribute Type]

Output: CDATA


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

Output: ID


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

Output: IDREF


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

Output: IDREFS


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

Output: NMTOKEN


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

Output: NMTOKENS


Input: [Definition] Sequence of one or more digits ([0-9]) [Attribute Type]

Output: NUMBER


Input: [Field Name] name [Details]

Output: 'dialog.exit'

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] dialogid [Details]

Output: The ID of the dialog.

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] connectionid [Details]

Output: The identifier of the connection to which the dialog connection is bridged (usually the connectionid that was specified in the ). If the dialog is bridged to a conference the value will be undefined.

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] conferenceid [Details]

Output: The identifier of the conference to which the dialog connection is bridged (usually the conferenceid that was specified in the ). If the dialog is bridged to a connection the value will be undefined.

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] namelist [Details]

Output: List of items that are stored on the values sub-object.

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] values.* [Details]

Output: Values returned from the dialog.

Voice Browser Call Control: CCXML Version 1.0


Input: [Model Aspect] End-point basics [Linked Data Platform (LDP)]

Output: A LDP server exposes at least one URI to a container-type resource. A client can learn about the container and its contents (members), by simply fetching the container. If only the non-member information is needed, a client can request only that. If a client needs to know if it can create things in this container, then usual HTTP methods can be used such as HEAD or OPTIONS to learn about which verbs are permitted on the request URI. Need: It might be useful to define a common property for external vocabularies to use to indicate the end-point, take for example: Alternative: LDP provides no new facilities for web clients to acquire URLs to Containers. Web clients might use out of band knowledge, home resources, POWDER, emailing a friend a link, or any other mechanism deemed appropriate by the application's needs. It is possible for a server to expose a single Container as a home resource, which web clients GET and examine to locate other resources (including other Containers). It is also possible for that same home resource to be serialized and provided to a client as a document. LDP assumes that each client is able to obtain whatever URLs it needs through non-LDP means, and restricts itself to an interaction model for Containers and their members.

Difference between revisions of "ISSUE-37" - Linked Data Platform


Input: [Model Aspect] Container basics [Linked Data Platform (LDP)]

Output: A container has a URI where you can start interacting with the container, at the most basic level you can GET a list of members, and for containers with many members it is likely the response is broken into pages. Through HTTP HEAD/OPTIONS introspection, a client can learn which HTTP verbs are permitted on this. Since LDP containers are described using RDF constructs, a LDP server may allow clients to POST the representation of the container to create it. Need: How are the acceptable content-types communicated via HTTP headers? Alternative: Before asking 'how' acceptable content-types are communicated, we need to agree that doing so is required (should it be in-scope for LDP - part of ISSUE-21 perhaps). In the simplest case, once the client "knows" it is dealing with a conformant LDP Container it does know (at least) that Turtle is supported. If communicating supported content-types is in-scope, then a syntax needs to be defined (either new, or re-used). Potential re-use choices might include (and these are not necessarily mutually exclusive, although to keep clients simple it would help to have at least one required method if it is in-scope): atom:accept predicate(s) on a container Link: <>; rel="self"; type="one acceptable media type value" Linking itself to a POWDER document - I don't see any POWDER syntax covering media types, but it might be possible to re-use atom:accept in this context. Aside: If we do place it in-scope, we have the same question about members, so it might be that we talk about this introspection at the LDPR level and let LDPCs "inherit" it from LDPRs. LDPRs might leave everything optional, and LDPC requires one particular method while allowing others, for example.

Difference between revisions of "ISSUE-37" - Linked Data Platform


Input: [Model Aspect] Creating container members (resources) [Linked Data Platform (LDP)]

Output: Any kind of resource can be listed in a container, and everything that is in a container is represented by a member. Members follow the standardized metadata model defined by RDF. If a client has POSTed a "media resource" (pretty much anything other than RDF) to a container URI, which has one of the media types that the container accepts, the server accepts this media resource and creates the resource, which will then represent this media resource when you list the container contents. The interesting aspect of this setup is that you POST one thing, its representation gets converted by the server to some appropriate storage and its membership added to the container. email: there is only one container, and what you POST determines whether it's self-contained or not. if the POSTed resource contains all data (... in XML), it's what we now call "composition". if the POSTed resource contains a link to "external content" ( in XML), it's what we now call "aggregation". Servers might try to be smart about populating additional data fields for the resource, for example creation date and who created it. They also might consider come properties to be "server managed", i.e. read-only from any client's point of view. ISSUE-11 questions how much the LDP spec constrains them.

Difference between revisions of "ISSUE-37" - Linked Data Platform


Input: [Model Aspect] Member (resource) identity [Linked Data Platform (LDP)]

Output: A container is a set of members and (perhaps) non-member properties, and thus contains a list of members (entries) representing each individual member. The model uses a URI to represent the identity of each member resource, which will be used for identification globally. The identification of the member as an entry, will be represented as using a simple RDF statement: rdfs:member . Note: some proposals on the mailing list for ISSUE-34 include the use of different membership predicates like ldp:owns or ldp:contains in place of rdfs:member. If accepted, those predicates might cover some of the ground for ISSUE-21 (affordances).

Difference between revisions of "ISSUE-37" - Linked Data Platform


Input: [Model Aspect] Interacting with container members [Linked Data Platform (LDP)]

Output: Members are listed when GETting a container, and their data is exposed through regular RDF mechanisms. If members are editable, a client can introspect via HEAD/OPTIONs to see if PUT, PATCH or DELETE verbs are permitted. A server may provide some member data or just a reference to it in the response of a request for container information.

Difference between revisions of "ISSUE-37" - Linked Data Platform


Input: [Model Aspect] Interacting with containers (composition) [Linked Data Platform (LDP)]

Output: Bringing into existence: typically containers just exist, though some servers may allow creation of containers by POSTing a representation of a container to an already-existing container. Removing from existence (DELETEing): containers are like any other HTTP web resource, they have a URI which a server may accept a DELETE request on. The question becomes, what happens to the members when a container is DELETEd? Based on resolution for ISSUE-25, in order for the container to be deleted all its members must also be deleted. There have been proposals for another model of containers, which may or may not have this rule, see ISSUE-34. Removing a member from a container: simply update the container's membership by PATCHing it with a statement to remove the membership triple. The resource still exists, its ownership is unknown (or perhaps a concept of a "default" container?). Adding an existing member to a container: potentially not allowed (ISSUE-25 resolution) Moving a member from one container to another: potentially not allowed (ISSUE-25 resolution) Alternative: PATCH to remove a member is not allowed; the client must DELETE the member to remove it from the container.

Difference between revisions of "ISSUE-37" - Linked Data Platform


Input: [Comments] PDF provides support for language identification for documents. The ISO 32000-1 PDF Specification details language support in section 14.9.2. Test results: Test id 16 (document with non-English default language) [Checkpoint]

Output: 3.1.1 Language of Page: The default human language of each Web page can be programmatically determined. (Level A)

Accessibility Support Documentation for PDF

Guideline 3.1 Readable: Make text content readable and understandable


Input: [Comments] PDF provides support for language identification for parts of documents. Test results: Test id 17 (Document with English primary language which includes Spanish phrases) [Checkpoint]

Output: 3.1.2 Language of Parts: The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. (Level AA)

Accessibility Support Documentation for PDF


Input: [Comments] No Accessibility Support impact. PDF document authors can provide a link to a definition of unusual words or phrases. [Checkpoint]

Output: 3.1.3 Unusual Words: A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon. (Level AAA)

Accessibility Support Documentation for PDF


Input: [Comments] PDF document authors can provide an explanation for abbreviations either by providing the expanded form immediately following the first instance of the abbreviation, by linking to a definition of the abbreviation, or by providing expansion text as a text equivalent to the abbreviation text. PDF supports abbreviations in tagged PDF by using a span and an abbreviation property. The ISO 32000-1 PDF Specification details abbreviation support in section 14.9.5. Test results: Test id 18 (Markup abbreviations in PDF tags) [Checkpoint]

Output: 3.1.4 Abbreviations: A mechanism for identifying the expanded form or meaning of abbreviations is available. (Level AAA)

Accessibility Support Documentation for PDF


Input: [Comments] No Accessibility Support impact. This is design-specific. Application or document authors need to consider this provision and ensure conformance. [Checkpoint]

Output: 3.1.5 Reading Level: When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available. (Level AAA)

Accessibility Support Documentation for PDF


Input: [Comments] PDF documents support this success criteria when document authors provide pronunciation information using general techniques: G120: Providing the pronunciation immediately following the word G121: Linking to pronunciations G62: Providing a glossary [Checkpoint]

Output: 3.1.6 Pronunciation: A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation. (Level AAA)

Accessibility Support Documentation for PDF


Input: [Name] target [Required] true [Type] ECMAScript Expression [Default Value] none [Valid Values] A valid target URL [Description]

Output: 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 should send the event to.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] targettype [Required] false [Type] ECMAScript Expression [Default Value] ccxml [Valid Values] ccxml dialog [Description]

Output: An ECMAScript expression which returns a character string that specifies the type of the Event I/O Processor that the event should be dispatched to. Values defined by the specification are: ccxml This species that the event will be dispatched to the CCXML Session Event Processor.. dialog This species that the event will be dispatched to the Dialog Event Processor..

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] sendid [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 will receive an internally generated unique string identifier to be associated with the event being sent. If this attribute is not specified, the event identifier is dropped.

Voice Browser Call Control: CCXML Version 1.0