Input: [Category] Presentation [4] Presentation is clear and to the point, clearly describing the project problem and proposed solution. The project plan is clearly communicated, including who is accountable for which tasks, when tasks need to be done by, how we know they are completed satisfactorily. [3] Presentation is reasonably clear and to the point, describing the project problem and proposed solution. The project plan is communicated, including who is accountable for which task, when tasks need to be done by, how we know they are completed satisfactorily. [2] Presentation is average, not very comprehensive or clear, describing the project problem and proposed solution. The project plan is communicated, including who is accountable for which tasks, when tasks need to be done by, how we know they are completed satisfactorily. [1]

Output: Presentation is long-winded, covers some description of the project problem and proposed solution but is somewhat incomplete. The project plan is communicated, but assignments, tasks timelines and quality criteria are not made clear and explicit.

Es/Interact/Gestión de proyectos - Web Education Community Group


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

Output: Meeting objectives not specific enough, items of discussion are not actionable.

Es/Interact/Gestión de proyectos - Web Education Community Group


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

Output: Meeting runs over time, not all points are covered and action points are not explicitly stated.

Es/Interact/Gestión de proyectos - Web Education Community Group


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

Output: Minutes are unclear, and not comprehensive, missing problems raised, solutions decided upon and lacking action points.

Es/Interact/Gestión de proyectos - Web Education Community Group


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

Output: Rarely provides useful ideas when participating in the group and in classroom discussion. May refuse to participate.

Es/Interact/Gestión de proyectos - Web Education Community Group


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

Output: Rarely listens to, shares with, and supports the efforts of others. Often is not a good team player.

Es/Interact/Gestión de proyectos - Web Education Community Group


Input: [Constant] UNKNOWN_ERR [Code] 0 [Situation]

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


Input: [Constant] DATABASE_ERR [Code] 1 [Situation]

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


Input: [Constant] VERSION_ERR [Code] 2 [Situation]

Output: The operation failed because the actual database version was not what it should be. For example, a statement found that the actual database version no longer matched the expected version of the Database or DatabaseSync object, or the Database.changeVersion() or DatabaseSync.changeVersion() methods were passed a version that doesn't match the actual database version.


Input: [Constant] TOO_LARGE_ERR [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: [Constant] QUOTA_ERR [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: [Constant] SYNTAX_ERR [Code] 5 [Situation]

Output: The statement failed because of a syntax error, or the number of arguments did not match the number of ? placeholders in the statement, or the statement tried to use a statement that is not allowed, such as BEGIN, COMMIT, or ROLLBACK, or the statement tried to use a verb that could modify the database but the transaction was read-only.


Input: [Constant] CONSTRAINT_ERR [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: [Constant] TIMEOUT_ERR [Code] 7 [Situation]

Output: A lock for the transaction could not be obtained in a reasonable time.


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

Output: Yes

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


Input: [Data category] Localization Note [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] None [Inheritance] Textual content of element, including content of child elements, but excluding attributes [Overriding] Yes [Local Usage]

Output: Yes

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


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

Output: Yes

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


Input: [Data category] Directionality [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] dir="ltr" [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes [Local Usage]

Output: Yes

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


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

Output: Yes

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


Input: [Data category] Language Information [Global, rule-based selection] Yes [Global adding of information] No Yes [Default Values] None [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes [Local Usage]

Output: No

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


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

Output: No

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


Input: [Arguments] name(optional) [Return Value] Success or Failure [Description] Creates a new scope object and pushes it on top of the scope stack. If no name is provided the scope is anonymous and may be accessed only when it on the top of the scope stack. A Failure status is returned if a scope already exists with the specified name. [Function]

Output: CreateScope

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Arguments] name(optional) [Return Value] Success or Failure [Description] Removes a scope from the scope stack. If no name is provided, the topmost scope is removed. Otherwise the scope with provided name is removed. A Failure status is returned if the stack is empty or no scope with the specified name exists. [Function]

Output: DeleteScope

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Arguments] variableName, value(optional), scopeName(optional) [Return Value] Success or Error [Description] Creates a variable. If scopeName is not specified, the variable is created in the top most scope on the scope stack. If no value is provided, the variable is created with the default value specified by the underlying datamodel. A Failure status is returned if a variable of the same name already exists in the specified scope. [Function]

Output: CreateVariable

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Arguments] variableName, scopeName(optional) [Return Value] Success or Failure [Description] Deletes the variable with the specified name from the specified scope. If no scopeName is provided, the variable is deleted from the topmost scope on the stack. The status Failure is returned if no variable with the specified name exists in the scope. [Function]

Output: DeleteVariable

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Arguments] variableName, newValue, scopeName(optional) [Return Value] Success or Failure [Description] Assigns a new value to the variable specified. If scopeName is not specified, the variable is accessed in the topmost scope on the stack. A Failure status is returned if the specified variable or scope cannot be found. [Function]

Output: UpdateVariable

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Arguments] variableName, scopeName(optional) [Return Value] value [Description] Returns the value of the variable specified. If scopeName is not specified, the variable is accessed in the topmost scope on the stack. An error is raised if the specified variable or scope cannot be found. [Function]

Output: ReadVariable

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Arguments] expr, scopeName(optional) [Return Value] value [Description] Evaluates the specified expression and returns its value. If scopeName is not specified, the expression is evaluated in the topmost scope on the stack. An error is raised if the specified scope cannot be found. [Function]

Output: EvaluateExpression

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Event Identifier] DOMFocusIn [Description] Occurs when an element receives focus. [DOM3 event category] UIEvent [Bubbling phase] Yes [Cancel -able] No [uDOM interface] UIEvent [Animation event name]

Output: focusin


Input: [Event Identifier] DOMFocusOut [Description] Occurs when an element loses focus. [DOM3 event category] UIEvent [Bubbling phase] Yes [Cancel -able] No [uDOM interface] UIEvent [Animation event name]

Output: focusout


Input: [Event Identifier] DOMActivate [Description] Occurs when an element is activated, for instance, through a mouse click or a keypress. [DOM3 event category] UIEvent [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] UIEvent [Animation event name]

Output: activate


Input: [Event Identifier] click [Description] Occurs when the pointing device button is clicked over an element. A click is defined as a mousedown and mouseup over the same screen location. The sequence of these events is: mousedown, mouseup, click. If multiple clicks occur at the same screen location, the sequence repeats with the detail attribute incrementing with each repetition. [DOM3 event category] MouseEvent [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] MouseEvent [Animation event name]

Output: click


Input: [Event Identifier] mousedown [Description] Occurs when the pointing device button is pressed over an element. [DOM3 event category] MouseEvent [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] MouseEvent [Animation event name]

Output: mousedown


Input: [Event Identifier] mouseup [Description] Occurs when the pointing device button is released over an element. [DOM3 event category] MouseEvent [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] MouseEvent [Animation event name]

Output: mouseup


Input: [Event Identifier] mouseover [Description] Occurs when the pointing device is moved onto an element. [DOM3 event category] MouseEvent [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] MouseEvent [Animation event name]

Output: mouseover


Input: [Event Identifier] mousemove [Description] Occurs when the pointing device is moved while it is over an element. [DOM3 event category] MouseEvent [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] MouseEvent [Animation event name]

Output: mousemove


Input: [Event Identifier] mouseout [Description] Occurs when the pointing device is moved away from an element. [DOM3 event category] MouseEvent [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] MouseEvent [Animation event name]

Output: mouseout


Input: [Event Identifier] textInput [Description] One or more characters have been entered. [DOM3 event category] TextEvent [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] TextEvent [Animation event name]


Input: [Event Identifier] keydown [Description] A key is pressed down. (The normative definition of this event is the description in the DOM3 Events specification.) [DOM3 event category] KeyboardEvent [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] KeyboardEvent [Animation event name]


Input: [Event Identifier] keyup [Description] A key is released. (The normative definition of this event is the description in the DOM3 Events specification.) [DOM3 event category] KeyboardEvent [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] KeyboardEvent [Animation event name]


