Input: [Attribute Name] connection [Required] true [Type] ECMAScript Object [Details]

Output: An ECMAScript object reference to the Connection object identified by the connectionid property of this event.

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 Platform 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. The value is platform dependent as this is an event generated by the Platform Event I/O processor.

Voice Browser Call Control: CCXML Version 1.0


Input: [PersonName.] Prefix [Type] Text [Short display name] Name Prefix [Category]

Output: Demographic and SocioEconomic Data


Input: [PersonName.] First [Type] Text [Short display name] First Name [Category]

Output: Physical Contact Information


Input: [PersonName.] Last [Type] Text [Short display name] Last Name [Category]

Output: Physical Contact Information


Input: [PersonName.] Middle [Type] Text [Short display name] Middle Name [Category]

Output: Physical Contact Information


Input: [PersonName.] Suffix [Type] Text [Short display name] Name Suffix [Category]

Output: Demographic and SocioEconomic Data


Input: [PersonName.] Nickname [Type] Text [Short display name] Nickname [Category]

Output: Demographic and SocioEconomic Data


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

Output: error.conference.join

Voice Browser Call Control: CCXML Version 1.0


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

Output: The ID of the Connection, Conference or Dialog representing a resource associated with this event.

Voice Browser Call Control: CCXML Version 1.0


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

Output: The ID of the Connection, Conference or Dialog representing a resource associated with this event.

Voice Browser Call Control: CCXML Version 1.0


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

Output: A description of the reason the operation 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 Platform 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. The value is platform dependent as this is an event generated by the Platform Event I/O processor.

Voice Browser Call Control: CCXML Version 1.0


Input: [Property] type [Type] xs:string [Value]

Output: The name of the event.

XPath Expressions Module - W3C XForms Group Wiki (Public)


Input: [Property] bubbles [Type] xs:boolean [Value]

Output: Indicates whether or not an event is a bubbling event. If the event can bubble the value is true, else the value is false.

XPath Expressions Module - W3C XForms Group Wiki (Public)


Input: [Property] cancelable [Type] xs:boolean [Value]

Output: Indicates whether or not an event can have its default action prevented. If the default action can be prevented the value is true, else the value is false.

XPath Expressions Module - W3C XForms Group Wiki (Public)


Input: [Property] targetid [Type] xs:string? [Value]

Output: The id of the target to which the event was originally dispatched. If the target does not have an id an empty sequence is returned.

XPath Expressions Module - W3C XForms Group Wiki (Public)


Input: [Property] current-targetid [Type] xs:string? [Value]

Output: The id of the target whose EventListeners are currently being processed. If that target does not have an id an empty sequence is returned.

XPath Expressions Module - W3C XForms Group Wiki (Public)


Input: [Property] event-phase [Type] xs:string [Value]

Output: The current event phase: capture, target, or bubbling (When the event arrives at the target, the value is 'target'. Values capture and bubbling are as described in XML events)

XPath Expressions Module - W3C XForms Group Wiki (Public)


Input: [Property] time-stamp [Type] xs:integer? [Value]

Output: The time (in milliseconds relative to the epoch) at which the event was created. Due to the fact that some systems may not provide this information the value of timeStamp may be not available for all events. When not available, an empty sequence will be returned. Examples of epoch time are the time of the system start or 0:0:0 UTC 1st January 1970.

XPath Expressions Module - W3C XForms Group Wiki (Public)


Input: [Attribute Name] name [Type] string [Details] dialog.prepared [Required]

Output: true

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] dialogid [Type] string [Details] The ID of the dialog. [Required]

Output: true

Voice Browser Call Control: CCXML Version 1.0


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

Output: true

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] connectionid [Type] string [Details] The identifier of the connection to which the dialog connection is prepared (usually the connectionid that was specified in the dialogprepare). If the dialog was prepared without a connection, the value must be undefined. [Required]

Output: false

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] conferenceid [Type] string [Details] The identifier of the conference to which the dialog connection is prepared (usually the conferenceid that was specified in the dialogprepare). If the dialog was prepared without a conferece, the value must be undefined. [Required]

Output: false

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 DIALOG 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. This must be set to dialog as this is an event generated by the Dialog Session Event processor. [Required]

Output: true

Voice Browser Call Control: CCXML Version 1.0


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

Output: error.notallowed

Voice Browser Call Control: CCXML Version 1.0


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

Output: The ID of the affected session.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] connectionid [Required] false [Type] string [Details]

Output: The ID, if specified in the element being executed, of the affected connection or conference.

Voice Browser Call Control: CCXML Version 1.0


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

Output: A description of the reason the operation was denied. 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 or Platform 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 if this event is generated by the CCXML Session Event processor. If the event is generated by the platform, the value will be platform dependent.

Voice Browser Call Control: CCXML Version 1.0


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

Output: This property must be set to the ECMAScript string value of the name of the element that produced the error (ie accept, reject, etc).

Voice Browser Call Control: CCXML Version 1.0


Input: [PersonName.] Prefix [Category] Demographic and SocioEconomic Data [Type] Text [Short display name]

Output: Name Prefix


Input: [PersonName.] First [Category] Physical Contact Information [Type] Text [Short display name]

Output: First Name


Input: [PersonName.] Last [Category] Physical Contact Information [Type] Text [Short display name]

Output: Last Name


Input: [PersonName.] Middle [Category] Physical Contact Information [Type] Text [Short display name]

Output: Middle Name


Input: [PersonName.] Suffix [Category] Demographic and SocioEconomic Data [Type] Text [Short display name]

Output: Name Suffix


Input: [PersonName.] Nickname [Category] Demographic and SocioEconomic Data [Type] Text [Short display name]

Output: Nickname


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

Output: error.dialog.wrongstate

Voice Browser Call Control: CCXML Version 1.0


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

Output: The ID of the dialog.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] dialog [Required] true [Type] ECMAScript Object [Details]

Output: An ECMAScript object reference to the dialog object identified by the dialogid property of this event.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] connectionid [Required] false [Type] string [Details]

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] conferenceid [Required] false [Type] string [Details]

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

Voice Browser Call Control: CCXML Version 1.0


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

Output: A description of the reason the dialog is in the wrong state. 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 DIALOG 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 dialog as this is an event generated by the Dialog Session Event processor.

Voice Browser Call Control: CCXML Version 1.0


Input: [0] Parameter [1] Type [2]

Output: Description


Input: [0] AutoAdvance [1] boolean [2]

Output: If set to true, forces the list to advance automatically to the next item if there is no response from the user


Input: [0] Browsable [1] Browsable [2]

Output: Object providing access to items to be browsed


Input: [0] ExitPrompt [1] Playable [2]

Output: Prompt played when the list exits


Input: [0] FirstPrePrompt [1] Playable [2]

Output: The pre-prompt played before the first item


Input: [0] Grammar [1] Grammar [2]

Output: The grammar used for both preamble and list item recognitions


Input: [0] LastPrePrompt [1] Playable [2]

Output: The pre-prompt played before the last item


Input: [0] ListNoSpeechTimeoutPrompt [1] Playable [2]

Output: The prompt played if there is a "no-speech" timeout when the user says a command after the list item


Input: [0] ListRecognizerTooSlowTimeoutPrompt [1] Playable [2]

Output: The prompt played if there is a "recognizer-too-slow" timeout when the user says a command after the list item


Input: [0] ListRejectedPrompt [1] Playable [2]

Output: The prompt played if there is a rejection when the user says a command after the list item


Input: [0] ListSpeechTooEarlyPrompt [1] Playable [2]

Output: The prompt played if there is a "speech-too-early" condition when the user says a command after the list item


