Input: [Bugzilla bug (if applicable)] Bugzilla 17619 [Erratum (if applicable)] None [Category] Editorial [Affected sections] 5.1.1 XML Output Method: the version Parameter 5.1.3 XML Output Method: the encoding Parameter C Summary of Error Conditions [Description of change]

Output: Text associated with links to the definitions of the terms NCName, EncName and VersionNum was repeated several times.


Input: [Bugzilla bug (if applicable)] Bugzilla 15915 [Erratum (if applicable)] None [Category] Editorial [Affected sections] 3.1 Setting Serialization Parameters by Means of a Data Model Instance [Description of change]

Output: Made uses of the terms "absent" and "unspecified" consistent.


Input: [Bugzilla bug (if applicable)] Bugzilla 17282 [Erratum (if applicable)] None [Category] Substantive [Affected sections] 3 Serialization Parameters B Schema for Serialization Parameters [Description of change]

Output: Changed type of the normalization-form serialization parameter to NMTOKEN. This would be an incompatible change from XQuery 1.0, for any implementation that supported the Serialization Feature, and supported an implementation-defined value for the normalization-form serialization parameter that did not have the lexical form of an NMToken.


Input: [Event handler] onabort [Event handler event type]

Output: abort


Input: [Event handler] oncanplay [Event handler event type]

Output: canplay


Input: [Event handler] oncanplaythrough [Event handler event type]

Output: canplaythrough


Input: [Event handler] onchange [Event handler event type]

Output: change


Input: [Event handler] onclick [Event handler event type]

Output: click


Input: [Event handler] oncontextmenu [Event handler event type]

Output: contextmenu


Input: [Event handler] oncuechange [Event handler event type]

Output: cuechange


Input: [Event handler] ondblclick [Event handler event type]

Output: dblclick


Input: [Event handler] ondrag [Event handler event type]

Output: drag


Input: [Event handler] ondragend [Event handler event type]

Output: dragend


Input: [Event handler] ondragenter [Event handler event type]

Output: dragenter


Input: [Event handler] ondragleave [Event handler event type]

Output: dragleave


Input: [Event handler] ondragover [Event handler event type]

Output: dragover


Input: [Event handler] ondragstart [Event handler event type]

Output: dragstart


Input: [Event handler] ondrop [Event handler event type]

Output: drop


Input: [Event handler] ondurationchange [Event handler event type]

Output: durationchange


Input: [Event handler] onemptied [Event handler event type]

Output: emptied


Input: [Event handler] onended [Event handler event type]

Output: ended


Input: [Event handler] oninput [Event handler event type]

Output: input


Input: [Event handler] oninvalid [Event handler event type]

Output: invalid


Input: [Event handler] onkeydown [Event handler event type]

Output: keydown


Input: [Event handler] onkeypress [Event handler event type]

Output: keypress


Input: [Event handler] onkeyup [Event handler event type]

Output: keyup


Input: [Event handler] onloadeddata [Event handler event type]

Output: loadeddata


Input: [Event handler] onloadedmetadata [Event handler event type]

Output: loadedmetadata


Input: [Event handler] onloadstart [Event handler event type]

Output: loadstart


Input: [Event handler] onmousedown [Event handler event type]

Output: mousedown


Input: [Event handler] onmousemove [Event handler event type]

Output: mousemove


Input: [Event handler] onmouseout [Event handler event type]

Output: mouseout


Input: [Event handler] onmouseover [Event handler event type]

Output: mouseover


Input: [Event handler] onmouseup [Event handler event type]

Output: mouseup


Input: [Event handler] onmousewheel [Event handler event type]

Output: mousewheel


Input: [Event handler] onpause [Event handler event type]

Output: pause


Input: [Event handler] onplay [Event handler event type]

Output: play


Input: [Event handler] onplaying [Event handler event type]

Output: playing


Input: [Event handler] onprogress [Event handler event type]

Output: progress


Input: [Event handler] onratechange [Event handler event type]

Output: ratechange


Input: [Event handler] onreadystatechange [Event handler event type]

Output: readystatechange


Input: [Event handler] onreset [Event handler event type]

Output: reset


Input: [Event handler] onseeked [Event handler event type]

Output: seeked


Input: [Event handler] onseeking [Event handler event type]

Output: seeking


Input: [Event handler] onselect [Event handler event type]

Output: select


Input: [Event handler] onshow [Event handler event type]

Output: show


Input: [Event handler] onstalled [Event handler event type]

Output: stalled


Input: [Event handler] onsubmit [Event handler event type]

Output: submit


Input: [Event handler] onsuspend [Event handler event type]

Output: suspend


Input: [Event handler] ontimeupdate [Event handler event type]

Output: timeupdate


Input: [Event handler] onvolumechange [Event handler event type]

Output: volumechange


Input: [Event handler] onwaiting [Event handler event type]

Output: waiting


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 whitespace separated NMTOKEN values


Input: [Attribute Type] PCDATA [Definition]

Output: Processed character data


Input: [Attribute Type] CDATA [Definition]

Output: Character data

XHTML Modularization 1.1 - Defining Abstract Modules


Input: [Attribute Type] ID [Definition]

Output: A document-unique identifier

XHTML Modularization 1.1 - Defining Abstract Modules


Input: [Attribute Type] IDREF [Definition]

Output: A reference to a document-unique identifier

XHTML Modularization 1.1 - Defining Abstract Modules


Input: [Attribute Type] IDREFS [Definition]

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

XHTML Modularization 1.1 - Defining Abstract Modules


Input: [Attribute Type] NAME [Definition]

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

XHTML Modularization 1.1 - Defining Abstract Modules


Input: [Attribute Type] NMTOKEN [Definition]

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

XHTML Modularization 1.1 - Defining Abstract Modules


