Input: [Rule] Rule 1: Each modality component must implement all of the MMI life cycle events events. [Component Information]

Output: See Table 2 for the details of the implementation of the life cycle life-cycle events.

Table 1: Component behavior of Face Identification with respect to modality component rules.


Input: [Rule] Rule 2: Identify other functions of the modality component that are relevant to the interaction manager. [Component Information]

Output: All the functions of the component are covered in the life cycle life-cycle events, no other functions are needed.


Input: [Rule] Rule 3: If the component uses media, specify the media format. [Component Information]

Output: The component uses the jpeg format for images to be identified and for its image database.


Input: [Rule] Rule 4: Specify protocols supported by the component for transmitting media (e.g. SIP). [Component Information]

Output: The component uses HTTP for transmitting media.


Input: [Rule] Rule 5: Specify supported human languages languages. [Component Information]

Output: This component does not support any human languages.


Input: [Rule] Rule 6: Specify supporting languages required by the component component. [Component Information]

Output: This component does not require any markup languages.


Input: [Rule] Rule 7: Modality components sending data to the interaction manager must use the EMMA format. [Component Information]

Output: This component uses EMMA.


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

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

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] 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: [Description] Alignment of event codes and content items [Default Value] bit-packed [EXI Option]

Output: alignment

EXI Options in Options Field


Input: [Description] EXI compression is used to achieve better compactness [Default Value] false [EXI Option]

Output: compression

EXI Options in Options Field


Input: [Description] Strict interpretation of schemas is used to achieve better compactness [Default Value] false [EXI Option]

Output: strict

EXI Options in Options Field


Input: [Description] Body is encoded as an EXI fragment instead of an EXI document [Default Value] false [EXI Option]

Output: fragment

EXI Options in Options Field


Input: [Description] Specifies whether comments, pis, etc. are preserved [Default Value] all false [EXI Option]

Output: preserve

EXI Options in Options Field


Input: [Description] Enables self-contained elements [Default Value] false [EXI Option]

Output: selfContained

EXI Options in Options Field


Input: [Description] Identify the schema information, if any, used to encode the body [Default Value] none [EXI Option]

Output: schemaID

EXI Options in Options Field


Input: [Description] Identify datatype representations used to encode values in EXI body [Default Value] none [EXI Option]

Output: datatypeRepresentationMap

EXI Options in Options Field


Input: [Description] Specifies the block size used for EXI compression [Default Value] 1,000,000 [EXI Option]

Output: blockSize

EXI Options in Options Field


Input: [Description] Specifies the maximum string length of value content items to be considered for addition to the string table. [Default Value] unbounded [EXI Option]

Output: valueMaxLength

EXI Options in Options Field


Input: [Description] Specifies the total capacity of value partitions in a string table [Default Value] unbounded [EXI Option]

Output: valuePartitionCapacity

EXI Options in Options Field


Input: [Description] User defined options may be added [Default Value] none [EXI Option]

Output: [user defined]

EXI Options in Options Field


Input: [Attribute Name] conid [Details]

Output: Is an ECMAScript expression which returns an identifier of a connection or conference. The default value of the "conid" attribute is "_event.source", which will be the connection that generated the previous event (typically a connection.CONNECTION_CONNECTED event). A connection will be allocated for the dialog being launched, and this connection will be bridged to the connection or conference specified by "conid". For more information about connections and bridges, refer to Section 10.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] src [Details]

Output: Is an ECMAScript expression which returns a character string identifying the URI of the dialog document that the dialog interpreter should load and begin executing upon startup.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] type [Details]

Output: an ECMAScript expression which returns a character string that specifies the MIME type of the document, and as a result, which dialog interpreter is actually loaded. A MIME type of "application/xml+vxml" associates the start-document with a VoiceXML interpreter instance. A MIME type of "audio/wav" associates the start-document with a dialog manager that merely plays wave files. If omitted, the mime-type attribute defaults to "application/xml+vxml", but the CCXML interpreter is free to guess the correct MIME type, e.g., by examining the filename-extension of the start-doc URI.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] namelist [Details]

Output: a list of zero or more CCXML variable names. These variable names and their associated values will be included in the URI sent to the dialog manager, with the same qualification used in the namelist.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] dialogid [Details]

Output: an ECMAScript left-hand-side expression that will receive the value of the session-name identifying the launched dialog interpreter instance. This session-name can be used by the CCXML script programmer in future invocations of .

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] duplex [Details]

Output: Equal to "half" or "full". This determines the type of bridge between the connection associated with the dialog and the connection or conference specified by the "conid" attribute. For more information about connections and bridges, refer to Section 10.

Voice Browser Call Control: CCXML Version 1.0


Input: [Identifier] acceptTracking [Semantics] The Assigner requires that the Assignee(s) accepts that the use of the Asset may be tracked [Comment]

Output: The collected information may be tracked by the Assigner, or may link to a Party with the role function “trackingParty”.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

Table 2.2.2: Terms for entity Action used with Duty


Input: [Identifier] attribute [Semantics] The Assigner requires that the Assignee(s) attributes the Asset to the Assigner or an attributed Party. [Comment]

Output: May link to an Asset with the attribution information. May link to a Party with the role function “attributedParty”.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] compensate [Semantics] 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. [Comment]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] delete [Semantics] The Assigner requires that the Assignee(s) permanently removes all copies of the Asset. [Comment]

Output: Use a constraint to define under which conditions the Asset should be deleted.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] include [Semantics] The Assigner requires that the Assignee(s) include(s) other related assets in the Asset. [Comment]

Output: For example; Bio picture must be included in the attribution. Use of the Asset relation attribute is required

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] inform [Semantics] 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. [Comment]

Output: May link to a Party with the role function “informedParty”.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] obtainConsent [Semantics] 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. [Comment]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] reviewPolicy [Semantics] The Assigner requires that the Assignee(s) has(ve) a person review the Policy applicable to the Asset. [Comment]

Output: Used when human intervention is required to review the Policy. May link to an Asset which represents the full Policy information.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] uninstall [Semantics] 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. [Comment]

Output: The Asset is no longer accessible to the Assignee(s).

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] watermark [Semantics] The Assigner requires that the Assignee(s) apply(ies) a watermark as provided by the Assigner to the Asset. [Comment]

Output: It is recommended to embed a link to the watermark.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: No conflict

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


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

Output: No conflict; added LDP headers

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


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

