Input: [0] Staff Contact [Working] Yes [Community] No [Business] Consulting role (e.g,. share expertise, but not likely to attend meetings regularly). But determined by W3C Management on a case-by-case basis. [Interest]

Output: Yes

Comparison of Group Types | Community and Business Groups


Input: [0] Other Staff Interactions [Working] Background support and coordination [Community] Monitoring, Outreach [Business] One project review with Team annually Light Monitoring by staff Liaison role as needed Communications of final reports through W3C news channels and to W3C Membership [Interest]

Output: Background support and coordination (for some)

Comparison of Group Types | Community and Business Groups


Input: [0] Other Coordination [Working] Via Coordination Groups [Community] Ad-hoc (e.g., organized by Community Development Lead) [Business] Direct Chair-to-Chair connectivity for Business Groups developing material intended as input to a Working Group. [Interest]

Output: Via Coordination Groups

Comparison of Group Types | Community and Business Groups


Input: [0] Fee to participate or organize [Working] Membership or Invited Expert (no fee) [Community] None [Business] Annual fees [Interest]

Output: Membership or Invited Expert (no fee)

Comparison of Group Types | Community and Business Groups


Input: [0] Visibility of comms. [Working] Public or Member [Community] Public (with non-Public for admin) [Business] Public or non-Public [Interest]

Output: Generally Public

Comparison of Group Types | Community and Business Groups


Input: [0] Patent Licensing Commitment for this Group’s Deliverables [Working] Defined for Recommendation track documents in Section 3 of W3C Patent Policy [Community] Defined in section 3 of W3C Community Contributor License Agreement (CLA) or Final Specification Agreement [Business] Defined in section 3 of W3C Community Contributor License Agreement (CLA) or Final Specification Agreement [Interest]

Output: No

Comparison of Group Types | Community and Business Groups


Input: [0] Patent Disclosure Obligation [Working] Defined in Section 6 of W3C Patent Policy [Community] Defined in Section 6 of W3C Patent Policy; no new obligations under CLA/FSA [Business] Defined in Section 6 of W3C Patent Policy; no new obligations under CLA/FSA [Interest]

Output: Defined in Section 6 of W3C Patent Policy

Comparison of Group Types | Community and Business Groups


Input: [0] Copyright for documents [Working] W3C Document License [Community] W3C Community Contributor License Agreement (CLA), Final Specification Agreement [Business] W3C Community Contributor License Agreement (CLA), Final Specification Agreement or W3C Document License [Interest]

Output: W3C Document License

Comparison of Group Types | Community and Business Groups


Input: [0] Copyright for software [Working] W3C Software License [Community] Group determines, but expectation is compatibility with Open Source Software Licenses. [Business] Group determines, but expectation is compatibility with Open Source Software Licenses. [Interest]

Output: W3C Software License

Comparison of Group Types | Community and Business Groups


Input: [0] Chair selection [Working] Appointed by Director [Community] Group determines [Business] Group determines [Interest]

Output: Appointed by Director

Comparison of Group Types | Community and Business Groups


Input: [0] Reporting requirement [Working] Heartbeat requirement [Community] None [Business] Public reporting expected periodically if group operates primarily internally. [Interest]

Comparison of Group Types | Community and Business Groups


Input: [0] Access to Member site [Working] Depends on charter [Community] No [Business] No [Interest]

Output: Depends on charter

Comparison of Group Types | Community and Business Groups


Input: [0] Decision-making based on consensus [Working] Required [Community] Recommended where applicable [Business] Recommended where applicable [Interest]

Output: Required where applicable

Comparison of Group Types | Community and Business Groups


Input: [0] Expectations regarding scope overlap with other groups [Working] Actively avoided [Community] Acceptable but not recommended [Business] Acceptable but not recommended [Interest]

Output: Actively avoided

Comparison of Group Types | Community and Business Groups


Input: [QName Local Name] Success [Final] Final [Description]

Output: The operation succeeded.

XML Key Management Specification (XKMS 2.0)


Input: [QName Local Name] VersionMismatch [Final] Final [Description]

Output: The service does not support the protocol version specified in the request.

XML Key Management Specification (XKMS 2.0)


Input: [QName Local Name] Sender [Final] Final [Description]

Output: An error occurred that was due to the message sent by the sender.

XML Key Management Specification (XKMS 2.0)


Input: [QName Local Name] Receiver [Final] Final [Description]

Output: An error occurred at the receiver.

XML Key Management Specification (XKMS 2.0)


Input: [QName Local Name] Represent [Final] Not Final [Description]

Output: The service has not acted on the request. In order for the request to be acted upon the request MUST be represented with the specified nonce in accordance with the two phase protocol

XML Key Management Specification (XKMS 2.0)


Input: [QName Local Name] Pending [Final] Not Final [Description]

Output: The request has been accepted for processing and the service will return the result asynchronously

XML Key Management Specification (XKMS 2.0)


Input: [Attribute Type] CDATA [Definition]

Output: Character data


Input: [Attribute Type] ID [Definition]

Output: A document-unique identifier


Input: [Attribute Type] IDREF [Definition]

Output: A reference to a document-unique identifier


Input: [Attribute Type] IDREFS [Definition]

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


Input: [Attribute Type] NAME [Definition]

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


Input: [Attribute Type] NMTOKEN [Definition]

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


Input: [Attribute Type] NMTOKENS [Definition]

Output: One or more whitespace separated NMTOKEN values


Input: [Attribute Type] PCDATA [Definition]

Output: Processed character data