Input: [Attribute Type] NMTOKENS [Definition]

Output: One or more white space separated NMTOKEN values

XHTML Modularization 1.1 - Defining Abstract Modules


Input: [Description] a supportedState must be supported by this role. Typically refers to states from the SAP namespace [Values] Any valid RDF object reference, such as a URI. [Property]

Output: supportedState

Role Taxonomy for Accessible Adaptable Applications Working Draft, V1, 03-08-2005


Input: [Description] A child element that must be contained by this role. For example a list must contain a listitem. [Values] Any valid RDF object reference, such as a URI or RDF ID. [Related Concepts] http://www.w3.org/2004/02/skos/core#subject [Property]

Output: mustContain

Role Taxonomy for Accessible Adaptable Applications Working Draft, V1, 03-08-2005


Input: [Description] Context, where this role is allowed. For example a list item is allowed inside a list. [Values] Any valid RDF object reference, such as a URI or RDF ID. [Related Concepts] http://www.w3.org/2004/02/skos/core#Concept [Property]

Output: scope

Role Taxonomy for Accessible Adaptable Applications Working Draft, V1, 03-08-2005


Input: [Description] The media type, where the Role is allowed - a type of scope [Values] Any valid RDF object reference, such as a URI or RDF ID. [Related Concepts] baseConcept: DC: Format XFORMS media type [Property]

Output: media

Role Taxonomy for Accessible Adaptable Applications Working Draft, V1, 03-08-2005


Input: [Description] Estimated importance of a role to completion of the main tasks of a delivery unit. For example a main menu is typically required for a user to beale to completer the main tasks of a site. A secondary side menu is typically less important. Hence a main menu has an importance level of one and secondary side menu may have an importance level of 0.6. [Values] 0 (min) 1 (max) [Property]

Output: importance

Role Taxonomy for Accessible Adaptable Applications Working Draft, V1, 03-08-2005


Input: [Description] How a role type name is extracted and referenced inside a document. For example the DOM might reference a role by it's title. [Values] Any valid RDF object reference, such as a URI or RDF ID. Recomended values: Child, title, content. [Property]

Output: nameRef

Role Taxonomy for Accessible Adaptable Applications Working Draft, V1, 03-08-2005


Input: [Status] Proposal [Summary] To promote the 'citation' property currently on MedicalScholarlyArticle up to CreativeWork. [Vocab] Moves citation up to CreativeWork [Topic]

Output: Citation Promotion

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Status] Proposal [Summary] Extension for describing accessibility properties of a CreativeWork. [Comments] Draft published to elicit feedback. [Topic]

Output: Accessibility

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Status] Accepted [Summary] Add one property 'department' to Organization, to allow local businesses to describe their depts (e.g. opening hours) in detail. [Comments] Proposal very greatly simplified after WebSchemas discussion. [Topic]

Output: Add Organization department property

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Status] Proposal [Summary] Property to indicate that a single identity is being described. [Vocab] Essentially same meaning as owl:sameAs, but suggesting a distinct name to make it easier to talk about; also schema.org data is typically scruffier than OWL re http-range-14. [Comments] Draft published to elicit feedback. [Topic]

Output: sameThingAs

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Status] Proposal [Summary] A proposal for a new Action type. [Vocab] See full entry and proposal for details. May2013 version builds on two previously published designs. [Comments] The schema.org team solicit comments on this draft via public-vocabs@w3.org. [Topic]

Output: Actions in Schema.org

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Status] Proposal [Summary] "While schema.org already supports marking up offers to sell products (pre-transaction), it does not currently provide schema for the common kinds of confirmations and notifications around orders (post-transaction)". [Vocab] Adds classes OrderStatus, Order, DeliveryMethod plus associated properties. [Comments] Complements Actions proposal, but independent. [Topic]

Output: Orders in Schema.org

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Status] Proposal [Summary] This proposal includes new types for describing reservations and tickets [Vocab] Adds classes Reservation, ReservationStatus, ProgramMembership, Flight, TrainTrip, TrainReservation, FoodEstablishmentReservation, FlightReservation, EventReservation, ReservationPackage, BusReservation, BusTrip, RentalCarReservation, RentalCar, Car, LodgingReservation plus associated properties. [Comments] Complements Actions proposal, but independent. [Topic]

Output: Reservations in Schema.org

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Status] Proposal [Summary] This proposal adds a single new type, EmailMessage [Vocab] EmailMessage is a CreativeWork representing email messages, just as WebPage already represents Web pages. [Comments] No properties currently defined; proposals welcomed. [Topic]

Output: EmailMessage type

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Status] Accepted [Summary] This proposal adds a single new type, WorkersUnion, addressing issue 17 in the WebSchemas tracker. [Vocab] "A Workers Union (...) is an organization that promotes the interests of its worker members by collectively bargaining with management, organizing, and political lobbying."" [Comments] One type, see draft schema. [Topic]

Output: Workers Union type

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Status] Accepted; published in next version [Summary] Proposes modest changes and additions to support TV and radio (from EBU and BBC). [Vocab] Adds Series, Season, Episode under CreativeWork. Existing TVSeries, TVSeason, TVEpisode under Series/Season/Episode. Adds RadioSeries/RadioSeason/RadioEpisode alongside. Adds Programme/Clip for programmes other than episodes. Adds description of a service with Service/PublicationEvent for broadcast, streaming, VoD, etc. [Comments] See also background notes and [[1]]. Draft initially from EBU/BBC/NoTube discussions. Nearby vocab: see VideoObject, AudioObject; Movie. Event re scheduling. See also UserPlays, a kind of UserInteraction. Comics and TV/Radio also share a concern for describing fictional characters and narratives. [Topic]