Output: No conflict; added LDP headers

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


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

Output: No conflict

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


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

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

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


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

Output: No conflict

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


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

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

Difference between revisions of "Linked Data Platform (LDP) vs SPARQL Graph Store HTTP Protocol (GSP)" - Linked Data Platform


Input: [Semantics] Policy expressions that are formal contracts (or licenses) stipulating all the terms of usage and all the parties involved. [Comment] Must contain at least the Party entity with Assigner role and a Party with Assignee role. The latter being granted the terms of the Agreement from the former. [Identifier]

Output: Agreement

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

Table 2.1: Terms for the entity Type of the Policy Entity


Input: [Semantics] Policy expressions that propose terms of usage from an Asset owner [Comment] Must contain a Party entity with Assigner role. The Offer may contain a Party entity with Assignee role, but does not grant any privileges to that Party. [Identifier]

Output: Offer

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] Policy expressions that stipulate the terms of usage over personal information. [Comment] Must contain at least the Party entity with Assigner role and a Party with Assignee role. Must also contain a Duty on the assignee related to obligations towards managing the assigner’s Asset containing personal information. The Assignee is being granted the terms of the Privacy policy from the Assigner. [Identifier]

Output: Privacy

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] Policy expressions that propose terms of usage to an Asset owner [Comment] Must contain a Party entity with Assignee role. The Request may also contain the Party entity with Assigner role if this is known. No privileges are granted to any Party. [Identifier]

Output: Request

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] Policy expressions that consists of entities from the complete model [Comment] The Set is aimed at scenarios where there is an open criteria for the semantics of the policy expressions and typically refined by other systems/profiles that process the information at a later time. No privileges are granted to any Party. [Identifier]

Output: Set

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] Policy expressions that stipulate the terms of usage and is redeemable by any Party who currently holds the Ticket in their possession [Comment] May contain the Party entity with Assigner role and the Party entity with Assignee role. A Ticket (or Voucher) may be anonymous or personalised, where the holder of that Ticket may remain unknown or has to be identified. The holder, or if known, the Assignee, is being granted the terms of the Ticket from the Assigner (in known). [Identifier]

Output: Ticket

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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: [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] Solid background colour to be used when presenting the image if no better option is available. [Type of information]

Output: Background colour

Portable Network Graphics (PNG) Specification (Second Edition)

Table 4.1 — Types of ancillary information


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

Output: Gamma and chromaticity

Portable Network Graphics (PNG) Specification (Second Edition)


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

Output: ICC profile

Portable Network Graphics (PNG) Specification (Second Edition)


Input: [Description] Frequency estimates of the usage of each entry in the palette by the image. [Type of information]

Output: Image histogram

Portable Network Graphics (PNG) Specification (Second Edition)


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

Output: Physical pixel dimensions

Portable Network Graphics (PNG) Specification (Second Edition)


Input: [Description] The number of bits that are significant in the channel values or the palette. [Type of information]

Output: Significant bits

Portable Network Graphics (PNG) Specification (Second Edition)


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

Output: sRGB colour space

Portable Network Graphics (PNG) Specification (Second Edition)


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

Output: Suggested palette

Portable Network Graphics (PNG) Specification (Second Edition)


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

Output: Textual data

Portable Network Graphics (PNG) Specification (Second Edition)


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

Output: Time

Portable Network Graphics (PNG) Specification (Second Edition)


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

Output: Transparency

Portable Network Graphics (PNG) Specification (Second Edition)


Input: [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: [Notation] {$ rule text $} [Interpretation]

Output: Emit the rule text substituting any occurrence of variables from the binding map. The outer {$ $} can be omitted in cases where there is no ambiguity.


Input: [Notation] for(?elt in ?list) { template } [Interpretation]

Output: ?list is a variable in the pattern which is bound to an RDF List. The for operator iterates over each element of the ?list in turn replacing the binding map for the ?elt variable with the next list entry and processes the enclosed template in the context of that new binding map.


Input: [Notation] for(?elt in ?list, != ?other) { template } [Interpretation]

Output: ?list is a variable in the pattern which is bound to an RDF List. The for operator iterates over each element of the ?list in turn, skipping any element identical to ?other, replacing the binding map for the ?elt variable with the next list entry and processes the enclosed template in the context of that new binding map.


Input: [Notation] $length(?list)$ [Interpretation]

Output: Used within a template this will be replaced by the length the RDFList bound to ?list.


Input: [Notation] $i$ [Interpretation]

Output: Used within a for(?elt in ?list){ template } this will be replaced by the index of the current ?elt.


Input: [Notation] $i+1$ [Interpretation]

Output: Used within a for(?elt in ?list){ template } this will be replaced by the index of the current ?elt, plus 1.


Input: [Details] Is an ECMAScript expression which returns an identifier of a connection or conference. The default value of the "conid" attribute is "_event.source", which will be the connection that generated the previous event (typically a connection.CONNECTION_CONNECTED event). A connection will be allocated for the dialog being launched, and this connection will be bridged to the connection or conference specified by "conid". For more information about connections and bridges, refer to Section 10. [Attribute Name]

Output: conid

Voice Browser Call Control: CCXML Version 1.0


Input: [Details] Is an ECMAScript expression which returns a character string identifying the URI of the dialog document that the dialog interpreter should load and begin executing upon startup. [Attribute Name]

Output: src

Voice Browser Call Control: CCXML Version 1.0


Input: [Details] an ECMAScript expression which returns a character string that specifies the MIME type of the document, and as a result, which dialog interpreter is actually loaded. A MIME type of "application/xml+vxml" associates the start-document with a VoiceXML interpreter instance. A MIME type of "audio/wav" associates the start-document with a dialog manager that merely plays wave files. If omitted, the mime-type attribute defaults to "application/xml+vxml", but the CCXML interpreter is free to guess the correct MIME type, e.g., by examining the filename-extension of the start-doc URI. [Attribute Name]

Output: type

Voice Browser Call Control: CCXML Version 1.0


Input: [Details] a list of zero or more CCXML variable names. These variable names and their associated values will be included in the URI sent to the dialog manager, with the same qualification used in the namelist. [Attribute Name]

Output: namelist

Voice Browser Call Control: CCXML Version 1.0


Input: [Details] an ECMAScript left-hand-side expression that will receive the value of the session-name identifying the launched dialog interpreter instance. This session-name can be used by the CCXML script programmer in future invocations of . [Attribute Name]

Output: dialogid

Voice Browser Call Control: CCXML Version 1.0


Input: [Details] Equal to "half" or "full". This determines the type of bridge between the connection associated with the dialog and the connection or conference specified by the "conid" attribute. For more information about connections and bridges, refer to Section 10. [Attribute Name]

Output: duplex

Voice Browser Call Control: CCXML Version 1.0


Input: [Semantics] The Assigner requires that the Assignee(s) accepts that the use of the Asset may be tracked [Comment] The collected information may be tracked by the Assigner, or may link to a Party with the role function “trackingParty”. [Identifier]

Output: acceptTracking

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Assigner requires that the Assignee(s) attributes the Asset to the Assigner or an attributed Party. [Comment] May link to an Asset with the attribution information. May link to a Party with the role function “attributedParty”. [Identifier]

Output: attribute

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] 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. [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 [Identifier]

Output: compensate

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Assigner requires that the Assignee(s) permanently removes all copies of the Asset. [Comment] Use a constraint to define under which conditions the Asset should be deleted. [Identifier]

Output: delete

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Assignee requires that the Assigner(s) ensure(s) that the permission on the Asset is exclusive to the Assignee. [Identifier]

Output: ensureExclusivity

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Assigner requires that the Assignee(s) include(s) other related assets in the Asset. [Comment] For example; Bio picture must be included in the attribution. Use of the Asset relation attribute is required [Identifier]

Output: include

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] 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. [Comment] May link to a Party with the role function “informedParty”. [Identifier]

