Input: [Topic] Real Estate [Status] Discussions but no proposal yet. [Summary] Enthusiastic discussion in favour of adding RealEstate support. Tracked as issue 13. This should likely follow along after the Good Relations work. [Comments] Related to Place vocabulary, and schema.org's numerous subclasses, and Offer class. [Vocab]

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Transport Data [Status] Discussion [Summary] Initial discussion on description of transport data. [Comments] Discussions on whether this scenario can be covered with existing vocabulary. [Vocab]

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Activities (things you can do) [Status] Proposal [Summary] Vocabulary for describing general activities not bound to any specific time or place. Unrelated to the Activities and Actions proposal for online user page interations that are listed above. [Comments] Public draft and description available on wiki. Original proposal on public vocabs mailinglist. [Vocab]

Output: Examples: 'Paragliding'. 'Going to the cinema', etc.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Person biography [Status] Proposal [Summary] A proposal for supporting people's biography [Vocab]

Output: Add a bibliography property to the Person type.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Project [Status] Proposal [Summary] Vocabulary for describing any kind of project [Comments] Use case gathering - see mailing list thread [Vocab]

Output: Terms (loosely) based on this project vocabulary

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Vacation Rental Schema [Status] Proposal [Summary] Creating an additional vocabulary for this hotel-alternative accommodation [Comments] Just initiated the discussion around this schema. Public proposal available on the Wiki [Vocab]

Output: Overview of new terms

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Fictional Thing [Status] Proposal [Summary] Providing the ability to identify a thing as being fictional [Comments] Supporting discussion around this schema. Public proposal available on the Wiki [Vocab]

Output: Proposal for the creation of a FictionalThing type

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] JobMarket [Status] Proposal [Summary] Extension for modelling job markets [Comments] Draft for an extension published to elicit feedback [Vocab]

Output: Classes added: Compensation, WorkExperience + class amended: JobPosting

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] VisualArtwork [Status] Early Proposal [Summary] Extension for CreativeWork and replacement/alternative to Painting and Sculpture [Comments] Early draft for an extension published to elicit feedback. [Vocab]

Output: Overview of Extension and new properties

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] GeoJSON [Status] Early propsal [Summary] addition to the Geo* family of topics. [Comments] Related to Place vocabulary [Vocab]

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Looking Inside Tables [Status] Early proposal [Summary] A mechanism to map the contents of tables into entities. [Comments] Draft for an extension published to elicit feedback. [Vocab]

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Online Presence [Status] Early proposal [Summary] expressing Online Presence and current Actions [Comments] Related to Action subtree and Online Presence Ontology. [Vocab]

Output: WIP

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Property-Value Pairs [Status] Work in progress [Summary] Adding support for arbitrary property-value pairs. Useful for product features and as a generic extension mechanism for properties in schema.org. [Comments] Mirrors an upcoming feature in GoodRelations. [Vocab]

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] SocialAccount [Status] Proposal [Summary] Introduce a type and a property to describe social accounts of http://schema.org/Person or http://schema.org/Organization [Comments] See also the mailing list discussion [Vocab]

Output: Add SocialAccount type derived from http://schema.org/Thing to capture social account. Update http://schema.org/Person and http://schema.org/Organization by adding the property socialAccount expecting the type SocialAccount

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] socialAccount [Status] Proposal [Summary] Introduce a property to describe social accounts of http://schema.org/Person and http://schema.org/Organization [Comments] See also the mailing list discussion This is an alternative of the previous item [Vocab]

Output: Update http://schema.org/Person and http://schema.org/Organization by adding the property socialAccount expecting a URL as value

WebSchemas/SchemaDotOrgProposals - W3C Wiki


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

Output: Overview of new terms

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Type of information] Background colour [Description]

Output: Solid background colour to be used when presenting the image if no better option is available.

Portable Network Graphics (PNG) Specification (Second Edition)

Table 4.1 — Types of ancillary information


Input: [Type of information] Gamma and chromaticity [Description]

Output: Gamma characteristic of the image with respect to the desired output intensity, and chromaticity characteristics of the RGB values used in the image.

Portable Network Graphics (PNG) Specification (Second Edition)


Input: [Type of information] ICC profile [Description]

Output: Description of the colour space (in the form of an International Color Consortium (ICC) profile) to which the samples in the image conform.

Portable Network Graphics (PNG) Specification (Second Edition)


Input: [Type of information] Image histogram [Description]

Output: Estimates of how frequently the image uses each palette entry.

Portable Network Graphics (PNG) Specification (Second Edition)


Input: [Type of information] Physical pixel dimensions [Description]

Output: Intended pixel size and aspect ratio to be used in presenting the PNG image.

Portable Network Graphics (PNG) Specification (Second Edition)


Input: [Type of information] Significant bits [Description]

Output: The number of bits that are significant in the samples.

Portable Network Graphics (PNG) Specification (Second Edition)


Input: [Type of information] sRGB colour space [Description]

Output: A rendering intent (as defined by the International Color Consortium) and an indication that the image samples conform to this colour space.

Portable Network Graphics (PNG) Specification (Second Edition)


Input: [Type of information] Suggested palette [Description]

Output: A reduced palette that may be used when the display device is not capable of displaying the full range of colours in the image.

Portable Network Graphics (PNG) Specification (Second Edition)


Input: [Type of information] Textual data [Description]

Output: Textual information (which may be compressed) associated with the image.

Portable Network Graphics (PNG) Specification (Second Edition)


Input: [Type of information] Time [Description]

Output: The time when the PNG image was last modified.

Portable Network Graphics (PNG) Specification (Second Edition)


Input: [Type of information] Transparency [Description]

Output: Alpha information that allows the reference image to be reconstructed when the alpha channel is not retained in the PNG image.

Portable Network Graphics (PNG) Specification (Second Edition)


Input: [Topic] ScholarlyArticle [Summary] Various ideas around improving ScholarlyArticle. [Vocab] Suggestion that scholarly articles could be described in more detail. [Comments] There is a lot of related work in this area. For example Google Scholar publisher guidelines; Microsoft Academic Search. The Open Archives Initiative - Protocol for Metadata Harvesting also addresses this problem area and has broad adoption. See also earlier comments from HighWire Press (pdf) and following discussion (on the old mailing list). [Status]

Output: Early proposal from HighWire Press needs review.

Early proposal from HighWire Press needs review.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Real Estate [Summary] Enthusiastic discussion in favour of adding RealEstate support. Tracked as issue 13. This should likely follow along after the Good Relations work. [Vocab] N/A [Comments] Related to Place vocabulary, and schema.org's numerous subclasses, and Offer class. [Status]

Output: Discussions but no proposal yet.

Early proposal from HighWire Press needs review.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Vehicles [Summary] A proposal extending schema.org for describing vehicles is being prepared. [Comments] No public draft yet. [Status]

