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

Output: IDREF

Building XHTML Modules - Defining Abstract Modules


Input: [Definition] A name with the same character constraints as ID above [Attribute Type]

Output: NAME

Building XHTML Modules - Defining Abstract Modules


Input: [Definition] A name composed of CDATA characters but no whitespace [Attribute Type]

Output: NMTOKEN

Building XHTML Modules - Defining Abstract Modules


Input: [Definition] Multiple names composed of CDATA characters separated by whitespace [Attribute Type]

Output: NMTOKENS

Building XHTML Modules - Defining Abstract Modules


Input: [Definition] Processed character data [Attribute Type]

Output: PCDATA

Building XHTML Modules - Defining Abstract Modules


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

Output: An arbitrary string


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

Output: Text with no line breaks


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

Output: Text with no line breaks


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

Output: Text with no line breaks


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

Output: An absolute URL


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

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


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

Output: Text with no line breaks (sensitive information)


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

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


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

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


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

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


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

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


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

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


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

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


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

Output: A numerical value


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

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


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

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


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

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


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

Output: An enumerated value


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

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


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

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


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

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


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


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


Input: [Name] bargein [Description] Controls whether the prompt can be interrupted. [Required] No [Default Value] bargein property [Type]

Output: boolean

Voice Extensible Markup Language (VoiceXML) 3.0

Table 22: Attributes


Input: [Name] bargeintype [Description] On prompts that can be interrupted, determines the type of bargein, either 'speech', or 'hotword'. [Required] No [Default Value] bargeintype property [Type]

Output: string

Voice Extensible Markup Language (VoiceXML) 3.0

Table 22: Attributes


Input: [Name] cond [Description] A data model expression that must evaluate to true after conversion to boolean in order for the prompt to be played. [Required] No [Default Value] true [Type]

Output: data model expression

Voice Extensible Markup Language (VoiceXML) 3.0

Table 22: Attributes


Input: [Name] count [Description] A number indicating the repetition count, allowing a prompt to be activated or not depending on the current repetition count. [Required] No [Default Value] 1 [Type]

Output: positive integer

Voice Extensible Markup Language (VoiceXML) 3.0

Table 22: Attributes


Input: [Name] timeout [Description] The time to wait for user input. [Required] No [Default Value] timeout property [Type]

Output: Time Designation

Voice Extensible Markup Language (VoiceXML) 3.0

Table 22: Attributes


Input: [Name] xml:lang [Description] The language identifier for the prompt. [Required] No [Default Value] document's "xml:lang" attribute [Type]

Output: string

Voice Extensible Markup Language (VoiceXML) 3.0

Table 22: Attributes


Input: [Name] xml:base [Description] Declares the base URI from which relative URIs in the prompt are resolved. [Required] No [Default Value] document's "xml:base" attribute [Type]

Output: string

Voice Extensible Markup Language (VoiceXML) 3.0

Table 22: Attributes


Input: [0] 3.1 [Test Status] Shruti Malugu created tests [Assertion]

Output: The pointerType attribute of a pointerup event must have the same value as the pointerType attribute of the last pointerdown event with the same pointerId attribute.


Input: [0] 3.2 [Test Status] Shruti Malugu created tests [Assertion]

Output: The isPrimary attribute of a pointerup event must have the same value as the isPrimary attribute of the last pointerdown event with the same pointerId attribute.


Input: [0] 3.3 [Test Status] Shruti Malugu created tests [Assertion]

Output: If the input device is a mouse and the device transitions from at least one button depressed to no buttons depressed, the pointerup event must be dispatched .


Input: [0] 3.4 [Test Status] Shruti Malugu created tests [Assertion]

Output: If the input device is touch and physical contact is removed from the digitizer, the pointerup event must be dispatched.


Input: [0] 3.5 [Test Status] Shruti Malugu created tests [Assertion]

Output: If the input device is touch and the pen is removed from physical contact with the digitizer, the pointerup event must be dispatched.


Input: [0] 3.6 [Test Status] Shruti Malugu created tests [Assertion]

Output: For input devices that do not support hover, a pointerout event must follow the pointerup event. Furthermore, the pointerType and isPrimary attributes of the pointerout must be the same as the respective attributes of the corresponding pointerup event.


Input: [0] 3.7 [Assertion]

Output: If the setPointerCapture method has been invoked on the pointer specified by pointerId, and the releasePointerCapture method has not been invoked, a lostpointercapture event must be dispatched to the element on which the setPointerCapture method was invoked. Furthermore, subsequent events for the specified pointer must follow normal hit testing mechanisms for determining the event target.


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

Output: hidden


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

Output: text


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

Output: search


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

Output: tel


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

Output: url


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

Output: email


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

Output: password


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

Output: datetime


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

Output: date


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

Output: month


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

Output: week


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

Output: time


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

Output: datetime-local


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

Output: number


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

Output: range


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

Output: color


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

Output: checkbox


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

Output: radio


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

Output: file


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

Output: submit


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

Output: image


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

Output: reset


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

Output: button


Input: [0] Standards Status [Transaction Layer Security] Same as XKMS Specification [WS-Security] Approved as an OASIS Technical Committee [Payload Security]

Output: Same as XKMS specification.

XML Key Management Specification (XKMS) Part II


Input: [0] Dependencies [Transaction Layer Security] Authentication mechanism defined by TLS which clients must implement [WS-Security] Authentication mechanism defined by Web Services Infrastructure, is common to all Web Services. [Payload Security]

Output: Authentication defined by XKMS specification, client does not need to implement a comprehensive framework.

XML Key Management Specification (XKMS) Part II


Input: [0] Use of XML Signature [Transaction Layer Security] Not required [WS-Security] Uses XML Signature in Detached mode which slightly simplifies processing. [Payload Security]

Output: Uses XML Signature in Enveloped Mode requiring slightly more complex processing.

XML Key Management Specification (XKMS) Part II


Input: [0] Support for Routing [Transaction Layer Security] None [WS-Security] Model is extensible to multi-hop message routing and multi-party transactions. [Payload Security]