Output: inform

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Assigner requires that the Assignee(s) grants the specified Policy to a third party for their use of the Asset. [Identifier]

Output: nextPolicy

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] 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. [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”. [Identifier]

Output: obtainConsent

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Assigner requires that the Assignee(s) has(ve) a person review the Policy applicable to the Asset. [Comment] Used when human intervention is required to review the Policy. May link to an Asset which represents the full Policy information. [Identifier]

Output: reviewPolicy

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] 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. [Comment] The Asset is no longer accessible to the Assignee(s). [Identifier]

Output: uninstall

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Assigner requires that the Assignee(s) apply(ies) a watermark as provided by the Assigner to the Asset. [Comment] It is recommended to embed a link to the watermark. [Identifier]

Output: watermark

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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: [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: [Attribute Name] dest [Details]

Output: is an ECMAScript expression which returns a string that is the target of the outbound telephone call. A platform MUST support a telephone URI, as described in http://www.ietf.org/rfc/rfc2806.txt and MAY support a SIP URI as described in http://www.ietf.org/rfc/rfc2543.txt

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] conid [Details]

Output: is an ECMAScript left-hand-side expression that receives the identifier of the Connection on which the outgoing call is attempted.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] aai [Details]

Output: is an optional ECMAScript expression which returns a string of application-to-application information to be passed to the destination endpoint when establishing the connection. Note: Even if an implementation platform accepts the aai data, certain protocols and network elements may prevent it's transmission to the target endpoint. If the platform does not support the transmission of aai data it should raise a connection.PROGRESSING event and indicate that the use of aai is not supported.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] callerid [Details]

Output: is an optional ECMAScript expression which returns a string defining the caller identity to be used when making the outbound connection. The format of this information is protocol and platform specific but might consist of a telephone URI, as described in http://www.ietf.org/rfc/rfc2806.txt or a SIP URI as described in http://www.ietf.org/rfc/rfc2543.txt. Note: An implementation platform is not required to use the specified data and certain protocols and network elements may prevent it's use. If the platform does not support specification of callerid it should raise a connection.PROGRESSING event and indicate that the use of callerid is not supported.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] hints [Details]

Output: is an optional ECMAScript expression which returns an object containing information which may be used by the implementing platform when establishing the outbound connection. This information may consist of protocol-specific parameters, protocol selection guidelines, or routing hints. Note: The meaning of these hints is specific to the implementing platform.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] use [Details]

Output: is an ECMAScript expression which returns a string that is the identifier of the Connection to be used for the outbound call; this attribute is mutually exclusive with connid

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] timeout [Details]

Output: is an ECMAScript expression returning a string in CSS2 format interpreted as a time interval. The interval begins when the createcall element is executed. The createcall will fail if not completed by the end of this interval. A failed createcall will return the connection.FAILED event.

Voice Browser Call Control: CCXML Version 1.0


Input: [EXI Option] alignment [Default Value] bit-packed [Description]

Output: Alignment of event codes and content items

Efficient XML Interchange (EXI) Format 1.0

Table 5-1. EXI Options in Options Document


Input: [EXI Option] compression [Default Value] false [Description]

Output: EXI compression is used to achieve better compactness

Efficient XML Interchange (EXI) Format 1.0


Input: [EXI Option] strict [Default Value] false [Description]

Output: Strict interpretation of schemas is used to achieve better compactness

Efficient XML Interchange (EXI) Format 1.0


Input: [EXI Option] fragment [Default Value] false [Description]

Output: Body is encoded as an EXI fragment instead of an EXI document

Efficient XML Interchange (EXI) Format 1.0


Input: [EXI Option] preserve [Default Value] all false [Description]

Output: Specifies whether comments, pis, etc. are preserved

Efficient XML Interchange (EXI) Format 1.0


Input: [EXI Option] selfContained [Default Value] false [Description]

Output: Enables self-contained elements

Efficient XML Interchange (EXI) Format 1.0


Input: [EXI Option] schemaID [Default Value] no default value [Description]

Output: Identify the schema information, if any, used to encode the body

Efficient XML Interchange (EXI) Format 1.0


Input: [EXI Option] datatypeRepresentationMap [Default Value] no default value [Description]

Output: Specify alternate datatype representations for typed values in the EXI body

Efficient XML Interchange (EXI) Format 1.0


Input: [EXI Option] blockSize [Default Value] 1,000,000 [Description]

Output: Specifies the block size used for EXI compression

Efficient XML Interchange (EXI) Format 1.0


Input: [EXI Option] valueMaxLength [Default Value] unbounded [Description]

Output: Specifies the maximum string length of value content items to be considered for addition to the string table.

Efficient XML Interchange (EXI) Format 1.0


Input: [EXI Option] valuePartitionCapacity [Default Value] unbounded [Description]

Output: Specifies the total capacity of value partitions in a string table

Efficient XML Interchange (EXI) Format 1.0