Output: Anticipated.

Early proposal from HighWire Press needs review.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Transport Data [Summary] Initial discussion on description of transport data. [Vocab] N/A [Comments] Discussions on whether this scenario can be covered with existing vocabulary. [Status]

Output: Discussion

Early proposal from HighWire Press needs review.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Activities (things you can do) [Summary] Vocabulary for describing general activities not bound to any specific time or place. Unrelated to the Activities and Actions proposal for online user page interations that are listed above. [Vocab] Examples: 'Paragliding'. 'Going to the cinema', etc. [Comments] Public draft and description available on wiki. Original proposal on public vocabs mailinglist. [Status]

Output: Proposal

Early proposal from HighWire Press needs review.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Person biography [Summary] A proposal for supporting people's biography [Vocab] Add a bibliography property to the Person type. [Status]

Output: Proposal

Early proposal from HighWire Press needs review.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Project [Summary] Vocabulary for describing any kind of project [Vocab] Terms (loosely) based on this project vocabulary [Comments] Use case gathering - see mailing list thread [Status]

Output: Proposal

Early proposal from HighWire Press needs review.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Vacation Rental Schema [Summary] Creating an additional vocabulary for this hotel-alternative accommodation [Vocab] Overview of new terms [Comments] Just initiated the discussion around this schema. Public proposal available on the Wiki [Status]

Output: Proposal

Early proposal from HighWire Press needs review.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Fictional Thing [Summary] Providing the ability to identify a thing as being fictional [Vocab] Proposal for the creation of a FictionalThing type [Comments] Supporting discussion around this schema. Public proposal available on the Wiki [Status]

Output: Proposal

Early proposal from HighWire Press needs review.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] JobMarket [Summary] Extension for modelling job markets [Vocab] Classes added: Compensation, WorkExperience + class amended: JobPosting [Comments] Draft for an extension published to elicit feedback [Status]

Output: Proposal

Early proposal from HighWire Press needs review.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] VisualArtwork [Summary] Extension for CreativeWork and replacement/alternative to Painting and Sculpture [Vocab] Overview of Extension and new properties [Comments] Early draft for an extension published to elicit feedback. [Status]

Output: Early Proposal

Early proposal from HighWire Press needs review.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] GeoJSON [Summary] addition to the Geo* family of topics. [Vocab] N/A [Comments] Related to Place vocabulary [Status]

Output: Early propsal

Early proposal from HighWire Press needs review.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Looking Inside Tables [Summary] A mechanism to map the contents of tables into entities. [Vocab] N/A [Comments] Draft for an extension published to elicit feedback. [Status]

Output: Early proposal

Early proposal from HighWire Press needs review.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Online Presence [Summary] expressing Online Presence and current Actions [Vocab] WIP [Comments] Related to Action subtree and Online Presence Ontology. [Status]

Output: Early proposal

Early proposal from HighWire Press needs review.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Property-Value Pairs [Summary] Adding support for arbitrary property-value pairs. Useful for product features and as a generic extension mechanism for properties in schema.org. [Vocab] N/A [Comments] Mirrors an upcoming feature in GoodRelations. [Status]

Output: Work in progress

Early proposal from HighWire Press needs review.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] SocialAccount [Summary] Introduce a type and a property to describe social accounts of http://schema.org/Person or http://schema.org/Organization [Vocab] Add SocialAccount type derived from http://schema.org/Thing to capture social account. Update http://schema.org/Person and http://schema.org/Organization by adding the property socialAccount expecting the type SocialAccount [Comments] See also the mailing list discussion [Status]

Output: Proposal

Early proposal from HighWire Press needs review.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] socialAccount [Summary] Introduce a property to describe social accounts of http://schema.org/Person and http://schema.org/Organization [Vocab] Update http://schema.org/Person and http://schema.org/Organization by adding the property socialAccount expecting a URL as value [Comments] See also the mailing list discussion This is an alternative of the previous item [Status]

Output: Proposal

Early proposal from HighWire Press needs review.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


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

Output: How far along

Early proposal from HighWire Press needs review.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Method] POST [URL] /session [Command]

Output: New Session


Input: [Method] DELETE [URL] /session/{session id} [Command]

Output: Delete Session


Input: [Method] POST [URL] /session/{session id}/url [Command]

Output: Get


Input: [Method] GET [URL] /session/{session id}/url [Command]

Output: Get Current Url


Input: [Method] POST [URL] /session/{session id}/back [Command]

Output: Back


Input: [Method] POST [URL] /session/{session id}/forward [Command]

Output: Forward


Input: [Method] POST [URL] /session/{session id}/refresh [Command]

Output: Refresh


Input: [Method] GET [URL] /session/{session id}/title [Command]

Output: Get Title


Input: [Method] GET [URL] /session/{session id}/window/handle [Command]

Output: Get Window Handle


Input: [Method] GET [URL] /session/{session id}/window/handles [Command]

Output: Get Window Handles


Input: [Method] DELETE [URL] /session/{session id}/window [Command]

Output: Close Window


Input: [Method] POST [URL] /session/{session id}/window/size [Command]

Output: Set Window Size


Input: [Method] GET [URL] /session/{session id}/window/size [Command]

Output: Get Window Size


Input: [Method] POST [URL] /session/{session id}/window/maximize [Command]

Output: Maximize Window


Input: [Method] POST [URL] /session/{session id}/window/fullscreen [Command]

Output: Fullscreen Window


Input: [Method] POST [URL] /session/{session id}/window [Command]

Output: Switch To Window


Input: [Method] POST [URL] /session/{session id}/frame [Command]

Output: Switch To Frame


Input: [Method] POST [URL] /session/{session id}/frame/parent [Command]

Output: Switch To Parent Frame


Input: [Method] POST [URL] /session/{session id}/element [Command]

Output: Find Element


Input: [Method] POST [URL] /session/{session id}/elements [Command]

Output: Find Elements


Input: [Method] GET [URL] /session/{session id}/element/{element id}/displayed [Command]

Output: Is Element Displayed


Input: [Method] GET [URL] /session/{session id}/element/{element id}/selected [Command]

Output: Is Element Selected


Input: [Method] GET [URL] /session/{session id}/element/{element id}/attribute/{name} [Command]

Output: Get Element Attribute


Input: [Method] GET [URL] /session/{session id}/element/{element id}/css/{property name} [Command]

Output: Get Element CSS Value


Input: [Method] GET [URL] /session/{session id}/element/{element id}/text [Command]

Output: Get Element Text


Input: [Method] GET [URL] /session/{session id}/element/{element id}/name [Command]

Output: Get Element Tag Name


Input: [Method] GET [URL] /session/{session id}/element/{element id}/rect [Command]

Output: Get Element Rect


Input: [Method] GET [URL] /session/{session id}/element/{element id}/enabled [Command]

Output: Is Element Enabled


