Input: [Description] Apps should not be vulnerable to common web vulnerabilities when granted significant privileges [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications] Non-browser security context: may be additional restrictions on HTML/JavaScript [Requirement]

Output: Immunity to browser-based threats

System Applications WG: Security Model - W3C Wiki


Input: [Description] Ability to grant trust for certain highly sensitive privileges (such as phone dialing) may be restricted at the OS level to specific trusted parties [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications] Different 'levels' apply to SysApps - possibly 'roles' [Requirement]

Output: Pre-installed app permissions

System Applications WG: Security Model - W3C Wiki


Input: [Description] Ability for a system application to access (read and write) files outside of that application's sandboxed storage area. [Source] Mailing list: http://lists.w3.org/Archives/Public/public-sysapps/2012Nov/0003.html [Implications] Need to provide both sandboxed and non-sandboxed storage [Requirement]

Output: Access to files outside owned by the platform

System Applications WG: Security Model - W3C Wiki


Input: [Member name] Compaq [Patent declaration] None declared [License statement] http://lists.w3.org/Archives/Member/patent-issues/1999JanMar/0005.html [good standing] no [License Summary]

Output: Royalty-Free

Summary of SMIL 2.0 Patent Statements from SYMM WG members


Input: [Member name] CSELT [Patent declaration] None declared [License statement] http://lists.w3.org/Archives/Team/symm-review/1999JanMar/0000.html [good standing] no [License Summary]

Output: No licence


Input: [Member name] CWI [Patent declaration] None declared [License statement] http://lists.w3.org/Archives/Team/symm-review/1999JanMar/0003.html [good standing] yes [License Summary]

Output: No licence


Input: [Member name] GLOCOM [Patent declaration] None declared [License statement] http://lists.w3.org/Archives/Team/symm-review/1999AprJun/0000.html [good standing] no [License Summary]

Output: No licence


Input: [Member name] IBM [Patent declaration] Possible Patent declared [License statement] http://lists.w3.org/Archives/Member/patent-issues/2001AprJun/0023.html [good standing] yes [License Summary]

Output: RAND


Input: [Member name] INRIA [Patent declaration] None declared [License statement] http://lists.w3.org/Archives/Team/symm-review/1999JanMar/0004.html [good standing] yes [License Summary]

Output: No licence


Input: [Member name] Intel [Patent declaration] None declared [License statement] http://lists.w3.org/Archives/Member/patent-issues/2001JanMar/0040.html [good standing] yes [License Summary]

Output: Royalty-Free


Input: [Member name] Macromedia [Patent declaration] Possible Patent declared [License statement] http://lists.w3.org/Archives/Member/patent-issues/2001AprJun/0025.html [good standing] yes [License Summary]

Output: Royalty-Free


Input: [Member name] Microsoft [Patent declaration] None declared [License statement] http://lists.w3.org/Archives/Member/patent-issues/2001AprJun/0024.html [good standing] yes [License Summary]

Output: Royalty-Free


Input: [Member name] Netscape/AOL [Patent declaration] None declared [License statement] http://lists.w3.org/Archives/Team/symm-review/2000AprJun/0000.html [good standing] no [License Summary]

Output: No licence


Input: [Member name] Nokia [Patent declaration] None declared [License statement] http://lists.w3.org/Archives/Team/symm-review/1999JulSep/0000.html [good standing] no [License Summary]

Output: No licence


Input: [Member name] Oratrix [Patent declaration] None declared [License statement] http://lists.w3.org/Archives/Team/symm-review/2001AprJun/0000.html [good standing] yes [License Summary]

Output: No licence


Input: [Member name] Panasonic (Matsushita) [Patent declaration] None declared [License statement] http://lists.w3.org/Archives/Member/patent-issues/2001AprJun/0015.html [good standing] yes [License Summary]

Output: Royalty-Free


Input: [Member name] Web3D Consortium [Patent declaration] None declared [License statement] http://lists.w3.org/Archives/Team/symm-review/2000JanMar/0001.html [good standing] no [License Summary]

Output: No licence


Input: [Member name] Philips [Patent declaration] None declared [License statement] http://lists.w3.org/Archives/Member/symm/2000Dec/0115.html [good standing] yes [License Summary]

Output: RAND


Input: [Member name] RealNetworks [Patent declaration] None declared [License statement] http://lists.w3.org/Archives/Member/patent-issues/2001JanMar/0029.html [good standing] yes [License Summary]

Output: Royalty-Free


Input: [Member name] WGBH * [Patent declaration] None declared [good standing] yes [License Summary]

Output: No licence


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

