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

Output: Success or Failure

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


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

Output: Success or Failure

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


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

Output: Success or Error

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


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

Output: Success or Failure

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


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

Output: Success or Failure

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


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

Output: value

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


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

Output: value

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


Input: [Numerical Code] 200 [Example] property delivered correctly [Textual Description]

Output: Ok OK


Input: [Numerical Code] 204 [Example] property retrieved without content [Textual Description]

Output: No Content


Input: [Numerical Code] 206 [Example] only a subset of the available data stored in the result set [Textual Description]

Output: Partial Content


Input: [Numerical Code] 400 [Example] syntactical error with respect to the GET method used [Textual Description]

Output: Bad Request


Input: [Numerical Code] 404 [Example] the queries resource is not found [Textual Description]

Output: Not Found


Input: [Numerical Code] 415 [Example] get duration call on an image data store [Textual Description]

Output: Unsupported Media Type


Input: [Numerical Code] 462 [Example] location is not defined in MediaRSS [Textual Description]

Output: Property not defined in Source Format


Input: [Numerical Code] 500 [Example] internal library (e.g., extractor) crashes [Textual Description]

Output: Internal Server Error


Input: [Numerical Code] 501 [Example] only a subset of GET methods for properties implemented [Textual Description]

Output: Not Implemented


Input: [Definition] Character data [Attribute Type]

Output: CDATA

XHTML™ Modularization 1.1 - Second Edition


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

Output: ID

XHTML™ Modularization 1.1 - Second Edition


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

Output: IDREF

XHTML™ Modularization 1.1 - Second Edition


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

Output: IDREFS

XHTML™ Modularization 1.1 - Second Edition


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

Output: NAME

XHTML™ Modularization 1.1 - Second Edition


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

Output: NMTOKEN

XHTML™ Modularization 1.1 - Second Edition


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

Output: NMTOKENS

XHTML™ Modularization 1.1 - Second Edition


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

Output: Initiate the drag-and-drop operation


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

Output: Continue the drag-and-drop operation


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

Output: Reject immediate user selection as potential target element


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


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

Output: Reset the current drag operation to "none"


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

Output: Varies


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

Output: Varies


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

Output: Citation Promotion

WebSchemas/SchemaDotOrgProposals - W3C Wiki


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

Output: Accessibility

WebSchemas/SchemaDotOrgProposals - W3C Wiki


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

Output: sameThingAs

WebSchemas/SchemaDotOrgProposals - W3C Wiki


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

Output: Actions in Schema.org

WebSchemas/SchemaDotOrgProposals - W3C Wiki


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

Output: Orders in Schema.org

WebSchemas/SchemaDotOrgProposals - W3C Wiki


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

Output: Reservations in Schema.org

WebSchemas/SchemaDotOrgProposals - W3C Wiki


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

Output: EmailMessage type

WebSchemas/SchemaDotOrgProposals - W3C Wiki


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

Output: Workers Union type

WebSchemas/SchemaDotOrgProposals - W3C Wiki


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

Output: TV and Radio proposal

WebSchemas/SchemaDotOrgProposals - W3C Wiki


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

Output: Sports

WebSchemas/SchemaDotOrgProposals - W3C Wiki


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

Output: Comics and Serials

WebSchemas/SchemaDotOrgProposals - W3C Wiki


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

Output: Event schema update

WebSchemas/SchemaDotOrgProposals - W3C Wiki


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

Output: Historical Data proposal

WebSchemas/SchemaDotOrgProposals - W3C Wiki


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

Output: Biological Databases

WebSchemas/SchemaDotOrgProposals - W3C Wiki


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

Output: Breadcrumbs

WebSchemas/SchemaDotOrgProposals - W3C Wiki


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

Output: Discussion

WebSchemas/SchemaDotOrgProposals - W3C Wiki


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

Output: Innovation

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [Topic]

WebSchemas/SchemaDotOrgProposals - W3C Wiki


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

Output: Proposal name

WebSchemas/SchemaDotOrgProposals - W3C Wiki


Input: [0] The cells in [1] this table [2]

Output: should go


Input: [0] green when [1] you hover [2]

Output: the pointing


Input: [0] The rows in [1] this table [2]

Output: should go


Input: [0] dark green [1] when the [2]

Output: pointing device


Input: [0] is over the [1] five pixel [2]

Output: border spacing


Input: [0] Including here, [2]

Output: blank cells.


Input: [Numerical Code] 200 [Textual Description] Ok OK [Example]

Output: property delivered correctly


Input: [Numerical Code] 204 [Textual Description] No Content [Example]

Output: property retrieved without content


Input: [Numerical Code] 206 [Textual Description] Partial Content [Example]

Output: only a subset of the available data stored in the result set


Input: [Numerical Code] 400 [Textual Description] Bad Request [Example]

Output: syntactical error with respect to the GET method used


Input: [Numerical Code] 404 [Textual Description] Not Found [Example]

Output: the queries resource is not found


Input: [Numerical Code] 415 [Textual Description] Unsupported Media Type [Example]

Output: get duration call on an image data store


Input: [Numerical Code] 462 [Textual Description] Property not defined in Source Format [Example]

Output: location is not defined in MediaRSS


Input: [Numerical Code] 500 [Textual Description] Internal Server Error [Example]

Output: internal library (e.g., extractor) crashes


Input: [Numerical Code] 501 [Textual Description] Not Implemented [Example]