Input: [Method] POST [URL] /session/{session id}/execute [Command]

Output: Execute Script


Input: [Method] POST [URL] /session/{session id}/execute_async [Command]

Output: Execute Async Script


Input: [Method] GET [URL] /session/{session id}/cookie/{name} [Command]

Output: Get Cookie


Input: [Method] POST [URL] /session/{session id}/cookie [Command]

Output: Add Cookie


Input: [Method] DELETE [URL] /session/{session id}/cookie/{name} [Command]

Output: Delete Cookie


Input: [Method] POST [URL] /session/{session id}/timeouts [Command]

Output: Set Timeout


Input: [Method] POST [URL] /session/{session id}/actions [Command]

Output: Actions


Input: [Method] POST [URL] /session/{session id}/element/{element id}/click [Command]

Output: Element Click


Input: [Method] POST [URL] /session/{session id}/element/{element id}/tap [Command]

Output: Element Tap


Input: [Method] POST [URL] /session/{session id}/element/{element id}/clear [Command]

Output: Element Clear


Input: [Method] POST [URL] /session/{session id}/element/{element id}/sendKeys [Command]

Output: Element Send Keys


Input: [Method] POST [URL] /session/{session id}/dismiss_alert [Command]

Output: Dismiss Alert


Input: [Method] POST [URL] /session/{session id}/alert/accept [Command]

Output: Accept Alert


Input: [Method] GET [URL] /session/{session id}/alert/text [Command]

Output: Get Alert Text


Input: [Method] POST [URL] /session/{session id}/alert/text [Command]

Output: Send Alert Text


Input: [Method] GET [URL] /session/{session id}/screenshot [Command]

Output: Take Screenshot


Input: [Method] GET [URL] /session/{session id}/element/{element id}/screenshot [Command]

Output: Take Element Screenshot


Input: [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 [Overriding] Yes [Data category]

Output: Translate

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


Input: [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 [Overriding] Yes [Data category]

Output: Localization Note

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


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

Output: Terminology

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


Input: [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 [Overriding] Yes [Data category]

Output: Directionality

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


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

Output: Ruby

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


Input: [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 [Overriding] Yes [Data category]

Output: Language Information

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


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

Output: Elements Within Text

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


Input: [Control Type] Text input (including date/time and password fields) [LiveCycle Placement Rules]

Output: Default placement for the label is to the left of the control. If this is not possible, LiveCycle will attempt to place it immediately above the control.

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


Input: [Control Type] Checkbox [LiveCycle Placement Rules]

Output: Default placement for the label is to the right of the check box.

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


Input: [Control Type] Radio button group [LiveCycle Placement Rules]

Output: Default placement for the label for each individual radio button is to the right of the button. Create a visible caption for the radio button group by creating static text and placing it to the left of or above the group. (See Labeling radio buttons below.)

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


Input: [Control Type] Combo box [LiveCycle Placement Rules]

Output: Default placement for the label is to the left of the drop-down list. If this is not possible, LiveCycle will attempt to place it immediately above the control..

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


Input: [Control Type] List box [LiveCycle Placement Rules]

Output: Default placement for the label is above the list box.

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


Input: [Control Type] Button [LiveCycle Placement Rules]

Output: LiveCycle automatically places the label on the button; it does not have to be positioned manually. Ensure that the button's purpose is properly described in the label text.

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


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 [Inheritance]

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

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


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

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

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


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

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


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

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

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


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

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


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

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

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


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

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


Input: [Level] 2. [testability of specification] In addition to the regular specifications reviews mentioned in the previous level, Working Group commits to develop a set of test assertions, not necessarily complete, before beginning development of a test suite. [extent of test materials]

Output: Working Group commits that test suite for the specification, not necessarily complete and thorough, will exist before specification becomes Recommendation.


Input: [Level] 3. [testability of specification] In addition to regular specification reviews, a Working Group aims to have numerous normative use cases in the body of the Recommendation. [extent of test materials]

Output: In addition to the commitment of the previous level, a Working Group ensures that the test suite produced is reviewed by the Working Group or externally and the review process meets the criteria established in this document.


Input: [Level] 4. [testability of specification] Same as above. [extent of test materials]

Output: Working Group commits to establish and maintain the test cases contribution and review process and will produce and review the test suite, not necessarily complete and thorough, before the specification becomes Recommendation.


Input: [Level] 5. [testability of specification] In addition to the commitments from the previous level, Working Group will derive the list of testable assertions as an addendum to specification by the time it becomes Recommendation. [extent of test materials]

Output: Same as above


Input: [Level] 6. [testability of specification] Same as above [extent of test materials]

Output: In addition to the commitment for the previous level, a Working Group insists on a complete test suite before corresponding standard becomes Recommendation.


Input: [Level] 7. [testability of specification] Same as above [extent of test materials]

Output: In addition to the commitment for the previous level, Working Group plans to maintain the test suite even after Specification becomes recommendation. Working Group plans to support versioning and errata in the test suite and review appeals.


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

Output: An ECMAScript expression returning the target location of the event. The target attribute specifies the unique identifier of the event target that the Event I/O Processor must send the event to.

Voice Browser Call Control: CCXML Version 1.0


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

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] sendid [Required] false [Type] ECMAScript Left Hand Side Expression [Default Value] none [Valid Values] ECMAScript Variable [Description]

Output: An ECMAScript left hand side expression evaluating to a previously defined variable. The value of the attribute must receive an internally generated unique string identifier to be associated with the event being sent.

Voice Browser Call Control: CCXML Version 1.0


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

Output: The character string returned must be interpreted as a time interval. The send element must return immediately, but the event must not be dispatched until the delay interval elapses. Timers are useful for a wide variety of programming tasks, and can be implemented using this attribute. Note: The delayed event queue for sending events must be maintained locally. Any events waiting to be sent must be purged when the session that issued this request terminates.

Voice Browser Call Control: CCXML Version 1.0


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

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] namelist [Required] false [Attribute Constraints] This attribute must not be specified in conjunction with inline content [Type] Var List [Default Value] none [Valid Values] List of ECMAScript Variable names [Description]

Output: A list of zero or more whitespace separated CCXML variable names to be included with the event. Values for these variables are evaluated when the element is processed See section 9.2.3.1 for details on how these variables are made available to the target. If used in conjunction with the inline content, an error.fetch must be thrown.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] hints [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression that returns an ECMAScript object [Description]

Output: The ECMAScript object returned contains information which may be used by the implementing platform to configure the event processor. Event I/O Processor. The meaning of these hints is specific to the implementing platform and the event processor. Event I/O Processor. Note: The meaning of these hints is specific to the implementing platform and protocol. Platforms that do not support hints MAY ignore this attribute. See Section 9.5.6 for additional requirements when hints are supported by the implementing platform.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] target [Required] true [Type] ECMAScript Expression [Default Value] none [Description] An ECMAScript expression returning the target location of the event. The target attribute specifies the unique identifier of the event target that the Event I/O Processor must send the event to. [Valid Values]

Output: A valid target URL URI

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] targettype [Required] false [Type] ECMAScript Expression [Default Value] ccxml [Description] An ECMAScript expression which returns a character string that specifies the type of the Event I/O Processor that the event must be dispatched to. Values defined by the specification are: ccxml This specifies that the event must be dispatched to the CCXML Session Event Processor.. dialog This specifies that the event must be dispatched to the Dialog Event Processor. basichttp This specifies that the event must be dispatched to the Basic HTTP Event Processor. [Valid Values]