Input: [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. [Vocab] 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; 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: [QName Local Name] Success [Description] The operation succeeded. [Final]

Output: Final

XML Key Management Specification (XKMS 2.0)


Input: [QName Local Name] VersionMismatch [Description] The service does not support the protocol version specified in the request. [Final]

Output: Final

XML Key Management Specification (XKMS 2.0)


Input: [QName Local Name] Sender [Description] An error occurred that was due to the message sent by the sender. [Final]

Output: Final

XML Key Management Specification (XKMS 2.0)


Input: [QName Local Name] Receiver [Description] An error occurred at the receiver. [Final]

Output: Final

XML Key Management Specification (XKMS 2.0)


Input: [QName Local Name] Represent [Description] The service has not acted on the request. In order for the request to be acted upon the request MUST be represented with the specified nonce in accordance with the two phase protocol [Final]

Output: Not Final

XML Key Management Specification (XKMS 2.0)


Input: [QName Local Name] Pending [Description] The request has been accepted for processing and the service will return the result asynchronously [Final]

Output: Not Final

XML Key Management Specification (XKMS 2.0)


Input: [Event Identifier] DOMFocusIn [Description] Occurs when an element receives focus. [DOM3 event category] UIEvent [Bubbling phase] Yes [Cancel -able] No [uDOM interface] UIEvent [Animation event name]

Output: focusin


Input: [Event Identifier] DOMFocusOut [Description] Occurs when an element loses focus. [DOM3 event category] UIEvent [Bubbling phase] Yes [Cancel -able] No [uDOM interface] UIEvent [Animation event name]

Output: focusout


Input: [Event Identifier] DOMActivate [Description] Occurs when an element is activated, for instance, through a mouse click or a keypress. [DOM3 event category] UIEvent [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] UIEvent [Animation event name]

Output: activate


Input: [Event Identifier] click [Description] Occurs when the pointing device button is clicked over an element. A click is defined as a mousedown and mouseup over the same screen location. The sequence of these events is: mousedown, mouseup, click. If multiple clicks occur at the same screen location, the sequence repeats with the detail attribute incrementing with each repetition. [DOM3 event category] MouseEvent [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] MouseEvent [Animation event name]

Output: click


Input: [Event Identifier] mousedown [Description] Occurs when the pointing device button is pressed over an element. [DOM3 event category] MouseEvent [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] MouseEvent [Animation event name]

Output: mousedown


Input: [Event Identifier] mouseup [Description] Occurs when the pointing device button is released over an element. [DOM3 event category] MouseEvent [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] MouseEvent [Animation event name]

Output: mouseup


Input: [Event Identifier] mouseover [Description] Occurs when the pointing device is moved onto an element. [DOM3 event category] MouseEvent [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] MouseEvent [Animation event name]

Output: mouseover


Input: [Event Identifier] mousemove [Description] Occurs when the pointing device is moved while it is over an element. [DOM3 event category] MouseEvent [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] MouseEvent [Animation event name]

Output: mousemove


Input: [Event Identifier] mouseout [Description] Occurs when the pointing device is moved away from an element. [DOM3 event category] MouseEvent [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] MouseEvent [Animation event name]

Output: mouseout


Input: [Event Identifier] textInput [Description] One or more characters have been entered. [DOM3 event category] TextEvent [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] TextEvent [Animation event name]


Input: [Event Identifier] keydown [Description] A key is pressed down. (The normative definition of this event is the description in the DOM3 Events specification.) [DOM3 event category] KeyboardEvent [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] KeyboardEvent [Animation event name]


Input: [Event Identifier] keyup [Description] A key is released. (The normative definition of this event is the description in the DOM3 Events specification.) [DOM3 event category] KeyboardEvent [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] KeyboardEvent [Animation event name]


Input: [Event Identifier] load [Description] The event is triggered at the point at which the user agent finishes loading the element and any dependent resources (such as images, style sheets, or scripts). In the case the element references a script, the event will be raised only after an attempt to interpret the script has been made. Dependent resources that fail to load will not prevent this event from firing if the element that referenced them is still accessible via the DOM unless they are designated as externalResourcesRequired. The event is independent of the means by which the element was added to DOM tree. [DOM3 event category] BasicEvent [Bubbling phase] No [Cancel -able] No [uDOM interface] Event [Animation event name]

Output: load


Input: [Event Identifier] SVGLoad [Description] This event is deprecated and is for backwards compatibility only, see notes below. This event is sent at the same time as the load event, but the load event must be sent before the SVGLoad event. [DOM3 event category] none [Bubbling phase] No [Cancel -able] No [uDOM interface] Event [Animation event name]


Input: [Event Identifier] resize [Description] Occurs when a document view is being resized. This event is only applicable to 'svg' elements and is dispatched after the resize operation has taken place. The target of the event is the 'svg' element. [DOM3 event category] BasicEvent [Bubbling phase] Yes [Cancel -able] No [uDOM interface] Event [Animation event name]

Output: resize


Input: [Event Identifier] SVGResize [Description] This event is deprecated and is for backwards compatibility only, see notes below. This event is sent at the same time as the resize event, but the resize event must be sent before the SVGResize event. [DOM3 event category] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface] Event [Animation event name]


Input: [Event Identifier] scroll [Description] Occurs when a document view is being shifted along the X or Y or both axis, either through a direct user interaction or any change on the currentTranslate property available on SVGSVGElement interface. This event is only applicable to 'svg' elements and is dispatched after the shift modification has taken place. The target of the event is the 'svg' element. [DOM3 event category] BasicEvent [Bubbling phase] Yes [Cancel -able] No [uDOM interface] Event [Animation event name]

Output: scroll


Input: [Event Identifier] SVGScroll [Description] This event is deprecated and is for backwards compatibility only, see notes below. This event is sent at the same time as the scroll event, but the scroll event must be sent before the SVGScroll event. [DOM3 event category] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface] Event [Animation event name]


Input: [Event Identifier] SVGZoom [Description] Occurs when the zoom level of a document view is being changed, either through a direct user interaction or any change to the currentScale property available on SVGSVGElement interface. This event is only applicable to 'svg' elements and is dispatched after the zoom level modification has taken place. The target of the event is the 'svg' element. [DOM3 event category] none [Bubbling phase] No [Cancel -able] No [uDOM interface] Event [Animation event name]

Output: zoom


Input: [Event Identifier] SVGRotate [Description] Occurs when the rotation of a document view is being changed, either through a direct user interaction or any change to the currentRotate property available on SVGSVGElement interface. This event is only applicable to 'svg' elements and is dispatched after the rotation modification has taken place. The target of the event is the 'svg' element. [DOM3 event category] none [Bubbling phase] No [Cancel -able] No [uDOM interface] Event [Animation event name]

Output: rotate


Input: [Event Identifier] beginEvent [Description] Occurs when a Timed Element begins. For details, see the description of the Events and event model in SMIL 2.1. [DOM3 event category] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface] TimeEvent [Animation event name]

Output: beginEvent


Input: [Event Identifier] endEvent [Description] Occurs when a Timed Element ends. For details, see the description of the Events and event model in SMIL 2.1. [DOM3 event category] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface] TimeEvent [Animation event name]

Output: endEvent


Input: [Event Identifier] repeatEvent [Description] Occurs when a Timed Element repeats. It is raised each time the element repeats, after the first iteration. For details, see the description of the Events and event model in SMIL 2.1. [DOM3 event category] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface] TimeEvent [Animation event name]

Output: repeatEvent


Input: [Event Identifier] SVGMousewheel [Description] Occurs when a rotational input device has been activated. [DOM3 event category] MouseEvent [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] WheelEvent [Animation event name]


Input: [Event Identifier] SVGPreload [Description] A load operation has begun. [DOM3 event category] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface] ProgressEvent [Animation event name]


Input: [Event Identifier] SVGLoadProgress [Description] Progress has occurred in loading a given resource. [DOM3 event category] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface] ProgressEvent [Animation event name]


Input: [Event Identifier] SVGPostload [Description] A load operation has completed. [DOM3 event category] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface] ProgressEvent [Animation event name]


Input: [Event Identifier] SVGTimer [Description] Occurs when the specified timer interval has elapsed for a timer. This event is triggered only by 'running' timers in the current global execution context of the SVG document (i.e. for timers which have been instantiated via the SVGGlobal interface and started via the start() method of the Timer interface). The target of the event is the 'timer' object itself. The event processing is limited to the target phase. [DOM3 event category] none [Bubbling phase] No [Cancel -able] No [uDOM interface] Event [Animation event name]