Input: [EXI Option] [user defined meta-data] [Default Value] no default value [Description]

Output: User defined meta-data may be added

Efficient XML Interchange (EXI) Format 1.0


Input: [Value] (true | false) [Description] Is set, usually, answers to Boolean true state for 2-state widgets. [State]

Output: checked

State and Adaptable Properties Draft 20050824


Input: [Value] (true | false) [Description] Indicates that the widget has in icon form [State]

Output: iconed

State and Adaptable Properties Draft 20050824


Input: [Value] (true | false) [Description] Indicates that the widget is present, but is not allowed for user actions - disabled elements cannot have focus. [State]

Output: disabled

State and Adaptable Properties Draft 20050824


Input: [Value] (true | false) [Description] Indicates that the widget is present, but is not allowed for user actions - However readonly elements can have focus. [Base and Related Concepts] related concept from XFORMS [State]

Output: readonly

State and Adaptable Properties Draft 20050824


Input: [Value] (true | false) [Description] Indicates that user may select more than one item from the current list. [State]

Output: multiselectable

State and Adaptable Properties Draft 20050824


Input: [Value] (true | false) [Description] The DOM activate event occurs when an element is activated, for instance, through a mouse-click or a key-press [Base and Related Concepts] SVG DOM active [State]

Output: domactive

State and Adaptable Properties Draft 20050824


Input: [Value] CDATA [Description] Defines the zoom of the element (e.g. 150%). [Base and Related Concepts] SVG [State]

Output: zoom

State and Adaptable Properties Draft 20050824


Input: [Value] (true | false) [Description] Indicates that an expandable/collapsible group of elements is currently expanded, i.e. all its child elements are shown [Base and Related Concepts] DOM ? [State]

Output: expanded

State and Adaptable Properties Draft 20050824


Input: [Value] (true | false) [Description] Indicates that a selectable element is actually selected [Base and Related Concepts] domActive [State]

Output: selected

State and Adaptable Properties Draft 20050824


Input: [Value] (true | false) [Description] Indicates that the button is pressed down Q: Do we want it? Is it the same as selected? [Base and Related Concepts] selected [State]

Output: pressed

State and Adaptable Properties Draft 20050824


Input: [Value] (true | false) (Q: what values do we want) [Description] Indicates an important widget. [Base and Related Concepts] XHTML roles Main / secondary [State]

Output: important

State and Adaptable Properties Draft 20050824


Input: [Value] (true | false) [Description] Indicates that some user-input is required before submission. [State]

Output: required

State and Adaptable Properties Draft 20050824


Input: [Value] CDATA [Description] Special effects working on a widget, such as fadeout [State]

Output: haseffect

State and Adaptable Properties Draft 20050824


Input: [Value] CDATA [Description] The (default) value of a widget. [Base and Related Concepts] XFORMS Range start [State]

Output: valueNew

State and Adaptable Properties Draft 20050824


Input: [Value] CDATA [Description] Maximum allowed value for a Range type of widget [Base and Related Concepts] XFORMS range [State]

Output: valuemax

State and Adaptable Properties Draft 20050824


Input: [Value] CDATA [Description] Minimum allowed value for a Range type of widget [Base and Related Concepts] XFORMS range [State]

Output: valuemin

State and Adaptable Properties Draft 20050824


Input: [Value] CDATA [Description] Minimal value by which a Range element value may be increased or decreased [Base and Related Concepts] XFORMS Range step [State]

Output: step

State and Adaptable Properties Draft 20050824


Input: [Value] (true | false) [Description] Indicates that the element's value is currently invalid, which prevents the form from being submitted. [State]

Output: invalid

State and Adaptable Properties Draft 20050824


Input: [Value] IDREF [Description] Points to element which describes the widget [State]

Output: describedby

State and Adaptable Properties Draft 20050824


Input: [Value] IDREF [Description] Points to element which labels the widget [State]

Output: labeledby

State and Adaptable Properties Draft 20050824


Input: [Value] IDREF [Description] Points to parent element such as the menu item of which this is a pop up menu [Base and Related Concepts] baseConcept: DC:Source, DC:isPartOf [State]

Output: hasparent

State and Adaptable Properties Draft 20050824


Input: [Value] IDREF [Description] Points to the child [State]

Output: haschild

State and Adaptable Properties Draft 20050824


Input: [Value] CDATA (Q: what values do we want) [Description] Type of has child (Q: do we need it? ) [Base and Related Concepts] haschild [State]

Output: haspopup

State and Adaptable Properties Draft 20050824


Input: [Value] CDATA [Description] Lists alternate styles for the element [State]

Output: alternatestyle

State and Adaptable Properties Draft 20050824


Input: [Value] Number (Q: what values do we want) [Description] The ordinal number of the element on the screen/page Note: Tabindex has not been added to the basic namespace but only to div, span, p, td, th and li tags in the extended XHTML Doctype. Tabindex should not be used with a prefix. [State]

Output: tabindex

State and Adaptable Properties Draft 20050824


Input: [Value] IDREF [Description] The ID of the next element in the default page reading order [State]

Output: flowto

State and Adaptable Properties Draft 20050824


Input: [Value] IDREF [Description] The ID of the previous element in the default page reading order [State]

Output: flowfrom

State and Adaptable Properties Draft 20050824


Input: [Value] IDREF [Description] The ID of the element that is controlled by this element [Base and Related Concepts] XML events object [State]

Output: controls

State and Adaptable Properties Draft 20050824


Input: [Value] IDREF [Description] The ID of the element that controls this element [Base and Related Concepts] XML events [State]

Output: controlledby

State and Adaptable Properties Draft 20050824


Input: [Value] CDATA (Q: what values do we want) [Description] Points to the parent page of the page Q: do we need it? [Base and Related Concepts] hasParent [State]

Output: subpageof

State and Adaptable Properties Draft 20050824


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

Output: No reply from reviewer


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

Output: No reply from reviewer


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

Output: No reply from reviewer


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

Output: No response to reviewer


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

Output: No reply from reviewer


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

Output: No reply from reviewer


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

Output: No response to reviewer


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

Output: No response to reviewer


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

Output: No response to reviewer


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

Output: No response to reviewer


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

Output: No response to reviewer


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

Output: No response to reviewer


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

Output: No response to reviewer


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

Output: No response to reviewer


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

Output: No response to reviewer


Input: [Range] Participant [Kind] Thing [Property]

Output: hasParticipant