Output: TV and Radio proposal

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Status] Some initial discussions. [Summary] Several parties are working towards a Sports Vocabulary proposal. See query from Paul Kelly (SportsML), Microdata + Sports Stats post describing earlier ESPN/Google collaboration, and the Sports Ontology used by BBC, Press Association and others. See also sports-schema-collab mailing list. [Vocab] Several sources including a full draft from the ESPN+Google work. Needs summary here. [Comments] March 2nd - posted writeup of the ESPN/Google Microdata vocabulary; next is discussion on finding common basic sports vocab for schema.org. [Topic]

Output: Sports

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Status] Discussing Proposals [Summary] Proposal from Marvel (see examples). [Vocab] Adds PeriodicalSeries (under Intangible(?)), PeriodicalIssue (under CreativeWork), Comic Issue (under PeriodicalIssue), GraphicNovel (under Book). Approx 6-9 properties for each of these classes. [Comments] Generally well received and specified, but some detailed discussion re fine-grain detail of comics (imprint, page count etc.). Can those properties be shared with Book/numberOfPages, or ScholarlyArticle? Should PeriodicalSeries be intangible? [Topic]

Output: Comics and Serials

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Status] Hopefully Final Proposal - please review [Summary] Proposes some modifications to Event based on deployment experience. [Vocab] Adds eventStatus, previousStartDate, previousEndDate; eventCategory; makes startDate/endDate repeatable. Encourages use of 'url' from Thing. [Comments] Fairly modest proposals based on implementor feedback. May2013 update addresses the last open issue on repeating events. [Topic]

Output: Event schema update

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Status] Proposal [Summary] The historical-data.org site proposes some extensions to schema.org to address historical and genealogical (family history) scenarios. [Vocab] Adds HistoricalRecord, HistoricalEvent (subclass of Event), overrides attendees, subEvents, superEvent to point to HistoricalEvent. [Comments] There is an associated implementation, github repository, and blog. [Topic]

Output: Historical Data proposal

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Status] Proposal [Summary] A schema extension for describing biological databases, Sagace. [Vocab] Adds a class 'BiologicalDatabaseEntry' as a kind of CreativeWork, introducing 'entryID', 'isEntryOf', 'taxonID'. Adds 'BiologicalDatabase' also subclass of CreativeWork, with no special properties. Both also use 'breadcrumb' from WebPage. [Comments] Others have also mentioned interest in adding some notion of species. [Topic]

Output: Biological Databases

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Status] Proposal [Summary] A proposal resolving current problems handling breadcrumbs. [Vocab] Adds Breadcrumb type with child property and supposes to use this class on breadcrumb property of a WebPage. An important schema, but needs attention. See discussion on using literal values. [Topic]

Output: Breadcrumbs

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Status] Proposal [Summary] A proposal extending schema.org for describing online discussion forums and message boards. [Vocab] Adds attachmentURL, contributorType, discussionState, interestedUsers, postCount, postType, votedHelpful. [Comments] Addition candidate [Topic]

Output: Discussion

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Status] Proposal [Summary] A proposal extending schema.org for describing Innovation and related concepts. Discussion found here: [2] [Vocab] Covers concepts and terms such as Need, Benefit, Usage, Disruption, Innovator, Innovation, Embodiment, to name a few. See [3] for complete list of terms. [Comments] Addition candidate [Topic]

Output: Innovation

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic]

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Status] How far along [Summary] Summary of contribution. [Vocab] Overview of new terms [Comments] Comments on status, particularly regarding integration, overlaps and open issues. [Topic]

Output: Proposal name

WebSchemas/SchemaDotOrgProposals - W3C Wiki


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

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

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


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

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

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


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

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

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


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

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

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


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

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

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


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

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

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