Input: [Event Identifier] SVGConnectionConnected [Description] Occurs when a connection has been established. No context information is available. [DOM3 event category] none [Bubbling phase] No [Cancel -able] No [uDOM interface] ConnectionEvent [Animation event name]


Input: [Event Identifier] SVGConnectionClosed [Description] Occurs when a connection has been closed. No context information is available [DOM3 event category] none [Bubbling phase] No [Cancel -able] No [uDOM interface] ConnectionEvent [Animation event name]


Input: [Event Identifier] SVGConnectionError [Description] Occurs when an error happens during the lifetime of a connection. Additional context information is available in the errorCode field. [DOM3 event category] none [Bubbling phase] No [Cancel -able] No [uDOM interface] ConnectionEvent [Animation event name]


Input: [Event Identifier] SVGConnectionDataSent [Description] Occurs when data has been successfully transmitted. No context information is available. [DOM3 event category] none [Bubbling phase] No [Cancel -able] No [uDOM interface] ConnectionEvent [Animation event name]


Input: [Event Identifier] SVGConnectionDataReceived [Description] Occurs when data has been received on the connection. Additional context information is available on the receivedData field. [DOM3 event category] none [Bubbling phase] No [Cancel -able] No [uDOM interface] ConnectionEvent [Animation event name]


Input: [Name] ServiceDescription [Definition ref] section 4.3 Provenance query service discovery [Description]

Output: Type for a generic provenance query service. Mainly for use in RDF provenance query service descriptions, to facilitate discovery in linked data environments.


Input: [Name] DirectQueryService [Definition ref] section 4.1.1 Direct HTTP query service description [Description]

Output: Type for a direct HTTP query service description. Mainly for use in RDF provenance query service descriptions, to distinguish direct HTTP query service descriptions from other query service descriptions.


Input: [Name] has_anchor [Definition ref] section 3.2 Resource represented as HTML , section 3.3 Resource represented as RDF [Description]

Output: Indicates a target-URI for an resource, used by an associated provenance record.


Input: [Name] has_provenance [Definition ref] section 3.1 Resource accessed by HTTP , section 3.2 Resource represented as HTML [Description]

Output: Indicates a provenance-URI for a resource; the resource identified by this property presents a provenance record about its subject or anchor resource.


Input: [Name] has_query_service [Definition ref] section 3.1.1 Specifying Provenance Query Services [Description]

Output: Indicates a provenance query service that can access provenance related to its subject or anchor resource.


Input: [Name] describesService [Definition ref] section 4.1 Provenance query service description [Description]

Output: relates a generic provenance query service resource (type prov:ServiceDescription ) to a specific query service description (e.g. a prov:DirectQueryService or a sd:Service ).


Input: [Name] provenanceUriTemplate [Definition ref] section 4.1.1 Direct HTTP query service description [Description]

Output: Indicates a URI template string for constructing provenance-URIs


Input: [Name] pingback [Definition ref] section 5. Forward provenance Provenance pingback [Description]

Output: Relates a resource to a provenance pingback service that may receive forward additional provenance links about the resource.


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

Output: Visual

Source Access Mode (before augmentation)


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

Output: Visual

Source Access Mode (before augmentation)


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

Output: Visual

Source Access Mode (before augmentation)


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

Output: Auditory

Source Access Mode (before augmentation)


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

Output: Auditory

Source Access Mode (before augmentation)


Input: [Expected Values] signLanguage [Augmented Access Mode] Visual [Description] The presentation of audio in sign language in the visual presentation. The most likely extension is an ISO 639 sign language code such as /sgn-en-us for American Sign Language.

Output: Auditory

Source Access Mode (before augmentation)


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

Output: Visual

Source Access Mode (before augmentation)


Input: [Expected Values] braille [Augmented Access Mode] Tactile [Description] braille content or alternative is available (e.g., eBraille or print braille). This can have extensions for the different types of braille (/ASCII, /unicode, /music, /math, /chem or /nemeth) as well as /grade1 and /grade2 (contracted) or other nomenclature: we are sure that the community will contribute more suggestions.)

Output: Visual or Textual

Source Access Mode (before augmentation)


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

Output: Visual

Source Access Mode (before augmentation)


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

Output: Visual

Source Access Mode (before augmentation)


Input: [Feature] The use of the role attribute with the value presentation [Indication]

Output: Probably a layout table


Input: [Feature] The use of the border attribute with the non-conforming value 0 [Indication]

Output: Probably a layout table


Input: [Feature] The use of the non-conforming cellspacing and cellpadding attributes with the value 0 [Indication]

Output: Probably a layout table


Input: [Feature] The use of caption, thead, or th elements [Indication]

Output: Probably a non-layout table


Input: [Feature] The use of the headers and scope attributes [Indication]

Output: Probably a non-layout table


Input: [Feature] The use of the border attribute with a value other than 0 [Indication]

Output: Probably a non-layout table


Input: [Feature] Explicit visible borders set using CSS [Indication]

Output: Probably a non-layout table


Input: [Feature] The use of the summary attribute [Indication]