Input: [Range] Input [Kind] Parameter [Property]

Output: hasInput


Input: [Range] Output [Kind] Parameter [Property]

Output: hasOutput


Input: [Range] Local [Kind] Parameter [Property]

Output: hasLocal


Input: [Range] Condition [Kind] Expression [Property]

Output: hasPrecondition


Input: [Range] Result [Kind] (see below) [Property]

Output: hasResult


Input: [Field Name] name [Details]

Output: "connection.DISCONNECTED"

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] connid [Details]

Output: The ID of the Connection associated with this event

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] protocol* [Details]

Output: The platform protocol ID of the Connection protocol

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] reason* [Details]

Output: A disconnection reason code

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] info* [Details]

Output: An object which provides additional platform or protocol dependent information

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] connection [Details]

Output: an ECMAScript object reference to the Connection object identified by the connid property for this event

Voice Browser Call Control: CCXML Version 1.0


Input: [Details] an ECMAScript expression which returns the URI of the CCXML document to be fetched. [Attribute Name]

Output: next

Voice Browser Call Control: CCXML Version 1.0


Input: [Details] a list of zero or more CCXML variable names. These variable names and their associated values will be included in the URI sent to the server, with the same qualification used in the namelist. [Attribute Name]

Output: namelist

Voice Browser Call Control: CCXML Version 1.0


Input: [Details] an ECMAScript expression which returns a character string that indicates the HTTP method to use. Valid values are "get" and "post". The default is "get". [Attribute Name]

Output: method

Voice Browser Call Control: CCXML Version 1.0


Input: [Details] is an ECMAScript left-hand-side expression which receives an internally generated unique string identifier to be associated with the completion event. This identifier can be tested by the fetch completion event handler to distinguish among several outstanding fetch requests. If this attribute is not specified, the fetch ID can be acquired from the fetch completion event. Every fetch request will receive a unique fetch ID, even requests for the same document. [Attribute Name]

Output: fetchid

Voice Browser Call Control: CCXML Version 1.0


Input: [Details] is an ECMAScript left-hand-side expression that is set to the fetch completion event. The specification of this attribute in a fetch element implies a blocking fetch, which will be executed synchronously. If this attribute is not specified, the fetch is asynchronous. [Attribute Name]

Output: synch

Voice Browser Call Control: CCXML Version 1.0


Input: [Details] is an ECMAScript expression returning a string in CSS2 format interpreted as a time interval. The interval begins when the fetch element is executed. The fetch will fail if not completed at the end of this interval. A failed fetch will return the error.fetch event. [Attribute Name]

Output: timeout

Voice Browser Call Control: CCXML Version 1.0


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)


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: Frequency estimates of the usage of each entry in the palette by the image.

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 channel values or the palette.

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: [Feature/Operation] propID [Key Word] MUST propID uniquely identifies any privacy proposal [Section]

Output: Terminology


Input: [Feature/Operation] the HTML LINK tag [Key Word] MUST agents and services must be able to locate a proposal in this location [Section]

Output: Data transport


Input: [Feature/Operation] XML parsing [Key Word] MUST proposals and data syntax are readily processed or presented to the user. The RDF data model was used to structure the required grammar/syntax but applications need not support RDF if they do not want to take advantage of the RDF data model. [Section]

Output: XML/RDF encoding


Input: [Feature/Operation] Full XML and XML-namespace support [Key Word] MUST implementations must support full XML and namespaces, not just that used here. [Section]

Output: XML/RDF encoding


Input: [Feature/Operation] base data reference syntax [Key Word] MUST agents must be able to understand that syntax of solicited information [Section]

Output: Data References


Input: [Feature/Operation] harmonized vocabulary [Key Word] MUST see the harmonized vocabulary [HARMV] for requirements; they must be followed otherwise the implementation abuses consensus on adequate levels of privacy disclosure [Section]

Output: Harmonized Vocab


Input: [Feature/Operation] (OK, SRY-, ERR-, SRY, ERR) [Key Word] MUST necessary for reaching agreement. [Section]

Output: Reason Codes


Input: [Feature/Operation] new schema instantiation [Key Word] MAY schemas other than the base set can be instantiated and supported by the agent. [Section]

Output: Data Definitions


Input: [Feature/Operation] source attributes "matched-form" and "extension" [Key Word] MAY agents support multiple, extensible mechanisms by which information is solicited. [Section]

Output: Source Attribute


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

Output: The Party is a single individual

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

Table 2.4.2: Terms for the attribute “scope” of the entity Role


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

Output: The Party represents a defined group with multiple individual members

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] All [Comment] For example, may be used to indicate all the users of a specific social network the party is a member of. Note that “group” scope is also assumed. [Semantics]

Output: All the collective individuals within a context

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] AllConnections [Comment] For example, may be used to indicate all “friends” of the Party. Note that “group” scope is also assumed. [Semantics]

Output: All the first-level connections of the Party

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] All2ndConnections [Comment] For example, may be used to indicate all “friends of friends” of the Party. Note that “group” scope is also assumed. [Semantics]

Output: All the second-level connections of the Party

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] AllGroups [Comment] For example, may be used to indicate all groups that the Party is a member of. Note that “group” scope is also assumed. [Semantics]

Output: All the group connections of the Party

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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: [State] checked [Value] (true | false) [Description]

Output: Is set, usually, answers to Boolean true state for 2-state widgets.

State and Adaptable Properties Draft 20050824


Input: [State] iconed [Value] (true | false) [Description]

Output: Indicates that the widget has in icon form

State and Adaptable Properties Draft 20050824


Input: [State] disabled [Value] (true | false) [Description]

Output: Indicates that the widget is present, but is not allowed for user actions - disabled elements cannot have focus.

State and Adaptable Properties Draft 20050824


Input: [State] readonly [Value] (true | false) [Base and Related Concepts] related concept from XFORMS [Description]

Output: Indicates that the widget is present, but is not allowed for user actions - However readonly elements can have focus.

State and Adaptable Properties Draft 20050824


Input: [State] multiselectable [Value] (true | false) [Description]

Output: Indicates that user may select more than one item from the current list.

State and Adaptable Properties Draft 20050824


Input: [State] domactive [Value] (true | false) [Base and Related Concepts] SVG DOM active [Description]

Output: The DOM activate event occurs when an element is activated, for instance, through a mouse-click or a key-press

State and Adaptable Properties Draft 20050824