Table 2.2.2: Terms for entity Action used with Duty


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] ensureExclusivity [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] nextPolicy [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Event Type] abort [Sync / Async] Sync [Bubbling phase] No [Trusted event target types] Element [DOM interface] Event [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] blur [Sync / Async] Sync [Bubbling phase] No [Trusted event target types] Element [DOM interface] FocusEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] click [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [DOM interface] MouseEvent [Default Action] DOMActivate event [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] compositionstart [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [DOM interface] CompositionEvent [Default Action] Show a text composition system candidate window [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] compositionupdate [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [DOM interface] CompositionEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] compositionend [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [DOM interface] CompositionEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] dblclick [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [DOM interface] MouseEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMActivate Warning! Deprecated [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [DOM interface] UIEvent [Default Action] none [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMAttrModified Warning! Deprecated [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [DOM interface] MutationEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMCharacterDataModified Warning! Deprecated [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Text, Comment, CDATASection, ProcessingInstruction [DOM interface] MutationEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMFocusIn Warning! Deprecated [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [DOM interface] FocusEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMFocusOut Warning! Deprecated [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [DOM interface] FocusEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMNodeInserted Warning! Deprecated [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element, Attr, Text, Comment, CDATASection, DocumentType, EntityReference, ProcessingInstruction [DOM interface] MutationEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMNodeInsertedIntoDocument Warning! Deprecated [Sync / Async] Sync [Bubbling phase] No [Trusted event target types] Element, Attr, Text, Comment, CDATASection, DocumentType, EntityReference, ProcessingInstruction [DOM interface] MutationEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMNodeRemoved Warning! Deprecated [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element, Attr, Text, Comment, CDATASection, DocumentType, EntityReference, ProcessingInstruction [DOM interface] MutationEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMNodeRemovedFromDocument Warning! Deprecated [Sync / Async] Sync [Bubbling phase] No [Trusted event target types] Element, Attr, Text, Comment, CDATASection, DocumentType, EntityReference, ProcessingInstruction [DOM interface] MutationEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMSubtreeModified Warning! Deprecated [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] defaultView, Document, DocumentFragment, Element, Attr [DOM interface] MutationEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] error [Sync / Async] Async [Bubbling phase] No [Trusted event target types] Element [DOM interface] Event [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] focus [Sync / Async] Sync [Bubbling phase] No [Trusted event target types] Element [DOM interface] FocusEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] focusin [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [DOM interface] FocusEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] focusout [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [DOM interface] FocusEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] keydown [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Document, Element [DOM interface] KeyboardEvent [Default Action] Varies: keypress event; launch text composition system; blur and focus events; DOMActivate event; other event [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] keypress [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Document, Element [DOM interface] KeyboardEvent [Default Action] Varies: launch text composition system; blur and focus events; DOMActivate event; other event [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] keyup [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Document, Element [DOM interface] KeyboardEvent [Default Action] none [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] load [Sync / Async] Async [Bubbling phase] No [Trusted event target types] defaultView, Document, Element [DOM interface] Event [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] mousedown [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [DOM interface] MouseEvent [Default Action] Varies: start a drag/drop operation; start a text selection; start a scroll/pan interaction (in combination with the middle mouse button, if supported) [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] mouseenter [Sync / Async] Sync [Bubbling phase] No [Trusted event target types] Element [DOM interface] MouseEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] mouseleave [Sync / Async] Sync [Bubbling phase] No [Trusted event target types] Element [DOM interface] MouseEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] mousemove [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [DOM interface] MouseEvent [Default Action] none [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] mouseout [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [DOM interface] MouseEvent [Default Action] none [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] mouseover [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [DOM interface] MouseEvent [Default Action] none [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] mouseup [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [DOM interface] MouseEvent [Default Action] Invoke a context menu (in combination with the right mouse button, if supported) [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] resize [Sync / Async] Sync [Bubbling phase] No [Trusted event target types] defaultView, Document [DOM interface] UIEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] scroll [Sync / Async] Async [Bubbling phase] No / Yes [Trusted event target types] defaultView, Document, Element [DOM interface] UIEvent [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] select [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [DOM interface] Event [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] unload [Sync / Async] Sync [Bubbling phase] No [Trusted event target types] defaultView, Document, Element [DOM interface] Event [Default Action] none [Cancelable]

Output: No

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] wheel [Sync / Async] Async [Bubbling phase] Yes [Trusted event target types] defaultView, Document, Element [DOM interface] WheelEvent [Default Action] Scroll (or zoom) the document [Cancelable]

Output: Yes

Document Object Model (DOM) Level 3 Events Specification


Input: [Identifier] absolutePosition [Comment] For example, JPEG image must be positioned at 100×100 pixel location. This may be used to express [PLUS] semantics. [Semantics]

Output: A point defined with absolute coordinates

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

Table 2.3.1: Terms for the attribute “name” of the entity Constraint


Input: [Identifier] absoluteSize [Comment] For example, JPEG image must be reproduced onto an area no larger than A0. This may be used to express [PLUS] semantics. [Semantics]

Output: The absolute dimension that the Asset may be resized

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] count [Comment] Should be a positive integer. [Semantics]

Output: The numeric count indicating the number of times the corresponding entity may be exercised

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] dateTime [Comment] Date and Time value must conform to [ISO-8601] as represented in [W3CXMLSCHEMA]. The use of Timezone information is strongly recommended. [Semantics]

Output: The date (and optional time and timezone) representing a point in time or period

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] fileFormat [Comment] For example, this may be used to express [PLUS] semantics; only JPEG image may be distributed. [Semantics]

Output: The file format applicable to the Asset

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] industry [Comment] For example, publishing, financial. [Semantics]

Output: The defined industry sector applicable to the asset usage

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] language [Comment] For example, this may be used to express [PLUS] semantics; JPEG image may only be reproduced with Spanish text. Must use [BCP-47] codes. [Semantics]

Output: The natural language applicable to the asset usage

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] deliveryChannel [Comment] For example, the asset may be distributed only on mobile networks. [Semantics]

Output: The delivery channel used for storing or communicating the asset

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] elapsedTime [Comment] The start of the period is when the action is first exercised. [Semantics]

Output: A period of time in which the policy action can be exercised.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] event [Comment] For example, asset may be used at the “FIFA World Cup” only. To express events related to undertaking Duties, a specific event value has been defined: policyUsage – the time period whilst the policy is being exercised This will enable constraints to be expressed such as “event lt o:policyUsage” indicating before the policy is exercised. [Semantics]

Output: Specification of a defined event applicable to the asset usage

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] media [Comment] For example, electronic, print, advertising, marketing. This may be used to express [PLUS] semantics. [Semantics]

Output: The media type in which the asset may be used

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] meteredTime [Comment] Value must conform to [ISO-8601] as represented in [W3CXMLSCHEMA]. For example “P30H” indicates a 30 hour period. [Semantics]

Output: The maximum period of metered usage time

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] payAmount [Comment] The dataType attribute may be used to indicate the type of the value (eg decimal) and the unit attribute to indicate the currency. May be used for compensation duties. [Semantics]

Output: The value of the financial payment

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] percentage [Comment] A numeric value from 0 to 100. For example, extract a maximum of 50% of the asset [Semantics]

Output: The amount (as a percentage) of the action applicable to the asset

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] product [Comment] For example, this may be used to express [PLUS] semantics; images may only be reproduced in the XYZ Magazine. [Semantics]

Output: The specified Product or Service name

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] purpose [Comment] For example, educational use. [P3P] Purpose values may also be used. [Semantics]

Output: Specification of a defined purpose applicable to the asset usage

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] recipient [Comment] The right operand must identify one or more specific parties or categories of party [Semantics]

Output: The party that receives the result of the Action on the Asset

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] relativePosition [Comment] For example, this may be used to express [PLUS] semantics; JPEG image must be positioned at the Top of the Page. [Semantics]