Input: [0] ListTooMuchSpeechTimeoutPrompt [1] Playable [2]

Output: The prompt played if there is a "too-much-speech" timeout when the user says a command after the list item


Input: [0] ListUnexpectedKeyPrompt [1] Playable [2]

Output: The prompt played if the user presses a dtmf key instead of speaking a command after the list item


Input: [0] MultiItemListErrorPrompt [1] Playable [2]

Output: The recognition error prompt when the list has more than one item


Input: [0] MultiItemListHelpPrompt [1] Playable [2]

Output: The help prompt when the list has more than one item


Input: [0] NextPrePrompt [1] Playable [2]

Output: The pre-prompt played when the user says "next", or when the list auto-advances to the next item


Input: [0] OnlyItemListErrorPrompt [1] Playable [2]

Output: The recognition error prompt when the list has only one item


Input: [0] OnlyItemListHelpPrompt [1] Playable [2]

Output: The help prompt when the list has only one item


Input: [0] OnlyItemPrePrompt [1] Playable [2]

Output: The pre-prompt played when there is only one item


Input: [0] PreambleHelpPrompt [1] Playable [2]

Output: The prompt played if the user asks for help during the preamble


Input: [0] PreamblePrompt [1] Playable [2]

Output: The prompt that is played only once when the user first enters the list


Input: [0] PreambleRecognitionErrorPrompt [1] Playable [2]

Output: The prompt played if there is a recognition error in the preamble


Input: [0] PreviousPrePrompt [1] Playable [2]

Output: The pre-prompt played when the user says "previous"


Input: [0] ReturnAtEnd [1] boolean [2]

Output: If true, list will automatically exit when it reaches the end


Input: [Value] 7 [Description] User agents must use this code when attempting to write to a file which cannot be modified due to the state of the underlying filesystem. [Name]

Output: NO_MODIFICATION_ALLOWED_ERR


Input: [Value] 8 [Description] User agents must use this code if: the directory containing the file to be written could not be found at the time the write was processed. the file to be written does not exist at the time the write was processed, and an offset other than zero is specified. [Name]

Output: NOT_FOUND_ERR


Input: [Value] 11 [Description] User agents must use this code if an application attempts to initiate a write, truncate, or seek using a FileWriter which is already in the WRITING state. [Name]

Output: INVALID_STATE_ERR


Input: [Value] 12 [Description] User agents must use this code when an application attempts to supply an invalid line ending specifier to the API. [Name]

Output: SYNTAX_ERR


Input: [Value] 18 [Description] User agents may use this code if: it is determined that certain files are unsafe for access within a Web application it is determined that too many write calls are being made on file resources it is determined that the file has changed on disk since the user selected it This is a security error code to be used in situations not covered by any other error codes. [Name]

Output: SECURITY_ERR


Input: [Value] 20 [Description] User agents must use this code if the read operation was aborted, typically with a call to abort(). [Name]

Output: ABORT_ERR


Input: [Title] Valid copyright Element With One No Language Tagged text Element [Assertion]

Output: The copyright element matches the schema. It contains one text element that does not have a language tag. This should be linked to a testable assertion in the spec.


Input: [Title] Valid copyright Element With One Language Tagged text Element [Assertion]

Output: The copyright element matches the schema. It contains one text element that has a language tag. This should be linked to a testable assertion in the spec.


Input: [Title] Valid copyright Element With Mixed text Element Language Tags 1 [Assertion]

Output: The copyright element matches the schema. One text element does not have a language tag. One text element has a language tag. This should be linked to a testable assertion in the spec.


Input: [Title] Valid copyright Element With Mixed text Element Language Tags 2 [Assertion]

Output: The copyright element matches the schema. Two text elements have a language tags. This should be linked to a testable assertion in the spec.


Input: [Title] More Than One copyright Element [Assertion]

Output: The copyright element occurs more than once. This should be linked to a testable assertion in the spec.


Input: [Title] No text Element in copyright Element [Assertion]

Output: The copyright element does not contain a text child element. This should be linked to a testable assertion in the spec.


Input: [Title] Unknown Attribute in copyright Element [Assertion]

Output: The copyright element contains an unknown attribute. This should be linked to a testable assertion in the spec.


Input: [Title] Unknown Child Element in copyright Element [Assertion]

Output: The copyright element contains an unknown child element. This should be linked to a testable assertion in the spec.


Input: [Title] Content in copyright Element [Assertion]

Output: The copyright element contains content. This should be linked to a testable assertion in the spec.


Input: [Title] Unknown Attribute in copyright Element text Element [Assertion]

Output: The copyright element contains a text element with an unknown attribute. This should be linked to a testable assertion in the spec.


Input: [Title] Unknown Child Element in copyright Element text Element [Assertion]

Output: The copyright element contains a text element with an unknown child element. This should be linked to a testable assertion in the spec.


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

Output: dialog.exit

Voice Browser Call Control: CCXML Version 1.0


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

Output: The ID of the dialog.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] dialog [Required] true [Type] ECMAScript Object [Details]

Output: An ECMAScript object reference to the dialog object identified by the dialogid property of this event.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] connectionid [Required] false [Type] string [Details]

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] conferenceid [Required] false [Type] string [Details]

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] namelist [Required] false [Type] string valued array [Details]

Output: If the namelist attribute was specified in the Dialog's exit element, this property must be a string valued array of the names in the list. The length of the property must be equal to the number of names in the list. The actual values are stored in the "values" sub-object.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] values.* [Required] false [Type] ECMAScript Object [Details]

Output: Each name in the namelist is a property whose value must be the value of the name at the time the Dialog's exit element was executed. Return values from the dialog. In VoiceXML this would be the values of each of the objects listed in the exit element's namelist.

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 DIALOG 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 dialog as this is an event generated by the Dialog Session Event processor.

Voice Browser Call Control: CCXML Version 1.0


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

Output: conference.joined

Voice Browser Call Control: CCXML Version 1.0


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

Output: The ID of the Connection, Conference or Dialog representing a resource associated with this event.

Voice Browser Call Control: CCXML Version 1.0


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

Output: The ID of the Connection, Conference or Dialog representing a resource associated with this event.

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 Platform 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. The value is platform dependent as this is an event generated by the Platform Event I/O processor.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] name [Required] true [Details] connection.progressing [Type]

Output: string

Voice Browser Call Control: CCXML Version 1.0


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

Output: string

Voice Browser Call Control: CCXML Version 1.0


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

Output: string

Voice Browser Call Control: CCXML Version 1.0


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

Output: ECMAScript Object

Voice Browser Call Control: CCXML Version 1.0


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

Output: ECMAScript Object

Voice Browser Call Control: CCXML Version 1.0


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

Output: string

Voice Browser Call Control: CCXML Version 1.0


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