Input: [State] zoom [Value] CDATA [Base and Related Concepts] SVG [Description]

Output: Defines the zoom of the element (e.g. 150%).

State and Adaptable Properties Draft 20050824


Input: [State] expanded [Value] (true | false) [Base and Related Concepts] DOM ? [Description]

Output: Indicates that an expandable/collapsible group of elements is currently expanded, i.e. all its child elements are shown

State and Adaptable Properties Draft 20050824


Input: [State] selected [Value] (true | false) [Base and Related Concepts] domActive [Description]

Output: Indicates that a selectable element is actually selected

State and Adaptable Properties Draft 20050824


Input: [State] pressed [Value] (true | false) [Base and Related Concepts] selected [Description]

Output: Indicates that the button is pressed down Q: Do we want it? Is it the same as selected?

State and Adaptable Properties Draft 20050824


Input: [State] important [Value] (true | false) (Q: what values do we want) [Base and Related Concepts] XHTML roles Main / secondary [Description]

Output: Indicates an important widget.

State and Adaptable Properties Draft 20050824


Input: [State] required [Value] (true | false) [Description]

Output: Indicates that some user-input is required before submission.

State and Adaptable Properties Draft 20050824


Input: [State] haseffect [Value] CDATA [Description]

Output: Special effects working on a widget, such as fadeout

State and Adaptable Properties Draft 20050824


Input: [State] valueNew [Value] CDATA [Base and Related Concepts] XFORMS Range start [Description]

Output: The (default) value of a widget.

State and Adaptable Properties Draft 20050824


Input: [State] valuemax [Value] CDATA [Base and Related Concepts] XFORMS range [Description]

Output: Maximum allowed value for a Range type of widget

State and Adaptable Properties Draft 20050824


Input: [State] valuemin [Value] CDATA [Base and Related Concepts] XFORMS range [Description]

Output: Minimum allowed value for a Range type of widget

State and Adaptable Properties Draft 20050824


Input: [State] step [Value] CDATA [Base and Related Concepts] XFORMS Range step [Description]

Output: Minimal value by which a Range element value may be increased or decreased

State and Adaptable Properties Draft 20050824


Input: [State] invalid [Value] (true | false) [Description]

Output: Indicates that the element's value is currently invalid, which prevents the form from being submitted.

State and Adaptable Properties Draft 20050824


Input: [State] describedby [Value] IDREF [Description]

Output: Points to element which describes the widget

State and Adaptable Properties Draft 20050824


Input: [State] labeledby [Value] IDREF [Description]

Output: Points to element which labels the widget

State and Adaptable Properties Draft 20050824


Input: [State] hasparent [Value] IDREF [Base and Related Concepts] baseConcept: DC:Source, DC:isPartOf [Description]

Output: Points to parent element such as the menu item of which this is a pop up menu

State and Adaptable Properties Draft 20050824


Input: [State] haschild [Value] IDREF [Description]

Output: Points to the child

State and Adaptable Properties Draft 20050824


Input: [State] haspopup [Value] CDATA (Q: what values do we want) [Base and Related Concepts] haschild [Description]

Output: Type of has child (Q: do we need it? )

State and Adaptable Properties Draft 20050824


Input: [State] alternatestyle [Value] CDATA [Description]

Output: Lists alternate styles for the element

State and Adaptable Properties Draft 20050824


Input: [State] tabindex [Value] Number (Q: what values do we want) [Description]

Output: The ordinal number of the element on the screen/page Note: Tabindex has not been added to the basic namespace but only to div, span, p, td, th and li tags in the extended XHTML Doctype. Tabindex should not be used with a prefix.

State and Adaptable Properties Draft 20050824


Input: [State] flowto [Value] IDREF [Description]

Output: The ID of the next element in the default page reading order

State and Adaptable Properties Draft 20050824


Input: [State] flowfrom [Value] IDREF [Description]

Output: The ID of the previous element in the default page reading order

State and Adaptable Properties Draft 20050824


Input: [State] controls [Value] IDREF [Base and Related Concepts] XML events object [Description]

Output: The ID of the element that is controlled by this element

State and Adaptable Properties Draft 20050824


Input: [State] controlledby [Value] IDREF [Base and Related Concepts] XML events [Description]

Output: The ID of the element that controls this element

State and Adaptable Properties Draft 20050824


Input: [State] subpageof [Value] CDATA (Q: what values do we want) [Base and Related Concepts] hasParent [Description]

Output: Points to the parent page of the page Q: do we need it?

State and Adaptable Properties Draft 20050824


Input: [Section] Terminology [Feature/Operation] propID propID uniquely identifies any privacy proposal [Key Word]

Output: MUST


Input: [Section] Data transport [Feature/Operation] the HTML LINK tag agents and services must be able to locate a proposal in this location [Key Word]

Output: MUST


Input: [Feature/Operation] the HTTP extension mechanism agents and services must be able to locate a proposal in this location [Key Word]

Output: MUST


Input: [Section] XML/RDF encoding [Feature/Operation] XML parsing proposals and data syntax are readily processed or presented to the user. The RDF data model was used to structure the required grammar/syntax but applications need not support RDF if they do not want to take advantage of the RDF data model. [Key Word]

Output: MUST


Input: [Section] XML/RDF encoding [Feature/Operation] Full XML and XML-namespace support implementations must support full XML and namespaces, not just that used here. [Key Word]

Output: MUST


Input: [Section] Data References [Feature/Operation] base data reference syntax agents must be able to understand that syntax of solicited information [Key Word]

Output: MUST


Input: [Section] Harmonized Vocab [Feature/Operation] harmonized vocabulary see the harmonized vocabulary [HARMV] for requirements; they must be followed otherwise the implementation abuses consensus on adequate levels of privacy disclosure [Key Word]

Output: MUST


Input: [Section] Reason Codes [Feature/Operation] (OK, SRY-, ERR-, SRY, ERR) necessary for reaching agreement. [Key Word]

Output: MUST


Input: [Feature/Operation] propID repository full proposals can be compactly represented, new negotiation and agreement are not necessary if an agreement already exists. [Key Word]

Output: SHOULD


Input: [Feature/Operation] data repository frequently requested user profile information is stored and managed by the user. [Key Word]

Output: MAY


Input: [Section] Data Definitions [Feature/Operation] new schema instantiation schemas other than the base set can be instantiated and supported by the agent. [Key Word]

Output: MAY