Output: A point defined with reference to another position

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] relativeSize [Comment] For example, this may be used to express [PLUS] semantics; JPEG image resized to maximum of 200%. [Semantics]

Output: The relative dimension that the Asset may be resized

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] resolution [Comment] For example, may be printed at 1200dpi. [Semantics]

Output: The resolution at which the asset may be used

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] spatial [Comment] The code value and code source must be represented. For example, the ISO-3166 Country Codes and the Getty Thesaurus of Geographic Names. A URI should be used to represent this value. [Semantics]

Output: A code representing a geospatial area

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] timeInterval [Comment] Interval value must conform to [ISO-8601] as represented in [W3CXMLSCHEMA]. For example, “P7D” indicates a 7 day period. [Semantics]

Output: Recurring period of time in which the usage may be exercised

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] systemDevice [Comment] For example, identifiable via the CPU or unique hardware address. [Semantics]

Output: An identifiable computing system

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] version [Comment] For example, Single Paperback, or Multiple Issues. This may be used to express [PLUS] semantics. [Semantics]

Output: The scope of versions for the asset

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] virtualLocation [Comment] For example, an Internet domain or IP address range [Semantics]

Output: Specification of a digital locale

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Additive?] yes ['set'] yes ['animate Color'] no ['animate Transform'] no ['animate']

Output: yes


Input: [Additive?] yes ['set'] yes ['animate Color'] yes ['animate Transform'] no [Notes] Only RGB color values are additive. ['animate']

Output: yes


Input: [Additive?] no ['set'] no ['animate Color'] no ['animate Transform'] no ['animate']

Output: no


Input: [Additive?] no ['set'] yes ['animate Color'] no ['animate Transform'] no ['animate']

Output: yes


Input: [Additive?] yes ['set'] no ['animate Color'] no ['animate Transform'] yes ['animate']

Output: no


Input: [Basic data type] All other animatable attributes and properties [Additive?] no ['set'] yes ['animate Color'] no ['animate Transform'] no ['animate']

Output: yes


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

Output: For Users

OWL 2 Web Ontology Language Document Overview


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

Output: Core Specification

OWL 2 Web Ontology Language Document Overview


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

Output: Core Specification

OWL 2 Web Ontology Language Document Overview


Input: [Part] 4 [Document] Direct Semantics defines the meaning of OWL 2 ontologies in terms of a model-theoretic semantics. [Type]

Output: Core Specification

OWL 2 Web Ontology Language Document Overview


Input: [Part] 5 [Document] RDF-Based Semantics defines the meaning of OWL 2 ontologies via an extension of the RDF Semantics. [Type]

Output: Core Specification

OWL 2 Web Ontology Language Document Overview


Input: [Part] 6 [Document] Conformance provides requirements for OWL 2 tools and a set of test cases to help determine conformance. [Type]

Output: Core Specification

OWL 2 Web Ontology Language Document Overview


Input: [Part] 7 [Document] Profiles defines three sub-languages of OWL 2 that offer important advantages in particular applications scenarios. [Type]

Output: Specification

OWL 2 Web Ontology Language Document Overview


Input: [Part] 8 [Document] OWL 2 Primer provides an approachable introduction to OWL 2, including orientation for those coming from other disciplines. [Type]

Output: For Users

OWL 2 Web Ontology Language Document Overview


Input: [Part] 9 [Document] OWL 2 New Features and Rationale provides an overview of the main new features of OWL 2 and motivates their inclusion in the language. [Type]

Output: For Users

OWL 2 Web Ontology Language Document Overview


Input: [Part] 10 [Document] OWL 2 Quick Reference Guide provides a brief guide to the constructs of OWL 2, noting the changes from OWL 1. [Type]

Output: For Users

OWL 2 Web Ontology Language Document Overview


Input: [Part] 11 [Document] XML Serialization defines an XML syntax for exchanging OWL 2 ontologies, suitable for use with XML tools like schema-based editors and XQuery/XPath. [Type]

Output: Specification

OWL 2 Web Ontology Language Document Overview


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

Output: Specification

OWL 2 Web Ontology Language Document Overview


Input: [Part] 13 [Document] Data Range Extension: Linear Equations (WG Note) specifies an optional extension to OWL 2 which supports advanced constraints on the values of properties. [Type]

Output: Specification

OWL 2 Web Ontology Language Document Overview


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 composed of only name tokens as defined in XML 1.0 [XML]. [Attribute Type]

Output: NMTOKEN


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

Output: NMTOKENS


Input: [Definition] Sequence of one or more digits ([0-9]) [Attribute Type]

Output: NUMBER


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

Output: The name of the event.

XPath Expressions Module - W3C XForms Group Wiki (Public)


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

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

XPath Expressions Module - W3C XForms Group Wiki (Public)


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

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

XPath Expressions Module - W3C XForms Group Wiki (Public)


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

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

XPath Expressions Module - W3C XForms Group Wiki (Public)


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

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

XPath Expressions Module - W3C XForms Group Wiki (Public)


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

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

XPath Expressions Module - W3C XForms Group Wiki (Public)


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

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

XPath Expressions Module - W3C XForms Group Wiki (Public)


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

Output: Description

Internationalization Tag Set (ITS) Version 2.0


Input: [0] terminology [2] The localization had â€œPen Driveâ€ when corporate terminology specified that â€œUSB Stickâ€ was to be used. The localization text inconsistently used "Start" and "Begin". A text renders the Hungarian term recsegÅ‘Ã©k as â€œbuzzer bridgeâ€ in English to translate (a literal translation), but the term used in English should be â€œwedge block,â€ as specified in a terminology list supplied to the translator. [3] S or T [4] This value MUST NOT be used for simple typographical errors or word choice not related to defined terminologies. For example, a mistyping of â€œpinâ€ as â€œpenâ€ or the use of â€œimplyâ€ instead of â€œinferâ€ (mistaking two commonly confused words) would not count as terminology issues and should be categorized as either spelling errors or mistranslations, depending on the nature of the issue. Terminology refers only to cases where incorrect choices about terms (either formal or commonly defined in a domain) are involved. [1]