Input: [Event Identifier] load [Description] The event is triggered at the point at which the user agent finishes loading the element and any dependent resources (such as images, style sheets, or scripts). In the case the element references a script, the event will be raised only after an attempt to interpret the script has been made. Dependent resources that fail to load will not prevent this event from firing if the element that referenced them is still accessible via the DOM unless they are designated as externalResourcesRequired. The event is independent of the means by which the element was added to DOM tree. [DOM3 event category] BasicEvent [Bubbling phase] No [Cancel -able] No [uDOM interface] Event [Animation event name]

Output: load


Input: [Event Identifier] SVGLoad [Description] This event is deprecated and is for backwards compatibility only, see notes below. This event is sent at the same time as the load event, but the load event must be sent before the SVGLoad event. [DOM3 event category] none [Bubbling phase] No [Cancel -able] No [uDOM interface] Event [Animation event name]


Input: [Event Identifier] resize [Description] Occurs when a document view is being resized. This event is only applicable to 'svg' elements and is dispatched after the resize operation has taken place. The target of the event is the 'svg' element. [DOM3 event category] BasicEvent [Bubbling phase] Yes [Cancel -able] No [uDOM interface] Event [Animation event name]

Output: resize


Input: [Event Identifier] SVGResize [Description] This event is deprecated and is for backwards compatibility only, see notes below. This event is sent at the same time as the resize event, but the resize event must be sent before the SVGResize event. [DOM3 event category] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface] Event [Animation event name]


Input: [Event Identifier] scroll [Description] Occurs when a document view is being shifted along the X or Y or both axis, either through a direct user interaction or any change on the currentTranslate property available on SVGSVGElement interface. This event is only applicable to 'svg' elements and is dispatched after the shift modification has taken place. The target of the event is the 'svg' element. [DOM3 event category] BasicEvent [Bubbling phase] Yes [Cancel -able] No [uDOM interface] Event [Animation event name]

Output: scroll


Input: [Event Identifier] SVGScroll [Description] This event is deprecated and is for backwards compatibility only, see notes below. This event is sent at the same time as the scroll event, but the scroll event must be sent before the SVGScroll event. [DOM3 event category] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface] Event [Animation event name]


Input: [Event Identifier] SVGZoom [Description] Occurs when the zoom level of a document view is being changed, either through a direct user interaction or any change to the currentScale property available on SVGSVGElement interface. This event is only applicable to 'svg' elements and is dispatched after the zoom level modification has taken place. The target of the event is the 'svg' element. [DOM3 event category] none [Bubbling phase] No [Cancel -able] No [uDOM interface] Event [Animation event name]

Output: zoom


Input: [Event Identifier] SVGRotate [Description] Occurs when the rotation of a document view is being changed, either through a direct user interaction or any change to the currentRotate property available on SVGSVGElement interface. This event is only applicable to 'svg' elements and is dispatched after the rotation modification has taken place. The target of the event is the 'svg' element. [DOM3 event category] none [Bubbling phase] No [Cancel -able] No [uDOM interface] Event [Animation event name]

Output: rotate


Input: [Event Identifier] beginEvent [Description] Occurs when a Timed Element begins. For details, see the description of the Events and event model in SMIL 2.1. [DOM3 event category] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface] TimeEvent [Animation event name]

Output: beginEvent


Input: [Event Identifier] endEvent [Description] Occurs when a Timed Element ends. For details, see the description of the Events and event model in SMIL 2.1. [DOM3 event category] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface] TimeEvent [Animation event name]

Output: endEvent


Input: [Event Identifier] repeatEvent [Description] Occurs when a Timed Element repeats. It is raised each time the element repeats, after the first iteration. For details, see the description of the Events and event model in SMIL 2.1. [DOM3 event category] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface] TimeEvent [Animation event name]

Output: repeatEvent


Input: [Event Identifier] SVGMousewheel [Description] Occurs when a rotational input device has been activated. [DOM3 event category] MouseEvent [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] WheelEvent [Animation event name]


Input: [Event Identifier] SVGPreload [Description] A load operation has begun. [DOM3 event category] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface] ProgressEvent [Animation event name]


Input: [Event Identifier] SVGLoadProgress [Description] Progress has occurred in loading a given resource. [DOM3 event category] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface] ProgressEvent [Animation event name]


Input: [Event Identifier] SVGPostload [Description] A load operation has completed. [DOM3 event category] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface] ProgressEvent [Animation event name]


Input: [Event Identifier] SVGTimer [Description] Occurs when the specified timer interval has elapsed for a timer. This event is triggered only by 'running' timers in the current global execution context of the SVG document (i.e. for timers which have been instantiated via the SVGGlobal interface and started via the start() method of the Timer interface). The target of the event is the 'timer' object itself. The event processing is limited to the target phase. [DOM3 event category] none [Bubbling phase] No [Cancel -able] No [uDOM interface] Event [Animation event name]


Input: [Event Identifier] SVGConnectionConnected [Description] Occurs when a connection has been established. No context information is available. [DOM3 event category] none [Bubbling phase] No [Cancel -able] No [uDOM interface] ConnectionEvent [Animation event name]


Input: [Event Identifier] SVGConnectionClosed [Description] Occurs when a connection has been closed. No context information is available [DOM3 event category] none [Bubbling phase] No [Cancel -able] No [uDOM interface] ConnectionEvent [Animation event name]


Input: [Event Identifier] SVGConnectionError [Description] Occurs when an error happens during the lifetime of a connection. Additional context information is available in the errorCode field. [DOM3 event category] none [Bubbling phase] No [Cancel -able] No [uDOM interface] ConnectionEvent [Animation event name]


Input: [Event Identifier] SVGConnectionDataSent [Description] Occurs when data has been successfully transmitted. No context information is available. [DOM3 event category] none [Bubbling phase] No [Cancel -able] No [uDOM interface] ConnectionEvent [Animation event name]


Input: [Event Identifier] SVGConnectionDataReceived [Description] Occurs when data has been received on the connection. Additional context information is available on the receivedData field. [DOM3 event category] none [Bubbling phase] No [Cancel -able] No [uDOM interface] ConnectionEvent [Animation event name]


Input: [Function] CreateScope [Arguments] name(optional) [Description] Creates a new scope object and pushes it on top of the scope stack. If no name is provided the scope is anonymous and may be accessed only when it on the top of the scope stack. A Failure status is returned if a scope already exists with the specified name. [Return Value]

Output: Success or Failure

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Function] DeleteScope [Arguments] name(optional) [Description] Removes a scope from the scope stack. If no name is provided, the topmost scope is removed. Otherwise the scope with provided name is removed. A Failure status is returned if the stack is empty or no scope with the specified name exists. [Return Value]

Output: Success or Failure

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Function] CreateVariable [Arguments] variableName, value(optional), scopeName(optional) [Description] Creates a variable. If scopeName is not specified, the variable is created in the top most scope on the scope stack. If no value is provided, the variable is created with the default value specified by the underlying datamodel. A Failure status is returned if a variable of the same name already exists in the specified scope. [Return Value]

Output: Success or Error

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Function] DeleteVariable [Arguments] variableName, scopeName(optional) [Description] Deletes the variable with the specified name from the specified scope. If no scopeName is provided, the variable is deleted from the topmost scope on the stack. The status Failure is returned if no variable with the specified name exists in the scope. [Return Value]

Output: Success or Failure

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Function] UpdateVariable [Arguments] variableName, newValue, scopeName(optional) [Description] Assigns a new value to the variable specified. If scopeName is not specified, the variable is accessed in the topmost scope on the stack. A Failure status is returned if the specified variable or scope cannot be found. [Return Value]

Output: Success or Failure

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Function] ReadVariable [Arguments] variableName, scopeName(optional) [Description] Returns the value of the variable specified. If scopeName is not specified, the variable is accessed in the topmost scope on the stack. An error is raised if the specified variable or scope cannot be found. [Return Value]

Output: value

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Function] EvaluateExpression [Arguments] expr, scopeName(optional) [Description] Evaluates the specified expression and returns its value. If scopeName is not specified, the expression is evaluated in the topmost scope on the stack. An error is raised if the specified scope cannot be found. [Return Value]

Output: value

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Patterns] RDF terms [Query Forms] SELECT [Modifiers]

Output: DISTINCT


Input: [Patterns] triple patterns [Query Forms] CONSTRUCT [Modifiers]

Output: REDUCED


Input: [Patterns] Basic graph patterns [Query Forms] DESCRIBE [Modifiers]

Output: PROJECT