Input: [Section] Source Attribute [Feature/Operation] source attributes "matched-form" and "extension" agents support multiple, extensible mechanisms by which information is solicited. [Key Word]

Output: MAY


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


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: [Part] 1 [Type] For Users [Document]

Output: Document Overview. A quick overview of the OWL 2 specification that includes a description of its relationship to OWL 1. This it the starting point and primary reference point for OWL 2.

OWL 2 Web Ontology Language Document Overview


Input: [Part] 2 [Type] Core Specification [Document]

Output: Structural Specification and Functional-Style Syntax defines the constructs of OWL 2 ontologies in terms of both their structure and a functional-style syntax, and defines OWL 2 DL ontologies in terms of global restrictions on OWL 2 ontologies.

OWL 2 Web Ontology Language Document Overview


Input: [Part] 3 [Type] Core Specification [Document]

Output: Mapping to RDF Graphs defines a mapping of the OWL 2 constructs into RDF graphs, and thus defines the primary means of exchanging OWL 2 ontologies in the Semantic Web.

OWL 2 Web Ontology Language Document Overview


Input: [Part] 4 [Type] Core Specification [Document]

Output: Direct Semantics defines the meaning of OWL 2 ontologies in terms of a model-theoretic semantics.

OWL 2 Web Ontology Language Document Overview


Input: [Part] 5 [Type] Core Specification [Document]

Output: RDF-Based Semantics defines the meaning of OWL 2 ontologies via an extension of the RDF Semantics.

OWL 2 Web Ontology Language Document Overview


Input: [Part] 6 [Type] Core Specification [Document]

Output: Conformance provides requirements for OWL 2 tools and a set of test cases to help determine conformance.

OWL 2 Web Ontology Language Document Overview


Input: [Part] 7 [Type] Specification [Document]

Output: Profiles defines three sub-languages of OWL 2 that offer important advantages in particular applications scenarios.

OWL 2 Web Ontology Language Document Overview


Input: [Part] 8 [Type] For Users [Document]

Output: OWL 2 Primer provides an approachable introduction to OWL 2, including orientation for those coming from other disciplines.

OWL 2 Web Ontology Language Document Overview


Input: [Part] 9 [Type] For Users [Document]

Output: OWL 2 New Features and Rationale provides an overview of the main new features of OWL 2 and motivates their inclusion in the language.

OWL 2 Web Ontology Language Document Overview


Input: [Part] 10 [Type] For Users [Document]

Output: OWL 2 Quick Reference Guide provides a brief guide to the constructs of OWL 2, noting the changes from OWL 1.

OWL 2 Web Ontology Language Document Overview


Input: [Part] 11 [Type] Specification [Document]

Output: XML Serialization defines an XML syntax for exchanging OWL 2 ontologies, suitable for use with XML tools like schema-based editors and XQuery/XPath.

OWL 2 Web Ontology Language Document Overview


Input: [Part] 12 [Type] Specification [Document]

Output: Manchester Syntax (WG Note) defines an easy-to-read, but less formal, syntax for OWL 2 that is used in some OWL 2 user interface tools and is also used in the Primer.

OWL 2 Web Ontology Language Document Overview


Input: [Part] 13 [Type] Specification [Document]

Output: Data Range Extension: Linear Equations (WG Note) specifies an optional extension to OWL 2 which supports advanced constraints on the values of properties.

OWL 2 Web Ontology Language Document Overview


Input: [Description] Alignment of event codes and content items [Default Value] bit-packed [EXI Option]

Output: alignment

Efficient XML Interchange (EXI) Format 1.0


Input: [Description] EXI compression is used to achieve better compactness [Default Value] false [EXI Option]

Output: compression

Efficient XML Interchange (EXI) Format 1.0


Input: [Description] Strict interpretation of schemas is used to achieve better compactness [Default Value] false [EXI Option]

Output: strict

Efficient XML Interchange (EXI) Format 1.0


Input: [Description] Body is encoded as an EXI fragment instead of an EXI document [Default Value] false [EXI Option]

Output: fragment

Efficient XML Interchange (EXI) Format 1.0


Input: [Description] Specifies whether comments, pis, etc. are preserved [Default Value] all false [EXI Option]

Output: preserve

Efficient XML Interchange (EXI) Format 1.0


Input: [Description] Enables self-contained elements [Default Value] false [EXI Option]

Output: selfContained

Efficient XML Interchange (EXI) Format 1.0


Input: [Description] Identify the schema information, if any, used to encode the body [Default Value] no default value [EXI Option]

Output: schemaID

Efficient XML Interchange (EXI) Format 1.0


Input: [Description] Specify alternate datatype representations for typed values in the EXI body [Default Value] no default value [EXI Option]

Output: datatypeRepresentationMap

Efficient XML Interchange (EXI) Format 1.0


Input: [Description] Specifies the block size used for EXI compression [Default Value] 1,000,000 [EXI Option]

Output: blockSize

Efficient XML Interchange (EXI) Format 1.0


Input: [Description] Specifies the maximum string length of value content items to be considered for addition to the string table. [Default Value] unbounded [EXI Option]

Output: valueMaxLength

Efficient XML Interchange (EXI) Format 1.0


Input: [Description] Specifies the total capacity of value partitions in a string table [Default Value] unbounded [EXI Option]

Output: valuePartitionCapacity

Efficient XML Interchange (EXI) Format 1.0


Input: [Description] User defined meta-data may be added [Default Value] no default value [EXI Option]

Output: [user defined meta-data]

Efficient XML Interchange (EXI) Format 1.0


Input: [Semantics] The Party is a single individual [Comment] Must be supported. [Identifier]

Output: Individual

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Party represents a defined group with multiple individual members [Comment] Must be supported. [Identifier]

Output: Group

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] All the collective individuals within a context [Comment] For example, may be used to indicate all the users of a specific social network the party is a member of. Note that “group” scope is also assumed. [Identifier]

Output: All

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] All the first-level connections of the Party [Comment] For example, may be used to indicate all “friends” of the Party. Note that “group” scope is also assumed. [Identifier]

Output: AllConnections

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] All the second-level connections of the Party [Comment] For example, may be used to indicate all “friends of friends” of the Party. Note that “group” scope is also assumed. [Identifier]

Output: All2ndConnections

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] All the group connections of the Party [Comment] For example, may be used to indicate all groups that the Party is a member of. Note that “group” scope is also assumed. [Identifier]