Output: only a subset of GET methods for properties implemented


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: [Event Name] dragstart [Target] Source node [Bubbles?] ✓ Bubbles [Cancelable?] ✓ Cancelable [effectAllowed] uninitialized [dropEffect] none [Default Action] Initiate the drag-and-drop operation [dataTransfer]

Output: Contains source node unless a selection is being dragged, in which case it is empty; files returns any files included in the drag operation


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

Output: Empty


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

Output: Empty


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

Output: Empty


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

Output: Empty


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

Output: getData() returns data set in dragstart event; files returns any files included in the drag operation


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

Output: Empty


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

Output: boolean

Voice Extensible Markup Language (VoiceXML) 3.0

Table 28: Attributes


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

Output: string

Voice Extensible Markup Language (VoiceXML) 3.0

Table 28: Attributes


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

Output: data model expression

Voice Extensible Markup Language (VoiceXML) 3.0

Table 28: Attributes


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

Output: positive integer

Voice Extensible Markup Language (VoiceXML) 3.0

Table 28: Attributes


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

Output: Time Designation

Voice Extensible Markup Language (VoiceXML) 3.0

Table 28: Attributes


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

Output: string

Voice Extensible Markup Language (VoiceXML) 3.0

Table 28: Attributes


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

Output: string

Voice Extensible Markup Language (VoiceXML) 3.0

Table 28: Attributes


Input: [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] details element [Restrictions] Role must be a role that supports aria-expanded [Default implied ARIA semantic]

Output: group 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] 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] 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 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 image [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: [Event] prepared [Description]

Output: response to prepare indicating that activeGrammars or activeVoiceModel have been successfully prepared

Voice Extensible Markup Language (VoiceXML) 3.0

Table 8: Recognition: Events from Device


Input: [Event] inputStarted [Description]

Output: notification that the onset of input has been detected

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Event] inputFinished [Description]

Output: notification that the end of input has been detected

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Event] partialResults [Payload] results (M) [Description]

Output: notification of a partial recognition results

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Event] recoResults [Payload] results (M) [Description]

Output: notification of final recognition results

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Event] error [Payload] error status (M) [Description]

Output: an error occurred

Voice Extensible Markup Language (VoiceXML) 3.0


Input: [Event Name] dragstart [Target] Source node [Cancelable?] ✓ Cancelable [Drag data store mode] Read/write mode [Default Action] Initiate the drag-and-drop operation [dropEffect]

Output: "none"