Input: [Patterns] Groups [Query Forms] ASK [Modifiers]

Output: ORDER BY


Input: [Patterns] OPTIONAL [Modifiers]

Output: LIMIT


Input: [Patterns] UNION [Modifiers]

Output: OFFSET


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)

Table 5-1. EXI Options in Options Document


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: [Event Identifier] DOMFocusIn [Description] Occurs when an element receives focus. [Animation event name] focusin [Bubbling phase] Yes [Cancel -able] No [uDOM interface] UIEvent [DOM3 event category]

Output: UIEvent


Input: [Event Identifier] DOMFocusOut [Description] Occurs when an element loses focus. [Animation event name] focusout [Bubbling phase] Yes [Cancel -able] No [uDOM interface] UIEvent [DOM3 event category]

Output: UIEvent


Input: [Event Identifier] DOMActivate [Description] Occurs when an element is activated, for instance, through a mouse click or a keypress. [Animation event name] activate [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] UIEvent [DOM3 event category]

Output: UIEvent


Input: [Event Identifier] click [Description] Occurs when the pointing device button is clicked over an element. A click is defined as a mousedown and mouseup over the same screen location. The sequence of these events is: mousedown, mouseup, click. If multiple clicks occur at the same screen location, the sequence repeats with the detail attribute incrementing with each repetition. [Animation event name] click [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] MouseEvent [DOM3 event category]

Output: MouseEvent


Input: [Event Identifier] mousedown [Description] Occurs when the pointing device button is pressed over an element. [Animation event name] mousedown [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] MouseEvent [DOM3 event category]

Output: MouseEvent


Input: [Event Identifier] mouseup [Description] Occurs when the pointing device button is released over an element. [Animation event name] mouseup [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] MouseEvent [DOM3 event category]

Output: MouseEvent


Input: [Event Identifier] mouseover [Description] Occurs when the pointing device is moved onto an element. [Animation event name] mouseover [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] MouseEvent [DOM3 event category]

Output: MouseEvent


Input: [Event Identifier] mousemove [Description] Occurs when the pointing device is moved while it is over an element. [Animation event name] mousemove [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] MouseEvent [DOM3 event category]

Output: MouseEvent


Input: [Event Identifier] mouseout [Description] Occurs when the pointing device is moved away from an element. [Animation event name] mouseout [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] MouseEvent [DOM3 event category]

Output: MouseEvent


Input: [Event Identifier] textInput [Description] One or more characters have been entered. [Animation event name] none [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] TextEvent [DOM3 event category]

Output: TextEvent


Input: [Event Identifier] keydown [Description] A key is pressed down. (The normative definition of this event is the description in the DOM3 Events specification.) [Animation event name] none [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] KeyboardEvent [DOM3 event category]

Output: KeyboardEvent


Input: [Event Identifier] keyup [Description] A key is released. (The normative definition of this event is the description in the DOM3 Events specification.) [Animation event name] none [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] KeyboardEvent [DOM3 event category]

Output: KeyboardEvent


Input: [Event Identifier] load [Description] The event is triggered at the point at which the user agent finishes loading the element and any dependent resources (such as images, style sheets, or scripts). In the case the element references a script, the event will be raised only after an attempt to interpret the script has been made. Dependent resources that fail to load will not prevent this event from firing if the element that referenced them is still accessible via the DOM unless they are designated as externalResourcesRequired. The event is independent of the means by which the element was added to DOM tree. [Animation event name] load [Bubbling phase] No [Cancel -able] No [uDOM interface] Event [DOM3 event category]

Output: BasicEvent


Input: [Event Identifier] SVGLoad [Description] This event is deprecated and is for backwards compatibility only, see notes below. This event is sent at the same time as the load event, but the load event must be sent before the SVGLoad event. [Animation event name] none [Bubbling phase] No [Cancel -able] No [uDOM interface] Event [DOM3 event category]


Input: [Event Identifier] resize [Description] Occurs when a document view is being resized. This event is only applicable to 'svg' elements and is dispatched after the resize operation has taken place. The target of the event is the 'svg' element. [Animation event name] resize [Bubbling phase] Yes [Cancel -able] No [uDOM interface] Event [DOM3 event category]

Output: BasicEvent


Input: [Event Identifier] SVGResize [Description] This event is deprecated and is for backwards compatibility only, see notes below. This event is sent at the same time as the resize event, but the resize event must be sent before the SVGResize event. [Animation event name] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface] Event [DOM3 event category]


Input: [Event Identifier] scroll [Description] Occurs when a document view is being shifted along the X or Y or both axis, either through a direct user interaction or any change on the currentTranslate property available on SVGSVGElement interface. This event is only applicable to 'svg' elements and is dispatched after the shift modification has taken place. The target of the event is the 'svg' element. [Animation event name] scroll [Bubbling phase] Yes [Cancel -able] No [uDOM interface] Event [DOM3 event category]

Output: BasicEvent


Input: [Event Identifier] SVGScroll [Description] This event is deprecated and is for backwards compatibility only, see notes below. This event is sent at the same time as the scroll event, but the scroll event must be sent before the SVGScroll event. [Animation event name] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface] Event [DOM3 event category]


Input: [Event Identifier] SVGZoom [Description] Occurs when the zoom level of a document view is being changed, either through a direct user interaction or any change to the currentScale property available on SVGSVGElement interface. This event is only applicable to 'svg' elements and is dispatched after the zoom level modification has taken place. The target of the event is the 'svg' element. [Animation event name] zoom [Bubbling phase] No [Cancel -able] No [uDOM interface] Event [DOM3 event category]


Input: [Event Identifier] SVGRotate [Description] Occurs when the rotation of a document view is being changed, either through a direct user interaction or any change to the currentRotate property available on SVGSVGElement interface. This event is only applicable to 'svg' elements and is dispatched after the rotation modification has taken place. The target of the event is the 'svg' element. [Animation event name] rotate [Bubbling phase] No [Cancel -able] No [uDOM interface] Event [DOM3 event category]


Input: [Event Identifier] beginEvent [Description] Occurs when a Timed Element begins. For details, see the description of the Events and event model in SMIL 2.1. [Animation event name] beginEvent [Bubbling phase] Yes [Cancel -able] No [uDOM interface] TimeEvent [DOM3 event category]


Input: [Event Identifier] endEvent [Description] Occurs when a Timed Element ends. For details, see the description of the Events and event model in SMIL 2.1. [Animation event name] endEvent [Bubbling phase] Yes [Cancel -able] No [uDOM interface] TimeEvent [DOM3 event category]


Input: [Event Identifier] repeatEvent [Description] Occurs when a Timed Element repeats. It is raised each time the element repeats, after the first iteration. For details, see the description of the Events and event model in SMIL 2.1. [Animation event name] repeatEvent [Bubbling phase] Yes [Cancel -able] No [uDOM interface] TimeEvent [DOM3 event category]


Input: [Event Identifier] SVGMousewheel [Description] Occurs when a rotational input device has been activated. [Animation event name] none [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] WheelEvent [DOM3 event category]

Output: MouseEvent


Input: [Event Identifier] SVGPreload [Description] A load operation has begun. [Animation event name] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface] ProgressEvent [DOM3 event category]


Input: [Event Identifier] SVGLoadProgress [Description] Progress has occurred in loading a given resource. [Animation event name] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface] ProgressEvent [DOM3 event category]


Input: [Event Identifier] SVGPostload [Description] A load operation has completed. [Animation event name] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface] ProgressEvent [DOM3 event category]


Input: [Event Identifier] SVGTimer [Description] Occurs when the specified timer interval has elapsed for a timer. This event is triggered only by 'running' timers in the current global execution context of the SVG document (i.e. for timers which have been instantiated via the SVGGlobal interface and started via the start() method of the Timer interface). The target of the event is the 'timer' object itself. The event processing is limited to the target phase. [Animation event name] none [Bubbling phase] No [Cancel -able] No [uDOM interface] Event [DOM3 event category]


Input: [Event Identifier] SVGConnectionConnected [Description] Occurs when a connection has been established. No context information is available. [Animation event name] none [Bubbling phase] No [Cancel -able] No [uDOM interface] ConnectionEvent [DOM3 event category]