Output: Not a good indicator (both layout and non-layout tables have historically been given this 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: [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: [Mobile device limitations] Small physical screen [Disabilitites]

Output: Can’t see small items


Input: [Mobile device limitations] Zoom interface [Disabilitites]

Output: Narrow vision


Input: [Mobile device limitations] Lightning conditions [Disabilitites]

Output: Color-blindness


Input: [Mobile device limitations] No mouse, limited keyboard [Disabilitites]

Output: Motricity troubles


Input: [Mobile device limitations] Can’t use sound (e.g. socially) [Disabilitites]

Output: Hearing problems


Input: [Mobile device limitations] Limited attention span [Disabilitites]

Output: Attention disorder


Input: [Mobile device limitations] Limited plug-ins support [Disabilitites]

Output: AT and plug-ins


Input: [Mobile device limitations] Download images on demand [Disabilitites]

Output: Can’t see images


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 whitespace separated NMTOKEN values [Attribute Type]

Output: NMTOKENS


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

Output: PCDATA


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

Output: Policy expressions that are formal contracts (or licenses) stipulating all the terms of usage and all the parties involved.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

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


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

Output: Policy expressions that propose terms of usage from an Asset owner

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Policy expressions that stipulate the terms of usage over personal information.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Policy expressions that propose terms of usage to an Asset owner

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Policy expressions that consists of entities from the complete model

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Policy expressions that stipulate the terms of usage and is redeemable by any Party who currently holds the Ticket in their possession

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [anyURI Name] Success [Final] Final [Description]

Output: The operation succeeded.

XML Key Management Specification (XKMS 2.0)


Input: [anyURI Name] VersionMismatch [Final] Final [Description]

Output: The service does not support the protocol version specified in the request.

XML Key Management Specification (XKMS 2.0)


Input: [anyURI Name] Sender [Final] Final [Description]

Output: An error occurred that was due to the message sent by the sender.

XML Key Management Specification (XKMS 2.0)


Input: [anyURI Name] Receiver [Final] Final [Description]

Output: An error occurred at the receiver.

XML Key Management Specification (XKMS 2.0)


Input: [anyURI Name] Represent [Final] Not Final [Description]

Output: The service has not acted on the request. In order for the request to be acted upon the request MUST be represented with the specified nonce in accordance with the two-phase protocol.

XML Key Management Specification (XKMS 2.0)


Input: [anyURI Name] Pending [Final] Not Final [Description]

Output: The request has been accepted for processing and the service will return the result asynchronously.

XML Key Management Specification (XKMS 2.0)


Input: [QName Local Name] Success [Description] The operation succeeded. [Final]

Output: Final

XML Key Management Specification (XKMS 2.0)


Input: [QName Local Name] VersionMismatch [Description] The service does not support the protocol version specified in the request. [Final]

Output: Final

XML Key Management Specification (XKMS 2.0)


Input: [QName Local Name] Sender [Description] An error occurred that was due to the message sent by the sender. [Final]

Output: Final

XML Key Management Specification (XKMS 2.0)


Input: [QName Local Name] Receiver [Description] An error occurred at the receiver. [Final]

Output: Final

XML Key Management Specification (XKMS 2.0)


Input: [QName Local Name] Represent [Description] The service has not acted on the request. In order for the request to be acted upon the request MUST be represented with the specified nonce in accordance with the two phase protocol [Final]

Output: Not Final

XML Key Management Specification (XKMS 2.0)


Input: [QName Local Name] Pending [Description] The request has been accepted for processing and the service will return the result asynchronously [Final]

Output: Not Final

XML Key Management Specification (XKMS 2.0)


Input: [User Action/External Input] User presses button on steering wheel [Action on Device] Service is initiated and GPS satellite detection begins [Event Description] HTTP Request to app server [Resulting Action] Welcome prompts are played. Authentication dialog is initiated (may be initiated via speaker identification or key identification). [Event Handler]

Output: App server returns initial page to device


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

Output: App server returns initial page to device including user preferences


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

Output: Device handles location information


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

Output: Touch screen detects and processes input


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

Output: ASR Server receives request and establishes connection


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

Output: ASR Server processes speech and returns results to device


Input: [User Action/External Input] User confirms destination [Action on Device] Device performs ASR Processing locally. Upon confirmation, destination info is sent to app server [Event Description] HTTP Request is sent to app server (includes current location and destination information) [Resulting Action] Device processes results and updates graphical display with route and directions highlighting next step [Event Handler]

Output: App Server processes input and returns data to device


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

Output: Device processes location data and checks if location milestone is hit


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

Output: Device processes location data and determines that user is off course


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

Output: App Server processes input and returns data to device


Input: [User Action/External Input] Alert received on device based on traffic conditions [Action on Device] N/A [Event Description] Route_Change Alert [Resulting Action] User is informed of traffic conditions and asked whether route should be recalculated. [Event Handler]

Output: Device processes event and initiates dialog to determine if route should be recalculated


Input: [User Action/External Input] User requests recalculation of route based on current traffic conditions [Action on Device] Device performs ASR Processing locally. Upon confirmation, destination info is sent to app server [Event Description] HTTP Request is sent to app server (includes current location and destination information) [Resulting Action] Device processes results and updates graphical display with route and directions highlighting next step [Event Handler]

Output: App Server processes input and returns data to device


Input: [User Action/External Input] User presses button on steering wheel [Action on Device] Connection to ASR server is established [Event Description] Start_Listening Event [Resulting Action] User hears acknowledgement prompt for continuation, and "listening" icon appears on display [Event Handler]

Output: ASR Server receives request and establishes connection


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

Output: ASR Server processes speech and returns results to device


Input: [User Action/External Input] User confirms destination via a multiple interaction dialog to determine exact destination [Action on Device] Device executes dialog based on user responses (using local ASR Processing) and accesses app server as needed [Event Description] HTTP requests to app server for dialog and data specific to user response [Resulting Action] User interacts in a dialog and selects destination. User is asked whether this is a new destination [Event Handler]

Output: App server responds with appropriate dialog


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

Output: App Server processes input and returns data to device


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

Output: Service is initiated and GPS satellite detection begins


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

Output: Device executes authentication dialog using local ASR processing


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


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


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

Output: Device initiates connection to ASR server


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


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

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


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


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


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

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


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


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

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


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

Output: Connection to ASR server is established


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


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

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


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

Output: Devices sends updated destination information to app server


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

Output: false

Static Context Components for use-when Expressions


Input: [Component] In scope namespaces [Value]

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


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

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


Input: [Component] Default function namespace [Value]

Output: The standard function namespace


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

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


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


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


Input: [Component] In scope variables [Value]


Input: [Component] In scope functions [Value]

Output: The core functions defined in [Functions and Operators], together with the functions element-available, function-available, and system-property defined in this specification, plus an implementation-defined set of extension functions. Note that stylesheet functions are not included in the context, which means that the function function-available will return false in respect of such functions.


Input: [Component] In scope collations [Value]

Output: Implementation-defined


Input: [Component] Default collation [Value]

Output: The Unicode Codepoint Collation


Input: [Component] Base URI [Value]

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


Input: [Component] Statically known documents [Value]


Input: [Component] Statically known collections [Value]


Input: [Event Identifier] DOMFocusIn [Description] Occurs when an element receives focus. [DOM3 event category] UIEvent [Animation event name] focusin [Bubbling phase] Yes [Cancel -able] No [uDOM interface]

Output: UIEvent


Input: [Event Identifier] DOMFocusOut [Description] Occurs when an element loses focus. [DOM3 event category] UIEvent [Animation event name] focusout [Bubbling phase] Yes [Cancel -able] No [uDOM interface]

Output: UIEvent


Input: [Event Identifier] DOMActivate [Description] Occurs when an element is activated, for instance, through a mouse click or a keypress. [DOM3 event category] UIEvent [Animation event name] activate [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface]

Output: UIEvent


Input: [Event Identifier] click [Description] Occurs when the pointing device button is clicked over an element. A click is defined as a mousedown and mouseup over the same screen location. The sequence of these events is: mousedown, mouseup, click. If multiple clicks occur at the same screen location, the sequence repeats with the detail attribute incrementing with each repetition. [DOM3 event category] MouseEvent [Animation event name] click [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface]

Output: MouseEvent


Input: [Event Identifier] mousedown [Description] Occurs when the pointing device button is pressed over an element. [DOM3 event category] MouseEvent [Animation event name] mousedown [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface]

Output: MouseEvent


Input: [Event Identifier] mouseup [Description] Occurs when the pointing device button is released over an element. [DOM3 event category] MouseEvent [Animation event name] mouseup [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface]

Output: MouseEvent


Input: [Event Identifier] mouseover [Description] Occurs when the pointing device is moved onto an element. [DOM3 event category] MouseEvent [Animation event name] mouseover [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface]

Output: MouseEvent


Input: [Event Identifier] mousemove [Description] Occurs when the pointing device is moved while it is over an element. [DOM3 event category] MouseEvent [Animation event name] mousemove [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface]

Output: MouseEvent


Input: [Event Identifier] mouseout [Description] Occurs when the pointing device is moved away from an element. [DOM3 event category] MouseEvent [Animation event name] mouseout [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface]

Output: MouseEvent


Input: [Event Identifier] textInput [Description] One or more characters have been entered. [DOM3 event category] TextEvent [Animation event name] none [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface]

Output: TextEvent


Input: [Event Identifier] keydown [Description] A key is pressed down. (The normative definition of this event is the description in the DOM3 Events specification.) [DOM3 event category] KeyboardEvent [Animation event name] none [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface]

Output: KeyboardEvent


Input: [Event Identifier] keyup [Description] A key is released. (The normative definition of this event is the description in the DOM3 Events specification.) [DOM3 event category] KeyboardEvent [Animation event name] none [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface]

Output: KeyboardEvent


Input: [Event Identifier] load [Description] The event is triggered at the point at which the user agent finishes loading the element and any dependent resources (such as images, style sheets, or scripts). In the case the element references a script, the event will be raised only after an attempt to interpret the script has been made. Dependent resources that fail to load will not prevent this event from firing if the element that referenced them is still accessible via the DOM unless they are designated as externalResourcesRequired. The event is independent of the means by which the element was added to DOM tree. [DOM3 event category] BasicEvent [Animation event name] load [Bubbling phase] No [Cancel -able] No [uDOM interface]

Output: Event


Input: [Event Identifier] SVGLoad [Description] This event is deprecated and is for backwards compatibility only, see notes below. This event is sent at the same time as the load event, but the load event must be sent before the SVGLoad event. [DOM3 event category] none [Animation event name] none [Bubbling phase] No [Cancel -able] No [uDOM interface]

Output: Event


Input: [Event Identifier] resize [Description] Occurs when a document view is being resized. This event is only applicable to 'svg' elements and is dispatched after the resize operation has taken place. The target of the event is the 'svg' element. [DOM3 event category] BasicEvent [Animation event name] resize [Bubbling phase] Yes [Cancel -able] No [uDOM interface]

Output: Event


Input: [Event Identifier] SVGResize [Description] This event is deprecated and is for backwards compatibility only, see notes below. This event is sent at the same time as the resize event, but the resize event must be sent before the SVGResize event. [DOM3 event category] none [Animation event name] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface]

Output: Event


Input: [Event Identifier] scroll [Description] Occurs when a document view is being shifted along the X or Y or both axis, either through a direct user interaction or any change on the currentTranslate property available on SVGSVGElement interface. This event is only applicable to 'svg' elements and is dispatched after the shift modification has taken place. The target of the event is the 'svg' element. [DOM3 event category] BasicEvent [Animation event name] scroll [Bubbling phase] Yes [Cancel -able] No [uDOM interface]

Output: Event


Input: [Event Identifier] SVGScroll [Description] This event is deprecated and is for backwards compatibility only, see notes below. This event is sent at the same time as the scroll event, but the scroll event must be sent before the SVGScroll event. [DOM3 event category] none [Animation event name] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface]