Input: [Event Name] drag [Target] Source node [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [Default Action] Continue the drag-and-drop operation [dropEffect]

Output: "none"


Input: [Event Name] dragenter [Target] Immediate user selection or the body element [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [Default Action] Reject immediate user selection as potential target element [dropEffect]

Output: Based on effectAllowed value


Input: [Event Name] dragleave [Target] Previous target element [Cancelable?] — [Drag data store mode] Protected mode [Default Action] None [dropEffect]

Output: "none"


Input: [Event Name] dragover [Target] Current target element [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [Default Action] Reset the current drag operation to "none" [dropEffect]

Output: Based on effectAllowed value


Input: [Event Name] drop [Target] Current target element [Cancelable?] ✓ Cancelable [Drag data store mode] Read-only mode [Default Action] Varies [dropEffect]

Output: Current drag operation


Input: [Event Name] dragend [Target] Source node [Cancelable?] — [Drag data store mode] Protected mode [Default Action] Varies [dropEffect]

Output: Current drag operation


Input: [Change] Group By clause in FLWOR expression. [Bugzilla] None. [Category] Substantive. [Description]

Output: A new clause was added to the FLWOR expression to allow query writers to cause groups of tuples to be created based on the values of some expression.


Input: [Change] Window clause in FLWOR expression. [Bugzilla] None. [Category] Substantive. [Description]

Output: A new clause was added to the FLWOR expression to allow query writers to create sliding and tumbling windows of tuples based on a number of criteria.


Input: [Change] Simplification of FLWOR expression. [Bugzilla] None. [Category] Substantive. [Description]

Output: The syntax of the FLWOR expression was considerably relaxed, permitting most clauses (other than the return clause) to be used at almost any position (only a few clauses are allowed to be the first clause) within a FLWOR expression.


Input: [Change] Outer for supported in FLWOR expressions. [Bugzilla] None. [Category] Substantive. [Description]

Output: The syntax of the for clause in FLWOR expressions was extended to allow the use of "outer for".


Input: [Change] Count clause in FLWOR expression. [Bugzilla] None. [Category] Substantive. [Description]

Output: A new clause was added to the FLWOR expression to allow query writers to capture the total number of items that are returned by a (portion of a) FLWOR expression.


Input: [Change] Declaration of decimal number formats. [Bugzilla] None. [Category] Substantive. [Description]

Output: A new option was added to the query prologue, allowing query authors to specify a named (or an unnamed default) format for decimal numbers. This allows the specification of such items as the decimal separator, the minus sign, the percent and per mille signs, and even the class of Unicode digits.


Input: [Change] Query version and encoding declaration. [Bugzilla] None. [Category] Substantive. [Description]

Output: Allows specification of either or both of the version of XQuery to which a query adheres and the encoding of the query (e.g., UTF8, ISO8859-1).


Input: [Change] Enhanced validation expression. [Bugzilla] [XQuery 1.1] Requirement: validation by type [Category] Substantive. [Description]

Output: Permits query authors to validate an expression against a specified XML Schema type.


Input: [Change] Nondeterministic external functions. [Bugzilla] None. [Category] Substantive. [Description]

Output: Functions declared to be external functions can also be specified to be deterministic or nondeterministic.


Input: [Change] Syntax used to provide default value for external variables. [Bugzilla] None. [Category] Minor. [Description]

Output: The declaration of external variables now uses ":=" to indicate the default value given to such variables, instead of the keyword "default".


Input: [Change] Try/catch for error handling. [Bugzilla] None. [Category] Substantive. [Description]

Output: A try/catch facility is provided that allows query authors to control how errors are handled when raised by evaluation of queries.


Input: [Change] Context item declaration. [Bugzilla] None. [Category] Substantive. [Description]

Output: It is now possible to declare both the type of and the default initial value of the context item of a query, and to specify whether its value may be provided by the external environment.


Input: [Change] Computed namespace constructor. [Bugzilla] None. [Category] Substantive. [Description]

Output: Added new complex type and element to XQueryX schema, and new template to XQueryX stylesheet, in support of computed namespace constructors in XQuery 1.1.


Input: [Change] Generate proper syntax for variable names in positional variable bindings. [Bugzilla] [XQX30] template for positionalVariableBinding [Category] Substantive. [Description]

Output: Modified XQueryX stylesheet template to correctly generate a "$" preceding the variable name.


Input: [Change] Allow positional variable bindings to be optional in window variables. [Bugzilla] [XQX30] positionalVariableBinding should be optional in windowVars [Category] Substantive. [Description]

Output: Modified XQueryX schema to add minOccurs="0" on element positionalVariableBinding in windowVars complex type definition.


Input: [Change] XQueryX syntax must allow wildcards in the try/catch error list. [Bugzilla] [XQX30] cannot represent a catchErrorList wildcard in XQueryX [Category] Substantive. [Description]

Output: In XQueryX schema, modified catchErrorList complex type definition to allow a choice between a nameText (essentially a QName) and a Wildcard. In XQueryX stylesheet, modified catchErrorList template to support Wildcard as well as nameText.


Input: [Change] Private functions. [Bugzilla] None. [Category] Substantive. [Description]

Output: In XQueryX schema, added new attribute "private" in functionDecl complex type. In XQUeryX stylesheet, template for functionDecl, added support for @private (generate "private" for private functions and "public" for others)


Input: [Change] Replace "outer for" with "allowing empty". [Bugzilla] None. [Category] Substantive. [Description]

Output: In XQueryX schema, forClause complex type, delete attribute "outer"; in forClauseItem complex type, add new element allowingEmpty. In XQueryX stylesheet template for forClause, remove generation of "outer"; in template for forClauseItem, generate "allowing empty".


Input: [Change] Higher-order functions. [Bugzilla] None. [Category] Substantive. [Description]

Output: Made changes to XQueryX schema and stylesheet corresponding to new higher-order function syntax in XQuery 1.1.


Input: [Change] New "switch" expression ("value switch", analogous to typeswitch). [Bugzilla] None. [Category] Substantive. [Description]

Output: Made changes to XQueryX schema and stylesheet corresponding to new switch syntax in XQuery 3.0.


Input: [Change] Support for partial function application. [Bugzilla] None. [Category] Substantive. [Description]

Output: Made changes to XQueryX schema and stylesheet to support the partial function application capability of XQuery 3.0.


Input: [Change] XML Schema and XSLT Stylesheet [Bugzilla] lack of syntactic symmetry between the control flow expressions [Category] Substantive. [Description]

Output: Eliminated the possibility of defining three "error variables" as part of the catch clause; those variables (and others) are now implicitly defined, and may be used without explicit definition. At the same time, fixed a bug in the schema and stylesheet that recognized and produced invalid syntax for the validation expression.


Input: [Property] void:triples [Purpose]

Output: The total number of triples contained in the dataset.

Describing Linked Datasets with the VoID Vocabulary

Properties in VoID for expressing dataset statistics


Input: [Property] void:entities [Purpose]

Output: The total number of entities that are described in the dataset. To be an entity in a dataset, a resource must have a URI, and the URI must match the dataset's void:uriRegexPattern, if any. Authors of VoID files may impose arbitrary additional requirements, for example, they may consider any foaf:Document resources as not being entities.

Describing Linked Datasets with the VoID Vocabulary


Input: [Property] void:classes [Purpose]

Output: The total number of distinct classes in the dataset. In other words, the number of distinct class URIs occuring as objects of rdf:type triples in the dataset.

Describing Linked Datasets with the VoID Vocabulary


Input: [Property] void:properties [Purpose]

Output: The total number of distinct properties in the dataset. In other words, the number of distinct property URIs that occur in the predicate position of triples in the dataset.

Describing Linked Datasets with the VoID Vocabulary


Input: [Property] void:distinctSubjects [Purpose]

Output: The total number of distinct subjects in the dataset. In other words, the number of distinct URIs or blank nodes that occur in the subject position of triples in the dataset.

Describing Linked Datasets with the VoID Vocabulary


Input: [Property] void:distinctObjects [Purpose]

Output: The total number of distinct objects in the dataset. In other words, the number of distinct URIs, blank nodes, or literals that occur in the object position of triples in the dataset.

Describing Linked Datasets with the VoID Vocabulary


Input: [Property] void:documents [Purpose]

Output: If the dataset is published as a set of individual documents, such as RDF/XML documents or RDFa-annotated web pages, then this property indicates the total number of such documents. Non-RDF documents, such as web pages in HTML or images, are usually not included in this count. This property is intended for datasets where the total number of triples or entities is hard to determine. void:triples or void:entities should be preferred where practical.

Describing Linked Datasets with the VoID Vocabulary


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

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

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


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

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

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


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

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

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


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

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

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


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

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

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


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

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

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


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

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

Voice Extensible Markup Language (VoiceXML) 3.0

Table 1: Data Model API


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

Output: DISTINCT


Input: [Patterns] Property path expression [Query Forms] CONSTRUCT [Other] SERVICE [Modifiers]

Output: REDUCED


Input: [Patterns] Property path patterns [Query Forms] DESCRIBE [Modifiers]

Output: Projection


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

Output: ORDER BY


Input: [Patterns] OPTIONAL [Modifiers]

Output: LIMIT


Input: [Patterns] UNION [Modifiers]

Output: OFFSET


Input: [Patterns] GRAPH [Modifiers]

Output: Select expressions


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

Output: Citation Promotion

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] Proposal for new Collection Type and part properties for CreativeWork. [Vocab] Collection subtype of CreativeWork hasPart & isPartOf properties for CreativeWork [Topic]

Output: Collection

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


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

Output: Accessibility

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Accepted [Summary] Add one property 'department' to Organization, to allow local businesses to describe their depts (e.g. opening hours) in detail. Final discussion on whether to call it subOrganizationOf instead. [Vocab] department property (range and domain both Organization) [Comments] Proposal very greatly simplified after WebSchemas discussion. [Topic]

Output: Add Organization department property

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] Add one type, 'QuotationSchema', a kind of CreativeWork, alongside some supporting properties. [Vocab] Quotation, spokenByCharacter, incorrectlyAttributedTo, aboutEvent, fromEvent, addressee. [Comments] Several other requirements are addressed by re-use of existing properties. Debate about whether incorrectlyAttributedTo is worthwhile. Some details to finalise. [Topic]

Output: Add Quotation type

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


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

Output: sameAs

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


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

Output: Actions in Schema.org

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


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

Output: Orders in Schema.org

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


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

Output: Reservations in Schema.org

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


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

Output: EmailMessage type

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Status] Proposal [Summary] Describing public civic services [Vocab] A proposal extending schema.org to cover various kinds of civic services. [Comments] GovernmentService, several kinds of CivicPermit, CivicAudience, BusinessAudience; various properties [Topic]