Input: [Event Identifier] SVGConnectionClosed [Description] Occurs when a connection has been closed. No context information is available [Animation event name] none [Bubbling phase] No [Cancel -able] No [uDOM interface] ConnectionEvent [DOM3 event category]


Input: [Event Identifier] SVGConnectionError [Description] Occurs when an error happens during the lifetime of a connection. Additional context information is available in the errorCode field. [Animation event name] none [Bubbling phase] No [Cancel -able] No [uDOM interface] ConnectionEvent [DOM3 event category]


Input: [Event Identifier] SVGConnectionDataSent [Description] Occurs when data has been successfully transmitted. No context information is available. [Animation event name] none [Bubbling phase] No [Cancel -able] No [uDOM interface] ConnectionEvent [DOM3 event category]


Input: [Event Identifier] SVGConnectionDataReceived [Description] Occurs when data has been received on the connection. Additional context information is available on the receivedData field. [Animation event name] none [Bubbling phase] No [Cancel -able] No [uDOM interface] ConnectionEvent [DOM3 event category]


Input: [Name] confidencelevel [Default] 0.5 [Description]

Output: The speech recognition confidence level, a float value in the range of 0.0 to 1.0. Results are rejected (a nomatch event is thrown) when application.lastresult$.confidence is below this threshold. A value of 0.0 means minimum confidence is needed for a recognition, and a value of 1.0 requires maximum confidence. The value is a Real Number Designation (see 8.4 Value Designations).

Voice Extensible Markup Language (VoiceXML) 3.0

Table 71: Speech Recognition Properties


Input: [Name] sensitivity [Default] 0.5 [Description]

Output: Set the sensitivity level. A value of 1.0 means that it is highly sensitive to quiet input. A value of 0.0 means it is least sensitive to noise. The value is a Real Number Designation (see 8.4 Value Designations).

Voice Extensible Markup Language (VoiceXML) 3.0

Table 71: Speech Recognition Properties


Input: [Name] speedvsaccuracy [Default] 0.5 [Description]

Output: A hint specifying the desired balance between speed vs. accuracy. A value of 0.0 means fastest recognition. A value of 1.0 means best accuracy. The value is a Real Number Designation (see 8.4 Value Designations).

Voice Extensible Markup Language (VoiceXML) 3.0

Table 71: Speech Recognition Properties


Input: [Name] completetimeout [Default] platform-dependent [Description]

Output: The length of silence required following user speech before the speech recognizer finalizes a result (either accepting it or throwing a nomatch event). The complete timeout is used when the speech is a complete match of an active grammar. By contrast, the incomplete timeout is used when the speech is an incomplete match to an active grammar. A long complete timeout value delays the result completion and therefore makes the computer's response slow. A short complete timeout may lead to an utterance being broken up inappropriately. Reasonable complete timeout values are typically in the range of 0.3 seconds to 1.0 seconds. The value is a Time Designation (see 8.4 Value Designations). See 8.3 Speech and DTMF Input Timing Properties. Although platforms must parse the completetimeout property, platforms are not required to support the behavior of completetimeout. Platforms choosing not to support the behavior of completetimeout must so document and adjust the behavior of the incompletetimeout property as described below.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 71: Speech Recognition Properties


Input: [Name] incompletetimeout [Default] undefined? [Description]

Output: The required length of silence following user speech after which a recognizer finalizes a result. The incomplete timeout applies when the speech prior to the silence is an incomplete match of all active grammars. In this case, once the timeout is triggered, the partial result is rejected (with a nomatch event). The incomplete timeout also applies when the speech prior to the silence is a complete match of an active grammar, but where it is possible to speak further and still match the grammar. By contrast, the complete timeout is used when the speech is a complete match to an active grammar and no further words can be spoken. A long incomplete timeout value delays the result completion and therefore makes the computer's response slow. A short incomplete timeout may lead to an utterance being broken up inappropriately. The incomplete timeout is usually longer than the complete timeout to allow users to pause mid-utterance (for example, to breathe). See 8.3 Speech and DTMF Input Timing Properties Platforms choosing not to support the completetimeout property (described above) must use the maximum of the completetimeout and incompletetimeout values as the value for the incompletetimeout. The value is a Time Designation (see 8.4 Value Designations).

Voice Extensible Markup Language (VoiceXML) 3.0

Table 71: Speech Recognition Properties


Input: [Name] maxspeechtimeout [Default] platform-dependent [Description]

Output: The maximum duration of user speech. If this time elapsed before the user stops speaking, the event "maxspeechtimeout" is thrown. The value is a Time Designation (see 8.4 Value Designations).

Voice Extensible Markup Language (VoiceXML) 3.0

Table 71: Speech Recognition Properties


Input: [Event Identifier] DOMFocusIn [Description] Occurs when an element receives focus. [DOM3 event category] UIEvent [Animation event name] focusin [Bubbling phase] Yes [uDOM interface] UIEvent [Cancel -able]

Output: No


Input: [Event Identifier] DOMFocusOut [Description] Occurs when an element loses focus. [DOM3 event category] UIEvent [Animation event name] focusout [Bubbling phase] Yes [uDOM interface] UIEvent [Cancel -able]

Output: No


Input: [Event Identifier] DOMActivate [Description] Occurs when an element is activated, for instance, through a mouse click or a keypress. [DOM3 event category] UIEvent [Animation event name] activate [Bubbling phase] Yes [uDOM interface] UIEvent [Cancel -able]

Output: Yes


Input: [Event Identifier] click [Description] Occurs when the pointing device button is clicked over an element. A click is defined as a mousedown and mouseup over the same screen location. The sequence of these events is: mousedown, mouseup, click. If multiple clicks occur at the same screen location, the sequence repeats with the detail attribute incrementing with each repetition. [DOM3 event category] MouseEvent [Animation event name] click [Bubbling phase] Yes [uDOM interface] MouseEvent [Cancel -able]

Output: Yes


Input: [Event Identifier] mousedown [Description] Occurs when the pointing device button is pressed over an element. [DOM3 event category] MouseEvent [Animation event name] mousedown [Bubbling phase] Yes [uDOM interface] MouseEvent [Cancel -able]

Output: Yes


Input: [Event Identifier] mouseup [Description] Occurs when the pointing device button is released over an element. [DOM3 event category] MouseEvent [Animation event name] mouseup [Bubbling phase] Yes [uDOM interface] MouseEvent [Cancel -able]

Output: Yes


Input: [Event Identifier] mouseover [Description] Occurs when the pointing device is moved onto an element. [DOM3 event category] MouseEvent [Animation event name] mouseover [Bubbling phase] Yes [uDOM interface] MouseEvent [Cancel -able]

Output: Yes


Input: [Event Identifier] mousemove [Description] Occurs when the pointing device is moved while it is over an element. [DOM3 event category] MouseEvent [Animation event name] mousemove [Bubbling phase] Yes [uDOM interface] MouseEvent [Cancel -able]

Output: Yes


Input: [Event Identifier] mouseout [Description] Occurs when the pointing device is moved away from an element. [DOM3 event category] MouseEvent [Animation event name] mouseout [Bubbling phase] Yes [uDOM interface] MouseEvent [Cancel -able]

Output: Yes


Input: [Event Identifier] textInput [Description] One or more characters have been entered. [DOM3 event category] TextEvent [Animation event name] none [Bubbling phase] Yes [uDOM interface] TextEvent [Cancel -able]

Output: Yes


Input: [Event Identifier] keydown [Description] A key is pressed down. (The normative definition of this event is the description in the DOM3 Events specification.) [DOM3 event category] KeyboardEvent [Animation event name] none [Bubbling phase] Yes [uDOM interface] KeyboardEvent [Cancel -able]

Output: Yes


Input: [Event Identifier] keyup [Description] A key is released. (The normative definition of this event is the description in the DOM3 Events specification.) [DOM3 event category] KeyboardEvent [Animation event name] none [Bubbling phase] Yes [uDOM interface] KeyboardEvent [Cancel -able]

Output: Yes


Input: [Event Identifier] load [Description] The event is triggered at the point at which the user agent finishes loading the element and any dependent resources (such as images, style sheets, or scripts). In the case the element references a script, the event will be raised only after an attempt to interpret the script has been made. Dependent resources that fail to load will not prevent this event from firing if the element that referenced them is still accessible via the DOM unless they are designated as externalResourcesRequired. The event is independent of the means by which the element was added to DOM tree. [DOM3 event category] BasicEvent [Animation event name] load [Bubbling phase] No [uDOM interface] Event [Cancel -able]