Output: AllGroups

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Section] Status of This Document [Change]

Output: mentioned ruby naming and structure control as issues to be discussed at the next WG meeting


Input: [Section] 1. Introduction [Change]

Output: removed a mention of formatting added a description and diagrams of ruby text that appears below the base or on the left (if vertical) covered the case of ruby text appearing below and above clarified the role the inline form of ruby text as a fallback additional clarifications and minor rewordings corrected figure 1.1.5 more markup examples for figure 1.1.7


Input: [Section] 2.2 The rb element [Change]

Output: allowed nesting of ruby elements inside of rb added examples of this functionality changed %ruby.content to %Inline


Input: [Section] 2.4 The rp element [Change]

Output: removed a mention of specific CSS properties


Input: [Section] 3. Ruby Box Model [Change]

Output: moved the whole section to i18n-format


Input: [Section] References [Change]

Output: added a reference to i18n-format updated the reference from HTML-XML to XHTML


Input: [Section] Changes from Previous Public Working Draft [Change]

Output: created new section


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

Output: link role


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

Output: No role


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

Output: article role


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

Output: note role


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

Output: No role


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

Output: button role


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

Output: group role


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

Output: No role


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

Output: No role


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

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


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

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


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

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


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

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


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

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


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

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


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

Output: No role


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

Output: No role


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

Output: img role


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

Output: img role


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

Output: button role


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

Output: checkbox role


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

Output: button role


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

Output: radio role


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

Output: listitem role


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

Output: No role


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

Output: list role


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

Output: status role


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

Output: region role


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

Output: list role


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

Output: No role


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

Output: document role


Input: [Definition] Character data [Attribute Type]

Output: CDATA


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

Output: ID


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

Output: IDREF


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

Output: IDREFS


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

Output: NAME


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

Output: NMTOKEN


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

Output: NMTOKENS


Input: [Test Case] 9.1.1.a [Link To Spec] 9.1.1 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: precedence of group element


Input: [Test Case] 9.1.1.b [Link To Spec] 9.1.1 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: label element in a group element


Input: [Test Case] 9.1.1.c [Link To Spec] 9.1.1 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: focus set to group element


Input: [Test Case] 9.1.1.d [Link To Spec] 9.1.1 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: group element inside case element of a switch


Input: [Test Case] 9.2.1.a [Link To Spec] 9.2.1 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: switch element


Input: [Test Case] 9.2.1.b [Link To Spec] 9.2.1 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: switch element receives events


Input: [Test Case] 9.2.2.a [Link To Spec] 9.2.2 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: multiple cases in a switch


Input: [Test Case] 9.2.2.b [Link To Spec] 9.2.2 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: multiple cases in a switch, one has selected="true"


Input: [Test Case] 9.2.2.c [Link To Spec] 9.2.2 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: multiple cases in a switch have selected="true"


Input: [Test Case] 9.2.3.a [Link To Spec] 9.2.3 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: toggle element events dispatched


Input: [Test Case] 9.3.1.a [Link To Spec] 9.3.1 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: repeat element over homogeneous collection


Input: [Test Case] 9.3.1.b [Link To Spec] 9.3.1 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: startindex attribute of repeat element


Input: [Test Case] 9.3.1.c [Link To Spec] 9.3.1 [Normative for XForms Basic] false [Normative for XForms Full] false [Description]

Output: number attribute of repeat element


Input: [Test Case] 9.3.1.d [Link To Spec] 9.3.1 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: unrolling a repeat element


Input: [Test Case] 9.3.1.e [Link To Spec] 9.3.1 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: example of repeat element


Input: [Test Case] 9.3.1.f [Link To Spec] 9.3.1 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: switch element within repeat element


Input: [Test Case] 9.3.2.a [Link To Spec] 9.3.2 [Normative for XForms Basic] false [Normative for XForms Full] false [Description]

Output: example of repeat structure using attributes in html table


Input: [Test Case] 9.3.3.a [Link To Spec] 9.3.3 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: example of itemset element


Input: [Test Case] 9.3.4.a [Link To Spec] 9.3.4 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: copy element


Input: [Test Case] 9.3.4.b [Link To Spec] 9.3.4 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: copy element has xforms-binding-exception event


Input: [Test Case] 9.3.5.a [Link To Spec] 9.3.5 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: insert element rules


Input: [Test Case] 9.3.6.a [Link To Spec] 9.3.6 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: delete element rules


Input: [Test Case] 9.3.7.a [Link To Spec] 9.3.7 [Normative for XForms Basic] true [Normative for XForms Full] true [Description]

Output: setindex element rules


Input: [Property] hasParticipant [Kind] Thing [Range]

Output: Participant


Input: [Property] hasInput [Kind] Parameter [Range]

Output: Input


Input: [Property] hasOutput [Kind] Parameter [Range]

Output: Output


Input: [Property] hasLocal [Kind] Parameter [Range]

Output: Local


Input: [Property] hasPrecondition [Kind] Expression [Range]

Output: Condition


Input: [Property] hasResult [Kind] (see below) [Range]

Output: Result


Input: [Field Name] name [Details]

Output: "connection.FAILED"

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] connid [Details]

Output: The ID of the Connection associated with this event

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] protocol* [Details]

Output: The platform protocol ID of the Connection protocol

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] reason* [Details]

Output: A failure reason code

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] info* [Details]

Output: An object which provides additional platform or protocol dependent information

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] connection [Details]

Output: an ECMAScript object reference to the Connection object identified by the connid property for this event

Voice Browser Call Control: CCXML Version 1.0


Input: [Part] 1 [Document] Document Overview. A quick overview of the OWL 2 specification that includes a description of its relationship to OWL 1. This it the starting point and primary reference point for OWL 2. [Type]

Output: For Users

OWL 2 Web Ontology Language Document Overview


Input: [Part] 2 [Document] Structural Specification and Functional-Style Syntax defines the constructs of OWL 2 ontologies in terms of both their structure and a functional-style syntax, and defines OWL 2 DL ontologies in terms of global restrictions on OWL 2 ontologies. [Type]

Output: Core Specification

OWL 2 Web Ontology Language Document Overview


Input: [Part] 3 [Document] Mapping to RDF Graphs defines a mapping of the OWL 2 constructs into RDF graphs, and thus defines the primary means of exchanging OWL 2 ontologies in the Semantic Web. [Type]

Output: Core Specification

OWL 2 Web Ontology Language Document Overview