Output: An incorrect term or a term from the wrong domain was used or terms are used inconsistently.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] mistranslation [2] The English source reads "An ape succeeded in grasping a banana lying outside its cage with the help of a stick" but the Italian translation reads "l'ape riuscÃ¬ a prendere la banana posta tuori dall sua gabbia aiutandosi con un bastone" ("A bee succeeded...") [3] T [4] Issues related to translation of specific terms related to the domain or task-specific language should be categorized as terminology issues. [1]

Output: The content of the target mistranslates the content of the source.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] omission [2] One or more segments found in the source that should have been translated are missing in the target. [3] S or T [4] This type should not be used for missing whitespace or formatting codes, but instead should be reserved for linguistic content. [1]

Output: Necessary text has been omitted from the localization or source.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] untranslated [2] The source segment reads "The Professor said to Smith that he would hear from his lawyer" but the Hungarian localization reads "A professzor azt modta Smithnek, hogy he would hear from his lawyer." [3] T [4] omission takes precedence over untranslated . Omissions are distinct in that they address cases where text is not present, while untranslated addresses cases where text has been carried from the source untranslated. [1]

Output: Content that should have been translated was left untranslated.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] addition [2] The translated text contains a note from the translator to himself to look up a term; the note should have been deleted but was not. [3] T [1]

Output: The translated text contains inappropriate additions.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] duplication [2] A section of the target text was inadvertently copied twice in a copy and paste operation. [3] T [1]

Output: Content has been duplicated improperly.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] inconsistency [2] The text states that an event happened in 1912 in one location but in another states that it happened in 1812. [3] S or T [1]

Output: The text is inconsistent with itself (NB: not for use with terminology inconsistency).

Internationalization Tag Set (ITS) Version 2.0


Input: [0] grammar [2] The text reads "The guidelines says that users should use a static grounding strap." [3] S or T [1]

Output: The text contains a grammatical error (including errors of syntax and morphology).

Internationalization Tag Set (ITS) Version 2.0


Input: [0] legal [2] The localized text is intended for use in Thailand but includes U.S. regulatory notices. A text translated into German contains comparative advertising claims that are not allowed by German law. [3] S or T [1]

Output: The text is legally problematic (e.g., it is specific to the wrong legal system).

Internationalization Tag Set (ITS) Version 2.0


Input: [0] register [2] A financia financial text in U.S. English refers to dollars as "bucks". [3] S or T [1]

Output: The text is written in the wrong linguistic register of uses slang or other language variants inappropriate to the text.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] locale-specific-content [2] A text translated for the Japanese market contains call center numbers in Texas and refers to special offers available only in the U.S. [3] S or T [4] Legally inappropriate material should be classified as legal . [1]

Output: The localization contains content that does not apply to the locale for which it was prepared.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] locale-violation [2] A text localized into German has dates in YYYY-MM-DD format instead of in DD.MM.YYYY. A text for the Irish market uses American-style foot and inch measurements instead of centimeters. A text intended for a U.S.-based audience uses U.K. spellings such as â€œcentreâ€ and â€œcolour.â€ [3] S or T [4] This category should be used for spelling errors only if they relate specifically to locale expectations (e.g., a text consitently uses British instead of U.S. spellings for a text intended for the U.S.). If these errors are not systematic (e.g., a text uses U.S. spellings but has a single instance of â€œcentreâ€), they should instead be counted as spelling errors. [1]

Output: Text violates norms for the intended locale.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] style [2] Company style guidelines dictates that all individuals be referred to as Mr. or Ms. with a family name, but the text refers to â€œJack Smithâ€. [3] S or T [1]

Output: The text contains stylistic errors.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] characters [2] A text should have a 'â€¢' but instead has a 'Â¥' sign. A text translated into German omits the umlauts over 'Ã¼', 'Ã¶', and 'Ã¤'. [3] S or T [1]

Output: The text contains characters that are garbled or incorrect or that are not used in the language in which the content appears.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] misspelling [2] A German text misspells the word "Zustellung" as "ZustellÃ¼ng". [3] S or T [1]

Output: The text contains a misspelling.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] typographical [2] An English text has the following sentence: "The man whom, we saw, was in the Military and carried it's insignias". [3] S or T [1]

Output: The text has typographical errors such as omitted/incorrect punctuation, incorrect capitalization, etc.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] formatting [2] Warnings in the text are supposed to be set in italic face, but instead appear in bold face. Margins of the text are narrower than specified. [3] S or T [1]

Output: The text is formatted incorrectly.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] inconsistent-entities [2] The name "Thaddeus Cahill" appears in an English source but is rendered as "TamaÅ¡ Cahill" in the Czech version. The date "February 9, 2007" appears in the source but the translated text has "2. September 2007". [3] S or T [1]

Output: The source and target text contain different named entities (dates, times, place names, individual names, etc.)

Internationalization Tag Set (ITS) Version 2.0


Input: [0] numbers [2] A source text states that an object is 120 cm long, but the target text says it is 129 cm. long. [3] S or T [4] Some tools may correct for differences in units of measurement to reduce false positives. [1]

Output: Numbers are inconsistent between source and target.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] markup [2] The source segment has five markup tags but the target has only two. An opening tag in the text is missing a closing tag. [3] S or T [1]

Output: There is an issue related to markup or a mismatch in markup between source and target.

Internationalization Tag Set (ITS) Version 2.0