Output: No


Input: [Event Identifier] SVGLoad [Description] This event is deprecated and is for backwards compatibility only, see notes below. This event is sent at the same time as the load event, but the load event must be sent before the SVGLoad event. [DOM3 event category] none [Animation event name] none [Bubbling phase] No [uDOM interface] Event [Cancel -able]

Output: No


Input: [Event Identifier] resize [Description] Occurs when a document view is being resized. This event is only applicable to 'svg' elements and is dispatched after the resize operation has taken place. The target of the event is the 'svg' element. [DOM3 event category] BasicEvent [Animation event name] resize [Bubbling phase] Yes [uDOM interface] Event [Cancel -able]

Output: No


Input: [Event Identifier] SVGResize [Description] This event is deprecated and is for backwards compatibility only, see notes below. This event is sent at the same time as the resize event, but the resize event must be sent before the SVGResize event. [DOM3 event category] none [Animation event name] none [Bubbling phase] Yes [uDOM interface] Event [Cancel -able]

Output: No


Input: [Event Identifier] scroll [Description] Occurs when a document view is being shifted along the X or Y or both axis, either through a direct user interaction or any change on the currentTranslate property available on SVGSVGElement interface. This event is only applicable to 'svg' elements and is dispatched after the shift modification has taken place. The target of the event is the 'svg' element. [DOM3 event category] BasicEvent [Animation event name] scroll [Bubbling phase] Yes [uDOM interface] Event [Cancel -able]

Output: No


Input: [Event Identifier] SVGScroll [Description] This event is deprecated and is for backwards compatibility only, see notes below. This event is sent at the same time as the scroll event, but the scroll event must be sent before the SVGScroll event. [DOM3 event category] none [Animation event name] none [Bubbling phase] Yes [uDOM interface] Event [Cancel -able]

Output: No


Input: [Event Identifier] SVGZoom [Description] Occurs when the zoom level of a document view is being changed, either through a direct user interaction or any change to the currentScale property available on SVGSVGElement interface. This event is only applicable to 'svg' elements and is dispatched after the zoom level modification has taken place. The target of the event is the 'svg' element. [DOM3 event category] none [Animation event name] zoom [Bubbling phase] No [uDOM interface] Event [Cancel -able]

Output: No


Input: [Event Identifier] SVGRotate [Description] Occurs when the rotation of a document view is being changed, either through a direct user interaction or any change to the currentRotate property available on SVGSVGElement interface. This event is only applicable to 'svg' elements and is dispatched after the rotation modification has taken place. The target of the event is the 'svg' element. [DOM3 event category] none [Animation event name] rotate [Bubbling phase] No [uDOM interface] Event [Cancel -able]

Output: No


Input: [Event Identifier] beginEvent [Description] Occurs when a Timed Element begins. For details, see the description of the Events and event model in SMIL 2.1. [DOM3 event category] none [Animation event name] beginEvent [Bubbling phase] Yes [uDOM interface] TimeEvent [Cancel -able]

Output: No


Input: [Event Identifier] endEvent [Description] Occurs when a Timed Element ends. For details, see the description of the Events and event model in SMIL 2.1. [DOM3 event category] none [Animation event name] endEvent [Bubbling phase] Yes [uDOM interface] TimeEvent [Cancel -able]

Output: No


Input: [Event Identifier] repeatEvent [Description] Occurs when a Timed Element repeats. It is raised each time the element repeats, after the first iteration. For details, see the description of the Events and event model in SMIL 2.1. [DOM3 event category] none [Animation event name] repeatEvent [Bubbling phase] Yes [uDOM interface] TimeEvent [Cancel -able]

Output: No


Input: [Event Identifier] SVGMousewheel [Description] Occurs when a rotational input device has been activated. [DOM3 event category] MouseEvent [Animation event name] none [Bubbling phase] Yes [uDOM interface] WheelEvent [Cancel -able]

Output: Yes


Input: [Event Identifier] SVGPreload [Description] A load operation has begun. [DOM3 event category] none [Animation event name] none [Bubbling phase] Yes [uDOM interface] ProgressEvent [Cancel -able]

Output: No


Input: [Event Identifier] SVGLoadProgress [Description] Progress has occurred in loading a given resource. [DOM3 event category] none [Animation event name] none [Bubbling phase] Yes [uDOM interface] ProgressEvent [Cancel -able]

Output: No


Input: [Event Identifier] SVGPostload [Description] A load operation has completed. [DOM3 event category] none [Animation event name] none [Bubbling phase] Yes [uDOM interface] ProgressEvent [Cancel -able]

Output: No


Input: [Event Identifier] SVGTimer [Description] Occurs when the specified timer interval has elapsed for a timer. This event is triggered only by 'running' timers in the current global execution context of the SVG document (i.e. for timers which have been instantiated via the SVGGlobal interface and started via the start() method of the Timer interface). The target of the event is the 'timer' object itself. The event processing is limited to the target phase. [DOM3 event category] none [Animation event name] none [Bubbling phase] No [uDOM interface] Event [Cancel -able]

Output: No


Input: [Event Identifier] SVGConnectionConnected [Description] Occurs when a connection has been established. No context information is available. [DOM3 event category] none [Animation event name] none [Bubbling phase] No [uDOM interface] ConnectionEvent [Cancel -able]

Output: No


Input: [Event Identifier] SVGConnectionClosed [Description] Occurs when a connection has been closed. No context information is available [DOM3 event category] none [Animation event name] none [Bubbling phase] No [uDOM interface] ConnectionEvent [Cancel -able]

Output: No


Input: [Event Identifier] SVGConnectionError [Description] Occurs when an error happens during the lifetime of a connection. Additional context information is available in the errorCode field. [DOM3 event category] none [Animation event name] none [Bubbling phase] No [uDOM interface] ConnectionEvent [Cancel -able]

Output: No


Input: [Event Identifier] SVGConnectionDataSent [Description] Occurs when data has been successfully transmitted. No context information is available. [DOM3 event category] none [Animation event name] none [Bubbling phase] No [uDOM interface] ConnectionEvent [Cancel -able]

Output: No


Input: [Event Identifier] SVGConnectionDataReceived [Description] Occurs when data has been received on the connection. Additional context information is available on the receivedData field. [DOM3 event category] none [Animation event name] none [Bubbling phase] No [uDOM interface] ConnectionEvent [Cancel -able]

Output: No


Input: [Category] Presentation [4] Presentation is clear and to the point, clearly describing the project problem and proposed solution. The project plan is clearly communicated, including who is accountable for which tasks, when tasks need to be done by, how we know they are completed satisfactorily. [2] Presentation is average, not very comprehensive or clear, describing the project problem and proposed solution. The project plan is communicated, including who is accountable for which tasks, when tasks need to be done by, how we know they are completed satisfactorily. [1] Presentation is long-winded, covers some description of the project problem and proposed solution but is somewhat incomplete. The project plan is communicated, but assignments, tasks timelines and quality criteria are not made clear and explicit. [3]

Output: Presentation is reasonably clear and to the point, describing the project problem and proposed solution. The project plan is communicated, including who is accountable for which task, when tasks need to be done by, how we know they are completed satisfactorily.

Es/Interact/Gestión de proyectos - Web Education Community Group


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

Output: Meeting objectives are reasonably clearly stated, items of discussion are listed.

Es/Interact/Gestión de proyectos - Web Education Community Group


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

Output: Meeting runs over time, all points are covered and all action points are assigned.

Es/Interact/Gestión de proyectos - Web Education Community Group


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

Output: Minutes are readable and fairly comprehensive, mentioning some problems raised, solutions decided upon, and clear action points.

Es/Interact/Gestión de proyectos - Web Education Community Group


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

Output: Usually provides useful ideas when participating in the group and in classroom discussion. Hesitant to challenge ideas. A strong group member who tries hard.

Es/Interact/Gestión de proyectos - Web Education Community Group


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

Output: Usually listens to, shares, with, and supports the efforts of others. Does not cause “waves” in the group.