Output: Civic Services

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


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

Output: Workers Union type

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


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

Output: TV and Radio proposal

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


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

Output: Sports

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


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

Output: Comics and Serials

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


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

Output: Event schema update

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


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

Output: Historical Data proposal

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


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

Output: Biological Databases

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


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

Output: Breadcrumbs

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


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

Output: Discussion

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


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

Output: Innovation

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [Topic]

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


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

Output: Proposal name

Difference between revisions of "WebSchemas/SchemaDotOrgProposals" - W3C Wiki


Input: [unit] em [relative to]

Output: the font size of the element (or, to the parent element's font size if set on the 'font-size' property)


Input: [unit] ex [relative to]

Output: the x-height of the element's font


Input: [unit] px [relative to]

Output: viewing device


Input: [unit] gd [relative to]

Output: the grid defined by 'layout-grid' described in the CSS3 Text module [CSS3TEXT]


Input: [unit] rem [relative to]

Output: the font size of the root element


Input: [unit] vw [relative to]

Output: the viewport's width


Input: [unit] vh [relative to]

Output: the viewport's height


Input: [unit] vm [relative to]

Output: the viewport's height or width, whichever is smaller of the two


Input: [Level] 1.

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

QA Framework: Process & Operational Guidelines


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

Output: Same as above

QA Framework: Process & Operational Guidelines


Input: [Level] 3. [extent of test materials] Same as above.

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

QA Framework: Process & Operational Guidelines


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 thourough, before the specification becomes Recommendation.

Output: Same as above.

QA Framework: Process & Operational Guidelines


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

Output: Same as above

QA Framework: Process & Operational Guidelines


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

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

QA Framework: Process & Operational Guidelines


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.

Output: Same as above

QA Framework: Process & Operational Guidelines


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: [Event Name] dragstart [Cancelable?] ✓ Cancelable [Drag data store mode] Read/write mode [dropEffect] "none" [Default Action] Initiate the drag-and-drop operation [Target]

Output: Source node


Input: [Event Name] drag [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [dropEffect] "none" [Default Action] Continue the drag-and-drop operation [Target]

Output: Source node


Input: [Event Name] dragenter [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [dropEffect] Based on effectAllowed value [Default Action] Reject immediate user selection as potential target element [Target]

Output: Immediate user selection or the body element


Input: [Event Name] dragleave [Cancelable?] — [Drag data store mode] Protected mode [dropEffect] "none" [Default Action] None [Target]

Output: Previous target element


Input: [Event Name] dragover [Cancelable?] ✓ Cancelable [Drag data store mode] Protected mode [dropEffect] Based on effectAllowed value [Default Action] Reset the current drag operation to "none" [Target]

Output: Current target element


Input: [Event Name] drop [Cancelable?] ✓ Cancelable [Drag data store mode] Read-only mode [dropEffect] Current drag operation [Default Action] Varies [Target]

Output: Current target element


Input: [Event Name] dragend [Cancelable?] — [Drag data store mode] Protected mode [dropEffect] Current drag operation [Default Action] Varies [Target]

Output: Source node


Input: [Identifier] acceptTracking [Comment] The collected information may be tracked by the Assigner, or may link to a Party with the role function “trackingParty”. [Semantics]

Output: The Assigner requires that the Assignee(s) accepts that the use of the Asset may be tracked

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

Table 2.2.2: Terms for entity Action used with Duty


Input: [Identifier] attribute [Comment] May link to an Asset with the attribution information. May link to a Party with the role function “attributedParty”. [Semantics]

Output: The Assigner requires that the Assignee(s) attributes the Asset to the Assigner or an attributed Party.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] compensate [Comment] The compensation may use different types of things with a value: – the thing is expressed by the value (term) of the Constraint name – the value is expressed by operator, rightOperand, dataType and unit [Semantics]

Output: The Assigner requires that the Assignee(s) compensates the Assigner (or other specified compensation Party) by some amount of value, if defined, for use of the Asset.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] delete [Comment] Use a constraint to define under which conditions the Asset should be deleted. [Semantics]

Output: The Assigner requires that the Assignee(s) permanently removes all copies of the Asset.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] ensureExclusivity [Semantics]