Output: ccxml dialog basichttp

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] sendid [Required] false [Type] ECMAScript Left Hand Side Expression [Default Value] none [Description] An ECMAScript left hand side expression evaluating to a previously defined variable. The value of the attribute must receive an internally generated unique string identifier to be associated with the event being sent. [Valid Values]

Output: ECMAScript Variable

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] delay [Required] false [Type] ECMAScript Expression [Default Value] '0s' [Description] The character string returned must be interpreted as a time interval. The send element must return immediately, but the event must not be dispatched until the delay interval elapses. Timers are useful for a wide variety of programming tasks, and can be implemented using this attribute. Note: The delayed event queue for sending events must be maintained locally. Any events waiting to be sent must be purged when the session that issued this request terminates. [Valid Values]

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] namelist [Required] false [Attribute Constraints] This attribute must not be specified in conjunction with inline content [Type] Var List [Default Value] none [Description] A list of zero or more whitespace separated CCXML variable names to be included with the event. Values for these variables are evaluated when the element is processed See section 9.2.3.1 for details on how these variables are made available to the target. If used in conjunction with the inline content, an error.fetch must be thrown. [Valid Values]

Output: List of ECMAScript Variable names

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] hints [Required] false [Type] ECMAScript Expression [Default Value] none [Description] The ECMAScript object returned contains information which may be used by the implementing platform to configure the event processor. Event I/O Processor. The meaning of these hints is specific to the implementing platform and the event processor. Event I/O Processor. Note: The meaning of these hints is specific to the implementing platform and protocol. Platforms that do not support hints MAY ignore this attribute. See Section 9.5.6 for additional requirements when hints are supported by the implementing platform. [Valid Values]

Output: An ECMAScript expression that returns an ECMAScript object

Voice Browser Call Control: CCXML Version 1.0


Input: [Parameter] propertyNames [Type] DOMString[] [Nullable] ✘ [Optional] ✘ [Description]

Output: This argument identifies an array containing the properties for which the values need to be retrieved. For an empty array all properties carrying values will be retrieved. Optional arguments allow refining the request.


Input: [Parameter] successCallback [Type] PropertyCallback [Nullable] ✘ [Optional] ✘ [Description]

Output: This argument holds a callback object for asynchronous requests to the property. The successCallback object implements the PropertyCallback interface and holds a handleEvent operation that needs to be called once all data for the requested property is gathered. This handleEvent operation needs to be called with a new MediaAnnotation array.


Input: [Parameter] errorCallback [Type] ErrorCallback [Nullable] ✘ [Optional] ✘ [Description]

Output: This argument holds a callback object for failure of asynchronous requests to the property. The errorCallback object implements the ErrorCallback interface and holds a handleEvent operation that needs to be called if an attempt fails. This handleEvent operation needs to be called with a new DOMString representing the status code of the error (see Section 4.7 for details).


Input: [Parameter] fragment [Type] DOMString [Nullable] ✘ [Optional] ✔ [Description]

Output: This argument contains a URI identifying the specific media fragment for which the metadata is requested. The URI must conform to the URI for Media Fragment [MEDIA-FRAGMENTS] specification. This parameter is optional.


Input: [Parameter] sourceFormat [Type] DOMString [Nullable] ✘ [Optional] ✔ [Description]

Output: This argument identifies a specific metadata format. It should use the metadata format identifiers defined in the Ontology for Media Resources 1.0 specification. If a metadata format is defined, only the metadata available in the corresponding metadata format are retrieved. This parameter is optional.


Input: [Parameter] language [Type] DOMString [Nullable] ✘ [Optional] ✔ [Description]

Output: This argument allows to identify the language of the metadata. Values for the metadata will only be returned if it is available in the specified language. Recommended best practice is to use BCP 47 [BCP47]. This parameter is optional.


Input: [Level] 1. [testability of specification]

Output: Working Group plans regular specification reviews for testability, following Specification Guidelines


Input: [Level] 2. [extent of test materials] Working Group commits that test suite for the specification, not necessarily complete and thorough, will exist before specification becomes Recommendation. [testability of specification]

Output: In addition to the regular specifications reviews mentioned in the previous level, Working Group commits to develop a set of test assertions, not necessarily complete, before beginning development of a test suite.


Input: [Level] 3. [extent of test materials] In addition to the commitment of the previous level, a Working Group ensures that the test suite produced is reviewed by the Working Group or externally and the review process meets the criteria established in this document. [testability of specification]

Output: In addition to regular specification reviews, a Working Group aims to have numerous normative use cases in the body of the Recommendation.


Input: [Level] 4. [extent of test materials] Working Group commits to establish and maintain the test cases contribution and review process and will produce and review the test suite, not necessarily complete and thorough, before the specification becomes Recommendation. [testability of specification]

Output: Same as above.


Input: [Level] 5. [extent of test materials] Same as above [testability of specification]

Output: In addition to the commitments from the previous level, Working Group will derive the list of testable assertions as an addendum to specification by the time it becomes Recommendation.


Input: [Level] 6. [extent of test materials] In addition to the commitment for the previous level, a Working Group insists on a complete test suite before corresponding standard becomes Recommendation. [testability of specification]

Output: Same as above


Input: [Level] 7. [extent of test materials] In addition to the commitment for the previous level, Working Group plans to maintain the test suite even after Specification becomes recommendation. Working Group plans to support versioning and errata in the test suite and review appeals. [testability of specification]

Output: Same as above


Input: [Description] Solid background colour to be used when presenting the image if no better option is available. [Type of information]

Output: Background colour

Portable Network Graphics (PNG) Specification (Second Edition)


Input: [Description] Gamma characteristic of the image with respect to the desired output intensity, and chromaticity characteristics of the RGB values used in the image. [Type of information]

Output: Gamma and chromaticity

Portable Network Graphics (PNG) Specification (Second Edition)


Input: [Description] Description of the colour space (in the form of an International Color Consortium (ICC) profile) to which the samples in the image conform. [Type of information]

Output: ICC profile

Portable Network Graphics (PNG) Specification (Second Edition)


Input: [Description] Estimates of how frequently the image uses each palette entry. [Type of information]