Output: Specification describes bi-lateral authentication only, multi-hop message routing and multi-party transactions are not supported.

XML Key Management Specification (XKMS) Part II


Input: [0] Support for Confidentiality [Transaction Layer Security] Supported [WS-Security] Confidentiality is supported through WS-Encryption [Payload Security]

Output: None, although applications may employ TLS to establish a secure channel

XML Key Management Specification (XKMS) Part II


Input: [0] Non-Repudiation [Transaction Layer Security] Requires additional payload security [WS-Security] Supported [Payload Security]

Output: Supported

XML Key Management Specification (XKMS) Part II


Input: [0] Unspecified Party Authentication [Transaction Layer Security] Requires additional payload security [WS-Security] Supported [Payload Security]

Output: Supported

XML Key Management Specification (XKMS) Part II


Input: [0] Client Authentication [Transaction Layer Security] Supported through certificate client authentication or through use of payload security. [WS-Security] Supported [Payload Security]

Output: Supported

XML Key Management Specification (XKMS) Part II


Input: [Attribute Type] CDATA [Definition]

Output: Character data

Building XHTML Modules - Defining Abstract Modules


Input: [Attribute Type] ID [Definition]

Output: A document-unique identifier

Building XHTML Modules - Defining Abstract Modules


Input: [Attribute Type] IDREF [Definition]

Output: A reference to a document-unique identifier

Building XHTML Modules - Defining Abstract Modules


Input: [Attribute Type] NAME [Definition]

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

Building XHTML Modules - Defining Abstract Modules


Input: [Attribute Type] NMTOKEN [Definition]

Output: A name composed of CDATA characters but no whitespace

Building XHTML Modules - Defining Abstract Modules


Input: [Attribute Type] NMTOKENS [Definition]

Output: Multiple names composed of CDATA characters separated by whitespace

Building XHTML Modules - Defining Abstract Modules


Input: [Attribute Type] PCDATA [Definition]

Output: Processed character data

Building XHTML Modules - Defining Abstract Modules


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

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

Voice Extensible Markup Language (VoiceXML) 3.0

Table 10: Attributes


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

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

Voice Extensible Markup Language (VoiceXML) 3.0

Table 10: Attributes


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

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

Voice Extensible Markup Language (VoiceXML) 3.0

Table 10: Attributes


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

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

Voice Extensible Markup Language (VoiceXML) 3.0

Table 10: Attributes


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

Output: Indicates that the document is willing to use content whose age is no greater than the specified time in seconds (cf. 'max-age' in HTTP 1.1 [RFC2616]). The document is not willing to use stale content, unless maxstale is also provided.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 10: Attributes


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

Output: Indicates that the document is willing to use content that has exceeded its expiration time (cf. 'max-stale' in HTTP 1.1 [RFC2616]). If maxstale is assigned a value, then the document is willing to accept content that has exceeded its expiration time by no more than the specified number of seconds.

Voice Extensible Markup Language (VoiceXML) 3.0

Table 10: Attributes


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 Textual content of element, including content of child elements, but excluding attributes [Overriding XML examples] Yes local , global [HTML5 examples] tbd local , global [Local Usage]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Ruby [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] None None [Overriding XML examples] Not applicable local , global [HTML5 examples] tbd [Local Usage]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: No

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Domain [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] None Textual content of element, including attributes and child elements [Overriding XML examples] Yes global [HTML5 examples] tbd global [Local Usage]

Output: No

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Disambiguation [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] None None [Overriding XML examples] Not applicable local , global [HTML5 examples] tbd local , global [Local Usage]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Locale Filter [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] localeFilterList="*" Textual content of element, including attributes and child elements [Overriding XML examples] local , global [HTML5 examples] local , global [Local Usage]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Translation Agent Provenance [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] None Textual content of element, including child elements, but excluding attributes [Overriding XML examples] tbd [HTML5 examples] tbd [Local Usage]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] External Resource [Global, rule-based selection] Yes [Global adding of information] No Yes [Default Values] None None [Overriding XML examples] Not applicable global [HTML5 examples] tbd global [Local Usage]

Output: No

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Target Pointer [Global, rule-based selection] Yes [Global adding of information] No Yes [Default Values] None None [Overriding XML examples] Not applicable global [HTML5 examples] tbd global [Local Usage]

Output: No

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Id Value [Global, rule-based selection] Yes [Global adding of information] No Yes [Default Values] None None [Overriding XML examples] Not applicable global [HTML5 examples] tbd global [Local Usage]

Output: No

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Preserve Space [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] default Textual content of element, including attributes and child elements [Overriding XML examples] Yes local , global [HTML5 examples] tbd n/a [Local Usage]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Localization Quality PrÃ©cis [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] None Textual content of element, including child elements, but excluding attributes [Overriding XML examples] tbd [HTML5 examples] tbd [Local Usage]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] MT Confidence [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] None Textual content of element, including child elements, but excluding attributes [Overriding XML examples] tbd [HTML5 examples] tbd [Local Usage]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Allowed Characters [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] None Textual content of element, including child elements, but excluding attributes [Overriding XML examples] tbd [HTML5 examples] tbd [Local Usage]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Storage Size [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] storageEncoding="UTF-8" None [Overriding XML examples] tbd [HTML5 examples] tbd [Local Usage]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Property] clear [Values] none | left | right | both [Initial] none [Applies to] block-level elements [Inh.] no [Media] visual [Percentages]


Input: [Property] display [Values] inline | block | inline-block | list-item | run-in | compact | table | inline-table | table-row-group | table-header-group | table-footer-group | table-row | table-column-group | table-column | table-cell | table-caption | ruby | ruby-base | ruby-text | ruby-base-group | ruby-text-group | | none [Initial] inline [Applies to] all elements [Inh.] no [Media] visual (‘none’ applies to all media) [Percentages]


Input: [Property] float [Values] left | right | none | [Initial] none [Applies to] all, but see 9.7 [Inh.] no [Media] visual [Percentages]