Output: Event


Input: [Event Identifier] SVGZoom [Description] Occurs when the zoom level of a document view is being changed, either through a direct user interaction or any change to the currentScale property available on SVGSVGElement interface. This event is only applicable to 'svg' elements and is dispatched after the zoom level modification has taken place. The target of the event is the 'svg' element. [DOM3 event category] none [Animation event name] zoom [Bubbling phase] No [Cancel -able] No [uDOM interface]

Output: Event


Input: [Event Identifier] SVGRotate [Description] Occurs when the rotation of a document view is being changed, either through a direct user interaction or any change to the currentRotate property available on SVGSVGElement interface. This event is only applicable to 'svg' elements and is dispatched after the rotation modification has taken place. The target of the event is the 'svg' element. [DOM3 event category] none [Animation event name] rotate [Bubbling phase] No [Cancel -able] No [uDOM interface]

Output: Event


Input: [Event Identifier] beginEvent [Description] Occurs when a Timed Element begins. For details, see the description of the Events and event model in SMIL 2.1. [DOM3 event category] none [Animation event name] beginEvent [Bubbling phase] Yes [Cancel -able] No [uDOM interface]

Output: TimeEvent


Input: [Event Identifier] endEvent [Description] Occurs when a Timed Element ends. For details, see the description of the Events and event model in SMIL 2.1. [DOM3 event category] none [Animation event name] endEvent [Bubbling phase] Yes [Cancel -able] No [uDOM interface]

Output: TimeEvent


Input: [Event Identifier] repeatEvent [Description] Occurs when a Timed Element repeats. It is raised each time the element repeats, after the first iteration. For details, see the description of the Events and event model in SMIL 2.1. [DOM3 event category] none [Animation event name] repeatEvent [Bubbling phase] Yes [Cancel -able] No [uDOM interface]

Output: TimeEvent


Input: [Event Identifier] SVGMousewheel [Description] Occurs when a rotational input device has been activated. [DOM3 event category] MouseEvent [Animation event name] none [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface]

Output: WheelEvent


Input: [Event Identifier] SVGPreload [Description] A load operation has begun. [DOM3 event category] none [Animation event name] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface]

Output: ProgressEvent


Input: [Event Identifier] SVGLoadProgress [Description] Progress has occurred in loading a given resource. [DOM3 event category] none [Animation event name] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface]

Output: ProgressEvent


Input: [Event Identifier] SVGPostload [Description] A load operation has completed. [DOM3 event category] none [Animation event name] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface]

Output: ProgressEvent


Input: [Event Identifier] SVGTimer [Description] Occurs when the specified timer interval has elapsed for a timer. This event is triggered only by 'running' timers in the current global execution context of the SVG document (i.e. for timers which have been instantiated via the SVGGlobal interface and started via the start() method of the Timer interface). The target of the event is the 'timer' object itself. The event processing is limited to the target phase. [DOM3 event category] none [Animation event name] none [Bubbling phase] No [Cancel -able] No [uDOM interface]

Output: Event


Input: [Event Identifier] SVGConnectionConnected [Description] Occurs when a connection has been established. No context information is available. [DOM3 event category] none [Animation event name] none [Bubbling phase] No [Cancel -able] No [uDOM interface]

Output: ConnectionEvent


Input: [Event Identifier] SVGConnectionClosed [Description] Occurs when a connection has been closed. No context information is available [DOM3 event category] none [Animation event name] none [Bubbling phase] No [Cancel -able] No [uDOM interface]

Output: ConnectionEvent