Input: [0] pattern-problem [2] The tool disallows the regular expression pattern ['"â€â€™][\.,] but the translated text contains "A leading â€œexpertâ€, a political hack, claimed otherwise." [3] S or T [1]

Output: The text fails to match a pattern that defines allowable content (or matches one that defines non-allowable content).

Internationalization Tag Set (ITS) Version 2.0


Input: [0] whitespace [2] A source segment starts with six space characters but the corresponding target segment has two non-breaking spaces at the start. The text uses a run of 12 space characters instead of a tab character to align numbers in a table. Two space characters appear after a period even though only a single period should be used. [3] S or T [1]

Output: There is a mismatch in whitespace between source and target content. content or the text violates specific rules related to the use of whitespace..

Internationalization Tag Set (ITS) Version 2.0


Input: [0] internationalization [2] A line of programming code has embedded language-specific strings. A user interface element leaves no room for text expansion. A form allows only for U.S.-style postal addresses and expects five digit U.S. ZIP codes. [3] S or T [4] There are many kinds of internationalization issues. This category is therefore very heterogeneous in what it can refer to. [1]

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

Internationalization Tag Set (ITS) Version 2.0


Input: [0] length [2] The translation of a segment is five times as long as the source. [3] T or S [4] What constitutes a "significant" difference in length is determined by the model referred to in the locQualityIssueProfileRef . [1]

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

Internationalization Tag Set (ITS) Version 2.0


Input: [0] uncategorized [2] A new version of a tool returns information on an issue that has not been previously checked and that is not yet classified. [3] S or T [4] This category has two uses: A tool can use it to pass through quality data from another tool in cases where the issues from the other tool are not classified (for example, a localization quality assurance tool interfaces with a third-party grammar checker). A tool's issues are not yet assigned to categories, and, until an updated assignment is made, they may be listed as uncategorized . In this case it is recommended that issues be assigned to appropriate categories as soon as possible since uncategorized does not foster interoperability. [1]

Output: The issue has not been categorized.

Internationalization Tag Set (ITS) Version 2.0


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

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

Internationalization Tag Set (ITS) Version 2.0


Input: [Process] contentQuote [Definition]

Output: indicates that a quoting or pricing is requested, not to perform the job


Input: [Process] contentAlignment [Definition]

Output: in case the content is to add to a Translation Memory (?)


Input: [Process] contentL10N [Definition]

Output: localize (cultural and formal adaptation to local) the content


Input: [Process] contentI18N [Definition]

Output: internationalize the content


Input: [Process] contentDtp [Definition]

Output: desktop publishing of content


Input: [Process] contentSubtitle [Definition]

Output: subtitling of content


Input: [Process] contentVoiceOver [Definition]

Output: voice over of content


Input: [Process] sourceRewrite [Definition]

Output: rewrite the source content


Input: [Process] hTranslate [Definition]

Output: human translation


Input: [Process] mTranslate [Definition]

Output: machine translation


Input: [Process] hTranscreate [Definition]

Output: human transcreation


Input: [Process] posteditQA [Definition]

Output: human postediting of mTranslate


Input: [Process] reviewQA [Definition]

Output: human review for quality assurance only the target text, without the source text (see UNE 15038 “review”), by an expert for instance


Input: [Process] reviseQA [Definition]

Output: human revision for quality assurance examining the translation and comparing source and target (see UNE 15038 “revision”)


Input: [Process] proofQA [Definition]

Output: human checking of proofs before publishing for quality assurance (see UNE15038 “proofreading”)


Input: [Process] sourceReview [Definition]

Output: review the source content


Input: [Process] sourceTranscribe [Definition]

Output: transcribe the source content


Input: [Process] sourceTransliteration [Definition]

Output: transliterate the source content


Input: [Process] importCMSWF [Definition]

Output: ready for importing of delivery in the CMS


Input: [Process] validationCMSWF [Definition]

Output: ready for validation of delivery in the CMS


Input: [Process] publishCMSWF [Definition]

Output: ready for publishing of delivery in the CMS


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: [Event Type] abort [Sync / Async] Sync [Bubbling phase] No [Trusted event target types] Element [Cancelable] No [Default Action] none [DOM interface]

Output: Event

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] blur [Sync / Async] Sync [Bubbling phase] No [Trusted event target types] Element [Cancelable] No [Default Action] none [DOM interface]

Output: FocusEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] click [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [Cancelable] Yes [Default Action] DOMActivate event [DOM interface]

Output: MouseEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] compositionstart [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [Cancelable] Yes [Default Action] Show a text composition system candidate window [DOM interface]

Output: CompositionEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] compositionupdate [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [Cancelable] No [Default Action] none [DOM interface]

Output: CompositionEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] compositionend [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [Cancelable] No [Default Action] none [DOM interface]

Output: CompositionEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] dblclick [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [Cancelable] No [Default Action] none [DOM interface]

Output: MouseEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMActivate Warning! Deprecated [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [Cancelable] Yes [Default Action] none [DOM interface]

Output: UIEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMAttrModified Warning! Deprecated [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [Cancelable] No [Default Action] none [DOM interface]

Output: MutationEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMCharacterDataModified Warning! Deprecated [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Text, Comment, CDATASection, ProcessingInstruction [Cancelable] No [Default Action] none [DOM interface]

Output: MutationEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMFocusIn Warning! Deprecated [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [Cancelable] No [Default Action] none [DOM interface]

Output: FocusEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMFocusOut Warning! Deprecated [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [Cancelable] No [Default Action] none [DOM interface]

Output: FocusEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMNodeInserted Warning! Deprecated [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element, Attr, Text, Comment, CDATASection, DocumentType, EntityReference, ProcessingInstruction [Cancelable] No [Default Action] none [DOM interface]

Output: MutationEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMNodeInsertedIntoDocument Warning! Deprecated [Sync / Async] Sync [Bubbling phase] No [Trusted event target types] Element, Attr, Text, Comment, CDATASection, DocumentType, EntityReference, ProcessingInstruction [Cancelable] No [Default Action] none [DOM interface]

Output: MutationEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMNodeRemoved Warning! Deprecated [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element, Attr, Text, Comment, CDATASection, DocumentType, EntityReference, ProcessingInstruction [Cancelable] No [Default Action] none [DOM interface]

Output: MutationEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMNodeRemovedFromDocument Warning! Deprecated [Sync / Async] Sync [Bubbling phase] No [Trusted event target types] Element, Attr, Text, Comment, CDATASection, DocumentType, EntityReference, ProcessingInstruction [Cancelable] No [Default Action] none [DOM interface]

Output: MutationEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] DOMSubtreeModified Warning! Deprecated [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] defaultView, Document, DocumentFragment, Element, Attr [Cancelable] No [Default Action] none [DOM interface]

Output: MutationEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] error [Sync / Async] Async [Bubbling phase] No [Trusted event target types] Element [Cancelable] No [Default Action] none [DOM interface]

Output: Event

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] focus [Sync / Async] Sync [Bubbling phase] No [Trusted event target types] Element [Cancelable] No [Default Action] none [DOM interface]

Output: FocusEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] focusin [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [Cancelable] No [Default Action] none [DOM interface]

Output: FocusEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] focusout [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [Cancelable] No [Default Action] none [DOM interface]

Output: FocusEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] keydown [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Document, Element [Cancelable] Yes [Default Action] Varies: keypress event; launch text composition system; blur and focus events; DOMActivate event; other event [DOM interface]

Output: KeyboardEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] keypress [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Document, Element [Cancelable] Yes [Default Action] Varies: launch text composition system; blur and focus events; DOMActivate event; other event [DOM interface]

Output: KeyboardEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] keyup [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Document, Element [Cancelable] Yes [Default Action] none [DOM interface]

Output: KeyboardEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] load [Sync / Async] Async [Bubbling phase] No [Trusted event target types] defaultView, Document, Element [Cancelable] No [Default Action] none [DOM interface]

Output: Event

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] mousedown [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [Cancelable] Yes [Default Action] Varies: start a drag/drop operation; start a text selection; start a scroll/pan interaction (in combination with the middle mouse button, if supported) [DOM interface]

Output: MouseEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] mouseenter [Sync / Async] Sync [Bubbling phase] No [Trusted event target types] Element [Cancelable] No [Default Action] none [DOM interface]

Output: MouseEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] mouseleave [Sync / Async] Sync [Bubbling phase] No [Trusted event target types] Element [Cancelable] No [Default Action] none [DOM interface]

Output: MouseEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] mousemove [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [Cancelable] Yes [Default Action] none [DOM interface]

Output: MouseEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] mouseout [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [Cancelable] Yes [Default Action] none [DOM interface]

Output: MouseEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] mouseover [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [Cancelable] Yes [Default Action] none [DOM interface]

Output: MouseEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] mouseup [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [Cancelable] Yes [Default Action] Invoke a context menu (in combination with the right mouse button, if supported) [DOM interface]

Output: MouseEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] resize [Sync / Async] Sync [Bubbling phase] No [Trusted event target types] defaultView, Document [Cancelable] No [Default Action] none [DOM interface]

Output: UIEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] scroll [Sync / Async] Async [Bubbling phase] No / Yes [Trusted event target types] defaultView, Document, Element [Cancelable] No [Default Action] none [DOM interface]