Es/Interact/Gestión de proyectos - Web Education Community Group


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

Output: No

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


Input: [Data category] Localization Note [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes [Default Values] None [Inheritance] Textual content of element, including content of child elements, but excluding attributes [Overriding] Yes

Output: Yes

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


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

Output: Yes

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


Input: [Data category] Directionality [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes [Default Values] dir="ltr" [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes

Output: No

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


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

Output: Yes

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


Input: [Data category] Language Information [Local Usage] No [Global, rule-based selection] Yes [Global adding of information] No [Default Values] None [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes

Output: Yes

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


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

Output: No

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


Input: [Component] Context item [Scope]

Output: dynamic; changes during evaluation of path expressions and predicates

Dynamic Context Components


Input: [Component] Context position [Scope]

Output: dynamic; changes during evaluation of path expressions and predicates

Dynamic Context Components


Input: [Component] Context size [Scope]

Output: dynamic; changes during evaluation of path expressions and predicates

Dynamic Context Components


Input: [Component] Variable values [Scope]

Output: dynamic; for-expressions and quantified expressions can bind new variables

Dynamic Context Components


Input: [Component] Current date and time [Scope]

Output: global; must be initialized by implementation

Dynamic Context Components


Input: [Component] Implicit timezone [Scope]

Output: global; must be initialized by implementation

Dynamic Context Components


Input: [Component] Available documents [Scope]

Output: global; must be initialized by implementation

Dynamic Context Components


Input: [Component] Available collections [Scope]

Output: global; must be initialized by implementation

Dynamic Context Components


Input: [Component] Default collection [Scope]

Output: global; must be initialized by implementation

Dynamic Context Components


Input: [Category] Presentation [3] Presentation is reasonably clear and to the point, describing the project problem and proposed solution. The project plan is communicated, including who is accountable for which task, when tasks need to be done by, how we know they are completed satisfactorily. [2] Presentation is average, not very comprehensive or clear, describing the project problem and proposed solution. The project plan is communicated, including who is accountable for which tasks, when tasks need to be done by, how we know they are completed satisfactorily. [1] Presentation is long-winded, covers some description of the project problem and proposed solution but is somewhat incomplete. The project plan is communicated, but assignments, tasks timelines and quality criteria are not made clear and explicit. [4]

Output: Presentation is clear and to the point, clearly describing the project problem and proposed solution. The project plan is clearly communicated, including who is accountable for which tasks, when tasks need to be done by, how we know they are completed satisfactorily.

Es/Interact/Gestión de proyectos - Web Education Community Group


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

Output: Meeting objectives are clearly defined, items of discussion are listed and written in an actionable manner.

Es/Interact/Gestión de proyectos - Web Education Community Group


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

Output: Meeting is kept on track and on time, all points are covered, and all action points are assigned.

Es/Interact/Gestión de proyectos - Web Education Community Group


Input: [Category] Meeting minutes [3] Minutes are readable and fairly comprehensive, mentioning some problems raised, solutions decided upon, and clear action points. [2] Minutes are fairly readable but not comprehensive, mentions some problem raised, some solutions decided upon and lacking clear action points. [1] Minutes are unclear, and not comprehensive, missing problems raised, solutions decided upon and lacking action points. [4]

Output: Minutes are readable, comprehensive, mentioning attendees, problems raised, solutions decided upon and clear action points assigned to team members.

Es/Interact/Gestión de proyectos - Web Education Community Group


Input: [Category] Contribution [3] Usually provides useful ideas when participating in the group and in classroom discussion. Hesitant to challenge ideas. A strong group member who tries hard. [2] Sometimes provides useful ideas when participating in the group and in classroom discussion. Does not challenge existing ideas. A satisfactory group member who does what is required. [1] Rarely provides useful ideas when participating in the group and in classroom discussion. May refuse to participate. [4]

Output: Routinely provides useful ideas when participating in the group and in classroom discussion. Not afraid to challenge an idea constructively. A definite leader who contributes a lot of effort.

Es/Interact/Gestión de proyectos - Web Education Community Group


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

Output: Almost always listens to, shares with, and supports the efforts of others. Tries to keep people working well together.

Es/Interact/Gestión de proyectos - Web Education Community Group


Input: [Function] CreateScope [Arguments] name(optional) [Return Value] Success or Failure [Description]

Output: Creates a new scope object and pushes it on top of the scope stack. If no name is provided the scope is anonymous and may be accessed only when it on the top of the scope stack. A Failure status is returned if a scope already exists with the specified name.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Function] DeleteScope [Arguments] name(optional) [Return Value] Success or Failure [Description]

Output: Removes a scope from the scope stack. If no name is provided, the topmost scope is removed. Otherwise the scope with provided name is removed. A Failure status is returned if the stack is empty or no scope with the specified name exists.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Function] CreateVariable [Arguments] variableName, value(optional), scopeName(optional) [Return Value] Success or Error [Description]

Output: Creates a variable. If scopeName is not specified, the variable is created in the top most scope on the scope stack. If no value is provided, the variable is created with the default value specified by the underlying datamodel. A Failure status is returned if a variable of the same name already exists in the specified scope.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Function] DeleteVariable [Arguments] variableName, scopeName(optional) [Return Value] Success or Failure [Description]

Output: Deletes the variable with the specified name from the specified scope. If no scopeName is provided, the variable is deleted from the topmost scope on the stack. The status Failure is returned if no variable with the specified name exists in the scope.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Function] UpdateVariable [Arguments] variableName, newValue, scopeName(optional) [Return Value] Success or Failure [Description]

Output: Assigns a new value to the variable specified. If scopeName is not specified, the variable is accessed in the topmost scope on the stack. A Failure status is returned if the specified variable or scope cannot be found.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Function] ReadVariable [Arguments] variableName, scopeName(optional) [Return Value] value [Description]

Output: Returns the value of the variable specified. If scopeName is not specified, the variable is accessed in the topmost scope on the stack. An error is raised if the specified variable or scope cannot be found.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Function] EvaluateExpression [Arguments] expr, scopeName(optional) [Return Value] value [Description]

Output: Evaluates the specified expression and returns its value. If scopeName is not specified, the expression is evaluated in the topmost scope on the stack. An error is raised if the specified scope cannot be found.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [4] Presentation is clear and to the point, clearly describing the project problem and proposed solution. The project plan is clearly communicated, including who is accountable for which tasks, when tasks need to be done by, how we know they are completed satisfactorily. [3] Presentation is reasonably clear and to the point, describing the project problem and proposed solution. The project plan is communicated, including who is accountable for which task, when tasks need to be done by, how we know they are completed satisfactorily. [2] Presentation is average, not very comprehensive or clear, describing the project problem and proposed solution. The project plan is communicated, including who is accountable for which tasks, when tasks need to be done by, how we know they are completed satisfactorily. [1] Presentation is long-winded, covers some description of the project problem and proposed solution but is somewhat incomplete. The project plan is communicated, but assignments, tasks timelines and quality criteria are not made clear and explicit. [Category]

Output: Presentation

Es/Interact/Gestión de proyectos - Web Education Community Group


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

Output: Meeting agenda

Es/Interact/Gestión de proyectos - Web Education Community Group


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

Output: Meeting management

Es/Interact/Gestión de proyectos - Web Education Community Group


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

Output: Meeting minutes

Es/Interact/Gestión de proyectos - Web Education Community Group


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

Output: Contribution

Es/Interact/Gestión de proyectos - Web Education Community Group


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

Output: Working with others

Es/Interact/Gestión de proyectos - Web Education Community Group


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)


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: [PREFIX] CONSTRUCT [2] DESCRIBE [3] ASK [BASE]

Output: SELECT


Input: [PREFIX] LIMIT [2] OFFSET [3] DISTINCT [4] REDUCED [BASE]

Output: ORDER BY


Input: [PREFIX] FROM NAMED [2] WHERE [BASE]

Output: FROM


Input: [PREFIX] OPTIONAL [2] UNION [3] FILTER [4] a [BASE]

Output: GRAPH


Input: [PREFIX] LANG [2] LANGMATCHES [3] DATATYPE [4] BOUND [5] sameTERM [BASE]

Output: STR


Input: [PREFIX] isIRI [2] isLITERAL [3] REGEX [4] true [5] false [BASE]

Output: isURI