Input: [Event Identifier] SVGConnectionError [Description] Occurs when an error happens during the lifetime of a connection. Additional context information is available in the errorCode field. [DOM3 event category] none [Animation event name] none [Bubbling phase] No [Cancel -able] No [uDOM interface]

Output: ConnectionEvent


Input: [Event Identifier] SVGConnectionDataSent [Description] Occurs when data has been successfully transmitted. No context information is available. [DOM3 event category] none [Animation event name] none [Bubbling phase] No [Cancel -able] No [uDOM interface]

Output: ConnectionEvent


Input: [Event Identifier] SVGConnectionDataReceived [Description] Occurs when data has been received on the connection. Additional context information is available on the receivedData field. [DOM3 event category] none [Animation event name] none [Bubbling phase] No [Cancel -able] No [uDOM interface]

Output: ConnectionEvent


Input: [Event Identifier] DOMFocusIn [Description] Occurs when an element receives focus. [DOM3 event category] UIEvent [Animation event name] focusin [Cancel -able] No [uDOM interface] UIEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] DOMFocusOut [Description] Occurs when an element loses focus. [DOM3 event category] UIEvent [Animation event name] focusout [Cancel -able] No [uDOM interface] UIEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] DOMActivate [Description] Occurs when an element is activated, for instance, through a mouse click or a keypress. [DOM3 event category] UIEvent [Animation event name] activate [Cancel -able] Yes [uDOM interface] UIEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] click [Description] Occurs when the pointing device button is clicked over an element. A click is defined as a mousedown and mouseup over the same screen location. The sequence of these events is: mousedown, mouseup, click. If multiple clicks occur at the same screen location, the sequence repeats with the detail attribute incrementing with each repetition. [DOM3 event category] MouseEvent [Animation event name] click [Cancel -able] Yes [uDOM interface] MouseEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] mousedown [Description] Occurs when the pointing device button is pressed over an element. [DOM3 event category] MouseEvent [Animation event name] mousedown [Cancel -able] Yes [uDOM interface] MouseEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] mouseup [Description] Occurs when the pointing device button is released over an element. [DOM3 event category] MouseEvent [Animation event name] mouseup [Cancel -able] Yes [uDOM interface] MouseEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] mouseover [Description] Occurs when the pointing device is moved onto an element. [DOM3 event category] MouseEvent [Animation event name] mouseover [Cancel -able] Yes [uDOM interface] MouseEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] mousemove [Description] Occurs when the pointing device is moved while it is over an element. [DOM3 event category] MouseEvent [Animation event name] mousemove [Cancel -able] Yes [uDOM interface] MouseEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] mouseout [Description] Occurs when the pointing device is moved away from an element. [DOM3 event category] MouseEvent [Animation event name] mouseout [Cancel -able] Yes [uDOM interface] MouseEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] textInput [Description] One or more characters have been entered. [DOM3 event category] TextEvent [Animation event name] none [Cancel -able] Yes [uDOM interface] TextEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] keydown [Description] A key is pressed down. (The normative definition of this event is the description in the DOM3 Events specification.) [DOM3 event category] KeyboardEvent [Animation event name] none [Cancel -able] Yes [uDOM interface] KeyboardEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] keyup [Description] A key is released. (The normative definition of this event is the description in the DOM3 Events specification.) [DOM3 event category] KeyboardEvent [Animation event name] none [Cancel -able] Yes [uDOM interface] KeyboardEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] load [Description] The event is triggered at the point at which the user agent finishes loading the element and any dependent resources (such as images, style sheets, or scripts). In the case the element references a script, the event will be raised only after an attempt to interpret the script has been made. Dependent resources that fail to load will not prevent this event from firing if the element that referenced them is still accessible via the DOM unless they are designated as externalResourcesRequired. The event is independent of the means by which the element was added to DOM tree. [DOM3 event category] BasicEvent [Animation event name] load [Cancel -able] No [uDOM interface] Event [Bubbling phase]

Output: No


Input: [Event Identifier] SVGLoad [Description] This event is deprecated and is for backwards compatibility only, see notes below. This event is sent at the same time as the load event, but the load event must be sent before the SVGLoad event. [DOM3 event category] none [Animation event name] none [Cancel -able] No [uDOM interface] Event [Bubbling phase]

Output: No


Input: [Event Identifier] resize [Description] Occurs when a document view is being resized. This event is only applicable to 'svg' elements and is dispatched after the resize operation has taken place. The target of the event is the 'svg' element. [DOM3 event category] BasicEvent [Animation event name] resize [Cancel -able] No [uDOM interface] Event [Bubbling phase]

Output: Yes


Input: [Event Identifier] SVGResize [Description] This event is deprecated and is for backwards compatibility only, see notes below. This event is sent at the same time as the resize event, but the resize event must be sent before the SVGResize event. [DOM3 event category] none [Animation event name] none [Cancel -able] No [uDOM interface] Event [Bubbling phase]

Output: Yes


Input: [Event Identifier] scroll [Description] Occurs when a document view is being shifted along the X or Y or both axis, either through a direct user interaction or any change on the currentTranslate property available on SVGSVGElement interface. This event is only applicable to 'svg' elements and is dispatched after the shift modification has taken place. The target of the event is the 'svg' element. [DOM3 event category] BasicEvent [Animation event name] scroll [Cancel -able] No [uDOM interface] Event [Bubbling phase]

Output: Yes


Input: [Event Identifier] SVGScroll [Description] This event is deprecated and is for backwards compatibility only, see notes below. This event is sent at the same time as the scroll event, but the scroll event must be sent before the SVGScroll event. [DOM3 event category] none [Animation event name] none [Cancel -able] No [uDOM interface] Event [Bubbling phase]

Output: Yes


Input: [Event Identifier] SVGZoom [Description] Occurs when the zoom level of a document view is being changed, either through a direct user interaction or any change to the currentScale property available on SVGSVGElement interface. This event is only applicable to 'svg' elements and is dispatched after the zoom level modification has taken place. The target of the event is the 'svg' element. [DOM3 event category] none [Animation event name] zoom [Cancel -able] No [uDOM interface] Event [Bubbling phase]

Output: No


Input: [Event Identifier] SVGRotate [Description] Occurs when the rotation of a document view is being changed, either through a direct user interaction or any change to the currentRotate property available on SVGSVGElement interface. This event is only applicable to 'svg' elements and is dispatched after the rotation modification has taken place. The target of the event is the 'svg' element. [DOM3 event category] none [Animation event name] rotate [Cancel -able] No [uDOM interface] Event [Bubbling phase]

Output: No