Input: [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 28: 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 28: 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 28: 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 28: 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 28: 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 28: 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 28: 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


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

Output: There is an issue related to the internationalization of content.

Internationalization Tag Set (ITS) Version 2.0


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

Output: There is a significant difference in source and target length.

Internationalization Tag Set (ITS) Version 2.0


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

Output: The issue has not been categorized.

Internationalization Tag Set (ITS) Version 2.0


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

Output: Any issue that cannot be assigned to any values listed above.

Internationalization Tag Set (ITS) Version 2.0


Input: [.capture*] new non-modal prompt [2] form control derived from input file, part of the page [(resp audio, video)] new form control, part of the page [0]

Output: UI


Input: [.capture*] several new interfaces [2] limited (derive from FileReader) [(resp audio, video)] limited (derive from FileReader) [0]

Output: scope of new API


Input: [.capture*] can grant access to API without prompt [2] awkward to use [(resp audio, video)] awkward to use [0]

Output: In widgets


Input: [.capture*] left to the developer [2] possibly transparent (but down to the UA) [(resp audio, video)] possibly transparent (but down to the UA) [0]

Output: Integration with Media gallery


Input: [.capture*] new API calls needed [2] possibly transparent? [(resp audio, video)] possibly transparent? [0]

Output: viewfinder compat


Input: [.capture*] available in API [2] number controled by number of fields — awkward user exp; not clear how to control duration [(resp audio, video)] could be controled with attributes on the input field? [0]

Output: control on number and duration of captures


Input: [.capture*] possible with boolean flags added to Capture interface [2] not clear; might need flags addition [(resp audio, video)] not clear either [0]

Output: detection for support of capture capabilities


Input: [.capture*] need new API calls added to Capture [2] no clear path; probably would need API of its own, but not clear how to plug in [(resp audio, video)] no clear path; probably would need API of its own, but not clear how to plug in [0]

Output: evolution for more control of the capture devices


Input: [.capture*] None [2] Limited [(resp audio, video)] Not trivial [0]

Output: impact/dependence on markup spec (html5?)


Input: [Name] x [Value(s)]

Output: points

DrawML, Markup for Scalable and Intelligent Drawings

Attributes


Input: [Name] y [Value(s)]

Output: points

DrawML, Markup for Scalable and Intelligent Drawings

Attributes


Input: [Name] attach-to [Value(s)]

Output: shape id

DrawML, Markup for Scalable and Intelligent Drawings

Attributes


Input: [Name] attach-point [Value(s)]

Output: hook name

DrawML, Markup for Scalable and Intelligent Drawings

Attributes


Input: [Name] delta-x [Default Value] 0 [Value(s)]

Output: points

DrawML, Markup for Scalable and Intelligent Drawings

Attributes


Input: [Name] arrowed [Default Value] "no" [Value(s)]

Output: points

DrawML, Markup for Scalable and Intelligent Drawings

Attributes


Input: [Required] false [Attribute Constraints] none [Type] IDREFS [Default Value] none [Valid Values] A legal state specification. See 3.11 Legal State Configurations and Specifications for details. [Description] The id of the initial state(s) for the document. If not specified, the default initial state is the first child state in document order. [Name]

Output: initial

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [Required] false [Attribute Constraints] none [Type] NMTOKEN [Default Value] none [Valid Values] Any valid NMTOKEN [Description] The name of this state machine. It is for purely informational purposes. [Name]

Output: name

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [Required] true [Attribute Constraints] none [Type] URI [Default Value] none [Valid Values] The value must MUST be "http://www.w3.org/2005/07/scxml". [Name]

Output: xmlns

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [Required] true [Attribute Constraints] none [Type] decimal [Default Value] none [Valid Values] The only legal value is MUST be "1.0" [Name]

Output: version

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [Required] false [Attribute Constraints] none [Type] NMTOKEN [Default Value] "none" platform-specific [Valid Values] "none", "null", "ecmascript", "xpath" or other platform-defined values. [Description] The datamodel that this document requires. "none" "null" denotes the Empty Null datamodel, "ecmascript" the ECMAScript datamodel, and "xpath" the XPath datamodel, as defined in D Data Models . [Name]

Output: datamodel

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [Required] false [Type] enum [Default Value] "early" [Valid Values] "early", "late" [Description] The data binding to use. See 5.3.3 Data Binding and Scoping for details. [Name]

Output: binding

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [Required] false [Type] enum [Default Value] "lax" [Valid Values] "lax", "strict" [Description] Determines whether the processor should silently ignore markup that it does not support. [Name]

Output: exmode

State Chart XML (SCXML): State Machine Notation for Control Abstraction


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Not applicable

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Not applicable

Internationalization Tag Set (ITS) Version 2.0


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

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 No [Default Values] withinText="no" [Inheritance] None [HTML5 examples] tbd [Overriding]

Output: Not applicable

Internationalization Tag Set (ITS) Version 2.0


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

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 Yes [Default Values] None [Inheritance] None [HTML5 examples] tbd [Overriding]

Output: Not applicable

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Not applicable

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 Yes [Default Values] None [Inheritance] None [HTML5 examples] tbd [Overriding]

Output: Not applicable

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 Yes [Default Values] None [Inheritance] None [HTML5 examples] tbd [Overriding]

Output: Not applicable

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 No [Default Values] default [Inheritance] Textual content of element, including attributes and child elements [HTML5 examples] tbd [Overriding]

Output: Yes

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 Yes [Default Values] None [Inheritance] Textual content of element, including child elements, but excluding attributes [HTML5 examples] tbd [Overriding]

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 Yes [Default Values] None [Inheritance] Textual content of element, including child elements, but excluding attributes [HTML5 examples] tbd [Overriding]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [1] nodeName [3] attributes [2]

Output: nodeValue


Input: [0] Element [1] tagName [3] NamedNodeMap [2]


Input: [0] Attr [1] name of attribute [3] null [2]

Output: value of attribute


Input: [0] Text [1] #text [3] null [2]

Output: content of the text node


Input: [0] CDATASection [1] #cdata-section [3] null [2]

Output: content of the CDATA Section


Input: [0] EntityReference [1] name of entity referenced [3] null [2]


Input: [0] Entity [1] entity name [3] null [2]


Input: [0] ProcessingInstruction [1] target [3] null [2]

Output: entire content excluding the target


Input: [0] Comment [1] #comment [3] null [2]

Output: content of the comment


Input: [0] Document [1] #document [3] null [2]


Input: [0] DocumentType [1] document type name [3] null [2]


Input: [0] DocumentFragment [1] #document-fragment [3] null [2]


Input: [0] Notation [1] notation name [3] null [2]


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: No

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: No

Internationalization Tag Set (ITS) Version 2.0


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

Output: No

Internationalization Tag Set (ITS) Version 2.0


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

Output: No

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [0] UI [.capture*] new non-modal prompt [(resp audio, video)] new form control, part of the page [2]

Output: form control derived from input file, part of the page


Input: [0] scope of new API [.capture*] several new interfaces [(resp audio, video)] limited (derive from FileReader) [2]

Output: limited (derive from FileReader)


Input: [0] In widgets [.capture*] can grant access to API without prompt [(resp audio, video)] awkward to use [2]

Output: awkward to use


Input: [0] Integration with Media gallery [.capture*] left to the developer [(resp audio, video)] possibly transparent (but down to the UA) [2]

Output: possibly transparent (but down to the UA)


Input: [0] viewfinder compat [.capture*] new API calls needed [(resp audio, video)] possibly transparent? [2]

Output: possibly transparent?


Input: [0] control on number and duration of captures [.capture*] available in API [(resp audio, video)] could be controled with attributes on the input field? [2]

Output: number controled by number of fields — awkward user exp; not clear how to control duration


Input: [0] detection for support of capture capabilities [.capture*] possible with boolean flags added to Capture interface [(resp audio, video)] not clear either [2]

Output: not clear; might need flags addition


Input: [0] evolution for more control of the capture devices [.capture*] need new API calls added to Capture [(resp audio, video)] no clear path; probably would need API of its own, but not clear how to plug in [2]

Output: no clear path; probably would need API of its own, but not clear how to plug in


Input: [0] impact/dependence on markup spec (html5?) [.capture*] None [(resp audio, video)] Not trivial [2]

Output: Limited


Input: [1] tagName [2] null [3] NamedNodeMap [0]

Output: Element


Input: [1] name of attribute [2] value of attribute [3] null [0]

Output: Attr


Input: [1] #text [2] content of the text node [3] null [0]

Output: Text


Input: [1] #cdata-section [2] content of the CDATA Section [3] null [0]

Output: CDATASection


Input: [1] name of entity referenced [2] null [3] null [0]

Output: EntityReference


Input: [1] entity name [2] null [3] null [0]

Output: Entity


Input: [1] target [2] entire content excluding the target [3] null [0]

Output: ProcessingInstruction


Input: [1] #comment [2] content of the comment [3] null [0]

Output: Comment


Input: [1] #document [2] null [3] null [0]

Output: Document


Input: [1] document type name [2] null [3] null [0]

Output: DocumentType


Input: [1] #document-fragment [2] null [3] null [0]

Output: DocumentFragment


Input: [1] notation name [2] null [3] null [0]

Output: Notation


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

Output: confidencelevel

Voice Extensible Markup Language (VoiceXML) 3.0

Table 98: Speech Recognition Properties


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

Output: sensitivity

Voice Extensible Markup Language (VoiceXML) 3.0

Table 98: Speech Recognition Properties


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

Output: speedvsaccuracy

Voice Extensible Markup Language (VoiceXML) 3.0

Table 98: Speech Recognition Properties


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

Output: completetimeout

Voice Extensible Markup Language (VoiceXML) 3.0

Table 98: Speech Recognition Properties


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

Output: incompletetimeout

Voice Extensible Markup Language (VoiceXML) 3.0

Table 98: Speech Recognition Properties


Input: [Description] The maximum duration of user speech. If this time elapsed before the user stops speaking, the event "maxspeechtimeout" is thrown. The value is a Time Designation (see 8.4 Value Designations ). [Default] platform-dependent [Name]

Output: maxspeechtimeout

Voice Extensible Markup Language (VoiceXML) 3.0

Table 98: Speech Recognition Properties


Input: [changeDeclined] decided

Output: The WG has decided what to do about this item, but any changes needed have not been integrated into the status quo document.

The Working Group declined to implement the change which the reviewer requested.


Input: [changeDeclined] editorial

Output: An editorial issue - final wording may need WG approval, but WG does not need to discuss technical direction.

The Working Group declined to implement the change which the reviewer requested.


Input: [changeDeclined] erratum

Output: This issue has been identified as an erratum and a correction has either been issued or is in process.

The Working Group declined to implement the change which the reviewer requested.


Input: [changeDeclined] externalComments

Output: The reviewer is not participating in the Working Group.

The Working Group declined to implement the change which the reviewer requested.


Input: [changeDeclined] futureConsideration

Output: This issue may be considered for a future version of the specification. (Used when the feature in question is out of scope for the current version.)

The Working Group declined to implement the change which the reviewer requested.


Input: [changeDeclined] ICS

Output: Implementation Conformance Statement

The Working Group declined to implement the change which the reviewer requested.


Input: [changeDeclined] LC

Output: Last Call version of a specification

The Working Group declined to implement the change which the reviewer requested.


Input: [changeDeclined] needsAction

Output: The issue resolution depends on an Action Item realisation

The Working Group declined to implement the change which the reviewer requested.


Input: [changeDeclined] needsAgreement

Output: For XML Schema bugs which have been classified, but on which the WG has not yet reached technical ('phase-1') agreement.

The Working Group declined to implement the change which the reviewer requested.


Input: [changeDeclined] needsDrafting

Output: For XML Schema bugs on which the WG has reached technical ('phase-1') agreement; the next step is for the editors to draft wording for the spec along the technical lines agreed by the WG.

The Working Group declined to implement the change which the reviewer requested.


Input: [changeDeclined] needsPublication

Output: An editor has drafted proposed wording for the issue resolution, but it hasn't been published to the WG yet.

The Working Group declined to implement the change which the reviewer requested.


Input: [changeDeclined] needsReview

Output: There is a proposed resolution for the issue, but it hasn't been reviewed yet

The Working Group declined to implement the change which the reviewer requested.


Input: [changeDeclined] noFurtherAction

Output: For XML Schema bugs which have been classified as nongoals, or which have been overtaken by events, or abandoned; also for items which the WG believes should be dealt with by writing an explanation to the bug reporter but without a change to the spec.

The Working Group declined to implement the change which the reviewer requested.


Input: [changeDeclined] nonEditorialChange

Output: To implement the comment, the Working Group made a non-editorial change to the specification.

The Working Group declined to implement the change which the reviewer requested.


Input: [changeDeclined] noResponse

Output: The reviewer did not respond to the decision of the Working Group.

The Working Group declined to implement the change which the reviewer requested.


Input: [changeDeclined] notInDTD

Output: For the Markup Validator, labels issues that are not in the realm of validation, but should be considered for a conformance checker.

The Working Group declined to implement the change which the reviewer requested.


Input: [changeDeclined] proposalAccepted

Output: The Working Group has accepted the proposal of the reviewer.

The Working Group declined to implement the change which the reviewer requested.


Input: [changeDeclined] resolved

Output: For XML Schema bugs which have been resolved and the wording for which has been integrated by the editors into the status quo document. (This keyword may be omitted when the bug's Status field has the value "RESOLVED".)

The Working Group declined to implement the change which the reviewer requested.


Input: [changeDeclined] reviewerNotSatisfied

Output: The reviewer is not satisfied with the response of the Working Group.

The Working Group declined to implement the change which the reviewer requested.


Input: [changeDeclined] reviewerSatisfied

Output: The reviewer is satisfied with the response of the Working Group.

The Working Group declined to implement the change which the reviewer requested.


Input: [changeDeclined] SpecGL

Output: QA Specification Guidelines

The Working Group declined to implement the change which the reviewer requested.


Input: [changeDeclined] unclassified

Output: For XML Schema bugs which are awaiting classification by the WG

The Working Group declined to implement the change which the reviewer requested.


Input: [changeDeclined] Usability

Output: Usability of the tool, including accessibility of input and output, style, interface, simplicity of error messages...

The Working Group declined to implement the change which the reviewer requested.


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

Output: Source node


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

Output: Source node


Input: [Event Name] dragenter [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 [Target]

Output: Immediate user selection or the body element


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

Output: Previous target element


Input: [Event Name] dragover [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" [Target]

Output: Current target element


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

Output: Current target element


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

Output: Source node


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

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

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" [Inheritance] None [Overriding] Not applicable [HTML5 examples] tbd

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" [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes [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 [Inheritance] None [Overriding] Not applicable [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 [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes [HTML5 examples] tbd

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" [Inheritance] None [Overriding] Not applicable [HTML5 examples] tbd

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 [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes [HTML5 examples] tbd

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 [Inheritance] None [Overriding] Not applicable [HTML5 examples] tbd

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="*" [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes [HTML5 examples] tbd

Output: No

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 [Inheritance] None [Overriding] Not applicable [HTML5 examples] tbd

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 [Inheritance] None [Overriding] Not applicable [HTML5 examples] tbd

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 [Inheritance] None [Overriding] Not applicable [HTML5 examples] tbd

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 [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes [HTML5 examples] tbd

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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


Input: [User Action/External Input] User presses button on steering wheel [Action on Device] Service is initiated and GPS satellite detection begins [Event Description] HTTP Request to app server [Event Handler] App server returns initial page to device [Resulting Action]

Output: Welcome prompts are played. Authentication dialog is initiated (may be initiated via speaker identification or key identification).


Input: [User Action/External Input] User interacts in an authentication dialog [Action on Device] Device executes authentication dialog using local ASR processing [Event Description] HTTP Request to app server which includes user credentials [Event Handler] App server returns initial page to device including user preferences [Resulting Action]

Output: User is prompted for a destination (if additional services are availble after authentication, assume that user selects driving direction application)


Input: [User Action/External Input] Initial GPS Input [Action on Device] N/A [Event Description] GPS_Data_In Event [Event Handler] Device handles location information [Resulting Action]

Output: Device updates map on graphical display (assumes all maps are stored locally on device)


Input: [User Action/External Input] User selects option to change volume of on-board unit using touch display. [Action on Device] N/A [Event Description] Touch_screen_event (includes x, y coordinates) [Event Handler] Touch screen detects and processes input [Resulting Action]

Output: Volume indicator changes on screen. Volume of speech output is changed


Input: [User Action/External Input] User presses button on steering wheel [Action on Device] Device initiates connection to ASR server [Event Description] Start_Listening Event [Event Handler] ASR Server receives request and establishes connection [Resulting Action]

Output: "listening" icon appears on display (utterances prior to establishing the connection are buffered)


Input: [User Action/External Input] User says destination address (may improve recognition accuracy by sending grammar constraints to server based on a local dialog with the user instead of allowing any address from the start) [Action on Device] N/A [Event Description] N/A [Event Handler] ASR Server processes speech and returns results to device [Resulting Action]

Output: Device processes results and plays confirmation dialog to user while highlighting destination and route on graphical display


Input: [User Action/External Input] User confirms destination [Action on Device] Device performs ASR Processing locally. Upon confirmation, destination info is sent to app server [Event Description] HTTP Request is sent to app server (includes current location and destination information) [Event Handler] App Server processes input and returns data to device [Resulting Action]

Output: Device processes results and updates graphical display with route and directions highlighting next step


Input: [User Action/External Input] GPS Input at regular intervals [Action on Device] N/A [Event Description] GPS_Data_In Event [Event Handler] Device processes location data and checks if location milestone is hit [Resulting Action]

Output: Device updates map on graphical display (assumes all maps are stored locally on device) and highlights current step. When milestone is hit, next instruction is played to user


Input: [User Action/External Input] GPS Input at regular intervals (indicating driver is off course) [Action on Device] N/A [Event Description] GPS_Data_In Event [Event Handler] Device processes location data and determines that user is off course [Resulting Action]

Output: Map on graphical display is updated and textual message is displayed indicating that route is not correct. Prompt is played from the device indicating that route is being recalculated


Input: [User Action/External Input] N/A [Action on Device] Route request is sent to app server including new location data [Event Description] HTTP Request is sent to app server (includes current location and destination information) [Event Handler] App Server processes input and returns data to device [Resulting Action]

Output: Device processes results and updates graphical display with route and directions highlighting next step


Input: [User Action/External Input] Alert received on device based on traffic conditions [Action on Device] N/A [Event Description] Route_Change Alert [Event Handler] Device processes event and initiates dialog to determine if route should be recalculated [Resulting Action]

Output: User is informed of traffic conditions and asked whether route should be recalculated.


Input: [User Action/External Input] User requests recalculation of route based on current traffic conditions [Action on Device] Device performs ASR Processing locally. Upon confirmation, destination info is sent to app server [Event Description] HTTP Request is sent to app server (includes current location and destination information) [Event Handler] App Server processes input and returns data to device [Resulting Action]

Output: Device processes results and updates graphical display with route and directions highlighting next step


Input: [User Action/External Input] User presses button on steering wheel [Action on Device] Connection to ASR server is established [Event Description] Start_Listening Event [Event Handler] ASR Server receives request and establishes connection [Resulting Action]

Output: User hears acknowledgement prompt for continuation, and "listening" icon appears on display


Input: [User Action/External Input] User requests new destination by destination type while still depressing button on steering wheel (may improve recognition accuracy by sending grammar constraints to server based on a local dialog with the user) [Action on Device] N/A [Event Description] N/A [Event Handler] ASR Server processes speech and returns results to device [Resulting Action]

Output: Device processes results and plays confirmation dialog to user while highlighting destination and route on graphical display


Input: [User Action/External Input] User confirms destination via a multiple interaction dialog to determine exact destination [Action on Device] Device executes dialog based on user responses (using local ASR Processing) and accesses app server as needed [Event Description] HTTP requests to app server for dialog and data specific to user response [Event Handler] App server responds with appropriate dialog [Resulting Action]

Output: User interacts in a dialog and selects destination. User is asked whether this is a new destination


Input: [User Action/External Input] User indicates that this is a stop on the way to original destination [Action on Device] Devices sends updated destination information to app server [Event Description] HTTP Request for updated directions (based on current location, detour destination, and ultimate destination) [Event Handler] App Server processes input and returns data to device [Resulting Action]

Output: Device processes results and updates graphical display with new route and directions highlighting next step


Input: [Data category] Translate [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] translate="yes" for elements, and translate="no" for attributes [Overriding] Yes [HTML5 examples] tbd [Inheritance]

Output: Textual content of element, including content of child elements, but excluding attributes

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Localization Note [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] None [Overriding] Yes [HTML5 examples] tbd [Inheritance]

Output: Textual content of element, including content of child elements, but excluding attributes

Internationalization Tag Set (ITS) Version 2.0


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

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Directionality [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] dir="ltr" [Overriding] Yes [HTML5 examples] tbd [Inheritance]

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

Internationalization Tag Set (ITS) Version 2.0


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

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Language Information [Local Usage] No [Global, rule-based selection] Yes [Global adding of information] No Yes [Default Values] None [Overriding] Yes [HTML5 examples] tbd [Inheritance]

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

Internationalization Tag Set (ITS) Version 2.0


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

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Domain [Local Usage] No [Global, rule-based selection] Yes [Global adding of information] Yes Yes [Default Values] None [Overriding] Yes [HTML5 examples] tbd [Inheritance]

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

Internationalization Tag Set (ITS) Version 2.0


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

Internationalization Tag Set (ITS) Version 2.0


Input: [Data category] Locale Filter [Local Usage] Yes [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] localeFilterList="*" [Overriding] Yes [HTML5 examples] tbd [Inheritance]

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

Internationalization Tag Set (ITS) Version 2.0


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

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 Yes [Default Values] None [Overriding] Not applicable [HTML5 examples] tbd [Inheritance]

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 Yes [Default Values] None [Overriding] Not applicable [HTML5 examples] tbd [Inheritance]

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 No [Default Values] default [Overriding] Yes [HTML5 examples] tbd [Inheritance]

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

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 Yes [Default Values] None [Overriding] Yes [HTML5 examples] tbd [Inheritance]

Output: Textual content of element, including child elements, but excluding attributes

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 Yes [Default Values] None [Overriding] Yes [HTML5 examples] tbd [Inheritance]

Output: Textual content of element, including child elements, but excluding attributes

Internationalization Tag Set (ITS) Version 2.0


Input: [User Action/External Input] User presses button on steering wheel [Event Description] HTTP Request to app server [Event Handler] App server returns initial page to device [Resulting Action] Welcome prompts are played. Authentication dialog is initiated (may be initiated via speaker identification or key identification). [Action on Device]

Output: Service is initiated and GPS satellite detection begins


Input: [User Action/External Input] User interacts in an authentication dialog [Event Description] HTTP Request to app server which includes user credentials [Event Handler] App server returns initial page to device including user preferences [Resulting Action] User is prompted for a destination (if additional services are availble after authentication, assume that user selects driving direction application) [Action on Device]

Output: Device executes authentication dialog using local ASR processing


Input: [User Action/External Input] Initial GPS Input [Event Description] GPS_Data_In Event [Event Handler] Device handles location information [Resulting Action] Device updates map on graphical display (assumes all maps are stored locally on device) [Action on Device]


Input: [User Action/External Input] User selects option to change volume of on-board unit using touch display. [Event Description] Touch_screen_event (includes x, y coordinates) [Event Handler] Touch screen detects and processes input [Resulting Action] Volume indicator changes on screen. Volume of speech output is changed [Action on Device]


Input: [User Action/External Input] User presses button on steering wheel [Event Description] Start_Listening Event [Event Handler] ASR Server receives request and establishes connection [Resulting Action] "listening" icon appears on display (utterances prior to establishing the connection are buffered) [Action on Device]

Output: Device initiates connection to ASR server


Input: [User Action/External Input] User says destination address (may improve recognition accuracy by sending grammar constraints to server based on a local dialog with the user instead of allowing any address from the start) [Event Description] N/A [Event Handler] ASR Server processes speech and returns results to device [Resulting Action] Device processes results and plays confirmation dialog to user while highlighting destination and route on graphical display [Action on Device]


Input: [User Action/External Input] User confirms destination [Event Description] HTTP Request is sent to app server (includes current location and destination information) [Event Handler] App Server processes input and returns data to device [Resulting Action] Device processes results and updates graphical display with route and directions highlighting next step [Action on Device]

Output: Device performs ASR Processing locally. Upon confirmation, destination info is sent to app server


Input: [User Action/External Input] GPS Input at regular intervals [Event Description] GPS_Data_In Event [Event Handler] Device processes location data and checks if location milestone is hit [Resulting Action] Device updates map on graphical display (assumes all maps are stored locally on device) and highlights current step. When milestone is hit, next instruction is played to user [Action on Device]


Input: [User Action/External Input] GPS Input at regular intervals (indicating driver is off course) [Event Description] GPS_Data_In Event [Event Handler] Device processes location data and determines that user is off course [Resulting Action] Map on graphical display is updated and textual message is displayed indicating that route is not correct. Prompt is played from the device indicating that route is being recalculated [Action on Device]


Input: [User Action/External Input] N/A [Event Description] HTTP Request is sent to app server (includes current location and destination information) [Event Handler] App Server processes input and returns data to device [Resulting Action] Device processes results and updates graphical display with route and directions highlighting next step [Action on Device]

Output: Route request is sent to app server including new location data


Input: [User Action/External Input] Alert received on device based on traffic conditions [Event Description] Route_Change Alert [Event Handler] Device processes event and initiates dialog to determine if route should be recalculated [Resulting Action] User is informed of traffic conditions and asked whether route should be recalculated. [Action on Device]


Input: [User Action/External Input] User requests recalculation of route based on current traffic conditions [Event Description] HTTP Request is sent to app server (includes current location and destination information) [Event Handler] App Server processes input and returns data to device [Resulting Action] Device processes results and updates graphical display with route and directions highlighting next step [Action on Device]

Output: Device performs ASR Processing locally. Upon confirmation, destination info is sent to app server


Input: [User Action/External Input] User presses button on steering wheel [Event Description] Start_Listening Event [Event Handler] ASR Server receives request and establishes connection [Resulting Action] User hears acknowledgement prompt for continuation, and "listening" icon appears on display [Action on Device]

Output: Connection to ASR server is established


Input: [User Action/External Input] User requests new destination by destination type while still depressing button on steering wheel (may improve recognition accuracy by sending grammar constraints to server based on a local dialog with the user) [Event Description] N/A [Event Handler] ASR Server processes speech and returns results to device [Resulting Action] Device processes results and plays confirmation dialog to user while highlighting destination and route on graphical display [Action on Device]


Input: [User Action/External Input] User confirms destination via a multiple interaction dialog to determine exact destination [Event Description] HTTP requests to app server for dialog and data specific to user response [Event Handler] App server responds with appropriate dialog [Resulting Action] User interacts in a dialog and selects destination. User is asked whether this is a new destination [Action on Device]

Output: Device executes dialog based on user responses (using local ASR Processing) and accesses app server as needed


Input: [User Action/External Input] User indicates that this is a stop on the way to original destination [Event Description] HTTP Request for updated directions (based on current location, detour destination, and ultimate destination) [Event Handler] App Server processes input and returns data to device [Resulting Action] Device processes results and updates graphical display with new route and directions highlighting next step [Action on Device]

Output: Devices sends updated destination information to app server


Input: [Major Concepts] Service AtomicProcess composedOf message channel [Module]

Output: FLOWS-Core

The FLOWS Process Model Ontology Modules


Input: [Major Concepts] Split Sequence Unordered Choice IfThenElse Iterate RepeatUntil [Module]

Output: Control Constraints


Input: [Major Concepts] OrderedActivity [Module]

Output: Ordering Constraints


Input: [Major Concepts] OccActivity [Module]

Output: Occurrence Constraints


Input: [Major Concepts] TriggeredActivity [Module]

Output: State Constraints


Input: [Major Concepts] Exception [Module]

Output: Exception Constraints


Input: [Value] copy: [Description]

Output: A duplicate of the source object will be dropped into the target.

Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [Value] move: [Description]

Output: The source object will be removed from its current location and dropped into the target.

Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [Value] link: [Description]

Output: A reference or shortcut to the dragged object will be created in the target object.

Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [Value] execute: [Description]

Output: A function supported by the drop target is executed, using the drag source as an input.

Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [Value] popup: [Description]

Output: There is a popup menu or dialog that allows the user to choose one of the drag operations (copy, move, link, execute) and any other drag functionality, such as cancel.

Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [Value] none (default): [Description]

Output: No operation can be performed; effectively cancels the drag operation if an attempt is made to drop on this object. Ignored if combined with any other token value. e.g. 'none copy' is equivalent to a 'copy' value.

Accessible Rich Internet Applications (WAI-ARIA) 1.0

Values of aria-dropeffect


Input: [Data category] Translate [Global, rule-based selection] Yes [Global adding of information] Yes No [Default Values] translate="yes" for elements, and translate="no" for attributes [Inheritance] Textual content of element, including content of child elements, but excluding attributes [Overriding] Yes [HTML5 examples] tbd [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 [Inheritance] Textual content of element, including content of child elements, but excluding attributes [Overriding] Yes [HTML5 examples] tbd [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" [Inheritance] None [Overriding] Not applicable [HTML5 examples] tbd [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" [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes [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 [Inheritance] None [Overriding] Not applicable [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 [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes [HTML5 examples] tbd [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" [Inheritance] None [Overriding] Not applicable [HTML5 examples] tbd [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 [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes [HTML5 examples] tbd [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 [Inheritance] None [Overriding] Not applicable [HTML5 examples] tbd [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="*" [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes [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 [Inheritance] None [Overriding] Not applicable [HTML5 examples] tbd [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 [Inheritance] None [Overriding] Not applicable [HTML5 examples] tbd [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 [Inheritance] None [Overriding] Not applicable [HTML5 examples] tbd [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 [Inheritance] Textual content of element, including attributes and child elements [Overriding] Yes [HTML5 examples] tbd [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 [Inheritance] Textual content of element, including child elements, but excluding attributes [Overriding] Yes [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 [Inheritance] Textual content of element, including child elements, but excluding attributes [Overriding] Yes [HTML5 examples] tbd [Local Usage]

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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