Input: [1] Description [2] Example [3] Scope [4] Notes [0]

Output: Value

Internationalization Tag Set (ITS) Version 2.0


Input: [1] An incorrect term or a term from the wrong domain was used or terms are used inconsistently. [2] The localization had â€œPen Driveâ€ when corporate terminology specified that â€œUSB Stickâ€ was to be used. The localization text inconsistently used "Start" and "Begin". [3] S or T [0]

Output: terminology

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The content of the target mistranslates the content of the source. [2] The English source reads "An ape succeeded in grasping a banana lying outside its cage with the help of a stick" but the Italian translation reads "l'ape riuscÃ¬ a prendere la banana posta tuori dall sua gabbia aiutandosi con un bastone" ("A bee succeeded...") [3] T [4] Issues related to translation of specific terms related to the domain or task-specific language should be categorized as terminology issues. [0]

Output: mistranslation

Internationalization Tag Set (ITS) Version 2.0


Input: [1] Necessary text has been omitted from the localization or source. [2] One or more segments found in the source that should have been translated are missing in the target. [3] S or T [4] This type should not be used for missing whitespace or formatting codes, but instead should be reserved for linguistic content. [0]

Output: omission

Internationalization Tag Set (ITS) Version 2.0


Input: [1] Content that should have been translated was left untranslated. [2] The source segment reads "The Professor said to Smith that he would hear from his lawyer" but the Hungarian localization reads "A professzor azt modta Smithnek, hogy he would hear from his lawyer." [3] T [4] omission takes precedence over untranslated . Omissions are distinct in that they address cases where text is not present, while untranslated addresses cases where text has been carried from the source untranslated. [0]

Output: untranslated

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The translated text contains inappropriate additions. [2] The translated text contains a note from the translator to himself to look up a term; the note should have been deleted but was not. [3] T [0]

Output: addition

Internationalization Tag Set (ITS) Version 2.0


Input: [1] Content has been duplicated improperly. [2] A section of the target text was inadvertently copied twice in a copy and paste operation. [3] T [0]

Output: duplication

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text is inconsistent with itself (NB: not for use with terminology inconsistency). [2] The text states that an event happened in 1912 in one location but in another states that it happened in 1812. [3] S or T [0]

Output: inconsistency

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text contains a grammatical error (including errors of syntax and morphology). [2] The text reads "The guidelines says that users should use a static grounding strap." [3] S or T [0]

Output: grammar

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text is legally problematic (e.g., it is specific to the wrong legal system). [2] The localized text is intended for use in Thailand but includes U.S. regulatory notices. A text translated into German contains comparative advertising claims that are not allowed by German law. [3] S or T [0]

Output: legal

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text is written in the wrong linguistic register of uses slang or other language variants inappropriate to the text. [2] A financia text in U.S. English refers to dollars as "bucks". [3] S or T [0]

Output: register

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The localization contains content that does not apply to the locale for which it was prepared. [2] A text translated for the Japanese market contains call center numbers in Texas and refers to special offers available only in the U.S. [3] S or T [4] Legally inappropriate material should be classified as legal . [0]

Output: locale-specific-content

Internationalization Tag Set (ITS) Version 2.0


Input: [1] Text violates norms for the intended locale. [2] A text localized into German has dates in YYYY-MM-DD format instead of in DD.MM.YYYY. A text for the Irish market uses American-style foot and inch measurements instead of centimeters. [3] S or T [0]

Output: locale-violation

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text contains stylistic errors. [2] Company style guidelines dictates that all individuals be referred to as Mr. or Ms. with a family name, but the text refers to â€œJack Smithâ€. [3] S or T [0]

Output: style

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text contains characters that are garbled or incorrect or that are not used in the language in which the content appears. [2] A text should have a 'â€¢' but instead has a 'Â¥' sign. A text translated into German omits the umlauts over 'Ã¼', 'Ã¶', and 'Ã¤'. [3] S or T [0]

Output: characters

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text contains a misspelling. [2] A German text misspells the word "Zustellung" as "ZustellÃ¼ng". [3] S or T [0]

Output: misspelling

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text has typographical errors such as omitted/incorrect punctuation, incorrect capitalization, etc. [2] An English text has the following sentence: "The man whom, we saw, was in the Military and carried it's insignias". [3] S or T [0]

Output: typographical

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text is formatted incorrectly. [2] Warnings in the text are supposed to be set in italic face, but instead appear in bold face. Margins of the text are narrower than specified. [3] S or T [0]

Output: formatting

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The source and target text contain different named entities (dates, times, place names, individual names, etc.) [2] The name "Thaddeus Cahill" appears in an English source but is rendered as "TamaÅ¡ Cahill" in the Czech version. The date "February 9, 2007" appears in the source but the translated text has "2. September 2007". [3] S or T [0]

Output: inconsistent-entities

Internationalization Tag Set (ITS) Version 2.0


Input: [1] Numbers are inconsistent between source and target. [2] A source text states that an object is 120 cm long, but the target text says it is 129 cm. long. [3] S or T [4] Some tools may correct for differences in units of measurement to reduce false positives. [0]

Output: numbers

Internationalization Tag Set (ITS) Version 2.0


Input: [1] There is an issue related to markup or a mismatch in markup between source and target. [2] The source segment has five markup tags but the target has only two. An opening tag in the text is missing a closing tag. [3] S or T [0]