Output: Image histogram

Portable Network Graphics (PNG) Specification (Second Edition)


Input: [Description] Intended pixel size and aspect ratio to be used in presenting the PNG image. [Type of information]

Output: Physical pixel dimensions

Portable Network Graphics (PNG) Specification (Second Edition)


Input: [Description] The number of bits that are significant in the samples. [Type of information]

Output: Significant bits

Portable Network Graphics (PNG) Specification (Second Edition)


Input: [Description] A rendering intent (as defined by the International Color Consortium) and an indication that the image samples conform to this colour space. [Type of information]

Output: sRGB colour space

Portable Network Graphics (PNG) Specification (Second Edition)


Input: [Description] A reduced palette that may be used when the display device is not capable of displaying the full range of colours in the image. [Type of information]

Output: Suggested palette

Portable Network Graphics (PNG) Specification (Second Edition)


Input: [Description] Textual information (which may be compressed) associated with the image. [Type of information]

Output: Textual data

Portable Network Graphics (PNG) Specification (Second Edition)


Input: [Description] The time when the PNG image was last modified. [Type of information]

Output: Time

Portable Network Graphics (PNG) Specification (Second Edition)


Input: [Description] Alpha information that allows the reference image to be reconstructed when the alpha channel is not retained in the PNG image. [Type of information]

Output: Transparency

Portable Network Graphics (PNG) Specification (Second Edition)


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 [Overriding]

Output: Yes

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


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

Output: Yes

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


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

Output: Not applicable

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


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

Output: Yes

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


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

Output: Not applicable

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


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

Output: Yes

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


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

Output: Not applicable

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


Input: [Function] avg [Arguments] node-set [Description] Average [Returns]

Output: number


Input: [Function] boolean-from-string [Arguments] string [Description] Type conversion [Returns]

Output: boolean


Input: [Function] count-non-empty [Arguments] node-set [Description] Count non-empty [Returns]

Output: number


Input: [Function] days-from-date [Arguments] string [Description] Days in epoch [Returns]

Output: number


Input: [Function] if [Arguments] boolean, string, string [Description] Conditional [Returns]

Output: string


Input: [Function] index [Arguments] string [Description] Repeat index [Returns]

Output: number


Input: [Function] instance [Arguments] string [Description] Locate instance [Returns]

Output: node-set


Input: [Function] max [Arguments] node-set [Description] Maximum [Returns]

Output: number


Input: [Function] min [Arguments] node-set [Description] Minimum [Returns]

Output: number


Input: [Function] months [Arguments] string [Description] Months in period [Returns]

Output: number


Input: [Function] now [Arguments] - [Description] Current time [Returns]

Output: string


Input: [Function] property [Arguments] string [Description] Feature value [Returns]

Output: string


Input: [Function] seconds [Arguments] string [Description] Seconds in period [Returns]

Output: number


Input: [Function] seconds-from-dateTime [Arguments] string [Description] Seconds in epoch [Returns]

Output: number


Input: [Event name] loadstart [Dispatched when...]

Output: The user agent begins looking for media data, as part of the resource selection algorithm.


Input: [Event name] progress [Dispatched when...]

Output: The user agent is fetching media data.


Input: [Event name] suspend [Dispatched when...]

Output: The user agent is intentionally not currently fetching media data, but does not have the entire media resource downloaded.


Input: [Event name] abort [Dispatched when...]

Output: The user agent stops fetching the media data before it is completely downloaded, but not due to an error.


Input: [Event name] error [Dispatched when...]

Output: An error occurs while fetching the media data.


Input: [Event name] emptied [Dispatched when...]