Input: [Event Identifier] beginEvent [Description] Occurs when a Timed Element begins. For details, see the description of the Events and event model in SMIL 2.1. [DOM3 event category] none [Animation event name] beginEvent [Cancel -able] No [uDOM interface] TimeEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] endEvent [Description] Occurs when a Timed Element ends. For details, see the description of the Events and event model in SMIL 2.1. [DOM3 event category] none [Animation event name] endEvent [Cancel -able] No [uDOM interface] TimeEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] repeatEvent [Description] Occurs when a Timed Element repeats. It is raised each time the element repeats, after the first iteration. For details, see the description of the Events and event model in SMIL 2.1. [DOM3 event category] none [Animation event name] repeatEvent [Cancel -able] No [uDOM interface] TimeEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] SVGMousewheel [Description] Occurs when a rotational input device has been activated. [DOM3 event category] MouseEvent [Animation event name] none [Cancel -able] Yes [uDOM interface] WheelEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] SVGPreload [Description] A load operation has begun. [DOM3 event category] none [Animation event name] none [Cancel -able] No [uDOM interface] ProgressEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] SVGLoadProgress [Description] Progress has occurred in loading a given resource. [DOM3 event category] none [Animation event name] none [Cancel -able] No [uDOM interface] ProgressEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] SVGPostload [Description] A load operation has completed. [DOM3 event category] none [Animation event name] none [Cancel -able] No [uDOM interface] ProgressEvent [Bubbling phase]

Output: Yes


Input: [Event Identifier] SVGTimer [Description] Occurs when the specified timer interval has elapsed for a timer. This event is triggered only by 'running' timers in the current global execution context of the SVG document (i.e. for timers which have been instantiated via the SVGGlobal interface and started via the start() method of the Timer interface). The target of the event is the 'timer' object itself. The event processing is limited to the target phase. [DOM3 event category] none [Animation event name] none [Cancel -able] No [uDOM interface] Event [Bubbling phase]

Output: No


Input: [Event Identifier] SVGConnectionConnected [Description] Occurs when a connection has been established. No context information is available. [DOM3 event category] none [Animation event name] none [Cancel -able] No [uDOM interface] ConnectionEvent [Bubbling phase]

Output: No


Input: [Event Identifier] SVGConnectionClosed [Description] Occurs when a connection has been closed. No context information is available [DOM3 event category] none [Animation event name] none [Cancel -able] No [uDOM interface] ConnectionEvent [Bubbling phase]

Output: No


Input: [Event Identifier] SVGConnectionError [Description] Occurs when an error happens during the lifetime of a connection. Additional context information is available in the errorCode field. [DOM3 event category] none [Animation event name] none [Cancel -able] No [uDOM interface] ConnectionEvent [Bubbling phase]

Output: No


Input: [Event Identifier] SVGConnectionDataSent [Description] Occurs when data has been successfully transmitted. No context information is available. [DOM3 event category] none [Animation event name] none [Cancel -able] No [uDOM interface] ConnectionEvent [Bubbling phase]

Output: No


Input: [Event Identifier] SVGConnectionDataReceived [Description] Occurs when data has been received on the connection. Additional context information is available on the receivedData field. [DOM3 event category] none [Animation event name] none [Cancel -able] No [uDOM interface] ConnectionEvent [Bubbling phase]

Output: No


Input: [Final] Final [Description] The operation succeeded. [anyURI Name]

Output: Success

XML Key Management Specification (XKMS 2.0)


Input: [Final] Final [Description] The service does not support the protocol version specified in the request. [anyURI Name]

Output: VersionMismatch

XML Key Management Specification (XKMS 2.0)


Input: [Final] Final [Description] An error occurred that was due to the message sent by the sender. [anyURI Name]

Output: Sender

XML Key Management Specification (XKMS 2.0)


Input: [Final] Final [Description] An error occurred at the receiver. [anyURI Name]

Output: Receiver

XML Key Management Specification (XKMS 2.0)


Input: [Final] Not Final [Description] The service has not acted on the request. In order for the request to be acted upon the request MUST be represented with the specified nonce in accordance with the two-phase protocol. [anyURI Name]

Output: Represent

XML Key Management Specification (XKMS 2.0)


Input: [Final] Not Final [Description] The request has been accepted for processing and the service will return the result asynchronously. [anyURI Name]

Output: Pending

XML Key Management Specification (XKMS 2.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

Table 2.2.2: Terms for entity Action used with Duty


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: [Event Identifier] DOMFocusIn [DOM3 event category] UIEvent [Animation event name] focusin [Bubbling phase] Yes [Cancel -able] No [uDOM interface] UIEvent [Description]

Output: Occurs when an element receives focus.


Input: [Event Identifier] DOMFocusOut [DOM3 event category] UIEvent [Animation event name] focusout [Bubbling phase] Yes [Cancel -able] No [uDOM interface] UIEvent [Description]

Output: Occurs when an element loses focus.


Input: [Event Identifier] DOMActivate [DOM3 event category] UIEvent [Animation event name] activate [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] UIEvent [Description]

Output: Occurs when an element is activated, for instance, through a mouse click or a keypress.


Input: [Event Identifier] click [DOM3 event category] MouseEvent [Animation event name] click [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] MouseEvent [Description]

Output: Occurs when the pointing device button is clicked over an element. A click is defined as a mousedown and mouseup over the same screen location. The sequence of these events is: mousedown, mouseup, click. If multiple clicks occur at the same screen location, the sequence repeats with the detail attribute incrementing with each repetition.


Input: [Event Identifier] mousedown [DOM3 event category] MouseEvent [Animation event name] mousedown [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] MouseEvent [Description]

Output: Occurs when the pointing device button is pressed over an element.


Input: [Event Identifier] mouseup [DOM3 event category] MouseEvent [Animation event name] mouseup [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] MouseEvent [Description]

Output: Occurs when the pointing device button is released over an element.


Input: [Event Identifier] mouseover [DOM3 event category] MouseEvent [Animation event name] mouseover [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] MouseEvent [Description]

Output: Occurs when the pointing device is moved onto an element.


Input: [Event Identifier] mousemove [DOM3 event category] MouseEvent [Animation event name] mousemove [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] MouseEvent [Description]

Output: Occurs when the pointing device is moved while it is over an element.


Input: [Event Identifier] mouseout [DOM3 event category] MouseEvent [Animation event name] mouseout [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] MouseEvent [Description]

Output: Occurs when the pointing device is moved away from an element.


Input: [Event Identifier] textInput [DOM3 event category] TextEvent [Animation event name] none [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] TextEvent [Description]

Output: One or more characters have been entered.


Input: [Event Identifier] keydown [DOM3 event category] KeyboardEvent [Animation event name] none [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] KeyboardEvent [Description]

Output: A key is pressed down. (The normative definition of this event is the description in the DOM3 Events specification.)


Input: [Event Identifier] keyup [DOM3 event category] KeyboardEvent [Animation event name] none [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] KeyboardEvent [Description]

Output: A key is released. (The normative definition of this event is the description in the DOM3 Events specification.)


Input: [Event Identifier] load [DOM3 event category] BasicEvent [Animation event name] load [Bubbling phase] No [Cancel -able] No [uDOM interface] Event [Description]

Output: The event is triggered at the point at which the user agent finishes loading the element and any dependent resources (such as images, style sheets, or scripts). In the case the element references a script, the event will be raised only after an attempt to interpret the script has been made. Dependent resources that fail to load will not prevent this event from firing if the element that referenced them is still accessible via the DOM unless they are designated as externalResourcesRequired. The event is independent of the means by which the element was added to DOM tree.


Input: [Event Identifier] SVGLoad [DOM3 event category] none [Animation event name] none [Bubbling phase] No [Cancel -able] No [uDOM interface] Event [Description]

Output: This event is deprecated and is for backwards compatibility only, see notes below. This event is sent at the same time as the load event, but the load event must be sent before the SVGLoad event.


Input: [Event Identifier] resize [DOM3 event category] BasicEvent [Animation event name] resize [Bubbling phase] Yes [Cancel -able] No [uDOM interface] Event [Description]

Output: Occurs when a document view is being resized. This event is only applicable to 'svg' elements and is dispatched after the resize operation has taken place. The target of the event is the 'svg' element.


Input: [Event Identifier] SVGResize [DOM3 event category] none [Animation event name] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface] Event [Description]

