Input: [Event Type] pointermove [Sync/Async] Sync [Bubbles] Yes Document, Element [Event object interface] PointerEvent [Default Action] Varies: when the pointer is primary, all default actions of mousemove [Cancellable]

Output: Yes


Input: [Event Type] pointerover [Sync/Async] Sync [Bubbles] Yes Document, Element [Event object interface] PointerEvent [Default Action] Varies: when the pointer is primary, all default actions of mouseover [Cancellable]

Output: Yes


Input: [Event Type] pointerout [Sync/Async] Sync [Bubbles] Yes Document, Element [Event object interface] PointerEvent [Default Action] Varies: when the pointer is primary, all default actions of mouseout [Cancellable]

Output: Yes


Input: [Event Type] pointerenter [Sync/Async] Sync [Bubbles] No Document, Element [Event object interface] PointerEvent [Default Action] Varies: when the pointer is primary, all default actions of mouseenter [Cancellable]

Output: Yes


Input: [Event Type] pointerleave [Sync/Async] Sync [Bubbles] No Document, Element [Event object interface] PointerEvent [Default Action] Varies: when the pointer is primary, all default actions of mouseleave [Cancellable]

Output: Yes


Input: [Event Type] gotpointercapture [Sync/Async] Async [Bubbles] Yes Element [Event object interface] PointerEvent [Default Action] None [Cancellable]

Output: No


Input: [Event Type] lostpointercapture [Sync/Async] Async [Bubbles] Yes Element [Event object interface] PointerEvent [Default Action] None [Cancellable]

Output: No


Input: [Definition] Character data [Attribute Type]

Output: CDATA


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

Output: ID


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

Output: IDREF


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

Output: IDREFS


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

Output: NAME


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

Output: NMTOKEN


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

Output: NMTOKENS


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

Output: PCDATA


Input: [Event Type] pointerdown [Sync/Async] Sync [Bubbles] Yes [Cancellable] Yes Document, Element [Event object interface] PointerEvent [Default Action]

Output: Varies: when the pointer is primary, all default actions of the mousedown event


Input: [Event Type] pointerup [Sync/Async] Sync [Bubbles] Yes [Cancellable] Yes Document, Element [Event object interface] PointerEvent [Default Action]

Output: Varies: when the pointer is primary, all default actions of mouseup


Input: [Event Type] pointercancel [Sync/Async] Sync [Bubbles] Yes [Cancellable] Yes Document, Element [Event object interface] PointerEvent [Default Action]


Input: [Event Type] pointermove [Sync/Async] Sync [Bubbles] Yes [Cancellable] Yes Document, Element [Event object interface] PointerEvent [Default Action]

Output: Varies: when the pointer is primary, all default actions of mousemove


Input: [Event Type] pointerover [Sync/Async] Sync [Bubbles] Yes [Cancellable] Yes Document, Element [Event object interface] PointerEvent [Default Action]

Output: Varies: when the pointer is primary, all default actions of mouseover


Input: [Event Type] pointerout [Sync/Async] Sync [Bubbles] Yes [Cancellable] Yes Document, Element [Event object interface] PointerEvent [Default Action]

Output: Varies: when the pointer is primary, all default actions of mouseout


Input: [Event Type] pointerenter [Sync/Async] Sync [Bubbles] No [Cancellable] Yes Document, Element [Event object interface] PointerEvent [Default Action]

Output: Varies: when the pointer is primary, all default actions of mouseenter


Input: [Event Type] pointerleave [Sync/Async] Sync [Bubbles] No [Cancellable] Yes Document, Element [Event object interface] PointerEvent [Default Action]

Output: Varies: when the pointer is primary, all default actions of mouseleave


Input: [Event Type] gotpointercapture [Sync/Async] Async [Bubbles] Yes [Cancellable] No Element [Event object interface] PointerEvent [Default Action]


Input: [Event Type] lostpointercapture [Sync/Async] Async [Bubbles] Yes [Cancellable] No Element [Event object interface] PointerEvent [Default Action]


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

Output: The operation succeeded.

XML Key Management Specification (XKMS 2.0)


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

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

XML Key Management Specification (XKMS 2.0)


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

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

XML Key Management Specification (XKMS 2.0)


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

Output: An error occurred at the receiver.

XML Key Management Specification (XKMS 2.0)


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

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

XML Key Management Specification (XKMS 2.0)


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

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

XML Key Management Specification (XKMS 2.0)


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group

Table 2.2.2: Terms for entity Action used with Duty


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [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

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


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

Output: acceptTracking

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: attribute

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Assigner requires that the Assignee(s) compensates the Assigner (or other specified compensation Party) by some amount of value, if defined, for use of the Asset. [Comment] The compensation may use different types of things with a value: – the thing is expressed by the value (term) of the Constraint name – the value is expressed by operator, rightOperand, dataType and unit [Identifier]

Output: compensate

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: delete

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: ensureExclusivity

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: include

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Assigner requires that the Assignee(s) inform(s) the Assigner or an informed Party that an action has been performed on or in relation to the Asset. [Comment] May link to a Party with the role function “informedParty”. [Identifier]

Output: inform

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: nextPolicy

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Semantics] The Assigner requires that the Assignee(s) obtains explicit consent from the Assigner or a consenting Party to perform the requested action in relation to the Asset. [Comment] Used as a Duty to ensure that the Assigner or a Party is authorized to approve such actions on a case-by-case basis. May link to a Party with the role function “consentingParty”. [Identifier]

Output: obtainConsent

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: reviewPolicy

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: uninstall

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: watermark

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Definition] Character data [Attribute Type]

Output: CDATA


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

Output: ID


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

Output: IDREF


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

Output: IDREFS


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

Output: NAME


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

Output: NMTOKEN


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

Output: NMTOKENS


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