Output: UIEvent

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] select [Sync / Async] Sync [Bubbling phase] Yes [Trusted event target types] Element [Cancelable] No [Default Action] none [DOM interface]

Output: Event

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] unload [Sync / Async] Sync [Bubbling phase] No [Trusted event target types] defaultView, Document, Element [Cancelable] No [Default Action] none [DOM interface]

Output: Event

Document Object Model (DOM) Level 3 Events Specification


Input: [Event Type] wheel [Sync / Async] Async [Bubbling phase] Yes [Trusted event target types] defaultView, Document, Element [Cancelable] Yes [Default Action] Scroll (or zoom) the document [DOM interface]

Output: WheelEvent

Document Object Model (DOM) Level 3 Events Specification


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

Output: The Party is the issuer of the policy statement

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

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


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

Output: The Party is the recipient of the policy statement

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: The Party to be attributed

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: The Party to obtain consent from

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: The Party to be informed of all uses

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: The Party is the recipient of the compensation

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: The Party is the usage tracker

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: DISTINCT


Input: [Patterns] triple patterns [Query Forms] CONSTRUCT [Modifiers]

Output: REDUCED


Input: [Patterns] Basic graph patterns [Query Forms] DESCRIBE [Modifiers]

Output: PROJECT


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

Output: ORDER BY


Input: [Patterns] OPTIONAL [Modifiers]

Output: LIMIT


Input: [Patterns] UNION [Modifiers]

Output: OFFSET


Input: [Additive?] yes ['animate'] yes ['animate Color'] no ['animate Transform'] no ['set']

Output: yes


Input: [Additive?] yes ['animate'] yes ['animate Color'] yes ['animate Transform'] no [Notes] Only RGB color values are additive. ['set']

Output: yes


Input: [Additive?] no ['animate'] no ['animate Color'] no ['animate Transform'] no ['set']

Output: no


Input: [Additive?] no ['animate'] yes ['animate Color'] no ['animate Transform'] no ['set']

Output: yes


Input: [Additive?] yes ['animate'] no ['animate Color'] no ['animate Transform'] yes ['set']

Output: no


Input: [Basic data type] All other animatable attributes and properties [Additive?] no ['animate'] yes ['animate Color'] no ['animate Transform'] no ['set']

Output: yes


Input: [Requirement] Alarm API [Source] SysApps Charter [Description]

Output: Applications can create alarms, notifying users

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Contacts API [Source] SysApps Charter [Description]

Output: Apps can add, remove and edit contacts

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Messaging API [Source] SysApps Charter [Description]

Output: Apps can send, receive and view SMS

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Telephony API [Source] SysApps Charter [Description]

Output: Apps can access the telephony capabilities of the underlyling platform: dial a number, pick up a call, route to voicemail, access the call log

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Raw Sockets API [Source] SysApps Charter [Description]

Output: Apps can create, manipulate and listen for low-level TCP and UDP connections

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Supports many device form factors [Source] SysApps Charter [Implications] The security model can make no assumptions about how the device will be used or shared between people and cannot assume a particular process model. [Description]

Output: Supports a wide variety of devices including desktop & laptop computers, smart phones, tablets, TVs, cameras, and other connected devices

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] DAP API Support [Source] SysApps Charter [Implications] Either DAP APIs will need to change slightly in the systems context or the security model must allow for API-specific access controls [Description]

Output: All APIs defined by DAP should be accessible to system applications

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Minimal user prompting [Source] SysApps Charter [Implications] Some details of the expected user interactions may need to be specified in the security model or APIs [Description]

Output: Problems such as 'double prompting' should be avoided when integrating other APIs

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] HTML5 [Description]

Output: Applications consist of HTML, CSS and JavaScript

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Location [Description]

Output: Applications have access to geolocation data

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Communicate with other applications [Implications] Some kind of messaging will be supported [Description]

Output: Applications can communicate with other applications

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Communicate with pre-defined endpoints [Implications] Access remote domains will be possible [Description]

Output: Applications can communicate with pre-defined web addresses

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Valid across multiple platforms [Source] Compatibility of application packages [Description]