Output: This event is deprecated and is for backwards compatibility only, see notes below. This event is sent at the same time as the resize event, but the resize event must be sent before the SVGResize event.


Input: [Event Identifier] scroll [DOM3 event category] BasicEvent [Animation event name] scroll [Bubbling phase] Yes [Cancel -able] No [uDOM interface] Event [Description]

Output: Occurs when a document view is being shifted along the X or Y or both axis, either through a direct user interaction or any change on the currentTranslate property available on SVGSVGElement interface. This event is only applicable to 'svg' elements and is dispatched after the shift modification has taken place. The target of the event is the 'svg' element.


Input: [Event Identifier] SVGScroll [DOM3 event category] none [Animation event name] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface] Event [Description]

Output: This event is deprecated and is for backwards compatibility only, see notes below. This event is sent at the same time as the scroll event, but the scroll event must be sent before the SVGScroll event.


Input: [Event Identifier] SVGZoom [DOM3 event category] none [Animation event name] zoom [Bubbling phase] No [Cancel -able] No [uDOM interface] Event [Description]

Output: Occurs when the zoom level of a document view is being changed, either through a direct user interaction or any change to the currentScale property available on SVGSVGElement interface. This event is only applicable to 'svg' elements and is dispatched after the zoom level modification has taken place. The target of the event is the 'svg' element.


Input: [Event Identifier] SVGRotate [DOM3 event category] none [Animation event name] rotate [Bubbling phase] No [Cancel -able] No [uDOM interface] Event [Description]

Output: Occurs when the rotation of a document view is being changed, either through a direct user interaction or any change to the currentRotate property available on SVGSVGElement interface. This event is only applicable to 'svg' elements and is dispatched after the rotation modification has taken place. The target of the event is the 'svg' element.


Input: [Event Identifier] beginEvent [DOM3 event category] none [Animation event name] beginEvent [Bubbling phase] Yes [Cancel -able] No [uDOM interface] TimeEvent [Description]

Output: Occurs when a Timed Element begins. For details, see the description of the Events and event model in SMIL 2.1.


Input: [Event Identifier] endEvent [DOM3 event category] none [Animation event name] endEvent [Bubbling phase] Yes [Cancel -able] No [uDOM interface] TimeEvent [Description]

Output: Occurs when a Timed Element ends. For details, see the description of the Events and event model in SMIL 2.1.


Input: [Event Identifier] repeatEvent [DOM3 event category] none [Animation event name] repeatEvent [Bubbling phase] Yes [Cancel -able] No [uDOM interface] TimeEvent [Description]

Output: Occurs when a Timed Element repeats. It is raised each time the element repeats, after the first iteration. For details, see the description of the Events and event model in SMIL 2.1.


Input: [Event Identifier] SVGMousewheel [DOM3 event category] MouseEvent [Animation event name] none [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] WheelEvent [Description]

Output: Occurs when a rotational input device has been activated.


Input: [Event Identifier] SVGPreload [DOM3 event category] none [Animation event name] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface] ProgressEvent [Description]

Output: A load operation has begun.


Input: [Event Identifier] SVGLoadProgress [DOM3 event category] none [Animation event name] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface] ProgressEvent [Description]

Output: Progress has occurred in loading a given resource.


Input: [Event Identifier] SVGPostload [DOM3 event category] none [Animation event name] none [Bubbling phase] Yes [Cancel -able] No [uDOM interface] ProgressEvent [Description]

Output: A load operation has completed.


Input: [Event Identifier] SVGTimer [DOM3 event category] none [Animation event name] none [Bubbling phase] No [Cancel -able] No [uDOM interface] Event [Description]

Output: Occurs when the specified timer interval has elapsed for a timer. This event is triggered only by 'running' timers in the current global execution context of the SVG document (i.e. for timers which have been instantiated via the SVGGlobal interface and started via the start() method of the Timer interface). The target of the event is the 'timer' object itself. The event processing is limited to the target phase.


Input: [Event Identifier] SVGConnectionConnected [DOM3 event category] none [Animation event name] none [Bubbling phase] No [Cancel -able] No [uDOM interface] ConnectionEvent [Description]

Output: Occurs when a connection has been established. No context information is available.


Input: [Event Identifier] SVGConnectionClosed [DOM3 event category] none [Animation event name] none [Bubbling phase] No [Cancel -able] No [uDOM interface] ConnectionEvent [Description]

Output: Occurs when a connection has been closed. No context information is available


Input: [Event Identifier] SVGConnectionError [DOM3 event category] none [Animation event name] none [Bubbling phase] No [Cancel -able] No [uDOM interface] ConnectionEvent [Description]

Output: Occurs when an error happens during the lifetime of a connection. Additional context information is available in the errorCode field.


Input: [Event Identifier] SVGConnectionDataSent [DOM3 event category] none [Animation event name] none [Bubbling phase] No [Cancel -able] No [uDOM interface] ConnectionEvent [Description]

Output: Occurs when data has been successfully transmitted. No context information is available.


Input: [Event Identifier] SVGConnectionDataReceived [DOM3 event category] none [Animation event name] none [Bubbling phase] No [Cancel -able] No [uDOM interface] ConnectionEvent [Description]

Output: Occurs when data has been received on the connection. Additional context information is available on the receivedData field.


Input: [Event Identifier] DOMFocusIn [Description] Occurs when an element receives focus. [Animation event name] focusin [Bubbling phase] Yes [Cancel -able] No [uDOM interface] UIEvent [DOM3 event category]

Output: UIEvent


Input: [Event Identifier] DOMFocusOut [Description] Occurs when an element loses focus. [Animation event name] focusout [Bubbling phase] Yes [Cancel -able] No [uDOM interface] UIEvent [DOM3 event category]

Output: UIEvent


Input: [Event Identifier] DOMActivate [Description] Occurs when an element is activated, for instance, through a mouse click or a keypress. [Animation event name] activate [Bubbling phase] Yes [Cancel -able] Yes [uDOM interface] UIEvent [DOM3 event category]

Output: UIEvent