Input: [Property] height [Values] | | auto [Initial] auto [Applies to] all elements but non-replaced inline elements, table columns, and column groups [Inh.] no [Media] visual [Percentages]

Output: see prose


Input: [Property] margin [Values] [ | | auto ]{1,4} [Initial] (see individual properties) [Applies to] see text [Inh.] no [Media] visual [Percentages]

Output: width* of containing block


Input: [Property] margin-top , margin-right, margin-bottom, margin-left [Values] | | auto [Initial] 0 [Applies to] see text [Inh.] no [Media] visual [Percentages]

Output: width* of containing block


Input: [Property] marquee-direction [Values] forward | reverse [Initial] reverse [Applies to] same as ‘overflow’ [Inh.] yes [Media] visual [Percentages]


Input: [Property] marquee-loop [Values] | infinite [Initial] 1 [Applies to] same as ‘overflow’ [Inh.] no [Media] visual [Percentages]


Input: [Property] marquee-speed [Values] slow | normal | fast [Initial] normal [Applies to] same as ‘overflow’ [Inh.] no [Media] visual [Percentages]


Input: [Property] marquee-style [Values] scroll | slide | alternate [Initial] scroll [Applies to] same as ‘overflow’ [Inh.] no [Media] visual [Percentages]


Input: [Property] max-width, max-height [Values] | | none [Initial] none [Applies to] all elements but non-replaced inline elements, table rows, and row groups [Inh.] no [Media] visual [Percentages]

Output: refer to width, resp. height of containing block


Input: [Property] min-width, min-height [Values] | | inherit [Initial] 0 [Applies to] all elements but non-replaced inline elements, table rows, and row groups [Inh.] no [Media] visual [Percentages]

Output: refer to width, resp. height of containing block


Input: [Property] overflow [Values] [ visible | hidden | scroll | auto | no-display | no-content ]{1,2} [Initial] see individual properties [Applies to] non-replaced block-level elements and non-replaced ‘inline-block’ elements [Inh.] no [Media] visual [Percentages]


Input: [Property] overflow-style [Values] auto | [scrollbar | panner | move | marquee] [, [scrollbar | panner | move | marquee]]* [Initial] auto [Applies to] same as ‘overflow’ [Inh.] yes [Media] visual [Percentages]


Input: [Property] overflow-x, overflow-y, [Values] visible | hidden | scroll | auto | no-display | no-content [Initial] visible [Applies to] non-replaced block-level elements and non-replaced ‘inline-block’ elements [Inh.] no [Media] visual [Percentages]


Input: [Property] padding [Values] [ | ]{1,4} [Initial] (see individual properties) [Applies to] all elements [Inh.] no [Media] visual [Percentages]

Output: width* of containing block


Input: [Property] padding-top , padding-right, padding-bottom, padding-left [Values] [ | ] [Initial] 0 [Applies to] all elements [Inh.] no [Media] visual [Percentages]

Output: width* of containing block


Input: [Property] rotation [Initial] 0 [Applies to] block-level elements, inline-table and inline-block [Inh.] no [Media] visual [Percentages]


Input: [Property] rotation-point [Initial] 50% 50% [Applies to] block-level elements [Inh.] no [Media] visual [Percentages]

Output: Width and height of border box


Input: [Property] visibility [Values] visible | hidden | collapse [Initial] visible [Applies to] all elements [Inh.] yes [Media] visual [Percentages]


Input: [Property] width [Values] | | auto [Initial] auto [Applies to] all elements but non-replaced inline elements, table rows, and row groups [Inh.] no [Media] visual [Percentages]

Output: refer to width of containing block


Input: [Requirement] Some [Comments] The information provided by an XKMS service may be confidential, the fact that a party has requested particular information from an XKMS service may allow confidential information to be deduced. Many XKMS applications do not require confidentiality however. [Security Issue]

Output: Confidentiality

XML Key Management Specification (XKMS) Part II


Input: [Requirement] Some [Comments] A service only needs to authenticate a request for information if either the information is confidential or some form of charge is to be made for use of the service. [Security Issue]

Output: Request Authentication

XML Key Management Specification (XKMS) Part II


Input: [Requirement] Most [Comments] An XKMS service that provides only a Location service for self authenticating key information such as Digital Certificates does not require authentication. [Security Issue]

Output: Response Authentication

XML Key Management Specification (XKMS) Part II


Input: [Requirement] Some [Comments] Although some XKMS applications have a specific requirement to support Non-Repudiation, the ability to repudiate requests and responses is acceptable in many applications. [Security Issue]

Output: Transitive Authentication

XML Key Management Specification (XKMS) Part II


Input: [Requirement] All [Comments] The RequestID correspondence mechanism can only be used if the Request Authentication mechanism can be relied upon. Otherwise the Digest Mechanism should be used. [Security Issue]

Output: Message Correspondence

XML Key Management Specification (XKMS) Part II


Input: [Requirement] Some [Comments] Request replay attacks are likely to only be a concern if the service charges on a per request basis or as a type of Denial of Service attack. [Security Issue]

Output: Request Replay

XML Key Management Specification (XKMS) Part II


Input: [Requirement] Most [Comments] Any service made available on a public network is likely to be subject to a Denial of Service attack. The risk of a Denial of Service attack is generally considered to be reduced on closed networks such as internal enterprise networks. [Security Issue]

Output: Denial of Service

XML Key Management Specification (XKMS) Part II


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 Textual content of element, including content of child elements, but excluding attributes [Overriding XML examples] Yes local , global [HTML5 examples] tbd local , global