Output: Applications can run on any conformant platform, potentially including any device form factor

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Access control log [Source] webinos [Description]

Output: Allow access control decisions to be logged.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] API access rationale [Source] webinos [Description]

Output: Applications shall be able to explain why access to data or APIs is being requested.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Application capability restriction [Source] webinos [Description]

Output: Applications shall access only its specified device features, extensions and content.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Application intent [Source] webinos [Description]

Output: Applications shall specify its required functionality at install time or during updates.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Application isolation [Source] webinos [Description]

Output: Applications shall be isolated from each other.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Application policy approval [Source] webinos [Description]

Output: Changes to existing application intentions and permissions shall be approved by the end user.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Authenticity check [Source] webinos [Description]

Output: Before being installed or updated, origin authenticity and integrity checks shall be performed by the runtime

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Certifier list [Source] webinos [Description]

Output: The list of authorities that certified an application shall be viewable by end-users.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Confidential credentials storage [Source] webinos [Description]

Output: The webinos runtime shall support the confidential storage of user credentials.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Credentials access restriction [Source] webinos [Description]

Output: Access to credentials storage shall be limited to a specific user, a specific device and a set of applications.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Data management rationale [Source] webinos [Description]

Output: applications shall be able to explain how collected sensitive data will be managed.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Default policy [Source] webinos [Description]

Output: A default security and privacy policy shall exist an be enforced on each conformant runtime

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Device-identity binding [Source] webinos [Description]

Output: Personal devices shall be bound to their owner's identities.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Device-identity binding revokation [Source] webinos [Description]

Output: The binding between personal devices and owner's identity shall be revokable.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Hierarchical policy enforcement [Source] webinos [Description]

Output: Runtimes can enforce multiple access control rules written by multiple stakeholders in a hierarchy.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Secure cache [Source] webinos [Description]

Output: Data cached by a runtime shall be securely stored to prevent disclosure and tampering by unauthorised entitites.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Secure storage [Source] webinos [Description]

Output: Application data shall be securely stored to prevent disclosure and tampering by unauthorised entities.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Trusted application source [Source] webinos [Implications] Apps must have provenance data attached to them [Description]

Output: When installing or using an application for the first time, the runtime shall establish that the user trusts the source of the application.

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] App stores can revoke applications [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications] App permissions can be changed remotely [Description]

Output: "An app store needs to be able to approve an application, implying they can verify the permissions, integrity and authenticity of the app"

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] External trusted party can set app default permissions [Source] Extrapolated from B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications] The user is not the only source of access control decisions. this also suggests a need for conflict resolution. [Description]

Output: B2G: "App store must be able to set the default permissions for an app".

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Installation [Source] B2G, webinos [Description]

Output: Applications must be installed before executed

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Owner override [Source] B2G (user), webinos (user) [Implications] Access control settings must be changeable [Description]

Output: The device owner must be able to override app settings and permissions (this may not be the user, but a corporate, for example)

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] App privilege visibility [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications] There must be a standard way for applications to identify the permissions they have and lack [Description]

Output: Apps should be able to discover their privileges and degrade gracefully in a limited privilege environment

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Permission usability [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Description]

Output: Apps should be able to discover their privileges and degrade gracefully in a limited privilege environment

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Immunity to browser-based threats [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications] Non-browser security context: may be additional restrictions on HTML/JavaScript [Description]

Output: Apps should not be vulnerable to common web vulnerabilities when granted significant privileges

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Pre-installed app permissions [Source] B2G - https://wiki.mozilla.org/B2G_App_Security_Model [Implications] Different 'levels' apply to SysApps - possibly 'roles' [Description]

Output: Ability to grant trust for certain highly sensitive privileges (such as phone dialing) may be restricted at the OS level to specific trusted parties

System Applications WG: Security Model - W3C Wiki


Input: [Requirement] Access to files outside owned by the platform [Source] Mailing list: http://lists.w3.org/Archives/Public/public-sysapps/2012Nov/0003.html [Implications] Need to provide both sandboxed and non-sandboxed storage [Description]

Output: Ability for a system application to access (read and write) files outside of that application's sandboxed storage area.

System Applications WG: Security Model - W3C Wiki


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

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


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

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


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

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


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

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


Input: [Notation] $i$ [Interpretation]

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


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

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


Input: [Identifier] Agreement [Semantics] Policy expressions that are formal contracts (or licenses) stipulating all the terms of usage and all the parties involved. [Comment]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] Offer [Semantics] Policy expressions that propose terms of usage from an Asset owner [Comment]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] Privacy [Semantics] Policy expressions that stipulate the terms of usage over personal information. [Comment]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] Request [Semantics] Policy expressions that propose terms of usage to an Asset owner [Comment]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] Set [Semantics] Policy expressions that consists of entities from the complete model [Comment]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] Ticket [Semantics] Policy expressions that stipulate the terms of usage and is redeemable by any Party who currently holds the Ticket in their possession [Comment]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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


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

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


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

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


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

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


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

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


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

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


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

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


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

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


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

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


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

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


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

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


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

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


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

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


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

Output: link role


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

Output: No role


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

Output: article role


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

Output: note role


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

Output: No role


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

Output: button role


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

Output: group role


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

Output: dialog role


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

Output: No role


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

Output: No role


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

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


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

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


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

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


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

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


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

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


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

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


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

Output: No role


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

Output: No role


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

Output: img role


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

Output: img role


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

Output: button role


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

Output: checkbox role


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

Output: button role


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

Output: radio role


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

Output: listitem role


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

Output: No role


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

Output: list role


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

Output: status role


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

Output: region role


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

Output: list role


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

Output: No role


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

Output: document role


Input: [Erratum] E1 [Bugzilla] 4372 [Category] substantive [Description]

Output: This erratum places constraints on the type of string that is valid for the doctype-public attribute of xsl:output.


Input: [Erratum] E2 [Bugzilla] 4557 [Category] editorial [Description]

Output: This erratum corrects an editorial error concerning the number of phases of serialization.


Input: [Erratum] E3 [Bugzilla] 5066 [Category] editorial [Description]

Output: This erratum corrects an editorial error concerning the currently registered XHTML media types.


Input: [Erratum] E4 [Bugzilla] 5433 [Category] substantive [Description]