Output: markup

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The text fails to match a pattern that defines allowable content (or matches one that defines non-allowable content). [2] The tool disallows the regular expression pattern ['"â€â€™][\.,] but the translated text contains "A leading â€œexpertâ€, a political hack, claimed otherwise." [3] S or T [0]

Output: pattern-problem

Internationalization Tag Set (ITS) Version 2.0


Input: [1] There is a mismatch in whitespace between source and target content. [2] A source segment starts with six space characters but the corresponding target segment has two non-breaking spaces at the start. [3] S or T [0]

Output: whitespace

Internationalization Tag Set (ITS) Version 2.0


Input: [1] There is an issue related to the internationalization of content. [2] A line of programming code has embedded language-specific strings. A user interface element leaves no room for text expansion. A form allows only for U.S.-style postal addresses and expects five digit U.S. ZIP codes. [3] S or T [4] There are many kinds of internationalization issues. This category is therefore very heterogeneous in what it can refer to. [0]

Output: internationalization

Internationalization Tag Set (ITS) Version 2.0


Input: [1] There is a significant difference in source and target length. [2] The translation of a segment is five times as long as the source. [3] T or S [4] What constitutes a "significant" difference in length is determined by the model referred to in the locQualityIssueProfileRef . [0]

Output: length

Internationalization Tag Set (ITS) Version 2.0


Input: [1] The issue has not been categorized. [2] A new version of a tool returns information on an issue that has not been previously checked and that is not yet classified. [3] S or T [4] This category has two uses: A tool can use it to pass through quality data from another tool in cases where the issues from the other tool are not classified (for example, a localization quality assurance tool interfaces with a third-party grammar checker). A tool's issues are not yet assigned to categories, and, until an updated assignment is made, they may be listed as uncategorized . In this case it is recommended that issues be assigned to appropriate categories as soon as possible since uncategorized does not foster interoperability. [0]

Output: uncategorized

Internationalization Tag Set (ITS) Version 2.0


Input: [1] Any issue that cannot be assigned to any values listed above. [3] S or T [4] This category allows for the inclusion of any issues not included in the previously listed values. This value MUST NOT be used for any tool- or model-specific issues that can be mapped to the values listed above. In addition, this value is not synonymous with uncategorized in that uncategorized issues may be assigned to another precise value, while other issues cannot. If a system has an "miscellaneous" or "other" category, it MUST be mapped to this value even if the specific instance of the issue might be mapped to another category. [0]

Output: other

Internationalization Tag Set (ITS) Version 2.0


Input: [Category] Presentation [4] Presentation is clear and to the point, clearly describing the project problem and proposed solution. The project plan is clearly communicated, including who is accountable for which tasks, when tasks need to be done by, how we know they are completed satisfactorily. [3] Presentation is reasonably clear and to the point, describing the project problem and proposed solution. The project plan is communicated, including who is accountable for which task, when tasks need to be done by, how we know they are completed satisfactorily. [1] Presentation is long-winded, covers some description of the project problem and proposed solution but is somewhat incomplete. The project plan is communicated, but assignments, tasks timelines and quality criteria are not made clear and explicit. [2]

Output: Presentation is average, not very comprehensive or clear, describing the project problem and proposed solution. The project plan is communicated, including who is accountable for which tasks, when tasks need to be done by, how we know they are completed satisfactorily.

Es/Interact/Gestión de proyectos - Web Education Community Group


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

Output: Meeting objectives are vague, items of discussion are incomplete and somewhat actionable.

Es/Interact/Gestión de proyectos - Web Education Community Group


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

Output: Meeting runs over time, most points are covered, action items established.

Es/Interact/Gestión de proyectos - Web Education Community Group


Input: [Category] Meeting minutes [4] Minutes are readable, comprehensive, mentioning attendees, problems raised, solutions decided upon and clear action points assigned to team members. [3] Minutes are readable and fairly comprehensive, mentioning some problems raised, solutions decided upon, and clear action points. [1] Minutes are unclear, and not comprehensive, missing problems raised, solutions decided upon and lacking action points. [2]

Output: Minutes are fairly readable but not comprehensive, mentions some problem raised, some solutions decided upon and lacking clear action points.

Es/Interact/Gestión de proyectos - Web Education Community Group


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

Output: Sometimes provides useful ideas when participating in the group and in classroom discussion. Does not challenge existing ideas. A satisfactory group member who does what is required.

Es/Interact/Gestión de proyectos - Web Education Community Group


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

Output: Often listens to, shares with, and supports the efforts of others, but sometimes is not a good team member.

Es/Interact/Gestión de proyectos - Web Education Community Group


Input: [Term] agency [Description]

Output: causal attribution -- who caused the event?


Input: [Term] blame [Description]

Output: blame and credit -- part of causal attribution


Input: [Term] controllability [Description]

Output: part of coping potential


Input: [Term] changeability [Description]

Output: part of coping potential


Input: [Term] power [Description]

Output: part of coping potential


Input: [Term] adaptability [Description]

Output: part of coping potential


Input: [Event Identifier] DOMFocusIn [Description] Occurs when an element receives focus. [DOM3 event category] UIEvent [Animation event name] focusin [Cancel -able] No [uDOM interface] UIEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] DOMFocusOut [Description] Occurs when an element loses focus. [DOM3 event category] UIEvent [Animation event name] focusout [Cancel -able] No [uDOM interface] UIEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] DOMActivate [Description] Occurs when an element is activated, for instance, through a mouse click or a keypress. [DOM3 event category] UIEvent [Animation event name] activate [Cancel -able] Yes [uDOM interface] UIEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] click [Description] Occurs when the pointing device button is clicked over an element. A click is defined as a mousedown and mouseup over the same screen location. The sequence of these events is: mousedown, mouseup, click. If multiple clicks occur at the same screen location, the sequence repeats with the detail attribute incrementing with each repetition. [DOM3 event category] MouseEvent [Animation event name] click [Cancel -able] Yes [uDOM interface] MouseEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] mousedown [Description] Occurs when the pointing device button is pressed over an element. [DOM3 event category] MouseEvent [Animation event name] mousedown [Cancel -able] Yes [uDOM interface] MouseEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] mouseup [Description] Occurs when the pointing device button is released over an element. [DOM3 event category] MouseEvent [Animation event name] mouseup [Cancel -able] Yes [uDOM interface] MouseEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] mouseover [Description] Occurs when the pointing device is moved onto an element. [DOM3 event category] MouseEvent [Animation event name] mouseover [Cancel -able] Yes [uDOM interface] MouseEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] mousemove [Description] Occurs when the pointing device is moved while it is over an element. [DOM3 event category] MouseEvent [Animation event name] mousemove [Cancel -able] Yes [uDOM interface] MouseEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] mouseout [Description] Occurs when the pointing device is moved away from an element. [DOM3 event category] MouseEvent [Animation event name] mouseout [Cancel -able] Yes [uDOM interface] MouseEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] textInput [Description] One or more characters have been entered. [DOM3 event category] TextEvent [Animation event name] none [Cancel -able] Yes [uDOM interface] TextEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] keydown [Description] A key is pressed down. (The normative definition of this event is the description in the DOM3 Events specification.) [DOM3 event category] KeyboardEvent [Animation event name] none [Cancel -able] Yes [uDOM interface] KeyboardEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] keyup [Description] A key is released. (The normative definition of this event is the description in the DOM3 Events specification.) [DOM3 event category] KeyboardEvent [Animation event name] none [Cancel -able] Yes [uDOM interface] KeyboardEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] load [Description] The event is triggered at the point at which the user agent finishes loading the element and any dependent resources (such as images, style sheets, or scripts). In the case the element references a script, the event will be raised only after an attempt to interpret the script has been made. Dependent resources that fail to load will not prevent this event from firing if the element that referenced them is still accessible via the DOM unless they are designated as externalResourcesRequired. The event is independent of the means by which the element was added to DOM tree. [DOM3 event category] BasicEvent [Animation event name] load [Cancel -able] No [uDOM interface] Event [Bubbling phase]

Output: No


Input: [Event Identifier] SVGLoad [Description] This event is deprecated and is for backwards compatibility only, see notes below. This event is sent at the same time as the load event, but the load event must be sent before the SVGLoad event. [DOM3 event category] none [Animation event name] none [Cancel -able] No [uDOM interface] Event [Bubbling phase]

Output: No


Input: [Event Identifier] resize [Description] Occurs when a document view is being resized. This event is only applicable to 'svg' elements and is dispatched after the resize operation has taken place. The target of the event is the 'svg' element. [DOM3 event category] BasicEvent [Animation event name] resize [Cancel -able] No [uDOM interface] Event [Bubbling phase]

Output: Yes


Input: [Event Identifier] SVGResize [Description] This event is deprecated and is for backwards compatibility only, see notes below. This event is sent at the same time as the resize event, but the resize event must be sent before the SVGResize event. [DOM3 event category] none [Animation event name] none [Cancel -able] No [uDOM interface] Event [Bubbling phase]

Output: Yes


Input: [Event Identifier] scroll [Description] Occurs when a document view is being shifted along the X or Y or both axis, either through a direct user interaction or any change on the currentTranslate property available on SVGSVGElement interface. This event is only applicable to 'svg' elements and is dispatched after the shift modification has taken place. The target of the event is the 'svg' element. [DOM3 event category] BasicEvent [Animation event name] scroll [Cancel -able] No [uDOM interface] Event [Bubbling phase]

Output: Yes


Input: [Event Identifier] SVGScroll [Description] This event is deprecated and is for backwards compatibility only, see notes below. This event is sent at the same time as the scroll event, but the scroll event must be sent before the SVGScroll event. [DOM3 event category] none [Animation event name] none [Cancel -able] No [uDOM interface] Event [Bubbling phase]

Output: Yes


Input: [Event Identifier] SVGZoom [Description] Occurs when the zoom level of a document view is being changed, either through a direct user interaction or any change to the currentScale property available on SVGSVGElement interface. This event is only applicable to 'svg' elements and is dispatched after the zoom level modification has taken place. The target of the event is the 'svg' element. [DOM3 event category] none [Animation event name] zoom [Cancel -able] No [uDOM interface] Event [Bubbling phase]

Output: No


Input: [Event Identifier] SVGRotate [Description] Occurs when the rotation of a document view is being changed, either through a direct user interaction or any change to the currentRotate property available on SVGSVGElement interface. This event is only applicable to 'svg' elements and is dispatched after the rotation modification has taken place. The target of the event is the 'svg' element. [DOM3 event category] none [Animation event name] rotate [Cancel -able] No [uDOM interface] Event [Bubbling phase]

Output: No


Input: [Event Identifier] beginEvent [Description] Occurs when a Timed Element begins. For details, see the description of the Events and event model in SMIL 2.1. [DOM3 event category] none [Animation event name] beginEvent [Cancel -able] No [uDOM interface] TimeEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] endEvent [Description] Occurs when a Timed Element ends. For details, see the description of the Events and event model in SMIL 2.1. [DOM3 event category] none [Animation event name] endEvent [Cancel -able] No [uDOM interface] TimeEvent [Bubbling phase]

Output: Yes