Output: The Assignee requires that the Assigner(s) ensure(s) that the permission on the Asset is exclusive to the Assignee.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] include [Comment] For example; Bio picture must be included in the attribution. Use of the Asset relation attribute is required [Semantics]

Output: The Assigner requires that the Assignee(s) include(s) other related assets in the Asset.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] inform [Comment] May link to a Party with the role function “informedParty”. [Semantics]

Output: The Assigner requires that the Assignee(s) inform(s) the Assigner or an informed Party that an action has been performed on or in relation to the Asset.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] nextPolicy [Semantics]

Output: The Assigner requires that the Assignee(s) grants the specified Policy to a third party for their use of the Asset.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] obtainConsent [Comment] Used as a Duty to ensure that the Assigner or a Party is authorized to approve such actions on a case-by-case basis. May link to a Party with the role function “consentingParty”. [Semantics]

Output: The Assigner requires that the Assignee(s) obtains explicit consent from the Assigner or a consenting Party to perform the requested action in relation to the Asset.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] reviewPolicy [Comment] Used when human intervention is required to review the Policy. May link to an Asset which represents the full Policy information. [Semantics]

Output: The Assigner requires that the Assignee(s) has(ve) a person review the Policy applicable to the Asset.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] uninstall [Comment] The Asset is no longer accessible to the Assignee(s). [Semantics]

Output: The Assigner requires that the Assignee(s) unload(s) and delete(s) the computer program Asset from a storage device and disable(s) its readiness for operation.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] watermark [Comment] It is recommended to embed a link to the watermark. [Semantics]

Output: The Assigner requires that the Assignee(s) apply(ies) a watermark as provided by the Assigner to the Asset.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Definition] Character data [Attribute Type]

Output: CDATA

XHTML™ Modularization 1.1 - Second Edition


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

Output: ID

XHTML™ Modularization 1.1 - Second Edition


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

Output: IDREF

XHTML™ Modularization 1.1 - Second Edition


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

Output: IDREFS

XHTML™ Modularization 1.1 - Second Edition


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

Output: NAME

XHTML™ Modularization 1.1 - Second Edition


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

Output: NMTOKEN

XHTML™ Modularization 1.1 - Second Edition


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

Output: NMTOKENS

XHTML™ Modularization 1.1 - Second Edition


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: [Event Name] dragstart [Target] Source node [Cancelable?] ✓ Cancelable [dropEffect] "none" [Default Action] Initiate the drag-and-drop operation [Drag data store mode]

Output: Read/write mode


Input: [Event Name] drag [Target] Source node [Cancelable?] ✓ Cancelable [dropEffect] "none" [Default Action] Continue the drag-and-drop operation [Drag data store mode]

Output: Protected mode


Input: [Event Name] dragenter [Target] Immediate user selection or the body element [Cancelable?] ✓ Cancelable [dropEffect] Based on effectAllowed value [Default Action] Reject immediate user selection as potential target element [Drag data store mode]

Output: Protected mode


Input: [Event Name] dragleave [Target] Previous target element [Cancelable?] — [dropEffect] "none" [Default Action] None [Drag data store mode]

Output: Protected mode


Input: [Event Name] dragover [Target] Current target element [Cancelable?] ✓ Cancelable [dropEffect] Based on effectAllowed value [Default Action] Reset the current drag operation to "none" [Drag data store mode]

Output: Protected mode


Input: [Event Name] drop [Target] Current target element [Cancelable?] ✓ Cancelable [dropEffect] Current drag operation [Default Action] Varies [Drag data store mode]

Output: Read-only mode


Input: [Event Name] dragend [Target] Source node [Cancelable?] — [dropEffect] Current drag operation [Default Action] Varies [Drag data store mode]

Output: Protected mode


Input: [function] For example, when defining an applet you could reference a space-separated list of jar files. [attribute]

Output: archive


Input: [function] This is similar to meta data, in that this can be used by the object handler as a hint to the physical size of the object data that is to be processed. [attribute]

Output: content-length