Output: No

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: No

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Ruby [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes [Default Values] None None [Overriding XML examples] Not applicable local , global [HTML5 examples] tbd

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Elements Within Text [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes [Default Values] withinText="no" None [Overriding XML examples] Not applicable local , global [HTML5 examples] tbd local , global

Output: No

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Domain [Local Usage] No [Global, rule-based selection] Yes [Global adding of information] Yes [Default Values] None Textual content of element, including attributes and child elements [Overriding XML examples] Yes global [HTML5 examples] tbd global

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Disambiguation [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes [Default Values] None None [Overriding XML examples] Not applicable local , global [HTML5 examples] tbd local , global

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Locale Filter [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes [Default Values] localeFilterList="*" Textual content of element, including attributes and child elements [Overriding XML examples] local , global [HTML5 examples] local , global

Output: No

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Translation Agent Provenance [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes [Default Values] None Textual content of element, including child elements, but excluding attributes [Overriding XML examples] tbd [HTML5 examples] tbd

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] External Resource [Local Usage] No [Global, rule-based selection] Yes [Global adding of information] No [Default Values] None None [Overriding XML examples] Not applicable global [HTML5 examples] tbd global

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Target Pointer [Local Usage] No [Global, rule-based selection] Yes [Global adding of information] No [Default Values] None None [Overriding XML examples] Not applicable global [HTML5 examples] tbd global

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Id Value [Local Usage] No [Global, rule-based selection] Yes [Global adding of information] No [Default Values] None None [Overriding XML examples] Not applicable global [HTML5 examples] tbd global

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Preserve Space [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes [Default Values] default Textual content of element, including attributes and child elements [Overriding XML examples] Yes local , global [HTML5 examples] tbd n/a

Output: No

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Localization Quality PrÃ©cis [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes [Default Values] None Textual content of element, including child elements, but excluding attributes [Overriding XML examples] tbd [HTML5 examples] tbd

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] MT Confidence [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes [Default Values] None Textual content of element, including child elements, but excluding attributes [Overriding XML examples] tbd [HTML5 examples] tbd

Output: No

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Allowed Characters [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes [Default Values] None Textual content of element, including child elements, but excluding attributes [Overriding XML examples] tbd [HTML5 examples] tbd

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Storage Size [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes [Default Values] storageEncoding="UTF-8" None [Overriding XML examples] tbd [HTML5 examples] tbd

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [Type] NotFoundError [Message (Optional)]

Output: The operation failed because the requested database object could not be found. For example, an object store did not exist but was being opened.


Input: [Type] InvalidStateError [Message (Optional)]

Output: An operation was called on an object on which it is not allowed or at a time when it is not allowed. Also occurs if a request is made on a source object that has been deleted or removed. Use TransactionInactiveError or ReadOnlyError when possible, as they are more specific variations of InvalidStateError.


Input: [Type] InvalidAccessError [Message (Optional)]

Output: An invalid operation was performed on an object. For example transaction creation attempt was made, but an empty scope was provided.


Input: [Type] AbortError [Message (Optional)]

Output: A request was aborted, for example through a call to IDBTransaction.abort.


Input: [Type] TimeoutError [Message (Optional)]

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


Input: [Type] QuotaExceededError [Message (Optional)]

Output: The operation 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: [Type] SyntaxError [Message (Optional)]

Output: The keypath argument contains an invalid key path.


Input: [Type] DataCloneError [Message (Optional)]

Output: The data being stored could not be cloned by the internal structured cloning algorithm.


Input: [Event Name] dragstart [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [effectAllowed] uninitialized [dropEffect] none [Default Action] Initiate the drag-and-drop operation [dataTransfer]

Output: Contains source node unless a selection is being dragged, in which case it is empty


Input: [Event Name] drag [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [effectAllowed] Same as last event [dropEffect] none [Default Action] Continue the drag-and-drop operation [dataTransfer]

Output: Empty


Input: [Event Name] dragenter [Target] Immediate user selection or the body element [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [effectAllowed] Same as last event [dropEffect] Based on effectAllowed value [Default Action] Reject immediate user selection as potential target element [dataTransfer]

Output: Empty


Input: [Event Name] dragleave [Target] Previous target element [Bubbles?] ✓ Bubbles [Cancelable?] — [effectAllowed] Same as last event [dropEffect] none [Default Action] None [dataTransfer]

Output: Empty


Input: [Event Name] dragover [Target] Current target element [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [effectAllowed] Same as last event [dropEffect] Based on effectAllowed value [Default Action] Reset the current drag operation to "none" [dataTransfer]

Output: Empty


Input: [Event Name] drop [Target] Current target element [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [effectAllowed] Same as last event [dropEffect] Current drag operation [Default Action] Varies [dataTransfer]

Output: getData() returns data set in dragstart event


Input: [Event Name] dragend [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] — [effectAllowed] Same as last event [dropEffect] Current drag operation [Default Action] Varies [dataTransfer]

Output: Empty


Input: [Attribute Type] CDATA [Definition]

Output: Character data


Input: [Attribute Type] ID [Definition]

Output: A document-unique identifier


Input: [Attribute Type] IDREF [Definition]

Output: A reference to a document-unique identifier


Input: [Attribute Type] IDREFS [Definition]

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


Input: [Attribute Type] NAME [Definition]

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


Input: [Attribute Type] NMTOKEN [Definition]

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


Input: [Attribute Type] NMTOKENS [Definition]

Output: One or more white space separated NMTOKEN values


Input: [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Contains source node unless a selection is being dragged, in which case it is empty [effectAllowed] uninitialized [dropEffect] none [Default Action] Initiate the drag-and-drop operation [Event Name]

Output: dragstart


Input: [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] none [Default Action] Continue the drag-and-drop operation [Event Name]

Output: drag


Input: [Target] Immediate user selection or the body element [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] Based on effectAllowed value [Default Action] Reject immediate user selection as potential target element [Event Name]

Output: dragenter


Input: [Target] Previous target element [Bubbles?] ✓ Bubbles [Cancelable?] — [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] none [Default Action] None [Event Name]

Output: dragleave


Input: [Target] Current target element [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] Based on effectAllowed value [Default Action] Reset the current drag operation to "none" [Event Name]

Output: dragover


Input: [Target] Current target element [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] getData() returns data set in dragstart event [effectAllowed] Same as last event [dropEffect] Current drag operation [Default Action] Varies [Event Name]

Output: drop


Input: [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] — [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] Current drag operation [Default Action] Varies [Event Name]

Output: dragend


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: [Definition] Character data [Attribute Type]

Output: CDATA


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

Output: ID


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

Output: IDREF


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

Output: IDREFS


Input: [Definition] A name with the same character constraints as ID above [Attribute Type]

Output: NAME


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

Output: NMTOKEN


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

Output: NMTOKENS


Input: [Event Name] dragstart [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Contains source node unless a selection is being dragged, in which case it is empty [effectAllowed] uninitialized [Default Action] Initiate the drag-and-drop operation [dropEffect]


Input: [Event Name] drag [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Empty [effectAllowed] Same as last event [Default Action] Continue the drag-and-drop operation [dropEffect]


Input: [Event Name] dragenter [Target] Immediate user selection or the body element [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Empty [effectAllowed] Same as last event [Default Action] Reject immediate user selection as potential target element [dropEffect]

Output: Based on effectAllowed value


Input: [Event Name] dragleave [Target] Previous target element [Bubbles?] ✓ Bubbles [Cancelable?] — [dataTransfer] Empty [effectAllowed] Same as last event [Default Action] None [dropEffect]


Input: [Event Name] dragover [Target] Current target element [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Empty [effectAllowed] Same as last event [Default Action] Reset the current drag operation to "none" [dropEffect]

Output: Based on effectAllowed value


Input: [Event Name] drop [Target] Current target element [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] getData() returns data set in dragstart event [effectAllowed] Same as last event [Default Action] Varies [dropEffect]

Output: Current drag operation


Input: [Event Name] dragend [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] — [dataTransfer] Empty [effectAllowed] Same as last event [Default Action] Varies [dropEffect]

Output: Current drag operation


Input: [Id: Title] wd-1 : QA Editorial Comments [State] agreed [Type] editorial [Ack.]

Output: No reply from reviewer


Input: [Id: Title] wd-2 : Normative vs. Informative [State] agreed [Type] editorial [Ack.]

Output: No reply from reviewer


Input: [Id: Title] wd-4 : Incomplete Conformance Section [State] agreed [Type] editorial [Ack.]

Output: No reply from reviewer


Input: [Id: Title] wd-17 : SCP ambiguity, sigh [State] agreed [Type] proposal [Ack.]

Output: No response to reviewer


Input: [Id: Title] wd-5 : The schema designator URI should be dereferenceable [State] agreed [Type] request [Ack.]

Output: No reply from reviewer


Input: [Id: Title] wd-6 : The Schema URI SHOULD be used [State] agreed [Type] request [Ack.]

Output: No reply from reviewer


Input: [Id: Title] wd-7 : Compatibility with XPath [State] agreed [Type] request [Ack.]

Output: No response to reviewer


Input: [Id: Title] wd-8 : Drop or Change Query Use Case [State] agreed [Type] request [Ack.]

Output: No response to reviewer


Input: [Id: Title] wd-9 : Change syntax for model group step [State] agreed [Type] request [Ack.]

Output: No response to reviewer


Input: [Id: Title] wd-10 : Support for redefined component's predecessor [State] agreed [Type] request [Ack.]

Output: No response to reviewer


Input: [Id: Title] wd-11 : Specify a canonical namespace prefix? [State] agreed [Type] request [Ack.]

Output: No response to reviewer


Input: [Id: Title] wd-12 : Allow type(*) and element(*)? [State] agreed [Type] request [Ack.]

Output: No response to reviewer


Input: [Id: Title] wd-13 : Interaction of expanded traversals with // [State] agreed [Type] request [Ack.]

Output: No response to reviewer


Input: [Id: Title] wd-15 : Interaction of elided steps with extended traversals [State] agreed [Type] request [Ack.]

Output: No response to reviewer


Input: [Id: Title] wd-16 : Short for syntax for type(qname) [State] agreed [Type] request [Ack.]

Output: No response to reviewer


Input: [Event Name] dragstart [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Contains source node unless a selection is being dragged, in which case it is empty [effectAllowed] uninitialized [dropEffect] none [Default Action]

Output: Initiate the drag-and-drop operation


Input: [Event Name] drag [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] none [Default Action]

Output: Continue the drag-and-drop operation


Input: [Event Name] dragenter [Target] Immediate user selection or the body element [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] Based on effectAllowed value [Default Action]

Output: Reject immediate user selection as potential target element


Input: [Event Name] dragleave [Target] Previous target element [Bubbles?] ✓ Bubbles [Cancelable?] — [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] none [Default Action]


Input: [Event Name] dragover [Target] Current target element [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] Based on effectAllowed value [Default Action]

Output: Reset the current drag operation to "none"


Input: [Event Name] drop [Target] Current target element [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [dataTransfer] getData() returns data set in dragstart event [effectAllowed] Same as last event [dropEffect] Current drag operation [Default Action]

Output: Varies


Input: [Event Name] dragend [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] — [dataTransfer] Empty [effectAllowed] Same as last event [dropEffect] Current drag operation [Default Action]

Output: Varies


Input: 1. A method of distributing content, comprising: creating a cryptographic hash of at least a portion of content; creating a ticket file including the cryptographic hash; and distributing the ticket file to a user system.

Output: WARP does not make use of any cryptographic information. WARP does not create a ticket file including the cryptographic hash. WARP does not distribute a ticket file to a user system or anything to the system.

WARP: Widgets Access Request Policy: PAG Report

Claims of the '1146 Application and WARP Features

Evaluation against the WARP Specification


Input: 2. The method of claim 1, where creating a ticket file comprises: including in the ticket file information relating to downloading the content from a distribution site over the network; digitally signing the ticket file; receiving a request for the content from the user system; and sending the user system the ticket file separate from the content.

Output: WARP does nothing relating to the above

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 3. The method of claim 1, further comprising: receiving notification from the user system that verification of the digital signature has failed; and initiating a security action in response to the notification.

Output: WARP does not make use of digital signatures.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 4. The method of claim 3, where initiating a security action comprises: initiating a revocation service.

Output: WARP has no relation to initializing revocation services.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 5. The method of claim 3, where initiating a security action comprises: preventing user systems from downloading the content.

Output: WARP does not rely in cryptographic methods to prevent user systems from downloading content.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 6. A method of downloading content from a network, comprising: sending a request for content to a content aggregator site; and receiving from the content aggregator site a digitally signed ticket file including a first cryptographic hash of at least a portion of content.

Output: WARP does not download any content. WARP does not make use of any cryptographic hashes or any cryptography.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 7. The method of claim 6, further comprising: downloading the content to a user system over a network, where the content is downloaded separately from the ticket file; and verifying the digital signature of the ticket file.

Output: WARP has no relationship to digital signatures or ticket files.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 8. The method of claim 7, where verifying the digital signature comprises: creating a second cryptographic hash of the downloaded content; comparing the second cryptographic hash with the first cryptographic hash; and if the hashes do not match, initiating a security action.

Output: See above 7.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 9. The method of claim 8, where initiating a security action comprises: deleting the content from the user system. WARP does not interact with the user's system.

Output: WARP does not have the ability to demand that, or have any provisions that would require, content be deleted from the user's system.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 10. The method of claim 8, where initiating a security action comprises: notifying the content aggregator site of a failed verification if the hashes do not match; and receiving a command for revoking the digital signature of the ticket file.

Output: WARP has no means to contact other sites on failure.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 11. The method of claim 8, where initiating a security action comprises: scanning the user system for instances of revoked content.

Output: WARP most definitely does not have any provisions to scan the user's hard drive deleting content

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 12. The method of claim 1, further comprising: creating a security log on the user system that includes a history of content installation

Output: WARP does not write anything to the user's hard drive or do any privacy violating things like keeping records of stuff on user's hard drives.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 13. A computer-readable medium having stored thereon instructions which, when executed by a processor, causes the processor to perform the operations of: creating a cryptographic hash of at least a portion of content; creating a ticket file including the cryptographic hash; and distributing the ticket file to a user system.

Output: WARP does not cryptographically do anything… specially nothing relating to content.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 14. The computer-readable medium of claim 13, where creating a ticket file comprises: including in the ticket file information relating to downloading the content from a distribution site over the network; digitally signing the ticket file; receiving a request for the content from the user system; and sending the user system the ticket file separate from the content.

Output: WARP does not cryptographically do anything… specially nothing relating to content.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 15. The computer-readable medium of claim 13, further comprising: receiving notification from the user system that verification of the digital signature has failed; and initiating a security action in response to the notification.

Output: WARP has nothing to do with digital signatures or events based on signatures failing of being verified.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 16. The computer-readable medium of claim 15, where initiating a security action comprises: initiating a revocation service.

Output: WARP has nothing to do with digital signatures or events based on signatures failing of being verified.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 17. The computer-readable medium of claim 15, where initiating a security action comprises: preventing user systems from downloading the content.

Output: WARP has nothing to do with digital signatures or events based on signatures failing of being verified. Hence this does not apply.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 18. A computer-readable medium having stored thereon instructions which, when executed by a processor, causes the processor to perform the operations of: sending a request for content to a content aggregator site; and receiving from the content aggregator site a digitally signed ticket file including a first cryptographic hash of at least a portion of content.

Output: WARP does not access content.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 19. The computer-readable medium of claim 18, further comprising: downloading the content to a user system over a network, where the content is downloaded separately from the ticket file; and verifying the digital signature of the ticket file.

Output: WARP does not access content. WARP does not download or deal with ticket files.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 20. The computer-readable medium of claim 18, where verifying the digital signature comprises: creating a second cryptographic hash of the downloaded content; comparing the second cryptographic hash with the first cryptographic hash; and if the hashes do not match, initiating a security action.

Output: WARP does not do any cryptographic checks.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 21. The computer-readable medium of claim 20, where initiating a security action comprises: deleting the content from the user system.

Output: WARP does not do any cryptographic checks. WARP does not do deletion of people's content.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 22. The computer-readable medium of claim 20, where initiating a security action comprises: notifying the content aggregator site of a failed verification if the hashes do not match; and receiving a command for revoking the digital signature of the ticket file.

Output: WARP does not do any cryptographic checks.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 23. The computer-readable medium of claim 20, where initiating a security action comprises: scanning the user system for instances of revoked content.

Output: WARP does not do any cryptographic checks. WARP does not do deletion of people's content.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 24. The computer-readable medium of claim 18, further comprising: creating a security log on the user system that includes a history of content installation.

Output: WARP does not write log files about their computer's content. WARP does not generate security logs.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 25. A method of installing content, comprising: receiving content from a content distributor, the content including a first cryptographic hash of the content; creating a second cryptographic hash of the content; comparing the second cryptographic hash with the first cryptographic hash; and if the hashes do not match, initiating a security action.

Output: WARP does not do this as it does not do any cryptographic checks.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: 26. The method of claim 25, further comprising: comparing the content to one or more lists of content to determine if the content can be safely installed.

Output: WARP does not do this. it has nothing to do with content installation.

WARP: Widgets Access Request Policy: PAG Report

Evaluation against the WARP Specification


Input: [General tool] HTML to Text converter [,shortcut] ,text [Access control] Same as the document [For this page]

Output: A plain text version of the page, handy for pasting into email.


Input: [General tool] Link Checker [,shortcut] ,checklink [Access control] Same as the document [For this page]

Output: List of bad links in the page


Input: [General tool] Link Checker [,shortcut] ,rchecklink [Access control] Same as the document [For this page]

Output: Bad links in a page and in pages linked from it


Input: [General tool] HTML Validator [,shortcut] ,validate [Access control] Same as the document [For this page]

Output: List of HTML markup errors.


Input: [General tool] W3C Spellchecker [,shortcut] ,spell [Access control] Same as the document [For this page]

Output: List of spelling errors.


Input: [General tool] CSS Validator [,shortcut] ,cssvalidate [Access control] Works only on public pages. [For this page]

Output: List of style CSS errors.


Input: [General tool] CVS Log [,shortcut] ,cvslog [Access control] Public on dev.w3.org, Team-only on www.w3.org [For this page]

Output: Log of changes to the document


Input: [General tool] Headers [,shortcut] ,headers [Access control] Same as the document [For this page]

Output: HTTP headers sent by the server


Input: [General tool] the pubrules checker [,shortcut] ,pubrules [Access control] Same as the document [For this page]

Output: Check the compliance of this document to the W3C publication rules


Input: [General tool] the pubrules checker [,shortcut] ,pubruleserrors [Access control] Same as the document [For this page]

Output: Check the compliance of this document to the W3C publication rules, only displaying errors


Input: [0] 5.1 [Assertion]

Output: The pointerType attribute of a pointermove event must have the same value as the pointerType attribute of the last pointerdown event with the same pointerId attribute.


Input: [0] 5.2 [Assertion]

Output: The isPrimary attribute of a pointermove event must have the same value as the isPrimary attribute of the last pointerdown event with the same pointerId attribute.


Input: [0] 5.3 [Assertion]

Output: When a pointer changes coordinates, the pointermove event must be dispatched.


Input: [0] 5.4 [Assertion]

Output: When a pointer changes button state, the pointermove event must be dispatched.


Input: [0] 5.5 [Assertion]

Output: When a pointer changes pressure, the pointermove event must be dispatched.


Input: [0] 5.6 [Assertion]

Output: When a pointer changes tilt (tiltX, tiltY), the pointermove event must be dispatched.


Input: [0] 5.7 [Assertion]

Output: When a pointer changes contact geometry (width, height), the pointermove event must be dispatched.


Input: [0] 5.8 [Assertion]

Output: If pointerType is "mouse" and no mouse button is depressed, then the button attribute of the pointermove event must be -1 and the buttons attribute must be 0.


Input: [Security Issue] Confidentiality [Requirement] Some [Comments]

Output: The information provided by an XKMS service may be confidential, the fact that a party has requested particular information from an XKMS service may allow confidential information to be deduced. Many XKMS applications do not require confidentiality however.

XML Key Management Specification (XKMS) Part II


Input: [Security Issue] Request Authentication [Requirement] Some [Comments]

Output: A service only needs to authenticate a request for information if either the information is confidential or some form of charge is to be made for use of the service.

XML Key Management Specification (XKMS) Part II


Input: [Security Issue] Response Authentication [Requirement] Most [Comments]

Output: An XKMS service that provides only a Location service for self authenticating key information such as Digital Certificates does not require authentication.

XML Key Management Specification (XKMS) Part II


Input: [Security Issue] Transitive Authentication [Requirement] Some [Comments]

Output: Although some XKMS applications have a specific requirement to support Non-Repudiation, the ability to repudiate requests and responses is acceptable in many applications.

XML Key Management Specification (XKMS) Part II


Input: [Security Issue] Message Correspondence [Requirement] All [Comments]

Output: The RequestID correspondence mechanism can only be used if the Request Authentication mechanism can be relied upon. Otherwise the Digest Mechanism should be used.

XML Key Management Specification (XKMS) Part II


Input: [Security Issue] Request Replay [Requirement] Some [Comments]

Output: Request replay attacks are likely to only be a concern if the service charges on a per request basis or as a type of Denial of Service attack.

XML Key Management Specification (XKMS) Part II


Input: [Security Issue] Denial of Service [Requirement] Most [Comments]

Output: Any service made available on a public network is likely to be subject to a Denial of Service attack. The risk of a Denial of Service attack is generally considered to be reduced on closed networks such as internal enterprise networks.

XML Key Management Specification (XKMS) Part II


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

Output: false

Static Context Components for use-when Expressions


Input: [Component] In scope namespaces [Value]

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


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

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


Input: [Component] Default function namespace [Value]

Output: The standard function namespace


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

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


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


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


Input: [Component] In scope variables [Value]


Input: [Component] In scope functions [Value]

Output: The core functions defined in [Functions and Operators], together with the functions element-available, function-available, type-available, and system-property defined in this specification, plus the set of extension functions that are present in the static context of every XPath expression (other than a use-when expression) within the content of the element that is the parent of the use-when attribute. Note that stylesheet functions are not included in the context, which means that the function function-available will return false in respect of such functions. The effect of this rule is to ensure that function-available returns true in respect of functions that can be called within the scope of the use-when attribute. It also has the effect that these extensions functions will be recognized within the use-when attribute itself; however, the fact that a function is available in this sense gives no guarantee that a call on the function will succeed.


Input: [Component] In scope collations [Value]

Output: Implementation-defined


Input: [Component] Default collation [Value]

Output: The Unicode Codepoint Collation


Input: [Component] Base URI [Value]

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


Input: [Component] Statically known documents [Value]


Input: [Component] Statically known collections [Value]


Input: [For this page] A plain text version of the page, handy for pasting into email. [,shortcut] ,text [Access control] Same as the document [General tool]

Output: HTML to Text converter


Input: [For this page] List of bad links in the page [,shortcut] ,checklink [Access control] Same as the document [General tool]

Output: Link Checker


Input: [For this page] Bad links in a page and in pages linked from it [,shortcut] ,rchecklink [Access control] Same as the document [General tool]

Output: Link Checker


Input: [For this page] List of HTML markup errors. [,shortcut] ,validate [Access control] Same as the document [General tool]

Output: HTML Validator


Input: [For this page] List of spelling errors. [,shortcut] ,spell [Access control] Same as the document [General tool]

Output: W3C Spellchecker


Input: [For this page] List of style CSS errors. [,shortcut] ,cssvalidate [Access control] Works only on public pages. [General tool]

Output: CSS Validator


Input: [For this page] Log of changes to the document [,shortcut] ,cvslog [Access control] Public on dev.w3.org, Team-only on www.w3.org [General tool]

Output: CVS Log


Input: [For this page] HTTP headers sent by the server [,shortcut] ,headers [Access control] Same as the document [General tool]

Output: Headers


Input: [For this page] Check the compliance of this document to the W3C publication rules [,shortcut] ,pubrules [Access control] Same as the document [General tool]

Output: the pubrules checker


Input: [For this page] Check the compliance of this document to the W3C publication rules, only displaying errors [,shortcut] ,pubruleserrors [Access control] Same as the document [General tool]

Output: the pubrules checker


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

Output: Notes

Internationalization Tag Set (ITS) Version 2.0


Input: [0] mistranslation [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]

Output: Issues related to translation of specific terms related to the domain or task-specific language should be categorized as terminology issues.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] omission [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]

Output: This type should not be used for missing whitespace or formatting codes, but instead should be reserved for linguistic content.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] untranslated [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]

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

Internationalization Tag Set (ITS) Version 2.0


Input: [0] locale-specific-content [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]

Output: Legally inappropriate material should be classified as legal .

Internationalization Tag Set (ITS) Version 2.0


Input: [0] numbers [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]

Output: Some tools may correct for differences in units of measurement to reduce false positives.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] internationalization [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]

Output: There are many kinds of internationalization issues. This category is therefore very heterogeneous in what it can refer to.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] length [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]

Output: What constitutes a "significant" difference in length is determined by the model referred to in the locQualityIssueProfileRef . .

Internationalization Tag Set (ITS) Version 2.0


Input: [0] uncategorized [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]

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

Internationalization Tag Set (ITS) Version 2.0


Input: [0] other [1] Any issue that cannot be assigned to any values listed above. [3] S or T [4]

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

Internationalization Tag Set (ITS) Version 2.0


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

Output: No conflict

Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP) - Linked Data Platform


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

Output: No conflict; added LDP headers

Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP) - Linked Data Platform


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

Output: No conflict; added LDP headers

Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP) - Linked Data Platform


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

Output: No conflict

Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP) - Linked Data Platform


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

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

Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP) - Linked Data Platform


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

Output: No conflict

Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP) - Linked Data Platform


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

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

Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP) - Linked Data Platform


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

Output: mode

Voice Extensible Markup Language (VoiceXML) 3.0

Table 10: Attributes


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

Output: weight

Voice Extensible Markup Language (VoiceXML) 3.0

Table 10: Attributes


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

Output: fetchhint

Voice Extensible Markup Language (VoiceXML) 3.0

Table 10: Attributes


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

Output: fetchtimeout

Voice Extensible Markup Language (VoiceXML) 3.0

Table 10: Attributes


Input: [Type] An unsigned integer [Description] Indicates that the document is willing to use content whose age is no greater than the specified time in seconds (cf. 'max-age' in HTTP 1.1 [RFC2616]). The document is not willing to use stale content, unless maxstale is also provided. [Required] No [Default Value] None [Name]

Output: maxage

Voice Extensible Markup Language (VoiceXML) 3.0

Table 10: Attributes


Input: [Type] An unsigned integer [Description] Indicates that the document is willing to use content that has exceeded its expiration time (cf. 'max-stale' in HTTP 1.1 [RFC2616]). If maxstale is assigned a value, then the document is willing to accept content that has exceeded its expiration time by no more than the specified number of seconds. [Required] No [Default Value] None [Name]

Output: maxstale

Voice Extensible Markup Language (VoiceXML) 3.0

Table 10: Attributes


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

Output: Description

Internationalization Tag Set (ITS) Version 2.0


Input: [0] terminology [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 [1]

Output: An incorrect term or a term from the wrong domain was used or terms are used inconsistently.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] mistranslation [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. [1]

Output: The content of the target mistranslates the content of the source.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] omission [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. [1]

Output: Necessary text has been omitted from the localization or source.

Internationalization Tag Set (ITS) Version 2.0


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

Output: Content that should have been translated was left untranslated.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] addition [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 [1]

Output: The translated text contains inappropriate additions.

Internationalization Tag Set (ITS) Version 2.0


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

Output: Content has been duplicated improperly.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] 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 [1]

Output: The text is inconsistent with itself (NB: not for use with terminology inconsistency).

Internationalization Tag Set (ITS) Version 2.0


Input: [0] grammar [2] The text reads "The guidelines says that users should use a static grounding strap." [3] S or T [1]

Output: The text contains a grammatical error (including errors of syntax and morphology).

Internationalization Tag Set (ITS) Version 2.0


Input: [0] legal [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 [1]

Output: The text is legally problematic (e.g., it is specific to the wrong legal system).

Internationalization Tag Set (ITS) Version 2.0


Input: [0] register [2] A financia text in U.S. English refers to dollars as "bucks". [3] S or T [1]

Output: The text is written in the wrong linguistic register of uses slang or other language variants inappropriate to the text.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] locale-specific-content [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 . [1]

Output: The localization contains content that does not apply to the locale for which it was prepared.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] locale-violation [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 [1]

Output: Text violates norms for the intended locale.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] style [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 [1]

Output: The text contains stylistic errors.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] characters [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 [1]

Output: The text contains characters that are garbled or incorrect or that are not used in the language in which the content appears.

Internationalization Tag Set (ITS) Version 2.0


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

Output: The text contains a misspelling.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] typographical [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 [1]

Output: The text has typographical errors such as omitted/incorrect punctuation, incorrect capitalization, etc.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] formatting [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 [1]

Output: The text is formatted incorrectly.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] inconsistent-entities [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 [1]

Output: The source and target text contain different named entities (dates, times, place names, individual names, etc.)

Internationalization Tag Set (ITS) Version 2.0


Input: [0] numbers [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. [1]

Output: Numbers are inconsistent between source and target.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] markup [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 [1]

Output: There is an issue related to markup or a mismatch in markup between source and target.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] pattern-problem [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 [1]

Output: The text fails to match a pattern that defines allowable content (or matches one that defines non-allowable content).

Internationalization Tag Set (ITS) Version 2.0


Input: [0] whitespace [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 [1]

Output: There is a mismatch in whitespace between source and target content.

Internationalization Tag Set (ITS) Version 2.0