Output: A media element whose networkState was previously not in the NETWORK_EMPTY state has just switched to that state (either because of a fatal error during load that's about to be reported, or because the load() method was invoked while the resource selection algorithm was already running).


Input: [Event name] stalled [Dispatched when...]

Output: The user agent is trying to fetch media data, but data is unexpectedly not forthcoming.


Input: [Event name] play [Dispatched when...]

Output: Playback has begun. Fired after the play() method has returned, or when the autoplay attribute has caused playback to begin.


Input: [Event name] pause [Dispatched when...]

Output: Playback has been paused. Fired after the pause() method has returned.


Input: [Event name] loadedmetadata [Dispatched when...]

Output: The user agent has just determined the duration and dimensions of the media resource


Input: [Event name] loadeddata [Dispatched when...]

Output: The user agent can render the media data at the current playback position for the first time.


Input: [Event name] waiting [Dispatched when...]

Output: Playback has stopped because the next frame is not available, but the user agent expects that frame to become available in due course.


Input: [Event name] playing [Dispatched when...]

Output: Playback has started.


Input: [Event name] canplay [Dispatched when...]

Output: The user agent can resume playback of the media data, but estimates that if playback were to be started now, the media resource could not be rendered at the current playback rate up to its end without having to stop for further buffering of content.


Input: [Event name] canplaythrough [Dispatched when...]

Output: The user agent estimates that if playback were to be started now, the media resource could be rendered at the current playback rate all the way to its end without having to stop for further buffering.


Input: [Event name] seeking [Dispatched when...]

Output: The seeking IDL attribute changed to true and the seek operation is taking long enough that the user agent has time to fire the event.


Input: [Event name] seeked [Dispatched when...]

Output: The seeking IDL attribute changed to false.


Input: [Event name] timeupdate [Dispatched when...]

Output: The current playback position changed as part of normal playback or in an especially interesting way, for example discontinuously.


Input: [Event name] ended [Dispatched when...]

Output: Playback has stopped because the end of the media resource was reached.


Input: [Event name] ratechange [Dispatched when...]

Output: Either the defaultPlaybackRate or the playbackRate attribute has just been updated.


Input: [Event name] durationchange [Dispatched when...]

Output: The duration attribute has just been updated.


Input: [Event name] volumechange [Dispatched when...]

Output: Either the volume attribute or the muted attribute has changed. Fired after the relevant attribute's setter has returned.


Input: [Type] DOMString[] [Nullable] ✘ [Optional] ✘ [Description] This argument identifies an array containing the properties for which the values need to be retrieved. For an empty array all properties carrying values will be retrieved. Optional arguments allow refining the request. [Parameter]

Output: propertyNames


Input: [Type] PropertyCallback [Nullable] ✘ [Optional] ✘ [Description] This argument holds a callback object for asynchronous requests to the property. The successCallback object implements the PropertyCallback interface and holds a handleEvent operation that needs to be called once all data for the requested property is gathered. This handleEvent operation needs to be called with a new MediaAnnotation array. [Parameter]

Output: successCallback


Input: [Type] ErrorCallback [Nullable] ✘ [Optional] ✘ [Description] This argument holds a callback object for failure of asynchronous requests to the property. The errorCallback object implements the ErrorCallback interface and holds a handleEvent operation that needs to be called if an attempt fails. This handleEvent operation needs to be called with a new DOMString representing the status code of the error (see Section 4.7 for details). [Parameter]

Output: errorCallback


Input: [Type] DOMString [Nullable] ✘ [Optional] ✔ [Description] This argument contains a URI identifying the specific media fragment for which the metadata is requested. The URI must conform to the URI for Media Fragment [MEDIA-FRAGMENTS] specification. This parameter is optional. [Parameter]

Output: fragment


Input: [Type] DOMString [Nullable] ✘ [Optional] ✔ [Description] This argument identifies a specific metadata format. It should use the metadata format identifiers defined in the Ontology for Media Resources 1.0 specification. If a metadata format is defined, only the metadata available in the corresponding metadata format are retrieved. This parameter is optional. [Parameter]

Output: sourceFormat


Input: [Type] DOMString [Nullable] ✘ [Optional] ✔ [Description] This argument allows to identify the language of the metadata. Values for the metadata will only be returned if it is available in the specified language. Recommended best practice is to use BCP 47 [BCP47]. This parameter is optional. [Parameter]

Output: language


Input: [Topic] ScholarlyArticle [Status] Early proposal from HighWire Press needs review. [Summary] Various ideas around improving ScholarlyArticle. [Vocab] Suggestion that scholarly articles could be described in more detail. [Comments]

Output: There is a lot of related work in this area. For example Google Scholar publisher guidelines; Microsoft Academic Search. The Open Archives Initiative - Protocol for Metadata Harvesting also addresses this problem area and has broad adoption. See also earlier comments from HighWire Press (pdf) and following discussion (on the old mailing list).

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Real Estate [Status] Discussions but no proposal yet. [Summary] Enthusiastic discussion in favour of adding RealEstate support. Tracked as issue 13. This should likely follow along after the Good Relations work. [Vocab] N/A [Comments]

Output: Related to Place vocabulary, and schema.org's numerous subclasses, and Offer class.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Vehicles [Status] Anticipated. [Summary] A proposal extending schema.org for describing vehicles is being prepared. [Comments]

Output: No public draft yet.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Transport Data [Status] Discussion [Summary] Initial discussion on description of transport data. [Vocab] N/A [Comments]

Output: Discussions on whether this scenario can be covered with existing vocabulary.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Activities (things you can do) [Status] Proposal [Summary] Vocabulary for describing general activities not bound to any specific time or place. Unrelated to the Activities and Actions proposal for online user page interations that are listed above. [Vocab] Examples: 'Paragliding'. 'Going to the cinema', etc. [Comments]

Output: Public draft and description available on wiki. Original proposal on public vocabs mailinglist.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Project [Status] Proposal [Summary] Vocabulary for describing any kind of project [Vocab] Terms (loosely) based on this project vocabulary [Comments]

Output: Use case gathering - see mailing list thread

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Vacation Rental Schema [Status] Proposal [Summary] Creating an additional vocabulary for this hotel-alternative accommodation [Vocab] Overview of new terms [Comments]

Output: Just initiated the discussion around this schema. Public proposal available on the Wiki

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Fictional Thing [Status] Proposal [Summary] Providing the ability to identify a thing as being fictional [Vocab] Proposal for the creation of a FictionalThing type [Comments]

Output: Supporting discussion around this schema. Public proposal available on the Wiki

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] JobMarket [Status] Proposal [Summary] Extension for modelling job markets [Vocab] Classes added: Compensation, WorkExperience + class amended: JobPosting [Comments]

Output: Draft for an extension published to elicit feedback

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] VisualArtwork [Status] Early Proposal [Summary] Extension for CreativeWork and replacement/alternative to Painting and Sculpture [Vocab] Overview of Extension and new properties [Comments]

Output: Early draft for an extension published to elicit feedback.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] GeoJSON [Status] Early propsal [Summary] addition to the Geo* family of topics. [Vocab] N/A [Comments]

Output: Related to Place vocabulary

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Looking Inside Tables [Status] Early proposal [Summary] A mechanism to map the contents of tables into entities. [Vocab] N/A [Comments]

Output: Draft for an extension published to elicit feedback.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Online Presence [Status] Early proposal [Summary] expressing Online Presence and current Actions [Vocab] WIP [Comments]

Output: Related to Action subtree and Online Presence Ontology.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Property-Value Pairs [Status] Work in progress [Summary] Adding support for arbitrary property-value pairs. Useful for product features and as a generic extension mechanism for properties in schema.org. [Vocab] N/A [Comments]

Output: Mirrors an upcoming feature in GoodRelations.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] SocialAccount [Status] Proposal [Summary] Introduce a type and a property to describe social accounts of http://schema.org/Person or http://schema.org/Organization [Vocab] Add SocialAccount type derived from http://schema.org/Thing to capture social account. Update http://schema.org/Person and http://schema.org/Organization by adding the property socialAccount expecting the type SocialAccount [Comments]

Output: See also the mailing list discussion

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] socialAccount [Status] Proposal [Summary] Introduce a property to describe social accounts of http://schema.org/Person and http://schema.org/Organization [Vocab] Update http://schema.org/Person and http://schema.org/Organization by adding the property socialAccount expecting a URL as value [Comments]

Output: See also the mailing list discussion This is an alternative of the previous item

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic] Proposal name [Status] How far along [Summary] Summary of contribution. [Vocab] Overview of new terms [Comments]

Output: Comments on status, particularly regarding integration, overlaps and open issues.

WebSchemas/SchemaDotOrgProposals - W3C Wiki


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

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] type [Required] false [Type] ECMAScript Expression [Default Value] In processed mode "application/ccxml+xml". In raw mode "*/*". [Valid Values] MIME Types formatted as per HTTP Accept header [RFC2616] [Description]

Output: An ECMAScript expression which returns a character string that specifies setting the MIME type value of the fetched content. Values defined by the specification are: application/ccxml+xml This specifies that the document being fetched must be a CCXML document. text/ecmascript This specifies that HTTP Accept header to tell the fetched application server what content must be ECMA Script. text/javascript This specifies that type the fetched content must be JAVA Script. application wishes to have returned.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] namelist [Required] false [Type] Var List [Default Value] none [Valid Values] List of ECMAScript Variable names [Description]

Output: A list of zero or more whitespace separated CCXML variable names. These variables must be submitted to the web server, with the same qualification as used in the namelist. When an ECMAscript ECMAScript variable is submitted to the web server, its value must be first converted into a string before being submitted. If the variable is an ECMAScript Object, the mechanism by which it must be submitted is not currently defined. Instead of submitting ECMAScript Objects directly, the application developer may explicitly submit the properties of an Object. e.g. "date.month date.year".

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] method [Required] false [Type] ECMAScript Expression [Default Value] get [Valid Values] get post [Description]