Input: [function] This URI points to the object data to be processed. This can be an absolute URI (http://www.example.com/datafiles/myinstance.mpg), or a relative URI (myinstance.mpg). If you use a relative URI, then you will need to use the xml:base attribute to define the base location of the object data. This attribute should only refer to the data to be processed. [attribute]

Output: data


Input: [function] This is used to delay the processing of the object data until such time that it is referred to by another element that requires the object data to be processed. In other words, the object data should be downloaded but should not be processed. For example, if an a element is coded to refer to the object element and the a element is activated, then the object data would be processed. [attribute]

Output: declare


Input: [function] The author can provide a text string that should be displayed while the object data is being downloaded and processed. [attribute]

Output: standby


Input: [function] Defining the mime type of the object data will assist the object handler in determining whether the object data can be processed by the user agent or if an external application needs to be launched to process the object data. [attribute]

Output: type


Input: [function] Use this attribute to define the base location of the object data. For example: http://www.example.com/datafiles/. This attribute should not be used for any other purpose. [attribute]

Output: xml:base


Input: [attribute] archive [function]

Output: For example, when defining an applet you could reference a space-separated list of jar files.


Input: [attribute] content-length [function]

Output: This is similar to meta data, in that this can be used by the object handler as a hint to the physical size of the object data that is to be processed.


Input: [attribute] data [function]

Output: This URI points to the object data to be processed. This can be an absolute URI (http://www.example.com/datafiles/myinstance.mpg), or a relative URI (myinstance.mpg). If you use a relative URI, then you will need to use the xml:base attribute to define the base location of the object data. This attribute should only refer to the data to be processed.


Input: [attribute] declare [function]

Output: This is used to delay the processing of the object data until such time that it is referred to by another element that requires the object data to be processed. In other words, the object data should be downloaded but should not be processed. For example, if an a element is coded to refer to the object element and the a element is activated, then the object data would be processed.


Input: [attribute] standby [function]

Output: The author can provide a text string that should be displayed while the object data is being downloaded and processed.


Input: [attribute] type [function]

Output: Defining the mime type of the object data will assist the object handler in determining whether the object data can be processed by the user agent or if an external application needs to be launched to process the object data.


Input: [attribute] xml:base [function]

Output: Use this attribute to define the base location of the object data. For example: http://www.example.com/datafiles/. This attribute should not be used for any other purpose.


Input: [Box] top content edge [Area]

Output: top edge of the content-rectangle


Input: [Box] padding edge [Area]

Output: padding-rectangle


Input: [Box] content area [Area]

Output: interior of the content-rectangle


Input: [Box] padding area [Area]

Output: region between the content-rectangle and the padding-rectangle


Input: [Box] border area [Area]

Output: region between the padding-rectangle and the border-rectangle


Input: [Box] background [Area]

Output: background


Input: [Box] containing block [Area]

Output: closest ancestor block-area that is not a line-area (see below for additional information when the "containing block" is used as a reference for percentage calculations)


Input: [Box] caption [Area]

Output: area generated by fo:table-caption


Input: [Box] inline box [Area]

Output: inline-area


Input: [Box] line box [Area]

Output: line-area


Input: [Box] block box [Area]

Output: block-area which is not a line-area


Input: [Box] page box [Area]

Output: page-area


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


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


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

Output: Based on effectAllowed value


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


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

Output: Based on effectAllowed value


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

Output: Current drag operation


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

Output: Current drag operation


Input: [Attribute Type] CDATA [Definition]

Output: Character data


Input: [Attribute Type] ID [Definition]

Output: A document-unique identifier


Input: [Attribute Type] IDREF [Definition]

Output: A reference to a document-unique identifier


Input: [Attribute Type] IDREFS [Definition]

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


Input: [Attribute Type] NAME [Definition]

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


Input: [Attribute Type] NMTOKEN [Definition]

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


Input: [Attribute Type] NMTOKENS [Definition]

Output: One or more white space separated NMTOKEN values


Input: [Attribute Type] PCDATA [Definition]

Output: Processed character data


Input: [Name] type [Description]

Output: Returns the name of the event.


Input: [Name] target [Description]

Output: Indicates the event target.


Input: [Name] currentTarget [Description]

Output: Indicates the EventTarget whose EventListeners are currently being processed.


Input: [Name] eventPhase [Description]

Output: Indicates which phase of event flow is currently being accomplished.


Input: [Name] bubbles [Description]

Output: Indicates whether or not an event is a bubbling event.


Input: [Name] cancelable [Description]

Output: Indicates whether or not an event can have its default action prevented.


Input: [Name] defaultPrevented [Description]

Output: Indicates whether Event.preventDefault() has been called for this event.


Input: [Name] isTrusted [Description]

Output: Indicates whether this event was generated by the user agent (trusted) or by script (untrusted).


Input: [Name] timeStamp [Description]

Output: Returns the time that the event was created.


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

Output: HTML to Text converter


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

Output: Link Checker


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

Output: Link Checker


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

Output: HTML Validator


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

Output: W3C Spellchecker


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

Output: CSS Validator


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

Output: CVS Log


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

Output: Headers


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

Output: the pubrules checker


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

Output: the pubrules checker


Input: [Description] The extension element matches the schema. This should be linked to a testable assertion in the spec. [Title]

Output: Valid extension Element


Input: [Description] Two extension elements match the schema. This should be linked to a testable assertion in the spec. [Title]

Output: Two Valid extension Elements


Input: [Description] The extension element does not have an id attribute but it still matches the schema. This should be linked to a testable assertion in the spec. [Title]

Output: Valid extension Element Without id Attribute


Input: [Description] The extension element does not have a name child element but it still matches the schema. This should be linked to a testable assertion in the spec. [Title]

Output: Valid extension Element Without name Element


Input: [Description] The extension element contains one name element without a lang attribute and another with a lang attribute. This should be linked to a testable assertion in the spec. [Title]

Output: Valid extension Element With Two name Elements 1


Input: [Description] The extension element contains two name elements with lang attributes. This should be linked to a testable assertion in the spec. [Title]

Output: Valid extension Element With Two name Elements 2


Input: [Description] The extension element contains two item child elements. This should be linked to a testable assertion in the spec. [Title]

Output: Valid extension Element With Two item Elements


Input: [Description] The extension element does not contain an item child element. This should be linked to a testable assertion in the spec. [Title]

Output: No item Element in extension Element


Input: [Description] The extension element contains an unknown attribute. This should be linked to a testable assertion in the spec. [Title]

Output: Unknown Attribute in extension Element


Input: [Description] The extension element contains an unknown child element. This should be linked to a testable assertion in the spec. [Title]

Output: Unknown Child Element in extension Element


Input: [Description] The extension element contains content. This should be linked to a testable assertion in the spec. [Title]

Output: Content in extension Element


Input: [Description] The item element in the extension element matches the schema. This should be linked to a testable assertion in the spec. [Title]

Output: Valid item Element in extension Element


Input: [Description] The item element in the extension element contains a variety of languages. This should be linked to a testable assertion in the spec. [Title]

Output: Valid item Element With Multiple Languages in extension Element


Input: [Description] The item element in the extension element does not contain an id attribute but it still matches the schema. This should be linked to a testable assertion in the spec. [Title]

Output: Valid item Element Without id Attribute in extension Element


Input: [Description] The item element in the extension element contains one name child element with no lang attribute and one with a lang attribute. This should be linked to a testable assertion in the spec. [Title]

Output: Valid item Element With Two name Elements in extension Element 1


Input: [Description] The item element in the extension element contains two name child elements with lang attributes. This should be linked to a testable assertion in the spec. [Title]

Output: Valid item Element With Two name Elements in extension Element 2


Input: [Description] The item element in the extension element contains one value child element with no lang attribute and one with a lang attribute. This should be linked to a testable assertion in the spec. [Title]

Output: Valid item Element With Two value Elements in extension Element 1


Input: [Description] The item element in the extension element contains two value child elements with lang attributes. This should be linked to a testable assertion in the spec. [Title]

Output: Valid item Element With Two value Elements in extension Element 2


Input: [Description] The item element in the extension element does not contain a name child element. This should be linked to a testable assertion in the spec. [Title]

Output: No name Element in item Element in extension Element


Input: [Description] The item element in the extension element does not contain a value child element. This should be linked to a testable assertion in the spec. [Title]

Output: No value Element in item Element in extension Element


Input: [Description] The item element in the extension element contains an unknown attribute. This should be linked to a testable assertion in the spec. [Title]

Output: Unknown Attribute in item Element in extension Element


Input: [Description] The item element in the extension element contains an unknown child element. This should be linked to a testable assertion in the spec. [Title]

Output: Unknown Child Element in item Element in extension Element


Input: [Description] The item element in the extension element contains content. This should be linked to a testable assertion in the spec. [Title]

Output: Content in item Element in extension Element


Input: [Description] The name element in the item element in the extension element matches the schema. This should be linked to a testable assertion in the spec. [Title]

Output: Valid name Element in item Element in extension Element


Input: [Description] The name element in the item element in the extension element contains a lang attribute and it matches the schema. This should be linked to a testable assertion in the spec. [Title]

Output: Valid name Element With lang Attribute in item Element in extension Element


Input: [Description] The name element in the item element in the extension element contains an unkown attribute. This should be linked to a testable assertion in the spec. [Title]

Output: Unkown Attribute in name Element in item Element in extension Element


Input: [Description] The name element in the item element in the extension element contains a child element. This should be linked to a testable assertion in the spec. [Title]

Output: Child Element in name Element in item Element in extension Element


Input: [Description] The value element in the item element in the extension element matches the schema. This should be linked to a testable assertion in the spec. [Title]

Output: Valid value Element in item Element in extension Element


Input: [Description] The value element in the item element in the extension element contains a lang attribute and it matches the schema. This should be linked to a testable assertion in the spec. [Title]

Output: Valid value Element With lang Attribute in item Element in extension Element


Input: [Description] The value element in the item element in the extension element contains an unkown attribute. This should be linked to a testable assertion in the spec. [Title]

Output: Unkown Attribute in value Element in item Element in extension Element


Input: [Description] The value element in the item element in the extension element contains a child element. This should be linked to a testable assertion in the spec. [Title]

Output: Child Element in value Element in item Element in extension Element


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

Output: Notes

Internationalization Tag Set (ITS) Version 2.0


Input: [0] mistranslation [1] The content of the target mistranslates the content of the source. [2] The English source reads "An ape succeeded in grasping a banana lying outside its cage with the help of a stick" but the Italian translation reads "l'ape riuscÃ¬ a prendere la banana posta tuori dall sua gabbia aiutandosi con un bastone" ("A bee succeeded...") [3] T [4]

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

Internationalization Tag Set (ITS) Version 2.0


Input: [0] omission [1] Necessary text has been omitted from the localization or source. [2] One or more segments found in the source that should have been translated are missing in the target. [3] S or T [4]

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

Internationalization Tag Set (ITS) Version 2.0


Input: [0] untranslated [1] Content that should have been translated was left untranslated. [2] The source segment reads "The Professor said to Smith that he would hear from his lawyer" but the Hungarian localization reads "A professzor azt modta Smithnek, hogy he would hear from his lawyer." [3] T [4]

Output: omission takes precedence over untranslated . Omissions are distinct in that they address cases where text is not present, while untranslated addresses cases where text has been carried from the source untranslated.

Internationalization Tag Set (ITS) Version 2.0


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

Output: Legally inappropriate material should be classified as legal .

Internationalization Tag Set (ITS) Version 2.0


Input: [0] numbers [1] Numbers are inconsistent between source and target. [2] A source text states that an object is 120 cm long, but the target text says it is 129 cm. long. [3] S or T [4]

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

Internationalization Tag Set (ITS) Version 2.0


Input: [0] internationalization [1] There is an issue related to the internationalization of content. [2] A line of programming code has embedded language-specific strings. A user interface element leaves no room for text expansion. A form allows only for U.S.-style postal addresses and expects five digit U.S. ZIP codes. [3] S or T [4]

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

Internationalization Tag Set (ITS) Version 2.0


Input: [0] length [1] There is a significant difference in source and target length. [2] The translation of a segment is five times as long as the source. [3] T or S [4]

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

Internationalization Tag Set (ITS) Version 2.0


Input: [0] uncategorized [1] The issue has not been categorized. [2] A new version of a tool returns information on an issue that has not been previously checked and that is not yet classified. [3] S or T [4]

Output: This category has two uses: A tool can use it to pass through quality data from another tool in cases where the issues from the other tool are not classified (for example, a localization quality assurance tool interfaces with a third-party grammar checker). A tool's issues are not yet assigned to categories, and, until an updated assignment is made, they may be listed as uncategorized . In this case it is recommended that issues be assigned to appropriate categories as soon as possible since uncategorized does not foster interoperability.

Internationalization Tag Set (ITS) Version 2.0


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

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

Internationalization Tag Set (ITS) Version 2.0


Input: [Expected Values] alternativeText Visual [Description] alternative text is provided for visual content (e.g., the HTML alt attribute). [Augmented Access Mode]

Output: Textual

Difference between revisions of "WebSchemas/Accessibility" - W3C Wiki


Input: [Expected Values] longDescription Visual [Description] descriptions are provided for image-based visual content and/or complex structures such as tables, mathematics, diagrams or charts. [Augmented Access Mode]

Output: Textual

Difference between revisions of "WebSchemas/Accessibility" - W3C Wiki


Input: [Expected Values] ChemML laTex MathML Visual [Description] The use of one of these specific ASCII/XML encodings for mathematics or chemistry. These can have extensions specified, but are rarely needed. [Augmented Access Mode]

Output: Textual

Difference between revisions of "WebSchemas/Accessibility" - W3C Wiki


Input: [Expected Values] transcript Auditory [Description] The addition of a separate transcript to convey the meaning of the audio. [Augmented Access Mode]

Output: Textual

Difference between revisions of "WebSchemas/Accessibility" - W3C Wiki


Input: [Expected Values] captions Auditory [Description] The addition of synchronized text (closed captions) to convey the meaning of the audio. Note that while many captions may be implemented as textual in the transport, users think of them as being a visual appearance. [Augmented Access Mode]

Output: Visual

Difference between revisions of "WebSchemas/Accessibility" - W3C Wiki


Input: [Expected Values] signLanguage Auditory [Description] The presentation of audio in sign language in the visual presentation. The most likely extension is /sgn-en-us or other ISO 639 sign language code. [Augmented Access Mode]

Output: Visual

Difference between revisions of "WebSchemas/Accessibility" - W3C Wiki


Input: [Expected Values] audioDescription Visual [Description] Audio descriptions are available (e.g., via the HTML5 track element). Common extensions are for the various "onImage" refinements noted above. [Augmented Access Mode]

Output: Auditory

Difference between revisions of "WebSchemas/Accessibility" - W3C Wiki


Input: [Expected Values] braille Visual or Textual [Description] braille content or alternative is available (e.g., eBraille or print braille) This can have extensions for the different types of braille, /ASCII, /music, /math, /chem or /nemeth) (also consider /contracted and /gradeII or other nomenclature... pretty open) [Augmented Access Mode]

Output: Tactile

Difference between revisions of "WebSchemas/Accessibility" - W3C Wiki


Input: [Expected Values] tactileGraphic Visual [Description] tactile graphics have been provided, as described in the BANA Guidelines and Standards for Tactile Graphics. [Augmented Access Mode]

Output: Tactile

Difference between revisions of "WebSchemas/Accessibility" - W3C Wiki


Input: [Expected Values] tactileObject Visual [Description] tactile 3D objects have been defined and a 3D object or instructions to build one are available. [Augmented Access Mode]

Output: Tactile

Difference between revisions of "WebSchemas/Accessibility" - W3C Wiki


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

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


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

Output: List of bad links in the page


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

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


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

Output: List of HTML markup errors.


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

Output: List of spelling errors.


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

Output: List of style CSS errors.


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

Output: Log of changes to the document


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

Output: HTTP headers sent by the server


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

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


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

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


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

Output: The name of the event.

XPath Expressions Module - W3C XForms Group Wiki (Public)


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

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

XPath Expressions Module - W3C XForms Group Wiki (Public)


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

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

XPath Expressions Module - W3C XForms Group Wiki (Public)


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

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

XPath Expressions Module - W3C XForms Group Wiki (Public)


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

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

XPath Expressions Module - W3C XForms Group Wiki (Public)


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

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

XPath Expressions Module - W3C XForms Group Wiki (Public)


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

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

XPath Expressions Module - W3C XForms Group Wiki (Public)


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0


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

Output: Yes

Internationalization Tag Set (ITS) Version 2.0