Output: string

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] eventsourcetype [Required] true [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. [Type]

Output: string

Voice Browser Call Control: CCXML Version 1.0


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

Output: UIEvent


Input: [Event Type] DOMAttrModified [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [Cancelable] No [Default Action] None [DOM interface]

Output: MutationEvent


Input: [Event Type] DOMCharacterDataModified [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Text, Comment, ProcessingInstruction [Cancelable] No [Default Action] None [DOM interface]

Output: MutationEvent


Input: [Event Type] DOMFocusIn [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Window, Element [Cancelable] No [Default Action] None [DOM interface]

Output: FocusEvent


Input: [Event Type] DOMFocusOut [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Window, Element [Cancelable] No [Default Action] None [DOM interface]

Output: FocusEvent


Input: [Event Type] DOMNodeInserted [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element, Attr, Text, Comment, DocumentType, ProcessingInstruction [Cancelable] No [Default Action] None [DOM interface]

Output: MutationEvent


Input: [Event Type] DOMNodeInsertedIntoDocument [Sync / Async] Sync [Bubbling phase] No [Trusted event target types] Element, Attr, Text, Comment, DocumentType, ProcessingInstruction [Cancelable] No [Default Action] None [DOM interface]

Output: MutationEvent


Input: [Event Type] DOMNodeRemoved [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element, Attr, Text, Comment, DocumentType, ProcessingInstruction [Cancelable] No [Default Action] None [DOM interface]

Output: MutationEvent


Input: [Event Type] DOMNodeRemovedFromDocument [Sync / Async] Sync [Bubbling phase] No [Trusted event target types] Element, Attr, Text, Comment, DocumentType, ProcessingInstruction [Cancelable] No [Default Action] None [DOM interface]

Output: MutationEvent


Input: [Event Type] DOMSubtreeModified [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Window, Document, DocumentFragment, Element, Attr [Cancelable] No [Default Action] None [DOM interface]

Output: MutationEvent


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

Output: KeyboardEvent


Input: [Test Case] F.1.a [Link To Spec] F.1 [XForms-Basic?] true [Normative?] false [Description]

Output: enabled and disabled pseudo classes


Input: [Test Case] F.1.b [Link To Spec] F.1 [XForms-Basic?] true [Normative?] false [Description]

Output: required and optional pseudo classes


Input: [Test Case] F.1.c [Link To Spec] F.1 [XForms-Basic?] true [Normative?] false [Description]

Output: valid and invalid pseudo classes


Input: [Test Case] F.1.d [Link To Spec] F.1 [XForms-Basic?] true [Normative?] false [Description]

Output: read-only and read-write pseudo classes


Input: [Test Case] F.1.e [Link To Spec] F.1 [XForms-Basic?] true [Normative?] false [Description]

Output: out-of-range and in-range pseudo classes


Input: [Test Case] F.2.a [Link To Spec] F.2 [XForms-Basic?] true [Normative?] false [Description]

Output: value pseudo elements


Input: [Test Case] F.2.b [Link To Spec] F.2 [XForms-Basic?] true [Normative?] false [Description]

Output: repeat-item pseudo elements


Input: [Test Case] F.2.c [Link To Spec] F.2 [XForms-Basic?] true [Normative?] false [Description]

Output: repeat-index pseudo elements


Input: [Test Case] F.2.d [Link To Spec] F.2 [XForms-Basic?] true [Normative?] false [Description]

Output: repeat-index and repeat-item pseudo elements


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

Output: Hidden


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

Output: Text


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

Output: Search


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

Output: Telephone


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

Output: URL


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

Output: E-mail


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

Output: Password


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

Output: Date


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

Output: Time


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

Output: Number


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

Output: Range


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

Output: Color


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

Output: Checkbox


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

Output: Radio Button


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

Output: File Upload


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

Output: Submit Button


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

Output: Image Button


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

Output: Reset Button


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

Output: Button


Input: [EXI Option] alignment [Description] Alignment of event codes and content items [Default Value]

Output: bit-packed

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)

Table 5-1. EXI Options in Options Document


Input: [EXI Option] compression [Description] EXI compression is used to achieve better compactness [Default Value]

Output: false

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [EXI Option] strict [Description] Strict interpretation of schemas is used to achieve better compactness [Default Value]

Output: false

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [EXI Option] fragment [Description] Body is encoded as an EXI fragment instead of an EXI document [Default Value]

Output: false

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [EXI Option] preserve [Description] Specifies whether the support for the preservation of comments, pis, etc. is each enabled [Default Value]

Output: all false

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [EXI Option] selfContained [Description] Enables self-contained elements [Default Value]

Output: false

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [EXI Option] schemaId [Description] Identify the schema information, if any, used to encode the body [Default Value]

Output: no default value

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [EXI Option] datatypeRepresentationMap [Description] Specify alternate datatype representations for typed values in the EXI body [Default Value]

Output: no default value

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [EXI Option] blockSize [Description] Specifies the block size used for EXI compression [Default Value]

Output: 1,000,000

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [EXI Option] valueMaxLength [Description] Specifies the maximum string length of value content items to be considered for addition to the string table. [Default Value]

Output: unbounded

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [EXI Option] valuePartitionCapacity [Description] Specifies the total capacity of value partitions in a string table [Default Value]

Output: unbounded

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [EXI Option] [user defined meta-data] [Description] User defined meta-data may be added [Default Value]

Output: no default value

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [Part] EventClass [Type] Element [Applies] Globally [Description]

Output: Specifies a class of events that span a simulation or simulations.

SRML - Simulation Reference Markup Language


Input: [Part] Events [Type] Element [Applies] Items [Description]

Output: Specifies a collection of events scheduled or posted for an item.

SRML - Simulation Reference Markup Language


Input: [Part] EventSink [Type] Element [Applies] Globally [Description]

Output: Specifies a name and filter for events to be received by an item simulation.

SRML - Simulation Reference Markup Language


Input: [Part] Item [Type] Element [Applies] Globally [Description]

Output: Specifies an item. This is implied by elements in a domain-specific schema and need not be specified.

SRML - Simulation Reference Markup Language


Input: [Part] ItemClass [Type] Element [Applies] Globally [Description]

Output: Specifies a class of items, which all have a similar structure and behavior.

SRML - Simulation Reference Markup Language


Input: [Part] ItemClasses [Type] Element [Applies] Globally [Description]

Output: Specifies a group of item classes.

SRML - Simulation Reference Markup Language


Input: [Part] ItemEvent [Type] Element [Applies] Events [Description]

Output: Specifies the information about an event that has been scheduled or posted to an item.

SRML - Simulation Reference Markup Language


Input: [Part] JavaScript or text/javascript [Type] Value [Applies] Script Language or Type [Description]

Output: Specifies that the script language for an item is JavaScript.

SRML - Simulation Reference Markup Language


Input: [Part] Link [Type] Element [Applies] Items [Description]

Output: Specifies a link (object reference) to another Item.

SRML - Simulation Reference Markup Language


Input: [Part] Links [Type] Element [Applies] Items [Description]

Output: Specifies a collection of individual links.

SRML - Simulation Reference Markup Language


Input: [Part] LocationFixed [Type] Attribute [Applies] Items [Description]

Output: Specifies that an item is fixed within its location. This makes the item directly accessible to the location through either its ID or its Name whichever takes precedence. If two items have the same ID or name, the last one will become the item that is directly accessible. For example, if "itemname" is location fixed, then it can be accessed through location.itemname.

SRML - Simulation Reference Markup Language


Input: [Part] Name [Type] Attribute [Applies] Items, ItemClasses [Description]

Output: Designates the name for the Item or ItemClass. Name is required for an ItemClass, but not for an Item.

SRML - Simulation Reference Markup Language


Input: [Part] Parameter [Type] Element [Applies] ItemEvent [Description]

Output: Specifies an individual event parameter.

SRML - Simulation Reference Markup Language


Input: [Part] Quantity [Type] Attribute [Applies] Items [Description]

Output: Specifies the number of items to be constructed at the enclosing location.

SRML - Simulation Reference Markup Language


Input: [Part] Script [Type] Attribute [Applies] Items, ItemClasses [Description]

Output: Specifies the script, which defines the state and behavior for items.

SRML - Simulation Reference Markup Language


Input: [Part] Simulation [Type] Element [Applies] Globally [Description]

Output: Specifies an individual simulation.

SRML - Simulation Reference Markup Language


Input: [Part] Simulations [Type] Element [Applies] Globally [Description]

Output: Specifies a group of simulations.

SRML - Simulation Reference Markup Language


Input: [Part] Source [Type] Attribute [Applies] Globally [Description]

Output: Specifies the location of a document or object class that provides an external source of structure and/or behavior for an item.

SRML - Simulation Reference Markup Language


Input: [Part] SuperClasses [Type] Attribute [Applies] ItemClass [Description]

Output: Specifies an ordered sequence of ItemClasses or EventClasses that provide default structure and behavior for the ItemClass or EventClass respectively. Entries specified to the left of other entries have higher priority.

SRML - Simulation Reference Markup Language


Input: [Part] Target [Type] Attribute [Applies] Link [Description]

Output: Specifies the target object of the link.

SRML - Simulation Reference Markup Language


Input: [Part] Type [Type] Attribute [Applies] Script [Description]

Output: Specifies the language that the script uses. The Language attribute is also allowed; however, only one needs to be specified.

SRML - Simulation Reference Markup Language


Input: [Part] VBScript or text/vbscript [Type] Value [Applies] Script Language or Type [Description]

Output: Specifies that the script language is VBScript.

SRML - Simulation Reference Markup Language


Input: [Expected Values] annotations [Description]

Output: The work includes annotations from the author, instructor and/or others.


Input: [Expected Values] bookmarks [Description]

Output: The work includes bookmarks to facilitate navigation to key points.


Input: [Expected Values] index [Description]

Output: The work includes an index to the content.


Input: [Expected Values] printPageNumbers [Description]

Output: The work includes equivalent print page numbers. This setting is most commonly used with ebooks for which there is a print equivalent.


Input: [Expected Values] readingOrder [Description]

Output: The reading order of the content is clearly defined in the markup (e.g., figures, sidebars and other secondary content has been marked up to allow it to be skipped automatically and/or manually escaped from.


Input: [Expected Values] structuralNavigation [Description]

Output: The use of headings in the work fully and accurately reflects the document hierarchy, allowing navigation by assistive technologies.


Input: [Expected Values] taggedPDF [Description]

Output: The structures in a PDF have been tagged to improve the navigation of the content.


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: [Date.] Year [Category] Demographic and SocioEconomic Data [Type] Number [Short display name]

Output: Year


Input: [Date.] Month [Category] Demographic and SocioEconomic Data [Type] Number [Short display name]

Output: Month


Input: [Date.] Day [Category] Demographic and SocioEconomic Data [Type] Number [Short display name]

Output: Day


Input: [Date.] Hour [Category] Demographic and SocioEconomic Data [Type] Number [Short display name]

Output: Hour


Input: [Date.] Minute [Category] Demographic and SocioEconomic Data [Type] Number [Short display name]

Output: Minute


Input: [Date.] Second [Category] Demographic and SocioEconomic Data [Type] Number [Short display name]

Output: Second


Input: [Date.] FractionSecond [Category] Demographic and SocioEconomic Data [Type] Number [Short display name]

Output: Fraction of Second


Input: [Date.] TimeZone [Category] Demographic and SocioEconomic Data [Type] Text [Short display name]

Output: Time Zone


Input: [Code] 0 [Situation]

Output: The transaction failed for reasons unrelated to the database itself and not covered by any other error code.


Input: [Code] 1 [Situation]

Output: The statement failed for database reasons not covered by any other error code.


Input: [Code] 2 [Situation]

Output: The statement failed because the expected version of the database didn't match the actual database version.


Input: [Code] 3 [Situation]

Output: The statement failed because the data returned from the database was too large. The SQL "LIMIT" modifier might be useful to reduce the size of the result set.


Input: [Code] 4 [Situation]

Output: The statement failed because there was not enough remaining storage space, or the storage quota was reached and the user declined to give more space to the database.


Input: [Code] 5 [Situation]

Output: The statement failed because the transaction's first statement was a read-only statement, and a subsequent statement in the same transaction tried to modify the database, but the transaction failed to obtain a write lock before another transaction obtained a write lock and changed a part of the database that the former transaction was dependending depending upon.


Input: [Code] 6 [Situation]

Output: An INSERT , UPDATE , or REPLACE statement failed due to a constraint failure. For example, because a row was being inserted and the value given for the primary key column duplicated the value of an existing row.


Input: [Part] EventClass [Type] Element [Description] Specifies a class of events that span a simulation or simulations. [Applies]

Output: Globally

SRML - Simulation Reference Markup Language


Input: [Part] Events [Type] Element [Description] Specifies a collection of events scheduled or posted for an item. [Applies]

Output: Items

SRML - Simulation Reference Markup Language


Input: [Part] EventSink [Type] Element [Description] Specifies a name and filter for events to be received by an item simulation. [Applies]

Output: Globally

SRML - Simulation Reference Markup Language


Input: [Part] Item [Type] Element [Description] Specifies an item. This is implied by elements in a domain-specific schema and need not be specified. [Applies]

Output: Globally

SRML - Simulation Reference Markup Language


Input: [Part] ItemClass [Type] Element [Description] Specifies a class of items, which all have a similar structure and behavior. [Applies]

Output: Globally

SRML - Simulation Reference Markup Language


Input: [Part] ItemClasses [Type] Element [Description] Specifies a group of item classes. [Applies]

Output: Globally

SRML - Simulation Reference Markup Language


Input: [Part] ItemEvent [Type] Element [Description] Specifies the information about an event that has been scheduled or posted to an item. [Applies]

Output: Events

SRML - Simulation Reference Markup Language


Input: [Part] JavaScript or text/javascript [Type] Value [Description] Specifies that the script language for an item is JavaScript. [Applies]

Output: Script Language or Type

SRML - Simulation Reference Markup Language


Input: [Part] Link [Type] Element [Description] Specifies a link (object reference) to another Item. [Applies]

Output: Items

SRML - Simulation Reference Markup Language


Input: [Part] Links [Type] Element [Description] Specifies a collection of individual links. [Applies]

Output: Items

SRML - Simulation Reference Markup Language


Input: [Part] LocationFixed [Type] Attribute [Description] Specifies that an item is fixed within its location. This makes the item directly accessible to the location through either its ID or its Name whichever takes precedence. If two items have the same ID or name, the last one will become the item that is directly accessible. For example, if "itemname" is location fixed, then it can be accessed through location.itemname. [Applies]

Output: Items

SRML - Simulation Reference Markup Language


Input: [Part] Name [Type] Attribute [Description] Designates the name for the Item or ItemClass. Name is required for an ItemClass, but not for an Item. [Applies]

Output: Items, ItemClasses

SRML - Simulation Reference Markup Language


Input: [Part] Parameter [Type] Element [Description] Specifies an individual event parameter. [Applies]

Output: ItemEvent

SRML - Simulation Reference Markup Language


Input: [Part] Quantity [Type] Attribute [Description] Specifies the number of items to be constructed at the enclosing location. [Applies]

Output: Items

SRML - Simulation Reference Markup Language


Input: [Part] Script [Type] Attribute [Description] Specifies the script, which defines the state and behavior for items. [Applies]

Output: Items, ItemClasses

SRML - Simulation Reference Markup Language


Input: [Part] Simulation [Type] Element [Description] Specifies an individual simulation. [Applies]

Output: Globally

SRML - Simulation Reference Markup Language


Input: [Part] Simulations [Type] Element [Description] Specifies a group of simulations. [Applies]

Output: Globally

SRML - Simulation Reference Markup Language


Input: [Part] Source [Type] Attribute [Description] Specifies the location of a document or object class that provides an external source of structure and/or behavior for an item. [Applies]

Output: Globally

SRML - Simulation Reference Markup Language


Input: [Part] SuperClasses [Type] Attribute [Description] Specifies an ordered sequence of ItemClasses or EventClasses that provide default structure and behavior for the ItemClass or EventClass respectively. Entries specified to the left of other entries have higher priority. [Applies]

Output: ItemClass

SRML - Simulation Reference Markup Language


Input: [Part] Target [Type] Attribute [Description] Specifies the target object of the link. [Applies]

Output: Link

SRML - Simulation Reference Markup Language


Input: [Part] Type [Type] Attribute [Description] Specifies the language that the script uses. The Language attribute is also allowed; however, only one needs to be specified. [Applies]

Output: Script

SRML - Simulation Reference Markup Language


Input: [Part] VBScript or text/vbscript [Type] Value [Description] Specifies that the script language is VBScript. [Applies]

Output: Script Language or Type

SRML - Simulation Reference Markup Language


Input: [Type] Element [Applies] Globally [Description] Specifies a class of events that span a simulation or simulations. [Part]

Output: EventClass

SRML - Simulation Reference Markup Language


Input: [Type] Element [Applies] Items [Description] Specifies a collection of events scheduled or posted for an item. [Part]

Output: Events

SRML - Simulation Reference Markup Language


Input: [Type] Element [Applies] Globally [Description] Specifies a name and filter for events to be received by an item simulation. [Part]

Output: EventSink

SRML - Simulation Reference Markup Language


Input: [Type] Element [Applies] Globally [Description] Specifies an item. This is implied by elements in a domain-specific schema and need not be specified. [Part]

Output: Item

SRML - Simulation Reference Markup Language


Input: [Type] Element [Applies] Globally [Description] Specifies a class of items, which all have a similar structure and behavior. [Part]

Output: ItemClass

SRML - Simulation Reference Markup Language


Input: [Type] Element [Applies] Globally [Description] Specifies a group of item classes. [Part]

Output: ItemClasses

SRML - Simulation Reference Markup Language


Input: [Type] Element [Applies] Events [Description] Specifies the information about an event that has been scheduled or posted to an item. [Part]

Output: ItemEvent

SRML - Simulation Reference Markup Language


Input: [Type] Value [Applies] Script Language or Type [Description] Specifies that the script language for an item is JavaScript. [Part]

Output: JavaScript or text/javascript

SRML - Simulation Reference Markup Language


Input: [Type] Element [Applies] Items [Description] Specifies a link (object reference) to another Item. [Part]

Output: Link

SRML - Simulation Reference Markup Language


Input: [Type] Element [Applies] Items [Description] Specifies a collection of individual links. [Part]

Output: Links

SRML - Simulation Reference Markup Language


Input: [Type] Attribute [Applies] Items [Description] Specifies that an item is fixed within its location. This makes the item directly accessible to the location through either its ID or its Name whichever takes precedence. If two items have the same ID or name, the last one will become the item that is directly accessible. For example, if "itemname" is location fixed, then it can be accessed through location.itemname. [Part]

Output: LocationFixed

SRML - Simulation Reference Markup Language


Input: [Type] Attribute [Applies] Items, ItemClasses [Description] Designates the name for the Item or ItemClass. Name is required for an ItemClass, but not for an Item. [Part]

Output: Name

SRML - Simulation Reference Markup Language


Input: [Type] Element [Applies] ItemEvent [Description] Specifies an individual event parameter. [Part]

Output: Parameter

SRML - Simulation Reference Markup Language


Input: [Type] Attribute [Applies] Items [Description] Specifies the number of items to be constructed at the enclosing location. [Part]

Output: Quantity

SRML - Simulation Reference Markup Language


Input: [Type] Attribute [Applies] Items, ItemClasses [Description] Specifies the script, which defines the state and behavior for items. [Part]

Output: Script

SRML - Simulation Reference Markup Language


Input: [Type] Element [Applies] Globally [Description] Specifies an individual simulation. [Part]

Output: Simulation

SRML - Simulation Reference Markup Language


Input: [Type] Element [Applies] Globally [Description] Specifies a group of simulations. [Part]

Output: Simulations

SRML - Simulation Reference Markup Language


Input: [Type] Attribute [Applies] Globally [Description] Specifies the location of a document or object class that provides an external source of structure and/or behavior for an item. [Part]

Output: Source

SRML - Simulation Reference Markup Language


Input: [Type] Attribute [Applies] ItemClass [Description] Specifies an ordered sequence of ItemClasses or EventClasses that provide default structure and behavior for the ItemClass or EventClass respectively. Entries specified to the left of other entries have higher priority. [Part]

Output: SuperClasses

SRML - Simulation Reference Markup Language


Input: [Type] Attribute [Applies] Link [Description] Specifies the target object of the link. [Part]

Output: Target

SRML - Simulation Reference Markup Language


Input: [Type] Attribute [Applies] Script [Description] Specifies the language that the script uses. The Language attribute is also allowed; however, only one needs to be specified. [Part]

Output: Type

SRML - Simulation Reference Markup Language


Input: [Type] Value [Applies] Script Language or Type [Description] Specifies that the script language is VBScript. [Part]

Output: VBScript or text/vbscript

SRML - Simulation Reference Markup Language


Input: [Definition] Sets the background colour of the HTML element. [Description] There are several ways to indicate background-color, including RGB values and keywords. Most people use hexadecimal notation, a pound/hash symbol (#) followed by six characters. The first pair indicates the red levels, and the second and third indicate the green and blue levels respectively—#RRGGBB. Many colour picker tools will help you find the hexadecimal notation of a given colour. Pure red, for example would be #FF0000. Valid values include a color value, transparent, or inherit. [Property]

Output: background-color


Input: [Definition] Indicates the path or URL of the background image. [Description] Set the background-image by showing the browser where to find the image, using the URL. For example; url(alert.png). Note that the path is prefaced with they keyword url and wrapped in parenthesis. This syntax is important to the browser understanding that you mean to indicate a location. Valid values include a URL, none, or inherit. [Property]

Output: image


Input: [Definition] Indicates in which direction the background image should be tiled. [Description] Images can be tiled vertically, horizontally, or both, to fill the entire width or height of an HTML element. Use background-repeat to instruct the browser to repeat a background image. Valid values include repeat, repeat-x, repeat-y, and no-repeat. [Property]

Output: repeat


Input: [Definition] Sets the behaviour of the background image when the user scrolls. [Description] Images can either scroll with their content, or stay fixed in place in the view screen. Valid values include scroll, fixed, and inherit. [Property]

Output: attachment


Input: [Definition] Tells the browser where to position the background image. [Description] Images can be displayed anywhere within the borders of the HTML element on which they are applied. Use background-position to precisely place your images for visual effect and layering. There are many useful ways to indicate background position, keywords and numeric values. Keywords (such as top and bottom) are very useful and easy to read. Pixel values are very precise, but don’t adapt to changing heights and widths. Negative pixel values are useful when using CSS sprites, as you’ll find out later. When percentages and pixels are used, the starting point is always the top left corner of the HTML element, although the way image positioning works with pixels and percentages is rather different. Pixels always move the image a set number of pixels towards the bottom and right of the containing box (or towards the top and left if they are negative values), regardless of the size of the image and the containing box. Percentages on the other hand move the image a percentage of the difference between the containing box size, and the image size. If the image and the containing box are the same size, percentages won’t move the image at all. Valid values include length (generally in pixels), percentage (of the width of the element), and the keywords top, right, bottom, left, and center. Note that center can be used to indicate both vertical and horizontal center. Note also that you can mix percentages and pixels in rules, but not keywords and pixels or keywords and percentages. [Property]

Output: position


Input: [Definition] The shorthand property that can be used to describe all the other properties in one line. [Description] Shorthand properties are very nifty indeed. Most developers use them to keep the CSS as lean as possible and group related properties. You can write a general rule using shorthand, and then override it as needed with specific properties. The properties should always be indicated in the same order, to allow browsers to easily interpret the intended styles: color url repeat attachment (very rarely used; may be omitted) horizontal-position vertical-position An example of this shorthand with all the properties used (except attachment) is as follows: background: green url(logo.gif) no-repeat left top; [Property]

Output: background


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] A 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 URL [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] A text field that obscures data entry [Keyword]

Output: password


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

Output: date


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] 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: [Description] The work includes annotations from the author, instructor and/or others. [Expected Values]

Output: annotations


Input: [Description] The work includes bookmarks to facilitate navigation to key points. [Expected Values]

Output: bookmarks


Input: [Description] The work includes an index to the content. [Expected Values]

Output: index


Input: [Description] The work includes equivalent print page numbers. This setting is most commonly used with ebooks for which there is a print equivalent. [Expected Values]

Output: printPageNumbers


Input: [Description] The reading order of the content is clearly defined in the markup (e.g., figures, sidebars and other secondary content has been marked up to allow it to be skipped automatically and/or manually escaped from. [Expected Values]

Output: readingOrder


Input: [Description] The use of headings in the work fully and accurately reflects the document hierarchy, allowing navigation by assistive technologies. [Expected Values]

Output: structuralNavigation


Input: [Description] The structures in a PDF have been tagged to improve the navigation of the content. [Expected Values]

Output: taggedPDF


Input: [Category] Demographic and SocioEconomic Data [Type] Number [Short display name] Year [Date.]

Output: Year


Input: [Category] Demographic and SocioEconomic Data [Type] Number [Short display name] Month [Date.]

Output: Month


Input: [Category] Demographic and SocioEconomic Data [Type] Number [Short display name] Day [Date.]

Output: Day


Input: [Category] Demographic and SocioEconomic Data [Type] Number [Short display name] Hour [Date.]

Output: Hour


Input: [Category] Demographic and SocioEconomic Data [Type] Number [Short display name] Minute [Date.]

Output: Minute


Input: [Category] Demographic and SocioEconomic Data [Type] Number [Short display name] Second [Date.]

Output: Second


Input: [Category] Demographic and SocioEconomic Data [Type] Number [Short display name] Fraction of Second [Date.]

Output: FractionSecond


Input: [Category] Demographic and SocioEconomic Data [Type] Text [Short display name] Time Zone [Date.]

Output: TimeZone


Input: [Attribute Type] CDATA [Definition]

Output: Character data

Modularization of XHTML - XHTML Abstract Modules


Input: [Attribute Type] ID [Definition]

Output: A document-unique identifier

Modularization of XHTML - XHTML Abstract Modules


Input: [Attribute Type] IDREF [Definition]

Output: A reference to a document-unique identifier

Modularization of XHTML - XHTML Abstract Modules


Input: [Attribute Type] IDREFS [Definition]

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

Modularization of XHTML - XHTML Abstract Modules


Input: [Attribute Type] NAME [Definition]

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

Modularization of XHTML - XHTML Abstract Modules


Input: [Attribute Type] NMTOKEN [Definition]

Output: A name composed of CDATA characters but no whitespace

Modularization of XHTML - XHTML Abstract Modules


Input: [Attribute Type] NMTOKENS [Definition]

Output: Multiple names composed of CDATA characters separated by whitespace

Modularization of XHTML - XHTML Abstract Modules


Input: [Attribute Type] PCDATA [Definition]

Output: Processed character data

Modularization of XHTML - XHTML Abstract Modules


Input: [Property] background-color [Definition] Sets the background colour of the HTML element. [Description]

Output: There are several ways to indicate background-color, including RGB values and keywords. Most people use hexadecimal notation, a pound/hash symbol (#) followed by six characters. The first pair indicates the red levels, and the second and third indicate the green and blue levels respectively—#RRGGBB. Many colour picker tools will help you find the hexadecimal notation of a given colour. Pure red, for example would be #FF0000. Valid values include a color value, transparent, or inherit.


Input: [Property] image [Definition] Indicates the path or URL of the background image. [Description]

Output: Set the background-image by showing the browser where to find the image, using the URL. For example; url(alert.png). Note that the path is prefaced with they keyword url and wrapped in parenthesis. This syntax is important to the browser understanding that you mean to indicate a location. Valid values include a URL, none, or inherit.


Input: [Property] repeat [Definition] Indicates in which direction the background image should be tiled. [Description]

Output: Images can be tiled vertically, horizontally, or both, to fill the entire width or height of an HTML element. Use background-repeat to instruct the browser to repeat a background image. Valid values include repeat, repeat-x, repeat-y, and no-repeat.


Input: [Property] attachment [Definition] Sets the behaviour of the background image when the user scrolls. [Description]

Output: Images can either scroll with their content, or stay fixed in place in the view screen. Valid values include scroll, fixed, and inherit.


Input: [Property] position [Definition] Tells the browser where to position the background image. [Description]

Output: Images can be displayed anywhere within the borders of the HTML element on which they are applied. Use background-position to precisely place your images for visual effect and layering. There are many useful ways to indicate background position, keywords and numeric values. Keywords (such as top and bottom) are very useful and easy to read. Pixel values are very precise, but don’t adapt to changing heights and widths. Negative pixel values are useful when using CSS sprites, as you’ll find out later. When percentages and pixels are used, the starting point is always the top left corner of the HTML element, although the way image positioning works with pixels and percentages is rather different. Pixels always move the image a set number of pixels towards the bottom and right of the containing box (or towards the top and left if they are negative values), regardless of the size of the image and the containing box. Percentages on the other hand move the image a percentage of the difference between the containing box size, and the image size. If the image and the containing box are the same size, percentages won’t move the image at all. Valid values include length (generally in pixels), percentage (of the width of the element), and the keywords top, right, bottom, left, and center. Note that center can be used to indicate both vertical and horizontal center. Note also that you can mix percentages and pixels in rules, but not keywords and pixels or keywords and percentages.


Input: [Property] background [Definition] The shorthand property that can be used to describe all the other properties in one line. [Description]

Output: Shorthand properties are very nifty indeed. Most developers use them to keep the CSS as lean as possible and group related properties. You can write a general rule using shorthand, and then override it as needed with specific properties. The properties should always be indicated in the same order, to allow browsers to easily interpret the intended styles: color url repeat attachment (very rarely used; may be omitted) horizontal-position vertical-position An example of this shorthand with all the properties used (except attachment) is as follows: background: green url(logo.gif) no-repeat left top;


Input: [EXI Option] alignment [Default Value] bit-packed [Description]

Output: Alignment of event codes and content items

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [EXI Option] compression [Default Value] false [Description]

Output: EXI compression is used to achieve better compactness

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [EXI Option] strict [Default Value] false [Description]

Output: Strict interpretation of schemas is used to achieve better compactness

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [EXI Option] fragment [Default Value] false [Description]

Output: Body is encoded as an EXI fragment instead of an EXI document

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [EXI Option] preserve [Default Value] all false [Description]

Output: Specifies whether the support for the preservation of comments, pis, etc. is each enabled

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [EXI Option] selfContained [Default Value] false [Description]

Output: Enables self-contained elements

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [EXI Option] schemaId [Default Value] no default value [Description]

Output: Identify the schema information, if any, used to encode the body

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [EXI Option] datatypeRepresentationMap [Default Value] no default value [Description]

Output: Specify alternate datatype representations for typed values in the EXI body

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [EXI Option] blockSize [Default Value] 1,000,000 [Description]

Output: Specifies the block size used for EXI compression

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [EXI Option] valueMaxLength [Default Value] unbounded [Description]

Output: Specifies the maximum string length of value content items to be considered for addition to the string table.

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [EXI Option] valuePartitionCapacity [Default Value] unbounded [Description]

Output: Specifies the total capacity of value partitions in a string table

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [EXI Option] [user defined meta-data] [Default Value] no default value [Description]

Output: User defined meta-data may be added

Efficient XML Interchange (EXI) Format 1.0 (Second Edition)


Input: [Description] Alignment of event codes and content items [Default Value] bit-packed [EXI Option]

Output: alignment

Efficient XML Interchange (EXI) Format 1.0

Table 5-1. EXI Options in Options Field


Input: [Description] EXI compression is used to achieve better compactness [Default Value] false [EXI Option]

Output: compression

Efficient XML Interchange (EXI) Format 1.0

Table 5-1. EXI Options in Options Field


Input: [Description] Strict interpretation of schemas is used to achieve better compactness [Default Value] false [EXI Option]

Output: strict

Efficient XML Interchange (EXI) Format 1.0

Table 5-1. EXI Options in Options Field


Input: [Description] Body is encoded as an EXI fragment instead of an EXI document [Default Value] false [EXI Option]

Output: fragment

Efficient XML Interchange (EXI) Format 1.0

Table 5-1. EXI Options in Options Field


Input: [Description] Specifies whether comments, pis, etc. are preserved [Default Value] all false [EXI Option]

Output: preserve

Efficient XML Interchange (EXI) Format 1.0

Table 5-1. EXI Options in Options Field


Input: [Description] Enables self-contained elements [Default Value] false [EXI Option]

Output: selfContained

Efficient XML Interchange (EXI) Format 1.0

Table 5-1. EXI Options in Options Field


Input: [Description] Identify the schema information, if any, used to encode the body [Default Value] none [EXI Option]

Output: schemaID

Efficient XML Interchange (EXI) Format 1.0

Table 5-1. EXI Options in Options Field


Input: [Description] Identify datatype representations used to encode values in EXI body [Default Value] none [EXI Option]

Output: datatypeRepresentationMap

Efficient XML Interchange (EXI) Format 1.0

Table 5-1. EXI Options in Options Field


Input: [Description] Specifies the block size used for EXI compression [Default Value] 1,000,000 [EXI Option]

Output: blockSize

Efficient XML Interchange (EXI) Format 1.0

Table 5-1. EXI Options in Options Field


Input: [Description] Specifies the maximum string length of value content items to be considered for addition to the string table. [Default Value] unbounded [EXI Option]

Output: valueMaxLength

Efficient XML Interchange (EXI) Format 1.0

Table 5-1. EXI Options in Options Field


Input: [Description] Specifies the total capacity of value partitions in a string table [Default Value] unbounded [EXI Option]

Output: valuePartitionCapacity

Efficient XML Interchange (EXI) Format 1.0

Table 5-1. EXI Options in Options Field


Input: [Description] User defined options may be added [Default Value] none [EXI Option]

Output: [user defined]

Efficient XML Interchange (EXI) Format 1.0

Table 5-1. EXI Options in Options Field


Input: [Part] Abort [Type] Method [Applies] Simulation [Description]

Output: Aborts the running simulation.

SRML - Simulation Reference Markup Language


Input: [Part] BroadcastEvent [Type] Method [Applies] Simulation [Description]

Output: Sends, Posts, or Schedules an event to occur and cascade either upward or downward starting at a given item.

SRML - Simulation Reference Markup Language


Input: [Part] CreateItems [Type] Method [Applies] Simulation [Description]

Output: Creates a specified number of items at a particular location, based on a prototype item.

SRML - Simulation Reference Markup Language


Input: [Part] CreateTimeAverage [Type] Method [Applies] Simulation [Description]

Output: Returns a newly created TimeAverage object.

SRML - Simulation Reference Markup Language


Input: [Part] CurrentTime [Type] Property [Applies] Simulation [Description]

Output: Sets or returns the simulation's current time.

SRML - Simulation Reference Markup Language


Input: [Part] CurrentEvent [Type] Property [Applies] Simulation [Description]

Output: Returns the most recently executed event that was either posted or scheduled.

SRML - Simulation Reference Markup Language


Input: [Part] DateAdd [Type] Method [Applies] Simulation [Description]

Output: Returns the result of adding an interval number to a date.

SRML - Simulation Reference Markup Language


Input: [Part] DateDiff [Type] Method [Applies] Simulation [Description]

Output: Returns an interval difference between two dates.

SRML - Simulation Reference Markup Language


Input: [Part] DestroyItem [Type] Method [Applies] Simulation [Description]

Output: Destroys an item.

SRML - Simulation Reference Markup Language


Input: [Part] Document [Type] Property [Applies] Simulation [Description]

Output: Returns or sets the XML DOM document object.

SRML - Simulation Reference Markup Language


Input: [Part] DoNextEvent [Type] Method [Applies] Simulation [Description]

Output: Sends the next scheduled or posted event to its target.

SRML - Simulation Reference Markup Language


Input: [Part] EndTime [Type] Property [Applies] Simulation [Description]

Output: Sets or returns the end time of the simulation.

SRML - Simulation Reference Markup Language


Input: [Part] Error [Type] Property [Applies] Simulation [Description]

Output: Returns an object that contains information about the last error.

SRML - Simulation Reference Markup Language


Input: [Part] EventOccurred [Type] Event [Applies] Simulation [Description]

Output: Indicates that an event occurred in the simulation.

SRML - Simulation Reference Markup Language


Input: [Part] Extension [Type] Property [Applies] Simulation [Description]

Output: Sets or returns the simulation's extension object. This is used to allow items in the simulation to directly access the properties and methods of the extension object.

SRML - Simulation Reference Markup Language


Input: [Part] FindItems [Type] Method [Applies] Simulation [Description]

Output: Returns a collection of items found using the specified query.

SRML - Simulation Reference Markup Language


Input: [Part] Format [Type] Method [Applies] Simulation [Description]

Output: Returns the result of applying a format string to an expression.

SRML - Simulation Reference Markup Language


Input: [Part] ForwardEvent [Type] Method [Applies] Simulation [Description]

Output: Forwards the specified event to the specified object.

SRML - Simulation Reference Markup Language


Input: [Part] GetItem [Type] Method [Applies] Simulation [Description]

Output: Returns the item with the specified ItemID.

SRML - Simulation Reference Markup Language


Input: [Part] Item [Type] Method [Applies] Simulation [Description]

Output: Returns the item with the specified ItemID.

SRML - Simulation Reference Markup Language


Input: [Part] ItemCount [Type] Method [Applies] Simulation [Description]

Output: Returns the number of items in the simulation.

SRML - Simulation Reference Markup Language


Input: [Part] ItemLocationChanged [Type] Event [Applies] Simulation [Description]

Output: Indicates that an item moved to a new location, passing the item and its previous location.

SRML - Simulation Reference Markup Language


Input: [Part] Load [Type] Method [Applies] Simulation [Description]

Output: Loads the simulation items from a path or url.

SRML - Simulation Reference Markup Language


Input: [Part] LoadXML [Type] Method [Applies] Simulation [Description]

Output: Loads the simulation items from a string containing XML.

SRML - Simulation Reference Markup Language


Input: [Part] Object [Type] Property [Applies] Simulation [Description]

Output: An object that represents the Simulation Item, as created in script.

SRML - Simulation Reference Markup Language


Input: [Part] PeekEvent [Type] Method [Applies] Simulation [Description]

Output: Returns the next scheduled event.

SRML - Simulation Reference Markup Language


Input: [Part] PostEvent [Type] Method [Applies] Simulation [Description]

Output: Sends an event asynchronously to an item (or object).

SRML - Simulation Reference Markup Language


Input: [Part] Random [Type] Method [Applies] Simulation [Description]

Output: Returns a random number from a set of available distributions.

SRML - Simulation Reference Markup Language


Input: [Part] RandomSeed [Type] Method [Applies] Simulation [Description]

Output: Sets or returns the Simulation object's random seed value.

SRML - Simulation Reference Markup Language


Input: [Part] RandomizeSeed [Type] Method [Applies] Simulation [Description]

Output: Randomizes the random number generator's seed value.

SRML - Simulation Reference Markup Language


Input: [Part] ReleaseAll [Type] Method [Applies] Simulation [Description]

Output: Releases all loaded items, and returns the simulation to the condition prior to any calls to load.

SRML - Simulation Reference Markup Language


Input: [Part] Reset [Type] Method [Applies] Simulation [Description]

Output: Initializes the simulation to the state immediately following the most recent load.

SRML - Simulation Reference Markup Language


Input: [Part] RetractEvent [Type] Method [Applies] Simulation [Description]

Output: Prevents a scheduled event from occurring.

SRML - Simulation Reference Markup Language


Input: [Part] Run [Type] Method [Applies] Simulation [Description]

Output: Runs the simulation object.

SRML - Simulation Reference Markup Language


Input: [Part] ScheduleEvent [Type] Method [Applies] Simulation [Description]

Output: Schedules an event.

SRML - Simulation Reference Markup Language


Input: [Part] SendEvent [Type] Method [Applies] Simulation [Description]

Output: Sends an event synchronously to an item (or object) and returns the result.

SRML - Simulation Reference Markup Language


Input: [Part] SetItemLocation [Type] Method [Applies] Simulation [Description]

Output: Sets an item's location. This has the same effect as directly changing an item's location property.

SRML - Simulation Reference Markup Language


Input: [Part] Simulation [Type] Property [Applies] Simulation [Description]

Output: Returns the Simulation object. (This is not the same as the Object property, because the Object property has a dynamic interface.)

SRML - Simulation Reference Markup Language


Input: [Name] clip-path [Value] | [ || ] | none [Initial] none [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] as specified [Media] visual [Animatable] as specified for [CSS-SHAPES], otherwise no [Computed value]

Output: as specified, but with values made absolute


Input: [Name] clip-rule [Value] nonzero | evenodd [Initial] nonzero [Applies to] Applies to SVG graphics elements [Inh.] yes [%ages] n/a [Media] visual [Animatable] no [Computed value]

Output: as specified


Input: [Name] mask-image [Value] # [Initial] none [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value]

Output: as specified, but with URIs made absolute


Input: [Name] mask-mode [Value] # [Initial] auto [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value]

Output: as specified


Input: [Name] mask-repeat [Value] # [Initial] no-repeat [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value]

Output: Consists of: two keywords, one per dimension


Input: [Name] mask-position [Value] # [Initial] center [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] refer to size of mask painting area minus size of mask layer image; see text background-position [CSS3BG] [Media] visual [Animatable] as repeatable list of simple list of length, percentage, or calc [Computed value]

Output: Consisting of: two keywords representing the origin and two offsets from that origin, each given as an absolute length (if given a ), otherwise as a percentage.


Input: [Name] mask-clip [Value] [ | no-clip ]# [Initial] border-box [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value]

Output: as specified


Input: [Name] mask-origin [Value] # [Initial] border-box [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value]

Output: as specified


Input: [Name] mask-size [Value] # [Initial] auto [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] as repeatable list of simple list of length, percentage, or calc (This means keyword values are not animatable.) [Computed value]

Output: as specified, but with lengths made absolute


Input: [Name] mask-composite [Value] # [Initial] add [Applies to] All elements. In SVG, it applies to container elements without the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value]

Output: as specified


Input: [Name] mask [Value] # [Initial] see individual properties [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] see individual properties [Media] visual [Animatable] see individual properties [Computed value]

Output: see individual properties


Input: [Name] mask-border-source [Value] none | [Initial] none [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value]

Output: none or the image with its URI made absolute


Input: [Name] mask-border-mode [Value] luminance | alpha [Initial] alpha [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value]

Output: as specified


Input: [Name] mask-border-slice [Value] [ | ]{1,4} fill? [Initial] 0 [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] refer to size of the mask border image [Media] visual [Animatable] no [Computed value]

Output: as specified


Input: [Name] mask-border-width [Value] [ | | | auto ]{1,4} [Initial] auto [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] relative to width/height of the mask border image area [Media] visual [Animatable] no [Computed value]

Output: all s made absolute, otherwise as specified


Input: [Name] mask-border-outset [Value] [ | ]{1,4} [Initial] 0 [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value]

Output: all s made absolute, otherwise as specified


Input: [Name] mask-border-repeat [Value] [ stretch | repeat | round | space ]{1,2} [Initial] stretch [Applies to] All elements. In SVG, it applies to container elements excluding the element and all graphics elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value]

Output: as specified


Input: [Name] mask-border [Value] <‘mask-border-source’> || <‘mask-border-slice’> [ / <‘mask-border-width’>? [ / <‘mask-border-outset’> ]? ]? || <‘mask-border-repeat’> || <‘mask-border-mode’> [Initial] See individual properties [Applies to] See individual properties [Inh.] no [%ages] n/a [Media] visual [Animatable] See individual properties [Computed value]

Output: See individual properties


Input: [Name] mask-type [Value] luminance | alpha [Initial] luminance [Applies to] mask elements [Inh.] no [%ages] n/a [Media] visual [Animatable] no [Computed value]

Output: as specified


Input: [Name] clip [Value] | auto [Initial] auto [Applies to] Absolutely positioned elements. In SVG, it applies to elements which establish a new viewport, elements and mask elements. [Inh.] no [%ages] n/a [Media] visual [Animatable] as rectangle [Computed value]

Output: as specified


Input: [Attribute Type] CDATA [Definition]

Output: Character data

XHTML™ Modularization 1.1 - Second Edition


Input: [Attribute Type] ID [Definition]

Output: A document-unique identifier

XHTML™ Modularization 1.1 - Second Edition


Input: [Attribute Type] IDREF [Definition]

Output: A reference to a document-unique identifier

XHTML™ Modularization 1.1 - Second Edition


Input: [Attribute Type] IDREFS [Definition]

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

XHTML™ Modularization 1.1 - Second Edition


Input: [Attribute Type] NAME [Definition]

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

XHTML™ Modularization 1.1 - Second Edition


Input: [Attribute Type] NMTOKEN [Definition]

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

XHTML™ Modularization 1.1 - Second Edition


Input: [Attribute Type] NMTOKENS [Definition]

Output: One or more white space separated NMTOKEN values

XHTML™ Modularization 1.1 - Second Edition


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

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

Buy standards compliant Web sites — W3C QA


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

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

Buy standards compliant Web sites — W3C QA


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

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

Buy standards compliant Web sites — W3C QA


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

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

Buy standards compliant Web sites — W3C QA


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

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

Buy standards compliant Web sites — W3C QA


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

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

Buy standards compliant Web sites — W3C QA


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

Output: Web developers and content providers


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

Output: Web developers and content providers


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

Output: Web developers and content providers


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

Output: Web developers and content providers


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

Output: Web developers and content providers


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

Output: Web developers and content providers


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

Output: Web developers and content providers