Output: An ECMAScript expression which returns a character string that indicates the HTTP method to use. Values defined by the specification are: get This indicates that the "GET" method must be used to fetch the URL. URI post This indicates that the "POST" method must be used while submitting the URL URI to the web server.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] fetchid [Required] false [Type] ECMAScript Left Hand Side Expression [Default Value] none [Valid Values] ECMAScript Variable [Description]

Output: An ECMAScript left hand side expression evaluating to a previously defined variable. The value of the attribute must receive an internally generated unique string identifier to be associated with the completion event. This identifier can be tested by the fetch completion event handler to distinguish among several outstanding fetch requests. If this attribute is not specified, the fetch identifier can be acquired from the fetch completion event. Every fetch request must receive a unique fetch identifier, even if the request is for the same URL. URI

Voice Browser Call Control: CCXML Version 1.0


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

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] maxage [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression which returns a valid time value for the HTTP 1.1 request [RFC2616] [Description]

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] maxstale [Required] false [Type] ECMAScript Expression [Default Value] none [Valid Values] An ECMAScript expression which returns a valid time value for the HTTP 1.1 request [RFC2616] [Description]

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] enctype [Required] false [Attribute Constraints] Valid only when the value of the method is "post" [Type] ECMAScript Expression [Default Value] application/x-www-form-urlencoded [Valid Values] valid media encoding type [Description]

Output: An ECMAScript expression which returns a character string that indicates the media encoding type of the submitted document (when the value of the method is "post"). Values defined by the specification are: application/x-www-form-urlencoded This indicates that the ccxml variables specified in the namelist must be url encoded.

Voice Browser Call Control: CCXML Version 1.0


Input: [Name] mode [Required] false [Type] ECMAScript Expression [Default Value] processed [Valid Values] processed, raw [Description]

Output: Controls what the CCXML platform should do with fetched content. If set to processed (the default) the CCXML platform MUST attempt to parse and validate the returned content. If set to raw the platform MUST NOT attempt to process the data and MUST leave processing of the content to the application who can do what it wishes with the content via the content attribute of the fetch.done event

Voice Browser Call Control: CCXML Version 1.0


Input: [Language feature] a element that creates a hyperlink [Restrictions] Role must be either link, button, checkbox, menuitem, menuitemcheckbox, menuitemradio , tab, or treeitem [Default implied ARIA semantic]

Output: link role


Input: [Language feature] address element [Restrictions] If specified, role must be contentinfo [Default implied ARIA semantic]

Output: No role


Input: [Language feature] article element [Restrictions] Role must be either article, document, application, or main [Default implied ARIA semantic]

Output: article role


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

Output: note role


Input: [Language feature] audio element [Restrictions] If specified, role must be application [Default implied ARIA semantic]

Output: No role


Input: [Language feature] button element [Restrictions] Role must be either button, link, menuitem, menuitemcheckbox, menuitemradio , radio [Default implied ARIA semantic]

Output: button role


Input: [Language feature] details element [Restrictions] Role must be a role that supports aria-expanded [Default implied ARIA semantic]

Output: group role


Input: [Language feature] dialog element [Restrictions] Role must be either alert, alertdialog, application, contentinfo, dialog, document, log, main, marquee, region, search, or status [Default implied ARIA semantic]

Output: dialog role


Input: [Language feature] embed element [Restrictions] If specified, role must be either application, document, or img [Default implied ARIA semantic]

Output: No role


Input: [Language feature] footer element [Restrictions] If specified, role must be contentinfo [Default implied ARIA semantic]

Output: No role


Input: [Language feature] h1 element that does not have an hgroup ancestor [Restrictions] Role must be either heading or tab [Default implied ARIA semantic]

Output: heading role, with the aria-level property set to the element's outline depth


Input: [Language feature] h2 element that does not have an hgroup ancestor [Restrictions] Role must be either heading or tab [Default implied ARIA semantic]

Output: heading role, with the aria-level property set to the element's outline depth


Input: [Language feature] h3 element that does not have an hgroup ancestor [Restrictions] Role must be either heading or tab [Default implied ARIA semantic]

Output: heading role, with the aria-level property set to the element's outline depth


Input: [Language feature] h4 element that does not have an hgroup ancestor [Restrictions] Role must be either heading or tab [Default implied ARIA semantic]

Output: heading role, with the aria-level property set to the element's outline depth


Input: [Language feature] h5 element that does not have an hgroup ancestor [Restrictions] Role must be either heading or tab [Default implied ARIA semantic]

Output: heading role, with the aria-level property set to the element's outline depth


Input: [Language feature] h6 element that does not have an hgroup ancestor [Restrictions] Role must be either heading or tab [Default implied ARIA semantic]

Output: heading role, with the aria-level property set to the element's outline depth


Input: [Language feature] header element [Restrictions] If specified, role must be banner [Default implied ARIA semantic]

Output: No role


Input: [Language feature] iframe element [Restrictions] If specified, role must be either application, document, or img [Default implied ARIA semantic]

Output: No role


Input: [Language feature] img element whose alt attribute's value is absent [Restrictions] No restrictions [Default implied ARIA semantic]

Output: img role


Input: [Language feature] img element whose alt attribute's value is present and not empty [Restrictions] No restrictions [Default implied ARIA semantic]

Output: img role


Input: [Language feature] input element with a type attribute in the Button state [Restrictions] Role must be either button, link, menuitem, menuitemcheckbox, menuitemradio , radio [Default implied ARIA semantic]

Output: button role


Input: [Language feature] input element with a type attribute in the Checkbox state [Restrictions] Role must be either checkbox or menuitemcheckbox [Default implied ARIA semantic]

Output: checkbox role


Input: [Language feature] input element with a type attribute in the Image Button state [Restrictions] Role must be either button, link, menuitem, menuitemcheckbox, menuitemradio , radio [Default implied ARIA semantic]

Output: button role


Input: [Language feature] input element with a type attribute in the Radio Button state [Restrictions] Role must be either radio or menuitemradio [Default implied ARIA semantic]

Output: radio role


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

Output: listitem role


Input: [Language feature] object element [Restrictions] If specified, role must be either application, document, or img [Default implied ARIA semantic]

Output: No role


Input: [Language feature] ol element [Restrictions] Role must be either directory, list, listbox, menu, menubar, tablist, toolbar, tree [Default implied ARIA semantic]

Output: list role


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

Output: status role


Input: [Language feature] section element [Restrictions] Role must be either alert, alertdialog, application, contentinfo, dialog, document, log, main, marquee, region, search, or status [Default implied ARIA semantic]

Output: region role


Input: [Language feature] ul element [Restrictions] Role must be either directory, list, listbox, menu, menubar, tablist, toolbar, tree [Default implied ARIA semantic]

Output: list role


Input: [Language feature] video element [Restrictions] If specified, role must be application [Default implied ARIA semantic]

Output: No role


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