Output: This erratum clarifies how descendant elements of an XML island must be serialized according to the HTML output method.


Input: [Erratum] E5 [Bugzilla] 5439 [Category] substantive [Description]

Output: This erratum aligns the description of the effect of the include-content-type serialization parameter of the HTML output method with that of the XHTML output method.


Input: [Erratum] E6 [Bugzilla] 5458 [Category] substantive [Description]

Output: This erratum ensures that the sequence normalization process preserves any type annotations associated with nodes in the input sequence.


Input: [Erratum] E7 [Bugzilla] 5300 [Category] substantive [Description]

Output: This erratum clarifies how elements with empty content models are to be serialized under the HTML and XHTML output methods.


Input: [Erratum] E8 [Bugzilla] 5441 [Category] substantive [Description]

Output: This erratum ensures that Unicode normalization applies to all characters that might be adjacent in the serialized result produced by the text output method, including those that are in text nodes that are separated by element nodes in the data model instance.


Input: [Erratum] E9 [Bugzilla] 5993 [Category] substantive [Description]

Output: This erratum makes previously non-normative text that describes how the xhtml and html output methods must behave if the indent parameter has the value yes into normative text.


Input: [Erratum] E10 [Bugzilla] 6466 [Category] substantive [Description]

Output: This erratum specifies the syntactic constraints on the values of the doctype-public and doctype-system serialization parameters.


Input: [Erratum] E11 [Bugzilla] 6376 [Category] editorial [Description]

Output: This erratum makes clear which parts of the recommendation are not considered to be normative.


Input: [Attribute Type] CDATA [Definition]

Output: Character data


Input: [Attribute Type] ID [Definition]

Output: A document-unique identifier


Input: [Attribute Type] IDREF [Definition]

Output: A reference to a document-unique identifier


Input: [Attribute Type] IDREFS [Definition]

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


Input: [Attribute Type] NAME [Definition]

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


Input: [Attribute Type] NMTOKEN [Definition]

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


Input: [Attribute Type] NMTOKENS [Definition]

Output: One or more white space separated NMTOKEN values


Input: [Attribute Type] PCDATA [Definition]

Output: Processed character data


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] compensate [Semantics] The Assigner requires that the Assignee(s) compensates the Assigner (or other specified compensation Party) by some amount of value, if defined, for use of the Asset. [Comment]

Output: The compensation may use different types of things with a value: – the thing is expressed by the value (term) of the Constraint name – the value is expressed by operator, rightOperand, dataType and unit

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] inform [Semantics] The Assigner requires that the Assignee(s) inform(s) the Assigner or an informed Party that an action has been performed on or in relation to the Asset. [Comment]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] obtainConsent [Semantics] The Assigner requires that the Assignee(s) obtains explicit consent from the Assigner or a consenting Party to perform the requested action in relation to the Asset. [Comment]

Output: Used as a Duty to ensure that the Assigner or a Party is authorized to approve such actions on a case-by-case basis. May link to a Party with the role function “consentingParty”.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] uninstall [Semantics] The Assigner requires that the Assignee(s) unload(s) and delete(s) the computer program Asset from a storage device and disable(s) its readiness for operation. [Comment]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [PREFIX] CONSTRUCT [2] DESCRIBE [3] ASK [BASE]

Output: SELECT


Input: [PREFIX] LIMIT [2] OFFSET [3] DISTINCT [4] REDUCED [BASE]

Output: ORDER BY


Input: [PREFIX] FROM NAMED [2] WHERE [BASE]

Output: FROM


Input: [PREFIX] OPTIONAL [2] UNION [3] FILTER [4] a [BASE]

Output: GRAPH


Input: [PREFIX] LANG [2] LANGMATCHES [3] DATATYPE [4] BOUND [5] sameTERM [BASE]

Output: STR


Input: [PREFIX] isIRI [2] isLITERAL [3] REGEX [4] true [5] false [BASE]

Output: isURI


Input: [Identifier] assigner [Semantics] The Party is the issuer of the policy statement [Comment]

Output: Must be supported.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] assignee [Semantics] The Party is the recipient of the policy statement [Comment]

Output: Must be supported.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] attributedParty [Semantics] The Party to be attributed [Comment]

Output: May be specified as part of the attribute action.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] consentingParty [Semantics] The Party to obtain consent from [Comment]

Output: May be specified as part of the obtainConsent action.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] informedParty [Semantics] The Party to be informed of all uses [Comment]

Output: May be specified as part of the inform action.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] compensatedParty [Semantics] The Party is the recipient of the compensation [Comment]

Output: May be specified as part of the compensate duty action.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] trackingParty [Semantics] The Party is the usage tracker [Comment]

Output: May be specified as part of the acceptTracking action.

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] eq [Semantics]

Output: The “Equals” operator indicating that a given value equals the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

Table 2.3.2: Terms for the attribute “operator” of the entity Constraint


Input: [Identifier] gt [Semantics]

Output: The “Greater Than” operator indicating that a given value is greater than the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] gteq [Semantics]

Output: The “Greater Than or Equal To” operator indicating that a given value is greater than or equal to the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] hasPart [Semantics]

Output: The “Has Part” operator indicating that a given value contains the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] isA [Semantics]

Output: The “Is A” operator indicating that a given value is an instance of the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] isAllOf [Semantics]

Output: The “Is All Of” operator indicating that a given value is all of the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] isAnyOf [Semantics]

Output: The “Is Any Of” operator indicating that a given value is any of the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] isNoneOf [Semantics]

Output: The “Is None Of” operator indicating that a given value is none of the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] isPartOf [Semantics]

Output: The “Is Part Of” operator indicating that a given value is contained by the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] lt [Semantics]

Output: The “Less Than” operator indicating that a given value is less than the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] lteq [Semantics]

Output: The “Less Than or Equal To” operator indicating that a given value is less than or equal to the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] neq [Semantics]

Output: The “Not Equal To” operator indicating that a given value is not equal to the rightOperand of the Constraint

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: For Users


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

Output: Core Specification


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

Output: Core Specification


Input: [Part] 4 [Document] Direct Semantics defines the meaning of OWL 2 ontologies in terms of a model-theoretic semantics. [Type]

Output: Core Specification