Output: PCDATA


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] ensureExclusivity [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Identifier] nextPolicy [Semantics]

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

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

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [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: [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: [Level] 1. [testability of specification]

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


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

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


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

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


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

Output: Same as above.


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

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


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

Output: Same as above


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

Output: Same as above


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

Output: Agreement

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Offer

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Privacy

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Request

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Set

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Ticket

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Agreement

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Offer

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Privacy

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Request

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Set

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


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

Output: Ticket

ODRL Version 2.1 Common Vocabulary | ODRL Community Group


Input: [Property] Directly Readable and Writable [XML+gzip] Yes [Notes]

Output: The XML format itself satisfies this property, but naturally any generic compression applied to a file format requires creating the intermediate form first.


Input: [Property] Compactness [XML+gzip] No [Notes]

Output: XML and gzip cannot take advantage of schema information, so this format fails in the Schema and Both classes. By definition, it succeeds in the Document class and fails in the Neither class (due to the different requirements, in the Neither class, it would have to be smaller than itself).


Input: [Property] Roundtrip Support [XML+gzip] Yes [Notes]

Output: The equivalence is exact in both cases.


Input: [Property] Generality [XML+gzip] No [Notes]

Output: The measurement value is 10/20.


Input: [Property] Format Version Identifier [XML+gzip] Yes [Notes]

Output: Both XML and gzip include an identifier in the header.


Input: [Property] Widespread Adoption [XML+gzip] Does Not Prevent [Notes]

Output: Both XML and gzip have been widely adopted and included in many protocol standards.


Input: [Name] event [Required] false [Attribute Constraints] This attribute is mandatory if "type" is 'scxml'. [Type] Value expression [Default Value] none [Description]

Output: A value expression which returns a character string that indicates the type of message being generated. See 8.3 Legal Data Values and Value Expressions for details. The message type may include alphanumeric characters and the "." (dot) character. The first character may not be a dot or a digit. Message type names are case-insensitive. If neither the event attribute or in-line content is specified, an error.fetch event will be thrown. If used in conjunction with the inline content, an error.fetch will be thrown.

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [Name] target [Required] false [Type] Value expression [Default Value] the current session [Valid Values] A valid target URL [Description]

Output: A value expression returning a unique identifier of the message target that the platform should send the event to. See 8.3 Legal Data Values and Value Expressions for details. If the special value '_internal' is specified, the event is added to the internal event queue of the current session. If no value is specified, the event is added to the external event queue of the current session.

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [Name] type [Required] false [Type] Value expression [Default Value] 'scxml' [Valid Values] Any value expression that evaluates to a string. [Description]

Output: A value expression which returns a character string that specifies the type of the message target. See 8.3 Legal Data Values and Value Expressions for details. Values defined by the specification are: scxml. See G SCXML Event I/O Processor for details. basichttp. See H Basic HTTP Event I/O Processor for details.

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [Name] id [Required] false [Attribute Constraints] This attribute may not occur with 'idlocation'. [Type] NMTOKEN [Default Value] none [Valid Values] Any valid token [Description]

Output: A string literal to be used as the identifier for this instance of . It is the author's responsibility to insure that it is unique.

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [Name] idlocation [Required] false [Attribute Constraints] This attribute may not occur with 'id'. [Type] Location expression [Default Value] none [Valid Values] Any valid location expression [Description]

Output: Any location expression evaluating to a data model location. See 8.2 Location Expressions for details. The location's value will be set to an internally generated unique identifier of type NMTOKEN to be associated with the message being sent.

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [Name] delay [Required] false [Attribute Constraints] This attribute may not be used with "target" '_internal'. [Type] Value expression [Default Value] '0s' [Valid Values] A value expression which returns a time designation as defined in CSS2 [CSS2] format [Description]

Output: The character string returned is interpreted as a time interval. The send tag will return immediately, but the message is not dispatched until the delay interval elapses. In this case, all arguments to send are evaluated when the send element is first processed, and not when the message is actually dispatched. Timers are useful for a wide variety of programming tasks, and can be implemented using this attribute. Note: The queue for messages events is maintained locally. Any messages waiting to be sent will be purged when the session that issued this request terminates.

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [Name] namelist [Required] false [Attribute Constraints] This attribute may not be specified in conjunction with the or elements. This attribute is supported only in profiles that contain the Data Module or the Script Module. [Type] List of location expressions [Default Value] none [Valid Values] List of data model locations [Description]

Output: A space-separated list of zero or more data model locations to be included with the message. See 8.2 Location Expressions for details.

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [Name] hints [Required] false [Type] Value expression [Default Value] none [Valid Values] A value expression. [Description]

Output: The data returned contains information which may be used by the implementing platform to optimize message transmission. The meaning of these hints is platform-specific.

State Chart XML (SCXML): State Machine Notation for Control Abstraction


Input: [State] Hidden [Data type] An arbitrary string [Control type] n/a [Keyword]

Output: hidden


Input: [State] Text [Data type] Text with no line breaks [Control type] Text field [Keyword]

Output: text


Input: [State] Search [Data type] Text with no line breaks [Control type] Search field [Keyword]

Output: search


Input: [State] Telephone [Data type] Text with no line breaks [Control type] A text field [Keyword]

Output: tel


Input: [State] URL [Data type] An absolute IRI [Control type] A text field [Keyword]

Output: url


Input: [State] E-mail [Data type] An e-mail address or list of e-mail addresses [Control type] A text field [Keyword]

Output: email


Input: [State] Password [Data type] Text with no line breaks (sensitive information) [Control type] Text field that obscures data entry [Keyword]

Output: password


Input: [State] Date and Time [Data type] A date and time (year, month, day, hour, minute, second, fraction of a second) with the time zone set to UTC [Control type] A date and time control [Keyword]

Output: datetime


Input: [State] Date [Data type] A date (year, month, day) with no time zone [Control type] A date control [Keyword]

Output: date


Input: [State] Month [Data type] A date consisting of a year and a month with no time zone [Control type] A month control [Keyword]

Output: month


Input: [State] Week [Data type] A date consisting of a week-year number and a week number with no time zone [Control type] A week control [Keyword]

Output: week


Input: [State] Time [Data type] A time (hour, minute, seconds, fractional seconds) with no time zone [Control type] A time control [Keyword]

Output: time


Input: [State] Local Date and Time [Data type] A date and time (year, month, day, hour, minute, second, fraction of a second) with no time zone [Control type] A date and time control [Keyword]

Output: datetime-local


Input: [State] Number [Data type] A numerical value [Control type] A text field or spinner control [Keyword]

Output: number


Input: [State] Range [Data type] A numerical value, with the extra semantic that the exact value is not important [Control type] A slider control or similar [Keyword]

Output: range


Input: [State] Color [Data type] An sRGB color with 8-bit red, green, and blue components [Control type] A color well [Keyword]

Output: color


Input: [State] Checkbox [Data type] A set of zero or more values from a predefined list [Control type] A checkbox [Keyword]

Output: checkbox


Input: [State] Radio Button [Data type] An enumerated value [Control type] A radio button [Keyword]

Output: radio


Input: [State] File Upload [Data type] Zero or more files each with a MIME type and optionally a file name [Control type] A label and a button [Keyword]

Output: file


Input: [State] Submit Button [Data type] An enumerated value, with the extra semantic that it must be the last value selected and initiates form submission [Control type] A button [Keyword]

Output: submit


Input: [State] Image Button [Data type] A coordinate, relative to a particular image's size, with the extra semantic that it must be the last value selected and initiates form submission [Control type] Either a clickable image, or a button [Keyword]

Output: image


Input: [State] Reset Button [Data type] n/a [Control type] A button [Keyword]

Output: reset


Input: [State] Button [Data type] n/a [Control type] A button [Keyword]

Output: button


Input: [Pattern] * [Meaning] Matches any element. [Described in section]

Output: Universal selector


Input: [Pattern] E [Meaning] Matches any E element. [Described in section]

Output: Type selectors


Input: [Pattern] A B [Meaning] Matches any B element that is a descendant of an A element. [Described in section]

Output: Descendant selectors


Input: [Pattern] A > B [Meaning] Matches any B element that is a child of an element A. [Described in section]

Output: Child selectors


Input: [Pattern] A:first-child [Meaning] Matches element A when A is the first child of some other element [Described in section]

Output: The :first-child pseudo-class


Input: [Pattern] E + F [Meaning] Matches any F element immediately preceded by an element E. [Described in section]

Output: Adjacent selectors


Input: [Pattern] E[foo] [Meaning] Matches any E element with the "foo" attribute set (whatever the value). [Described in section]

Output: Attribute selectors


Input: [Pattern] E[foo="warning"] [Meaning] Matches any E element whose "foo" attribute value is exactly equal to "warning". [Described in section]

Output: Attribute selectors


Input: [Pattern] E[foo~="warning"] [Meaning] Matches any E element whose "foo" attribute value is a list of space-separated of values, one of which is exactly equal to "warning". [Described in section]

Output: Attribute selectors


Input: [Pattern] DIV.warning [Meaning] HTML only. The same as DIV[class~="warning"]. [Described in section]

Output: The "class" attribute in HTML


Input: [Pattern] E#myid [Meaning] Matches any E element with the "id" attribute equal to "myid". [Described in section]

Output: ID selectors


Input: [Pattern] * [Described in section] Universal selector [Meaning]

Output: any element


Input: [Pattern] E [Described in section] Type element selector [Meaning]

Output: an element of type E


Input: [Pattern] E[foo] [Described in section] Attribute selectors [Meaning]

Output: an E element with the "foo" attribute set


Input: [Pattern] E[foo="warning"] [Described in section] Attribute selectors [Meaning]

Output: an E element whose "foo" attribute value is exactly equal to "warning"


Input: [Pattern] E[foo~="warning"] [Described in section] Attribute selectors [Meaning]

Output: an E element whose "foo" attribute value is a list of space-separated values, one of which is exactly equal to "warning"


Input: [Pattern] E[lang|="en"] [Described in section] Attribute selectors [Meaning]

Output: an E element whose "lang" attribute has a hyphen-separated list of values beginning (from the left) with "en"


Input: [Pattern] E:root [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, root of the document


Input: [Pattern] E:first-child [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, first child of its parent


Input: [Pattern] E:not-first-child [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, not the first child of its parent


Input: [Pattern] E:last-child [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, last child of its parent


Input: [Pattern] E:not-last-child [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, not the last child of its parent


Input: [Pattern] E:first-of-type [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, first sibling of its type


Input: [Pattern] E:not-first-of-type [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, not the first sibling of its type


Input: [Pattern] E:last-of-type [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, last sibling of its type


Input: [Pattern] E:not-last-of-type [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, not the last sibling of its type


Input: [Pattern] E:only-of-type [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, only sibling of its type


Input: [Pattern] E:not-only-of-type [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, not the only sibling of its type


Input: [Pattern] E:only-child [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, only child of its parent


Input: [Pattern] E:not-only-child [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, not the only child of its parent


Input: [Pattern] E:nth-child(n) [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, the n-th child of its parent


Input: [Pattern] E:nth-of-type(n) [Described in section] Structural pseudo-classes [Meaning]

Output: an E element, the n-th sibling of its type


Input: [Pattern] E:link E:visited [Described in section] The link pseudo-classes [Meaning]

Output: an E element being the source anchor of a hyperlink of which the target is not yet visited (:link) or already visited (:visited)


Input: [Pattern] E:active E:hover E:focus [Described in section] The user action pseudo-classes [Meaning]

Output: an E element during certain user actions


Input: [Pattern] E:target [Described in section] The target pseudo-class [Meaning]

Output: an E element being the target of the refering URI containing a fragment identifier


Input: [Pattern] E:lang(c) [Described in section] The :lang() pseudo-class [Meaning]

Output: an element of type E in (human) language c (the document language specifies how language is determined)


Input: [Pattern] E:subject [Described in section] The subject element pseudo-class [Meaning]

Output: an E element that is a subject of the selector the current simple selectors belong to


Input: [Pattern] E:first-line [Described in section] The :first-line pseudo-element [Meaning]

Output: the first formatted line of an E element


Input: [Pattern] E:first-letter [Described in section] The :first-letter pseudo-element [Meaning]

Output: the first formatted letter of an E element


Input: [Pattern] E:before [Described in section] The :before pseudo-element [Meaning]

Output: generated content before an E element


Input: [Pattern] E:after [Described in section] The :after pseudo-element [Meaning]

Output: generated content after an E element


Input: [Pattern] E.warning [Described in section] Class selectors [Meaning]

Output: HTML only. The same as E[class~="warning"].


Input: [Pattern] E#myid [Described in section] ID selectors [Meaning]

Output: an E element, its ID being equal to "myid".


Input: [Pattern] E"foo" [Described in section] Content selector [Meaning]

Output: an E element containing substring foo in its textual contents


Input: [Pattern] E F [Described in section] Descendant combinator [Meaning]

Output: an F element descendant of an E element


Input: [Pattern] E > F [Described in section] Child combinator [Meaning]

Output: an F element child of an element E


Input: [Pattern] E + F [Described in section] Direct adjacent combinator [Meaning]

Output: an F element immediately preceded by an element E


Input: [Pattern] E ~ F [Described in section] Indirect adjacent combinator [Meaning]

Output: an F element preceded by an element E


Input: [Pattern] * [Meaning] any element [Described in section]

Output: Universal selector


Input: [Pattern] E [Meaning] an element of type E [Described in section]

Output: Type element selector


Input: [Pattern] E[foo] [Meaning] an E element with the "foo" attribute set [Described in section]

Output: Attribute selectors


Input: [Pattern] E[foo="warning"] [Meaning] an E element whose "foo" attribute value is exactly equal to "warning" [Described in section]

Output: Attribute selectors


Input: [Pattern] E[foo~="warning"] [Meaning] an E element whose "foo" attribute value is a list of space-separated values, one of which is exactly equal to "warning" [Described in section]

Output: Attribute selectors


Input: [Pattern] E[lang|="en"] [Meaning] an E element whose "lang" attribute has a hyphen-separated list of values beginning (from the left) with "en" [Described in section]

Output: Attribute selectors


Input: [Pattern] E:root [Meaning] an E element, root of the document [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:first-child [Meaning] an E element, first child of its parent [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:not-first-child [Meaning] an E element, not the first child of its parent [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:last-child [Meaning] an E element, last child of its parent [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:not-last-child [Meaning] an E element, not the last child of its parent [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:first-of-type [Meaning] an E element, first sibling of its type [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:not-first-of-type [Meaning] an E element, not the first sibling of its type [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:last-of-type [Meaning] an E element, last sibling of its type [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:not-last-of-type [Meaning] an E element, not the last sibling of its type [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:only-of-type [Meaning] an E element, only sibling of its type [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:not-only-of-type [Meaning] an E element, not the only sibling of its type [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:only-child [Meaning] an E element, only child of its parent [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:not-only-child [Meaning] an E element, not the only child of its parent [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:nth-child(n) [Meaning] an E element, the n-th child of its parent [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:nth-of-type(n) [Meaning] an E element, the n-th sibling of its type [Described in section]

Output: Structural pseudo-classes


Input: [Pattern] E:link E:visited [Meaning] an E element being the source anchor of a hyperlink of which the target is not yet visited (:link) or already visited (:visited) [Described in section]

Output: The link pseudo-classes


Input: [Pattern] E:active E:hover E:focus [Meaning] an E element during certain user actions [Described in section]

Output: The user action pseudo-classes


Input: [Pattern] E:target [Meaning] an E element being the target of the refering URI containing a fragment identifier [Described in section]

Output: The target pseudo-class


Input: [Pattern] E:lang(c) [Meaning] an element of type E in (human) language c (the document language specifies how language is determined) [Described in section]

Output: The :lang() pseudo-class


Input: [Pattern] E:subject [Meaning] an E element that is a subject of the selector the current simple selectors belong to [Described in section]

Output: The subject element pseudo-class


Input: [Pattern] E:first-line [Meaning] the first formatted line of an E element [Described in section]

Output: The :first-line pseudo-element


Input: [Pattern] E:first-letter [Meaning] the first formatted letter of an E element [Described in section]

Output: The :first-letter pseudo-element


Input: [Pattern] E:before [Meaning] generated content before an E element [Described in section]

Output: The :before pseudo-element


Input: [Pattern] E:after [Meaning] generated content after an E element [Described in section]

Output: The :after pseudo-element


Input: [Pattern] E.warning [Meaning] HTML only. The same as E[class~="warning"]. [Described in section]

Output: Class selectors


Input: [Pattern] E#myid [Meaning] an E element, its ID being equal to "myid". [Described in section]

Output: ID selectors


Input: [Pattern] E"foo" [Meaning] an E element containing substring foo in its textual contents [Described in section]

Output: Content selector


Input: [Pattern] E F [Meaning] an F element descendant of an E element [Described in section]

Output: Descendant combinator


Input: [Pattern] E > F [Meaning] an F element child of an element E [Described in section]

Output: Child combinator


Input: [Pattern] E + F [Meaning] an F element immediately preceded by an element E [Described in section]

Output: Direct adjacent combinator


Input: [Pattern] E ~ F [Meaning] an F element preceded by an element E [Described in section]

Output: Indirect adjacent combinator


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

Output: archive


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

Output: content-length


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

Output: data


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

Output: declare


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

Output: standby


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

Output: type


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

Output: xml:base


Input: [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


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: [Details] an ECMAScript expression which returns the URI of the CCXML document to be fetched. [Attribute Name]

Output: next

Voice Browser Call Control: CCXML Version 1.0


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

Output: namelist

Voice Browser Call Control: CCXML Version 1.0


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

Output: method

Voice Browser Call Control: CCXML Version 1.0


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

Output: fetchid

Voice Browser Call Control: CCXML Version 1.0


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

Output: synch

Voice Browser Call Control: CCXML Version 1.0


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

Output: timeout

Voice Browser Call Control: CCXML Version 1.0


Input: [Description] The copyright element matches the schema. It contains one text element that does not have a language tag. This should be linked to a testable assertion in the spec. [Title]

Output: Valid copyright Element With One No Language Tagged text Element


Input: [Description] The copyright element matches the schema. It contains one text element that has a language tag. This should be linked to a testable assertion in the spec. [Title]

Output: Valid copyright Element With One Language Tagged text Element


Input: [Description] The copyright element matches the schema. One text element does not have a language tag. One text element has a language tag. This should be linked to a testable assertion in the spec. [Title]

Output: Valid copyright Element With Mixed text Element Language Tags 1


Input: [Description] The copyright element matches the schema. Two text elements have a language tags. This should be linked to a testable assertion in the spec. [Title]

Output: Valid copyright Element With Mixed text Element Language Tags 2


Input: [Description] The copyright element occurs more than once. This should be linked to a testable assertion in the spec. [Title]

Output: More Than One copyright Element


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

Output: No text Element in copyright Element


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

Output: Unknown Attribute in copyright Element


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

Output: Unknown Child Element in copyright Element


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

Output: Content in copyright Element


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

Output: Unknown Attribute in copyright Element text Element


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

Output: Unknown Child Element in copyright Element text Element


Input: [Name] name [Description] The form item variable in the dialog scope that will hold the recording. The name must be unique among form items in the form. If the name is not unique, then a badfetch error is thrown when the document is fetched. Note that how this variable is implemented may vary between platforms (although all platforms must support its behaviour behavior in and as described in this specification). [Required] Yes [Type]

Output: The name must conform to the variable naming conventions in (TODO).

Voice Extensible Markup Language (VoiceXML) 3.0

Table 79: 85: Attributes


Input: [Name] expr [Description] The initial value of the form item variable. If initialized to a value, then the form item will not be visited unless the form item variable is cleared. [Required] No [Default Value] ECMAScript undefined [Type]

Output: TBD

Voice Extensible Markup Language (VoiceXML) 3.0

Table 79: 85: Attributes


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

Output: data model expression

Voice Extensible Markup Language (VoiceXML) 3.0

Table 79: 85: Attributes


Input: [Name] modal [Description] If this is true, all non-local speech and DTMF grammars are not active while making the recording. If this is false, non-local speech and DTMF grammars are active. [Required] No [Default Value] true [Type]

Output: boolean

Voice Extensible Markup Language (VoiceXML) 3.0

Table 79: 85: Attributes


Input: [Name] beep [Description] If true, a tone is emitted just prior to recording. [Required] No [Default Value] false [Type]

Output: boolean

Voice Extensible Markup Language (VoiceXML) 3.0

Table 79: 85: Attributes


Input: [Name] maxtime [Description] The maximum duration to record. [Required] No [Default Value] Platform-specific value [Type]

Output: Time Designation

Voice Extensible Markup Language (VoiceXML) 3.0

Table 79: 85: Attributes


Input: [Name] finalsilence [Description] The interval of silence that indicates end of speech. [Required] No [Default Value] Platform-specific value [Type]

Output: Time Designation

Voice Extensible Markup Language (VoiceXML) 3.0

Table 79: 85: Attributes


Input: [Name] dtmfterm [Description] If true, any DTMF keypress will be treated as a match of an active (anonymous) local DTMF grammar. [Required] No [Default Value] true [Type]

Output: boolean

Voice Extensible Markup Language (VoiceXML) 3.0

Table 79: 85: Attributes


Input: [Name] type [Description] The media format of the resulting recording. [Required] No [Default Value] Platform-specific (one of the required formats) [Type]

Output: Required audio file formats specified in Appendix E of VoiceXML 2 (Other formats may also be supported)

Voice Extensible Markup Language (VoiceXML) 3.0

Table 79: 85: Attributes


Input: [Attribute Name] src [Details]

Output: Is an ECMAScript expression which returns a character string identifying the URI of the dialog document that the dialog interpreter should prepare.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] type [Details]

Output: An OPTIONAL ECMAScript expression which returns a character string that specifies the MIME type of the document, and as a result, determines which dialog manager environment is actually used. A MIME type of "application/xml+vxml" requests a VoiceXML interpreter instance. A MIME type of "audio/wav" requests a dialog manager that merely plays wave files. If omitted, the type attribute defaults to "application/xml+vxml".

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] namelist [Details]

Output: An OPTIONAL list of one or more CCXML variable names. These variable names and their associated values will be added to the URI, specified by the src attribute, as a query string. The complete URI, including query string, is sent to the selected dialog manager.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] dialogid [Details]

Output: An OPTIONAL ECMAScript left-hand-side expression that will receive a dialog identifier value for the launched dialog interpreter instance. This identifier may be used on future invocations of or .

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] connectionid [Details]

Output: Is an OPTIONAL ECMAScript expression which returns the identifier of a connection. The specified connection will be associated with the dialog being prepared.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] conferenceid [Details]

Output: Is an ECMAScript expression which returns an identifier of a conference bridge. A connection will be allocated for the dialog being prepared.

Voice Browser Call Control: CCXML Version 1.0


Input: [Title] Valid credits Element With Single credit Element [Description]

Output: The credits element matches the schema and it contains one credit child element. This should be linked to a testable assertion in the spec.


Input: [Title] Valid credits Element With Two credit Elements [Description]

Output: The credits element matches the schema and it contains two credit child elements. This should be linked to a testable assertion in the spec.


Input: [Title] More Than One credits Element [Description]

Output: The credits element occurs more than once. This should be linked to a testable assertion in the spec.


Input: [Title] No credit Element in credits Element [Description]

Output: The credits element does not contain a credit child element. This should be linked to a testable assertion in the spec.


Input: [Title] Unknown Attribute in credits Element [Description]

Output: The credits element contains an unknown attribute. This should be linked to a testable assertion in the spec.


Input: [Title] Unknown Child Element in credits Element [Description]

Output: The credits element contains an unknown child element. This should be linked to a testable assertion in the spec.


Input: [Title] Content in credits Element [Description]

Output: The credits element contains an content. This should be linked to a testable assertion in the spec.


Input: [Definition] Character data [Attribute Type]

Output: CDATA


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

Output: ID


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

Output: IDREF


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

Output: IDREFS


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

Output: NAME


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

Output: NMTOKEN


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

Output: NMTOKENS


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

Output: PCDATA


Input: [Field Name] name [Details]

Output: 'dialog.user.*'

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] dialogid [Details]

Output: The ID of the dialog.

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] connectionid [Details]

Output: The identifier of the connection to which the dialog connection is bridged (usually the connectionid that was specified in the ). If the dialog is bridged to a conference the value will be null.

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] conferenceid [Details]

Output: The identifier of the conference to which the dialog connection is bridged (usually the conferenceid that was specified in the ). If the dialog is bridged to a connection the value will be null.

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] namelist [Details]

Output: List of items that are stored on the values sub-object.

Voice Browser Call Control: CCXML Version 1.0


Input: [Field Name] values.* [Details]

Output: Values associated with the event.

Voice Browser Call Control: CCXML Version 1.0


Input: [Property] additionalType [Description] An additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax. [Expected Type]

Output: URL

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


Input: [Property] description [Description] A short description of the entry. [Expected Type]

Output: Text

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


Input: [Property] image [Description] URL of an image of the entry. [Expected Type]

Output: URL

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


Input: [Property] name [Description] The name of the entry. [Expected Type]

Output: Text

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


Input: [Property] url [Description] URL of the entry. [Expected Type]

Output: URL

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


Input: [Property] alternativeHeadline [Description] A secondary title of the entry. [Expected Type]

Output: Text

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


Input: [Property] inLanguage [Description] The language of the content. Please use one of the language codes from the IETF BCP 47 standard. [Expected Type]

Output: Language

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


Input: [Property] dateCreated [Description] The date on which the content was created (in ISO 8601 date format). [Expected Type]

Output: Date

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


Input: [Property] dateModified [Description] The date on which the content was most recently modified (in ISO 8601 date format). [Expected Type]

Output: Date

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


Input: [Property] keywords [Description] The keywords/tags used to describe this content. [Expected Type]

Output: Text

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


Input: [Property] provider [Description] Specifies the person or organization that distributed the content. [Expected Type]

Output: Person or Organization

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


Input: [Property] breadcrumb [Description] A set of links that can help a user understand and navigate a website hierarchy. [Expected Type]

Output: Text

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


Input: [Property] entryID [Description] The identifier of the entry. [Expected Type]

Output: Text

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


Input: [Property] isEntryOf [Description] Indicates the database to which the entry belongs. [Expected Type]

Output: BiologicalDatabase

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


Input: [Property] taxon [Description] The taxonomy information of the entry. [Expected Type]

Output: BiologicalDatabaseEntry or Text

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


Input: [Property] seeAlso [Description] Reference to another resource. [Expected Type]

Output: BiologicalDatabaseEntry or URL

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


Input: [Property] reference [Description] The identifier of the reference, such as PMID, DOI, and PMCID. For example: . [Expected Type]

Output: Text

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


Input: [user.] name. [Category] Physical Contact Information, Demographic and Socioeconomic Data [Type] personname. [Short display name]

Output: User's Name


Input: [user.] bdate. [Category] Demographic and Socioeconomic Data [Type] date. [Short display name]

Output: User's Birth Date


Input: [user.] cert. [Category] Unique Identifiers [Type] certificate [Short display name]

Output: User's Identity Certificate


Input: [user.] gender [Category] Demographic and Socioeconomic Data [Type] gender [Short display name]

Output: User's Gender


Input: [user.] employer [Category] Demographic and Socioeconomic Data [Type] text [Short display name]

Output: User's Employer


Input: [user.] department [Category] Demographic and Socioeconomic Data [Type] text [Short display name]

Output: Department or division of organization where user is employed


Input: [user.] jobtitle [Category] Demographic and Socioeconomic Data [Type] text [Short display name]

Output: User's Job Title


Input: [user.] home. [Category] Physical Contact Information, Online Contact Information, Demographic and Socioeconomic Data [Type] contact. [Short display name]

Output: User's Home Contact Information


Input: [user.] business. [Category] Physical Contact Information, Online Contact Information, Demographic and Socioeconomic Data [Type] contact. [Short display name]

Output: User's Business Contact Information


Input: [Property] clear [Values] none | left | right | both [Initial] none [Applies to] block-level elements [Inh.] no [Media] visual [Percentages]


Input: [Property] display [Values] inline | block | inline-block | list-item | run-in | compact | table | inline-table | table-row-group | table-header-group | table-footer-group | table-row | table-column-group | table-column | table-cell | table-caption | ruby | ruby-base | ruby-text | ruby-base-group | ruby-text-group | | none [Initial] inline [Applies to] all elements [Inh.] no [Media] visual (‘none’ applies to all media) [Percentages]


Input: [Property] float [Values] left | right | none | [Initial] none [Applies to] all, but see 9.7 [Inh.] no [Media] visual [Percentages]


Input: [Property] height [Values] | | auto [Initial] auto [Applies to] all elements but non-replaced inline elements, table columns, and column groups [Inh.] no [Media] visual [Percentages]

Output: see prose


Input: [Property] margin [Values] [ | | auto ]{1,4} [Initial] (see individual properties) [Applies to] see text [Inh.] no [Media] visual [Percentages]

Output: width* of containing block


Input: [Property] margin-top , margin-right, margin-bottom, margin-left [Values] | | auto [Initial] 0 [Applies to] see text [Inh.] no [Media] visual [Percentages]

Output: width* of containing block


Input: [Property] marquee-direction [Values] forward | reverse [Initial] reverse [Applies to] same as ‘overflow’ [Inh.] yes [Media] visual [Percentages]


Input: [Property] marquee-loop [Values] | infinite [Initial] 1 [Applies to] same as ‘overflow’ [Inh.] no [Media] visual [Percentages]


Input: [Property] marquee-speed [Values] slow | normal | fast [Initial] normal [Applies to] same as ‘overflow’ [Inh.] no [Media] visual [Percentages]


Input: [Property] marquee-style [Values] scroll | slide | alternate [Initial] scroll [Applies to] same as ‘overflow’ [Inh.] no [Media] visual [Percentages]


Input: [Property] max-width, max-height [Values] | | none [Initial] none [Applies to] all elements but non-replaced inline elements, table rows, and row groups [Inh.] no [Media] visual [Percentages]

Output: refer to width, resp. height of containing block


Input: [Property] min-width, min-height [Values] | | inherit [Initial] 0 [Applies to] all elements but non-replaced inline elements, table rows, and row groups [Inh.] no [Media] visual [Percentages]

Output: refer to width, resp. height of containing block


Input: [Property] overflow [Values] [ visible | hidden | scroll | auto | no-display | no-content ]{1,2} [Initial] see individual properties [Applies to] non-replaced block-level elements and non-replaced ‘inline-block’ elements [Inh.] no [Media] visual [Percentages]


Input: [Property] overflow-style [Values] auto | [scrollbar | panner | move | marquee] [, [scrollbar | panner | move | marquee]]* [Initial] auto [Applies to] same as ‘overflow’ [Inh.] yes [Media] visual [Percentages]


Input: [Property] overflow-x, overflow-y, [Values] visible | hidden | scroll | auto | no-display | no-content [Initial] visible [Applies to] non-replaced block-level elements and non-replaced ‘inline-block’ elements [Inh.] no [Media] visual [Percentages]


Input: [Property] padding [Values] [ | ]{1,4} [Initial] (see individual properties) [Applies to] all elements [Inh.] no [Media] visual [Percentages]

Output: width* of containing block


Input: [Property] padding-top , padding-right, padding-bottom, padding-left [Values] [ | ] [Initial] 0 [Applies to] all elements [Inh.] no [Media] visual [Percentages]

Output: width* of containing block


Input: [Property] rotation [Initial] 0 [Applies to] block-level elements, inline-table and inline-block [Inh.] no [Media] visual [Percentages]


Input: [Property] rotation-point [Initial] 50% 50% [Applies to] block-level elements [Inh.] no [Media] visual [Percentages]

Output: Width and height of border box


Input: [Property] visibility [Values] visible | hidden | collapse [Initial] visible [Applies to] all elements [Inh.] yes [Media] visual [Percentages]


Input: [Property] width [Values] | | auto [Initial] auto [Applies to] all elements but non-replaced inline elements, table rows, and row groups [Inh.] no [Media] visual [Percentages]

Output: refer to width of containing block


Input: [Attribute Name] next [Details]

Output: an ECMAScript expression which returns the URI of the CCXML document to be fetched.

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] namelist [Details]

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] method [Details]

Output: an ECMAScript expression which returns a character string that indicates the HTTP method to use. Valid values are " get " and " post ". The default is " get ".

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] fetchid [Details]

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] synch [Details]

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Attribute Name] timeout [Details]

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

Voice Browser Call Control: CCXML Version 1.0


Input: [Feature] Level of abstraction [Webinos proposal] Javascript API to obtain Javascript-based Service APIs [Opera/CableLabs proposal] Javascript API to obtain HTTP Service URL endpoints [Google Web Intents] Javascript API to allow client web application to find and communicate with service web application [Google Web Introducer]

Output: Javascript API to allow client web application to find and communicate with service web application

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Relation to underlying low level discovery/communication mechanisms [Webinos proposal] Agnostic to underlying low levels discovery/communication mechanisms. This is subject for implementation of discovery infrastructure and services based on supported low level discovery and communication mechanisms [Opera/CableLabs proposal] Agnostic to underlying low levels discovery/communication mechanisms (but includes standard processing rules for Zeroconf and UPnP). [Google Web Intents] None [Google Web Introducer]

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Location of services [Webinos proposal] In device, locally connected, local network and web-based services [Opera/CableLabs proposal] In device, locally connected, local network and web-based services [Google Web Intents] Anywhere, service is represented by a web application that hides any underlying low level service access methods [Google Web Introducer]

Output: Anywhere, service is represented by a web application that hides any underlying low level service access methods

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Network infrastructure required [Webinos proposal] Underlying infrastructure for registering user’s devices/services (more details) [Opera/CableLabs proposal] Both an underlying Zeroconf and UPnP infrastructure [Google Web Intents] None (Claes: Rich, I believe a “Web Intents server”is needed. Please explain your view [Google Web Introducer]

Output: “Web Introducer server”

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Identification of service type [Webinos proposal] URI identifying a JavaScript API to access the service [Opera/CableLabs proposal] Service type tokens exposed from the underlying discovery mechanisms [Google Web Intents] A service (intent) is defined by: Action: a URI defining what to do (share, pick, view, etc) Type: the data type to perform the action on (image, url, json etc) [Google Web Introducer]

Output: A service (intent) is a string identifying an interaction pattern between a Client and a Service. Examples are bookmark for sharing, link to media file, user's stream of incoming SMSs

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Security / access control [Webinos proposal] Based on user selection of discovered service and security mechanisms implemented for respective services. A distributed approach where policy decisions are hosted in a Personal Zone. [Opera/CableLabs proposal] Based on user selection of discovered service and security mechanisms implemented for respective services. Assumes that access control is handled in the UA. [Google Web Intents] Based on user selection of discovered service and security mechanisms implemented for respective services [Google Web Introducer]

Output: Based on user selection of discovered service and security mechanisms implemented for respective services

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Service registration [Webinos proposal] An application can register new services through a statement in the manifest file [Opera/CableLabs proposal] UA silently (i.e. in the background) handles discovery and registration of services from the local device, local network. UA also silently handles service discovery and registration on visited web sites. [Google Web Intents] To make a service (intent) discoverable it need to be registered in the UA through a simple API. The services Action, Type and URL to a web page that implements the service is registered. For example, in-page meta header registration syntax is collected as the user browses their web sites. [Google Web Introducer]

Output: To make a service (intent) discoverable it need to be registered in the UA through a simple API. The service's name, supported intent strings, icons, URLs to service pages are registered.

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Discovery process [Webinos proposal] UA searches for networked services at API invocation.A successCallback is issued for each service found. Timer for how long search process lasts could be set. Pending search process can be canceled [Opera/CableLabs proposal] UA searches for networked services (the timing of which is at the discretion of the UA) in the local network and on user visited web sites and maintains a list of currently available services. [Google Web Intents] A web application wanting to use a service calls a simple API stating the requested Action and Type. An iframe allows the user to select one of the registered services for this Action and Type. [Google Web Introducer]

Output: A web application wanting to use a service calls a simple API stating the requested intent. An iframe or a new window allows the user to select one of the registered services for this intent.

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Search filter [Webinos proposal] Yes. Allows web application to search for services belonging to certain user(s), to state remote or local only services and to state location of service. Also allows the page to set a timer for how long search process lasts could be set. Pending search processes can be canceled. [Opera/CableLabs proposal] No [1]. [Google Web Intents] No. [Google Web Introducer]

Output: No.

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Communication with service [Webinos proposal] A standardized / “well-known” JavaScript API is provided to the web application to access the service. [Opera/CableLabs proposal] A URL, extracted directly from the underlying service discovery process, is provided to the web application to access the service. The web page can then use standard XmlHttpRequest, Web Sockets, Server-Sent Events and Web Messaging, etc (all with implicit cross-origin resource sharing) to communcate with the service. Protocol depends on messaging format implemented in device implementing service (e.g. json, protobufs, text-based, xml, etc). [Google Web Intents] Data is sent bi-directionally between client web application page and the service web page through the Web Intents API. The format/protocol of this data exchange is defined for each Action by the Web Intents specification. Underlying communication mechanism is web messaging but this level is hided to the application developer. [Google Web Introducer]

Output: Data is sent bi-directionally between client web application page and the service web page through Web Messaging. The format/protocol of this data exchange must be defined for each Intent by specific API/protocol specifications for each intent type.

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Service status monitoring [Webinos proposal] onLost callback when found but not yet bound service is lost. onServiceUnavaialble and onServiceAvailable callbacks for bound services. [Opera/CableLabs proposal] readyState changes fire back to web page's network service objects. readystatechange events occur on a network service object when the service becomes available or unavailable. servicesAvailable attribute is used to monitor general number of services of the authorized type currently available in the user's network(s). [Google Web Intents] No service status monitoring in the Web Intents API itself but guess that this could be handled in the specific protocol for the specific Action. [Google Web Introducer]

Output: No service status monitoring in the Web Introducer API itself but guess that this could be handled in the specific protocol for the specific intent type.

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] Service binding lifecycle [Webinos proposal] Service binding valid until unbind() is called or client page is left. Later the binding to the service can be resumed using the saved service id. [Opera/CableLabs proposal] Opera to elaborate [Google Web Intents] To be completed [Google Web Introducer]

Output: To be completed

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Feature] .... [Webinos proposal] ... [Opera/CableLabs proposal] ... [Google Web Intents] .... [Google Web Introducer]

ServiceDiscoveryComparison - DAP WG Wiki


Input: [Topic] PHP history and uses [Evaluation Methods] Final exam [Competency]

Output: Explain the difference between server side and client side scripts. Summarize the origin and development of PHP. List and briefly describe the most common alternatives to PHP. List some well known web sites and applications that has been built in PHP. Briefly explain the concept of Open Source. List some well-known public mailing lists, IRC channels and discussion forums where you can find help with PHP.

Es/Interact/Secuencias de comando del lado servidor 1 - Web Education Community Group


Input: [Topic] Installation and basic configuration of PHP and an IDE [Evaluation Methods] Module 1: Installation Final exam [Competency]

Output: Demonstrate installing an HTTP-server, PHP and MySQL on a computer. Demonstrate the usage of php.ini and .htaccess Explain why display_errors should be off on a production web server. List some commonly used PHP-modules and demonstrate how to activate them on a web server. Demonstrate how to get information about a PHP-installation using phpinfo() and php -m. Demonstrate how to use PHP CLI. Demonstrate how to install an IDE or editor for PHP development. Explain the purpose and usage of development and staging servers. Explain the purpose of a version control system.

Es/Interact/Secuencias de comando del lado servidor 1 - Web Education Community Group


Input: [Topic] Basic PHP syntax [Evaluation Methods] Module 1: Installation Final exam Final assignment [Competency]

Output: Demonstrate how to switch between HTML-mode and PHP mode. List what types of php tags that you can use, and explain the potential pitfalls of using short open tags. (Note to teachers: Turn open tags off on the server you provide.) Demonstrate how to use single line, multi line and PhpDoc-style comments. Demonstrate how to separate instructions. Demonstrate how to use the echo and print statements. Recognize the differences between the two.

Es/Interact/Secuencias de comando del lado servidor 1 - Web Education Community Group


Input: [Topic] Using PHP as a simple template engine [Evaluation Methods] Assignment 1: Use PHP as a Template System [Competency]

Output: Explain the concept of server side includes and why it is better than client side frames. Describe the differences between PHP’s include, include_once, require and require_once commands. Explain performance benefits of using absolute paths when including files. Explain why included files should always reside outside of the server root directory. Demonstrate how PHP can make client side frames redundant.

Es/Interact/Secuencias de comando del lado servidor 1 - Web Education Community Group


Input: [Topic] PHP best practices overview [Evaluation Methods] (Most assignments will touch upon these concepts in some way.) Final assignment. Final exam. [Competency]

Output: Note: This is meant as an overview. No in-depth knowledge yet. Briefly discuss key characteristics of a well written PHP_application. Demonstrate how to write readable and properly indented code. Demonstrate basic knowledge about coding conventions, especially the PEAR coding standard. Explain what revision control is. Show basic knowledge about phpDocumentor. Use the most basic tags in phpDocumentor and produce generated documentation for your code. Explain what bug tracking is. List a few well known bug trackers.

Es/Interact/Secuencias de comando del lado servidor 1 - Web Education Community Group


Input: [Topic] Programming concepts [Evaluation Methods] (Modules with exercises are appreciated.) Final assignment. Final exam. [Competency]

Output: Explain the concept of identifiers and list some identifier names one is not allowed to use in PHP. Explain the concept of sigils. Explain the consept of data types and compare strong and weak typing. Demonstrate type checking and type juggling. Recognize that all user-submitted data, and all data-base results, are strings to PHP. Demonstrate how to check for numeric values in strings. Explain the null value, and describe the difference between variables that are null and variables that have not been set. Demonstrate how to use the isset() and empty() functions. Explain what values in PHP that convert to false, when used in a boolean check. Demonstrate usage of variables and constants, using best practice naming conventions. Recognize the different kinds of constants in PHP (built in, magic, user defined; global, class). Demonstrate different syntaxes for setting constants (define and const - also for global constants since PHP 5.3) Explain the concept of statements. Demonstrate correct usage of statements and block statements. Explain the concept of expressions. Demonstrate correct usage of expressions. Explain what operators are and demonstrate correct usage of all common operators. Explain the concept of functions and all associated terminology and demonstrate how to write and use functions. Explain and use assignment by value and assignment by reference. Explain what arrays are in PHP and contrast the implementation to a few other programming languages. Demonstrate how to create and manipulate arrays and how to access individual items in arrays. Recognize all error levels in PHP and explain the difference between an error and an exception. Demonstrate how to handle errors appropriately.

Es/Interact/Secuencias de comando del lado servidor 1 - Web Education Community Group


Input: [Topic] HTTP [Evaluation Methods] Module 2 (a): Emulate HTTP-connections with netcat or telnet Module 2 (b): Analyze HTTP-traffic using Firebug or a similar tool. Final assignment. Final exam. [Competency]

Output: Explain the most commonly used HTTP methods (get, post, head) Demonstrate how to fetch information from the client using $_SERVER. Explain MIME-types, and demonstrate how to set MIME-types using PHP’s header-function.

Es/Interact/Secuencias de comando del lado servidor 1 - Web Education Community Group


Input: [Topic] Character encoding [Evaluation Methods] Assignment 3. Final assignment Final exam Extra questions for SS 2: Explain what a BOM is and how it can cause problems for PHP scripts. What is the difference between little endian and big endian UTF-16? What is Unicode normalization? [Competency]

Output: Note: For any audience using non ascii-characters (almost everybody outside the USA and UK) this is essential! Describe the basics of character encodings and compare the terminology used by Unicode to the terminology used in HTTP-headers encoding vs. charset. Demonstrate how to specify the encoding used in a script (the setting on your editor or IDE). Explain the difference between multi-byte encodings and single-byte encodings. Demonstrate how to use multi-byte string functions in PHP 5.x. Recognize problems that might occur in PHP because of misinterpreted character encodings. Demonstrate how to set character encoding in HTTP-headers, using the http-server tools and PHP. List the characters that have a highest potential for abuse (e.g. “null” and “eof”) and demonstrate how to filter input to avoid them using ctype functions. Demonstrate how to set the encoding (and collation) in a MySQL table or field, using PhpMyAdmin or a similar tool. Demonstrate how to convert text between different encodings.

Es/Interact/Secuencias de comando del lado servidor 1 - Web Education Community Group