Output: document role


Input: [Additive?] yes [‘set’] yes [‘animateColor’] no [‘animateTransform’] no [‘animate’]

Output: yes


Input: [Additive?] yes [‘set’] yes [‘animateColor’] yes [‘animateTransform’] no [Notes] Only additive if each value can be converted to an RGB color. [‘animate’]

Output: yes


Input: [Additive?] no [‘set’] no [‘animateColor’] no [‘animateTransform’] no [‘animate’]

Output: no


Input: [Additive?] no [‘set’] yes [‘animateColor’] no [‘animateTransform’] no [‘animate’]

Output: yes


Input: [Additive?] yes [‘set’] no [‘animateColor’] no [‘animateTransform’] yes [Notes] Additive means that a transformation is post-multiplied to the base set of transformations. [‘animate’]

Output: no


Input: [Data type] All other data types used in animatable attributes and properties [Additive?] no [‘set’] yes [‘animateColor’] no [‘animateTransform’] no [‘animate’]

Output: yes


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 [Overriding]

Output: Yes

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


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

Output: Yes

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


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

Output: Not applicable

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


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

Output: Yes

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


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

Output: Not applicable

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


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

Output: Yes

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


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

Output: Not applicable

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


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

Output: The ID of the dialog.

Voice Browser Call Control: CCXML Version 1.0


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

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

Voice Browser Call Control: CCXML Version 1.0


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

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

Voice Browser Call Control: CCXML Version 1.0


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

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

Voice Browser Call Control: CCXML Version 1.0


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

Output: A string value specifying the transfer type.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] uri [Required] true [Type] a valid URI [Details]

Output: A URI describing the destination to which this call must be transferred. The format of this information is protocol and platform specific but might consist of a telephone URI RFC3966 or a SIP URI RFC3261 .

Voice Browser Call Control: CCXML Version 1.0


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

Output: Properties returned from the dialog processor relating to the dialogs transfer request.

Voice Browser Call Control: CCXML Version 1.0


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

Output: A string in CSS2 format that specifies the maximum amount of time the transfer may stay connected. If the amount of time is unlimited the value must be 0s.

Voice Browser Call Control: CCXML Version 1.0


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

Output: A string in CSS2 format that specifies the maximum amount of time to spend while attempting to connect the call.

Voice Browser Call Control: CCXML Version 1.0


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

Output: A string of application-to-application information to be passed to the destination party when establishing the transfer.

Voice Browser Call Control: CCXML Version 1.0


Input: [LiveCycle Placement Rules] Default placement for the label is to the left of the control. If this is not possible, LiveCycle will attempt to place it immediately above the control. [Control Type]

Output: Text input (including date/time and password fields)

Text input (including date/time and password fields)

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


Input: [LiveCycle Placement Rules] Default placement for the label is to the right of the check box. [Control Type]

Output: Checkbox

Text input (including date/time and password fields)

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


Input: [LiveCycle Placement Rules] Default placement for the label for each individual radio button is to the right of the button. Create a visible caption for the radio button group by creating static text and placing it to the left of or above the group. (See Labeling radio buttons below.) [Control Type]

Output: Radio button group

Text input (including date/time and password fields)

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


Input: [LiveCycle Placement Rules] Default placement for the label is to the left of the drop-down list. If this is not possible, LiveCycle will attempt to place it immediately above the control.. [Control Type]

Output: Combo box

Text input (including date/time and password fields)

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


Input: [LiveCycle Placement Rules] Default placement for the label is above the list box. [Control Type]

Output: List box

Text input (including date/time and password fields)

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


Input: [LiveCycle Placement Rules] LiveCycle automatically places the label on the button; it does not have to be positioned manually. Ensure that the button's purpose is properly described in the label text. [Control Type]

Output: Button

Text input (including date/time and password fields)

PDF10: Providing labels for interactive form controls in PDF documents | Techniques for WCAG 2.0


Input: [Parameter] propertyNames [Type] DOMString[] [Nullable] ✘ [Description] This argument identifies an array containing the properties for which the values need to be retrieved. For an empty array all properties carrying values will be retrieved. Optional arguments allow refining the request. [Optional]


Input: [Parameter] successCallback [Type] PropertyCallback [Nullable] ✘ [Description] This argument holds a callback object for asynchronous requests to the property. The successCallback object implements the PropertyCallback interface and holds a handleEvent operation that needs to be called once all data for the requested property is gathered. This handleEvent operation needs to be called with a new MediaAnnotation array. [Optional]


Input: [Parameter] errorCallback [Type] ErrorCallback [Nullable] ✘ [Description] This argument holds a callback object for failure of asynchronous requests to the property. The errorCallback object implements the ErrorCallback interface and holds a handleEvent operation that needs to be called if an attempt fails. This handleEvent operation needs to be called with a new DOMString representing the status code of the error (see Section 4.7 for details). [Optional]


Input: [Parameter] fragment [Type] DOMString [Nullable] ✘ [Description] This argument contains a URI identifying the specific media fragment for which the metadata is requested. The URI must conform to the URI for Media Fragment [MEDIA-FRAGMENTS] specification. This parameter is optional. [Optional]


Input: [Parameter] sourceFormat [Type] DOMString [Nullable] ✘ [Description] This argument identifies a specific metadata format. It should use the metadata format identifiers defined in the Ontology for Media Resources 1.0 specification. If a metadata format is defined, only the metadata available in the corresponding metadata format are retrieved. This parameter is optional. [Optional]


Input: [Parameter] language [Type] DOMString [Nullable] ✘ [Description] This argument allows to identify the language of the metadata. Values for the metadata will only be returned if it is available in the specified language. Recommended best practice is to use BCP 47 [BCP47]. This parameter is optional. [Optional]


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: [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 [Inheritance]

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

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


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

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

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


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

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


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

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

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


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

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


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

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

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


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

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


Input: [Identifier] assigner [Comment] Must be supported. [Semantics]

Output: The Party is the issuer of the policy statement

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

Table 2.4.1: Terms for the attribute “function” of the entity Role


Input: [Identifier] assignee [Comment] Must be supported. [Semantics]

Output: The Party is the recipient of the policy statement

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] attributedParty [Comment] May be specified as part of the attribute action. [Semantics]

Output: The Party to be attributed

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] consentingParty [Comment] May be specified as part of the obtainConsent action. [Semantics]

Output: The Party to obtain consent from

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] informedParty [Comment] May be specified as part of the inform action. [Semantics]

Output: The Party to be informed of all uses

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] compensatedParty [Comment] May be specified as part of the compensate duty action. [Semantics]

Output: The Party is the recipient of the compensation

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] trackingParty [Comment] May be specified as part of the acceptTracking action. [Semantics]

Output: The Party is the usage tracker

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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 71: 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 71: 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 71: 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 71: 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 71: 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 71: Speech Recognition Properties